<Enter Project Name> Disposition Plan

UNITED STATES MINT

Office of the Chief Information Officer (OCIO)

Version: Date:

Revision History Date mm/dd/yyyy Version 1.0 Description Initial publication. Custodian/Organization / OCIO

Note to Document Authors

Some text in this template appears in green. The green color indicates that the text is an instruction for completing the document, and should not appear in the final version. After you complete the associated portion of the document, delete any related green text. To improve the readability of your document, this template uses a pale yellow background to emphasize table headings. Do not change the background color in your final document. Be sure to delete this note box and its contents in your final document.

Version: Date:

Disposition Plan
<Enter Project Name>
Table of Contents
1. Introduction.....................................................................................................1 1.1 Project Description....................................................................................1 1.2 Assumptions and Constraints...................................................................1 1.3 Document Overview.................................................................................2 1.4 For Additional Information or Changes.....................................................2 2. Disposition Team............................................................................................3 2.1 Roles & Responsibilities...........................................................................3 2.2 Organization Chart....................................................................................4 3. System Disposition.........................................................................................5 3.1 Rationale..................................................................................................5 3.2 Notifications..............................................................................................5 3.3 Data Disposition........................................................................................5 3.4 Software Disposition.................................................................................5 3.5 System Documentation Disposition..........................................................5 3.6 Equipment Disposition..............................................................................5 3.7 Disposition Schedule................................................................................6 3.8 Future Access...........................................................................................6 4. Project Shutdown............................................................................................7 4.1 Project Staff..............................................................................................7 4.2 Project Records........................................................................................7 4.3 Project Facilities........................................................................................7 Appendix A: Glossary........................................................................................8 Appendix B: Reference Documents.................................................................9

Tables & Figures

Figure 1: Disposition Team Organization Chart...............................................4 Table 1: Roles & Responsibilities Matrix..........................................................3

Version: Date:

Disposition Plan
<Enter Project Name>

1. Introduction
The Disposition Plan describes how the various components of the system will be handled at the completion of operations, including software, data, hardware, communications, and documentation. The plan also notes any future access to the system. This section provides a brief overview of the information system to be disposed of, including a description of the system and its organization.

1.1

Project Description
Title

Section Project Name Project Code Primary Objective(s) Customer

<Provide a brief description of each objective in one or two sentences.> <List the organization for which this project is being developed.>

1.2

Assumptions and Constraints

This section presents all assumptions and constraints for the project. Assumptions are future situations, beyond the control of the project, whose outcomes influence the success of a project; for example: Availability of a hardware/software platform Pending legislation Court decisions that have not been rendered Developments in technology

Constraints are conditions outside the control of the project that limit the design alternatives; for example: Government regulations Standards imposed on the solution Strategic decisions

Version: Date:

Disposition Plan
<Enter Project Name>
1.3
Section 1 2

Document Overview
Title Introduction Disposition Team Describes The purpose and scope of this project, as well as information about this document. The key players and their roles, the structure of the disposition team, and project communications. The plan for an orderly system shutdown, ensuring that system components and data are properly archived or incorporated into other systems. The plan for an orderly notification and transfer of staff, and the proper handling of project records and facilities. Terms used in this document. External references used to prepare the Disposition Plan.

System Disposition

Project Shutdown

Appendix A Appendix B

Glossary Reference Documents

1.4

For Additional Information or Changes

The <Enter Project Name/Office> prepared this document, and will update the document in accordance with approved configuration control procedures. Suggested changes to this document should be submitted via SCR/CCR to a Configuration Management Specialist. Please forward all requests for additional information to: <Enter Project Manager> Name Office, OCIO United States Mint Phone: Email:

Version: Date:

Disposition Plan
<Enter Project Name>

2. Disposition Team
This section describes the disposition teams members, responsibilities, structure, and communication reporting.

2.1

Roles & Responsibilities

The following table identifies and describes the key players on the Disposition team. It is possible, and very likely, that a single individual may perform one or more of these roles. This is acceptable provided that separation of duties is enforced according to the US Mint Information Security Manual. <In the table below, insert the responsibilities, tasks, and/or activities that each role holds for establishing, performing, and evaluating the disposition functions on this project. Use the table below as a starting point, but customize it to reflect your project. In the future, the Project Managers Guide will contain suggested responsibilities for each defined role.> Table 1: Roles & Responsibilities Matrix Role Project Manager Project Sponsor Change Management Lead Configuration Management Specialist Configuration Management Tool Administrator Configuration Manager Data Owner Database Administrator Hardware Manager Hardware Specialist Quality Assurance Lead Person/Organization Responsibilities

Version: Date:

