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.
Shar was relying on Windows Task Scheduler and/or manual intervention to run their critical processes. Manually streaming these processes was a very labor intensive and error prone process, especially at month-end.
In the past, DDI relied on Windows Task Scheduler, Cron, and manual intervention to run all of its internal processes. One of the biggest issues the company faced was not having a single, centralized view of all of the jobs running across the enterprise.
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.
Tight integration between JAMS and PowerShell has minimized Marketing Associates’ dependence on multiple scripting languages. The feedback that JAMS provides through PowerShell on completion status and notification status helps streamline many of the company’s batch processes.
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.
West had employed several workarounds to make sure the master schedule proceeded as reliably as possible. As the company approached 6,000 jobs across multiple servers, the business recognized the need for a centralized solution.