What do you like most about Tidal Automation?

It has been super stable. There are no complaints on stability. We would not be using it if Tidal wasn't stable.

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.

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.

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...

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.

The solution also enables admins and users to see the information relevant to them. They're able to actually run jobs that they weren't necessarily able to run before. They can see the output and they can be notified when there are issues and resolve those issues before they cause more issues.

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.

The first, big thing that we got out of using Tidal Workload Automation was having a centralized view of the status of all of our batch processes across all these systems... We can look into the schedule at any given time and see if things are running on track or if they are falling behind. We can also see if something failed.

Tidal helps administrators and users to see the information that is relevant to them in that single pane of glass. They can see jobs running, they can see job history, and they can see job progression. If you look at alternatives like Airflow and clouds, you'd have to design your own UI to monitor the progress of the different jobs that you've created in Airflow. So Tidal is huge for us.

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 wouldn't be able to do many of the complex scheduling that we do today without it. For us, it is a mission-critical app. Because if it doesn't work or has a problem, then SAP doesn't function. It is that critical. So, it's an essential tool for us to manage and run SAP jobs.

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.

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.

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.

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.