The scope of this project was to provide support for Inventory Management applications on a 24x7x365 basis in an onsite/offshore mode. U.S. day time support was provided by an onsite team and U.S. overnight support was provided by the offshore team.
The project team provided support to fix a run-time production problems associated with existing Inventory Management applications. They performed the following tasks on a day to day basis.
Day-to-day production support.
- On-call activities.
- Log, correct and migrate production fixes.
- Update production system documentation for changes.
- Maintenance of the change log for programs.
Service Level Agreements (SLAs) were defined for this project. There was the categorization of support requests (run time production problems) based on the business needs. The project team resolved/escalated the critical problems within an hour of notification. The software and hardware environment in which the project was executed consists of:
- Hardware Platform - IBM Mainframe
- Software Platform
- Operating System - OS/390
- Languages - COBOL- II, CICS, JCL , ISPF (Interactive System Productivity Facility) V- 5.0.
- Databases -DB2, TERADATA, IMS
- Tools and Utilities
DUMPMASTER
ESP
Expeditor
PLATINUM
DB2 MON
INSYNC
- MS Word – Documentation tool
- MS Excel – Documentation support
- MS Outlook – E-mail
- Emulator – EXCEED
- REMEDY AR System – Problem tracking & support
The offshore team accessed the IBM Mainframe, Remedy Server, Web Portals and other servers.
A transition plan was prepared at the beginning of this project that was divided into three main phases i.e. Initial Phase, Knowledge Transfer Phase and Ongoing Support Phase. The objective was to transfer the service responsibility from the client team to the SPI team in a carefully planned manner and to ensure a smooth transition without affecting the existing services. The following was executed:
Initial phase
- Formed the project team
- Developed an assessment of the system
- Prepared knowledge transfer plan
Knowledge transfer phase
- Gained an understanding of all aspects of the application systems, associated procedures and controls.
- Analyzed all aspects of service delivery, availability and reliability. This phase typically includes:
- Study of business documentation.
- Study of business overview presentations by users and/or existing team members.
- Study and analysis of technical overview documentation.
- Study and analysis of past run time problems.
- Study of existing procedures.
- Training on operation of the problem management tool.
- Undertaking production support under supervision of the current client support team.
- Identifying configurable items, tools used for configuration management and process for configuration management.
Ongoing support phase
- Support and problem management.
- Contact analysts responsible.
- Publish status report on web.
- Resolve day-to-day issues.
- Application code changes requested by the client - onsite/offsite.
- Communication with the stores and data center