![](media/image1.wmf){width="1.4in" height="1.3527777777777779in"}

> **INSTALLATION AND**
>
> **CONVERSION**
>
> **PLAN**
>
> *Project or System Name*
>
> **U.S. Department of Housing and Urban Development**
>
> Month, Year

**Revision Sheet**

  ----------- ---------- ---------------------------------------------------
  **Release   **Date**   **Revision Description**
  No.**                  

  Rev. 0      5/30/00    Installation and Conversion Plan Template and
                         Checklist

  Rev. 1      6/13/00    Additional text in section 2.5

  Rev. 2      4/10/02    Conversion to WORD 2000 format

                         

                         

                         

                         
  ----------- ---------- ---------------------------------------------------

  ---------------------------------------------------- -----------------------------------------------
  ![](media/image2.wmf){width="1.1152777777777778in"   **Installation and Conversion Plan
  height="1.0951388888888889in"}                       Authorization Memorandum**

  ---------------------------------------------------- -----------------------------------------------

I have carefully assessed the Installation and Conversion Plan for the
[(System Name)]{.underline}. This document has been completed in
accordance with the requirements of the HUD System Development
Methodology.

MANAGEMENT CERTIFICATION - Please check the appropriate statement.

\_\_\_\_\_\_ The document is accepted.

\_\_\_\_\_\_ The document is accepted pending the changes noted.

\_\_\_\_\_\_ The document is not accepted.

We fully accept the changes as needed improvements and authorize
initiation of work to proceed. Based on our authority and judgment, the
continued operation of this system is authorized.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

NAME DATE

Project Leader

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

NAME DATE

Operations Division Director

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

NAME DATE

Program Area/Sponsor Representative

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

NAME DATE

Program Area/Sponsor Director

**INSTALLATION AND CONVERSION PLAN**

**TABLE OF CONTENTS**

[Page \#]{.underline}

1.0 GENERAL INFORMATION

> 1.1 Purpose
>
> 1.2 Scope
>
> 1.3 System Overview
>
> 1.4 Project References 1-2
>
> 1.5 Acronyms and Abbreviations
>
> 1.6 Points of Contact
>
> 1.6.1 Information
>
> 1.6.2 Coordination

2.0 INSTALLATION AND CONVERSION GUIDE

> 2.1 Installation Overview
>
> 2.2 Security Considerations
>
> 2.3 System Installation Strategy
>
> 2.3.x Installation Task Name\]
>
> 2.4 Conversion Strategy
>
> 2.4.x \[Conversion Task Name\]
>
> 2.5 Overall Schedule
>
> 2.6 Roles and Responsibilities
>
> 2.6.1 Organizations and Roles
>
> 2.6.2 Personnel Requirements
>
> 2.6.3 Training
>
> 2.7 Master Inventory
>
> 2.7.1 Software
>
> 2.7.2 Support Software
>
> 2.7.3 Hardware
>
> 2.7.4 Other
>
> 2.x \[Site Inventory Identifier\]
>
> 2.x.1 Site Software
>
> 2.x.2 Site Support Software
>
> 2.x.3 Site Hardware
>
> 2.x.4 Other Site Inventory
>
> 2.x.5 Site Support Facilities
>
> 2.x.6 Site Training
>
> 2.x.7 Site Implementation Team

3.0 SITE INFORMATION

> 3.x \[Site Identifier\]
>
> 3.x.1 Site Schedule
>
> ***3.x.2 Site-Specific Procedures***

**1.0 GENERAL INFORMATION**

*[**NOTE TO AUTHOR:** Highlighted, italicized text throughout this
template is provided solely as background information to assist you in
creating this document. Please delete all such text, as well as the
instructions in each section, prior to submitting this document. **ONLY
YOUR PROJECT-SPECIFIC INFORMATION SHOULD APPEAR IN THE FINAL VERSION OF
THIS DOCUMENT**.]{.mark}*

*[This Installation and Conversion Plan provides instructions for
performing installation and conversion procedures at all installation
sites. This plan is developed in a preliminary state in the "Build"
phase of the lifecycle and finalized with additional detail in the
"Evaluate" stage.]{.mark}*

# GENERAL INFORMATION

## 1.1 Purpose

Describe the purpose of the Installation and Conversion Plan.

## 1.2 Scope

Describe the scope of the Installation and Conversion Plan as it relates
to the project.

## 1.3 System Overview

Provide a brief system overview description as a point of reference for
the remainder of the document. In addition, include the following:

-   Responsible organization

-   System name or title

-   System code

-   System category

```{=html}
<!-- -->
```
-   *Major application*: performs clearly defined functions for which
    there is a readily identifiable security consideration and need

-   *General support system*: provides general ADP or network support
    for a variety of users and applications

```{=html}
<!-- -->
```
-   Operational status

