IBM Workload Automation vs Tidal by Redwood comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jul 12, 2023
 

Categories and Ranking

IBM Workload Automation
Ranking in Workload Automation
14th
Average Rating
8.2
Number of Reviews
28
Ranking in other categories
No ranking in other categories
Tidal by Redwood
Ranking in Workload Automation
2nd
Average Rating
9.0
Number of Reviews
37
Ranking in other categories
No ranking in other categories
 

Market share comparison

As of June 2024, in the Workload Automation category, the market share of IBM Workload Automation is 7.5% and it decreased by 14.7% compared to the previous year. The market share of Tidal by Redwood is 5.1% and it decreased by 0.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation
Unique Categories:
No other categories found
No other categories found
 

Featured Reviews

SR
Feb 13, 2023
Great ability to pre-schedule jobs but unfortunately the simulation is complicated
We use this product for batch processing. We have hundreds of users and carry out 25,000-30,000 jobs per day The solution has helped us because we have multiple node servers and the workload is distributed between them. The key valuable feature is that jobs can be triggered in multiple nodes.…
KK
Apr 26, 2023
Good data management with useful backup and storage capabilities
Tidal Automation actually helps a lot to improve overall SLA breaching (in percentage). We can easily maintain the incidents in SLA as it was triggering alerts. It allowed us to see the priorities so that the team could easily work on those alerts in a timely fashion. Also, server data visualization is much easier and helps to identify the capability and extended the resources to help scale up the project accordingly. This scaling was possible thanks to the Tidal Automation tool. It makes work easy and fast. There is no need to add more engineers to each shift. In the end, fewer resources could handle things with Tidal.

Quotes from Members

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

Pros

"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 support from Cisco is very good. I was with them as a company for 40 years"
"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."
"The initial setup is easy."
"Jobs can be triggered in multiple nodes."
"Technical support from IBM is very good."
"The DWC, when configured correctly, is a great GUI tool to provide Self-Service Scheduling capabilities to the user community."
"Jobs can be triggered in multiple nodes."
"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."
"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."
"Tidal Automation is very efficient and can quickly automate most manual and repetitive tasks."
"It's the most efficient tool in doing repetitive tasks and saves a lot of time with minimum possibility of error."
"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."
"By leveraging machine learning algorithms, Tidal Automation can use this data to optimize turbine settings and improve overall efficiency and performance."
"We use the solution for cross-platform, cross-application workloads. That's the biggest use for us and that's the biggest advantage."
"We have to run about 12,000 jobs every day and the majority of them need to be launched from our ERP, JD Edwards. The native compatibility of the Tidal platform with JD Edwards dovetails with our greatest need. It's directly connected to the heart of our IT system. We couldn't work without it."
 

Cons

"It should support other schedulers that aren't IBM products."
"Scalability-wise, it can be a little bit challenging."
"This solution does have bugs and could be improved in this regard. However, these bugs are resolved relatively quickly."
"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."
"The schedule refreshes daily and that's a challenge for us."
"The performance of the previous versions could be better."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"Tidal Software interface could be more intuitive and user-friendly."
"The product’s UI is outdated. They should work on this particular area."
"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."
"The GUI, the graphical user interface, gets a little bit busy."
"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."
"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."
"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."
"The job failure alerts can be updated with more details for better troubleshooting."
 

Pricing and Cost Advice

"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."
"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."
"Pricing depends on the number of agents that you install."
"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 pricing is pretty reasonable. That seems to help a lot versus other companies. There are no other fees aside from the standard licensing fees. There are other products out there where you pay based on how many jobs you run and so on, and I know that's very frustrating for users."
"Right now, we are in a good position with the licensing model that we have with the Tidal vendor. So, we won't have any issues. even if we double in our current production. Initially, Tidal provided us some specs where if you have these number of jobs, then you come under this category. They usually provide a range of jobs from 2,000 to 10,000. You can use these specs for your infrastructure. Whether you have 2,000 or 8,000 jobs, Tidal should support it."
"Tidal is a low-cost tool and not expensive in comparison to other tools."
"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."
"I have had no issues with the licensing."
"If you are willing to shop around to other vendors, you can possibly get a good price on your support license."
"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.
787,061 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
33%
Computer Software Company
9%
Insurance Company
8%
Manufacturing Company
8%
Manufacturing Company
21%
Financial Services Firm
20%
Computer Software Company
9%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with IBM Workload Automation?
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 acc...
What is your primary use case for IBM Workload Automation?
We are using IBM Workload Automation to run batch operations. The development teams batches, and the team that makes a plan and schedules the batches to be executed, and keep track of the summary o...
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
 

Learn More

Video not available
 

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 2024.
787,061 professionals have used our research since 2012.