Try our new research platform with insights from 80,000+ expert users

Control-M vs IBM Cloud Pak for Automation comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 9, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Control-M
Ranking in Process Automation
3rd
Average Rating
8.8
Reviews Sentiment
7.0
Number of Reviews
120
Ranking in other categories
Managed File Transfer (MFT) (4th), Workload Automation (1st)
IBM Cloud Pak for Automation
Ranking in Process Automation
21st
Average Rating
8.0
Reviews Sentiment
5.8
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Process Automation category, the mindshare of Control-M is 4.5%, up from 3.9% compared to the previous year. The mindshare of IBM Cloud Pak for Automation is 0.4%, down from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Process Automation
 

Featured Reviews

Pedro Fuentes - PeerSpot reviewer
Cost-effective, excellent support, and centralized access and control
They have a department that handles requests for enhancements. I talked to Control-M guys back in October or November when they had a gathering here in Atlanta. We talked about not being able to go back in history in Helix Control-M for more than two weeks. We submitted a request for enhancement. They told us that they are working on it, and they are thinking of expanding that to 30 days. We would like to see it expand to 90 days, but they are working on it. In Control-M, we were able to go back 180 days, but that was on-prem. The storage of that data was on our own servers. We know that storage is money, and we do not expect them to store that much of the data, but at least 30 to 60 days seem proper.
SYEDMUJTABA - PeerSpot reviewer
Effectively handles parallel instances effectively
I find it quite straightforward, perhaps around 8.5 out of 10 in terms of ease. When we upgraded from the old version of IBM BPM to the new one within IBM Cloud Pak for Automation, we didn't encounter any major issues. There were some minor ones, but they were easy to overcome.The migration process was part of our deployment strategy. We had a plan to migrate two processes per week from on-premises to the cloud. The migration involved taking the instances and migrating them to the new environment. There is an inbuilt feature in IBM Cloud Pak for Automation that facilitates the migration process, although I personally haven't conducted it myself; it's managed by my team. Overall, the setup process was relatively smooth.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The ability to dynamically predict batch run time is so valuable."
"The multiple scheduling options allow you to do anything you want, whenever you want, and however you want. You can easily be in control when things happen."
"Our data transfers have improved using Control-M processes, e.g., our monthly batches. When we used to do things manually, like copying files and reports, we used to take three to four days to complete a batch. However, with the automated file transfers and report sharing, we have been able to complete a batch within two and a half days and our reports are on time to users. So, 30% to 40% of the execution time has been saved."
"Automation of the batch jobs is the most valuable feature."
"First of all, the shift from manual to automation has been valuable. We have a tool that can automate."
"Monitoring is a valuable aspect of it. The monitoring tool is very good, and it is easy for expert and entry level users to use on a short notice."
"Control-M is infinitely scalable. We only need to add agents. BMC will take care of it if you need anything on the SaaS side, but we can handle the rest using our agent architecture."
"Most of our tasks also deal with databases, and Control-M's purpose-built module for the databases comes in very handy when handling database components."
"I believe two significant features of IBM Cloud Pak for Automation are the focus on SLA management and the capability to handle parallel instances effectively. Parallel instances, for instance, are valuable when dealing with a large number of users, enabling tasks to be performed concurrently for efficient system operation. The SLA aspect is crucial for tracking and ensuring timely completion of tasks. Additionally, the cloud compatibility of IBM BAW allows for seamless migration from on-premises to the cloud. This version also includes a business rule management system for storing and managing business rules effectively."
"What this product allows us to do is to move from on-prem instances where we are running independent instances of FileNet, Datacap, and ODM. It allows us to leverage container-based resiliency and availability modeling so that we have some visibility across the CP4BA ecosystem. We're now migrating all of our data to be in the Cloud Object Storage, and we can now use some of the features of Azure in terms of how we store and retrieve content for our members and our providers."
 

Cons