```{=html}
<!-- -->
```
-   Operational

-   Under development

-   Undergoing a major modification

```{=html}
<!-- -->
```
-   System environment or special conditions

## 1.4 Project References

Provide a list of the references that were used in preparation of this
document. *[Examples of references are:]{.mark}*

-   *[Previously developed documents relating to the project]{.mark}*

-   *[Documentation concerning related projects]{.mark}*

-   *[HUD standard procedures documents]{.mark}*

## 1.5 Acronyms and Abbreviations

Provide a list of the acronyms and abbreviations used in this document
and the meaning of each.

## 1.6 Points of Contact

### 1.6.1 Information

Provide a list of the points of organizational contact (POCs) that may
be needed by the document user for informational and troubleshooting
purposes. Include type of contact, contact name, department, telephone
number, and e-mail address (if applicable). Points of contact may
include, but are not limited to, helpdesk POC, development/maintenance
POC, and operations POC.

### 1.6.2 Coordination

Provide a list of organizations that require coordination between the
project and its specific support function (e.g., installation
coordination, security, etc.). Include a schedule for coordination
activities.

**2.0 INSTALLATION AND CONVERSION GUIDE**

# INSTALLATION and conversion guide

*[This section describes implementation methodology for the Installation
and Conversion Plan.]{.mark}*

## 2.1 Installation Overview

Provide a general description of the process for system installation
and/or conversion.

## 2.2 Security Considerations

Present an overview of security considerations associated with
installation and/or conversion procedures.

## 2.3 System Installation Strategy

*[As a living plan, the system installation tasks described in this
section will be enhanced and updated throughout the lifecycle. Each task
should be under a separate section header, 2.3.1 through 2.3.x.]{.mark}*

### 2.3.x \[Installation Task Name\]

Identify and describe in detail each installation task required to
implement the system (installation and/or conversion) in the sequence of
the task's execution. Link each task with the functional group that will
perform the task (user, operations, and developer). *[Tasks may include,
but are not limited to, the following:]{.mark}*

[]{.mark}

-   *[Establishing criteria, providing supervision, and conducting
    training activities associated with the implementation]{.mark}*

-   *[Scheduling processing required for the implementation]{.mark}*

-   *[Providing comprehensive support for the implementation]{.mark}*

-   *[Ensuring that all prerequisites have been fulfilled prior to the
    implementation date]{.mark}*

-   *[Arranging lodging, transportation, and office facilities for the
    implementation team, if required]{.mark}*

-   *[Providing computer support]{.mark}*

-   *[Providing priority scheduling to ensure adequate
    turnaround]{.mark}*

## 2.4 Conversion Strategy

Indicate in the conversion strategy the procedures for converting
existing automated and manual files. Include procedures for ensuring the
correctness of the data after conversion to prepare the plan for
approval by the appropriate organizations within HUD. Each task should
be under a separate section header, 2.4.1 through 2.4.x.

### 2.4.x \[Conversion Task Name\]

Identify and describe each conversion task in the sequence of the task's
execution. *[Some examples of conversion tasks are as follows:]{.mark}*

-   *[Converting existing automated files]{.mark}*

-   *[Converting existing manual files]{.mark}*

-   *[Staffing requirements and organization for conversion]{.mark}*

-   *[Checking accuracy of converted data]{.mark}*

-   *[Schedule for data conversion]{.mark}*

