Workload Automation with Streamworks

• Pay per agent
• Pay per job
• SaaS
• Full managed service
• All flat
• Assurance of stable maintenance costs
• Operation of Streamworks in the customer's infrastructure possible
• Simple definition of dependencies on other workflows or external events

• Further development and support from Germany
• Contact persons are experienced Streamworks users from our own company
• Workload automation for 40 years
• Strong quality assurance thanks to productive lead time in our own data centers

• Annual user group meetings with alternating evening events
• Customer influence on the further development of Streamworks via rating

• Data storage completely in German certified data centers
• Data storage exclusively under German law without using global cloud providers
• Long-term assurance of license models

• Little scripting
• Graphic design area
• Definition of any dependencies
• Inheritance concept
• Overview monitoring
• Intelligent incident handling
• Automatic notifications
• Change history for all changes

• House Keeping
• File transfers
• SAP
• Web requests
• Service orchestration
• Cloud Services
• Containers / Kubernetes
• Mainframe
• Integration of any external systems

Workload automation extends pure job scheduling, such as CRON jobs or the Windows Task Scheduler, with additional functions, such as the definition of dependencies between jobs and other jobs or external sources, so that a job is not only triggered by a specific time and date. In order to maintain an overview of the dependencies and simplify data entry, job chains are usually displayed graphically in a workload automation tool. Common external systems such as SAP are well integrated via interfaces so that they can be conveniently controlled.
 

Workload automation tools provide comprehensive monitoring in order to react quickly to errors in job execution (incident handling). To further simplify incident handling, rules for automatic reaction to execution errors and automatic notifications can be defined. Simulations can be carried out before productive job execution to simplify the creation of job definitions and increase quality.

In the context of data security and traceability/audit capability, all changes to job definitions and actions in the context of incident handling are logged and there is user and role management.

Due to the increasing complexity of IT systems, the number of job executions in companies is constantly growing. Workload automation tools have become indispensable for maintaining an overview while saving time and maintaining the quality of job definitions.

They simplify the monitoring of job execution through a single point of view concept and shorten the response time for processing incidents through the use of rules for automatic notification and automated incident handling.
 

They are able to provide information on all changes or actions carried out.

Compared to workload automation, service orchestration and automation platforms (SOAP) focus on the orchestration and automation of IT services and processes that often integrate multiple systems and applications across different environments. They are designed to orchestrate complex workflows that involve multiple services and resources.