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

Control-M vs IBM Workload 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 Workload Automation
1st
Average Rating
8.8
Reviews Sentiment
7.0
Number of Reviews
121
Ranking in other categories
Process Automation (3rd), Managed File Transfer (MFT) (4th)
IBM Workload Automation
Ranking in Workload Automation
12th
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
32
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Workload Automation category, the mindshare of Control-M is 23.1%, down from 26.1% compared to the previous year. The mindshare of IBM Workload Automation is 7.2%, down from 8.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload 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.
Ilhami Arikan - PeerSpot reviewer
With an easy setup phase in place, agent-based installation can be done in minutes
Sometimes we have issues with the solution's stability. So, stability can be improved. Reporting and visibility of the solution need improvement. These days, we need more visibility. We need to access the logs and databases easily. You need to keep track of the running number of logs, like which ones are executed, completed, etc. So if there would be a good reporting dashboard, then it would be good. There's room for improvement in the solution since it is a challenging thing when we want to use the solution's technology with our new technologies. For example, if we need to use TWS on our OpenShift platform, the solution's API is not capable enough. So the product itself needs to be aligned with new technologies.

Quotes from Members

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

Pros

"The Automation API has opened up a world of possibilities for us, including the ability to create workflows on-demand using traditional DevOps tools."
"Before Control-M, we didn't have a centralized view and could not view what happened in the past to determine what will happen in the future. The Gantt view that we have in Control-M is like a project view. It is nice because we sometimes have some application maintenance that we need to do. So, in a single console, we can hold the jobs for the next hour or two. We can release that job when it is finished. This is a really nice feature that we didn't have before. It is something really simple, but we didn't previously have a console where we could say, "For the next two hours, what are the jobs that we will run? And, hold these jobs not to run." This is really important."
"Technical support is very helpful and available 24/7."
"The flexibility of Helix Control-M allows us to manage tasks efficiently. The user interface is comprehensive and lets me view all my jobs on one page, monitor everything, and access the job history."
"We used Control-M's Python Client and cloud data service integrations with AWS and, as a feature, it was very customizable. It gave us a lot of flexibility for customizing whatever data maneuver we wanted to do within a pipeline."
"Our ability to integrate with many different solutions has been invaluable. The new approach of the automation API and jobs-as-code is also valuable."
"Control-M is excellent when it comes to building, scheduling, managing, and monitoring production workflows. Those workflows are of very high importance to our operations."
"The ability to dynamically predict batch run time is so valuable."
"Jobs can be triggered in multiple nodes."
"Technical support from IBM is very good."
"The support from Cisco is very good. I was with them as a company for 40 years"
"The whole product is valuable because it is a tool for batch automation."
"Provides a robust, full spectrum enterprise-wide WLA platform."
"Jobs can be triggered in multiple nodes."
"The technical support is great, the product is easy-to-use, and it is stable."
"The most valuable feature of IBM Workload Automation is its holistic view, which helps me find technical solutions quickly. For instance, if a customer has an issue completing their workload within a specific time frame, the tool provides enough information to identify and resolve the issue. One of the main challenges is dealing with data infrastructure problems and pending updates. Workload Automation helps me leverage current AI capabilities to recommend architectural updates to avoid these issues. It also allows me to balance CPU usage effectively, ensuring service level agreements are met. The interface is user-friendly and facilitates this process smoothly."
 

Cons

"I would like to see them adopt more cloud. Most companies don't have a single cloud, meaning we have data sources that come from different cloud providers. That may have been solved already, but supporting Azure would be an improvement because companies tend not to have only AWS and GCP."
"The MFT applications should have more functionality and flexibility within that tool. Having more flexibility with that tool for handling the one to many or many to one concept. Like being able to take data from one source and push it to many locations or pull data from many locations and bring it back into a single source. That's why we still use our TPS program for the file transfers just because we don't have some of those capabilities available to us within MFT."
"The community and the networking that goes on within that community need improvement. We want to be able to reach out to an SME, and say, "Hey, we are doing it this way. Does that make sense?" Ideally, they come back. and say, "Yes, it does make sense to do it that way. However, if you want to do it this way, then it is a little more efficient." We understand that one solution framework doesn't fit everybody. Depending on the breadth of the data and how broad it is, you may have different models for one over the other."
"I would like to see automatic license management. And probably more importantly, some kind of machine learning to help identify the optimum automation path."
"There are numerous boxes to tick and things to check to ensure everything is in order before the upgrade happens. The process is very long"
"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."
"The UI can be challenging for new users due to its learning curve. Additionally, there are some errors during automation. More detailed logs would be helpful."
"But for some issues, BMC will suggest to upgrade to new version which will not be feasible to standards of the organisation. Hence some work around should be shown to run the business until new version was upgraded."
"IBM needs to move away from its native terminology and adopt a more cloud-centric approach."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"There should be more custom documentation, specifically around Java APIs. There should also be more training. In terms of features, we are currently using only 50% of its features. We don't use all features that are available, but there is always room for improvement in all of the tools."
"Slow down on the releases a bit. I fully understand that IWA functionality is increasing at an amazing rate, but trying to keep up with the upgrades is rough."
"The solution's installation could be improved because the customers have to do it all the time."
"It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
"Scalability-wise, it can be a little bit challenging."
"The configuration of IBM Workload Automation has some challenges. We have a difficult time customizing it, but it is similar to other solutions."
 

Pricing and Cost Advice

"Cost-wise, it is good."
"You must accept that BMC licensing can be very confusing. No one can easily understand how they calculate things, whether it is user-based, job-based, or server-based. The calculation is quite tough. How BMC calculates licensing is not easily available anywhere."
"Licensing costs are around $3000 a year."
"We have a license till 2024. We are good and satisfied with it."
"BMC's price is based on the number of jobs."
"It works on task-based licensing."
"It is not bad. The company can afford it, and it pays for itself. We have those jobs running automatically."
"We have a five-year contract with task-based licensing."
"Pricing depends on the number of agents that you install."
"It is about one-third of the cost of a controller."
"We transitioned from a server license to per job license, and that saved us a lot money."
"To my knowledge, IWA is the only WLA product that will provide "parallel tracking" capability to assist in upgrading from one platform to IWA."
"The solution is a little bit expensive."
"The contract is with the customer with whom we are working, so IBM is not directly involved in this."
"The solution's pricing is affordable."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
848,716 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
28%
Computer Software Company
13%
Manufacturing Company
8%
Retailer
6%
Financial Services Firm
33%
Computer Software Company
9%
Retailer
8%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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 needs improvement with IBM Workload Automation?
IBM needs to move away from its native terminology and adopt a more cloud-centric approach. For example, IBM still refers to machines as 'workstations,' whereas other systems, like Control-M, use m...
 

Also Known As

Control M
IBM Tivoli Workload Scheduler, IBM TWS
 

Overview

 

Sample Customers

CARFAX, Tampa General Hospital, Navistar, Amadeus, Raymond James, Railinc
Standard Life Group, Banca Popolare di Milano, A*STAR, ArcelorMittal Gent
Find out what your peers are saying about Control-M vs. IBM Workload Automation and other solutions. Updated: April 2025.
848,716 professionals have used our research since 2012.