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.6
Number of Reviews
42
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 May 2026, in the Workload Automation category, the mindshare of JAMS is 3.0%, up from 1.9% compared to the previous year. The mindshare of IBM Workload Automation is 4.4%, down from 6.9% compared to the previous year. The mindshare of Tidal by Redwood is 4.1%, up from 3.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS3.0%
IBM Workload Automation4.4%
Tidal by Redwood4.1%
Other88.5%
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.
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

"Our company is based on data. Everything we do is data-driven, so it has been very valuable having one place where we can process all of the data and do batch schedules with chunks of data."
"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."
"JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful."
"The most valuable feature for us is that it's DR-ready. With respect to disaster recovery, it has the built-in capability for failover to our DR site. If all of the required ports are open, it can be done seamlessly."
"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
"The scheduling and execution of jobs are the most valuable features. The scheduling is important because if there is a task we want to execute at 4:00 AM, there's no way we will have someone who can manually run the job. In addition, we execute 100 to 200 jobs per day, and manual intervention is not an option."
"Fortra's JAMS helped us centralize job management across our platforms and applications. This is critical because we schedule tasks across multiple applications and operating systems, using triggers and start dates to coordinate their execution."
"The most valuable aspect of JAMS is its robustness."
"Tivoli consistently runs jobs as scheduled and precisely as defined."
"The most valuable feature of IBM Workload Automation is its holistic view, which helps me find technical solutions quickly. For instance, if a customer has an issue completing their workload within a specific time frame, the tool provides enough information to identify and resolve the issue. One of the main challenges is dealing with data infrastructure problems and pending updates. Workload Automation helps me leverage current AI capabilities to recommend architectural updates to avoid these issues. It also allows me to balance CPU usage effectively, ensuring service level agreements are met. The interface is user-friendly and facilitates this process smoothly."
"The initial setup is easy."
"I recommend IBM Workload Automation as it's a well-established and stable product."
"Having used all of the major WLA platforms, I believe: IWA is the most user-friendly and feature-packed product on the market today."
"It offers features like MDM and a Windows workstation, although there are some technical dependencies. It is more user-friendly and also includes failover and failback capabilities. While both systems offer high availability, Control-M's high availability is superior to AWS's."
"The solution helps automate processes so that the workload can be handled on a daily basis."
"Real-time database updating is less time consuming because you do not have to upload and download changes or turn the job on, as you can simply leave it off the schedule until it is needed and give it a first-run date."
"Having a single pane of glass, regardless of which technology we're talking about has been great."
"The first, big thing that we got out of using Tidal Workload Automation was having a centralized view of the status of all of our batch processes across all these systems... We can look into the schedule at any given time and see if things are running on track or if they are falling behind. We can also see if something failed."
"Overall, it does what it's supposed to do."
"Tidal Automation offers extensive monitoring and reporting features that let users keep track of the status of their workflows and quickly spot any problems."
"We had a number of different schedulers in this organization and we've been porting everything that was running out of these other, unrelated schedulers into this scheduler. That has afforded us the ability to set up direct dependencies between processes that couldn't talk to one another before. Over the 15 years, we've definitely gained a lot from that. What had been manual controls have become automated controls..."
"The Graphical Views feature is also very good for helping us to understand a job stream. It's great for providing a visual overview of the status of a workflow, especially the Critical Path view. That is one of our favorites."
"The most valuable feature is the job scheduler, where you can schedule thousands of jobs to execute at specific times."
"With the varied features in the varied adapters provided, we use Tidal Enterprise Scheduler because we want everything to be scheduled in one place."
 

Cons

