We performed a comparison between Automic Workload Automation and Control-M based on our users’ reviews in four categories. After reading the collected data, you can find our conclusion below.
Comparison Results: Control-M comes out on top in this comparison. It is a very innovative and feature-rich solution and can be used to complete many diverse tasks and solve different issues, resulting in significant time savings and cost-effectiveness. Automic Workload Automation requires a bit of a learning curve, and some users tell us the web version is missing many of the solution's best features.
"We automate very manual, robust tasks, which are very time consuming and not error-free."
"The Zero Upgrade feature is the most valuable."
"The most valuable feature of this solution is the scheduler."
"It will improve how we function. It is just meeting a functional need in a maybe more agile way; it is faster."
"The most valuable features are the predefined templates for application-specific jobs and the access for different users."
"We have seen big improvements in automation and automated tasks allowing our people to work on more important things for the company, as well as getting financial data quicker."
"Both the stability and the scalability of Automic Workload Automation are great."
"Automation helps us. It makes our lives easier. Anything that can be automated is automated."
"Control-M has enabled true enterprise batch automation, which combined with the other BMC Control products on our mainframe platform, allows us to run a 24/7 site with the lights out."
"The most valuable feature is the reporting function. It allows us to pull up reports for specific information that the end-users are looking for."
"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."
"Self Service for repeatable, low impact workload automation processes."
"The pressure on our operations and our maintenance has been reduced."
"It is simple to create, integrate, and automate data pipelines and to ingest data from different platforms. It integrates well between platforms."
"Technical support is very helpful and available 24/7."
"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."
"During installation, some database elective issues popped up. These took some time to fix, but after some back and forth communication, these issues were resolved."
"This solution's out-of-box automation sets could be improved. They could be industry standardized out-of-box, or even runbook automation processes could be useful—just some plug-and-play automation processes out-of-box. It has many integration capabilities, from APIs to databases, but if the customer sees some out-of-box automation processes in it, it could be useful."
"I would like to see the event engine in the next release."
"Today, we use a rich client for this product. In the future, or for the next release, they will be using a web interface. This web interface is not as scalable as the rich client for us. The web client is not 100 percent programmed as we need it."
"It would be better if it was easier to view the automated processes."
"The forecast and long-term planning could be made a little better when you work with it in the future."
"The direction in which the UI is going is concerning to me. It does not offer the security context we would need to implement future versions. While I see benefit in the Web UI, the security it would lack in separating a user's experience from an administrator's experience is an issue for us. MFA functionality is required since we're dealing with connectivity to the POS and for PCI/SOX compliance."
"The vendor support is really bad and should be improved."
"Regarding product design and R&D, the DevOps pipeline could be improved with better capabilities and automation. API security and authentication is another area that could use improvement; users must have static credential passwords, which is a security concern."
"They can improve their interface."
"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."
"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."
"An issue we have run into in our lower environments is that Control-M can log you out frequently."
"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."
"I would like not to have to reach out to a third-party application company to do automated notifications. Right now, we still have people manually calling people and emailing people. There's a company called xMatters - and there are others - that has an API through Control-M that can automate any aspect of failure management. I'd like to see it build right into the product. I'd like to see a better notification product."
"We have some plug-ins like BOBJ, and we need a little improvement there. Other than that, it has been pretty good. I haven't seen any issues."
Automic Workload Automation is ranked 7th in Workload Automation with 85 reviews while Control-M is ranked 1st in Workload Automation with 110 reviews. Automic Workload Automation is rated 8.2, while Control-M is rated 8.8. The top reviewer of Automic Workload Automation writes "A tool requiring an easy setup phase that provides its users with flexibility and flow chart visibility ". On the other hand, the top reviewer of Control-M writes "We have seen quicker file transfers with more visibility and stability". Automic Workload Automation is most compared with AutoSys Workload Automation, Red Hat Ansible Automation Platform, Dollar Universe Workload Automation, AppWorx Workload Automation and IBM Workload Automation, whereas Control-M is most compared with AutoSys Workload Automation, IBM Workload Automation, Rocket Zena, ESP Workload Automation Intelligence and Redwood RunMyJobs. See our Automic 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.