1. Review and understand contract language of legacy system to determine decommissioning activities, including licensing expirations, contract expirations, options to extend, etc. for both software and infrastructure contracts, and the O&M support contracts (S)
2. Identify application components (i.e. classify components to be decommissioned such as testing or production environments, systems user IDs, and business app) (C)
3. Ascertain hardware components - if applicable (i.e. ascertain where infrastructure is in its maintenance/resource life cycle) (C)
4. Pinpoint network devices (C)
5. Work with system owner, Agency Records Manager, and other key stakeholders of legacy system to establish how far back to archive data, what data will be migrated, and timelines for migration (C)
6. Identify network, software and hardware location/ownership (i.e. activities include but are not limited to population of assets, management of data stores and development and validation of assets) (C)
7. Prioritize decommission effort (i.e. which components are simple versus complex to offline) (C)
8. Identify failover/offline procedures (i.e. have components backup/archive current state been verified) (C)
9. Coordinate with agency IT Security office to identify guidelines for managing/cleansing the data (C)
10. Draft Decommission Plan with timelines and key activities for retiring legacy system (based on activities noted above) (C)
|
|
|
Phase 2 Guidance
Activities
Best Practice
2.7 Conduct Initial Data Cleansing
Inputs
Outputs
Stakeholders