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.
"ActiveBatch provides summary reports and logs for further analysis and improvements in monitoring servers, which is very handy."
"It can connect to a number of third-party/legacy systems."
"We leverage the solution's native integrations regularly. We have to get files from a remote server outside the organization, and even send things outside the organization. We use a lot of its file manipulation and SFTP functionality for contacting remote servers."
"The user interface is really incredible."
"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."
"The most valuable feature is its stability. We've only had very minor issues and generally they have happened because someone has applied a patch on a Windows operating system and it has caused some grief. We've actually been able to resolve those issues quite quickly with ActiveBatch. In all the time that I've had use of ActiveBatch, it hasn't failed completely once. Uptime is almost 100 percent."
"As far as centralization goes it's nice because we can see all these processes that are tied to this larger process. The commissions, FTP processing, the reporting, the file moves to the business users — all that is right there. It's very easy to read. It's easy to tie it together, visually, and see where each of these steps fits into the bigger picture."
"Error Handling is one of the best standout features of ActiveBatch."
"We have to run about 12,000 jobs every day and the majority of them need to be launched from our ERP, JD Edwards. The native compatibility of the Tidal platform with JD Edwards dovetails with our greatest need. It's directly connected to the heart of our IT system. We couldn't work without it."
"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."
"We use the solution for cross-platform, cross-application workloads. The solution’s ability to manage and monitor these workloads is very easy and accurate. We have file dependencies for running jobs. The job does not start until a file exists on a completely different server, then where the job will run. So, it is cross systems."
"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."
"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."
"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."
"The data management on offer was valuable."
"Tidal Automation allows organizations to automate complex workflows and processes, reducing the need for manual intervention and improving operational efficiency."
"Except for the GUI, everything looks good."
"There are very few documents that provide us with detailed information on the troubleshooting of errors that occur during integration with the existing environment."
"A cloud option is not provided as a free feature, making it a costly solution for smaller organizations."
"Providing some detailed training materials could be very helpful for new users who have very limited technical information about the tool."
"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."
"An area for improvement in ActiveBatch Workload Automation is its interface or GUI. It could be a little better. There isn't any additional feature I'd like to see in the tool, except for the GUI, everything looks good."
"One thing I've noticed is that navigation can be difficult unless you are familiar with the structure that we have in place. If someone else had to look at our ActiveBatch console and find a job, they might not know where to find it."
"I have faced struggles to understand, set up the tool, and implement it in my early days as a new user."
"The UI might have the potential to provide a more polished and user-centric encounter, promoting seamless engagements and simplifying the navigation process for individuals interacting with the software."
"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."
"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."
"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."
"One of the weaknesses of the product is, when something happens, it's difficult to find out the root cause. There are a lot of logs you can take a look at in Tidal. Sometimes, they are useful, but other times, they're not. That is mostly relegated to the administrative team. Users for the most part don't see that and don't know anything about that. They just know they have a problem, then it's up to the administrative team to see what happened and figure out the problem."
"The job failure alerts can be updated with more details for better troubleshooting."
"The solution needs more advanced reporting and data visualization capabilities to enable deeper analysis of job performance and trends."
"The user interface is the place that needs the most work. If and when we find issues with the product, they are usually in that area. If I had to choose, that's where I'd want issues, as opposed to in the engine. But the UI is average. It's a little sluggish at times and there are some bugs in it."
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.
