Control-M SaaS
Workflow automation has improved data accuracy and saves hours daily for healthcare analytics
What is our primary use case?
My main use case for Control-M revolves around initially starting with mainframe day-to-day jobs and job scheduling, and recently, we have integrated with SCP as a job as a service, allowing us to monitor and automate workflows.
We are using it for patient-related data, and we have it operational.
Our main business use case for Control-M is analytics, which is crucial in healthcare for running various campaigns that handle significant data from healthcare providers and patients.
The integration of AI or ML workloads in our Control environment primarily comes from the customer side.
We use Control-M's policy, approval, or risk gating capabilities in various scenarios.
In terms of MLOps workflows, we have utilized Vertex AI within Control-M.
We employ Control-M for interactive journey building, automated model retraining, and on-demand forecasting.
While we do not currently use Control-M to orchestrate workloads across multiple environments since we only employ a private cloud, this is something we may explore in the future.
In our organization, we only utilize SAP batch jobs, with no use of non-SAP workflows.
We have used the Control-M Python client for data streaming, mainly to fetch data from existing sources.
We are not exploring the features related to orchestrating Kubernetes jobs or cloud-native workflows during this initial stage, but we may in the future.
How has it helped my organization?
Control-M has positively impacted my organization by improving accuracy, which is crucial in healthcare since we need to be accurate across various channels.
In terms of time saved, as a developer I have saved almost four hours per day, as we previously needed to verify all logs to find issues with data accuracy if something went wrong.
This product helps me catch issues earlier in the day before they become bigger problems, improving my team's efficiency and reducing downtime.
Control-M's ability to free up IT personnel for essential operations is important for our organization.
Control-M has provided measurable benefits like improved SLAs and reduced manual work, enhancing the accuracy of data processing and streamlining information retrieval when issues arise.
The implementation of Control-M has improved organizational functioning as it has eradicated the need for emails from clients about inaccurate data, boosting our confidence in operations.
What is most valuable?
The best features Control-M offers include a monitoring dashboard, which is the main useful tool for this, providing more information related to our jobs and offering detailed insights.
The job dependencies help me get information about my jobs, informing us if any jobs are dependent on each other and if they are completed on time or taking longer than expected, which prompts timely notifications if a job runs beyond its SLA.
These alerts in Control-M significantly reduce many questions and production timeouts, saving a lot of time because we can stop jobs if they are not running properly.
Regarding Control-M's AI capabilities, the governance and security are strong, as the jobs running are not vulnerable to hacking or bypassing, ensuring good governance and reliable, timely results.
Control-M gives business users vital visibility and control over their jobs, which is crucial for ensuring that tasks are completed on time.
Control-M significantly supports our DataOps and DevOps initiatives, especially with jobs using the CI/CD pipeline.
In terms of governance requirements, Control-M excels in audit trails and policy enforcement.
I assess Control-M's ability to create and automate data pipelines across on-premises and cloud technologies as very supportive.
Control-M's performance encompasses building, scheduling, managing, and monitoring workflows, effectively reducing a lot of manual effort.
Control-M integrates effectively with new or changing technologies within our DataOps and DevOps stack through the automation we have linked to our pipelines.
Control-M's functionalities that assist in meeting SOX compliance and audit trail generation are beneficial, especially the audit trail and dashboard features.
Control-M integrates seamlessly with our ITSM tools to facilitate incident responses, automatically creating tickets for any issues that arise.
What needs improvement?
While I do not find anything frustrating to use in Control-M, I expect more improvements on the AI side, particularly in AI/ML use cases.
I think the mechanism in Control-M needs to be enhanced, particularly in how prompts are given, to recognize user intent and provide appropriate maintenance suggestions.
I believe that Control-M's wide-use connectors need improvement to better connect with multiple CRM systems, as out-of-the-box connectors would be greatly beneficial.
For how long have I used the solution?
I have been using Control-M for the past two and a half years.
What do I think about the stability of the solution?
Control-M has been consistent for us, achieving about 90% accuracy, although there are instances where improvement is needed.
Control-M is stable.
What do I think about the scalability of the solution?
We are at the next stage of leveraging Control-M and plan to expand its usage for more clients.
Control-M is very scalable, enabling integration with various platforms without requiring underlying development.
How are customer service and support?
Our relationship with BMC is strategic; we stay in touch with them as they provide new features and community support.
Customer support for Control-M is great.
Which solution did I use previously and why did I switch?
Previously, we used custom solutions, so we did not transition from any specific scheduling solution.
We have not migrated from any other workload automation solution.
How was the initial setup?
The deployment duration of Control-M varies with each situation.
What about the implementation team?
Usually, one member can handle deployment and maintenance tasks.
What was our ROI?
Control-M has shown a return on investment by significantly reducing effort for the SRE, allowing us to monitor jobs with a single SRE, thus saving time and costs.
What other advice do I have?
I give Control-M a 10 out of 10 because it reduces a lot of manual effort, especially during automations where not all solutions yield consistent results and accuracy.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Job scheduling has become reliable and unified while complex data pipelines run smoothly
What is our primary use case?
My use cases for Control-M primarily involve scheduling, especially with applications like SAP, database plugins, and mostly OS.
How has it helped my organization?
Using Control-M has made it simpler to create, integrate, and automate data pipelines. We used Airflow to run data pipelines at one point, but it lacked many features that Control-M offered. Fortunately, Control-M had a plugin for Airflow, so we could use Airflow for data pipelines but schedule them via Control-M jobs, which gives us a native, feature-rich scheduling environment and integrates with data pipelines along with Airflow. BMC keeps up well with the technologies and developments out there.
What is most valuable?
What I appreciate most about Control-M is its stability. It is stable and usually does not go down. The consistency when the application restarts is flawless, and there is no usual data loss with Oracle as the backend. It is dependable based on my experience as an administrator using BMC across organizations.
Control-M is easy to integrate with other applications and technologies because it provides plugins for the latest solutions by default. If not, there is an Application Integrator built for that purpose, and there are community-driven integrations. From an alerting perspective, BMC had a very good affinity to its own tools, and it did not have ServiceNow integration, which is the most popular ITSM tool. We ended up using ancient SNMP calls to get the alerts out to custom tools. Other than that, integrations are good.
What needs improvement?
What I dislike about Control-M is that until very recently, and even now, it was not containerized or stateless. It is a stateful application, which is what I still dislike about it. It prefers its host, tries to maintain the connection, and lives on the host. It is not fully containerized or split into microservices, and it cannot be installed on anything with a database connection to start working. It prefers the host on which it was originally installed, and the statefulness of the application is what I do not like.
For how long have I used the solution?
I have been using Control-M overall for 19 years.
What do I think about the stability of the solution?
Control-M is stable. Only heavy upgrades require downtime of approximately 30 minutes for the Enterprise Manager and Control-M server applications every year or every six months. Other than that, it runs continuously.
What do I think about the scalability of the solution?
Control-M likes its nodes and is stateful. You cannot just add multiple nodes. It operates on active-passive high availability and does not scale horizontally much. Though capacity-wise it is good, at a given point in time, an instance runs on one VM, not ten. If that goes down, it can switch over to another, but that statefulness is what I do not like about scalability. It works, but it does not feel scalable. One node at a time is not scalable.
How are customer service and support?
Control-M's technical support is good. For priority cases, they are quick. P1 and P2 cases respond at the earliest, while P3 takes some time based on the time zone you are in and the time zone you are signed up for. They have always been helpful and go out of their way to get things done for me.
I would give Control-M's technical support a score of nine out of ten.
Which solution did I use previously and why did I switch?
I migrated from Tandem to Control-M as my organization used Tandem earlier. They brought in Control-M because they had mainframe and CS-7, and I believe that is how it started for the current organization. In the previous one, some brought it for SAP, some brought it because of the mainframes. We had cron before Control-M or the mainframe had JCLs being scheduled by the mainframe itself, and then we brought in Control-M in the 1990s.
How was the initial setup?
The initial deployment of Control-M, from what I did hands-on with migrations from the OS and new projects, was seamless. I did not bring Control-M into any organization as such. I went when it was already there. I enhanced, refactored, and migrated everything. In a development environment, it is seamless. You might still sometimes need to call support, but the documentation and a case here and there, along with a little bit of experience using it, works adequately. Open source tools like Rundeck are more straightforward and easy to install, set up, and manage for someone starting, but Control-M still needs expertise in this area to get it started and working since it has its own configs and the way it works.
What's my experience with pricing, setup cost, and licensing?
Control-M has gotten better at its pricing and with the latest offer for minimal jobs, it is acceptable given the value it provides. Mainframe is a bit expensive regarding the mainframe components, but I believe that is the way for any of the mainframe components. For distributed scheduling, non-mainframe, Unix, and Windows, it is reasonably priced.
Which other solutions did I evaluate?
I have used alternatives like Rundeck, and people use cron. I have also used Airflow, which provided some other functionality. Rundeck and Airflow are alternatives, and I regard Rundeck as an alternative.
I prefer Control-M more than the alternatives. It is a paid tool, but it is worth it.
What other advice do I have?
I started working in my current field overall with Control-M after my first year in IT, so that would be 18 years.
Control-M requires maintenance on my end for patches when there are vulnerabilities, which are usually released by Control-M. Other than that, everything can be automated.
Control-M takes care of all scheduling jobs, and when you have Control-M, you do not need to use any other tools. If one application has a single server running a couple of jobs, I would still suggest using cron as that would be more suitable. If complexity arises, you can better use Control-M. Because it is not free and not unlimited, you pay per job license. Whenever something simple can be triggered by cron and easily managed, I would personally use cron on a single server with a handful of jobs. If I need alerting, monitoring, a GUI, integrations, and audit and compliance, I would switch to Control-M even if I have to pay per job. Competing scheduling tools are not usually required as Control-M will suffice with data transfer, mainframes, distributed, and everything.
My relationship with BMC is balanced between transactional and transformative. It has been good, but it depends on the organization's priorities. There was a push towards going to open source schedulers, wherein we as an organization had to wind down the job licenses. The licensing calls are always tricky and handled by the vendor management team. They have their own logistics. I am a purely technical person making technical decisions, and I probably push something if it is good, but then it would go that way. BMC genuinely tries to help their customers. They have built us plugins, but at the same time, it is about the money.
Overall, I would give Control-M a rating of eight out of ten because it is not vertically scalable, and they did not fully containerize it or make it into microservices. For that reason, I would give it an eight. If not for those issues, I would give it a nine.
Workflow automation has improved data migrations and secures AI-driven integrations
What is our primary use case?
I primarily use Control-M for application and data workflow orchestration, workflow automation, and batch processing. My tech team uses it as well.
We are currently working on an API integration project where we have used Control-M for automating workflows and for batch processing of data moving from one system to another. We built that API integration using Control-M.
I think that covers what we have actually used Control-M for primarily. We are exploring other capabilities of Control-M, but that is what we have used so far.
How has it helped my organization?
Control-M has actually helped us with efficiency primarily. I'm sure in the long run, it will definitely help us in reducing some costs or controlling some costs. The improved efficiency due to automation is the best thing for us right now.
In the API integration project that I mentioned, we have saved roughly 20 percent of the time, or basically the process has improved by 20 percent in terms of efficiency. Previously, the bulk migration used to take roughly an hour, and now we can do it in 45 to 47 minutes. We have achieved a 20 percent saving so far, and we are trying to improve it.
What is most valuable?
Some of the features I can think of in data workflow are the native cloud and big data integration, including integration for Snowflake and Databricks, as well as built-in connections for AWS, Azure, and Google Cloud.
Regarding workload automation, features include DevOps integration, Jobs-as-Code, and hybrid and multi-cloud provisioning.
The native cloud and big data integration stand out as the most important thing because it gives me built-in connections for tools such as Snowflake and Databricks.
Two things that come to mind are both related to the execution guardrails for AI agents. One is the MFT server support that Control-M features, which is the native MFT support acting as a standardized connection layer. Another feature is the intent-based access control, where every action initiated by an AI agent is bound by strict role-based access control, or RBAC. These two are great features for securing both the governance and security aspects of the product.
What needs improvement?
For our use case, everything is there, at least for now.
For how long have I used the solution?
I have been using Control-M for three to four months.
What other advice do I have?
Understanding the product properly before using it would be better. You should first understand or map your requirements into the solutions or features provided by the product so that it will be much better for you as a user as well as for Control-M as a product.
Matching your requirements with the features provided by the product will be a win-win for both of you and will be a great experience for you as well as for the product builders to have a relationship between.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Workflow orchestration has unified job scheduling and now simplifies repetitive task automation
How has it helped my organization?
Control-M did consolidate job scheduler tools in my organization by pulling it all in one place.
What is most valuable?
What I like the most about Control-M is the task management, specifically the ability to integrate with multiple products and successfully complete repetitive tasks with ease.
It is easy to integrate Control-M with other technologies as my DataOps and DevOps processes change.
Control-M is excellent for building, scheduling, managing, and monitoring production workflows, but I would not use it for monitoring purposes.
What needs improvement?
The feature I would like to add is related to the licensing model, which I find challenging. The licensing model is based on the number of repetitive runs rather than the number of tasks. Sometimes it is difficult to understand how many runs we may have in a particular requirement.
For how long have I used the solution?
I have been using Control-M overall for the last year.
What do I think about the scalability of the solution?
Control-M is pretty scalable based on what we are currently using. However, what we intend to do is try to reduce its application and use it more effectively rather than scaling it.
How are customer service and support?
Regarding technical support, we have a support contract, and when we reach out to them, the response is always very fast. Whatever we need gets addressed quickly.
Which solution did I use previously and why did I switch?
Before Control-M, we were using Ansible.
How was the initial setup?
The initial deployment of Control-M was fairly easy. I don't exactly remember how long it took the first time, but I think it was set up entirely in two hours.
Which other solutions did I evaluate?
I have used alternatives, but nothing comes close to Control-M because the advantage that Control-M has is the ability to convert business applications data integration into other IT-related solutions that we use. In other cases, we would have to use multiple middleware. There are products evolving in the market that we are seeing that could be utilized here, but nothing is completely replacing Control-M fully. We really have to look into custom development to plug those gaps.
What other advice do I have?
I have been working in my current field as a professional for the last 18 years.
Control-M does require maintenance on my end. The overall server management involves ensuring that patches, vulnerability validations, and related tasks are properly handled because we have it in an on-premises deployment. Many deployments need this level of attention when it comes to patch management and vulnerabilities. Those are the types of maintenance and version controls required.
I would give Control-M an overall score of 8.5 out of 10.
Automation has improved nightly batch monitoring and now simplifies cross-team job management
What is our primary use case?
My main use case for Control-M comes from when I was an operations analyst, using it for scheduling, reporting, and others, and now as a supervisor ensuring that our people are up to date on all the procedures and practices for the product and ensuring that the product is working well for our needs.
Currently, my team uses Control-M for maintaining, processing, and scheduling our nightly batch cycles, and we are in the midst of a conversion from an MVS system to another using Control-M as its primary application for our scheduling and batch processing needs.
I manage the team that actually uses Control-M, so it is very intuitive, and our people seem to catch on to it rather quickly. They appreciate the product, they appreciate the functionality, and so far everything is working well.
How has it helped my organization?
Control-M has impacted our organization positively, and we appreciate it so much that we moved from using Tivoli on the mainframe. It is more intuitive with more robust features, and from my experience using Control-M at previous places, we were very pleased with it, so I am sure this newer version is robust, user-friendly, and intuitive.
I do see specific outcomes of reduced errors and faster processing since switching, although I don't observe the metrics of it as I am more of a supervisor of a group of users, but I am sure that it is happening because overall, it is very effective.
What is most valuable?
In my opinion, the best features that Control-M offers are ease of use and predictability. It is very easy to use and very intuitive, it does not take much to find errors in our processing, and the flexibility to restart and hold job streams is very good. Our team seems to pick it up very well and even if they had not used this product previously, they are appreciating it now.
The flexibility of Control-M has helped my team in practice, especially when we run our batch cycle throughout the night. Our operations analysts work only until about 8:00 p.m. or maybe 9:00 p.m., and during the evening, we have our operations staff doing the monitoring and ensuring that if there are errors with the processes, we can contact the programmers on call. Our staff does not need to be as knowledgeable as our operations analyst staff, making holding and restarting jobs easy for them.
What needs improvement?
Nothing comes to my attention regarding improvements needed for Control-M. There was a discussion of a stop button where one simple click would stop a whole process, which would be useful if we encounter an error, but I am not sure if that was suggested or implemented.
For how long have I used the solution?
I have been using Control-M since 2000.
What other advice do I have?
I would rate Control-M a 10 overall. From all the different users and groups involved with this project—including the programming staff—everyone appreciates the functionality, and I feel confident that I could step in there to restart or hold jobs if needed, indicating that anyone could handle the basics in case of absences or illnesses.
I chose a rating of 10 because it is something that everyone finds very intuitive. People enjoy using it for its simplicity, and the options we get in its use are very helpful and tailored to our needs, with different divisions and groups involved all being pleased with its process.
We have a security team that scrutinizes all our applications, and I have not been privy to any information from that department.
I do not believe my team has had issues with Control-M's accuracy and reliability of output, as I am aware that AI is a big focus, but unfortunately, I do not have any detailed information on its uses and capabilities.
My advice to others looking into using Control-M is to start using it and not be afraid to try it. I would feel that everyone would be very satisfied with the product since it is very user-friendly and a good fit for any large or small company regarding scheduling and processing monitoring needs.
Centralized job visibility has saved hours daily and now needs broader time and server features
What is our primary use case?
My main use case for Control-M is for orchestration purposes.
A recent task I managed with Control-M for orchestration was to get the failing details from the server; Control-M was helpful to get all the details at one time. Whenever a failing scenario occurs, I can see it on the web page, and this is very helpful without any difficult tasks.
I do not have anything else to add about my main use case or how I use Control-M.
How has it helped my organization?
Control-M has positively impacted my organization by reducing the time I used to spend logging into one server to get the information; this was taking a lot of time. From a business perspective, it was very tedious to explain things to business people, but now, this is all articulated in one file and shown in the browser itself. This has most benefited us with time, which is very valuable. These are very good features.
Out of an eight-hour job, I am saving nearly 3 to 3.5 hours using Control-M, which is almost 35% to 40% of my time.
What is most valuable?
In my opinion, the best features Control-M offers include a flow that is very useful; there is a web page displaying all the jobs running, the jobs that are critical, and the jobs that need to be reviewed. For any job that is failing, I can get to know. If there are any jobs that are still running or have pending tasks, this is helpful from a business perspective. Business people can just see the web browser and get to know what's happening. They don't need to go deep into the technologies and everything; they can get to know easily.
I would not like to add anything else about the features.
Regarding Control-M's AI capabilities, its governance and security are among the most secure features I can use; it is more trustable and bankable when I use its AI capabilities. For example, if I have very useful data like scientific data that needs to be very secure, I can go with Control-M, which is very good and will be more helpful for security as there is no data deviation.
In my experience, Control-M's AI capabilities have an accuracy and reliability rating of almost nine out of ten, with an accuracy of almost 99 to 99.5%; it is working great from my perspective.
What needs improvement?
Control-M could be improved by adding some more features, such as time management and business perspective features; many other features, such as server management, could also be added.
I do not wish to add more about the needed improvements.
For how long have I used the solution?
I have been using Control-M for only two or three months.
What other advice do I have?
I rate Control-M seven out of ten.
I chose a 7 out of 10 because it is just the latest technology, and I have only been working with it for two months. I need to explore more to know it better; I think it would be a nine out of ten with more daily use.
I advise others looking into using Control-M to go for it because this will help save time. It will help from a business perspective and be very helpful day-to-day. This will not only save your time, but it will also help you know which jobs are failing. There is no need for me to go and investigate every job that is failing; all these results will be in a business format, and I can see them in Python, which will be most helpful.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Centralized workflows have streamlined PO validation and now reduce manual effort and errors
What is our primary use case?
My main use case for Control-M is a PO validation use case where I receive an email with details. I capture the details from the email and process a PO, which is basically to approve or reject a PO.
Control-M helps in this PO validation process by orchestrating the different steps involved in this workflow. When a new purchase order is received, the process involves extracting information from a PDF, validating key details such as a PO number, vendor information, payment details, payment terms, and approval details and signatures. Control-M can coordinate these activities by managing job dependencies, ensuring that each stage starts only after the previous one has completed successfully. For instance, the validation stage should begin only after document processing and data extraction are complete. If a job fails or encounters an issue, the workflow can be monitored and alerts can be sent to the support team to investigate further.
Another important aspect of my use case is visibility and operational control. In the PO validation workflow, multiple documents are processed simultaneously, and delays or failures in one stage can impact the downstream activities. Control-M's centralized monitoring and dependency management capabilities can help me identify bottlenecks. It helps me track job execution and ensures that the overall workflow runs in a structured manner.
How has it helped my organization?
Control-M has positively impacted my organization by improving operational efficiency. Particularly in environments where multiple processes and systems work together, one of the biggest advantages is reducing the need for manual coordination and monitoring of individual jobs. Coordinating processes like document processing, data extraction, and validation through a structured workflow reduces errors, delays, and improves process consistency. Centralized monitoring makes it easier to help me take corrective action without manual checks at each stage. I see value in improved visibility, better dependency management, and more controlled execution of recurring processes. While I haven't personally measured specific productivity gains, these capabilities contribute to better operational efficiency and scalability in an enterprise automation environment.
Regarding positive outcomes, time saved is definitely one of the metrics, and ROI is another. With multiple stages involved, this happens sequentially, leaving no space for error. Without centralized orchestration, teams monitor individual jobs and manually coordinate dependencies. Control-M organizes these activities. If there is a failure, it gives clear visibility on the failure, and the potential improvement lies in error eradication. Another potential improvement is reduced manual monitoring; I don't have to look at the nitty-gritty of each process. I can trust the process for better consistency.
What is most valuable?
The best features Control-M offers, which I found most valuable, are centralized workflow monitoring, job scheduling, dependency management, and automated failure notifications. The ability to define dependencies between different jobs is particularly useful because it ensures that activities supposed to be processed later execute only when their prerequisites are completed. I also see strong value in its integration capabilities, especially when coordinating workflows across databases, enterprise applications, file systems, and cloud environments. Centralized visibility makes it easier to monitor execution.
One thing worth highlighting about the features is Control-M's integration capabilities. In an enterprise environment, workflows rarely operate within a single application; multiple applications are involved. For instance, they involve databases, file transfers, CRM systems, ERP systems, cloud platforms, and other automation tools. Control-M's ability to orchestrate workflows across these applications or environments is a significant advantage. I also find centralized monitoring very valuable. Having visibility into job statuses, execution histories, dependencies, and failures from a single interface makes troubleshooting easier, allowing teams to identify issues before they significantly impact any business process. For my scenario, that means better coordination between document processing, validation, and filling up values in different applications and all the downstream updates. These capabilities can help improve operational visibility for leaders to see how the team is performing and reduce manual intervention.
Regarding Control-M's AI capabilities, I believe governance and security are important considerations, especially when introducing AI capabilities in enterprise workflows, and I think Control-M is doing a great job at that. In the PO validation scenario, documents may contain sensitive vendor information, PII, payment details, and approval records. Therefore, access control, data protection, audit trails, and traceability are essential. I expect AI capabilities to operate within established enterprise security policies with appropriate role-based access, and human oversight should be maintained for critical activities, particularly financial approvals and exception handling. From an enterprise perspective, I see governance, compliance, and secure integration as important factors in building trust in any AI-driven automations.
Regarding Control-M's AI capabilities, accuracy and reliability of output are particularly important when introducing AI. I believe AI capabilities should be supported by proper validation mechanisms and exception handling, which Control-M is greatly looking into. I would say it provides significant value to enterprise automation and remains committed to this idea.
What needs improvement?
One area where I feel Control-M could improve is in overall user experience and ease of configuration. For new users of workload automation, making workflow creation, dependency configuration, and troubleshooting more intuitive would help them adapt to Control-M faster and reduce the learning curve. I would also like to see more intelligent monitoring capabilities, such as AI-assisted failure analysis or root cause suggestions, or recommendations for optimizing job execution. This improvement would help companies adapt faster and allow teams to move beyond simply identifying failed jobs. Another area worth enhancing is the integration experience with modern AI and RPA platforms for easier orchestration involving intelligent document processing APIs and automation bots. Overall, Control-M has strong orchestration capabilities, but improving usability, intelligent monitoring, and simplified integrations would make it more accessible and powerful for automation teams.
Regarding needed improvements, the learning and onboarding experience for someone getting started with Control-M could use more practical or end-to-end tutorials. Industry-specific implementation examples would be greatly helpful. Clear documentation with real-world scenarios, troubleshooting guides, and best practices for integrations will make development time faster. I would also value more hands-on labs or guided exercises covering complex workflow orchestration, dependency management, and API integrations, which would help users move from understanding individual features to implementing complete enterprise workflows.
For how long have I used the solution?
I have been using Control-M for about a couple of months.
What do I think about the stability of the solution?
Control-M is very stable.
What do I think about the scalability of the solution?
For what I have tested until now, Control-M's scalability is great. When UAT started, it began with two employees, and about 25 to 30 processes ran concurrently, which it handled very well. For scalability, on a scale of 1 to 10, I would definitely rate it a 9.
How are customer service and support?
Customer support has always been great. Control-M has a thriving community, and I have received extensive help for any queries. I value timely responses and clear troubleshooting guides; while I would prefer better documented troubleshooting guides, the support has been very great, which is crucial for new users and administrators. I would rate customer support a 9 out of 10.
Which solution did I use previously and why did I switch?
I have previously worked with various competitors, including UIPath, Automation Anywhere, and Microsoft Power Platform. However, these primarily address RPA and business process automation requirements, while Control-M focuses on enterprise workload scheduling and orchestration. My exposure does not describe a direct migration from another platform to Control-M; rather, I see Control-M serving a different purpose, particularly when an organization needs centralized scheduling, dependency management, and monitoring of complex workflows across multiple enterprise systems.
What was our ROI?
I have seen a return on investment, which can be measured through monetary savings showing fewer employees needed. I am looking at saving more than $100,000, which reduces headcount by about 12 to 13. These metrics I have calculated indicate the potential ROI stemming from reduced manual operational effort.
What's my experience with pricing, setup cost, and licensing?
My understanding is that Control-M follows an enterprise licensing model, and overall cost depends on the deployment scale. In an on-premises deployment, organizations also need to consider infrastructure provisioning, installation, configuration, maintenance, and support costs. However, for larger organizations managing complex workloads, the value should be evaluated against operational efficiency, centralized monitoring, and reduced manual effort it provides.
Which other solutions did I evaluate?
Before choosing Control-M, I evaluated options such as UIPath, Automation Anywhere, and Microsoft Power Automate.
What other advice do I have?
On a scale of 1 to 10, I would rate Control-M an 8. This is based on the brief hands-on exposure I had and my assessment of its enterprise workload orchestration capabilities.
I chose 8 because Control-M offers strong enterprise workflow automation, particularly in job scheduling, workflow orchestration, dependency management, and centralized monitoring. What keeps it from being a 9 or 10 for me is the opportunity for improvement in user experience and the learning curve for new users. I would also like to see more intelligent monitoring, such as AI-assisted troubleshooting.
Control-M is mostly deployed on-premises in my organization. Although I have had brief hands-on exposure to Control-M through practical sessions, I understand it supports different deployment modes based on an organization's infrastructure. Here, it is predominantly on-premises.
I recommend Control-M to organizations looking for a centralized enterprise workload automation and orchestration platform. Before adopting it, it is essential to clearly identify processes needing orchestration, evaluate integration requirements, and invest time in learning job scheduling, dependency management, monitoring, and failure handling. For organizations already using RPA or AI-based automations, I suggest exploring how Control-M can complement those solutions rather than compete or replace them. For example, in the PO validation process, AI can handle document extraction and validation while Control-M coordinates the overall workflows. My advice would be to start with a well-defined use case, run a practical proof of concept, and evaluate scalability, operational benefits, and ease of administration before committing to a wider enterprise rollout.
Daily data loads have become reliable and support teams manage jobs without coding
What is our primary use case?
My main use case for Control-M is running Oracle package procedures on a daily basis to load data from an external system to Oracle staging tables. We need to schedule the Oracle packages on specific dates and times, and we configured Oracle packages in Control-M so that on a specified date and time, Control-M picks and runs the Oracle package jobs.
During my initial learning phase, I faced difficulties in understanding Control-M's capabilities, but when I started exploring, things became easier. Debugging the logs proved to be helpful.
My organization uses Control-M to address compliance requirements such as SOX and audit trails, which are involved in regulatory reports.
How has it helped my organization?
Control-M positively impacts my organization by improving performance and offering no-code features since no coding is involved to configure any monitoring for job scheduling.
We have developed more than 20 packages, and for running and scheduling these packages using Control-M, it is easy for the L2 support team to handle without involving developer support.
What is most valuable?
The best features Control-M offers are for debugging logs and monitoring scheduler jobs.
Whenever any issues occur, I can find the particular job log in the monitoring interface. I can see how many failed jobs and successful jobs there are, and I can monitor based on that information.
Regarding Control-M's governance and security capabilities, I find them very important for protecting an organization's data. Control-M has all the capabilities to configure secured configurations.
Control-M's AI capabilities are accurate and reliable, definitely meeting my expectations.
What needs improvement?
Control-M is overall good, and currently, there is no specific improvement needed.
For how long have I used the solution?
I have used Control-M in previous companies for scheduling Oracle packages in a UNIX environment for loading delta and incremental data to Oracle staging tables.
What do I think about the stability of the solution?
Control-M is stable in my experience.
What do I think about the scalability of the solution?
Control-M's scalability is good.
How are customer service and support?
The customer support for Control-M is very responsive. If any issues arise and I create a support ticket, they resolve the issues very quickly.
I rate the customer support as 10 out of 10.
Which solution did I use previously and why did I switch?
We exclusively used Control-M and did not use any other tool previously.
What was our ROI?
I have seen a return on investment from using Control-M as it definitely saves considerable time.
What other advice do I have?
I would rate Control-M as 10 out of 10.
I choose 10 out of 10 for Control-M because it is easy to use and easy to explain to others, with no coding involved.
My advice for others looking into using Control-M is that if you have any scheduling jobs to run and monitor, you should definitely prefer Control-M.
Workflow automation has transformed batch windows and now supports reliable AI-driven pipelines
What is our primary use case?
My main use case for Control-M when I worked with it was as a workflow architecture and workload automation platform where I used it to design, schedule, and monitor jobs. I managed complex IT processes, bringing business processes across multiple cloud environments—not only cloud solutions but also on-premises, multi-cloud solutions such as public cloud, private cloud, or hybrid environments. I used it for batch job scheduling and automation when I was familiar with it.
To manage the integration and sequencing of data processing across diverse data platforms and cloud environments, using Control-M depends on whether you can operate out of the box or with plugins and APIs. Most of the time, these API connections or custom integrations are utilized, which involves plugins or native cloud tools, and this also applies to application integrations or CI/CD automation.
My organization is planning to use Control-M to support AI or ML workloads. Control-M's AI integration, including generative artificial intelligence, is beneficial for building and running managing data pipelines and application workloads using workflow automations. This AI workflow creation acts as a natural language tool that translates simple text into comprehensive job workflows. We also have execution insights, RCA integration, and various troubleshooting aids with the RCA agent.
Control-M handles compliance requirements such as SOX, audit trails, or regulatory reporting effectively. Audit automation features in Control-M include an audit mechanism configurable with this configuration manager. We can set the system to prompt users for mandatory text justification when they perform sensitive actions or modify automation workflows, achieving SOX requirements by centralizing jobs and automating batch scheduling with workflows that satisfy IT general controls around change management, job scheduling integrity, and segregation of duties in SOX.
How has it helped my organization?
Control-M has positively impacted my organization. I worked on this, and the use cases for Control-M are very high. The automations, such as job run scheduling, clearly dominate, and no other solution can beat it. That's how Control-M finds its place.
Specific measurable outcomes in Control-M relate to project management. The control phase gives distinct measurable parameters in project management and workload automations. By implementing Control-M, a workload automation software, I am able to track and validate job behavior effectively. No other solution can beat it in making batch window performance measurable.
What is most valuable?
The best features that Control-M offers include agents for job scheduling, cloud and data pipelines through integrations, self-service management, and security. We also have many other features, such as multi-cloud support and active-active capabilities where normally we have active-passive configurations.
The active-active feature impacts my work positively; it allows both servers to manage workloads when going to cloud or on-prem. In contrast to active-passive, where one server manages the total load while the other stands by, the active-active setup is useful. I attended an event that highlighted active-active as a valuable feature.
Regarding Control-M's AI capabilities, I believe its accuracy and reliability of output are exceptional. The accuracy is assured due to its integration and other factors; the time processing is also good. The AI agents, such as fabric agents, demonstrate solid performance.
What needs improvement?
I found working with those different environments presented challenges; I faced many issues while modifying the jobs in Control-M. Frequently, several phases presented operational issues such as synchronization issues, and sometimes there were significant time challenges, which I think have decreased.
Regarding enhancements, when I attended an event, I noticed many areas for Control-M improvement, including performance tuning and job design best practices, such as resource management utilizing check config utility. While there are existing options such as true enterprise manager parameters and optimization tools, I believe we can manage these aspects better.
For how long have I used the solution?
I am not much familiar with Control-M, but I have worked with Control-M a long time ago, and I do have some knowledge on Control-M.
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 performs well when it comes to scalability.
How are customer service and support?
Regarding customer support, I can say it is very good. Although I do not remember exact details since it has been a while, insights from the events I attended regarding Control-M were excellent.
Which solution did I use previously and why did I switch?
We did not previously use another solution; we have used Control-M itself.
What was our ROI?
I have seen a return on investment as evidenced by money saved and time saved.
What's my experience with pricing, setup cost, and licensing?
Concerning pricing, I believe the pricing is reasonable; when compared with others, Control-M's audit trails feature is included in the standard pricing plan. As I remember, it costs about $2,400 per month, and this is useful.
Which other solutions did I evaluate?
Before choosing Control-M, we did not evaluate other options. We compared Control-M with other platforms and concluded it was the best choice at that time when I worked there earlier.
What other advice do I have?
On a scale of one to ten, I would rate Control-M around eight.
I chose that number because when I compare the integration of Control-M, which includes connections with AWS, Azure, and SAP, the integration looks good, with no delays or issues. The processes for job running and scheduling are perfect.
My advice to others looking into using Control-M is that the key feature is its fabric agents. I recommend investing in training and doing due diligence on business prefixes, job names, and organizing folders by domain. There are many aspects such as runtimes, retry strategies, and leveraging API automation to consider. Based on this, I suggest these as key advice for others.