Under Wilson HTM Investment Group’s old method, there were no dependencies in place between jobs, which increased the business risk of jobs potentially running out of sequence (or not at all). If this occurred, then the result was a significant effort the following day to remedy the situation.
Stater not only wanted to move their core batch scheduling system to a Windows platform, but also needed to centrally manage all of these decentralized tasks and processes.
Crane Group relied on a hodgepodge of tools like Windows Task Scheduler, SQL Server Agent, and the scheduling capabilities native to JD Edwards. The issue was that none of these schedulers are robust.
One of the main issues that Zong faced was that there was no centralized control or management of their processes. Zong also had no way of being notified if remote jobs failed.
Using Windows Task Scheduler and SQL Server Agent, TyMetrix could not keep up with customer demand for real-time data. IT staff spent considerable time to deliver its robust legal billing and matter management reports on time.
The DSE previously used tools causing several pain points for the department’s IT staff. Failure notifications were frequently unreliable, and lacked sufficient information to identify specific points of failure.
Although native SQL tools provide basic scheduling capabilities, Frontline recognized that leaning on SQL for automation was a less than ideal solution.
ESCO Advisors’ proprietary applications draw content from multiple data stores and run millions of calculations against the data every day. For each energy retailer, they collect data such as weather forecasts, usage history, market prices, energy supply, and billed revenue per customer.
Hosting critical applications and business processes on multiple platforms had created a variety of pressure points for UVA Health’s workload automation tools. Failures and delays caused by the shortcomings of these tools were unacceptable.