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.
"The customized views that each individual can create, and views that can be made free-form, makes this very popular with the programmers."
"We automate recurring processes, keeping track of IT processes controlled worldwide."
"It allows you to automate tasks, and reduce headcount, prevent errors, self-heal."
"The scheduling feature allows us to know when jobs are going to run and makes sure they run in the order needed."
"The features that I have found most valuable with AutoSys are that it is scalable, easy to use, fast, and always available. That's very important because if it's not steady then it's a real problem. So, at this point, we are satisfied with it."
"It is a fairly stable solution."
"I prefer AutoSys over the other ones out there for ease of use, ease of understanding, and getting people to understand how the tool works."
"It gives a real-time view of all the batch processing that we have. Monitoring-wise, it 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."
"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..."
"It is intended to enable large-scale automation environments, making it appropriate for companies with complicated processes and big data volumes."
"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."
"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."
"Tidal Automation’s most valuable feature is customization. It can work and connect with any app."
"With other tools, you do not have the ability to schedule jobs on their own. You need to create a group and then assign everything to that group. Only then will the job be able to execute. In Tidal, you can schedule a single job and there is no need to create a group. That's what I like the most."
"Tidal Automation allows organizations to automate complex workflows and processes, reducing the need for manual intervention and improving operational efficiency."
"I am looking forward to more of their dashboard features. I think it would be very valuable for us to have dashboard features that could be delivered to our customers in the form of a URL, and they could refresh that URL whenever they wanted to get up to date performance metrics out of our systems."
"I would like to see the Service Orchestrator, a B2B product, and maybe a process audit."
"We have to escalate through channels to get to somebody who knows what's going on. It takes time that we do not necessarily have."
"A better graphical user interface, because we have a lot of people using the client utility, and we want to get them away from that."
"Performance improvements in the UI would be appreciated."
"We see improvement possibilities in the processing provision of predefined evaluations or individual objects, or in the Self Service portal, which can be used by any user to monitor objects or start objects."
"AutoSys Workload Automation could improve in the Linux environment. The previous versions of the AutoSys Workload Automation let you take the profile of the user that you were using to run the tasks that you're going to automate, but in the latest versions, you can't do that, you need to make more definitions and it's a little bit difficult. It was easier in the previous versions."
"Because this product only computes processing days, it is hard when things need to be scheduled according to non-processing days."
"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."
"The solution needs more advanced reporting and data visualization capabilities to enable deeper analysis of job performance and trends."
"The job failure alerts can be updated with more details for better troubleshooting."
"The product’s UI is outdated. They should work on this particular area."
"Setting up the initial product was a little hard."
"Some users have complained that the initial setup process is complicated and time-consuming, while others have suggested that the software could offer more freedom in customizing processes."
"The biggest improvement they need to work on is doing better QA checks before they release new patches and service packs. We do find that you can't trust getting the new product right away, as they have to get some bug fixes out. They do tend to have some bugs in the first iteration."
"The software's performance and scalability could be improved, particularly when dealing with large-scale workloads or complex business processes."
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, Automic Workload Automation 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.