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

"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."
"The code-driven automation for more complex scheduling requirements frees up time because it's really easy to use... It's almost like a stand-alone software that we can't live without."
"The planning capabilities are most valuable."
"By using JAMS, my company has seen benefits such as getting to know about Google products and the latest features that are newly launched by Google, and they help me in building my projects portfolio and engaging with knowledge."
"The dashboard is intuitive."
"The feature or capability to import a job is most valuable. We can import an existing job from different platforms, and all the configurations get migrated as well without modifying the code, job schedule, etc."
"The built-in triggers are great."
"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."
"Jobs can be triggered in multiple nodes."
"It's very, very stable. The support is quite good."
"It's a very good scheduling product if you have a combination of mainframe and distributed environments that have batch operations and repetitive tasks running on them."
"The technical support is great, the product is easy-to-use, and it is stable."
"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."
"I did not encounter any stability issues; it has been a very stable and reliable product."
"Depending on that it may be interesting to use Tivoli because it is a good tool."
"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."
"We wouldn't be able to do many of the complex scheduling that we do today without it; for us, it is a mission-critical app because if it doesn't work or has a problem, then SAP doesn't function, so it's an essential tool for us to manage and run SAP jobs."
"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..."
"Overall, it does what it's supposed to do."
"It's pretty much a 24/7 operation in terms of uptime, and we've definitely used Tidal to meet that goal."
"The best feature is that it allows task scheduling based on particular occurrences, like the receipt of files, database updates, or system notifications."
"The job dependency is something that you cannot have in a regular, simple cron job or simple scheduler dependency. The event-driven jobs are core for us, as we really need that. Therefore, we really need Tidal with its ability to run thousands of jobs per day."
"It's the most efficient tool in doing repetitive tasks and saves a lot of time with minimum possibility of error."
"You will enjoy the features of it; it is a great tool."
 

Cons

"There could be a better simulation for banning the termination. You have to simulate every one of the processes in order to have an idea for better planning. This kind of simulation is broken and needs improvement."
"It is important to receive notifications if a charged job fails and SQL is halted. JAMS does not provide halted notifications by default, which is a critical feature that needs to be added."
"The documentation is not super... It's not as quick and slick as I'd like it to be."
"Fortra is getting much better with documentation and examples, but there is still room for improvement."
"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."
"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."
"For scalability, I would rate it as seven because when we have a huge volume, sometimes the tool is not so responsive."
"I would enhance the compatibility feature of JAMS because sometimes when the server is under high load, it does not inform us and we cannot get answers."
"This solution does have bugs and could be improved in this regard. However, these bugs are resolved relatively quickly."
"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."
"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."
"To improve IBM Workload Automation, I suggest enhancing automation features further, as more automation would be beneficial. The product is good enough for my current customers, but improving technical support and pricing would be welcome. We often need quicker responses and better solutions than we can manage manually. These improvements would make the product even better."
"One area of improvement is the user interface. While it is extremely functional, it’s not very user friendly and it’s difficult to visualize the flow of a complicated job schedule."
"IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly, and a lower cost would be beneficial."
"This solution does have bugs and could be improved in this regard."
"The GUI, the graphical user interface, gets a little bit busy. You have these flyouts that sometimes are a little tedious to get through."
"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 can do better reporting in terms of production statistics reporting."
"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."
"With the client, we have had certain issues. The user interface for Tidal is a little slow."
"Some users have complained that the initial setup process is complicated and time-consuming, while others have suggested that the software could offer more freedom in customizing processes."
"We've had some quirky stuff happen on an occasional basis where a job does not take off; for example, a job we expected to be finished by 3:00 a.m. is sitting there and not executing when we come in in the morning, and I have brought this up with Tidal's support but they have never had an answer for it."
"It takes a lot of time to learn the product. I have admins and developers who are working on the products for the last three to four years and still don't know all the functionalities."
 

Pricing and Cost Advice

"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."
"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."
"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."
"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."
"The pricing is very fair. We have seen very minimal to no price increases over the years. We are not banging down the door of support all the time either. I would imagine if we were a company that submitted a dozen support tickets a week for the last nine years, then it might be a little different because we would be eating up everybody's time. However, for what we get out of it, the pricing is extremely fair. Back when we were originally looking and brought in JAMS, we were looking at a couple of the other competitive products that were in this space, but the pricing from JAMS was far and away better than what the other competitors could offer for the same functionality."
"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."
"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"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 contract is with the customer with whom we are working, so IBM is not directly involved in this."
"We transitioned from a server license to per job license, and that saved us a lot money."
"The solution's pricing is affordable."
"It is about one-third of the cost of a controller."
"The solution is a little bit expensive."
"Pricing depends on the number of agents that you install."
"There are project, system, and server costs. Some of the things that they are doing is introducing new products. They are introducing what they call their Repository, which is a way for you to move a job. That doesn't cost anything to us, because it is reusing a tool called Transporter. The repository is the successor to Transporter, so we already own it and are sort of grandfathered in. But that new product requires a server and database, so now we have to go out and get a server and database. So, there is a cost there."
"The solution enables admins and users to see the information relevant to them, but this is bundled as an add-on that we would have to pay for."
"Tidal is a low-cost tool and not expensive in comparison to other tools."
"The new prices that we've received seem reasonable and comparable to the marketplace."
"Their pricing seems very fair. It is more than the other solutions, but the functionality and the support are very much there. You pay for the job scheduler, and then they have certain things that are built into it, such as the FTP processes. If you then want to do JD Edwards jobs, you need an adapter. If you want to do SQL jobs, there is another adapter. Similarly, if you want to do Oracle jobs, there is an adapter. It is like there is the base and then there are the adapters for the jobs that you want to do, but it seems that's also how they pay for each of those adapters and keep them up to date."
"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."
"I have had no issues with the licensing."
"...it is a pretty affordable scheduler tool that lets us do a lot. You get a lot of bang for the buck... The licensing model is hugely flexible."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
893,915 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
26%
Retailer
7%
Manufacturing Company
6%
Government
5%
Financial Services Firm
18%
Manufacturing Company
8%
Construction Company
7%
Performing Arts
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 Enterprise30
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,915 professionals have used our research since 2012.