Control-M Managed File Transfer

My use case is workload automation. Control-M adapts to my environment by using data pipelines that are orchestrated through Control-M, providing all the data needed for machine learning initiatives.

Regarding specific machine learning operations workflows, I have orchestrated them by integrating Control-M with tools such as MLflow. I have primarily focused on integrations and DataOps. Beyond MLflow, I have also integrated Snowflake and Vortex. Snowflake executes SQL commands and handles data format and data transformations. Once data transformations are completed using Snowflake, Kafka, and Vortex, multiple integrations are performed through API with agents, and Vortex is also utilized.

For ITSM and change management tools, I have integrated Control-M with these systems.

For change management workflows, I create scenarios such as user creation in Active Directory, where the workflow executes and calls API scripts or automation for Active Directory to create the users. These workflows have been created for release management. Once a change is approved internally within the ITSM system with all necessary approvals from the CAB, it is critical to ensure the release happens according to the change guidelines. This requires a sophisticated and reliable system with robustness. Control-M allows me to perform the change and ensure that the data is returned to the ITSM.

The benefits I have seen from implementing Control-M include increased productivity by ensuring jobs are completed based on prerequisites. Control-M reduces my complete total cost of ownership through increased visibility, which reduces multiple tool sprawl and results in cost reduction. I have achieved increased productivity, better SLA management, and ensured that SLA records, SLA points, and SLA metrics meet KPIs. Control-M provides automated failure recovery so that remediation is also taken care of.

Moving into DataOps operations, Control-M ensures that my AI infrastructure and AI initiatives are all supported. The advantages include reduction in cost, increase in productivity, and ensuring compliance.

The best features I find in Control-M are its robustness and job visibility of complex job dependencies and status. When I have a mesh of jobs, Control-M can clearly identify and update and also run all these multiple jobs while providing clear output. Control-M offers robustness, visibility, and scalability.

Control-M helps with policies, approval, and risk gating capabilities. It is very robust in handling workflow approvals within my organization with multiple levels of approvals, even with stable rollbacks and clear status updates. Notifications are proper and informative. Control-M is the right fit for my needs.

Regarding visibility, Control-M provides full clear visibility of all processes. It has centralized visibility so that multiple platforms, multiple orchestrators, and different functionalities across departments can all be visible from a single pane of glass.

Control-M sits on top of many orchestration tools that are available in the market. One area for improvement is that I still have dependency on orchestration tools. If Control-M develops or acquires an orchestration tool and builds that capability within Control-M as a complete orchestrator, similar to Ansible or Terraform, my dependency on external orchestrators would reduce and I would use Control-M more extensively as a complete end-to-end tool. Building a full-fledged orchestrator inside Control-M would be ideal and would be a wonderful value addition.

Aside from an orchestrator, there might be value in performing some functions without headless architecture. An orchestrator capability should provide that ability. Control-M is bringing AI and LLM integrations, which is positive. The orchestrator capability is the main area for improvement at this time.

I have been using Control-M for more than five years. Throughout my five years of association with Control-M, I have found it to be successful when dealing with complex workload automation tasks.

Control-M is very stable. I rate its stability as a nine out of ten.

Control-M handles very large numbers of jobs, going beyond 10,000 jobs. My organization has many BMC Control-M specialists, and I have implemented Control-M organization-wide. My clients are large organizations, very large. My organization has 150,000 people. Control-M is very much scalable. I rate its scalability as a nine out of ten.

I rate the technical support at nine out of ten.

The return on investment I see is at least something like 30% easily.

Regarding pricing, Control-M is expensive compared to the competition, but it is worth it. Even though Control-M is expensive, pricing could be brought down slightly. One more improvement I was looking at from a pricing perspective is that SaaS pricing is too expensive. On-premises pricing has no limitation on the jobs and licenses, but when moving to SaaS, there is a big impact.

Control-M is fantastic because of its support, which is number one. The ability to scale up and the best implemented solution across the globe make Control-M stand out. There are competitors such as ActiveBatch and other companies, but Control-M is still the number one in workload automation.

My business role is as a partner and system integrator. I have Control-M deployed in every mode, both cloud and on-premises as well as in private cloud. For cloud services, I use prominently Azure and AWS.

My relationship with BMC is strategic and transformational. I would describe Control-M as positioned for performance in building, scheduling, and managing workflows. My final rating for the solution overall is around nine out of ten.

My use case is workflow automation, and I work as an administrator for Control-M. I previously worked on mainframe environments, but now I work on distributed systems.

