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

IBM Workload Automation vs Tidal by Redwood 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.7
Number of Reviews
39
Ranking in other categories
No ranking in other categories
IBM Workload Automation
Ranking in Workload Automation
8th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
33
Ranking in other categories
No ranking in other categories
Tidal by Redwood
Ranking in Workload Automation
19th
Average Rating
9.0
Reviews Sentiment
7.2
Number of Reviews
37
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2026, in the Workload Automation category, the mindshare of JAMS is 2.7%, up from 1.7% compared to the previous year. The mindshare of IBM Workload Automation is 4.3%, down from 7.2% compared to the previous year. The mindshare of Tidal by Redwood is 4.3%, up from 3.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS2.7%
IBM Workload Automation4.3%
Tidal by Redwood4.3%
Other88.7%
Workload Automation
 

Featured Reviews

reviewer2770605 - PeerSpot reviewer
Cloud Engineer at a financial services firm with 501-1,000 employees
Has streamlined complex job scheduling across scripting languages while reducing manual effort
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. A functionality running on the JAMS server to continuously check the JAMS agents would ensure they are working properly. If an agent is not responding, a feature to restart the service from the job server machine would be beneficial. The upgrade process, particularly when switching from V6 to V7, could be clearer in terms of documentation, ideally with screenshots showing exactly what needs to be done on each screen.
reviewer2701716 - PeerSpot reviewer
Technical Lead at a financial services firm with 1,001-5,000 employees
Dynamic workload balancing facilitates efficient job scheduling and ensures continuity with a master-slave setup
One valuable feature of IBM Workload Automation is the ability to combine different applications and platforms to organize jobs together, creating dependencies. It's akin to an orchestra. Another feature is dynamic workload balancing, which I find enhances efficiency by automating job setup to run daily. Moreover, having a backup setup allows for immediate recovery if the master setup fails.
JG
Batch Production Manager at a consultancy with 201-500 employees
Its versatility, ease of use, scalability, and cost-effectiveness make it a 10/10 and the best of the breed
The company is not really big. One of the areas that they are working on is improving the process of migrating jobs from the lower environment to the upper environment. They had used a tool called Transporter, which was a little difficult to use, but they've now released a new tool in August, which I've not yet used, to do that. It's probably called Repository or something like that, but it's a tool for migrating jobs from the lower environment to the upper environment. That's where they needed to improve, and it looks like they may have, but I haven't tried the tool yet. They can do better reporting in terms of production statistics reporting.

Quotes from Members

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

Pros

"The planning capabilities are most valuable."
"The overall product is fantastic. I love it. It has been a fantastic, solid product. If I have one tiny bit of a problem with it, the support team gets in touch with me right away. I don't know if I've had another service that has been as fantastic as the JAMS support team."
"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."
"The most valuable aspect of JAMS is its robustness."
"What my team needs are tools to reliably execute all the jobs, minimize the risks, and support high-availability, and JAMS does the job."
"The interface is good, and it's very easy to define and create jobs. If a job is not running or there is an error, the solution will send an email. That's all very good and very useful."
"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."
"JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
"The technical support is great, the product is easy-to-use, and it is stable."
"The project we worked on involved the running of nearly 24,000 job instances in a single day, so I would say that the solution is stable."
"The whole product is valuable because it is a tool for batch automation."
"It has definitely improved many different processes in our organization."
"Technical support from IBM is very good."
"The support from Cisco is very good. I was with them as a company for 40 years"
"The project we worked on involved the running of nearly 24,000 job instances in a single day, so I would say that the solution is stable."
"Jobs can be triggered in multiple nodes."
"We use the solution for cross-platform, cross-application workloads. The solution’s ability to manage and monitor these workloads is very easy and accurate. We have file dependencies for running jobs. The job does not start until a file exists on a completely different server, then where the job will run. So, it is cross systems."
"I like the fact that I have control, and I am able to monitor. If there is an issue, I would be able to respond to any jobs that may fail. With any other scheduler that I know of, a lot of times, when I have a very complex script, if there is an issue in the middle of it, I have to let the whole process fail and then figure out a way to recover from it, whereas Tidal will stop the process, and I can resolve that issue. Once I resolve the issue, I can continue the process. This is very important for invoicing, accounts payable, accounts receivable, or any kind of financial reporting. It allows you to recover from an issue much more effectively than anything else that I have seen."
"Tidal Automation’s most valuable feature is customization. It can work and connect with any app."
"The data management on offer was valuable."
"I've used it at six different companies, and to me, it's the most versatile, easy to use, and dependable."
"Thinking of all the people involved in checking jobs on a daily basis, manually running jobs or auditing them through standalone tools, and trying to connect them, we have saved hundreds of hours weekly, which is substantial."
"Our implementation has been super stable, and it really kind of ticks all of the boxes."
"The thing that I like the most is the reliability of the engine. The actual scheduling part of the product is pretty much flawless, but the stability of the product is what I find to be reassuring."
 

Cons

