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
 

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 December 2024, in the Workload Automation category, the mindshare of Control-M is 26.7%, up from 26.0% compared to the previous year. The mindshare of IBM Workload Automation is 8.4%, up 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 solution is innovative. Specifically for the overseas and time differences, you can feel the efficiency of Batch Impact Manager on jobs, batch processing, and impact management. It works the best on these kinds of issues. It saves us time and money, which is important. We save a lot using Control-M."
"The workflow is much easier compared to the ACS services we were using."
"Control-M has helped us resolve issues 70% to 80% faster. It provides us with alerts instead of having someone go to that particular server and check the logs to determine where the issue is. We can simply click on the alert information, then everything is in front of us. This provides us with time savings, human effort savings, and process savings."
"The reporting is top-notch. I haven't found any other applications on the market that can replicate what Control-M offers. The alerting is very good, and I think their service monitoring is the best in the industry."
"The initial setup is straightforward."
"The integration with ServiceNow is good. When a job ends and there are problems with it, we automatically open an incident in this platform, and the number of the incident is forwarded to Control-M. This means that we have a record of it with the log of the job."
"Promotions between environments, as well as local, mass update, versioning, and self-service."
"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."
"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 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."
"Provides a robust, full spectrum enterprise-wide WLA platform."
"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."
"It offers features like MDM and a Windows workstation, although there are some technical dependencies. It is more user-friendly and also includes failover and failback capabilities. While both systems offer high availability, Control-M's high availability is superior to AWS's."
"I have supported this product in literally 100s of different environments and its unmatched in its ability to scale to any size."
"The DWC, when configured correctly, is a great GUI tool to provide Self-Service Scheduling capabilities to the user community."
"Jobs can be triggered in multiple nodes."
 

Cons

"The performance could be better. Control-M Enterprise Manager tends to slow the system down even on a server with a six-core processor and 32 gigabytes RAM. The console is Java-based, so maybe OpenJDK 16 or 17 would be a performance improvement."
"Control-M should receive more notice when it releases new features. The user interface is also a bit complex, and the navigation should be streamlined."
"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."
"I'm currently working on the SaaS version, but I've also worked on the on-prem versions before. There is a handful of features that haven't been added to the SaaS version, and the BMC knows that. It's a matter of time before they prioritize the missing pieces and bring them into the SaaS version."
"Some of the documentation could use some improvement, however, it gets you from point A to point B pretty quickly to get the solution in place."
"The downtime is higher compared to AWS."
"They really need to work on improving the web interface, as there are still a lot of bugs... In general, they need to do a lot of work on shoring up their testing and quality assurance. A lot of bugs seem to make it into the product."
"I am unsure if Control-M is compliant with Microsoft Azure environment integrations. We have some clients in Azure environments. Specifically, in Canada, government agencies and nonprofits mostly use Microsoft Azure."
"This solution does have bugs and could be improved in this regard. However, these bugs are resolved relatively quickly."
"IBM needs to move away from its native terminology and adopt a more cloud-centric approach."
"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."
"Scalability-wise, it can be a little bit challenging."
"The performance of the previous versions could be better."
"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."
"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."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
 

Pricing and Cost Advice

"The cost is basically $100 a job, give or take."
"There are human costs in addition to the standard pricing and licensing of this solution."
"Pricing can be steep, but you get what you pay for."
"The pricing of Control-M is reasonable."
"BMC does NOT have a great licensing model from my perspective."
"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."
"This is now from my previous years as support for banks and big companies. If it's not enterprise scale, I find that it's too expensive for smaller companies. You really have to be quite big and need to have a dedicated support staff to run it, then you'll be fine. What we've seen at smaller companies, it's too expensive because they want to automate everything. Now, stuff that can literally run once a day for the rest of their lives is costing them $3 a job a day. It becomes too expensive, eventually. They are not seeing the return on investment because it's not business critical. Nobody is going to die or they're going to lose money if that job didn't run exactly at 11 minutes past 4:00. It's definitely for bigger enterprise companies, especially banks or healthcare providers. We have had an instance where Control-M was unavailable due to external factors for 20 minutes and there was a loss of almost a million euros because the solution involved logistics."
"The pricing and licensing could be better. However, when I compare Control-M pricing with JAMS, Control-M is still better priced than JAMS enterprise."
"The contract is with the customer with whom we are working, so IBM is not directly involved in this."
"It is about one-third of the cost of a controller."
"The solution's pricing is affordable."
"Pricing depends on the number of agents that you install."
"The solution is a little bit expensive."
"To my knowledge, IWA is the only WLA product that will provide "parallel tracking" capability to assist in upgrading from one platform to IWA."
"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.
823,951 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
9%
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 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
 

Learn More

 

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: December 2024.
823,951 professionals have used our research since 2012.