Control-M Managed File Transfer

Our company has been using Control-M for more than 10 years, and the majority of our usage is focused on batch scheduling purposes.

We are exploring the use of Control-M to support AI or ML workloads, but I cannot say that we will use it. We have our AI bot, such as a chatbot, for governance, so we must ensure that it actually meets all our governance requirements in terms of AI before we explore and deploy it.

Our company uses Control-M to address compliance requirements such as SOX, audit trails, and regulatory reporting. We have our audit team, both internal and external. The majority of what has been included in our GTech and ITech must be monitored, and Control-M provides us with that traceability from wherever they run the job, when it failed, and what action was taken to be compliant with all those critical and sensitive job information.

We mainly only use job scheduling features of Control-M, which is good because you can accomplish a lot of recurring complexity in terms of precedent jobs, job alerting, failures, and error message handling.

Control-M features allow us to capture a lot of job failures and determine what action needs to be taken by my support team.

I am not in R&D, but whatever they are doing with Control-M is good. If they can improve their cockpit and make it more intuitive in terms of how things are configured and improve error handling messages, that would be beneficial. I am certain that their R&D is going to explore more in terms of how they improve their product development.

I have been using Control-M for 10 years since I joined the company, as Control-M was already in place when I arrived, so my usage extends beyond 10 years.

Control-M has been very stable for the past 10 years, and that stability is the primary reason we have continued using it.

Control-M is very scalable as a SaaS offering. We can add whatever jobs we want, but we need to be careful with the licensing.

We have limited interaction with BMC support because of Control-M's stability, but whenever we have any issue, BMC support is quite proactive and responds in a timely manner.

Prior to adopting Control-M, we used SAP internal job scheduling as a starting point, but due to our complexity and further business requirements, we explored certain vendors and came across BMC's Control-M, which is one of the best applications to handle SAP and integrate well with SAP. That is the primary reason why we moved from internal SAP scheduling to BMC for more centralized control. It is a one-stop center where you can view, organize, create, set alerts, and manage a lot of complexity within the application in the cockpit itself.

We were on-premises before 10 years ago, and recently, we migrated over to the SaaS model of Control-M.

With the recent migration from on-premises to BMC SaaS, the deployment and migration from on-premises to our SaaS cloud has been quite smooth.

We are working with VMA as their partners, and they are very knowledgeable and helpful, so the process has been quite smooth.

I can share a few benefits realized in terms of ROI and time savings with Control-M. For example, in our month-end reporting, batch jobs that we require for our BI reporting need to go through multiple layers, and each of those needs to be successful before we get to our report. Other jobs regarding our pricing are very crucial, and we run a lot of pricing updates to enable our pricing to be competitive.

With the new SaaS model, we are actually comparing costs, and it makes sense to move to SaaS whereby BMC and Control-M are managing their infrastructure for us rather than us maintaining our service on-premises.

I am very supportive of using AI features in Control-M because it is definitely the way forward in the current environment to reduce manual interventions using all those AI capabilities to assist us for more efficiency.

I rate Control-M as a nine out of ten, and I will not rate it a ten because there is always room for improvement, but so far their product is good and their support is good.

The main use case for Control-M in my organization is automating productive batch processes. We have more than 18,000 tasks that used to be executed manually, and now they are handled through Control-M.

Approximately 15 users use Control-M in my organization, specifically the production operations people across three different shifts, and they are monitoring and ensuring that the production chain flows correctly, raising alerts in a timely manner in case of any incident.

Control-M has positively impacted my organization by increasing availability and minimizing operational errors. Availability at the batch level is now at zero operational errors, whereas before implementation we had several errors from manual processes and our operators.

Since Control-M was implemented, operational errors have been reduced to one or two per year.

I consider the best features that Control-M offers to be availability and ease of scheduling.

The ease of scheduling benefits my team in our daily operations by making it quite easy to integrate new processes into the production chain when we have something new.

Control-M's performance when it comes to building, scheduling, managing, and monitoring workflows in production is very important, and that is what we are looking for, even from when new systems and functionalities start being developed.

The artificial intelligence capabilities of Control-M have been quite useful for us, giving us the perception that it is quite secure in terms of governance and security. The accuracy and reliability of the results that Control-M offers in terms of its artificial intelligence capabilities have helped us, and we see it as a very reliable tool.

