We performed a comparison between ActiveBatch Workload Automation and Automic 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 highly regarded for its flexibility, simplicity, and ready-made tasks. It provides live monitoring, automatic scheduling, and effective resource management. Automic Workload Automation receives acclaim for its strength, scalability, and straightforward integration. It enables control over various operating systems and products, offering a wide array of features and a user-friendly interface.
ActiveBatch Workload Automation can be enhanced in areas such as managed file transfer, licensing, cloud aspect, user interface, reliability of triggers, monitoring dashboard, price, documentation, support, and integration capabilities. Automic Workload Automation requires improvement in automation sets, language support, functionality, interface, web-based edition, file transfer, pricing, and support.
Service and Support: ActiveBatch Workload Automation has been praised for its customer service, specifically its helpful and responsive technical support. However, there are concerns about the service model and availability of the hotline. Automic Workload Automation has received mixed reviews, with some customers appreciating quick response times and helpful knowledge articles. However, others have faced challenges in reaching support and experienced delays in issue resolution.
Ease of Deployment: The setup process for ActiveBatch Workload Automation is straightforward and uncomplicated, although it can be slightly challenging when implementing it on various operating systems. The initial setup for Automic Workload Automation can be time-consuming and intricate, taking anywhere from one to five days.
Pricing: ActiveBatch Workload Automation is highly regarded for its flexible and reasonably priced setup cost. Users find it to be competitive when compared to other tools. Automic Workload Automation has experienced pricing changes. While some users view it as expensive, they still consider it affordable in comparison to similar solutions.
ROI: Active Workload Automation has been highly regarded for its ability to generate positive financial outcomes, resulting in a notable increase in net revenue ranging from 20% to 30%. Automic Workload Automation did not provide much ROI for users and was perceived as an added expenditure.
Comparison Results: ActiveBatch Workload Automation is the preferred choice when compared to Automic Workload Automation. Users appreciate ActiveBatch for its straightforward setup process and intuitive interface, while Automic is acknowledged to have different degrees of complexity. ActiveBatch is also praised for its versatility, offering prebuilt jobs and a user-friendly configuration.
"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."
"There are hundreds of pre-built steps."
"Easy to configure and simple to develop new features."
"The product offers a centralized platform for managing activities across many environments, applications, etc."
"The automation feature is a very valuable feature as the associates do not have to worry about performing repetitive tasks (i.e. endpoint security scans on a daily basis) that would take several hours to complete on a daily basis."
"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."
"From a scheduling point of view, it is pretty good."
"ActiveBatch's Self-Service Portal allows our business units to run and monitor their own workloads. They can simply run and review the logs, but they can't modify them. It increases their productivity because they are able to take care of things on their own. It saves us time from having to rerun the scripts, because the business units can just go ahead and log in and and rerun it themselves."
"Workload Automation's most valuable features are perspective analytics and coding."
"A good piece of software is like a good referee. If it's doing good, you don't notice it. That's the good thing about Automic. We don't even notice that it's there a lot of the time. It's a very, very stable product."
"An important feature is the ability to modify PeopleSoft Run Controls at run-time."
"We have two nodes that are highly available. You can add new nodes if you need that. You can take a node, a total node, down and still be operating fine. It has a lot of scaling to it."
"We do not have different automated silos. We have one view for our operators, which are doing things 24/7, and need just one interface, not multiple ones."
"We have a lot of governance and compliance requirements as a bank that we can fulfill with this product."
"The modulation of some of the things, like how the things are connected and disconnected. You have different login objects that you can quickly put to other different objects and other objects that you create, which makes transporting things very easy from one environment to the next."
"There are a lot of features which help us get a stable application. It is easy to have a stable production line, because this app supports us very well."
"Except for the GUI, everything looks good."
"Setting up the software was hard."
"The user interface can be improved so that it is more appealing and accessible to new users."
"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."
"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."
"Whenever there is an overload, we are seeing crashes happening."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time. So, if there was a constraint waiting, you may be looking for it in the wrong time frame. Plus, with thousands of jobs showing up and the way it pages output jobs, sometimes you end up with multiple pages on the screen, then you have to go through to find the specific job you're looking for. On the opposite side, you can limit the daily activity screen to show only jobs that failed or jobs currently running, which will shrink that back down. However, we have operators who are looking at the whole nightly cycle to make sure everything is there and make sure nothing got blocked or was waiting. Sometimes, they have a hard time finding every item within the list."
"ActiveBatch is a little complex."
"We have some problems with updates where some functions are changed, so you have to check your whole system to see if everything is still running. The update process for us is around two months of testing and one day of updates."
"The versioning and support for the lifecycle of Automic's developed solution is what we were missing. However, this is coming in version 12.2, so I am looking forward to seeing how it works."
"If you're getting deep into some of these workflows, you may have 20 different windows open and, if you didn't already have that deep understanding of how enterprise orchestration works, it would be very overwhelming to get up to speed on something like that... It needs some way to minimize the amount of windows and get it to where you could have all the information you need available on the screen."
"The user interface could be a little more user-friendly, as it is not the best out there."
"We would like to have some features with the AWI with the founding technique, which cannot currently be delivered."
"Automic Workload Automation could improve the SaaS deployment."
"They should work to reduce pricing."
"We would also like improved SLR monitoring. There are SLR objects, but I can't define an SLR object plus one, or end days. I can only do it for one day. As we are time shifting to another day, it is not possible. This should be improved."
ActiveBatch by Redwood is ranked 4th in Workload Automation with 35 reviews while Automic Workload Automation is ranked 7th in Workload Automation with 85 reviews. ActiveBatch by Redwood is rated 9.2, while Automic Workload Automation is rated 8.2. The top reviewer of ActiveBatch by Redwood writes "Flexible, easy to use, and offers good automation". On the other hand, 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 ". ActiveBatch by Redwood is most compared with Control-M, AutoSys Workload Automation, Tidal by Redwood, Redwood RunMyJobs and OpCon, whereas Automic Workload Automation is most compared with Control-M, AutoSys Workload Automation, Red Hat Ansible Automation Platform, Dollar Universe Workload Automation and Fortra's GoAnywhere MFT. See our ActiveBatch by Redwood vs. Automic 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.