Caterpillar
JAMS has been great. Tech support has been pretty amazing in helping with questions. Users are very happy with the capabilities they have gained with JAMS such as triggered jobs, dependencies, and much easier FTP processing.
JAMS has been great. Tech support has been pretty amazing in helping with questions. Users are very happy with the capabilities they have gained with JAMS such as triggered jobs, dependencies, and much easier FTP processing.
I have nothing but praise for the quality and responsiveness of your support team. One of the best vendor support teams I have worked with.
The IT team faced issues such as support for multiple ERP systems, support for applications for the Wholesale Trading team, and consolidation of data from multiple billing applications.
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.
Southwest Power Pool took advantage of the ability to run any kind of script in JAMS. They leveraged JAMS to run their batch scripts, SQL SSIS packages, PowerShell scripts and C# code all within the larger context of their enterprise workflows.
Since going live with JAMS, Bruce Power has automated more than 150 business-critical jobs. In addition to standard Windows Tasks, they’ve automated and integrated jobs from a long list of applications including: Passport, Workday, Sharepoint, NextAxiom, Informatica, and proprietary applications.
Seminole’s transition from mainframe processing to distributed processing presented the electric cooperative’s IT team with an important choice. Continue to invest in Control-M, the cooperative’s original mainframe scheduling tool, or start to look at alternative solutions.
Seminole Electric Cooperative is one of the largest electric power generation and transmission facilities in the United States. Initially, Seminole would run its Dynamics AX batch jobs at 11:00 PM, in the hopes that other processes would be done by the time Dynamics jobs started. A Thursday backup that included weekly consolidation of several databases frequently ran long, causing Dynamics jobs to fail. The Seminole team would often spend Friday mornings troubleshooting and re-running jobs.