Control-M could improve further by integrating it into online processes and rolling it out to our operational areas.

I would suggest improving its dashboards so that they are dynamic, enabling us to know which processes had an error and to handle them as a top-level alert automatically.

I have been using Control-M for about 6 years.

Control-M is very stable in my daily operation.

The scalability of Control-M is very easy to scale since if we need to integrate new servers or new processes, it is not difficult.

I rate the customer support I have received with Control-M as very good since last year and this year. We have received excellent support directly from BMC or from a Control-M partner.

I could not point to an exact metric for the return on investment with Control-M; however, it has helped us in terms of staff since we have not reduced the number of people and we have not increased headcount even though we have increased the number of operations.

This has helped us avoid penalties for any financial loss due to a bad batch operation.

Regarding licensing, I would describe my experience with the licensing, implementation, and pricing of Control-M as positive. Since last year, there has been greater engagement from the BMC people, and right now we are already in the renewal process, where we can see a lot of interest and support directly from BMC.

I did not evaluate other options before choosing Control-M as I joined when Control-M was already implemented.

I rate Control-M overall as a 10 out of 10. I give Control-M that rating because it perfectly covers our needs and has helped us a lot in operations here in production.

Currently, the integration process of Control-M with other technologies within our DataOps or DevOps operations is not being carried out, but in the near future, we will surely need to integrate it with DevOps tools.

The most important lesson I have learned using Control-M over these years is that we have minimized operational errors by no longer doing things manually and, as a result, increased the availability of those batch processes.

Automation of workloads in different environments such as physical servers, virtual servers, or in the cloud is very important for my organization, but Control-M is not yet integrated there, so we are using other tools such as Ansible for those types of functions.

My advice to other companies that are considering implementing Control-M is that it is highly recommended. Although it is not inexpensive, it helps a lot, especially in the financial sector, being very useful for managing high availability and continuous availability with zero operational errors.

Our primary use case for BMC Control-M is enterprise job automation and scheduling. We use Control-M to centrally manage and monitor a large number of jobs across the organization, including scheduling, execution, failure handling, job resumption, and alerting. It provides end-to-end automation and centralized control of critical batch workloads.

Control-M has improved operational efficiency by automating and centrally managing job scheduling, reducing manual intervention, minimizing failures and downtime and providing faster alerts and recovery of failed jobs.

The features I appreciate most about Control-M are its user-friendly interface and simplicity. It is not overly complex and the built-in APIs make it easy to use and integrate with other technologies.

For DataOps and DevOps processes, integrating Control-M with other technologies is relatively easy with an overall medium level of integration complexity.

The version of Control-M I was using did not have AI capabilities. Control-M would benefit from stronger AI integration that can analyze error messages, identify the root cause and take appropriate corrective actions without human intervention. Currently, some basic errors still require manual intervention, which AI could help minimize.

I have been working with BMC Control-M for more than 15 years, with my first implementation experience being for a leading Saudi telecom operator.

I rate the stability of Control-M as a stable 10. Control-M is a stable product.

The number of users using Control-M is around 50 plus. We have a centralized administrator who has a team working with different stakeholders, making this a centralized tool.

Control-M is scalable. We can do both scale-out and scale-up. Both options are available.

I rate Control-M support around nine out of 10.

We have been using Control-M since the beginning. We explored other products in parallel, but this was a fresh installation with no migration.

Regarding ROI with Control-M, we have not quantified it, but it has definitely saved manual work. A lot of human work has been automated through Control-M, although we do not have quantification of the exact savings.

When I compare Control-M with other solutions such as Apache, ActiveBatch, Broadcom, and HCLTech HWA , I find that Control-M stands out, particularly in terms of product support and global support capabilities.

I definitely recommend Control-M to others and some customers have already purchased Control-M based on our recommendation. I give this review an overall rating of 10.

My main use case for Control-M is that we use it for DevOps jobs.

A quick, specific example of a DevOps job I run with Control-M is that we patch servers often, and we have a sophisticated deployment process for different packages in our on-premises servers. We do not just use an out-of-the-box package manager; we have a Control-M process that handles pushing these patches into these controlled environments.

Regarding my main use case or how I use Control-M for these deployments, that is everything I do. We have lots of different Control-M jobs for doing different things, but we mostly use it for patching.

