We performed a comparison between Autosys Workload Automation and Control-M based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: In this comparison, Control-M finishes ahead of Autosys Workload Automation. With Control-M, all documentation is available online; many users feel this is a big win. The solution is very stable in most environments and the solution is very easy to use. The consistent excellent 24/7 support is a benefit that really rounds out this amazing solution.
"The most valuable aspects of AutoSys Workload Automation are its performance, scalability, and ease of getting started for new users."
"We get better reports than we use to have."
"It scales very well. We can add jobs and remove jobs. We do not have problems maintaining the product across multiple environments and multiple servers."
"It has allowed us to automate many of the functions of our operations staff. For instance, we had production control staff spending two hours a day entering date parms into our daily business processes. And now, CA Workload Automation does it for us."
"The CA workload agent has gotten much better. For our organization it's important for us to communicate in a secure fashion between the host and the other platforms, and we are able to do that with our CA product"
"The initial setup is easy."
"It can run an object on our Windows systems or our Unix systems, and then send messages to the other system when they are complete."
"We run millions of jobs through it every day using it for financial transactions, banking, credit cards, PeopleSoft, payroll, etc."
"You can let users access the system and manage jobs: 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 pressure on our operations and our maintenance has been reduced."
"The initial setup is straightforward."
"Control-M is useful to automate all critical and non-critical processes. Using Control-M, we can automate application workflows as well as file transfers involved in application workflows. We can also use it to run batches related to applications. Automating these processes reduces the RTO and RPO, which helps in the case of failures. It also helps us to identify bottlenecks and take corrective measures."
"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."
"Control-M provides us with a unified view, where we can easily define, orchestrate, and monitor all our application workflows and data pipelines. It also provides the ability to filter. So, if I don't want to see everything, I can also narrow it down or open ViewPoint. This is very important since we have thousands of jobs to monitor. If we did not have this ability, it would be very difficult to see what is going on."
"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."
"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."
"This product needs to improve its graphical user interface."
"Quick search feature and job analysis could be improved."
"AutoSys Workload Automation could improve in the Linux environment. The previous versions of the AutoSys Workload Automation let you take the profile of the user that you were using to run the tasks that you're going to automate, but in the latest versions, you can't do that, you need to make more definitions and it's a little bit difficult. It was easier in the previous versions."
"Some of the reports are either a bit hard to understand or don’t give you what you might expect to see."
"An area for improvement in AutoSys Workload Automation is that it lacks advanced features or advanced built-in functionalities found in competitors, for example, an advanced workflow feature. Even the handling or notification from AutoSys Workload Automation isn't the best in the industry. Other products have very good workflow-related functionalities such as ActiveBatch that's missing in AutoSys Workload Automation, so I wish the tool had those features."
"The solution does not have a friendly subscription model because it forces users to take a five-year subscription simultaneously, charging millions of dollars."
"The solution could improve by having support for container environments."
"It is a very strong product, but the reporting could be better."
"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 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."
"We develop software. More frequently, we are working with microservices and APIs, using our integration tool, MuleSoft. While Control-M is really a good tool to integrate with other tools, it is important for them to continue improving their microservices and API."
"A lot of businesses are using ServiceNow, which is another tool. I would like there to be some integration with ServiceNow or other third-party tools as well as have easily available integrations. Right now, we need to write scripts. Apart from that, if there were some integrations with an ITSM tool, then that would be good. Because at the end of the day, most of our clients are using different ITSM tools. I know that BMC Remedy is easy to integrate with Control-M. However, if there was availability for Jira as well as other ITSM and DevOps tools, that would be a good improvement."
"The biggest improvement they could have is better QA testing before releases come out the door."
"After we complete FTP jobs, those FTP jobs will be cleared from the Control-M schedule after the noon refresh. So, I struggle to find out where those jobs are saved. Then, we need to request execution of the FTP jobs again. If there could be an option to show the logs, which have been previously completed, that would help us. I can find all other job logs from the server side, but FTP job logs. Maybe I am missing the feature, or if it is not there, it could be added."
"They can give more predefined plug-ins so that we don't have to create them."
AutoSys Workload Automation is ranked 6th in Workload Automation with 79 reviews while Control-M is ranked 1st in Workload Automation with 110 reviews. AutoSys Workload Automation is rated 8.4, while Control-M is rated 8.8. The top reviewer of AutoSys Workload Automation writes "Helps us manage complex workloads, reduce our workload failure rates, and save us time". On the other hand, the top reviewer of Control-M writes "We have seen quicker file transfers with more visibility and stability". AutoSys Workload Automation is most compared with IBM Workload Automation, Red Hat Ansible Automation Platform, Automic Workload Automation, Stonebranch and CA 7 Workload Automation Intelligence, whereas Control-M is most compared with IBM Workload Automation, Rocket Zena, Automic Workload Automation, ESP Workload Automation Intelligence and Redwood RunMyJobs. See our AutoSys Workload Automation vs. Control-M report.
See our list of best Workload Automation vendors.
We monitor all Workload Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
