Control-M SaaS
Control-M Makes Batch Job Monitoring Organized and Reliable
Powerful Workflow Orchestration, But UI and Pricing Need Improvement
As a result, operational reliability improves because job failures and bottlenecks are easier to spot, troubleshoot, and resolve. It also helps ensure dependent tasks run in the right sequence and that critical workflows finish on time. Overall, it reduces manual effort, increases visibility, and makes large-scale workflow management significantly easier.
Effective Centralization Despite a Steep Learning Curve
Simplifying Complex Workflow Automation
Control-M: Exceptional Reliability for Complex Enterprise Workflows
A Reliable Backbone for Enterprise Job Scheduling
Mainframes jobs Scheduling and monitor tool helps in managing Billion-dollar batch processing
It connects well with other systems too, not just mainframe jobs, but distributed systems and file transfers as well which helps in my quick job's flow and its dependencies. So I get one place to track everything.
It performs well even when hundreds of jobs run during peak overnight batch cycles which process high Business logics. I can quickly see what ran, what triggered it, and what's next(dependencies), which makes troubleshooting fast and helps with daily Processing
Support has been reliable, with regular updates from BMC. I've also noticed newer versions adding AI features like predictive alerts, which is a good step forward. But we are exploring these features and trying to integrate with our systems.
And what impresses me most is that mainframe technology is almost 60 years old, and it's still running strong today - with Control-M playing a big part in keeping it going smoothly.
It notify jobs failures via emails which help me in my support of jobs and with AI in place we are adding features where person who is responsible for production is notified via a call
Unified automation has reduced manual file transfers and now improves end‑to‑end monitoring
What is our primary use case?
Control-M is used for MFT service MFT features in daily work because files are transferred from one server to the target, and it is used primarily for integration between two systems. It is also used for scheduling and managing SAP jobs.
One workflow managed with Control-M currently involves encrypting files and transferring them to the bank, where the source system is encrypted and the encrypted file is transferred, which is easier to analyze and prevents breaches of flat files.
Control-M is used for MFT-based managed file transfers across different businesses globally, and the features provided by MFT in Control-M are believed to be the best for transferring files between on-premise and cloud systems.
Approximately 20 to 30 people use Control-M in the organization, performing various roles such as job configuration, administration, and usage for MFT and SAP jobs.
Control-M usage is being increased and businesses globally are being engaged to expand its implementation.
What is most valuable?
The favorite feature of Control-M is MFT manage file transfer, which is easy to integrate with other systems. It is used daily, and the API is utilized for admin activities and triggering Control-M jobs.
The API in Control-M helps automate tasks, such as creating jobs automatically using code in Visual Studio, enabling workload policies, job creation, and sharing the API swagger with the business to trigger Control-M jobs.
Control-M is a good tool with the best features for SAP scheduling.
Control-M has positively impacted Saint-Gobain by reducing manual work in file transfers, allowing automation of tasks, improvement of SLA, and enhancement of daily work and workload.
Control-M has improved organizational functionality by providing one platform to monitor jobs easily and access detailed logs to track SAP and MFT jobs with end-to-end visibility of job dependencies.
What needs improvement?
One area for improvement in Control-M is the ability to encrypt and decrypt files without needing to install an agent on the other side, and better customization options for SharePoint access in line with Saint-Gobain policy would be appreciated.
DevOps integration into Control-M needs to be explored more, as it is currently not being used in the organization but the potential benefits are evident.
For how long have I used the solution?
I have been working in my current field for almost 11 years.
What do I think about the stability of the solution?
Control-M is stable.
What do I think about the scalability of the solution?
Control-M's scalability is good.
How are customer service and support?
Customer support for Control-M is excellent, and that aspect is greatly appreciated.
Which solution did I use previously and why did I switch?
Previously, scripting was used for file transfers, which did not allow proper monitoring, leading to the switch to Control-M for both file transfers and SAP.
Other options were not evaluated before choosing Control-M because its features and functionalities were recognized in advance.
How was the initial setup?
Before Control-M, scripts had to be created manually for file transfers, which took a significant amount of time. With Control-M, jobs are simply set up through drag and drop, which has reduced effort significantly.
What about the implementation team?
Control-M is used for MFT-based managed file transfers across different businesses globally, and the features provided by MFT in Control-M are believed to be the best for transferring files between on-premise and cloud systems.
What was our ROI?
Although specific data is not available, Control-M has saved time in future implementations of end-to-end flows, making monitoring easier.
What's my experience with pricing, setup cost, and licensing?
Control-M pricing is good, though it is somewhat expensive; still, it offers great features.
Which other solutions did I evaluate?
Other options were not evaluated before choosing Control-M because its features and functionalities were recognized in advance.
What other advice do I have?
I advise others looking into using Control-M to experience its ease of monitoring jobs on a single user-friendly platform, streamlining job creation and monitoring.
The biggest lesson learned from using Control-M is that it reduces manual effort and increases productivity.
Control-M is effective for scheduling, managing, and monitoring workflows, and it is crucial for DevOps initiatives as it provides a single platform for monitoring related jobs, helping to reduce SLAs.
Control-M is good for my needs, and I would rate this review as a five out of five.
Centralized automation has improved cross-platform workflows and reduces manual operational effort
What is our primary use case?
Control-M is primarily used to automate and monitor critical operational and database-related jobs, such as backups, batch processing, and application workflows. It helps reduce manual interactions and provides centralized monitoring while improving reliability and ensuring that dependent processes execute in the correct sequence. Overall, Control-M is a valuable tool for maintaining operational efficiency and reducing scheduling-related risks.
The primary daily use case for Control-M is scheduling and monitoring automated jobs, such as database backup jobs, archive log backups, and maintenance tasks and batch processing workflows. It is also used to monitor job dependencies, track failures, and receive alerts so that issues can be resolved quickly with minimum manual interactions. Control-M is used daily to automate and monitor database maintenance jobs, backup workflows, and batch processes. The centralized monitoring and alerting capabilities help ensure that critical workflows complete successfully and on schedule.
Beyond job scheduling, Control-M is used for end-to-end workload automation, monitoring critical business processes, and managing cross-application dependencies. It helps ensure that database maintenance jobs, backup processes, file transfers, and batch workloads execute in the correct sequence with minimal manual interactions. The centralized monitoring, alerting, and restart capabilities help reduce operational overhead and improve service reliability. Control-M provides good visibility into workflow status, making it easier for supporting teams to identify and resolve issues quickly. Control-M is a key tool for workload automation and operational monitoring. It helps automate repetitive tasks, manage job dependencies, provide proactive alerts, and ensure critical business processes run reliably. This has significantly reduced manual effort and improved overall operational efficiency.
Control-M is deployed as a centralized workflow automation platform that supports multiple applications and databases across several environments throughout the organization. Different application teams use it to schedule and manage their batch workloads, while operations and support teams use the centralized monitoring and alerting capabilities to track job execution and respond to issues. The platform enables workflow architecture across Windows, Linux, Unix, database, and application environments while providing a single point of control for all critical business processes.
Control-M is relatively easy to integrate with different technologies and operational requirements. One of its strengths is the broad support for multiple platforms, applications, databases, and file transfer processes. This helps organizations bring diverse workflows under a centralized automation framework. It provides integration capabilities that reduce the need for custom scheduling solutions and manual coordination between systems. As DevOps, one opportunity is to continue simplifying onboarding and integration.
Control-M has been integrated with the Oracle database environment to automate backup and log backup and maintenance jobs. This integration significantly reduced manual interaction, improved scheduling reliability, and provided centralized monitoring and alerting. As a result, the organization was able to identify and resolve job failures more quickly and ensure that critical database operations were completed on time. Database integration is most relevant to the role. ServiceNow integration has also been implemented. When critical jobs fail, alerts are tracked and managed more effectively through ServiceNow integration, reducing response times and improving operational visibility. Cloud integrations with Azure have been utilized. Integrating Control-M with Azure-based workloads enabled automation and monitoring of cloud-hosted processes alongside on-premises jobs. This provides a unified view of workflows and improves operational efficiency across environments. One of the most valuable integrations has been with the database environment.
What is most valuable?
The most valuable features of Control-M are its centralized monitoring, workload automation, job scheduling, job dependencies management, and proactive alerting capabilities. Control-M allows teams to schedule and manage complex workflows across multiple platforms from a single interface, improving visibility and operational control. It supports both calendar-based and event-driven scheduling and provides automated notifications for job failures. It enables quick recovery and rerun of jobs when issues occur. These features help reduce manual effort, improve reliability, and ensure critical business processes run smoothly.
The best features of Control-M are centralized job monitoring, workload automation, dependency management, proactive alerting, and cross-platform scheduling. These capabilities help automate critical business processes, reduce manual effort, improve operational visibility, and ensure reliable execution of batch workflows across multiple systems. The ability to quickly identify and troubleshoot and restart failed jobs is particularly valuable for operational teams.
Control-M is much more than a simple job scheduler. Its real value comes from workload automation, dependency management, and centralized monitoring across multiple systems and applications. Once workflows are properly designed, it can significantly reduce manual effort, improve operational reliability, and provide better visibility into critical business processes. Features such as automated alerts, job restart capabilities, historical tracking, and cross-platform integration make day-to-day operations easier and help teams respond quickly when issues occur.
What needs improvement?
Control-M is a reliable workload automation platform. There is an opportunity for improvement in troubleshooting failed jobs in complex workflows, as this can sometimes be time-consuming, especially when multiple dependencies are involved. Improved root cause analysis, more intuitive error messages, and enhanced reporting capabilities would help operations teams resolve issues faster. Additionally, a more modern and responsive user interface would improve overall user experience.
From an operational support perspective, complex dependency chains can be difficult to troubleshoot, and error messages could provide more actionable details. Reporting on dashboard customizations could be more flexible. The user interface could be more modern and user-friendly, and faster search and filtering capabilities for large job environments would be beneficial. While Control-M is a robust and dependable automation tool, troubleshooting failures in complex job workflows can sometimes be challenging. Improved root cause analysis, richer alert details, and enhanced reporting would further improve operational efficiency and reduce investigation time for support teams.
One improvement that would be valuable is the use of more intelligent monitoring and analytics capabilities. For example, predictive alerts that identify potential job delays and failures before they occur would help operations teams act proactively and enhance root cause analysis. Artificial intelligence assistance for troubleshooting recommendations and more customizable dashboards would improve efficiency. Additionally, simplifying the management of complex job dependencies and providing clear visual workflow views would make day-to-day operations easier.
For how long have I used the solution?
I have been using BMC Control-M for the past six years.
What other advice do I have?
Control-M should be highly rated for building, scheduling, managing, and monitoring production workflows. Its strength lies in providing a centralized platform where complex workflows can be designed, scheduled, and managed across multiple systems and applications. The dependency management capabilities help ensure that workflows execute in the correct sequence, while real-time monitoring and alerting provide visibility into job status and exceptions.
Control-M is extremely important for database and DevOps initiatives because many business processes depend on multiple interconnected systems, including applications, databases, and file transfers. Control-M provides a centralized way to coordinate these workflows and manage dependencies across different platforms. This helps ensure that tasks execute in the correct order and that downstream processes only begin when prerequisite activities have been completed. From a team efficiency perspective, it reduces the amount of manual monitoring and interaction required to manage complex workflows. Automated scheduling, centralized visibility, and a proactive alerting system support focus on issue resolution and process improvements rather than routine operational activities.
Control-M provides strong controls around user access and authorization, auditing, and workload management through role-based access. This helps ensure that users only have the permissions required for their responsibilities. Audit and activity tracking provide accountability and support complex requirements. Control-M also supports secure authentication, encrypted communications, and detailed monitoring of job scheduling, job execution, and workflow changes. The focus on governance and automation rather than uncontrolled oversight is appreciated. Control-M should be considered from governance and security standpoints. Features such as role-based access control and auditing demonstrate Control-M's emphasis on governance.
Based on my experience, the artificial intelligence-related capabilities appear reliable for operational assistance, workflow insights, and accelerating routine tasks. The outputs are generally useful and align with the information available within the platform. For business-critical activities, human review and validation remain important, especially when making operational decisions or implementing workflow changes. No major reliability concerns have been observed, but as with any artificial intelligence-enabled capabilities, external validation is necessary to ensure accuracy and context. What provides confidence is that Control-M combines artificial intelligence capabilities with governance, monitoring, auditability, and operational control. While outputs from artificial intelligence would still be validated for critical decisions, the combination of artificial intelligence with governance, auditing, and control mechanisms increases confidence in the platform's recommendations and outputs. I would rate Control-M an eight out of ten overall.
Workflow has provided end-to-end ownership and consistently improves on-time client deliveries
What is our primary use case?
My main use case for Control-M is to deliver the client's cases.
A recent example of how I use Control-M to deliver a client's case involved a complex client case with several moving parts and a tight delivery timeline. I took control by first clarifying the client's requirements, breaking the case down into specific actions, and ensuring that I understood the responsible deadlines. By keeping the client priorities focused, we ultimately delivered the case on time and to the expected standard.
What is most valuable?
The best features of Control-M are the ability to take ownership of a case from start to finish, keep track of all important details, and ensure nothing gets missed.
Control-M has positively impacted my organization by providing better visibility, consistency, and accountability across the client cases. It helps us stay organized, track work more effectively, and ensure that important actions and follow-ups are not missed. It has also improved collaboration, as everyone has a clear understanding of what needs to be done.
What needs improvement?
Control-M is functioning well, and I am not aware of any necessary improvements at this time.
For how long have I used the solution?
I have been working in my current field for the past four years.
I have been using Control-M for the last two years.
What other advice do I have?
I would rate Control-M an eight overall on a scale of one to ten.
I gave Control-M an eight because everything is good, but I have not been exploring all the features, which keeps it from being a ten.
I believe Control-M's AI capabilities provide complete assurance of security to us, so there is no issue with governance and security.
I think Control-M's AI capabilities are generally accurate and reliable, especially for handling routine tasks, summarizing information, identifying relevant details, and helping move cases forward.
Control-M is deployed in a cloud-based environment within our organization, with appropriate enterprise security, access controls, and governance measures in place.
We use AWS as our cloud provider.
We purchased Control-M from BMC, and we did not purchase it through the AWS Marketplace.
Control-M is relatively easy to integrate with our existing DataOps and DevOps processes because it can fit into the broader technology ecosystem without requiring major changes to our workflows.
I recommend that others looking into using Control-M understand the business problem and start with a focused use case, validating the results while paying attention to the quality of the data and inputs.