Control-M does not currently support AI or ML workloads at version 9.0.21, but AI support will be available in version 27, which I plan to install next year.

Regarding policies, approval, and risk-gating capabilities for automated workflows, I use an in-house product to automate the workflow between several environments, so I do not use a solution from BMC for this purpose.

I do not use Control-M with SAP solutions such as SAP S/4HANA or BW.

One of the challenges I was looking to overcome with Control-M involved using PeopleSoft. I use BMC with an interface that was written in-house to start jobs on PeopleSoft.

Control-M integrates with my ITSM and change management tools through REST APIs that call a connection with HEAT to create tickets automatically. This integration is an in-house solution using API programs.

I do not use Control-M to support DevOps or DataOps initiatives.

Control-M saves approximately 20% of my time, though it is difficult to quantify precisely.

The best features of Control-M are the graphical interface, which I appreciate the most about the product.

Control-M is one of the most popular and most complete products available for workload automation.

Regarding integration capabilities with external products and my security or technical stack, the ease of integration is reasonably good. I have integrated Azure jobs, DB2, and SQL, and I am looking for Micro Focus integration, which is not provided by either BMC or Micro Focus. These are the integrations I currently use, but I expect additional integrations in the future.

Control-M performs exceptionally well in building, scheduling, managing, and monitoring workflows. There are extensive possibilities and numerous REST APIs available to manage the workflow, providing a very broad spectrum for monitoring everything in the workload.

Support from BMC has room for improvement, especially regarding the Micro Focus environment. I have encountered several issues in the past where I needed to contact the lab environment to obtain correct solutions for installations, particularly with the Windows fault-tolerant mechanism.

I have been working with Control-M for more than 10 years.

Overall, Control-M stability is good, though I sometimes experience problems related to Windows issues with memory or similar issues that can cause problems with Control-M.

I rate the overall stability as a nine out of ten.

Approximately 500 users use Control-M in my organization.

I rate the scalability as a nine out of ten.

I rate support from BMC as an eight out of ten.

Prior to using Control-M, I used Tivoli OPC on mainframe. When my organization merged with another firm, I had to migrate to Control-M on mainframe.

I think Control-M is expensive, but I do not have complete information about the full pricing details.

I do not have recent experience with other schedulers on distributed systems, but on mainframe, I had experience with CS7.

Control-M is currently deployed on-premises, and I do not have plans to move to the cloud in the near future.

Control-M does require maintenance. The maintenance is not always easy or complex, but as I mentioned before, I work in a Windows environment, and that environment is not always correctly documented by BMC. For other environments such as Linux and Unix, there seems to be no problem, but I have encountered issues from time to time on Windows.

I recommend Control-M as a good solution, with the exception that it is not the best solution to deploy on Windows. Organizations should conduct a proof of concept before implementation.

My main use case for Control-M is to automate and schedule workflows and manage batch jobs, monitor dependencies, and ensure critical business processes run smoothly without any manual intervention.

I mainly use Control-M to automate daily data processing, financial reporting, database updates, and schedule application jobs because it helps ensure data is available on time and reduces manual work across business operations.

We are using Control-M for financial services.

We use Control-M for approval mainly for sensitive financial data processing, production deployment, and critical business workflows. It helps ensure proper authorization, follow company policies, and reduce risk before important jobs run automatically. This also improves accountability and compliance.

We mainly use Control-M to schedule and control workflows, including data preparation, model training, and deployment tasks. Integration with tools such as Azure ML and MLflow can help manage dependencies, automate execution, and improve overall workflow reliability.

Control-M supports our DataOps and DevOps initiative by automating data pipelines, managing dependencies, and scheduling application deployment. It improves coordination between teams, reduces manual tasks, and helps ensure reliable and timely delivery of our business processes.

I use Control-M to orchestrate workloads across on-premises environments. It helps manage job dependencies, centralize monitoring, and maintain consistent execution across different platforms. This improves flexibility and makes operations easier to manage.

We use Control-M to manage both SAP and non-SAP workflows. It helps schedule and monitor SAP ECC and BW jobs alongside database operations, data transfer, and application tasks. Centralized monitoring makes it easier to manage dependencies and ensure smooth execution across different systems.

We use Control-M to manage data processing tasks through job dependencies, scheduling, and automated workflows. It helps coordinate tasks across databases, SAP systems, and cloud platforms. We monitor job statuses through a centralized dashboard and use alerts to quickly handle failures. This ensures smooth data flow and reduces manual effort.