My main business use cases or services supported by Control-M include DevOps and management of devices used for deploying our application at different environments.

Control-M's reliability is its big appeal to me, as it has consistently worked for the organization since long before I got into it. Its simplicity in that way and its user interface are the big appeal, but that is about it.

That reliability and simplicity have helped my team when it works correctly and as desired, as the little task box turns red when it has failed, which is a good indicator for us that it is something we need to look at. It is an easy way to review a large number of jobs through a kind of world view of all the jobs, allowing us to see if anything has failed and letting us know what has failed in a nice user interface, making it very accessible to a lot of teammates. However, it has the drawback that just because a job has not completed successfully does not mean it has returned an error that turns the box red.

I do not have any metrics regarding how Control-M has improved the way my organization functions. It seems to have been picked a long time ago for its nice UI, but I think we made poor use of it. Good use of it is not very intuitive, and the lack of integrated version control makes people afraid to change things to try and improve them. Due to its proprietary nature, we lack environments to test adjustments on, which leads me to believe it has not been particularly helpful.

The best features Control-M offers, in my opinion, include the ability to selectively hold and run different jobs and the nice user interface, although I am not really keen on Control-M myself. It is not version controlled, which I really hate, or at least our implementation of it, but it is lacking in a lot of features. That is why I also use Jenkins.

The UI helps my daily workflow by giving us a quick visual way to establish what kind of progress a specific job is making.

I would appreciate Control-M providing better logging on the output of different jobs because sometimes a job completes and it thinks it succeeded, but it did not. There should be more programmability around error logging and better integration with version control. We are not really using Control-M as well as we could because we are not parameterizing all of our jobs and their steps, which I think can be done better, but that should be a lot easier to do. It is very hard to update these jobs, especially since we do not have something such as a JSON file for it that we can update.

To improve Control-M, there needs to be more programmability around how and when we log errors, and it would be nice to have some tools that actually allow us to interface with Control-M with scripts being run by the task steps. I think it would be beneficial to have some kind of configuration file that we could read, representing each job, giving us the ability to text edit these jobs instead of having to drag these boxes around, which is inconvenient. Additionally, better integration with version control, a web view, and improved resizing for the desktop application would be awesome. I also find that when I search jobs, the search bar does not order them in the order they are actually executed in, just alphabetically, and better searchability for these jobs is needed, especially when you have a large number of them in queue simultaneously.

It is very inconvenient to integrate Control-M with technologies for my data ops and DevOps processes as things change.

I would assess Control-M for building, scheduling, managing, and monitoring production workflows as not very effective. I use Control-M at least every few days, but it presents a kind of unhelpful user interface. While we have more senior people on my team familiar with all these functionalities, I mostly just run patches when needed, which is not very convenient. Coming from a more Linux-heavy world with depth in Jenkins, I find that these processes are much more convenient and the user interface for actual configuration and programming is much easier. Overall, Control-M comes across as very low-tech and clunky.

Using Control-M has made it pretty much impossible to create, integrate, and automate data pipelines across on-premises and cloud technologies. We almost never make new Control-M jobs because it is so inconvenient, and it is just a very clunky and tough tool to use. I would almost always prefer to do my work with Jenkins or simply write a Python script that logs its progress rather than use Control-M due to the cumbersome process of breaking steps into little boxes without version control.

I have been using Control-M for just a year.

I do not really know how many users are using Control-M in my organization, but my team consists of about ten people using it on and off, depending on our needs at the time.

I do not know how long the deployment of Control-M took, as that predates me by a long time.

I did not participate in the migration to Control-M, and I assume that over time, we will migrate more to Jenkins, as much as we can in the probably distant future.

I would rate Control-M overall a two out of ten.

I rate it that low because it is really very low-tech for what it does, and it has really fallen behind a lot of DevOps tooling. I use Jenkins here and there, which has version control and the convenience of managing credentials, making it easy to add agents and nodes, and it facilitates connections between those nodes more intuitively than what Control-M does. Control-M just makes you SSH into target machines; it essentially runs scripts and lacks built-in configuration compared to a tool such as Jenkins. Even though Control-M seems general-purpose, that just means it is not very well applied to the DevOps work I do, making it a clunky, proprietary piece of software. Its user interfaces are not really that valuable to actual technical people who just want good logging and good integrations for their automation.

