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

AutoSys Workload Automation vs OpCon comparison

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
Sponsored
Ranking in Workload Automation
3rd
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
44
Ranking in other categories
No ranking in other categories
AutoSys Workload Automation
Ranking in Workload Automation
4th
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
12th
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 July 2026, in the Workload Automation category, the mindshare of JAMS is 3.1%, up from 1.9% compared to the previous year. The mindshare of AutoSys Workload Automation is 6.7%, down from 10.9% compared to the previous year. The mindshare of OpCon is 2.3%, up from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS3.1%
AutoSys Workload Automation6.7%
OpCon2.3%
Other87.9%
Workload Automation
 

Featured Reviews

LV
Principal Data Base And Infrastructure Engineer at a outsourcing company with 501-1,000 employees
Automation has replaced nightly monitoring and delivers reliable, unified job scheduling
We have really enjoyed working with JAMS in terms of notifications, alerts, and streamlining. There used to be a process with Automate, which is another product from Fortra, but even before that, the other division of the company that we were merging with had a tool that was built in-house called a file handler or file distributor. It was an in-house developed tool, but it was not as streamlined or as efficient as JAMS is. We literally had to have a dedicated nighttime person monitoring. Although we are 24/7, the divisions of the company that we were using JAMS for have been small scale. While we have automated it, we have streamlined it in such a way that notifications go out and alerts go out, but if there is anything, then we get paged and alerted, and if anything needs to happen at midnight, we can wake up. On the other hand, with the tool I mentioned, the file handler and distributor, we used to have a dedicated nighttime person that had to be sitting and monitoring it to see when a file arrived, whether it met the conditions, and then execute the next particular job. 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.
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

"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."
"I find the historical tracking feature of JAMS invaluable for reviewing past events."
"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
"JAMS has improved our productivity immensely because everything flows. I don't think we could operate at our current staffing levels without it."
"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."
"The product is easy to use."
"JAMS is easier to use and cheaper than our previous solution. The installation is more straightforward, and JAMS has a graphical user interface, so it's more accessible."
"It's worth its weight in gold and we cannot get rid of it now."
"The one that we actually support is the CA-7 Edition for the scheduling package, it's very, very stable, always has been, and we rarely have any problems with it, so that's great."
"It's very easy to work with. The learning curve is not that steep."
"The flexibility of being able to schedule the timing and frequency of different automation scripts makes it easier for us to meet our customers’ business requirements."
"One of the biggest strengths is the stability of the product."
"AutoSys significantly reduces manual effort."
"The Inherit Dependencies feature reduces scheduling errors for holiday processing."
"It is a fairly stable solution."
"CA 7 is stable all the time."
"We have automated 95 percent of our processes since deploying this solution."
"There's also a self-service solution manager... that allows us to enable staff to run complex automation tasks by clicking a button and entering some information. They don't have to have access to the OpCon environment to kick off those kinds of events."
"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."
"File Watcher can run jobs when files are made available in a folder."
"The end code response allows us to evaluate how a process finished, set the termination/end code appropriately, and then trigger further processing based on how it ended."
"The solution streamlined our mortgage operations."
"It's very scalable. Right now we're barely scratching the surface of what it can do. I've looked at Symitar's instance of OpCon and they're running something like 13,000 jobs a day with all the clients that they have. So it can go from small use cases like ours to enterprise-level."
"It's a good product. They can run almost anything you need to run, as far as I am aware."
 

Cons

