Skip to main content

M3 Framework Introduction M3 Framework Overview M3 Phase 0 - Assessment M3 Phase 1 - Readiness M3 Phase 2 - Selection M3 Phase 3 - Engagement M3 Phase 4 - Migration M3 Phase 5 - Operations M3 Resources
M3 Playbook > Phase 5: Operations
5.6 Decommission Legacy Systems
5.5 Maintain Applications Post Go-Live
5.7 Conduct Continuous Improvement
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Customer Readiness Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective: Retire legacy systems including hardware, software, licenses, interface, and close out support contracts.

Phase 5 GuidanceResponsible Party - Customer, Provider, Shared
Activities
1. Once the Cutover Plan is complete, execute the Decommissioning Plan (C)
2. Develop hardware disposition, software licensing, and contract end of life plan (C)
3. Archive software, data, and documentations (security and access) necessary to bring back the system if required (C)
4. Retire applications, databases, and hardware per requirements (C)
5. Provide Decommissioning Report (C)

Inputs
• Cutover Plan
• Decommissioning Plan

Outputs
• Decommissioning Report
Stakeholders Update
• Program Manager (C)
• Business Owners (C)
• Functional Lead (C)
• Technical Lead/Solution Architect (C)
• Security SMEs (C)
• Network SMEs (C)
• O&M Team (C)
• PMO Lead (C)

Best Practice
• Build decommissioning plan into the overall migration program to capitalize on cost reduction and operational improvements