"JAMS handles exceptions fairly well but there are some areas where it might improve a little bit. It has to do with being able to automatically handle exceptions, out-of-the-box, rather than having to code them."
"The JAMS automation code isn't so clean."
"I want JAMS to implement a global search function."
"If there were a softcover book on how to really take advantage of all of JAMS' tools, I would buy it. I do better with training books than online searching, so a book would be helpful."
"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."
"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."
"JAMS handles exceptions fairly well but there are some areas where it might improve a little bit. It has to do with being able to automatically handle exceptions, out-of-the-box, rather than having to code them."
"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."
"ROI seems very low and rate of realization is too slow for simple networks."
"Control-M had a far superior user interface and also had a notification system which TWS lacked."
"It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
"IBM needs to move away from its native terminology and adopt a more cloud-centric approach."
"Out of the box reporting and provision for customization/integration with other products are the areas where this product can be improved."
"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."
"IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly, and a lower cost would be beneficial."
"A lot of the automation that we added to the product should come built into it, so that every customer doesn't have to reinvent the wheel."
"I would like more involvement with the cloud."
"With the client, we have had certain issues. The user interface for Tidal is a little slow. A lot of people would love this tool if they had a faster user interface. The drill-down functionality should be much quicker than what it is pulling out now. If I fill out some data, then it takes awhile to get that data back onto the screen. It's not as fast as we were expecting."
"I don't know if Tidal wants to get into the business of monitoring long-running jobs, but that could be a feature for the future: a job launching and monitoring tool. Using Tidal for monitoring doesn't seem like a good fit, but if they could offer something that did that as an add-on or include it, it might be helpful."
"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."
"My complaint about their pricing model is that every year or every time technology changes or somebody has a new requirement, it usually means that I can schedule that with Tidal, but I would need another adapter. So, every time there is a change, I need a different adapter that I don't have. That's why it is harder to plan for Tidal growth because you have to buy a new adapter every time."
"The product’s UI is outdated. They should work on this particular area."
"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."
"Setting up the initial product was a little hard."
 

Pricing and Cost Advice

"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 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."
"This is a good product at a fair price."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"The product is reasonably priced, and we don't have any add-ons."
"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."
"I haven't been involved in the financial side for several years, but we buy one host and unlimited agents, and we get a reasonable price for that. We're happy with the amount we pay and the scalability it provides."
"To my knowledge, IWA is the only WLA product that will provide "parallel tracking" capability to assist in upgrading from one platform to IWA."
"The solution's pricing is affordable."
"It is about one-third of the cost of a controller."
"We transitioned from a server license to per job license, and that saved us a lot money."
"The contract is with the customer with whom we are working, so IBM is not directly involved in this."
"Pricing depends on the number of agents that you install."
"The solution is a little bit expensive."
"This solution is a bit expensive in the current world where everybody is trying to cut down on certain things."
"There have been pricing increases, but with the reduction that our company obtained from Tidal this year, the pricing has become very acceptable for this type of product."
"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."
"We are satisfied with the pricing of Tidal. It's in the moderate range and it feels very achievable for us."
"Our licensing model for Tidal is on an annual basis. It is very good and works well for us. Tidal's licensing is very transparent and simple. It lets you know, for the amount you use, that's the price that you pay. So, we buy X number of licenses, and we know that this is where we are. I'm very happy with that. I saw the licensing modules on other platforms, and I didn't like them. Other companies and solutions would calculate the connections, adapters, and instances. I think that's the reason that BMC was pretty expensive: They just didn't understand what our needs are."
"BMC is really expensive. The other solutions are about the same price. I think Tidal is even cheaper than the others, such as CA, Stonebranch, and JAMS."
"We think the pricing is very fair. We have been happy with the pricing compared to some of the other solutions in the space."
"The new prices that we've received seem reasonable and comparable to the marketplace."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
893,221 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
12%
Manufacturing Company
8%
Healthcare Company
6%
Financial Services Firm
25%
Retailer
7%
Manufacturing Company
6%
Government
5%
Financial Services Firm
18%
Manufacturing Company
8%
Performing Arts
7%
Construction Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise13
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?
I believe the pricing and licensing were fair. I was not here when that process took place and do not know exactly, b...
What needs improvement with JAMS?
When it comes to improvements for JAMS, I think upgrading and migrating some of the current processes could benefit f...
What is your primary use case for JAMS?
Our main use case for JAMS is to automate our data pump backups for our PeopleSoft Oracle system, as well as run a my...
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.
893,221 professionals have used our research since 2012.