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 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."
"The nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially."
"Error Handling is one of the best standout features of ActiveBatch."
"We are able to integrate it into multiple third-party tools like email, backup, tracking systems, SharePoint, Slack alerts, etc."
"Managing the workload and monitoring the tasks were very difficult with manual interventions. Now, by using ActiveBatch, the process is automated and it runs tasks on a scheduled basis."
"We use the main job-scheduling feature. It's the only thing we use in the tool. That's the reason we are using the tool: to reduce costs by replacing manual tasks with automated tasks and to perform regular, repetitive tasks in a more reliable way."
"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."
"The ability to create calendars, calendering for batch jobs to run on a scheduled frequency."
"The customized views that each individual can create, and views that can be made free-form, makes this very popular with the programmers."
"This solution has made my clients' workplaces a lot less labor-intensive."
"The most valuable feature of this solution is the functions are easy to use."
"We use technical support all the time. We would be lost without them. They're fantastic. Really good job. We're able to reach the right person to help us out right away."
"It's very easy to work with. The learning curve is not that steep."
"The scheduling feature allows us to know when jobs are going to run and makes sure they run in the order needed."
"The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it."
"It could be easier to provide dashboards on how many jobs are running at the same time; more monitoring."
"As more organizations are moving towards a cloud-based infrastructure, ActiveBatch could incorporate more capabilities that support popular cloud platforms, such as AWS, Azure, and Google Cloud."
"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."
"They could provide an easier installation guide or technical support to the organizations during the installation process."
"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."
"We have faced a couple of issues where we were supposed to log a defect with ActiveBatch. That said, the Active batch Vendor Support is very responsive and reliable."
"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."
"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."
"Some support issues need to be addressed, but not through email, through personal contact via phone or WebEx."
"Needs better documentation with fully explained examples for some of the job types."
"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."
"Quick search feature and job analysis could be improved."
"Pricing model for distributed should have an Enterprise option."
"CA Workload Automation is not part of CA's strategic vision going forward."
"The lack of documentation, that is an issue. When we do need to bring it down for maintenance, it is always a scary moment for us because we have never had it crash."
"The solution could improve by having support for container environments."
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, VisualCron, IBM Workload Automation and Redwood RunMyJobs, 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.