Regarding Control-M's AI capabilities, I have not seen any governance and security features.

I have never used Control-M's AI capabilities to assess the accuracy and reliability of output.

The biggest lesson I have learned from using Control-M is that it is good to have code in front of you. Many organizations have followed trends onto tools that are very WYSIWYG, and I have used several such as Telerik Reports in the past. If you do not have code in front of you, you do not really know what is going on, and it becomes hard to facilitate integrations and log specific technical and business functionalities. Buying higher-level proprietary tools can lock you out of your own workflow due to the lack of customization and access.

My advice to others looking into using Control-M is to not do that because it is a proprietary product that overlaps a lot with newer open-source technology that is more accessible and paradigmatic for modern software development. Since it is a commercial product, the company likely offers consulting for best practices on how to use it, and getting training for its intended users along with documentation within the organization could help prevent other companies from falling into the same un-paradigmatic usage we have experienced.

I have been using Control-M in my career overall for quite some time. I joined this company about five years ago, but Control-M has been used there for way before, perhaps eight years, nine years, or more than that.

What I like the most about Control-M is that it is very reliable and works well for scheduling and even monitoring. The best thing I could say is the good visibility of jobs and their dependencies. When something fails, suppose when multiple jobs are affected, it would be useful to quickly identify the original failure and what was impacted because of it. Otherwise, it has very good visibility, scheduling jobs, and status is everything is good.

When something fails, as an improvement, it would be useful to have a clear explanation of what actually went wrong. The interface can sometimes feel a little busy for us. Finding the right information can take some time. It is not that we cannot find it, but it takes a few clicks. It is always helpful to have something very clear that quickly identifies what went wrong.

Regarding stability, there is no lagging and no issues with stability; it is pretty good.

Regarding scalability, I can say ten out of ten because it gives very good visibility of all the jobs and stability. There is no crash or downtime. It runs pretty well.

I have contacted the technical support or customer support of Control-M;. If we have any issues or need any help, we do contact them and raise tickets.

Regarding the quality and the speed of the support, as of now, I can say that it is acceptable. The response time is quite good. When we need them to be on call to help us, we decide on time and they come online to assist us. So it is acceptable.

I have never used any alternatives or something similar; we have been using Control-M for quite some time.

Regarding how easy or difficult it was to learn how to use Control-M, we have been using both web client and fat client, and I feel that the fat client is easier than the web client. There are a lot of options in the web client. With the fat client, I get more visibility and a more user-friendly interface. In terms of easiness, since it was already deployed and the functionality was there, it was pretty easy with some training from my team. It was not so hard to get through Control-M.

Control-M does require some maintenance on my end; we have periodic updates and patches. However, that is regular and that is needed to patch the vulnerabilities. Other than that, there is not much maintenance required.

I am not familiar with the pricing;I think it is still in discussion with Control-M.

Control-M is used for MFT service MFT features in daily work because files are transferred from one server to the target, and it is used primarily for integration between two systems. It is also used for scheduling and managing SAP jobs.

One workflow managed with Control-M currently involves encrypting files and transferring them to the bank, where the source system is encrypted and the encrypted file is transferred, which is easier to analyze and prevents breaches of flat files.

Control-M is used for MFT-based managed file transfers across different businesses globally, and the features provided by MFT in Control-M are believed to be the best for transferring files between on-premise and cloud systems.

Approximately 20 to 30 people use Control-M in the organization, performing various roles such as job configuration, administration, and usage for MFT and SAP jobs.

Control-M usage is being increased and businesses globally are being engaged to expand its implementation.

The favorite feature of Control-M is MFT manage file transfer, which is easy to integrate with other systems. It is used daily, and the API is utilized for admin activities and triggering Control-M jobs.

The API in Control-M helps automate tasks, such as creating jobs automatically using code in Visual Studio, enabling workload policies, job creation, and sharing the API swagger with the business to trigger Control-M jobs.

Control-M is a good tool with the best features for SAP scheduling.

Control-M has positively impacted Saint-Gobain by reducing manual work in file transfers, allowing automation of tasks, improvement of SLA, and enhancement of daily work and workload.