-   *[Organizations involved with data conversion effort and each
    organization's role in the effort]{.mark}*

-   *[Methods (e.g., meetings and communications) for keeping all
    organizations informed about the status of the conversion]{.mark}*

## 2.5 Overall Schedule

Provide a high level schedule for all sites, including start and end
times for conversion and implementation at each site depicting the
required tasks in chronological order.

## 2.6 Roles and Responsibilities

*[This section identifies the organizations directly involved with
system installation and conversion, each organization's role, and
methods (e.g., meetings, communications) for keeping each organization
informed about the status of the installation.]{.mark}*

### 2.6.1 Organizations and Roles

Identify the organizations directly involved with system installation
and conversion, each organization's role, and their information exchange
methods.

### 2.6.2 Personnel Requirements

Describe the number, staff hours, and skill category level of all
personnel required for the installation and conversion processes.
Include clerical, administrative, and functional personnel.

### 2.6.3 Training

Describe the type and amount of special training required to install and
convert the system, or to convert the existing system. Include personnel
and schedule requirements.

## 2.7 Master Inventory

List all items that may be required for system installation. List the
type, source, and quantity of materials required.

### 2.7.1 Software

Provide an inventory of the required software to be installed. Classify
the software, data, files, etc., by name, identification code or
acronym, and security classification. Indicate whether the software is
to be maintained on site or delivered for the installation. Identify any
software to be used to facilitate the implementation process.
Additionally, specify the configuration management process for software
if not described in the Configuration Management Plan.

### 2.7.2 Support Software

Provide an inventory of the software required to support the
installation and/or conversion. Classify the software, data, files, etc.
by name, identification code or acronym, and security classification.

### 2.7.3 Hardware

Provide an inventory of the required hardware to be installed. Classify
the hardware by type, make, model, serial or other individual
identification number, and security classification. Indicate whether the
software is to be provided on site or delivered for the installation.
Identify any hardware to be used to facilitate the installation.
Additionally, specify the configuration management process for hardware
if not described in the Configuration Management Plan.

### 2.7.4 Other

Provide an inventory of other materials and peripheral equipment
required for the implementation. Classify the objects by name, type,
make/model, identification number or code, and security classification.
Indicate whether the materials are to be maintained on site or delivered
for the installation. Include items such as tapes, diskettes, and
continuous form or printer paper. Identify any equipment to be used to
facilitate the installation. Specify the configuration management
process for all configuration items. *[Some of the factors to be
considered are:]{.mark}*

[]{.mark}

-   *[Additional climate control]{.mark}*

-   *[Wiring and power conditioning]{.mark}*

-   *[Physical security and access controls]{.mark}*

-   *[Floor plan]{.mark}*

-   *[Required supplies]{.mark}*

-   *[Classroom space needed]{.mark}*

-   *[Workspace required]{.mark}*

-   *[Training aids to enhance presentation]{.mark}*

-   *[Number of hours per day resources are required]{.mark}*

-   *[Number of days resources are required]{.mark}*

## 2.x \[Site Inventory Identifier\]

Provide a site inventory identifier here for reference in the remainder
of the section. Each site should be under a separate section header, 2.8
through 2.x.

### 2.x.1 Site Software

Provide an inventory of the required software to be installed at the
site. Classify the software, data, files, etc., by name, identification
code or acronym, and security classification. Identify any software to
be used to facilitate the installation process.

### 2.x.2 Site Support Software

Provide an inventory of the software required to support the
installation and/or conversion at the site. Classify the software, data,
files, etc., by name, identification code or acronym, and security
classification.

### 2.x.3 Site Hardware

Provide an inventory of the required hardware to be installed at the
site. Classify the hardware by type, make, model, serial or other
individual identification number, and security classification. Identify
any hardware to be used to facilitate the installation.

### 2.x.4 Other Site Inventory

Provide an inventory of other materials and peripheral equipment
required for the implementation. Classify the objects by name, type,
make/model, identification number or code, and security classification.
Indicate whether the materials are to be maintained on site or delivered
for the implementation. Include items such as tapes, diskettes, and
continuous form or printer paper. Identify any equipment to be used to
facilitate the implementation process. Specify the configuration
management process for all configuration items.

### 2.x.5 Site Support Facilities

Detail the physical facilities and accommodations required during the
installation (described in subsection 2.7.4) at the particular site.
*[Some of the factors to be considered are:]{.mark}*

[]{.mark}

-   *[Additional climate control]{.mark}*

-   *[Wiring and power conditioning]{.mark}*

-   *[Physical security and access controls]{.mark}*

-   *[Floor plan]{.mark}*

-   *[Required supplies]{.mark}*

-   *[Classroom space needed]{.mark}*

-   *[Workspace required]{.mark}*

-   *[Training aids to enhance presentation]{.mark}*

-   *[Number of hours per day resources are required]{.mark}*

-   *[Number of days resources are required]{.mark}*

### 2.x.6 Site Training

Describe the type and amount of special training required to install and
convert the system, or to convert the existing system at the site.
Include personnel and schedule requirements.

### 2.x.7 Site Implementation Team

If an implementation team at the site is required, specify its
composition and define the tasks of each of the members.

**3.0 SITE INFORMATION**

# SITE INFORMATION

## 3.x \[Site Identifier\]

Provide a site name and identifier here for reference in the remainder
of the section. Each site should be under a separate section header, 3.1
through 3.x.

### 3.x.1 Site Schedule

Present a detailed schedule of activities to be performed during
installation and/or conversion implementation at the site. Depict the
required tasks in chronological order with beginning and ending dates of
each task. Include supporting narrative as necessary.

### 3.x.2 Site-Specific Procedures

Provide in this section the sequence of steps and detailed procedures
required to perform the implementation at the site. Tailor the master
tasks identified previously to site-specific needs and the
implementation. Reference may be made to other documentation. Encompass
steps and procedures applicable in the following areas:

-   *[Control input]{.mark}*

-   *[Operating instructions]{.mark}*

-   *[Communications]{.mark}*

-   *[Database description]{.mark}*

-   *[Data conversion]{.mark}*

-   *[Output (including reports)]{.mark}*

-   *[Diagnostic messages]{.mark}*

-   *[Restart/recovery procedures installation]{.mark}*