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 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."
"We get better reports than we use to have."
"Inherit Dependencies feature reduces scheduling errors for holiday processing."
"It works constantly and is pretty seamless. You do not have to open up many support tickets."
"The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it."
"We need to have things run in a very sequential order, so it is very useful that we can schedule the work flows."
"We automate recurring processes, keeping track of IT processes controlled worldwide."
"We use CA Workload Automation AE r11.3.6 to automate enterprise-wide scheduling and file transfers using an FTP plugin."
"For us, the calendaring system is very robust. Some of the teams have very specific requests for when they need jobs to run. That's been really valuable, because a lot of times, when people run scripts, if they run on a holiday, they're going to fail... A couple of times a month it probably saves us work and the necessity of logging in from home and checking to make sure everything's okay."
"The best feature is that it allows task scheduling based on particular occurrences, like the receipt of files, database updates, or system notifications."
"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."
"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 by Redwood is a user-friendly solution."
"It is intended to enable large-scale automation environments, making it appropriate for companies with complicated processes and big data volumes."
"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."
"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."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"In terms of what should be in the next release, I want integration and AI and so on. I'd like easy reporting where you can compare information, for example, "that job normally takes three minutes and last time it took six minutes or 10 minutes." Then you can get the information to the engineer of which job is taking more time than normal - understanding strange behavior compared to the baseline."
"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."
"Some of the reports are either a bit hard to understand or don’t give you what you might expect to see."
"Reduce the number of operational files. This would make the job of a system programmer supporting ESP easier."
"The graphical interface can be improved."
"Pricing model for distributed should have an Enterprise option."
"I am not sure whether it is our limitation or a tool limitation because we haven't yet explored it, but whenever we look for different types of reporting, we have some limitations in getting those. It could be because of the way we have set it up internally in our enterprise, but it would be helpful if we can customize the reporting features and some of the alerts that can go out. When we connect enterprise systems, each one looks for a different use case, and if we can get different types of reporting, it will be helpful."
"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."
"It takes a lot of time to learn the product. I have admins and developers who are working on the products for the last three to four years and still don't know all the functionalities. Tidal has really great things about it, but people are focused on their day-to-day job and the solution is not intuitive."
"I don't know if Tidal wants to get into the business of monitoring long-running jobs, but that could be a feature for the future: a job launching and monitoring tool. Using Tidal for monitoring doesn't seem like a good fit, but if they could offer something that did that as an add-on or include it, it might be helpful."
"The GUI, the graphical user interface, gets a little bit busy."
"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."
"Understanding and using Tidal Automation could be overwhelming for someone with minimal programming language."
"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."
"The product’s UI is outdated. They should work on this particular area."
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.