We performed a comparison between ActiveBatch 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: ActiveBatch Workload Automation is highly praised for its versatility and ease of use. Users appreciate the prebuilt jobs and real-time monitoring capabilities, as well as the automatic scheduling feature. Tidal Automation is known for its excellent job scheduling and single pane of glass interface, which allows for convenient management. Users also value the flexibility in running jobs and the data security features offered by Tidal Automation.
ActiveBatch could improve licensing, user interface, trigger reliability, documentation, support services, and integration capabilities. Tidal Automation could benefit from enhancements in its user interface, pricing model, integration options, and customization features.
Service and Support: Users have provided positive feedback for the customer service of ActiveBatch Workload Automation, appreciating the helpfulness, reliability, and responsiveness of the support team. However, there are concerns regarding the service model and availability of the hotline. Tidal Automation has highly praised customer service that is responsive, knowledgeable, and willing to assist. The experienced support team promptly addresses problems, although there are occasional mentions of lower-priority items being overlooked.
Ease of Deployment: The setup process for ActiveBatch Workload Automation was smooth and straightforward, without any significant challenges. However, there was a minor requirement for additional documentation during the file import. The setup for Tidal Automation was described as easy to handle and uncomplicated, with useful documentation available. Some users expressed a desire for more training to tackle complex tasks.
Pricing: Users find the setup cost for ActiveBatch Workload Automation to be quick and straightforward. The pricing is seen as reasonable and competitive. Tidal Automation's pricing is also fair and predictable, with a transparent licensing model. However, some users mention the complexity of licensing when additional adapters are required.
ROI: ActiveBatch Workload Automation is highly regarded for its ability to enhance net revenue, offering a valuable solution. Tidal Automation streamlines operations, mitigates risks, and consolidates tasks, providing substantial benefits in terms of reducing manual efforts and improving overall job management.
Comparison Results: Tidal Automation is the favored choice over ActiveBatch Workload Automation. Users commend Tidal Automation's job scheduler, streamlined interface, and ability to run jobs on various servers. The user-friendly interface and seamless integration with other systems are also highly regarded.
"The REST API adapters and native integrations for integrating and orchestrating the software stack are very flexible."
"ActiveBatch has reduced work by providing automated workflows across several different applications."
"Approximately ~20 hours of manual effort have been reduced to ~5 hours with the help of ActiveBatch."
"The software offers real-time monitoring and reporting features that let IT teams keep tabs on the progress of their batch operations and workflows."
"There are hundreds of pre-built steps."
"The nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially."
"We use the main job-scheduling feature. It's the only thing we use in the tool. That's the reason we are using the tool: to reduce costs by replacing manual tasks with automated tasks and to perform regular, repetitive tasks in a more reliable way."
"ActiveBatch provides summary reports and logs for further analysis and improvements in monitoring servers, which is very handy."
"It saves times due to automation. With some files, we do hundreds a day for a particular vendor. This would be hard to do manually. Also, the speed at which we can do this is excellent."
"By leveraging machine learning algorithms, Tidal Automation can use this data to optimize turbine settings and improve overall efficiency and performance."
"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."
"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."
"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."
"It's easy to use and easy to administer, and it's very flexible."
"One of the most useful features is being able to set up a schedule and create dependencies. The calendar can kick off processes at certain times, based on dependencies that you specify, like time, or whether another process has finished. Dependencies are the most useful thing."
"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."
"It does have a little bit of a learning curve because it is fairly complex. You have to learn how it does things. I don't know if it's any worse than any other tool would be, just because of the nature of what it does... the learning curve is the hardest part."
"They could provide an easier installation guide or technical support to the organizations during the installation process."
"Some improvements can be made to the user interface."
"Except for the GUI, everything looks good."
"The product should be improved by providing a customization option."
"We have faced a couple of issues where we were supposed to log a defect with ActiveBatch. That said, the Active batch Vendor Support is very responsive and reliable."
"There is this back and forth, where ActiveBatch says, "Your Oracle people should be dealing with this," and Oracle people say, "No, we don't know anything about ActiveBatch." Then, it all falls back on me as to what happens. Nobody is taking responsibility. This is the biggest failing for ActiveBatch."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time. So, if there was a constraint waiting, you may be looking for it in the wrong time frame. Plus, with thousands of jobs showing up and the way it pages output jobs, sometimes you end up with multiple pages on the screen, then you have to go through to find the specific job you're looking for. On the opposite side, you can limit the daily activity screen to show only jobs that failed or jobs currently running, which will shrink that back down. However, we have operators who are looking at the whole nightly cycle to make sure everything is there and make sure nothing got blocked or was waiting. Sometimes, they have a hard time finding every item within the list."
"Initially, it is complicated to understand the functionalities as there is limited product documentation."
"Understanding and using Tidal Automation could be overwhelming for someone with minimal programming language."
"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."
"Tidal Automation could be further integrated with other systems used in the operation of tidal energy systems, such as weather forecasting tools, energy management systems, or asset management software."
"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."
"The GUI, the graphical user interface, gets a little bit busy."
"There are several improvement points that our team has provided to the vendor."
"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."
ActiveBatch by Redwood is ranked 4th in Workload Automation with 35 reviews while Tidal by Redwood is ranked 2nd in Workload Automation with 37 reviews. ActiveBatch by Redwood is rated 9.2, while Tidal by Redwood is rated 9.0. The top reviewer of ActiveBatch by Redwood writes "Flexible, easy to use, and offers good automation". 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". ActiveBatch by Redwood is most compared with Control-M, AutoSys Workload Automation, Redwood RunMyJobs, IBM Workload Automation and JSCAPE by Redwood, whereas Tidal by Redwood is most compared with Control-M, AutoSys Workload Automation, IBM Workload Automation, Redwood RunMyJobs and Rocket Zeke. See our ActiveBatch by Redwood 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.
