No more typing reviews! Try our Samantha, our new voice AI agent.

AutoSys Workload Automation vs OpCon comparison

Why PeerSpot?
Sponsored
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 29, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

JAMS Scheduler
Sponsored
Ranking in Workload Automation
3rd
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
56
Ranking in other categories
No ranking in other categories
AutoSys Workload Automation
Ranking in Workload Automation
5th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
84
Ranking in other categories
No ranking in other categories
OpCon
Ranking in Workload Automation
14th
Average Rating
9.2
Reviews Sentiment
7.3
Number of Reviews
59
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the Workload Automation category, the mindshare of JAMS Scheduler is 3.5%, up from 2.1% compared to the previous year. The mindshare of AutoSys Workload Automation is 6.5%, down from 9.8% compared to the previous year. The mindshare of OpCon is 2.6%, up from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS Scheduler3.5%
AutoSys Workload Automation6.5%
OpCon2.6%
Other87.4%
Workload Automation
 

Featured Reviews

reviewer2890770 - PeerSpot reviewer
Developer at a healthcare company with 1,001-5,000 employees
Centralized scheduling has improved automation and reduces manual monitoring for complex workflows
The best features JAMS Scheduler offers are centralized job scheduling, dependency management, and monitoring. I also appreciate the alerts and retry options because they help us handle failures without constantly checking jobs manually. Centralized scheduling makes it easier to manage all our jobs from one place instead of maintaining multiple schedulers or scripts. Dependency management is especially useful for chaining workflows because JAMS Scheduler can automatically trigger the next job only when the required previous step completes successfully. Another useful feature is the monitoring and alerting. If a scheduled job fails or runs longer than expected, we can quickly identify it and take action, which is particularly helpful for production support and reducing manual monitoring. JAMS Scheduler has helped quite a bit with identifying common job failures, missed schedules, dependency issues, and execution errors. The alerts and job history make it easier to identify the failure point and take corrective action without manually checking every workflow. JAMS Scheduler's code-driven automation has been useful for handling more complex scheduling logic and workflows that go beyond simple time-based triggers. It is important for us because we can combine scripts, dependencies, conditions, and parameters to support different production scenarios without creating too much manual intervention.
PK
Assistant VP at a financial services firm with 10,001+ employees
Experience significant automation with robust integration and user-friendly interfaces
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancements in the R24 release. The web UI needs some improvement. Cloud integrations are limited to 25 or 30 configurable plugins and integrations to the cloud. They can improve in that area. They have separate tools, not AutoSys Workload Automation, such as Atomic and other SaaS-based solutions that can run inside the cloud. AutoSys Workload Automation can be configured in the cloud, but it requires a substantial number of VMs depending on the load. For on-premises deployment, it is a very good solution. They need to increase their footprint in the cloud and improve the web UI. They are making excellent progress in the R24 release.
Jose Rivera Hernandez - PeerSpot reviewer
Senior VP of Technology at Triangle Credit Union
Helps automate all kinds of jobs and it's worth the price because it saves a lot of time and money
One problem that I had with them when we got SMA Technologies is that sometimes the jobs fail, but they automatically restart. SMA Technologies automatically gets a notification that the job has failed, and they restart it on their end, so now, we have the job restarting twice. There were times when we came into the office in the morning, and we had two files because the job ran twice. I do not know if the system can prevent a job from running the second time. If a job has run successfully, or it is running, it should not run again.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The fact that we no longer need to use Excel spreadsheets is huge."
"JAMS has positively impacted our organization by saving us time, reducing errors, and improving workflows."
"The user-friendly and adaptable scheduler allows us to manage various scheduling scenarios."
"By using JAMS, we have gained a lot more efficiencies in terms of all of those to streamline it, and there is no necessary need for having an overnight engineer just keeping an eye on all of this."
"One of the things I like the most, as a SQL DBA, is the fact that we can manipulate tables in the background. Also, the fact that you can have your own views and work with the product the way it fits best is a very helpful feature."
"I like how you can add new execution methods on the fly. It isn't overly complex to add Python script support to an execution method in the JAMS system. The scheduling is excellent. You can schedule a maintenance window and take that resource unit out of everything. It halts all of the jobs."
"It makes everything that we want to do so much easier. We have had a number of instances in the past where we have had developers who have been working on a project, and even though we have had JAMS for all these years, they will create some SQL Server Agent job, or something like that, to run a task. When it is in code review and development is complete, the question always comes around, "Can JAMS do this?" The answer has always been, "Yes." Pretty much anything we have ever developed could be run by JAMS."
"We also use the solution’s Interactive Agents. If we need to push something to our dealer portal, we can just drop a file in a folder and it goes. Running interactive tasks helps me users focus on business processes since I don’t have to take care of running the jobs manually."
"The benefits I have seen from AutoSys Workload Automation are significant; I would say it is about ease of administration."
"We have not encountered any stability issues with the supported versions."
"It's very stable, it's highly redundant, it's very recoverable within the batch work, and it's easy to use."
"It has helped to simplify cross-dependency between MVS and Open systems jobs."
"The web UI is beneficial and the granular security policies allow us to cover all of our audit requirements."
"The most valuable feature is the ease of coding up schedules to run jobs in both the mainframe and distributed environments."
"Automation of patch process."
"Centralizing all this into a single workload automation tool using the CA product has really helped a lot of customers."
"File Watcher can run jobs when files are made available in a folder."
"The most significant benefit is time savings, which translates into money savings."
"We haven't freed up a full person's job using it, but there are a good handful of people for whom it has freed up about half of their time. And those employees love it. A lot of tasks are based on certain times, and they're no longer stuck doing those things at those times. We don't have to have anybody coming in early anymore. They can focus on the processing part of their jobs instead of the file moving and downloading."
"We've saved thousands of man-hours with automation and reduced errors significantly."
"It is so simplistic that it gives us peace of mind."
"In two weeks, OpCon has done 15,677 jobs that an operator would normally have had to do, significantly streamlining operations and doing things right every time."
"It can run scripted tasks automatically over and over without intervention. That is what it does and the part that I really like because repetitive tasks need to be done over and over, day after day, no matter what day of the week it is. It is difficult to have staff do these manually and consistently, especially over weekends or through the night. Instead, you can have OpCon do them."
"ROI has been great."
 

