"We recently did a branch acquisition of another bank, though not a full bank. With that, we had to convert all of their ACH transactions. It was a very complicated product that we received from our core provider, Fiserv, for some translation programs. It was very cumbersome to run through the process, convert it out, get output files, etc. Without anyone touching it, I was able to automate the full process from pulling in the files from this other bank, converting everything needed, and posting it to our customer's account 24-hours throughout the day."
"Last year, we added a second environment and the OpCon Deploy product. This has allowed us to build a testing environment. This has been a great addition for us as we can work through our workflows without disrupting our production environment."
"With a simple click of a button in self-service, the department or the user can complete his/her job."
"Reliability is always important, and the reliability of the system is outstanding."
"When a lot of jobs are scheduled on different platforms, without any interaction possible between them, it's very difficult to manage things. With OpCon we avoid this difficulty. It's very visual."
"The whole product is valuable to us because of the integrations that it has with the MCP and the Windows environments. You have to have the agent on each one of them that you want to monitor. The integrations that we have created are along the lines of extracting files and sending them through SFTP to another vendor. Those are the things that were taking a lot of time away from my staff."
"Often times there are criteria that cannot be determined by the system, which allows a human to make the determination and use the Self-Service Solution Manager to trigger a job."
"We're also starting to use its Self Service and Solution Manager. My team in the data center and some of the development team use the Self Service. Developers are using the Self Service for upon-request jobs for their testing. They used to have to go through us to schedule testing and now they can just go on and kick it off all they want. They have also really appreciated that they have access to view and/or submit jobs."
"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."
"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 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."
"We leverage the solution's native integrations regularly. We have to get files from a remote server outside the organization, and even send things outside the organization. We use a lot of its file manipulation and SFTP functionality for contacting remote servers."
"One of the most valuable features of this solution is the versatility of the prebuilt jobs."
"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."
"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."
"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"
"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."
"Easy configuration and integration with SAP."
"The features that I have found most valuable with AutoSys are that it is scalable, easy to use, fast, and always available. That's very important because if it's not steady then it's a real problem. So, at this point, we are satisfied with it."
"The most valuable feature of this solution is the functions are easy to use."
"AutoSys Workload Automation is a stable solution."
"This solution has made my clients' workplaces a lot less labor-intensive."
"It gives a real-time view of all the batch processing that we have. Monitoring-wise, it is really good."
"More functionality within self-service would be greatly appreciated."
"The products are extremely powerful and capable. Anytime you have such capability, the programming/configuration that goes into making it work can be complicated."
"Stability is an area for improvement. There are FTP agents that run on the MCP and they are there so that we can transfer a file from the MCP to the Windows environment or vice versa. Sometimes, and nobody has been able to figure out why, it just goes down, and all of my jobs that need it are hanging or failing... It would be very helpful if they could figure out what in the world is happening with that FTP client that's on the MCP."
"It would be great if you could create physically separate "clients," as I call them. I wish I could have a production client and a testing client and that they would be separate."
"The only downside to OpCon is that its features can be complicated and really must be taught. Most of our users don't have training beyond the free Basic Training that SMA provides, so for fresh eyes, it is kind of difficult to understand some of the language used."
"The FICS integration is a little bit clunky. We've had some tickets with their support team, and sometimes they couldn't figure it out, but that probably has more to do with FICS than with OpCon."
"The logs are a little daunting to look at the first few times, however, as you begin to understand what you're looking at, it becomes easier."
"I would like to see OpCon being accessible using a mobile app."
"A nice thing to have would be the ability to comfortably pass variables from one job to another. That was one of the things that I found difficult."
"Between version 10 and version 12 there was a change. In version 10, they had each object in its own folder. But on the back end, they saw it at the root level. So when we moved over to version 12, everything was in the same area mixed together. It was incredibly difficult and we actually had to create our own folders and move those objects—like schedules, jobs, user accounts—and manually put those into folders, whereas the previous version already had it."
"The interface is not that user-friendly and is a little tough to navigate."
"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."
"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."
"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."
"It could be easier to provide dashboards on how many jobs are running at the same time; more monitoring."
"Quick search feature and job analysis could be improved."
"I am not sure whether it is our limitation or a tool limitation because we haven't yet explored it, but whenever we look for different types of reporting, we have some limitations in getting those. It could be because of the way we have set it up internally in our enterprise, but it would be helpful if we can customize the reporting features and some of the alerts that can go out. When we connect enterprise systems, each one looks for a different use case, and if we can get different types of reporting, it will be helpful."
"The solution could improve by having support for container environments."
"The graphical interface can be improved."
"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."
"In terms of what should be in the next release, I want integration and AI and so on. I'd like easy reporting where you can compare information, for example, "that job normally takes three minutes and last time it took six minutes or 10 minutes." Then you can get the information to the engineer of which job is taking more time than normal - understanding strange behavior compared to the baseline."
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.
CA Workload Automation is an enterprise scheduling solution for the automation of IT processes in a heterogeneous environment. It automates and delivers millions of mission-essential services across thousands of companies worldwide. With the CA team and expert community, you get so much more than software. Work with us to get to mission-accomplished—every second of your business.
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 13 reviews while AutoSys Workload Automation is ranked 5th in Workload Automation with 8 reviews. ActiveBatch Workload Automation is rated 9.0, while AutoSys Workload Automation is rated 7.2. 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 AutoSys Workload Automation writes "Mature, reliable, scalable, and helpful for orchestrating jobs". ActiveBatch Workload Automation is most compared with Control-M, Tidal Automation, Automic Workload Automation, VisualCron and HelpSystems GoAnywhere MFT, whereas AutoSys Workload Automation is most compared with Control-M, Automic Workload Automation, Red Hat Ansible Automation Platform, CA Workload Automation ESP and Stonebranch Universal Automation Center. See our ActiveBatch Workload Automation 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.