Case Study

Centralized job scheduling and lower maintenance costs after migration from IBM‘s TWS to BatchMan

Centralized job scheduling and lower maintenance costs after migration from IBM‘s TWS to BatchMan

Pages 2 Pages

Success Story K+S and BatchMan K+S‘s main reason for deciding to use BatchMan was the complete integration of the scheduler into the SAP System. WHY K+S CHOSE BATCHMAN: Simple handling Considerably lower maintenance costs No additional hardware required Can also be used on development and test systems, thereby integrating into the ITIL Change Management License costs only arise for live systems, not for development and test systems Better graphics for network representations Smooth transition to the FlexFrame landscape Only minimal amount of training needed Since the employees in the application development area were to take on a large part of the responsibilities and they were already familiar with SAP, the new job scheduling system preference was obvious

Join for free to read