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

AutoSys Workload Automation vs Control-M 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

AutoSys Workload Automation
Ranking in Workload Automation
8th
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
79
Ranking in other categories
No ranking in other categories
Control-M
Ranking in Workload Automation
1st
Average Rating
8.8
Reviews Sentiment
7.0
Number of Reviews
118
Ranking in other categories
Process Automation (3rd), Managed File Transfer (MFT) (4th)
 

Mindshare comparison

As of January 2025, in the Workload Automation category, the mindshare of AutoSys Workload Automation is 15.5%, down from 19.0% compared to the previous year. The mindshare of Control-M is 26.5%, up from 25.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation
 

Featured Reviews

Antony Askew - PeerSpot reviewer
Helps us manage complex workloads, reduce our workload failure rates, and save us time
The visibility and control features are somewhat limited. This is a recognized weakness, but thee vendor is currently revamping the user interface to address it. While the current UI is a bit outdated, it's undergoing improvement. AutoSys Workload Automation has some areas for improvement, particularly in housekeeping and product maintenance. These tasks are currently quite manual and labor-intensive for our team. Additionally, the reporting and forecasting functionalities could be more robust. One area for improvement with AutoSys Workload Automation is that it comprises several distinct tools configured to work together. This necessitates familiarity with multiple tools for effective solution management. Consequently, it can sometimes lack a sense of cohesiveness as a unified solution.
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.

Quotes from Members

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

Pros

"We need to have things run in a very sequential order, so it is very useful that we can schedule the work flows."
"To me, what's most valuable in AutoSys Workload Automation is its robustness and quickness. The tool can trigger jobs within a few milliseconds, and it can handle large volumes of jobs."
"Integration with multiple services and applications across the enterprise."
"The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it."
"I find that it provides better agility in regards to job execution features."
"It gives a real-time view of all the batch processing that we have. Monitoring-wise, it is really good."
"The most valuable feature of AutoSys Workload Automation is batch processing."
"It is very valuable for us when we are trying to arrange or orchestrate jobs into a system. It is helpful for triggering jobs for a scheduled task."
"The monitoring tool is very good. It's very easy for expert and entry-level users to use on short notice."
"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."
"It is very easy to use. The HA feature is also very good."
"We value Control-M mainly for the ability to control multiple nodes in a coordinated manner. Control-M has the ability to really coordinate across a lot of nodes."
"Because it's a tool which allows us to do scheduled work, it allows for notifications when jobs aren't running within that scheduled time frame. This improves the opportunity to meet SLAs."
"I think the administration part is much more valuable than any other feature."
"The product has enhanced the interface with a clear visual display of data and process batches, showing the completion status of workflows."
"The scheduling and management were really good. Monitoring was also better. It had a good visual presentation. It showed me charts and all such things. It was really good on that side."
 

Cons

"​The cross-platform arena, where you can run work on multiple platforms, needs improvement."
"Because this product only computes processing days, it is hard when things need to be scheduled according to non-processing days."
"We are trying to see if we can use this from a cloud perspective with AWS, Azure, and other clouds, but it seems that there is no cloud integration in this product. We would like to see cloud integration. We are very pleased with this solution, but we are moving our application to the cloud, and we found out that it doesn't support any cloud features. So, we are trying to find a replacement."
"I would like to see the Service Orchestrator, a B2B product, and maybe a process audit."
"The lack of documentation, that is an issue. When we do need to bring it down for maintenance, it is always a scary moment for us because we have never had it crash."
"In terms of what should be in the next release, I want integration and AI and so on. I'd like easy reporting where you can compare information, for example, "that job normally takes three minutes and last time it took six minutes or 10 minutes." Then you can get the information to the engineer of which job is taking more time than normal - understanding strange behavior compared to the baseline."
"Some of the reports are either a bit hard to understand or don’t give you what you might expect to see."
"They could do better supporting it. They have too many of the same type of products, so sometimes it doesn't get as much attention as it should."
"A developer sandbox could be very helpful to try out new features or experience them."
"When it comes to supporting cloud services, Control-M is a bit slow. We are not advancing with the technology because we don't have the modules that can interact or use the new application services provided by the cloud technologies."
"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."
"Its operations and infrastructure can be improved."
"I would like to see more auditing capabilities. Right now, it has the basics and I've been trying to set those up to work with what our auditors are looking for."
"The history module only contains a maximum of 10 days, but we would like to have access to more. For example, it would be helpful to have 30 days or two months of history available."
"The stability could be improved. I ran into an issue with a recent Control-M patch. The environment would become unstable if security ports were scanned. This is an area they need to improve on, but ultimately it's a relatively small improvement."
"Whenever I pull an S4HANA job to the Helix Control-M tool, it pulls it naturally with all the steps. A job can have several steps, and in this case, it is very easy to control the steps taken. However, in the case of the SaaS IBP tool, it can pull the job but cannot identify the steps. So, when I want to take an action in a step, I have to split the job."
 

Pricing and Cost Advice

"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"I don't have information on the exact licensing cost of AutoSys Workload Automation because that's managed by the tools and financing teams. For agents, it's close to $4,00, but for the server setup, it's usually a one-time license initially, and it's AMC which is paid every year and comes close to $8,000 to $10,000."
"There is an annual license to use AutoSys Workload Automation."
"I certainly think the pricing is worth the value."
"CA pricing has been a problem, and not looked upon favorably here at all."
"We paid to use the solution monthly."
"It is overpriced."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"The license model is based on the number of jobs we run on the SaaS application or the number of executions, unlike the on-premise model options. If we have a handful of jobs, it's always good to consider Control-M, but if it's a large number of jobs, Control-M might not be a great option."
"Pricing varies depending on which components and modules you are using."
"You're going to spend a lot of money upfront, but the benefits you're going to get out of it are going to quickly pay for it."
"BMC's price is based on the number of jobs."
"They are expensive. If we were a small company, it would be complicated because we have to have strong sales and operations to be able to afford a tool of this level. Being a large company, the cost-benefit is covered, but it is not within the level of cheap solutions."
"Control-M isn't cheap, but this is an enterprise model."
"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."
"The solution is not cheap, it comes with quite a hefty price tag. Control-M is the market leader, but we still want the price to be as friendly as possible."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
831,158 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
47%
Manufacturing Company
12%
Computer Software Company
6%
Insurance Company
5%
Financial Services Firm
28%
Computer Software Company
13%
Manufacturing Company
8%
Insurance Company
6%
 

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 AutoSys Workload Automation?
The most valuable aspects of AutoSys Workload Automation are its performance, scalability, and ease of getting started for new users.
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 Control-M?
They should have a proper integration method that clearly defines the workflow. Additionally, there should be an automation system for developers to set it up more easily and quickly. My Ops team f...
 

Also Known As

CA Workload Automation, CA Workload Automation AE
Control M
 

Learn More

 

Overview

 

Sample Customers

Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
CARFAX, Tampa General Hospital, Navistar, Amadeus, Raymond James, Railinc
Find out what your peers are saying about AutoSys Workload Automation vs. Control-M and other solutions. Updated: January 2025.
831,158 professionals have used our research since 2012.