Reporting after processing
A reporting task starts once the required data has been processed. Dependencies determine the sequence.
Workload automation and orchestration
BMC Control-M
Coordinate processes that depend on each other.
BMC Control-M manages the sequence and dependencies of application and data workflows. This is called workload automation or workflow orchestration: starting the right step once its prerequisites are complete.
Free of charge and without obligation. Around 30 minutes, through Microsoft Bookings. Privacy information.
One delayed step affects the whole chain
A file needs to arrive, be processed and then become available for a report or another system. If one step runs late, you need to know what it means for the rest. Control-M helps manage these workflows as a connected chain.
What this could look like in practice
Three working situations where this solution could play a part.
SAP and other systems
Steps in SAP and other applications can form part of the same workflow, using the required integrations and agents.
Track a deadline
When a data flow is delayed, central visibility helps assess the next steps and their deadline.
How could this help your organisation?
The right sequence
Define dependencies so connected tasks can follow the agreed process logic.
Visibility into progress
Central visibility and SLA management help track delays. An SLA records service expectations, such as a target completion time.
Coordinate across systems
Cloud environments and local systems can form part of the same workflow. The chosen integrations and modules determine what can be connected.
Which organisations could this suit?
BMC describes applications in financial data workflows, supply chains and telecoms. Their common need is visibility across dependent steps with important deadlines.
A team with a growing workflow
Alongside Enterprise, BMC offers a SaaS Starter Pack for teams. Control-M is therefore not aimed only at the largest organisations; the required setup still determines the fit.
An organisation with critical IT processes
When several systems, dependencies and owners come together, central orchestration can be relevant. A lighter approach may be enough for a single simple task.
What does setting it up involve?
Map the steps, dependencies, deadlines and failure paths. Then establish who manages workflows, access and execution environments.
Connections and agents
Depending on the environment, integrations and agents are required: components that execute tasks in connected environments. Permissions and maintenance form part of that choice.
SaaS or self-managed
With Control-M SaaS, BMC manages the platform. Your organisation retains responsibility for its configuration and agent environments. Self-managed deployment requires a different division of work.
Data, access and control
Central orchestration needs clear arrangements for access, credentials and responsibilities. These differ between SaaS and a self-managed environment.
SSO and roles in SaaS
For Control-M SaaS, BMC documents SAML 2.0 SSO and roles. SSO lets employees use their existing sign-in service; multi-factor authentication can be configured through the identity provider.
SOC 2 Type II for SaaS
BMC lists SOC 2 Type II for Control-M SaaS, an assessment of controls over a period of time. The service and period covered by the report matter when selecting a deployment.
Region and AI options
Regional SaaS options are available. BMC states that AI features can involve additional processing locations. The desired region is therefore assessed alongside the chosen features.
Your process first, then the solution
I am Joshua Boermans, an Automation Consultant at Korper. I assess what could be automated and where it would add value. I then work with technical colleagues to shape a suitable approach. Korper is a partner of the supplier described here.
Understand the work
We discuss the current steps, manual work and exceptions. You do not need to choose a tool beforehand.
Assess the options
We consider the expected value, existing systems and the ongoing management required.
Agree a suitable next step
If automation is a good fit, we identify the technical work needed. We coordinate implementation with the technical team at Korper.
Questions before you choose
Is this the same as RPA?
Control-M focuses on coordinating and executing application and data workflows. RPA can focus on actions inside applications. The appropriate approach depends on the work you want to improve.
Does our entire environment need to move to the cloud?
Control-M supports workflows across cloud environments and local systems. The integrations, agents and chosen deployment need to fit your environment.
Does SaaS take over all management?
BMC manages the SaaS platform. Your organisation remains responsible for areas including configuration, access and its own agent environments.
Where do we start?
With a workflow that currently needs attention: its steps, systems, deadlines and recurring problems. This lets us discuss the orchestration and setup required.
Discuss the process you want to improve
Tell me where the work gets held up. We can explore whether this solution fits and what a useful next step would be.
Free of charge and without obligation. Around 30 minutes, through Microsoft Bookings. Privacy information.