We performed a comparison between AutoSys 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: AutoSys Workload Automation is highly regarded for its ability to handle large workloads, its user-friendly interface, efficient performance, and continuous availability. It particularly shines in efficiently managing job sequencing, executing real-time batch tasks, and seamlessly connecting various software processes. Tidal Automation distinguishes itself with its exceptional job scheduling capabilities, consolidated and intuitive interface, versatile job execution options, and seamless integration with different systems.
AutoSys needs enhancements in cloud service integration, reporting and performance comparison, Linux compatibility, migration capabilities, monitoring, advanced features, and workload window management. Tidal Automation would benefit from improvements in result interpretation, pricing model simplification, user interface, AI and machine learning capabilities, integration, job dependency management, security, performance and scalability, customization, collaboration, alerting configurations, and adaptability.
Service and Support: The customer service for Tidal Automation is commendable for its impressive product knowledge and willingness to assist with integration. However, there are occasional mentions of lower-priority items getting lost in the mix for Tidal Automation. AutoSys support is sufficient and capable with standardized approaches.
Ease of Deployment: The setup for AutoSys Workload Automation is described as quick and hassle-free, taking approximately 10 minutes or less. Tidal Automation's setup is easy and straightforward, however, it requires a significantly longer time of around three weeks to complete.
Pricing: AutoSys Workload Automation has a diverse range of setup costs, including a yearly subscription and an annual license. Tidal Automation is praised for its fair and predictable pricing, offering transparent licensing and the option for additional adapters to cater to specific job needs.
ROI: AutoSys Workload Automation offers benefits such as time savings, improved reliability, scalability, and enhanced visibility and control. Tidal Automation provides advantages like cost savings, increased efficiency, productivity, risk management, and seamless integration.
Comparison Results: AutoSys Workload Automation is the preferred choice when compared to Tidal Automation. Users appreciate AutoSys for its simple setup, scalability, user-friendly interface, and consistent availability. Its valuable features include file transfer protocol and file watcher. Additionally, AutoSys is commended for its reliability and promptness in executing tasks.
"This solution enables us to improve our daily processing times. We can do everything faster than before we used this solution."
"It can run an object on our Windows systems or our Unix systems, and then send messages to the other system when they are complete."
"The flexibility in solving job scheduling challenges allows us to successfully integrate an acquired business’ fiscal close with our own, even though there is a lot of variance as to when they run in the calendar month."
"Without this product we would have to manually submit jobs and it would take longer. There would also be a much greater possibility of jobs running wrong and/or not at the right time."
"AutoSys Workload Automation is a stable solution."
"To me, what's most valuable in AutoSys Workload Automation is its robustness and quickness. The tool can trigger jobs within a few milliseconds, and it can handle large volumes of jobs."
"Automation of patch process."
"It works constantly and is pretty seamless. You do not have to open up many support tickets."
"Thinking of all the people involved in checking jobs on a daily basis, manually running jobs or auditing them through standalone tools, and trying to connect them. We have saved hundreds of hours weekly, which is substantial."
"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."
"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."
"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. That's the biggest use for us and that's the biggest advantage."
"The Graphical Views feature is also very good for helping us to understand a job stream. It's great for providing a visual overview of the status of a workflow, especially the Critical Path view. That is one of our favorites."
"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."
"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..."
"Performance improvements in the UI would be appreciated."
"An area for improvement in AutoSys Workload Automation is that it lacks advanced features or advanced built-in functionalities found in competitors, for example, an advanced workflow feature. Even the handling or notification from AutoSys Workload Automation isn't the best in the industry. Other products have very good workflow-related functionalities such as ActiveBatch that's missing in AutoSys Workload Automation, so I wish the tool had those features."
"I would like to see the Service Orchestrator, a B2B product, and maybe a process audit."
"The GUI/Workstation is weak and needs to be improved. CA is working on this right now."
"We are trying to see if we can use this from a cloud perspective with AWS, Azure, and other clouds, but it seems that there is no cloud integration in this product. We would like to see cloud integration. We are very pleased with this solution, but we are moving our application to the cloud, and we found out that it doesn't support any cloud features. So, we are trying to find a replacement."
"The visibility and control features are somewhat limited."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"The lack of documentation, that is an issue. When we do need to bring it down for maintenance, it is always a scary moment for us because we have never had it crash."
"From an administrative point of view, I wouldn't give really high marks to the solution. I actually entertained getting the JAWS application at one point. One of the shortcomings with the scheduler is the reporting capabilities. At least at the time, JAWS was the best that they had for a third-party integration. I think they've got things in the pipeline to help alleviate that gap."
"They can do better reporting in terms of production statistics reporting."
"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."
"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."
"Their software installation and update process could use some improvements. I'm pretty sure they're working on that, but that's definitely an area where it could be streamlined a lot. There's still a lot of manual work that you have to do with the schedule when you deploy masters or do the agents."
"I would like more involvement with the cloud."
"The solution needs more advanced reporting and data visualization capabilities to enable deeper analysis of job performance and trends."
"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."
AutoSys Workload Automation is ranked 6th in Workload Automation with 79 reviews while Tidal by Redwood is ranked 2nd in Workload Automation with 37 reviews. AutoSys Workload Automation is rated 8.4, while Tidal by Redwood is rated 9.0. The top reviewer of AutoSys Workload Automation writes "Helps us manage complex workloads, reduce our workload failure rates, and save us time". 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". AutoSys Workload Automation is most compared with Control-M, IBM Workload Automation, Red Hat Ansible Automation Platform, Stonebranch and OpCon, whereas Tidal by Redwood is most compared with Control-M, IBM Workload Automation, Redwood RunMyJobs, ActiveBatch by Redwood and Rocket Zeke. See our AutoSys 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.
