We have seen ROI in the sense that it's primarily about our ability to stay flat in cost while constantly increasing our volume. That's the biggest ROI that I see.

We feel that the benefit is there for us. There's a good return on investment. There's no doubt. Being on the product for as long as we have, it's harder to quantify because we don't know what it was like without it. But compared to a scenario where we had a go with a different solution or some type of manual solution, the ROI with Tidal is very positive for us.

We definitely have a favorable cost of ownership. We are very satisfied with the product. Are there opportunities for improvement? Sure, like with anything. But we believe that the cost of ownership definitely outweighs the cost of not having ownership.

If I look at absolutely nothing else and just the licensing cost, I'm definitely saving money versus licensing Robot. I get a whole bunch of added features that I never had with Robot. 

We use it to do our patching and that brings down the cost of services and people. People don't have to sit there and do that manual work. It is automated. They just watch it. That definitely saves somebody from having to do work. So, instead of having four or five people on call over the weekend running all of these scripts manually, it is automated and I have one person watching to make sure it works. We've seen a great improvement. 

It is extremely important for our organization. For our MRP job stream, if Tidal can just once prevent an MRP issue from happening or let us recover from an MRP issue quickly, it has paid for itself. We would have paid for the software in just one instance of an outage. If I take that and multiply it against four other systems, I have the same situation. So, the software pays for itself over and over again on a yearly basis.

The time that it saves my staff is not huge, maybe four hours a week.

It has helped our organization by having one scheduler, instead of multiple schedulers, and having resources to support dependencies. It saves both monetary resources as well as fiscal resources. We don't want people to look at the screens on multiple platforms, and say, "Okay, this job is done. Go trigger another job."

The TCO is okay, but not out-of-the-box.

It's productivity. I don't get involved in the financials, but efficiency and productivity have certainly increased. Risk has decreased. So, I'm sure the return has been well worth it.

I spoke with our CTO, and he realized its benefits within three months of deployment. So, within three months of me setting up Tidal and deploying jobs to it, we've seen benefits and reduced risk. That was from the CTO. It doesn't take long. It takes a couple of months to get everything working right, moved over, and set up.

In terms of Total Cost of Ownership (TCO), it has been helpful with infrastructure expenses. It has been an improvement because we've been able to use this tool to more closely monitor the infrastructure environment to take action faster whenever there are problems. By centralizing the jobs, we've been able to reduce the number of servers needed. So, we're simply able to run more efficiently using this tool, which I'm sure has provided a benefit to the overall infrastructure.

The tool needs to integrate with different APIs, which it does. A big part of the business includes other solutions that need to integrate with Tidal. Different business users around the company use different ERP systems and reporting systems, and it's important that those interface with Tidal and that Tidal is dependable, which it has been. It has been seamless. There haven't been any issues.

We have absolutely seen ROI. It's not just that it's critical to our company, but I also feel that there is definitely return on investment because of the good support.

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.

I am able to create something predictable and manageable in such a way that we know that we will get alerted if there's a problem and know how jobs are going to run. People can see and manage their jobs on a daily basis without having to talk to me about them. The return on investment is scope of jobs, making it so the management of jobs is not something that is handled by one team. It can be parsed out to the schedulers who know and understand those jobs so they can have some control over them, then I don't have to worry about all the different jobs streams. I just have to look from above and be able to help make sure that the system itself works. 

For ROI we'd have to figure out how many man-hours am we're saving with Tidal versus not having it or having one of the other automation tools. We've grown up with it. I can't imagine being without it. Back in 2016, when we looked at possibly switching over to another solution, it wasn't a clear path to migrate to any of the other tools. We literally run our whole enterprise on this, so if Tidal goes down, the world stops.

We feel we're getting a pretty good deal with Tidal. It's supporting $600 to $700 million in revenue.

The ROI is okay and that is why we continue to work with Tidal. Overall, the price is fair for the service we receive and the way it meets our automation requirements.

The most important measure, and our basis for comparison, is to look at the number of people who would be required to do the same thing.

In terms of ROI, we have witnessed an:

• Increase in Productivity by ~28%
• Increase in Accuracy by ~8%

Tidal Workload Automation is a no-brainer for us, given the importance of the processes that we have. The cost for coordinating, managing, and getting all these things to complete, while warning us when things are not running on time, to me, makes it a no-brainer. 

I do not know how to quantify our ROI. We get everything that we pay for in the product, and there are even features that we do not use.

We have seen ROI from savings in time. We run on average about 2,200 jobs a day. This is a cost savings for us due to the fact that our users do not have to run these jobs manually since Tidal will do it for them.  As an estimate, this has probably freed up 10 full-time people, in the various departments, about an hour or two a day.

Overall, the TCO is pretty good. There has never really been a conversation where any customers I have worked with complained about it.

The product generates a return on investment.

I was not involved in measuring the ROI.

If you can automate things that people are doing, you will save time and resources because people can be doing more value-add work than manual stuff. Broadly speaking, if you start automating all of your clients' compliance evidence and collecting, it becomes standard, then the people who are doing that can do something more useful. If you extrapolate that, then that is time well spent and saved.

I don't really have metrics for ROI. It's more of a feeling because we've been able to consolidate from all these separate scheduling products into this one scheduling tool, allowing us to have direct dependencies between things. That's an efficiency in itself, but I don't have any statistics to support the number of hours saved and the number of dollars saved. Overall, it has improved our business model with automation.

We have seen return on investment.

Our organization has been using Tidal for the past 10 to 15 years. That means it's a valuable tool.

I would say we have seen a return on investment by going with Tidal, and not only because of the volume of jobs we're running, but because of the variation of jobs that we're running. It gives us the ability to manually adjust processes on-the-fly, and having that visibility and quick reaction to failures has been a big plus for us.

The ROI is pretty straightforward. It's a mission-critical app, and if we had to go back and do things the way we used to, it would be impossible. 

It would be undoable because now we would build a whole system that depends on functionality that is in Tidal. For example, to do something like calendars in SAP, they will be nowhere near as sophisticated or high quality. 

Could you do intrasystems dependencies? You could. However, there would be quite a bit of work to make that happen. It would be too complex. While here it is two clicks, and you're done. 

The alternative would be to go to a different product. But how? Migrating to a new product would be expensive, consuming, and complex. I just don't see that happening.

It does generate ROI but I do not have specific metrics available because it is known by my customer. When a customer continues to use the same product for a number of years then it seems that they are happy with the return on investment.