Tidal Automation Previous Solutions

Reviewer957656
Tidal Administrator at a retailer with 5,001-10,000 employees
In my previous company we used the Lawson ERP's internal job scheduler. There were Windows tasks that we had to check on. They were running a lot of VB6 stuff. In my current company, I came onboard years after they had already cut over to Tidal. I know they had some mainframe stuff in the past, but I don't think they converted from something like CA to Tidal. Tidal was their first choice. View full review »
EmmetWagle
Sr System Engineer at a financial services firm with 5,001-10,000 employees
We only had crontab on a bunch of Unix systems. We looked into Tidal because we were having so many missed processes. Our environment is so much bigger and more complicated now compared to 15 years ago. But even back then it was almost like having things in crontab made it easier for there to be issues because they were all arbitrarily set to run at different times, different users, different systems. If there was some sort of conflict or collision, there was really no way to even regulate the fact that there were too many processes running at given time. It actually helped prevent some issues then, and now we have so many things cranking through Tidal. Getting all this to work in crontab would be impossible. View full review »
LeeAnn McLennan
Application Engineer at Columbia Sportswear
I think we had a variety of solutions that were sort of stitched together. View full review »
Learn what your peers think about Tidal Automation. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
418,116 professionals have used our research since 2012.
reviewer1275663
Team Lead at a manufacturing company with 10,001+ employees
We were using SAP native schedule, which was fairly primitive. View full review »
AndrewGriffin
Lead Control Analyst at Central States Funds
We had two mainframes running all of our applications. We were using CA products. Our health application was ClaimFacts, from TriZetto, but they were dropping support for the mainframe product and everybody had to switch to Facets. We were running both products at the same time while we were transitioning to Facets. We had to run ClaimFacts, the mainframe version, for about a year or so because, if somebody has a claim they have a year to report that claim and another six months to make adjustments on their claim. So our old mainframe product had to be kept until all that faded away. Then everything went into PC, server-oriented applications. We got Tidal because the company, TriZetto, used Tidal to run their stuff. So we brought it in and we started setting up our whole batch schedule. View full review »
reviewer1283868
Production Control Analyst at a healthcare company with 1,001-5,000 employees
As I mentioned, we came off of Maestro. Back in 2004 or 2005, when we were looking at schedulers, Tidal was one of the solutions we demoed. Universally, we all decided that Tidal seemed to be the better candidate. View full review »
DavidCorbishley
Senior Consultant at Corbishley Consulting
I have worked with other workload automation solutions before, but nothing that is still around. Even though we have been a Tidal user for quite awhile, there was still stuff being run with Windows Scheduler or cron. We have been able to pull that stuff in and reduce the workload on teams. View full review »
reviewer1271571
Sr. Platform Engineer at a software R&D company with 10,001+ employees
We used local solutions, like scheduling for each platform, such as SAP Scheduler, SnapLogic scheduler, and cron jobs. We didn't have a centralized place. View full review »
reviewer1275831
Data Platforms Operations Lead Managed Hosting at a marketing services firm with 1,001-5,000 employees
We were using a home-grown solution. It was a cron job manager. It didn't do file events very well; it had monitor CIS logs. It was tough to schedule tasks. It was purpose-built so it didn't have a SQL adapter. It didn't have the ability to run on Netezza and things like that. We switched because to programmatically create the enhancements for the things that came out-of-the-box with Tidal was just too costly. It would have taken too much time. View full review »
MosesGujjarlapudi
Tidal Administrator at Devon Energy
This is my first scheduler. I used to send jobs to the Control-M team, but that was with my previous organization. When I started working for my current organization, Tidal was already available. My team was supposed to support Tidal too. View full review »
reviewer1323876
Automation Manager at a financial services firm with 1,001-5,000 employees
We went from AutoSys (formerly CA) to Tidal. We switched because of CA's expensive licensing. They were also behind the curve. View full review »
DianeMiller
IT Vendor Manager at a paper AND forest products with 5,001-10,000 employees
In my past job, I have used HelpSystems Robot. At the time, HelpSystems only ran on an AS/400 or iSeries while the Tidal solution runs on various platforms. They are pretty comparable though for functionality. View full review »
Learn what your peers think about Tidal Automation. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
418,116 professionals have used our research since 2012.