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 3: Engagement
3.14 Develop Integrated Technical Strategy
3.13 Finalize Target State Systems Environment
3.15 Prepare Data for Mock Conversions (Data Cleansing, Data Mapping
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Selection Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective: Develop the IT strategy to define the overall management and execution approach to system enhancements and implementation.

Phase 3 GuidanceResponsible Party - Customer, Provider, Shared
Based on the fit-gap analysis and finalized Target State Systems Environment, develop the Migration Plan, including the approach for technical components: 1. Develop Business Intelligence (BI) and Data Warehouse Strategy (S)
2. Develop reports strategy including BI development
standards and tool analysis (S)
3. Develop Interface Strategy (S)
4. Develop Enhancement Strategy (S)
5. Update plan to decommission systems post-migration (C)
6. Document development controls (S)
7. Document configuration and workflow strategy (S)
8. Develop Configuration Management/Change Request Process (S)
9. Document Continuity of Operations (CooP) and Disaster Recovery Plan (S)
10. Develop Test Plan (S)
11. Report updates in governance meetings and Status Reports/Dashboards (S)

• Target State Concept of Operations
• Target State Systems Environment
• Business Intelligence and Data Warehouse Strategy

• Test Plan
• Configuration Management Plan
• CooP and Disaster Recovery Plan
• Interface Strategy
• Enhancement Strategy
Stakeholders Update
• Program Manager (C, P)
• Business Owners (C, P)
• Functional Lead (C, P)
• Technical Lead/Solution Architect (C, P)
• Interface Lead (C, P)
• Data Conversion Lead (C, P)
• Functional SMEs (C, P)
• Technical SMEs (C, P)
• Change Management Lead (C, P)
• PMO Lead (C, P)

Best Practice
• Conduct a thorough analysis early to determine which existing reports are still in use and need to be included in requirements
• Minimize enhancements, leverage bolt-ons where possible, to help ease patch/fix application and upgrade path