Our DataOps and DevOps stack includes Control-M, SQL databases, SAP systems, and a cloud platform. We use these technologies for data integration, workflow automation, application deployment, and job monitoring. Control-M helps connect different tools and manage dependencies, ensuring smooth execution across environments.

We are planning to use the Control-M Python client or API in the coming days.

Control-M has reduced troubleshooting time by providing real-time job monitoring and instant failure alerts. My IT team can quickly identify failed jobs, check error details, and resolve issues before they impact daily business operations.

Control-M has improved our overall operational efficiency by reducing manual work, minimizing job failures, and ensuring timely data processing.

Control-M has helped us save around 25 to 30 percent of manual monitoring time. We have also seen fewer job failures, faster issue resolution, and better SLA performance through automated scheduling alerts.

Control-M helps free up IT personnel by automating repetitive scheduling, monitoring, and troubleshooting tasks. This allows my team to focus more on important activities such as system improvement, security, and business-critical operations. This is very important for our organization because it improves productivity and reduces operational workload.

Control-M has helped us achieve faster workflow delivery, improved SLA performance, and fewer job failures. Automation has reduced manual effort and improved error handling. Better monitoring and audit trails have also strengthened operational efficiency and compliance across our organization.

Control-M has improved our daily operations by automating job scheduling and reducing manual monitoring. We have reduced manual effort by around 30 percent and improved job completion time by 20 percent and reduced delay through faster failure alerts. It also improved SLA management and overall team productivity.

Control-M is helpful because it simplifies workflow management, reduces operational complexity, and brings all workflows under one platform.

Before implementing Control-M, audit preparation involved manually collecting job execution reports and approval records from different systems that took too much time. After implementation, everything is centralized. Automated logs and audit trails have made it easier to retrieve information, verify activity, and prepare compliance reports very quickly.

Control-M offers many features such as easy job scheduling, workflow automation, real-time monitoring, dependency management, and failure alerts. I especially like its centralized dashboard because it helps me track jobs, identify issues quickly, and reduce manual efforts.

Control-M's AI capability provides fairly accurate and reliable output for monitoring and identifying workflow issues. These capabilities help analyze job patterns and highlight potential problems. However, output should still be reviewed by a team, especially for security and governance-related decisions.

Control-M integrates well with AI and ML tools by supporting automated workflows, data pipelines, and scheduled model execution. It helps manage data processing, monitor ML jobs, and ensure timely execution. Better integration with AI platform predictive monitoring would make it even more useful for us.

The approval process in Control-M is fairly easy once everything is configured. It helps organizations maintain better control over critical jobs, avoid unauthorized changes, reduce operational risk, and improve compliance. It also gives the team more confidence in automated processes.

Control-M provides good visibility through its dashboard and allows business users to track job statuses, monitor progress, and identify failures without depending completely on our IT teams. This is important for our organization because it improves transparency, saves time, and helps the team make decisions more quickly.

Control-M requires clear audit trails, proper tracking of data and model changes, and role-based access for production AI workloads. Control-M helps monitor workflow execution, maintain accountability, and enforce approval processes. These controls are important for security, transparency, and compliance.

Control-M helps us manage workflows across on-premises infrastructure. We use it to schedule jobs, manage dependencies, transfer data, and monitor execution across different environments. This improves visibility, reduces manual efforts, and ensures smooth coordination between all environments.

Control-M performs very well in building, scheduling, managing, and monitoring workflows. Its interface makes it easier to create jobs, manage dependencies, automate repeated tasks, and track execution in real-time. Failure alerts and centralized monitoring help my team resolve issues quickly. I believe it improves productivity, reduces manual effort, and ensures reliable workflow execution.

Control-M helps us meet SOX and audit requirements through detailed job execution logs, audit trails, role-based access, and approval workflows. These features help track who executed or modified jobs, maintaining accountability and providing useful records for compliance checks and regulatory reporting.

Control-M integrates with ITSM tools such as ServiceNow to improve incident management and approval processes. It helps automatically raise alerts for failed jobs, create incidents, and track resolution statuses. This improves communication between teams, speeds up troubleshooting, and ensures better control over production changes.

Workflow orchestration is very important for our DataOps and DevOps initiative. Control-M helps us automate production workflows, manage dependencies, and monitor jobs across different environments. It reduces manual efforts, improves delivery speed, minimizes errors, and ensures critical business processes run reliably.

Centralized management of workflows across on-premises servers is very important for our organization. It improves visibility, simplifies scheduling, reduces manual efforts, and ensures reliable execution across different environments. It also gives us flexibility to scale as business needs grow.