Cons

"I would enhance the compatibility feature of JAMS because sometimes when the server is under high load, it does not inform us and we cannot get answers."
"The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back."
"One area of improvement I see for JAMS Scheduler is making the user interface more intuitive for new users, especially when configuring complex job dependencies."
"One area for improvement would be making the user interface more intuitive, especially for new users working with complex job dependencies."
"The UI could be better. There were some things that were not quite intuitive, such as the search tool. When we tried to search for jobs, we had to clear the entire search and then go in and enter the new search query. That's something that wasn't intuitive for a new user."
"Right now there's not much of an Azure integration with JAMS at the moment directly because we run separate pipelines."
"JAMS could be improved with a web client that is accessible and as fast as a normal website, eliminating the need to RDP to the servers to access the JAMS client."
"The documentation is not super... It's not as quick and slick as I'd like it to be."
"However, when compared to other products in the market, it is still behind other solutions."
"Quick search feature and job analysis could be improved."
"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."
"An area for improvement in AutoSys Workload Automation is that it lacks advanced features or advanced built-in functionalities found in competitors, for example, an advanced workflow feature. Even the handling or notification from AutoSys Workload Automation isn't the best in the industry. Other products have very good workflow-related functionalities such as ActiveBatch that's missing in AutoSys Workload Automation, so I wish the tool had those features."
"We would like to see good improvement on the historical reporting capabilities."
"With requirements, they have "always" and "skip" on them. That would be nice, for them to have it on triggers also."
"The main push is the web UI, to be able to give it to our business users."
"Some of the reports are either a bit hard to understand or don’t give you what you might expect to see."
"It is a pricey solution. Comparatively speaking, you can certainly find schedulers which are cheaper."
"The biggest area where there is room for improvement would be integration with their code. They've got a function for embedded scripts and it would be nice if that worked with a code or versioning management system, like GitLab."
"I would like to see improvements with the graphical display during the execution of jobs with complex sequences, step-by-step, in self-service."
"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."
"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."
"Of course they have a RESTful API within OpCon, but they have that new web services agent that we installed because we have some SOAP APIs and we had to interact with SMA to get things running. Our developers did do some tweaks, but we have now been able to get some test jobs running, and understand how the workflow goes back and forth."
"I might like to see a little bit more of a seamless user interface."
"We have found it difficult to have people rely solely on Solution Manager."
 

