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

"JAMS offers diverse scheduling capabilities for any kind of job, including Linux, PowerShell scripts, and SQL, enabling automation of jobs, which has proven beautiful after three years of usage."
"In summary, this product is top class."
"One of the best features JAMS Scheduler offers is that it is cheaper than any other scheduler, making it a significant advantage alongside its user-friendliness that allows easy checking of logs and failures."
"The built-in triggers are great."
"JAMS has positively impacted our organization by saving us time, reducing errors, and improving workflows."
"JAMS positively impacts my organization because it helps make it easier to manage JD Edwards scheduled jobs and fills the gap that the JD Edwards application has with scheduling, resolving a lot of those issues."
"While I appreciate the other features, the agent stands out for its ease of installation and configuration for JAMS monitoring."
"Getting JAMS in place was a game changer for us back then."
"I prefer AutoSys over the other ones out there for ease of use, ease of understanding, and getting people to understand how the tool works."
"In a billion dollar company, you want a scheduling product that is very robust, which can handle the magnitude of schedules that we run through it."
"The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it."
"The most valuable aspects of AutoSys Workload Automation are its performance, scalability, and ease of getting started for new users."
"Automation of patch process."
"We're able to monitor a complex workload, easily see where we're at in our batch flows, and take care of problems before they become bigger issues."
"The really nice thing is that, as the business grows, we're not seeing the infrastructure grow."
"Running anything in crontab, you need to put a lot of logic into it to make it work. With this product, you don't have to worry about it. You have the schedule object where you put all the dates or holidays in it, and it does it for you."
"OpCon has absolutely streamlined our operations."
"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."
"Overall, I don't really have any complaints; the system does exactly what I want it to do in its current iteration, and if it never changed, it would still do what I need it to do, the way I want it to happen, and I am content with the way it operates."
"It has streamlined operations, specifically with the timing of our processes. We don't have to worry about if things are going to run at a certain time. The automation allows us to say, "Okay, we want this to run at this time, and this to not run until that is done." So, it has really streamlined the accuracy and timeline of when jobs run throughout the day."
"It allows us to organize everything into a process flow throughout the day for our different tasks that we have to run. So, it keeps everything organized. It is easy to monitor and adjust, if we need to."
"Having the jobs laid out while attaching dependencies is a nice addition to the program."
"The image scanning and anti-malware features are really valuable."
"OpCon is really reliable; we take a lot of value from OpCon, and it has improved our everyday jobs by a lot."
 

Cons

"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."
"They recently switched to subscription-based pricing, which increased."
"Improvements could be made in the service desk's knowledge and communication skills among engineers to better address customer needs and ensure issues are fully resolved."
"I would like a simple web interface that I could give to my team to go in and kill jobs or see why jobs died so that we don't have to drill down deeper into the application and know everything about it. It would be good to have a really clean web engine that would say here are the jobs running. We can then click to see the time running and whether any of them fails and other similar things. I know they have one, but it's not very simplistic."
"The client is horrible. Every time JAMS puts out a survey on what they can improve, I always say, "The client: When you are setting up jobs, it is quite horrible." The response has been, "Well, we are just using the Windows foundation," and I am like, "Why isn't it only your product?" We can get around it now that we know its quirks, but it is not the most user-friendly of tools out there. The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back. It is not user-friendly at all."
"The cost has definitely gone up tremendously. That is where I do know, as much as the feature sets are there, and if the newly acquired company is going to be doing a pushback, they might just say, 'Do we still need to pay this much? Or at that point, should we look into an alternative?'"
"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."
"For scalability, I would rate it as seven because when we have a huge volume, sometimes the tool is not so responsive."
"I've used this product for a long time, but the GUI to me feels outdated."
"They can be a little complex. It's just a big complex product that takes a lot of evaluation."
"There should be easier migrations from a different bus scheduler."
"There is always something that can be improved, but I do like this product."
"The solution could improve by having support for container environments."
"Some of the reports are either a bit hard to understand or don’t give you what you might expect to see."
"The scalability could be improved upon."
"The scalability is poor because I cannot use it for all automation solutions."
"We sometimes have a large number of jobs on the SQL Server and we can experience a very light lag in job starts. The lag can be a few seconds. It's never more than one minute, but sometimes we can experience some lags."
"In our environment, OpCon is much more expensive than it used to be a year ago."
"There is a learning curve."
"The UI refresh rate is really bad and needs improvement."
"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."
"Expect price hikes and threats when you hold them to account at every opportunity."
"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."
 

Pricing and Cost Advice

"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 relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"For what it does, the product is priced very well."
"JAMS is priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"It was $10,000 for the first year. Then, there is a maintenance cost for licensing every year that we get billed $5,000 for every year."
"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."
"All licensing models are a little overpriced, but JAMS offers a good value, especially given their support response times and ability to handle unforeseen issues like the SFTP transfers. I hope to find more use cases to get a better bang for our buck."
"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."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"There is an annual license to use AutoSys Workload Automation."
"We paid to use the solution monthly."
"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."
"I certainly think the pricing is worth the value."
"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."
"It is overpriced."
"It's definitely worth the cost."
"The cost is just shy of $20,000. That's for two licenses annually, production, and failover. It is a pricey solution. Comparatively speaking, you can certainly find schedulers which are cheaper. In some cases, you can find ones that are free or use free solutions. However, OpCon is by far the superior quality product, and you pay for that. This also has a cost savings associated with an FTE, so you can more than outweigh the cost of the solution if you were to reduce the staff that you have onsite. Plus, this means that you don't need to have someone during irregular hours."
"Yearly, we're paying about $62,000. OpCon has an all-inclusive feature and module license, but you pay per task."
"I am the one who signs the contract. In the beginning, when I started working here, it seemed very expensive, but after I learned everything that it does, I found it worth the price."
"It is at a decent price for the work that it does for us."
"Scaling is pricey."
"While the base pricing is reasonable, the à la carte options are making the overall cost more complicated and potentially problematic."
"While the overall cost is reasonable, I'm interested in exploring options for making the managed automation solution, specifically the mass solution, more cost-effective."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
919,003 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.
919,003 professionals have used our research since 2012.