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

IBM Workload Automation vs Tidal by Redwood comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 15, 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

IBM Workload Automation
Ranking in Workload Automation
11th
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
12th
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 July 2025, in the Workload Automation category, the mindshare of IBM Workload Automation is 6.8%, down from 8.2% compared to the previous year. The mindshare of Tidal by Redwood is 4.2%, up from 3.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation
 

Featured Reviews

Ilhami Arikan - PeerSpot reviewer
With an easy setup phase in place, agent-based installation can be done in minutes
Sometimes we have issues with the solution's stability. So, stability can be improved. Reporting and visibility of the solution need improvement. These days, we need more visibility. We need to access the logs and databases easily. You need to keep track of the running number of logs, like which ones are executed, completed, etc. So if there would be a good reporting dashboard, then it would be good. There's room for improvement in the solution since it is a challenging thing when we want to use the solution's technology with our new technologies. For example, if we need to use TWS on our OpenShift platform, the solution's API is not capable enough. So the product itself needs to be aligned with new technologies.
Steve Mikula - PeerSpot reviewer
Very reliable processing engine, and scheduling is flawless—crucial elements in our financial transaction processing
Because we've been on it for 20 years, it's pretty easy for us to automate jobs with Tidal at this point. It has become second nature. It's pretty simplistic to set up and get going, although there are different levels of complexity you can have within the product. It depends on how simple you want to keep it. If you just keep it: Job A, Job B, Job C, Job D, that becomes pretty simple. But when you start integrating some complex calendars that use sub-calendars—and you can go three, four, or five deep to set up schedules—it becomes more complicated. The beauty of it is you can go as deep as you need to. We can get really complex or we can keep it simple. We have some use cases for both scenarios. 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. We are a financial company, we move billions of dollars a day, and if we don't have our transactions processed in a timely manner we can be penalized and our clients can be penalized. It can have a serious financial impact.

Quotes from Members

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

Pros

"Provides a robust, full spectrum enterprise-wide WLA platform."
"The DWC, when configured correctly, is a great GUI tool to provide Self-Service Scheduling capabilities to the user community."
"I have supported this product in literally 100s of different environments and its unmatched in its ability to scale to any size."
"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."
"Jobs can be triggered in multiple nodes."
"This solution has a request feature where users can request the added features they need to have developed. Based on client voting for those features, these are developed and released."
"With the varied features in the varied adapters provided, we use Tidal Enterprise Scheduler because we want everything to be scheduled in one place. Tidal provides that for us with its tools and varying platforms in our organization. Tidal provides all the connectors to the platforms. This is very useful because we don't want to look for another scheduler for scheduling certain jobs. We don't want to look at those schedules manually between platforms."
"The best feature is that it allows task scheduling based on particular occurrences, like the receipt of files, database updates, or system notifications."
"It is intended to enable large-scale automation environments, making it appropriate for companies with complicated processes and big data volumes."
"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."
"It's the most efficient tool in doing repetitive tasks and saves a lot of time with minimum possibility of error."
"Tidal Automation’s most valuable feature is customization. It can work and connect with any app."
"It's easy to use and easy to administer, and it's very flexible."
"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."
 

Cons

"The solution should offer more free technical sessions to customers so that they can gain more experience or learn more about how to use it."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"The performance of the previous versions could be better."
"IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly, and a lower cost would be beneficial."
"The solution's installation could be improved because the customers have to do it all the time."
"Scalability-wise, it can be a little bit challenging."
"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."
"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."
"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 current user interface of Tidal Software is functional. However, it can be improved to make it more intuitive and user-friendly."
"To better fit their unique needs, the solution should give more customization options."
"When we patch to the next version, there is often a little thing that breaks. It has rarely been a big deal, but I always seem to have to follow up on one tiny issue. It would help if they had some better QA testing of their patches."
"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."
"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."
"The job failure alerts can be updated with more details for better troubleshooting."
"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."
 

Pricing and Cost Advice

"It is about one-third of the cost of a controller."
"The solution's pricing is affordable."
"Pricing depends on the number of agents that you install."
"We transitioned from a server license to per job license, and that saved us a lot money."
"The solution is a little bit expensive."
"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."
"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."
"This solution is a bit expensive in the current world where everybody is trying to cut down on certain things."
"The price is reasonable in terms of the product’s functionality."
"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’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."
"We think the pricing is very fair. We have been happy with the pricing compared to some of the other solutions in the space."
"...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."
"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."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
861,390 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
31%
Computer Software Company
10%
Retailer
7%
Manufacturing Company
7%
Financial Services Firm
19%
Manufacturing Company
12%
Computer Software Company
10%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with IBM Workload Automation?
IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly, and a lower cost would be beneficial.
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 application servers and use scheduling to trigger jobs on other servers. Our us...
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. The product features a master-slave setup that ensures continuity during failures....
What do you like most about Tidal Automation?
Tidal Automation by Redwood is a user-friendly solution.
What is your experience regarding pricing and costs for Tidal Automation?
The price is reasonable in terms of the product’s functionality.
What needs improvement with Tidal Automation?
Initially, it is complicated to understand the functionalities as there is limited product documentation. The setup and configuration of the software is a bit complicated. Providing the training vi...
 

Also Known As

IBM Tivoli Workload Scheduler, IBM TWS
Tidal Workload Automation, Cisco Workload Automation, Tidal Enterprise Scheduler
 

Overview

 

Sample Customers

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: June 2025.
861,390 professionals have used our research since 2012.