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 Nov 24, 2024

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
119
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 February 2025, in the Workload Automation category, the mindshare of Control-M is 25.5%, down from 25.8% compared to the previous year. The mindshare of IBM Workload Automation is 8.0%, 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 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."
"The most valuable features of Control-M are automation and orchestration. It allows a different schedule, and we can manage thousands of jobs. It ensures we can complete them on time accurately. This automation reduces our manual intervention, significantly reducing error."
"I find it very helpful to be able to keep track of all our help desk tickets."
"We have a better picture of our auditability. When someone comes to us, and asks for sources, "How did the deltas occur?" We can provide answers quickly, or at least quicker than what we used to. We are actually sure of the information that we provide, where before it was like, "Hmm, I think it comes from over there. Let me double check, but it gets really convoluted over here and I think that is where it comes from." Now, if it is within the Control-M environment, it has a straightforward answer that we can provide with confidence."
"Workload Archiving is a very good feature for us. It helps with our customer requirements in terms of reporting and auditing... Previously, when we didn't have any archive server, we managed the data in Control-M with man-made scripts, and we would pull the data for the last 365 days, or three or four months back. Since we installed the archiving, we have been able to pull the data, anytime and anywhere, with just one click."
"The initial setup is straightforward."
"It provides a unified view where you can orchestrate and monitor all your application workloads and data pipelines. That's very important because with cloud, software as a service, edge computing, traditional data center, and legacy apps, there are all these environments. If you don't have that single pane of glass or that one place to look at, you're going to invest a lot of time and resources into tracking things down when they go wrong."
"Control-M has improved application reliability and the SLAs in our company by quite a bit. You can see if problems are coming. If we have an SLA in a couple of hours, we know well before that couple hours if processing is behind, and it allows us to take some preventative action."
"The technical support is great, the product is easy-to-use, and it is stable."
"The initial setup is easy."
"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."
"The most important feature is the creation of folders. It's a really great feature because you can organize the process with naming conventions."
"The solution helps automate processes so that the workload can be handled on a daily basis."
"The project we worked on involved the running of nearly 24,000 job instances in a single day, so I would say that the solution is stable."
"Jobs can be triggered in multiple nodes."
"This solution has a request feature where users can request the added features they need to have developed. Based on client voting for those features, these are developed and released."
 

Cons

"I think it's slightly expensive but at the same time it's a good product."
"The licensing cost can be improved."
"They could enhance the product's data flow, job processing speed, and efficiency."
"The reporting tool still needs a lot of improvement. It was supposed to get better with the upgrade, and it really didn't get better. It needs help, because it's such a useful thing to have. It needs to be more powerful and easier to use."
"Control-M reporting is a bit of a pain point right now. Control-M doesn't have robust reporting. I would like to see better reporting options. I would like to be able to pull charts or statistics that look nicer. Right now, we can pull some data, but it is kind of choppy. It would be nicer to have enterprise-level reporting that you can present to managers."
"One feature I would like to include is in the middle of the monitoring domain. In the monitoring domain, if I have to update a number of jobs, the only way to do it is by manually clicking on each job. I would like a feature that allows me to do a mass update in the jobs, which I feel is still lacking."
"Reporting in Control-M could use improvement."
"A lot of the areas of improvement revolve around Automation API because that area is constantly evolving. It is constantly changing, and it is constantly being updated. There are some bugs that are introduced from one version to the next. So, the regression testing doesn't seem to capture some of the bugs that have been fixed in prior versions, and those bugs are then reintroduced in later versions."
"The configuration of IBM Workload Automation has some challenges. We have a difficult time customizing it, but it is similar to other solutions."
"The schedule refreshes daily and that's a challenge for us."
"To improve IBM Workload Automation, I suggest enhancing automation features further, as more automation would be beneficial. The product is good enough for my current customers, but improving technical support and pricing would be welcome. We often need quicker responses and better solutions than we can manage manually. These improvements would make the product even better."
"This solution does have bugs and could be improved in this regard. However, these bugs are resolved relatively quickly."
"The solution should offer more free technical sessions to customers so that they can gain more experience or learn more about how to use it."
"IBM needs to move away from its native terminology and adopt a more cloud-centric approach."
"The performance of the previous versions could be better."
"The solution's installation could be improved because the customers have to do it all the time."
 

Pricing and Cost Advice

"One of the restrictions that we had was with some of the licensing, and not having any insight on the financials part of the product. I don't know what the licensing on the product is, but we don't have an unlimited enterprise license. So, there might be a limitation on either the cost of the licensing or the number of seats."
"Cost-wise, it is good."
"As we increase the number of tasks or jobs on the system, there are concerns about cost."
"The cost of the hardware is high. Because you need to license each job, it is costly."
"The pricing is reasonable. It's not an exorbitant amount. The licensing is pretty reasonable for the number of jobs that we run."
"We are paying way more for Control-M than we've paid for any of our other scheduling tools."
"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."
"Its cost is a little bit higher than other solutions such as AutoSys or DAC. For the demo, there were some plans, such as start plan, scale plan, etc. Pricing was based on the plan."
"Pricing depends on the number of agents that you install."
"To my knowledge, IWA is the only WLA product that will provide "parallel tracking" capability to assist in upgrading from one platform to IWA."
"It is about one-third of the cost of a controller."
"The solution is a little bit expensive."
"The solution's pricing is affordable."
"The contract is with the customer with whom we are working, so IBM is not directly involved in this."
"We transitioned from a server license to per job license, and that saved us a lot money."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
832,340 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%
Financial Services Firm
32%
Computer Software Company
9%
Manufacturing Company
8%
Insurance Company
8%
 

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 is your experience regarding pricing and costs for Control-M?
Pricing is generally affordable, though some features cost a bit more.
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: January 2025.
832,340 professionals have used our research since 2012.