We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"Auto-scheduling is the most valuable feature. We have the ability to schedule [batch jobs on our Unisys mainframes] seven days in advance, so we know exactly how we're running every night."
"The most valuable feature is the self-service because it has made it possible to provide simple and quick solutions in the handling of certain tasks."
"Previously, we would receive a file from a vendor, then we would have to go through and make changes to individual accounts in our core system. There are probably between 10 to 20 accounts any given week. It probably took around five minutes for it to run through the report and make all the changes, and that was if there was nothing complicated with all very straightforward changes. Now, that is done in 30 seconds."
"There are three features which are valuable: the automated calendar functions; the notification process for failed jobs or unscheduled events occurring, via email and text messaging; and the ability for the scheduling package to communicate across multiple platforms."
"It has also helped to streamline our operations. We contract out our collection department so they are no longer housed on our system. They're housed on another platform. OpCon is able to not only pull in our data, but it also, on a daily basis, updates that third-party."
"Manual processing has been automated 99 percent by OpCon. With new processes, we give it at least two weeks manual so we can write down the details of how to do the steps, then we automate it. Within a month, it has been automated, then it's no longer a manual process."
"One of the advantages of OpCon is the ability to use the API and web services. We couldn't do that with our previous solution. We have been able to change our procedure for ticketing. When a job is down, we can immediately create a ticket from OpCon in our ticketing solution, which is ServiceNow, using the web services."
"I have been pleased with the support that we can get from the European partners. I think they are very good. All the time, when we have a question, they have an answer. It is very reassuring to have that support every day. Then, you can concentrate on your job and OpCon is just there to work. For us, it's perfect."
"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."
"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."
"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"
"What ActiveBatch allows you to do is develop a more efficient process. It gave me visibility into all my jobs so I could choose which jobs to run in parallel. This is much easier than when I have to try to do it through cron for Windows XP, where you really can't do things in parallel and know what is going on."
"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."
"As far as centralization goes it's nice because we can see all these processes that are tied to this larger process. The commissions, FTP processing, the reporting, the file moves to the business users — all that is right there. It's very easy to read. It's easy to tie it together, visually, and see where each of these steps fits into the bigger picture."
"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."
"From a scheduling point of view, it is pretty good."
"The Zero Upgrade feature is the most valuable."
"It has its own object-oriented scripting language and you can reload your object in many different places."
"It integrates well with the CICD pipeline."
"Both the stability and the scalability of Automic Workload Automation are great."
"The monitoring and troubleshooting features are rich and with the dashboards and other features, automation work is made easier."
"Do your first install, your first upgrade, with SMA. It's simple, it's as per the manual, as per the training, but you need that little bit of confidence."
"The ability to retrieve information from logs in variables to display relevant information would be helpful."
"What can get complicated is if you're doing anything more than just the built-in jobs. If you're using the more advanced features, troubleshooting becomes extremely complicated."
"The calendar interface and the frequency interface is a very powerful, yet complex, section of OpCon in which all our staff have made mistakes. They have implemented what they believed was logically correct and then afterward discovered that their logic was flawed because OpCon did it a different way. That part, which is incredibly useful, is also incredibly dangerous. The interface or the ability to directly do more functions within the frequency definitely has room for expansion. As good as it is, it can be a lot better."
"Usage is a little complex. It's not like you can bring somebody in and they can just use it. They have to be trained... As far as complexity goes, it's right up there."
"There is some difficulty with the ease of use when I don't have some of the templates that were already created. More templates would be great. Non-core featured templates are my biggest struggle."
"I would like to see them improve the Solution Manager for the web application. It's the future for us. Our customers need a lot of functionality, but there isn't that functionality within Solution Manager. So they have to develop and improve it."
"It was hard to automate in the beginning because there were a lot of concepts. I had to learn a lot of things, as I never used such a software before. I learned a lot of the concepts and ideas behind it in the beginning."
"It does have a little bit of a learning curve because it is fairly complex. You have to learn how it does things. I don't know if it's any worse than any other tool would be, just because of the nature of what it does... the learning curve is the hardest part."
"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 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."
"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."
"It could be easier to provide dashboards on how many jobs are running at the same time; more monitoring."
"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."
"The interface is not that user-friendly and is a little tough to navigate."
"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."
"Its dashboard can be improved. In version 12, they have already moved to a web-based interface from a UI. We are looking into this feature now. We are also looking for available APIs that we can use to interface the engine into our other systems. There should be a subservice facility that we can use to interface with Microsoft Teams and send out authorization on job executions. We have seen a feature like this in other products that we are looking into."
"The vendor support is really bad and should be improved."
"We would like a way to test our cloud-based automations on-premises, and then migrate them to the cloud after they have been tested, without needing an additional license."
"There are some monitoring features that could be added."
"In most of the packages available, it took time to study and gain knowledge of the features and resources due to poor documentation."
"This solution is certainly not the cheapest, but we win in time."
"Yearly, it's around $30,000."
"Our licensing is on a yearly basis."
"Our license is for 1000 jobs. Including support, the license and upgrades are 2000 euros a month."
"Yearly, we're paying about $62,000. OpCon has an all-inclusive feature and module license, but you pay per task."
"Our annual maintenance costs are $45,000. The initial cost is separate."
"On a yearly basis our cost is between $25,000 and $30,000."
"Annually, we pay $29,000. This is for a blanket policy that covers everything, like licensing and support."
"The price was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."
"I don't think we've ever had a problem with the pricing or licensing. Even the maintenance fees are very much in line. They are not excessive. I think for the support that you get, you get a good value for your money. It's the best value on the market."
"It allows for lower operational overhead."
"Currently, we are paying approximately $7,000 yearly, which includes support."
"ActiveBatch is currently redesigning themselves. In the past, they were a low cost solution for automation. They had a nice tool that was very inexpensive. With their five-year plan, they will be more enhancement-driven, so they're trying to improve their software, customer service, and the way that their customers get information from them. In doing that, they're raising the price of their base system. They changed from one pricing model to another, which has caused some friction between ActiveBatch and us. We're working through that right now with them. That's one of the reasons why we're why we were evaluating other software packages."
"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."
"The pricing was fair. There are additional costs for the plugins. We have the standard licensing fees for different pieces, then we have the plugins which were add-ons. However, we expected that."
"It costs too much. That's why we are now looking at other products."
"There are no costs in addition to the standard licensing fees."
"There are different licensing fees for cases where high availability is important."
OpCon is a robust and flexible platform capable of scaling up to meet the needs of clients running 140,000+ daily jobs across multiple environments and operating systems. Our proven migration framework helps clients painlessly transition from outdated or cost inefficient platforms thanks to our deep organizational expertise, REST API, and extensive library of legacy connectors. We have a variety of consulting options available for clients and offer no-cost training for the life of the contract.
Orchestrate your entire tech stack with ActiveBatch Workload Automation and Enterprise Job Scheduling. Build and centralize end-to-end workflows under a single pane of glass. Seamlessly manage systems, applications, and services across your organization. Eliminate manual workflows with ActiveBatch so you can focus on higher value activities that drive your company forward.
Limitless Endpoints: Use native integrations and our low-code REST API adapter to connect to any server, any application, any service.
Proactive Support Model: 24/7- US-based support and predictive diagnostics.
Low Code Drag-and-Drop GUI: Easily build reliable, customizable, end-to-end processes.
The modern enterprise needs to orchestrate a complex, diverse landscape of applications, platforms and technologies. Workload automation can prove a critical differentiator, but only if it provides intelligent automation driven by data analytics.
The IT landscape is currently more complex than ever: Islands of automation are a barrier to scaling and standardizing your workload activities. Processing errors are common because of manual handoffs. And the lack of an end-to-end view of the business process make inefficiencies and problems difficult to resolve. In addition to this, you are operating 24x7 and cannot find maintenance windows to upgrade your infrastructure in order to innovate.
CA Automic Workload Automation gives you the agility, speed, visibility and scalability needed to respond to the constantly changing technology landscape. It centrally manages and automates the execution of business processes end-to-end; across mainframe, cloud and hybrid environments in a way that never stops—even when doing an upgrade to the next version.
Automate repetitive tasks so you can focus on projects that drive your business forward. Find out how OpCon workload automation enables you to create repeatable, reliable workflows - all managed from a single platform.
ActiveBatch Workload Automation is ranked 3rd in Workload Automation with 12 reviews while Automic Workload Automation is ranked 5th in Workload Automation with 5 reviews. ActiveBatch Workload Automation is rated 9.2, while Automic Workload Automation is rated 8.0. The top reviewer of ActiveBatch Workload Automation writes "Everything runs automatically from start to finish; we don't have to worry about somebody clicking the wrong button". On the other hand, the top reviewer of Automic Workload Automation writes "Good integration, responsive support, and a short learning curve". ActiveBatch Workload Automation is most compared with Control-M, AutoSys Workload Automation, Tidal Automation, VisualCron and Redwood Business Process Automation - Workload Edition, whereas Automic Workload Automation is most compared with Control-M, AutoSys Workload Automation, Ansible, AppWorx Workload Automation and ASG-Zena. See our ActiveBatch Workload Automation 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.