Try our new research platform with insights from 80,000+ expert users

AutoSys Workload Automation vs JAMS comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 4, 2025

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

AutoSys Workload Automation
Ranking in Workload Automation
7th
Average Rating
8.4
Reviews Sentiment
7.2
Number of Reviews
81
Ranking in other categories
No ranking in other categories
JAMS
Ranking in Workload Automation
5th
Average Rating
8.8
Reviews Sentiment
7.6
Number of Reviews
34
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Workload Automation category, the mindshare of AutoSys Workload Automation is 12.8%, down from 18.5% compared to the previous year. The mindshare of JAMS is 1.7%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation
 

Featured Reviews

Antony Askew - PeerSpot reviewer
Helps us manage complex workloads, reduce our workload failure rates, and save us time
The visibility and control features are somewhat limited. This is a recognized weakness, but thee vendor is currently revamping the user interface to address it. While the current UI is a bit outdated, it's undergoing improvement. AutoSys Workload Automation has some areas for improvement, particularly in housekeeping and product maintenance. These tasks are currently quite manual and labor-intensive for our team. Additionally, the reporting and forecasting functionalities could be more robust. One area for improvement with AutoSys Workload Automation is that it comprises several distinct tools configured to work together. This necessitates familiarity with multiple tools for effective solution management. Consequently, it can sometimes lack a sense of cohesiveness as a unified solution.
Rob Grafrath - PeerSpot reviewer
We can scale up our organization's scheduling and automation without having to add staff to the department
The biggest area with room for improvement is the area that my organization benefits the most from using JAMS, and that is in custom execution methods. I happen to have a very good C# developer. Ever since we got JAMS, he has spent a lot of time talking to JAMS developers, researching the JAMS libraries, and creating custom execution methods. He's gotten very good at it. He is now able to create them and maintain them very easily, but that was hard-won knowledge. If I ever lose this developer, I would be hard-pressed to find anyone who could create JAMS custom execution methods as well as he can since there really isn't all that much help, such as documentation or information, available on how to create custom execution methods. I really think that they could benefit greatly by being much more transparent about C# development, maybe by making a JAMS cookbook or a developer portal where they could throw ideas at each other. One of my complaints with the marketing around JAMS is that it says things like, "It integrates with Teams". They talk about integrating with a lot of things, but marketing doesn't tell you that they are talking about JAMS running PowerShell jobs. Since PowerShell can automate things like SharePoint and Teams, that is how marketing gets away with saying it has so many integrations. JAMS doesn't have as many built-in integrations as they advertise. I think they should build more of them, and improve on the ones they have built.

Quotes from Members

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

Pros

"Integration with multiple services and applications across the enterprise."
"We don't have to manually run things anymore. We can have the work that a team of 50 people would do, all inside of one platform."
"I find that it provides better agility in regards to job execution features."
"AutoSys significantly reduces manual effort."
"The customized views that each individual can create, and views that can be made free-form, makes this very popular with the programmers."
"The aggregator reporting utility which tells us our throughput in lag and latency."
"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."
"The flexibility in solving job scheduling challenges allows us to successfully integrate an acquired business’ fiscal close with our own, even though there is a lot of variance as to when they run in the calendar month."
"The most valuable feature is the easily accessible data in the database because we run a lot of SQL scripting against the database."
"We looked at other companies, like VisualCron, that were cheaper, but one of the main sticking points was the fact that they wouldn't have provided a central location for us to monitor across all servers. That was one of the biggest selling points of JAMS."
"I find the historical tracking feature of JAMS invaluable for reviewing past events."
"It has definitely drastically improved our capabilities to scale our automation. Before JAMS, there were a lot of manual processes. We had a couple of operators who spent all day doing that. A lot of the time with human intervention and human processes, it is as good as the person who may be following a procedure and human error is a big problem."
"The fact that we no longer need to use Excel spreadsheets is huge. Before JAMS, every group was keeping track of their own batch jobs. Nobody really knew what the other jobs were. So, if jobs failed, other groups wouldn't necessarily know. With JAMS, everything is done through a single scheduler. You can choose who to notify."
"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."
 

Cons

"We have to escalate through channels to get to somebody who knows what's going on. It takes time that we do not necessarily have.​"
"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."
"It lacks support and integration with cloud computing platforms."
"There is a slow response time by tech support. Unless, you say it's severity level one. That will give you a two hour timing window for them to call you. It doesn't really happen exactly in two hours, but they try."
"Reduce the number of operational files. This would make the job of a system programmer supporting ESP easier."
"It would be helpful to be able to monitor and manage workload windows so we could minimize downstream applications. This would allow us easier access to the applications."
"I would like to see the Service Orchestrator, a B2B product, and maybe a process audit."
"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."
"The ACL or access permission area needs to be improved. When it comes to defining and providing security permissions, it's a bit confusing if you are new to JAMS. JAMS needs to improve the features for security access or permissions."
"When looking at a folder in JAMS with many jobs, it would be good to have better information in the list display of what's inside those jobs. We get some information, but other important details are missing."
"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."
"With no programming experience, I find JAMS code-driven automation challenging due to the required PowerShell scripting."
"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 has built-in reporting. I've never really used it. I tried using it a few years ago and I couldn't figure it out. It was wonky. It could be improved upon."
"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."
"As an admin, I would like to have a web-based GUI instead of a client application that we have to install on our PCs."
 

Pricing and Cost Advice

"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."
"There is an annual license to use AutoSys Workload Automation."
"We paid to use the solution monthly."
"CA pricing has been a problem, and not looked upon favorably here at all."
"I certainly think the pricing is worth the value."
"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."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"The pricing is reasonable."
"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."
"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."
"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"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."
"The product is reasonably priced, and we don't have any add-ons."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
845,040 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
48%
Manufacturing Company
10%
Computer Software Company
6%
Insurance Company
5%
Computer Software Company
15%
Financial Services Firm
15%
Manufacturing Company
9%
Healthcare Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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 because nothing gets left unattended since it is all visible in one place, and th...
What do you like most about AutoSys Workload Automation?
The most valuable aspects of AutoSys Workload Automation are its performance, scalability, and ease of getting started for new users.
What is your experience regarding pricing and costs for AutoSys Workload Automation?
The solution is costly. The pricing is based on the number of users, which for me, translates to approximately $120,000 to $130,000 for a license period of two to three years.
What do you like most about JAMS?
I find the historical tracking feature of JAMS invaluable for reviewing past events.
What is your experience regarding pricing and costs for JAMS?
Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra. Previously, both Help Systems and MVP offered more favorable pricing and licensing terms. However, Fo...
What needs improvement with JAMS?
The monitoring of the JAMS product and its performance is an area of concern for me. I also need better tools to adopt version seven. Another area for improvement would be the addition of source co...
 

Also Known As

CA Workload Automation, CA Workload Automation AE
No data available
 

Overview

 

Sample Customers

Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Find out what your peers are saying about AutoSys Workload Automation vs. JAMS and other solutions. Updated: March 2025.
845,040 professionals have used our research since 2012.