"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."
"I'm not sure if they have fixed it in a newer version, but there is no global search in the version I have. If I have multiple sub-folders that are named for business units, like HR or IT, and I have to search for a job, I cannot search from the top. I have to go to the HR folder to search for a particular job, or to the IT folder."
"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."
"The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back."
"The documentation is not super... It's not as quick and slick as I'd like it to be."
"All my machines at work are Macs. JAMS client is a Windows-based thing."
"The product does not allow the users to cut and paste the job names from the screen."
"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."
"TWS lacks sophisticated predictive analytics capability. The limited analytics it does offer is predicated on user-defined variables such as job run duration estimates, which if miscalculated render outputs unreliable."
"It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
"This solution does have bugs and could be improved in this regard."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"Slow down on the releases a bit. I fully understand that IWA functionality is increasing at an amazing rate, but trying to keep up with the upgrades is rough."
"IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly, and a lower cost would be beneficial."
"There were real stability issues. The WebSphere process gets hung on TWS masters running TWS 9.1."
"I think that is a good and modern development, but the first v9.x releases (and maybe also the latest, I don’t know) lacked the event-driver WLA functionality that was already available for years in older on-prem versions of the product."
"One area for improvement is the command-line interface and the API to bulk-load jobs. It's a little bit kludgy, but we still manage without it. They're working on it and it's getting better all the time. In addition, the documentation for their API for creating jobs needs to be updated. It's a bit of a learning curve."
"Tidal's adaptability and user-friendliness could be increased by integrating it with additional programmes and platforms."
"Understanding and using Tidal Automation could be overwhelming for someone with minimal programming language."
"One of the weaknesses of the product is, when something happens, it's difficult to find out the root cause. There are a lot of logs you can take a look at in Tidal. Sometimes, they are useful, but other times, they're not. That is mostly relegated to the administrative team. Users for the most part don't see that and don't know anything about that. They just know they have a problem, then it's up to the administrative team to see what happened and figure out the problem."
"There are several improvement points that our team has provided to the vendor."
"From an administrative point of view, I wouldn't give really high marks to the solution. I actually entertained getting the JAWS application at one point. One of the shortcomings with the scheduler is the reporting capabilities. At least at the time, JAWS was the best that they had for a third-party integration. I think they've got things in the pipeline to help alleviate that gap."
"The software's performance and scalability could be improved, particularly when dealing with large-scale workloads or complex business processes."
"Tidal Automation could be further integrated with other systems used in the operation of tidal energy systems, such as weather forecasting tools, energy management systems, or asset management software."
 

Pricing and Cost Advice

"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'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."
"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."
"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"This is a good product at a fair price."
"There are no additional costs other than the license for Fortra's JAMS which is affordable."
"The pricing is reasonable."
"It's expensive, to be honest, but it does the job."
"We transitioned from a server license to per job license, and that saved us a lot money."
"The solution's pricing is affordable."
"To my knowledge, IWA is the only WLA product that will provide "parallel tracking" capability to assist in upgrading from one platform to IWA."
"It is about one-third of the cost of a controller."
"The contract is with the customer with whom we are working, so IBM is not directly involved in this."
"The solution is a little bit expensive."
"Pricing depends on the number of agents that you install."
"If you are willing to shop around to other vendors, you can possibly get a good price on your support license."
"The licensing model's flexibility is awesome. The way it's licensed for us is that it's licensed per master and then per agent. We have an enterprise agreement, so we have unlimited agents, and we have it on 500 devices."
"I have had no issues with the licensing."
"The solution’s licensing model in terms of its flexibility and transparency regarding costs is pretty good. A person can buy the license, and if you decide to stop support, you can do that but still have the product. So, it's not like you're paying constantly to keep that license alive. Certainly, you want to keep support going too. Once you buy it, you own it. It's not like I have to keep paying somebody to keep using it."
"Our yearly licensing costs are between $10,000 to $20,000. They have always been reasonable with us. I like that non-production licensing is about half the cost of production licensing. Licensing is by adapter typically. We have had scenarios where we have had to take an adapter from one environment to another, and they've allowed us to do that. They have made it a very reasonable process. There's definitely a feeling that they will work with you."
"The new prices that we've received seem reasonable and comparable to the marketplace."
"We pay maintenance annually through Blue House of about $9,000. That's for our two environments: production and test."
"This solution is a bit expensive in the current world where everybody is trying to cut down on certain things."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
886,976 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
13%
Manufacturing Company
8%
Computer Software Company
7%
Financial Services Firm
25%
Retailer
8%
Manufacturing Company
6%
Government
5%
Financial Services Firm
17%
Manufacturing Company
8%
Construction Company
8%
Performing Arts
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise10
Large Enterprise19
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise29
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise6
Large Enterprise38
 

Questions from the Community

What is your experience regarding pricing and costs for JAMS?
My thoughts on the pricing of JAMS are that I won't say it is cheap, but it is cost-efficient, and that should be acc...
What needs improvement with JAMS?
An area that has room for improvement is related to the AWS RDS and database part, where they said that is in progres...
What is your primary use case for JAMS?
My use case is in batch scheduling and managing the batch jobs.
What needs improvement with IBM Workload Automation?
IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly,...
What is your primary use case for IBM Workload Automation?
We use IBM Workload Automation ( /products/ibm-workload-automation-reviews ) as a scheduler. We install agents on the...
What advice do you have for others considering IBM Workload Automation?
I recommend IBM Workload Automation as it's a well-established and stable product. However, the cost is a concern. Th...
Ask a question
Earn 20 points
 

Also Known As

No data available
IBM Tivoli Workload Scheduler, IBM TWS
Tidal Workload Automation, Cisco Workload Automation, Tidal Enterprise Scheduler
 

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
Standard Life Group, Banca Popolare di Milano, A*STAR, ArcelorMittal Gent
Information Not Available
Find out what your peers are saying about IBM Workload Automation vs. Tidal by Redwood and other solutions. Updated: April 2026.
886,976 professionals have used our research since 2012.