9.2 Disposition Plan

---

The objectives of the Disposition Plan are to end the operation of the system in a planned, orderly manner and to ensure that system components and data are properly archived or incorporated into other systems. This will include removing the active support by the operations and maintenance organizations. The users will need to play an active role in the transition. All concerned groups will need to be kept informed of the progress and target dates. The decision to proceed with disposition will be based on recommendations and approvals from the BROC or based on a date (or time period) specified by the SPMO.

This plan will include a statement of why the application is no longer supported, a description of replacement/upgrade, a list of tasks/activities (transition plan) with estimated dates of completion, and the notification strategy. Additionally, it will include the responsibilities for future residual support issues: identification of media alternatives if technology changes; new software product transition plans; alternative support issues (once the application is removed); parallel operations of retiring and the new software product; archiving of the software product, associated documentation, movement of logs and code; and accessibility of archive, data protection identification, and audit applicability. Finally, the plan should include the five closeout actions listed in the next section.

---