Control-M has improved organizational functionality by providing one platform to monitor jobs easily and access detailed logs to track SAP and MFT jobs with end-to-end visibility of job dependencies.

One area for improvement in Control-M is the ability to encrypt and decrypt files without needing to install an agent on the other side, and better customization options for SharePoint access in line with Saint-Gobain policy would be appreciated.

DevOps integration into Control-M needs to be explored more, as it is currently not being used in the organization but the potential benefits are evident.

I have been working in my current field for almost 11 years.

Control-M is stable.

Control-M's scalability is good.

Customer support for Control-M is excellent, and that aspect is greatly appreciated.

Previously, scripting was used for file transfers, which did not allow proper monitoring, leading to the switch to Control-M for both file transfers and SAP.

Other options were not evaluated before choosing Control-M because its features and functionalities were recognized in advance.

Before Control-M, scripts had to be created manually for file transfers, which took a significant amount of time. With Control-M, jobs are simply set up through drag and drop, which has reduced effort significantly.

Control-M is used for MFT-based managed file transfers across different businesses globally, and the features provided by MFT in Control-M are believed to be the best for transferring files between on-premise and cloud systems.

Although specific data is not available, Control-M has saved time in future implementations of end-to-end flows, making monitoring easier.

Control-M pricing is good, though it is somewhat expensive; still, it offers great features.

Other options were not evaluated before choosing Control-M because its features and functionalities were recognized in advance.

I advise others looking into using Control-M to experience its ease of monitoring jobs on a single user-friendly platform, streamlining job creation and monitoring.

The biggest lesson learned from using Control-M is that it reduces manual effort and increases productivity.

Control-M is effective for scheduling, managing, and monitoring workflows, and it is crucial for DevOps initiatives as it provides a single platform for monitoring related jobs, helping to reduce SLAs.

Control-M is good for my needs, and I would rate this review as a five out of five.

Control-M is primarily used to automate and monitor critical operational and database-related jobs, such as backups, batch processing, and application workflows. It helps reduce manual interactions and provides centralized monitoring while improving reliability and ensuring that dependent processes execute in the correct sequence. Overall, Control-M is a valuable tool for maintaining operational efficiency and reducing scheduling-related risks.

The primary daily use case for Control-M is scheduling and monitoring automated jobs, such as database backup jobs, archive log backups, and maintenance tasks and batch processing workflows. It is also used to monitor job dependencies, track failures, and receive alerts so that issues can be resolved quickly with minimum manual interactions. Control-M is used daily to automate and monitor database maintenance jobs, backup workflows, and batch processes. The centralized monitoring and alerting capabilities help ensure that critical workflows complete successfully and on schedule.

Beyond job scheduling, Control-M is used for end-to-end workload automation, monitoring critical business processes, and managing cross-application dependencies. It helps ensure that database maintenance jobs, backup processes, file transfers, and batch workloads execute in the correct sequence with minimal manual interactions. The centralized monitoring, alerting, and restart capabilities help reduce operational overhead and improve service reliability. Control-M provides good visibility into workflow status, making it easier for supporting teams to identify and resolve issues quickly. Control-M is a key tool for workload automation and operational monitoring. It helps automate repetitive tasks, manage job dependencies, provide proactive alerts, and ensure critical business processes run reliably. This has significantly reduced manual effort and improved overall operational efficiency.

Control-M is deployed as a centralized workflow automation platform that supports multiple applications and databases across several environments throughout the organization. Different application teams use it to schedule and manage their batch workloads, while operations and support teams use the centralized monitoring and alerting capabilities to track job execution and respond to issues. The platform enables workflow architecture across Windows, Linux, Unix, database, and application environments while providing a single point of control for all critical business processes.

Control-M is relatively easy to integrate with different technologies and operational requirements. One of its strengths is the broad support for multiple platforms, applications, databases, and file transfer processes. This helps organizations bring diverse workflows under a centralized automation framework. It provides integration capabilities that reduce the need for custom scheduling solutions and manual coordination between systems. As DevOps, one opportunity is to continue simplifying onboarding and integration.

Control-M has been integrated with the Oracle database environment to automate backup and log backup and maintenance jobs. This integration significantly reduced manual interaction, improved scheduling reliability, and provided centralized monitoring and alerting. As a result, the organization was able to identify and resolve job failures more quickly and ensure that critical database operations were completed on time. Database integration is most relevant to the role. ServiceNow integration has also been implemented. When critical jobs fail, alerts are tracked and managed more effectively through ServiceNow integration, reducing response times and improving operational visibility. Cloud integrations with Azure have been utilized. Integrating Control-M with Azure-based workloads enabled automation and monitoring of cloud-hosted processes alongside on-premises jobs. This provides a unified view of workflows and improves operational efficiency across environments. One of the most valuable integrations has been with the database environment.

The most valuable features of Control-M are its centralized monitoring, workload automation, job scheduling, job dependencies management, and proactive alerting capabilities. Control-M allows teams to schedule and manage complex workflows across multiple platforms from a single interface, improving visibility and operational control. It supports both calendar-based and event-driven scheduling and provides automated notifications for job failures. It enables quick recovery and rerun of jobs when issues occur. These features help reduce manual effort, improve reliability, and ensure critical business processes run smoothly.

The best features of Control-M are centralized job monitoring, workload automation, dependency management, proactive alerting, and cross-platform scheduling. These capabilities help automate critical business processes, reduce manual effort, improve operational visibility, and ensure reliable execution of batch workflows across multiple systems. The ability to quickly identify and troubleshoot and restart failed jobs is particularly valuable for operational teams.

Control-M is much more than a simple job scheduler. Its real value comes from workload automation, dependency management, and centralized monitoring across multiple systems and applications. Once workflows are properly designed, it can significantly reduce manual effort, improve operational reliability, and provide better visibility into critical business processes. Features such as automated alerts, job restart capabilities, historical tracking, and cross-platform integration make day-to-day operations easier and help teams respond quickly when issues occur.

Control-M is a reliable workload automation platform. There is an opportunity for improvement in troubleshooting failed jobs in complex workflows, as this can sometimes be time-consuming, especially when multiple dependencies are involved. Improved root cause analysis, more intuitive error messages, and enhanced reporting capabilities would help operations teams resolve issues faster. Additionally, a more modern and responsive user interface would improve overall user experience.

From an operational support perspective, complex dependency chains can be difficult to troubleshoot, and error messages could provide more actionable details. Reporting on dashboard customizations could be more flexible. The user interface could be more modern and user-friendly, and faster search and filtering capabilities for large job environments would be beneficial. While Control-M is a robust and dependable automation tool, troubleshooting failures in complex job workflows can sometimes be challenging. Improved root cause analysis, richer alert details, and enhanced reporting would further improve operational efficiency and reduce investigation time for support teams.

One improvement that would be valuable is the use of more intelligent monitoring and analytics capabilities. For example, predictive alerts that identify potential job delays and failures before they occur would help operations teams act proactively and enhance root cause analysis. Artificial intelligence assistance for troubleshooting recommendations and more customizable dashboards would improve efficiency. Additionally, simplifying the management of complex job dependencies and providing clear visual workflow views would make day-to-day operations easier.

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

Control-M should be highly rated for building, scheduling, managing, and monitoring production workflows. Its strength lies in providing a centralized platform where complex workflows can be designed, scheduled, and managed across multiple systems and applications. The dependency management capabilities help ensure that workflows execute in the correct sequence, while real-time monitoring and alerting provide visibility into job status and exceptions.

Control-M is extremely important for database and DevOps initiatives because many business processes depend on multiple interconnected systems, including applications, databases, and file transfers. Control-M provides a centralized way to coordinate these workflows and manage dependencies across different platforms. This helps ensure that tasks execute in the correct order and that downstream processes only begin when prerequisite activities have been completed. From a team efficiency perspective, it reduces the amount of manual monitoring and interaction required to manage complex workflows. Automated scheduling, centralized visibility, and a proactive alerting system support focus on issue resolution and process improvements rather than routine operational activities.

Control-M provides strong controls around user access and authorization, auditing, and workload management through role-based access. This helps ensure that users only have the permissions required for their responsibilities. Audit and activity tracking provide accountability and support complex requirements. Control-M also supports secure authentication, encrypted communications, and detailed monitoring of job scheduling, job execution, and workflow changes. The focus on governance and automation rather than uncontrolled oversight is appreciated. Control-M should be considered from governance and security standpoints. Features such as role-based access control and auditing demonstrate Control-M's emphasis on governance.

Based on my experience, the artificial intelligence-related capabilities appear reliable for operational assistance, workflow insights, and accelerating routine tasks. The outputs are generally useful and align with the information available within the platform. For business-critical activities, human review and validation remain important, especially when making operational decisions or implementing workflow changes. No major reliability concerns have been observed, but as with any artificial intelligence-enabled capabilities, external validation is necessary to ensure accuracy and context. What provides confidence is that Control-M combines artificial intelligence capabilities with governance, monitoring, auditability, and operational control. While outputs from artificial intelligence would still be validated for critical decisions, the combination of artificial intelligence with governance, auditing, and control mechanisms increases confidence in the platform's recommendations and outputs. I would rate Control-M an eight out of ten overall.

Control-M serves as my primary solution for enterprise workload automation and job scheduling. I use Control-M for running batch jobs at specified times and frequencies, ensuring that jobs execute in the correct sequence while coordinating jobs across applications, databases, APIs, cloud, and platforms, including the movement of files between systems. Control-M provides monitoring capabilities for detecting failed, delayed, or stopped jobs and for alerting the operations team when workflows breach conditions. Furthermore, it helps restart failed jobs based on predefined rules, allowing me to track whether business workflows will complete within the required time timeline, which supports SLA management. On the cross-platform automation side, Control-M coordinates between Windows, Linux systems, mainframe, databases, cloud, and SaaS workloads.

Control-M offers exceptional features including centralized monitoring, workflow orchestration, cross-platform compatibility, advanced alerting, and automated recovery. I particularly appreciate the end-to-end workflow orchestration, which connects jobs across applications, databases, cloud, data platforms, and infrastructure, and it is also relevant for AI-first IT operations, giving AI agents control execution.

My primary feature is end-to-end workflow orchestration, but I also find the secondary feature of event-driven automation valuable, where jobs can be triggered by events, files, conditions, or external signals, not just schedules. This functionality is helpful for sequencing jobs and triggering them at the right point when the business is ready for the process to follow, allowing me observability in terms of events to initiate operational workflows. Other notable features include automated recovery remediation, real-time monitoring, and integration with ecosystems like SAP, databases, AWS, Azure, Snowflake, Databricks, and Informatica.

The AI-assisted workflow creation is fantastic, as Control-M capabilities include AI-assisted creation of workflows from natural language intent, which is useful for moving towards AI-first operations. Control-M has taken the right step in bridging the traditional world with the new AI-first approach. Additionally, the orchestration of complex business workflows is significant for my operations as it connects what is otherwise a collection of independent jobs. The dependency and impact intelligence feature knows what depends on what, which is extremely valuable when an upstream job fails or is delayed. This impact intelligence becomes handy for complex integrations or workflow processes needing connection.

Finally, the predictive SLA management feature can identify when a workflow is at risk of missing its business SLA, making my management predictive and not just preventive, which helps in rectifying issues proactively. Furthermore, the event-driven automation in the closed-loop automation helps me act as soon as I detect an anomaly in the system. Monitoring systems detect the issues, Control-M orchestrates it while I use my ITSM or any service management tools to govern all these steps.

Throughout my organization, Control-M has positively helped establish certain capabilities by providing centralized workflow orchestration that replaced the fragmented scheduling and manual coordination that was previously required. This shift has eliminated repetitive operations by implementing automation, significantly reducing manual intervention and operator dependency for routine batch activities. As a result, I manage dependencies much better, ensuring complex upstream and downstream processes execute in the correct sequence. This enhanced dependency management has led to improved reliability, with reduced missed schedules, reduced incomplete workflows, and fewer failures needing correction through human involvement.

Control-M has also contributed to faster recovery procedures by creating standardized recovery processes to eliminate knowledge dependency on individual operators. Beyond this, I have transitioned from merely monitoring jobs to managing business processes, ensuring operational personnel have a comprehensive view of the business processes' impacts, bolstering operational visibility. Cross-platform integration has connected legacy distributed databases, file transfers, and workloads through a common orchestration mechanism, minimizing the tool sprawl that previously required excessive investment. Operational standardization from Control-M has created repeatable ways of scheduling, monitoring, escalating, and recovering workloads, which has significantly enhanced the outlook on processes. Finally, operational visibility has provided a consolidated view of workflow execution and dependencies, expanding the understanding of processes without requiring extensive discussions with business teams, instilling confidence in IT operations.

The areas for improvement in Control-M involve four key dimensions: observability, intelligence, integration, and automation. I strive to shift from job monitoring to business service monitoring and integrate with enterprise observability tools like Dynatrace. I aim to incorporate AI-driven root cause analysis to avoid manual examinations of multiple jobs by allowing an AI agent to analyze job histories and dependencies. I envision improving recovery processes by making them more autonomous, where AI diagnoses failures and Control-M executes necessary actions with subsequent verification. Enhancing SLA management with predicted outcomes is essential to help me intervene proactively. I want to reduce operational noise by collecting intelligence around job failures and achieving a self-healing candidate factory.

I have not used Control-M's AI capabilities to the extent I would desire, as the accuracy was not very impressive. Insights for failure and performance analysis are not reliable. The AI workflow creator serves as a productivity accelerator, but generated workflows need thorough review and testing. AI monitoring is moderate in usefulness for summarizing logs, while root cause analysis should be treated as a hypothesis rather than a certainty. The AI pilot for planning is similarly moderate in that it assists in generating jobs but requires human validation for production changes. As for autonomous remediation, trust remains a concern as it necessitates deterministic policies and verification. While data-grounded AI capable of querying operational data is somewhat reliable, the interpretive nature of natural language queries leads to susceptibility to incomplete inferences, resulting in hallucinations. Therefore, I cannot consider Control-M AI a reliable root cause analysis engine at this stage.

I have been using Control-M on and off for about ten years.

Control-M is stable.

Control-M's scalability has met my business demands, supporting organic growth efficiently. I have not pinpointed any significant issues as my preparatory measures have allowed for both horizontal and vertical scaling.

I feel customer support could use improvements, not as a complaint but as an observation. Enterprise clients typically require more attention to hasten new feature implementations without acquisition barriers.

I have utilized Control-M for almost a decade now, and while alternative, non-enterprise solutions existed, their footprint has considerably diminished, with Control-M remaining my primary orchestration solution. When searching for a solution, I evaluated various competitors and believe I made a commendable choice selecting Control-M, which continues to expand in usage since.

My deployment of Control-M took about six to nine months, significantly influenced by my focus on standardization and numerous discussions regarding necessary amendments for partner integrations, which impacted SLA management and governance features requiring their own cycles of standardization and acclimatization.

I maintain a 360-degree relationship with the vendor, contributing certain features not necessarily related to the core product but within the ecosystems.

Regarding return on investment, I am witnessing a favorable trend toward realizing significant ROI through standardization where numerous inefficiencies have been addressed. My aim is to bring standardization across automation, which has curtailed tool sprawl considerably. Control-M's automation features are now treated as essential enterprise-grade solutions, driving alignment and significant cost reductions across various departments. In addition, centralized AI usage aids in managing token costs, which I find beneficial.

Pricing, setup costs, and licensing can be complex. The licensing has generally been acceptable in value, but it requires careful planning since costs can greatly vary based on deployment models and environmental scales, as well as the number and type of workload integrations being consumed.

When searching for a solution, I evaluated various competitors and believe I made a commendable choice selecting Control-M, which continues to expand in usage since.

Control-M is currently used significantly within my organization, largely due to my early adoption as legacy systems are centered on it. I have plans to increase its usage further as I experience more mergers and acquisitions, particularly in integrating smaller-scale entities into my main workflows. Thus, as I navigate diverse environments, enhancing integration remains a priority while minimizing the impact of security challenges and optimizing operational tasks. Control-M is highly effective when processes are somewhat homogeneous. Organizations should leverage its features to ensure full advantage of what Control-M offers, as my learning experiences have shown that a solid understanding of the solution supports effective business service management. I would rate Control-M as an eight out of ten. I choose an eight out of ten because I still have steps to cover in implementing broader intelligence from large language models into Control-M's features. Control-M is evolving toward an AI-native approach to IT operations, and I would like to see it embody that more fully. From a governance standpoint, I rate it as an eight, as there are areas needing evolution to become a very enterprise-grade application. Security-wise, I want to see a stronger AI-first methodology for operations, indicating there is ample opportunity for enhanced security features within Control-M.