We performed a comparison between Automic Workload Automation and Tidal Automation based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: Automic Workload Automation is highly valued for its strong performance, ability to handle large workloads, and user-friendly implementation. It provides comprehensive control over various systems and products. Tidal Automation is particularly praised for its efficient job scheduler and advanced real-time monitoring features.
Automic could enhance its out-of-box automation sets, language support, functionality, user interface, web-based edition features, file transfer management, pricing, and SaaS deployment. Tidal could benefit from improvements in its graphical user interface, pricing model, cloud/hybrid solution, QA testing, job migration, reporting, artificial intelligence capabilities, integration, and user-friendliness.
Service and Support: Automic Workload Automation's customer service has received varied feedback, with some customers appreciating prompt responses and useful knowledge articles, while others have encountered challenges in contacting the support team. Tidal Automation's customer service is highly regarded for its responsiveness, expertise, and consistent resolution of issues.
Ease of Deployment: Automic's initial setup duration and complexity can differ, lasting anywhere from one to five days based on the project scale and implementation. Tidal Automation's initial setup is described as simple and effortless, necessitating approximately three weeks along with a few servers and a database.
Pricing: Automic Workload Automation and Tidal Automation were compared for their setup cost. Users found Automic Workload Automation to be more cost-effective and user-friendly compared to Tidal Automation. They praised Automic for its efficiency in setting up automation processes without incurring excessive expenses.
ROI: Automic Workload Automation is seen as an added cost without clear ROI figures, while Tidal Automation has demonstrated positive ROI through cost savings, enhanced efficiency, and better risk management. Tidal Automation also excels in seamless integration and fulfilling automation needs.
Comparison Results: Tidal Automation emerges as the preferred choice compared to Automic Workload Automation. The setup process for Tidal Automation is described as straightforward and easy, taking approximately three weeks, whereas Automic's setup can take anywhere from one to five days. Users highly appreciate Tidal Automation's job scheduler and single pane of glass interface, which make workload management and monitoring simple.
"The ability to be able to automate more of our business processes."
"I use this automation solution, because it is very flexible. This automation solution supports a lot of computer platforms. Also, a lot of operating systems are supported other than automation solutions."
"It is the automation. Saving time and money is the key. We automate everything."
"Being able to script, create something I want the software to do for a specific job. This allows me to do that. Very powerful."
"They just talked about adding support for hundreds of thousands of agents, and I know it goes up to about a thousand clients per engine, so you can do a lot with that. It's a very scalable solution."
"The most valuable feature is the one for SAP batch processing... There are certain other mid-level workload automation tools which can handle the OS level, but SAP is something which is really very critical. Automic stands out from the ordinary tools because handling SAP processes is absolutely easy with it."
"We do not have to use a broad variety of agents to connect to different types of systems."
"We have a lot of governance and compliance requirements as a bank that we can fulfill with this product."
"Tidal Automation by Redwood is a user-friendly solution."
"The best feature of Tidal Workload Automation Software is its ease of integration with other systems, including ERP, CRM, and BI tools."
"It's the most efficient tool in doing repetitive tasks and saves a lot of time with minimum possibility of error."
"We use the solution for cross-platform and cross-application workloads. That's one of the core reasons we chose it. It's one of a few things in the industry that can be used for cross-platform integration."
"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. It is that critical. So, it's an essential tool for us to manage and run SAP jobs."
"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."
"We use the solution for cross-platform, cross-application workloads. That's the biggest use for us and that's the biggest advantage."
"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."
"I would also like to see a little bit more connectivity, more, "Play nice with other toys." For instance, we have IServ as our primary tool for our service request tickets. In order for it to play nice with Automic, we had to actually create a file and put it somewhere, where Automic can see it. I would like to see more connectivity with other tools, or more compatibility with other tools."
"An area for improvement would be SQL performance. While tracing SQL traffic, we noticed a lot of commands that cause contention/locks as well as forced waits. The efficiency of the SQL could be greatly improved (in some cases by simply replacing nested Selects and using NOLOCK hints)."
"It would be better if it was easier to view the automated processes."
"When you want to use the entirety of Automic, it is heavy."
"Today, we use a rich client for this product. In the future, or for the next release, they will be using a web interface. This web interface is not as scalable as the rich client for us. The web client is not 100 percent programmed as we need it."
"Automic Workload Automation could improve the SaaS deployment."
"We would like to have token-based authentication. Where we do not have to use a password, and can use tokens for authentication in other systems."
"I would like more training on workload automation, because I do not have a complete insight of the product yet."
"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. We have to go all the way back to the dependencies and then we can see that one of the dependencies has become unscheduled, for some reason. No changes were made to the schedule but this prerequisite job has, all of a sudden, become unscheduled. I have brought this up with Tidal's support but they have never had an answer for it."
"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."
"Tidal's adaptability and user-friendliness could be increased by integrating it with additional programmes and platforms."
"They can do better reporting in terms of production statistics reporting."
"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."
"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."
"Setting up the initial product was a little hard."
Automic Workload Automation is ranked 7th in Workload Automation with 85 reviews while Tidal by Redwood is ranked 2nd in Workload Automation with 37 reviews. Automic Workload Automation is rated 8.2, while Tidal by Redwood is rated 9.0. The top reviewer of Automic Workload Automation writes "A tool requiring an easy setup phase that provides its users with flexibility and flow chart visibility ". On the other hand, the top reviewer of Tidal by Redwood writes "Great visibility with a single pane of glass and a low learning curve". Automic Workload Automation is most compared with Control-M, AutoSys Workload Automation, Red Hat Ansible Automation Platform, Dollar Universe Workload Automation and MOVEit, whereas Tidal by Redwood is most compared with Control-M, AutoSys Workload Automation, IBM Workload Automation, Redwood RunMyJobs and Fortra's JAMS. See our Automic Workload Automation vs. Tidal by Redwood report.
See our list of best Workload Automation vendors.
We monitor all Workload Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.