Our latest evaluation compares Fortra's JAMS and Tidal by Redwood, two prominent Workload Automation Solutions, drawing insights from user reviews on PeerSpot.
Tidal offers robust workload management, scalable, event-driven scheduling, and graphical views regarding valuable features. Its integration capabilities with systems like ServiceNow and JD Edwards are particularly notable. JAMS is recognized for its effective tracking and visualization of job dependencies, user interface, and PowerShell capabilities.
However, both products have areas for improvement. Tidal could benefit from a more intuitive GUI, simplified licensing, AI and enhanced reporting capabilities. JAMS needs more precise documentation, especially for custom execution methods and better integration transparency. A global search feature and a fully web-based client are also suggested enhancements.
Looking at pricing and ROI, Tidal is praised for its predictable costs and value for functionality despite the complexity of licensing and adapters. JAMS is seen as reasonably priced with scalable licensing options, offering significant time and cost savings.
Ease of deployment is a highlight for both; Tidal is commended for its straightforward setup, involving minimal maintenance and a learning curve of just one to two hours, resulting in a three-week deployment timeframe. Similarly, JAMS is appreciated for its easy installation and configuration. Users could easily follow webpage instructions, with setup completed within hours and a native installation of SQL Express being a convenient feature.
Tidal users shared that customer service is responsive and knowledgeable. JAMS receives accolades for its quick, effective support and various communication channels.
In summary, both Tidal and JAMS are robust workload automation solutions with distinct strengths and minor areas for improvement. Their ease of deployment, feature sets, pricing, ROI, and customer service are well-regarded, making them competitive choices in their domain.
"I find the historical tracking feature of JAMS invaluable for reviewing past events."
"I didn't know about JAMS because I don't have a person with any challenges with the purchase administration. The feature or the user interface is user-friendly because of the readable icons or very descriptive icons. Though I'm a beginning user of JAMS, I had no issues using it."
"The interface is good, and it's very easy to define and create jobs. If a job is not running or there is an error, the solution will send an email. That's all very good and very useful."
"JAMS has improved my organization by taking a myriad of manual processes and allowing us to automate them. It enables our folks to focus more on tasks that require their human intelligence and their creativity and less on just mundane tasks. It increases efficiency, accuracy, and consistency."
"The scheduling and execution of jobs are the most valuable features. The scheduling is important because if there is a task we want to execute at 4:00 AM, there's no way we will have someone who can manually run the job. In addition, we execute 100 to 200 jobs per day, and manual intervention is not an option."
"The planning capabilities are most valuable."
"Our company is based on data. Everything we do is data-driven, so it has been very valuable having one place where we can process all of the data and do batch schedules with chunks of data."
"We looked at other companies, like VisualCron, that were cheaper, but one of the main sticking points was the fact that they wouldn't have provided a central location for us to monitor across all servers. That was one of the biggest selling points of JAMS."
"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..."
"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."
"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 thing that I like the most is the reliability of the engine. The actual scheduling part of the product is pretty much flawless, but the stability of the product is what I find to be reassuring."
"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."
"The versatility of being able to run on many different types of servers is valuable. There is also a versatility of different services that you could run jobs on. It's highly versatile. You can run a lot of different types of scripts on a lot of different types of servers. It interfaces with all of them."
"The best feature of Tidal Workload Automation Software is its ease of integration with other systems, including ERP, CRM, and BI tools."
"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."
"The product does not allow the users to cut and paste the job names from the screen."
"I would like to see the ability to interface with Microsoft group-managed service accounts, but they're still in the research phase. They need to ensure everything's legit and safe. The report designer and dashboards could also be improved. We're running 7.3, so I don't know if they have updated the reporting in 7.5, but I think the reports and dashboards could be better."
"The documentation is not super... It's not as quick and slick as I'd like it to be."
"The biggest area with room for improvement is the area that my organization benefits the most from using JAMS, and that is in custom execution methods. I happen to have a very good C# developer. Ever since we got JAMS, he has spent a lot of time talking to JAMS developers, researching the JAMS libraries, and creating custom execution methods. He's gotten very good at it. He is now able to create them and maintain them very easily, but that knowledge was hard-won knowledge. It was difficult to come by, and if I should ever lose this developer, then I would be hard-pressed to find anyone who could create JAMS custom execution methods quite as well as he can since there really isn't all that much help, such as documentation or information, available on how to create custom execution methods."
"Fortra is getting much better with documentation and examples, but there is still room for improvement."
"It is important to receive notifications if a charged job fails and SQL is halted. JAMS does not provide halted notifications by default, which is a critical feature that needs to be added."
"All my machines at work are Macs. JAMS client is a Windows-based thing. It is all built on .NET, which makes perfect sense. However, that means in order for me to access it, I need to connect to a VPN, then log onto one of our Azure VMs in order to access the JAMS client. This is fine, but if for some reason I am unable to do so, it would be nice to be able to have a web-based JAMS client that has all the exact same functionality in it. There are probably a whole bunch of disadvantages that you would get with that as well, but that is definitely something that would make life easier in a few cases."
"When looking at a folder in JAMS with many jobs, it would be good to have better information in the list display of what's inside those jobs. We get some information, but other important details are missing."
"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."
"The GUI, the graphical user interface, gets a little bit busy."
"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."
"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."
"Initially, it is complicated to understand the functionalities as there is limited product documentation."
"Tidal Software interface could be more intuitive and user-friendly."
"There are several improvement points that our team has provided to the vendor."
"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."
Fortra's JAMS is ranked 5th in Workload Automation with 27 reviews while Tidal by Redwood is ranked 2nd in Workload Automation with 37 reviews. Fortra's JAMS is rated 9.0, while Tidal by Redwood is rated 9.0. The top reviewer of Fortra's JAMS writes "We can scale up our organization's scheduling and automation without having to add staff to the department". 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". Fortra's JAMS is most compared with Control-M, AutoSys Workload Automation, Redwood RunMyJobs and VisualCron, whereas Tidal by Redwood is most compared with Control-M, AutoSys Workload Automation, IBM Workload Automation, Redwood RunMyJobs and VisualCron. See our Fortra's JAMS 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.
