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.
"The Jobs Library has been a tremendous asset. For the most, that's what we use. There are some outliers, but we pretty much integrate those Jobs Library steps throughout the process, whether it's REST calls, FTP processes, or file copies and moves... That has helped us to build end-to-end workflows."
"Since I started using this product, I have been able to easily track everything as it mainly monitors, alerts, and looks after all the services - even across platform scheduling - which has helped me immensely."
"It has helped with scheduling complex jobs with simple scripts."
"ActiveBatch can automate predictable, repeatable processes very well. There is no real trick to what ActiveBatch does. ActiveBatch does exactly what you would expect a scheduling piece of software to do. It does it in a timely manner and does it with very little outside interference and fanfare. It runs when it is supposed to, and I don't have to jump through a bunch of hoops to double check it."
"For developers, it is easy to orchestrate the workflows and the integration has been very easy."
"Since we are no longer waiting for an operator to see that a job is finished, we have changed our daily cycle from running in eight hours down to about five. We had a third shift-operator retire and that position was never refilled."
"ActiveBatch helped us automate and schedule routine tasks such as data backups, file transfers, database updates, and report generation, which frees IT staff to focus on other studies."
"Error Handling is one of the best standout features of ActiveBatch."
"The customized views that each individual can create, and views that can be made free-form, makes this very popular with the programmers."
"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."
"The solution has been stable."
"It gives us flexibility when doing releases. We can make changes for one day in a PDS member, since we stage our jobs by date, and the next day the normal job definitions are run."
"The scheduling feature allows us to know when jobs are going to run and makes sure they run in the order needed."
"We need to have things run in a very sequential order, so it is very useful that we can schedule the work flows."
"The actual scheduling of our jobs has helped us tremendously. Before it was all done manually, and we've totally automated the whole functionality, so there's no longer a case where somebody didn't run something."
"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."
"Some of the advanced features in the user interface are a bit confusing even after referring to the documents."
"I have faced struggles to understand, set up the tool, and implement it in my early days as a new user."
"The user interface can be improved so that it is more appealing and accessible to new users."
"They could provide an easier installation guide or technical support to the organizations during the installation process."
"I can't get the cleaning up of logs to work consistently. Right now, we are not setup correctly, and maybe it is something that I have not effectively communicated to them."
"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."
"The monitoring dashboard could have been more user-friendly so that in the monitoring dashboard itself we can see the total number of jobs created in the system and how many were currently active/scheduled/chained."
"The interface is not that user-friendly and is a little tough to navigate."
"Because this product only computes processing days, it is hard when things need to be scheduled according to non-processing days."
"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."
"Documentation and cross-application externals could be improved."
"Quick search feature and job analysis could be improved."
"We have to escalate through channels to get to somebody who knows what's going on. It takes time that we do not necessarily have."
"There is a difference between a web interface and the thick client interface. We particularly like a thick client interface, and it has gone away."
"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."
"CA Workload Automation is not part of CA's strategic vision going forward."
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, Automic Workload Automation 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.