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 1: Readiness
1.9 Define As-Is and Initial Target State Systems Environments
1.8 Understand As-Is Workforce
1.10 Plan and Conduct Initial Data Quality Assessment
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Customer Readiness Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective:    Understand and validate the As-is Systems Environment, including applications, interfaces, data management, and security needs, and draft the initial high-level Target State Systems Environment.

Phase 1 GuidanceLegend - Customer, Provider, Shared
 Activities
Understand the As-is Systems Environment
1. Validate as-is application landscape (C)
2. Validate as-is interface inventory (C)
3. Validate IT architecture (C)
4. Validate data flows (C)
Define Initial Target State Systems Environment as part of the Initial Scope of Services desired from the migration
1. Determine functionality and systems to migrate to the provider and those that will be retained (C)
2. Identify required business intelligence capabilities and legacy data management strategy to support reporting needs (C)
3. Identify required interfaces based on mandatory organization activities (C)
4. Document the initial capabilities to be included in the Initial Target State Concept of Operations (C)

Inputs
• Vision
• Business Case
• Existing Enterprise Architecture Documents & System Specifications

Outputs
• As-Is Systems Environment
• Target State Systems Environment
Stakeholders Update
• Business Owner (C)
• Program Manager (C)
• Functional Lead (C)
• Technical Lead/Solution Architect (C)
• Interface Lead (C)
• Functional Subject Matter Expert (SME) (C)
• Technical SME (C)

Best Practice
• Begin with the current systems architecture and specification documents to understand as-is systems environment
• Assess the data needs for business intelligence capabilities between mission and mission-support systems
• Assess current capabilities to help determine whether the capability should be developed internally or migrated to the provider