APPENDIX_3.pdf

APPENDIX 3 – PHASE-IN/PHASE-OUT PLAN

SINLEC16C0014

JUSTICE ADMINISTRATION AND MANAGEMENT SUPPORT SERVICES

PHASE-IN/PHASE OUT PLAN

The purpose of a transition plan is to layout the tasks and activities needed to properly and efficiently transition production, operation, and maintenance. The transition must identify the team, its responsibility, schedule, techniques, tools, and methodology. Special attention must be given to risk management and contingency planning.

TRANSITION-OUT PLAN. The service provider shall also provide a transition-out plan of 30 days and shall cooperate with, and assist, the new service provider personnel to assure a smooth and effective transfer to minimize loss of efficiency in support of the Government during the transition-out period. Cooperation and assistance shall be limited to guidance and advice, as well as support within the functions covered by the contract. The incumbent service provider shall establish transition procedures with the new service provider.

The Contractor shall provide a complete product detail, including serial or other form of identification number, description, version number, or release dates to any given project performed to include:

4.1 Logical work breakdown, key milestones and dependencies during transition and deployment.

4.2 Testing and verification activities, including testing of related/impacted projects, software, and hardware.

4.3 Contingency plans and work-around(s) in the event problems arise.

4.4 Specific activities related to new and/or existing equipment, including roles and responsibilities of external vendors and internal resources.

4.5 Specific activities related to new, existing, and/or upgraded software, including roles and responsibilities of external vendors and internal resources.

4.6 Systems and/or data back-up(s), conversion plans, etc.

4.7 Hand-off(s) between developers, vendors, operational staff, and/or technical support.

4.8 Communication(s) to client and end-users: timing related to unavailability, periodic status updates, and notification of completion/system availability. Consider timing and mode of communication(s) among technical team, between the technical team and the customer/client, and broader set of end-users.

4.9 Transition review to assess and document results of the transition, defects found, correction actions to be taken, work-around(s) to be implemented, etc.