Pricing and Cost Advice

"The pricing of JAMS has not been an issue for us, as it has allowed us to save time."
"In the end, you'll find that it's really worth the price. There is some sticker shock, but it's worth every dime."
"The licensing model for JAMS is straightforward and based on the number of agents, not the number of jobs you run. It's cheap and fairly simple."
"It's expensive, to be honest, but it does the job."
"JAMS is priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."
"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"I certainly think the pricing is worth the value."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"CA pricing has been a problem, and not looked upon favorably here at all."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"People need to pay attention to how they use their ESP agents on the distributed platform. That's where some of the cost comes in, based on how many you need or how many you use."
"It is overpriced."
"The price of this solution is reasonable and there is an annual license required."
"We paid to use the solution monthly."
"I have seen some contracts, and it seems that Control-M is a lot more expensive than OpCon, but I do not know the pricing of OpCon. Control-M seems to be four or five times more expensive than OpCon."
"Compared to AutoSys and ISE, OpCon was a lot cheaper to put in. AutoSys is hundreds of thousands of dollars to just install it because they don't have an interface into our system. You have to teach them what your system does."
"The cost is based on the number of jobs. You pay for what you use. For us, the support cost is between €20,000 and €30,000 per year. It's too expensive."
"Yearly, it's around $30,000."
"OpCon cost us $80,000 in 2017 money, and that included everything: support, installation, onsite assistance during the conversion, etc. It's been a worthwhile investment by far."
"It was substantially less expensive than ASG-Zeke... I would suggest that someone who is only looking at price when evaluating workload automation tools take a very hard look at OpCon because it is well-priced."
"This solution is certainly not the cheapest, but we win in time."
"The purchasing price was in the $30,000 or $40,000 range, but I don't remember how much of that was licensing or installation and how it was broken out."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
918,614 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Construction Company
10%
Comms Service Provider
10%
Manufacturing Company
9%
Financial Services Firm
31%
Outsourcing Company
9%
Manufacturing Company
7%
Retailer
4%
Financial Services Firm
17%
Construction Company
8%
Computer Software Company
7%
Outsourcing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise18
Large Enterprise30
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise79
By reviewers
Company SizeCount
Small Business16
Midsize Enterprise29
Large Enterprise19
 

Questions from the Community

What is your experience regarding pricing and costs for JAMS?
The pricing, setup cost, and licensing for JAMS Scheduler are favorable.
What needs improvement with JAMS?
One area of improvement I see for JAMS Scheduler is making the user interface more intuitive for new users, especiall...
What is your primary use case for JAMS?
My main use case for JAMS Scheduler is scheduling daily RPA jobs, such as running an invoice process automation after...
How does Control-M compare with AutoSys Workload Automation?
Control-M acts as a single, centralized interface for monitoring and managing all batch processes, which is helpful b...
What needs improvement with AutoSys Workload Automation?
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancement...
Ask a question
Earn 20 points
 

Also Known As

No data available
CA Workload Automation, CA Workload Automation AE
No data available
 

Interactive Demo

Demo not available
Demo not available
 

Overview

 

Sample Customers

Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
LOHR, Carnival Cruise Lines, Herbalife, Digital Federal Credit Union, Synergent, Frandsen Bank & Trust
Find out what your peers are saying about AutoSys Workload Automation vs. OpCon and other solutions. Updated: September 2026.
918,614 professionals have used our research since 2012.