<Project Name>

Installation into Production

Installation into Production Plan Template Instructions

(Please remove this section before completion of template)

The Installation into Production Plan will outline the process that will be taken to move the system and/or application into the Live or Production environment. The plan should include an outline of all pre-requisites, approach and contingency plans. The communication of how this process will proceed is key and should be well defined in this plan. Once the installation is complete, the verification process will, also, need to be identified in this plan.

Be sure to maintain version control as the analysis is modified and/or edited.

All instructions within the template are italicized within the document.

Any examples are in a red font.

Any portion of the template that does not fit or pertain to your project should be documented that it was reviewed and is not relevant. See below for requirements for a project and deliverable approvals.

Be sure to unlock table of contents by selecting TOC then Ctrl-Shift-F11 to enable TOC updating in Word docx.

Project Deliverable	Requirements by Project Size
Executing Phase	Large	Medium	Small	Requirements	Approvals
Installation into Production Plan (SDLC)	O	O	O	This deliverable is optional for all project sizes, unless requested by the Sponsor, Steering Committee or IT management.	The Installation into Production Plan will have two approvals. The first approval will be the processes identified in the plan, and the second will be for the completion and verification or acceptance of the production environment. This plan should be approved by the Implementation Team, IT Change Management (if applicable), Sponsor, and the Steering Committee.

Table of Contents

1.	Introduction	2

1.1.	Purpose	2

1.2.	Assumptions	2

2.	Version Control	3

3.	Implementation Plan	4

3.1.	Overview	4

3.2.	Installation Prerequisites and Criteria	4

3.3.	Deployment Approach/Procedures	4

3.4.	Contingency Plan	4

4.	Communication Plan	5

5.	Verification Plan	6

6.	Approvals	7

6.1	Plan Approval	7

6.2	Completion Approval/Acceptance	7

Introduction

Purpose

Assumptions

This document assumes.....

Version Control

Version	Date	Person	Change
1.0	Initial Document Creation

Implementation Plan

Overview

Provide an overview of the implementation plan to be executed for this project.

Installation Prerequisites and Criteria

Define the prerequisite criteria that must be met prior to installation.

Deployment Approach/Procedures

Outline the approach, timing, steps, tasks, etc that will be implemented to complete this plan.

Contingency Plan

Document what the process will be if the installation into production fails.

Communication Plan

Define how the process will be communicated to the end user community.

*Make sure that the OIT Change Management Policy has been addressed. The part of the policy to pay attention to is:

“Notify the Rutgers OIT community of any change to the production environment in accordance with the OIT Change Management and Communication Policy. The policy states that "All computer and communications systems used for production processing at the University must employ a formal change control procedure used to ensure that only authorized changes are made. This change control procedure must be used for all changes to software, hardware, communications networks, and related procedures." (UMDNJ Policy on IST Change Management and Communication 95-01-04-01, Section V.A). Write to IST_CHG@umdnj.edu for specific instructions.”

Verification Plan

The test plan for installation should confirm that all key aspects of hardware and/or software installation adhere to the approved design intentions. Installation verification is intended to verify that the designed and tested hardware architecture &/or software configuration is installed correctly. Be sure to include roles and responsibilities, tools, and documentation requirements.

Approvals

Plan Approval

The individuals below agree that they have reviewed and approved the plan outlined in this Support Documentation.

APPROVED BY:
Function Role	Name and Title	Signature	Date

Completion Approval/Acceptance

The individuals below agree that the plan outlined in this Support Documentation has been executed to completion.

APPROVED BY:
Function Role	Name and Title	Signature	Date