Because we've been on it for 20 years, it's pretty easy for us to automate jobs with Tidal at this point. It has become second nature. It's pretty simplistic to set up and get going, although there are different levels of complexity you can have within the product. It depends on how simple you want to keep it. If you just keep it: Job A, Job B, Job C, Job D, that becomes pretty simple. But when you start integrating some complex calendars that use sub-calendars—and you can go three, four, or five deep to set up schedules—it becomes more complicated. The beauty of it is you can go as deep as you need to. We can get really complex or we can keep it simple. We have some use cases for both scenarios. 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 are a financial company, we move billions of dollars a day, and if we don't have our transactions processed in a timely manner we can be penalized and our clients can be penalized. It can have a serious financial impact.
