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
41
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

"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."
"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."
"The user-friendly and adaptable scheduler allows us to manage various scheduling scenarios."
"One of the things I like the most, as a SQL DBA, is the fact that we can manipulate tables in the background. Also, the fact that you can have your own views and work with the product the way it fits best is a very helpful feature."
"What my team needs are tools to reliably execute all the jobs, minimize the risks, and support high-availability, and JAMS does the job."
"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."
"JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
"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."
"I did not encounter any stability issues; it has been a very stable and reliable product."
"Provides a robust, full spectrum enterprise-wide WLA platform."
"The whole product is valuable because it is a tool for batch automation."
"The API is a valuable feature as it allowed us to integrate the inventory, change and ticketing systems to fully automate most of the monitoring processes for new devices, decommissioned devices and during approved changes."
"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 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."
"I would recommend other users to definitely consider TWS, as it has proven to be a powerful tool in our environment so far."
"Automation capabilities with dependencies, long-term plan and modifying current plan, and ease of use are the product's most valuable features to me."
"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."
"What had been manual controls have become automated controls, by using this tool to replace a number of schedulers."
"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."
"Especially in the newer versions of Tidal, the segmentation of user permissions enables us to give people operator permissions for their jobs, to rerun jobs, but view-only for other groups' jobs. We're able to keep people from hurting themselves or other groups accidentally. The permissioning is really good."
"You will enjoy the features of it; it is a great tool."
"The feature that I find to be valuable, as I'm working with other folks, is the ability to cross-schedule across platforms, and the flexibility that comes with that."
"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..."
"For our MRP job stream, if Tidal can just once prevent an MRP issue from happening or let us recover from an MRP issue quickly, it has paid for itself."
 

Cons

"I want JAMS to implement a global search function."
"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 knowledge was hard-won knowledge. It was difficult to come by, and if I should ever lose this developer, then I would be hard-pressed to find anyone who could create JAMS custom execution methods quite 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."
"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."
"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 monitoring of the JAMS product and its performance is an area of concern for me."
"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."
"For scalability, I would rate it as seven because when we have a huge volume, sometimes the tool is not so responsive."
"All my machines at work are Macs. JAMS client is a Windows-based thing."
"The interface for the operator is not so good."
"The solution's installation could be improved because the customers have to do it all the time."
"There should be more custom documentation, specifically around Java APIs. There should also be more training. In terms of features, we are currently using only 50% of its features. We don't use all features that are available, but there is always room for improvement in all of the tools."
"It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
"Out of the box reporting and provision for customization/integration with other products are the areas where this product can be improved."
"Customer service is 7/10; technical support is virtually impossible to get via direct phone call, as you have to rely on trouble tickets, wait several hours for a return call, and keep constant follow-up because your ticket can slip through the cracks and go unnoticed for days."
"It is complex to use Lacks scalability It is difficult to set up jobs to run"
"IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly, and a lower cost would be beneficial."
"I'm still hoping with Explorer to be able to see end-to-end job streams. That's not really something that's easy to see today in the web client. However, I haven't worked with Explorer yet. One of the things that we have found frustrating is not being able to see an end-to-end job stream across multiple applications within Tidal. We use jobs for that right now, but I have high hopes that we'll be able to see that in Explorer."
"The UI might have the potential to provide a more polished and user-centric encounter, promoting seamless engagements and simplifying the navigation process for individuals interacting with the software."
"For the most part, the drill-down and the logging are really good. But if we take an Informatica job, for example: We have the ability, and the operators have the ability, to actually drill down and see, at a session level, where the failure is. There is, unfortunately, no way to extract that into an actual output email or failure email. It's not that that information is not available, but extracting it into an email would be a nice-to-have."
"With the client, we have had certain issues. The user interface for Tidal is a little slow."
"I would like more involvement with the cloud."
"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."
"One thing I would like to see improved is that, currently, when an action is executed and finishes in Tidal, it's marked as either "success" or "failure." I would like more options that would flag a job according to multiple options, rather than just "good" or bad"... Tidal has told us that it's possible to do so through the product or with a workaround."
"Tidal's adaptability and user-friendliness could be increased by integrating it with additional programmes and platforms."
 

Pricing and Cost Advice

"It's expensive, to be honest, but it does the job."
"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."
"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."
"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 priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"The pricing is reasonable."
"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."
"The pricing of JAMS has not been an issue for us, as it has allowed us to save time."
"To my knowledge, IWA is the only WLA product that will provide "parallel tracking" capability to assist in upgrading from one platform to IWA."
"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."
"Pricing depends on the number of agents that you install."
"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."
"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 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."
"If you are willing to shop around to other vendors, you can possibly get a good price on your support license."
"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."
"We pay maintenance annually through Blue House of about $9,000. That's for our two environments: production and test."
"We are satisfied with the pricing of Tidal. It's in the moderate range and it feels very achievable for us."
"Tidal is a low-cost tool and not expensive in comparison to other tools."
"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."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
892,611 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
8%
Manufacturing Company
7%
Government
5%
Financial Services Firm
18%
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 Enterprise20
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.
892,611 professionals have used our research since 2012.