M3 Playbook > Phase 5: Operations > 5.6 Decommission Legacy Systems
5.5 Maintain Applications Post Go-Live
5.7 Conduct Continuous Process Improvement
5.6 : Decommission Legacy Systems
Technology
Objective
Retire legacy systems including hardware, software, licenses, interface, and close out support contracts.
View Lessons LearnedRecommended Best Practices
-
Customer
Once the Cutover Plan is complete, execute the Decommission Plan
-
Customer
Finalize plans for hardware disposition, software licensing, and contract end of life plan
-
Customer
Archive software, data, and documentations (security and access) necessary to bring back the system if required
-
Customer
Retire applications, databases, and hardware per requirements
-
Customer
Provide Decommission Report to appropriate stakeholders
5.6 Lessons Learned
- Build the Decommission Plan into the overall migration program to capitalize on cost reduction and operational improvements
Stakeholders
Recommended stakeholders, inputs, & outputs may vary by implementation; however, agencies that contributed to this Playbook reported these factors as increasing the likelihood of success.Customer
- Program Manager
- Business Owner
- Functional Lead
- Technical Lead/Solution Architect
- Security SME
- Network SME
- O&M Team
- PMO Lead
Inputs
- Cutover Plan
- Decommission Plan
Outputs
- Decommission Report
