In our organization, we are running scheduled jobs in batches. There are three different uses for Tidal, which are primarily development, testing, and production. It's like the environment that allows you to run batch jobs in those three environments.
I do production, like systems administration, and the development of the batch environment. So, I install Tidal, maintain it, upgrade it, apply hotfixes, or do any type of system admin function. Also, I set up batch environments for development, QA, and production which run in Tidal. I also train people on how to use it.
In terms of deployment, we're on-prem. We've adapters and virtual machines, but everything is on-prem.
It streamlined the batch environments. It got everybody on the same page, and people haven't had to monitor their own jobs. We've been able to centralize the running of batch environments. We've been able to migrate various schedulers into one central location. It has helped with reducing risk by being aware of what's running and making sure that what needed to run did run versus something breaking somewhere and nobody knowing about it. Here, if something breaks, everybody would know about it, and then action would be taken. It has reduced risk and streamlined and centralized operations.
It's very versatile. We generally have SQL jobs. We've SQL, SSIS, PowerShell, C#.NET, etc. So, whatever a program is written in, and whether it runs on Windows, UNIX, Linux, or mainframe, there are just a wide variety of jobs it runs in different programming languages.
I've been an administrator for other schedulers over many years, which includes CA, AutoSys, Control-M, etc. Of all of them, Tidal is the easiest one to use. It's very GUI oriented, whereas a lot of the other schedulers have been command-line-based. It's by far the easiest scheduler to use for creating objects, which would be jobs, events, and things like that. It's all graphical. It's Windows-based. When building a job, most features are predefined. You just have to select where the executable is to run from and the time or event-based settings. You don't have to use the command line. Everything is kind of predefined for you. So, you just go through Windows and fill out different features in different jobs. It's simple. I've trained a lot of people on how to use it, and people who use Tidal for the first time are able to make jobs, whereas, with other schedulers, there are other things that they need to know, such as operating system-level commands. With Tidal, almost everything is already defined. You just tell it where to run the job from, which folder it's in, what's the name of the executable, and then the time when you want it to run. It can be learned within an hour. It's pretty cool.
I've used Tidal Automation to connect and integrate with a lot of different software and systems. I've used PeopleSoft, Informatica, BI, SQL Databases, VMware, Azure, and others. I haven't had any issues. So far, everything has been great. They have a compatibility matrix that ensures that different versions of Tidal will work with different software. They're good about keeping that up to date. Occasionally, you have to apply hotfixes to different software levels, but I've had good luck with the interfaces.
It is easy to integrate other technologies and processes via the REST API. All you need is access and a log-in ability, and it integrates well. You don't really need to do a lot of configuration.
It has increased capacity by manyfold in terms of the number of jobs and/or integrations. I've gone from 500 jobs to 1,500 in just six months. That's really in the first year of setting up Tidal. It worked that way at other companies too, with the same kind of jump.