Control-M has made it simpler to create, integrate, and automate data pipelines across on-premises. Its centralized interface helps manage job dependency, schedule workflows, and monitor execution. Although initial configuration takes some time and effort, it reduces manual work and makes overall pipeline management easier.

Control-M can be improved by making the interface more user-friendly, simplifying workflow configuration, and providing better error messages because sometimes we face issues. Faster troubleshooting, smarter failure prediction, easier cloud integration, and more detailed reporting would also make our daily job management even smoother.

Control-M can improve AI capabilities for governance and security by adding intelligent threat detection, automated compliance checks, and unusual activity monitoring and role-based access recommendation. AI-based alerts and audit reports would help identify risk early and maintain better control over sensitive workflows.

One challenge is managing dependencies between Kubernetes jobs and cloud-native applications and traditional batch processes. Monitoring and troubleshooting across different environments can also be complex. However, Control-M provides centralized scheduling, better visibility, and automated workflow that is helping my team improve coordination, reduce manual work, and manage hybrid environments more efficiently.

I have been using Control-M for the past two years.

Control-M has been stable.

In our organization, approximately 50 to 60 percent of users interact with Control-M. Main role cases are Technical Architect that maintains all the infrastructure, as well as the IT team that continuously checks the transactions and how they are controlling our system without any impact on business operations.

Control-M is currently used across several important areas of our organization, mainly for job scheduling, data processing, workflow automation, and monitoring. We plan to increase its usage for cloud-based automated workflows, AI and ML operations, and DevOps processes to improve automation and efficiency.

Around 25 to 30 users across our organization are using Control-M, including IT operation engineers, DevOps engineers, data engineers, database administrators, and system administrators.

I would rate Control-M eight out of ten for scalability. The solution is very good.

My relationship with BMC is more transformative than transactional. BMC provides ongoing support and solutions that help us improve automation, modernize workflow, and manage complex operations. We see good value in long-term innovation, product improvement, and the ability to support our changing business needs.

BMC is very supportive.

I would rate customer service an eight.

We transitioned to Control-M from a traditional job scheduling approach to get better automation and centralized workflow management. The transition improved visibility, simplified job scheduling, and reduced manual intervention. It also made managing complex workflows across different environments easier.

I did not consider alternate solutions before Control-M.

The initial deployment takes around three to four months, including installation, configuration, workflow migration, integration testing, and user training.

We required a team that handles all IT operations, DevOps engineers, and data engineers. They handle all the operations so that we can deploy these things on our on-premises as soon as possible.

BMC helped us understand the migration process by providing guidance on planning, workload assessment, and migration strategy. Their support helped identify dependencies, prioritize critical jobs, reduce migration risk, and ensure a smoother transition to Control-M with minimum disruption to daily operations.

We have seen a good return on investment of approximately 50 to 60 percent reduction in overall cost.

We have also seen a good ROI of around 25 percent because it improved job completion efficiency and reduced operational delays. Faster issue resolution and fewer job failures have also helped us save time and improve overall team productivity.

Pricing is reasonable, considering the automation and operational benefits that Control-M provides. Initial setup and licensing costs can be slightly high, especially for smaller teams. However, the centralized management, reduced manual efforts, and improved productivity make it a worthwhile investment in the long run.

I would like to rate Control-M an eight because it offers reliable automation, easy job monitoring, and good workflow management. It saves my time and reduces manual work efforts. However, there is still room for improvement in user interface, configuration simplicity, and troubleshooting.

Control-M is very helpful for handling all the workload management because we can handle everything from a centralized dashboard. It reduces manual intervention.

I would recommend Control-M for anyone considering this solution for their operations.

My use cases for Control-M primarily involve scheduling, especially with applications like SAP, database plugins, and mostly OS.

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 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 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.

I have been using Control-M overall for 19 years.

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.

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.

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.

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.

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.

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.

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.

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.

Control-M did consolidate job scheduler tools in my organization by pulling it all in one place.

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.

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.

I have been using Control-M overall for the last year.

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.

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.

Before Control-M, we were using Ansible.

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.

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.

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.

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.

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.

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.

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.

I have been using Control-M since 2000.

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.

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.

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.

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.

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.

I have been using Control-M for about a couple of months.

Control-M is very stable.

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.

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.

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.

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.

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.

Before choosing Control-M, I evaluated options such as UIPath, Automation Anywhere, and Microsoft Power Automate.

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.