Disposition Plan
<Enter Project Name>
Role Quality Assurance Specialist Release Manager Security Analyst Software Test Librarian Subject-Matter Expert System Administrator System Owner Systems Analyst Technical Writer Test Lead Test Specialist Training Lead Training Specialist User Documentation Lead User Contact Person/Organization Responsibilities

2.2

Organization Chart

The chart below shows the reporting hierarchy of the key members on the Disposition team.

P T T T y p e y p e

r o je y p e

c t M n a m

a n a g e r e h e r e h e e h r e e r e

t i t l e T h y e p r e e t i t l e T h y ep r e e t i t l e a m T ey p h e e nr e a m T ey p h e e nr e a m

Figure 1: Disposition Team Organization Chart

Version: Date:

Disposition Plan
<Enter Project Name>

3. System Disposition
This section describes the plan for an orderly system shutdown, ensuring that system components and data are properly archived or incorporated into other systems

3.1

Rationale

This section describes the rationale for terminating system operation, including the events leading to the termination, the effective date, and any successor system.

3.2

Notifications

This section describes the plan for notifying users of the system shutdown.

3.3

Data Disposition

This section describes the plan for archiving, deleting, or transferring to other systems the data files in the system being shut down. If data will be transferred (converted) from existing systems to the new system as a result of this project, please refer to the Conversion Plan for more information.

3.4

Software Disposition

This section describes the plan for archiving, deleting, or transferring to other systems the software library files and related documentation in the system being shut down.

3.5

System Documentation Disposition

This section describes the plan for archiving, deleting, or transferring to other systems the hardcopy and softcopy systems and user documentation for the system being shut down. Project managers must submit reference copies of SDLC documentation to the COINS Library prior to going to production.

3.6

Equipment Disposition

This section describes the plan for archiving, deleting, or transferring to other systems the hardware and other equipment used by the system being shut down.

Version: Date:

Disposition Plan
<Enter Project Name>
3.7 Disposition Schedule

This section describes the plan for records management. <Note that: One year after a final decision is made, you can destroy or delete records for projects that are not implemented. Five years after a project is terminated, you can destroy records for projects that are implemented. Three years after final decision on acceptance is made, you can destroy installation and testing records. For records purposes, termination date is when you have deleted all data contained in the application according to approved records schedules, or you have migrated the data to a new or replacement system. As long as the data has not been deleted from the system, you should retain the documentation. For additional guidance, refer to NARA General Records Schedule 24. If you determine that record copies of documentation contain information that could have substantial future value, you can convert them to reference copies when their normal disposition date has passed.>

3.8

Future Access

This section describes the plan for future access to the software, data, and lifecycle documentation for the system being shut down. <Insert plan for future software access.> <Insert plan for future data access.> The OCIO Library will collect, maintain, and make available to Mint employees reference copies of system development lifecycle documentation. While most of this material will be made generally available, some may be restricted to more targeted audiences. The project manager will deliver electronic copies of this documentation to the library with a completed transmittal form at major milestones during a project or upon system implementation. Paper copies of documentation will be placed in the library only when adequate electronic copies do not exist. Project managers remain responsible for maintaining project documentation for records management purposes.

Version: Date:

Disposition Plan
<Enter Project Name>

4. Project Shutdown
This section describes the plan for an orderly notification and transfer of staff, and the proper handling of project records and facilities.

4.1

Project Staff

This section describes the plan for notifying project team members of the system shutdown, and the transfer of these team members to other projects.

4.2

Project Records

This section describes the plan for archiving, deleting, or transferring to other projects the records of project activity.

4.3

Project Facilities

This section describes the plan for transferring or disposing of facilities used by the project staff.

Version: Date:

Disposition Plan
<Enter Project Name>

Appendix A: Glossary
<Use this section to provide a glossary (in alphabetical order) of all terms, acronyms, and abbreviations used in this document.> Word Definition Word Definition Word Definition

Version: Date:

Disposition Plan
<Enter Project Name>

Appendix B: Reference Documents

Title Information System Life Cycle Manual Nomenclature Treasury Directive Publication (TD P 84-01), Version 3.2, March 2002 Version 1.1 May 2002 Version 2.0, June 2002 Version 3, June 2002

United States Mint SDLC OCIO United States Mint CM Standards and Procedures United States Mint Project Documentation Guide

Software Engineering Institute (SEI), Carnegie Mellon University, Key Practices of the Capability Maturity Model

<Add any references that you used to prepare this Disposition Plan. For example, these references might include cost-benefit analyses, existing documentation describing internal processes, or existing documentation of the system if the project is a conversion.>

Version: Date: