We performed a comparison between AutoSys Workload Automation and Tidal Automation based on real PeerSpot user reviews.
Find out in this report how the two Workload Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"Last year, we added a second environment and the OpCon Deploy product. This has allowed us to build a testing environment. This has been a great addition for us as we can work through our workflows without disrupting our production environment."
"Having the jobs laid out while attaching dependencies is a nice addition to the program."
"There are a lot of valuable features. The version that we're currently casting, Self Service, is going to be the most valuable to us. It is going to allow us to open up the doors, broaden our automation capability and help other business units to be able to automate a lot of the little things that they do from day to day. I'm really looking forward to being able to help other areas with their automation needs. Self Service is really key."
"The biggest example in which OpCon has improved my organization is that we have to download and process files from the federal reserve several times a day. If we don't do it in a certain timeframe, we can be penalized. It's the fact that we can download these files, process them, get our accounting teams the information they need to work the exceptions that is one of the most important roles."
"With a simple click of a button in self-service, the department or the user can complete his/her job."
"File Watcher can run jobs when files are made available in a folder."
"It seems like it would scale well."
"Often times there are criteria that cannot be determined by the system, which allows a human to make the determination and use the Self-Service Solution Manager to trigger a job."
"The most valuable features of AutoSys Workload Automation are the file transfer protocol and file watcher. The solution has a user-friendly user interface. It is very simple to use. You have a scope of all your jobs, jobs are what you call tasks that you will automate in the solution. It lets you monitor everything in these jobs."
"AutoSys Workload Automation is a stable solution."
"The initial setup is easy."
"It is very valuable for us when we are trying to arrange or orchestrate jobs into a system. It is helpful for triggering jobs for a scheduled task."
"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."
"This solution has made my clients' workplaces a lot less labor-intensive."
"AutoSys Workload Automation is scalable."
"The most valuable feature of this solution is the functions are easy to use."
"The most valuable feature is the job scheduler, where you can schedule thousands of jobs to execute at specific times."
"I like the fact that I have control, and I am able to monitor. If there is an issue, I would be able to respond to any jobs that may fail. With any other scheduler that I know of, a lot of times, when I have a very complex script, if there is an issue in the middle of it, I have to let the whole process fail and then figure out a way to recover from it, whereas Tidal will stop the process, and I can resolve that issue. Once I resolve the issue, I can continue the process. This is very important for invoicing, accounts payable, accounts receivable, or any kind of financial reporting. It allows you to recover from an issue much more effectively than anything else that I have seen."
"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."
"There are some limitations in the actual jobs that are created and how you're able to rename files. Suppose you're bringing in, say, 10, 15, or 20 reports from a core system, and you're using an "asterisk character" to identify files. For example, if you're grabbing files that start with this, end with this, but the characters in between could be different, it has to retain that same name in the destination. It won't allow you to rename them with a date stamp or the like."
"We would like a display of the created date, created by, and last modified date, as well as modified by."
"It would be great if you could create physically separate "clients," as I call them. I wish I could have a production client and a testing client and that they would be separate."
"Upgrading to newer versions remains complex."
"The initial setup is very complex, but that's not necessarily something that needs to be improved. I'm told that in the next version they're improving the upgrade process. So that's in the works already."
"More functionality within self-service would be greatly appreciated."
"We are still in the early stages of our implementation, so at this point, I cannot see any needed improvements or features."
"The logs are a little daunting to look at the first few times, however, as you begin to understand what you're looking at, it becomes easier."
"AutoSys Workload Automation could improve the integration."
"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."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"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."
"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."
"The graphical interface can be improved."
"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."
"The solution could improve by having support for container environments."
"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."
"There are several improvement points that our team has provided to the vendor."
"The GUI, the graphical user interface, gets a little bit busy."
"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."
Automate repetitive tasks so you can focus on projects that drive your business forward. Find out how OpCon workload automation enables you to create repeatable, reliable workflows - all managed from a single platform.
AutoSys Workload Automation is ranked 4th in Workload Automation with 11 reviews while Tidal Automation is ranked 7th in Workload Automation with 4 reviews. AutoSys Workload Automation is rated 7.6, while Tidal Automation is rated 8.6. The top reviewer of AutoSys Workload Automation writes "Mature, reliable, scalable, and helpful for orchestrating jobs". On the other hand, the top reviewer of Tidal Automation writes "Allows us to use one scheduler for multiple instances, helps us to recover from an issue much more effectively, and is extremely flexible". AutoSys Workload Automation is most compared with Control-M, IBM Workload Automation, Red Hat Ansible Automation Platform, Automic Workload Automation and BigFix, whereas Tidal Automation is most compared with Control-M, IBM Workload Automation, ActiveBatch Workload Automation, ESP dSeries Workload Automation and Automic Workload Automation. See our AutoSys Workload Automation vs. Tidal Automation 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.