"With earlier versions, the support was not accurate or delivered in a timely manner. What would happen is that I would be in production mode and I would have an issue and would want to get someone on a call to see what was happening. But they would always say, “Hey, provide the log first and then we'll review and we'll get back to you." I feel that when a customer asks about a production issue, they should jump onto the call to see what is going on, and then collect the logs."
"I've never been very successful when researching ways to utilize Batch Impact Manager. It's a tool to set up dummy jobs in your job flow and it's supposed to come back to you and say, 'Okay, for this job flow, you are 50 percent complete at a certain point in time'...I would like things like Batch Impact Manager to be a little more user-friendly, out-of-the-box."
"There is definitely room for improvement. Version 9.0.20 actually comes with a web-based interface, but there are still a lot of things unavailable with it. There will eventually be more inclusions added into the web interface, but there is still a long way to go."
"It is a very strong product, but the reporting could be better."
"The unifying features between Control-M for different platforms needs improvement. The scheduling options on the Control-M mainframe jobs are different than they are on our Linux server. There are a few differences here and there."
"We did encounter a few scalability issues. Sometimes, there are too many jobs in our environment on different servers, but that’s not the tool issue, we can simply increase the FS size. However, that requires bank cost; hence the scalability issue."
"I think it's slightly expensive but at the same time it's a good product."
"A Control-M on-prem license is based on the number of jobs, which is the number of tasks a particular customer wants to have. These tasks have to be run within 24 hours window. For example, if you have a license for 100 jobs, you can run a maximum of 100 jobs in a 24-hour window. If your operations could not run 10 jobs, and they ran only 90 jobs, they just carry over to the next day, but the next day, they will have 110 jobs. Control-M asks you to buy those 10 more licenses because you were out of compliance in terms of the number of licenses. This is something that needs to be indicated in Control-M GUI so that customers know the number of licenses they're going to use in this time window. Their support and documentation should be improved. I am not that satisfied with their customer support. Sometimes, they don't have the answers. Their documentation is very poor. It is not well written, and it is not in a very logical manner. You can use it on Unix, Linux, Windows, and AIX, but it needs some improvement on iSeries. It needs a built-in mechanism inside the system to give you an option to restore from the last point of failure. If a process crashes, the Control-M needs to have a mechanism in iSeries where the process can be restored from the last point of failure."
"One of the challenges we're having is finding vendors who have experience in developing on the cloud. We can find developers on the old platform, but it is leading-edge technology. So, we are having some challenges, and IBM is assisting us to find vendor partners. To be able to leverage all the capabilities of the new platform, we have to upgrade our existing ecosystem of FileNet applications. Upgrading to the new platform while trying to modernize is always challenging because it is like you have a moving target."
"I believe there is room for improvement in the user interface, particularly in the Process Portal that customers use to view and manage their tasks. The UI of the Process Portal needs enhancement. Additionally, in the next release, I would like to see improved compatibility with Angular, allowing for direct integration with front-end systems. It would be beneficial to have built-in GUI features based on Angular within the system, rather than developing separate applications externally. This, in turn, would provide a more seamless and enhanced front-end experience."
 

Pricing and Cost Advice

"BMC does NOT have a great licensing model from my perspective."
"we are more looking for a better cost/license/performance model because BMC, while we could say it's the best, is also the most expensive. That is what we are probably most annoyed with. We are paying something like €1,000,000 over three years for having 4,000 jobs running. That's expensive."
"In our environment, pricing depends on the total number of maximum jobs that can run, which is fine. Therefore, if the number of jobs increases, then the licensing fees will increase."
"The pricing is reasonable. It's not an exorbitant amount. The licensing is pretty reasonable for the number of jobs that we run."
"Initially, our licensing model was based on the number of jobs per day. That caused some issues because we were restricted to a number. So at our renewal time we said, 'We want to convert from number of jobs to number of endpoints.' That cost us extra money but it gave us additional capabilities, without worrying about the number of jobs."
"Licensing costs are around $3000 a year."
"The price is right because of the licensing schema, which is based on nodes and processes. You purchase what you use, no more and no less, and you can grow with time."
"Compare to other tools Pricing and licensing was more. It should be decrease."
"Its cost is almost the same or comparable to what we pay with FileNet, but I'm not sure what we pay a year. A good part of CP4BA is the CPU-based licensing model. When we're dealing with 50,000 dentists, for example, if we were to use Salesforce, we would be hit with the licensing of 50,000 dentists, whereas when we build out in CP4BA, it is just based on our CPU usage, not on individual licenses."
"IBM Cloud Pak for Automation is relatively expensive, especially considering it is designed for long-living processes, not for normal automation needs. On a scale of one to ten, I would rate the pricing at around 9. There are no additional costs beyond the standard licensing fees, but IBM has multiple pricing models that make it expensive in its own way. Different plans are available, but overall, the experience suggests it is a costly solution."
report
Use our free recommendation engine to learn which Process Automation solutions are best for your needs.
846,617 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Computer Software Company
13%
Manufacturing Company
8%
Insurance Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

How does Control-M compare with AutoSys Workload Automation?
Control-M acts as a single, centralized interface for monitoring and managing all batch processes, which is helpful because nothing gets left unattended since it is all visible in one place, and th...
What do you like most about Control-M?
First of all, the shift from manual to automation has been valuable. We have a tool that can automate.
What do you like most about IBM Cloud Pak for Automation?
I believe two significant features of IBM Cloud Pak for Automation are the focus on SLA management and the capability to handle parallel instances effectively. Parallel instances, for instance, ar...
What is your experience regarding pricing and costs for IBM Cloud Pak for Automation?
IBM Cloud Pak for Automation is relatively expensive, especially considering it is designed for long-living processes, not for normal automation needs. On a scale of one to ten, I would rate the pr...
What needs improvement with IBM Cloud Pak for Automation?
I believe there is room for improvement in the user interface, particularly in the Process Portal that customers use to view and manage their tasks. The UI of the Process Portal needs enhancement. ...
 

Also Known As

Control M
No data available
 

Overview

 

Sample Customers

CARFAX, Tampa General Hospital, Navistar, Amadeus, Raymond James, Railinc
Information Not Available
Find out what your peers are saying about Control-M vs. IBM Cloud Pak for Automation and other solutions. Updated: April 2025.
846,617 professionals have used our research since 2012.