We performed a comparison between ActiveBatch Workload Automation and AutoSys Workload Automation based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: ActiveBatch Workload Automation is known for its versatility and ease of use, as well as its prebuilt jobs and real-time monitoring. It also has a strong alerting mechanism and excels in workload distribution and integration capabilities.AutoSys Workload Automation is highly acclaimed for its scalability and ease of use, as well as its speed and availability. It is particularly valued for job scheduling and orchestrating tasks.
ActiveBatch users would like to see enhancements in licensing, user interface, trigger reliability, monitoring dashboard, documentation, support services, cloud capabilities, and pricing. AutoSys users desire integration with cloud services, better reporting and monitoring capabilities, improved workflow management, and enhanced workload window management.
Service and Support: Users have praised ActiveBatch for its helpful and reliable technical support, which includes workarounds, a clear knowledge base, and APIs. AutoSys receives high praise for its very good, helpful, and responsive support. Users see the support team for both products as sufficient and capable, with a standardized approach and a mature product.
Ease of Deployment: The setup process for ActiveBatch Workload Automation is uncomplicated, although there could be improved documentation for file importing. However, configuring it on varied environments like Windows and Linux can be challenging. AutoSys Workload Automation setup is described as effortless, direct, and fairly rapid, taking around 10 minutes or less with minimal clicks. For more intricate setups, a complete implementation may require a month or two.
Pricing: ActiveBatch Workload Automation has an uncomplicated and quick setup process, with users finding the pricing fair and competitive. AutoSys Workload Automation offers different pricing and licensing choices, with some users perceiving it as costly.
ROI: Users have praised ActiveBatch Workload Automation for its positive financial impact, such as a notable rise in net revenue. AutoSys Workload Automation provides various advantages like heightened productivity, enhanced efficiency, cost savings, improved visibility and control, and decreased downtime.
Comparison Results: ActiveBatch Workload Automation is the preferred choice when compared to AutoSys Workload Automation. Users appreciate ActiveBatch's simplicity in setup and implementation, its versatility, ease of use, and extensive library of prebuilt job steps. They also value its real-time monitoring and scalability.
"There are hundreds of pre-built steps."
"It is very useful in sending confidential files through FPP servers."
"One of the most valuable features is the job templates. If we need to create an FTP job, we just drag over the FTP template and fill out the requirements using the variables that ActiveBatch uses. And that makes it reusable. We can create a job once but use it for many different clients."
"Approximately ~20 hours of manual effort have been reduced to ~5 hours with the help of ActiveBatch."
"One of the most valuable features of this solution is the versatility of the prebuilt jobs."
"One of the valuable features is the ability to trigger workflows, one after another, based on success, without having to worry about overlapping workflows. The ability to integrate our BI, analytics, and our data quality jobs is also valuable"
"It can connect to a number of third-party/legacy systems."
"Easy to configure and simple to develop new features."
"It streamlines processing really well, so we're able to cut down on our processing times."
"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."
"It's very easy to work with. The learning curve is not that steep."
"This solution enables us to improve our daily processing times. We can do everything faster than before we used this solution."
"We use CA Workload Automation AE r11.3.6 to automate enterprise-wide scheduling and file transfers using an FTP plugin."
"The ability to create calendars, calendering for batch jobs to run on a scheduled frequency."
"I prefer AutoSys over the other ones out there for ease of use, ease of understanding, and getting people to understand how the tool works."
"I find that it provides better agility in regards to job execution features."
"The thing I've noticed the most is the Help function. It's very difficult, at times, to find examples of how to do something. The Help function will explain what the tool does, but we're not a Windows shop at the data warehouse. Our data warehouse jobs actually run on Linux servers. Finding things for Linux-based solutions is not as easy as it is for Windows-based solutions. I would like to see more examples, and more non-Windows examples as well, in the Help."
"The user interface can be improved so that it is more appealing and accessible to new users."
"The interface is not that user-friendly and is a little tough to navigate."
"An area for improvement in ActiveBatch Workload Automation is its interface or GUI. It could be a little better. There isn't any additional feature I'd like to see in the tool, except for the GUI, everything looks good."
"Between version 10 and version 12 there was a change. In version 10, they had each object in its own folder. But on the back end, they saw it at the root level. So when we moved over to version 12, everything was in the same area mixed together. It was incredibly difficult and we actually had to create our own folders and move those objects—like schedules, jobs, user accounts—and manually put those into folders, whereas the previous version already had it."
"They have some crucial design flaws within the console that still need to be worked out because it is not working exactly how we hoped to see it, e.g., just some minor things where when you hit the save button, then all of a sudden all your job's library items collapse. Then, in order to continue on with your testing, you have to open those back up. I have taken that to them, and they are like, "Yep. We know about it. We know we have some enhancements that need to be taken care of. We have more developers now." They are working towards taking the minor things that annoy us, resolving them, and getting them fixed."
"The help center and documentation are not that helpful."
"One thing I've noticed is that navigation can be difficult unless you are familiar with the structure that we have in place. If someone else had to look at our ActiveBatch console and find a job, they might not know where to find it."
"Ease of implementation for upgrades."
"I am looking forward to more of their dashboard features. I think it would be very valuable for us to have dashboard features that could be delivered to our customers in the form of a URL, and they could refresh that URL whenever they wanted to get up to date performance metrics out of our systems."
"It would be helpful to be able to monitor and manage workload windows so we could minimize downstream applications. This would allow us easier access to the applications."
"I would like to see the Service Orchestrator, a B2B product, and maybe a process audit."
"Needs better documentation with fully explained examples for some of the job types."
"The GUI/Workstation is weak and needs to be improved. CA is working on this right now."
"The cross-platform arena, where you can run work on multiple platforms, needs improvement."
"There is a slow response time by tech support. Unless, you say it's severity level one. That will give you a two hour timing window for them to call you. It doesn't really happen exactly in two hours, but they try."
ActiveBatch by Redwood is ranked 4th in Workload Automation with 35 reviews while AutoSys Workload Automation is ranked 6th in Workload Automation with 79 reviews. ActiveBatch by Redwood is rated 9.2, while AutoSys Workload Automation is rated 8.4. The top reviewer of ActiveBatch by Redwood writes "Flexible, easy to use, and offers good automation". On the other hand, the top reviewer of AutoSys Workload Automation writes "Helps us manage complex workloads, reduce our workload failure rates, and save us time". ActiveBatch by Redwood is most compared with Control-M, Tidal by Redwood, Redwood RunMyJobs, VisualCron and IBM Workload Automation, whereas AutoSys Workload Automation is most compared with Control-M, IBM Workload Automation, Red Hat Ansible Automation Platform, Stonebranch and Dollar Universe Workload Automation. See our ActiveBatch by Redwood vs. AutoSys Workload Automation 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.