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.12 Develop Initial Target State Concept of Operations
1.11 Understand As-Is Business Processes
1.13 Define Scope of Services, Document Initial Business Capabilities & Define Mission Critical Needs
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Customer Readiness Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective:   Define which processes and service layers are desired to be migrated to the provider versus retained to understand the Target State Concept of Operations and identify initial performance requirements.

   Phase 1 GuidanceResponsible Party - Customer, Provider, Shared
 Activities
1. Review in-scope process documentation (C)
2. Document initial mandatory business requirements that a provider must have to be able to support the organization’s mission and operations in the target state and validate with business owners (C)
3. Understand the as-is operating model including people, process, organization, and systems (C)
4. Validate and update as-is operating model with stakeholders (C)
5. Determine which business service layers are required, where they should be performed in the future (e.g., internally, with provider, shared) and determine the service type (i.e. Technology, Workforce, Advisory) (C)
6. Identify major processes that will be performed in the new solution, how users will interact with the solution, the future state operating model (which processes will be performed where in the future), and how the solution will be supporting during O&M (C)
7. Define the Initial Target State Concept of Operations for retained and modernized/migrated systems and processes, which includes the Initial Target State Systems Environment (C)
8. Report updates in governance meetings and Status Reports/Dashboards (C)

Inputs
• Vision
• Business Case
• As-Is Business Process Documentation
• As-Is Systems Environment
• Initial Target State Systems Environment
• Migration and O&M Training needs

Outputs
• Initial Target State Concept of Operations
Stakeholders Update
• Executive Sponsor (C)
• Business Owners (C)
• Program Manager (C)
• Functional Lead (C)
• Function SMEs (C)
• PMO Lead (C)
• PMO Team (C)

Best Practice
• Understand which processes should be retained versus migrated
• Understand which processes will have to change due to the migration to a shared environment
 
Related
Frequently Asked Question(s)

1-2. What level of detail should be provided in the Concept of Operations to effectively develop a full cost estimate for the customers need?

o The Target State Concept of Operations should clearly outline an ideal future state systems environment (including what service layers and systems the customers wishes to retain, which the customer hopes to obtain from a provider, and which the customer hopes to share), major processes that will be performed in the system and how users would interact with the system in the future, where processes are desired to be performed in the future between the customer and provider, how the system would be supported in the future, and operational scenarios.