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.
"Using this tool, if there are any huge failures, we immediately get an email notification, and the proper team will be informed, at which time they can act accordingly."
"It can connect to a number of third-party/legacy systems."
"Approximately ~20 hours of manual effort have been reduced to ~5 hours with the help of ActiveBatch."
"The product offers a centralized platform for managing activities across many environments, applications, etc."
"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."
"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."
"By implementing a sophisticated scheduling mechanism, the system allows for the precise triggering of jobs at user-selected frequencies, enabling a seamless and automated execution of tasks according to specified time intervals."
"The most valuable feature is its stability. We've only had very minor issues and generally they have happened because someone has applied a patch on a Windows operating system and it has caused some grief. We've actually been able to resolve those issues quite quickly with ActiveBatch. In all the time that I've had use of ActiveBatch, it hasn't failed completely once. Uptime is almost 100 percent."
"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."
"The web UI is beneficial and the granular security policies allow us to cover all of our audit requirements."
"Running anything in crontab, you need to put a lot of logic into it to make it work. With this product, you don't have to worry about it. You have the schedule object where you put all the dates or holidays in it, and it does it for you."
"The aggregator reporting utility which tells us our throughput in lag and latency."
"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 capabilities of the product to schedule on multiple platforms, multiple operating systems."
"The most valuable feature of this solution is the functions are easy to use."
"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"
"There is this back and forth, where ActiveBatch says, "Your Oracle people should be dealing with this," and Oracle people say, "No, we don't know anything about ActiveBatch." Then, it all falls back on me as to what happens. Nobody is taking responsibility. This is the biggest failing for ActiveBatch."
"The documentation is very limited, and it can be improved."
"ActiveBatch is a little complex."
"Some improvements can be made to the user interface."
"The UI could potentially offer a more refined and user-friendly experience, fostering smoother interactions and facilitating easier navigation for users engaging with the application."
"The user interface can be improved so that it is more appealing and accessible to new users."
"Any product is going to have some room for improvement, no matter what. I see the company has already ventured into AWS and they're constantly trying to improve the managed file transfer which they have recently improvised. I think they bought a software called JSCAPE and they're trying to improve it, which is good. I am not sure if JSCAPE would be part of the base product but currently, you have to buy a separate license for it, which doesn't make sense. If it was Microsoft, ServiceNow, or integrating with other software vendors, I would understand but JSCAPE is now in-house and I'm not sure if they can justify having a separate license for JSCAPE. I would probably expect them to be packaging JSCAPE into the base product. They did switch over from a perpetual license model to a subscription model, which hurt the company a little bit. Nobody is offering the perpetual model anymore. As long as the transition is fair for both the companies, I think it should be fine and not burn us out."
"Setting up the software was hard."
"We see improvement possibilities in the processing provision of predefined evaluations or individual objects, or in the Self Service portal, which can be used by any user to monitor objects or start objects."
"The visibility and control features are somewhat limited."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"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."
"Pricing model for distributed should have an Enterprise option."
"It lacks support and integration with cloud computing platforms."
"Performance improvements in the UI would be appreciated."
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.