"The product does not allow the users to cut and paste the job names from the screen."
"JAMS notifications for hung jobs could be improved."
"They recently switched to subscription-based pricing, which increased."
"The only thing that they could improve on is the fact that they don't have a browser version of JAMS. They've got all the bits and pieces there if you want to build your own web version of it. It does come with a web client, but it's pretty clunky. They could improve on that."
"One thing that I know that the JAMS people said that they were working on that would be huge for us is a search capability so that you could search for tasks. It may be available in version 7 or in a future release of 7. I think that's on their roadmap. But right now, for us to do a search, we have to search through database queries."
"For scalability, I would rate it as seven because when we have a huge volume, sometimes the tool is not so responsive."
"We have had a lot of people working from home who can't always connect to the JAMS server. We use VPN, as most companies do, and we have it set up so that everybody can access the JAMS server. But many times, our people cannot access it... JAMS could do a better job of telling you what the problem is when you try to log in to the server."
"JAMS lacks source control features. Our previous solution had job control language, but JAMS doesn't. When migrating between versions, JAMS doesn't migrate all the data, like job change history, etc. Also, the scheduler doesn't have a way to make jobs invisible, so you can temporarily turn a job off if you decide not to run it today."
"We are not ready to go to the newest release (12.0)."
"Needs better documentation with fully explained examples for some of the job types."
"There is always something that can be improved, but I do like this product."
"I'd like to see automation pushed even further, giving us greater looks into other systems."
"​A better graphical user interface, because we have a lot of people using the client utility, and we want to get them away from that.​"
"I would like to see the Service Orchestrator, a B2B product, and maybe a process audit."
"AutoSys Workload Automation could improve in the Linux environment. The previous versions of the AutoSys Workload Automation let you take the profile of the user that you were using to run the tasks that you're going to automate, but in the latest versions, you can't do that, you need to make more definitions and it's a little bit difficult. It was easier in the previous versions."
"We received a 'Not active. "Scan Failed"; "The 'path/file' does not exist or not a directory" error message/email on one of our event level file triggers."
"It is a pricey solution. Comparatively speaking, you can certainly find schedulers which are cheaper."
"Licensing would be the first part I would overhaul. Each time a new licensing paradigm comes out, more features are removed and costs are added. They "add" features that are rarely used and increase charges for the number of jobs run. I'm sure someone in finance got a raise for their brilliance but the end-users won't thank them one bit. Expect price hikes and threats when you hold them to account at every opportunity."
"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."
"The initial setup was complex. There's so much it can do."
"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."
"It's not something you can just quickly grab, try, run, and play with."
"I'd like to see the product include a view where you can see everything about a specific job on a single screen."
"We are still in the early stages of our implementation, so at this point, I cannot see any needed improvements or features."
 

Pricing and Cost Advice

"There are no additional costs other than the license for Fortra's JAMS which is affordable."
"It's certainly a lot cheaper than Tivoli and Control-M. In comparison to them, you get a lot more bang for your buck. You get pretty much the whole functionality and more, in some cases, when compared to Control-M, but at a fraction of the price."
"JAMS is close to the lower end of the pricing models for enterprise scheduling solutions. They are much cheaper than Control-M, as well as some other products that I've used. I also don't know of another solution where you can actually get true, unlimited licensing, where you can have as many instances and as many agents as you want."
"Take advantage of its scalability. You can start small. The initial cost is very reasonable. Once you have started picking up the tool and adopting it, then you can scale up from there and buy more agents."
"The product is reasonably priced, and we don't have any add-ons."
"In the end, you'll find that it's really worth the price. There is some sticker shock, but it's worth every dime."
"It's expensive, to be honest, but it does the job."
"Definitely check how many single processes you want to run and count them as jobs. That is how you would work out your pricing on JAMS. For example, if you're running a number of commands and you can put them all into one script and run that script, you can count that as one job."
"It is overpriced."
"I don't have information on the exact licensing cost of AutoSys Workload Automation because that's managed by the tools and financing teams. For agents, it's close to $4,00, but for the server setup, it's usually a one-time license initially, and it's AMC which is paid every year and comes close to $8,000 to $10,000."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"We paid to use the solution monthly."
"Validate how many agents you need beforehand."
"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."
"I certainly think the pricing is worth the value."
"There is an annual license to use AutoSys Workload Automation."
"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."
"The pricing is over $100,000 for our credit union and I believe it's $89,000 for our clients, in total, annually."
"The pricing is reasonable."
"Yearly, we're paying about $62,000. OpCon has an all-inclusive feature and module license, but you pay per task."
"The pricing is very reasonable."
"Our annual maintenance costs are $45,000. The initial cost is separate."
"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."
"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."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
906,418 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
12%
Manufacturing Company
9%
Comms Service Provider
6%
Financial Services Firm
36%
Manufacturing Company
8%
Outsourcing Company
5%
Retailer
5%
Computer Software Company
19%
Financial Services Firm
17%
Construction Company
7%
Outsourcing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business14
Midsize Enterprise14
Large Enterprise20
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?
I was not really involved in the pricing, setup cost, and licensing at that level. I am more involved in the technica...
What needs improvement with JAMS?
To improve JAMS, it should resolve the issues with the JD Edwards application and the need for the SSH client connect...
What is your primary use case for JAMS?
My main use case for JAMS is to install, set up, and configure for customers working with JD Edwards application. A s...
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...
What is your experience regarding pricing and costs for OpCon?
I am the one who signs the contract. In the beginning, when I started working here, it seemed very expensive, but aft...
What needs improvement with OpCon?
One problem that I had with them when we got SMA Technologies is that sometimes the jobs fail, but they automatically...
What is your primary use case for OpCon?
In this credit union, we use OpCon for automation. That is the main use of it. We have over 3,000 jobs and schedules ...
 

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: June 2026.
906,418 professionals have used our research since 2012.