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 4: Migration
4.14 Design and Develop Interfaces
4.13 Configure Systems
4.15 Design and Develop Reports
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Selection Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective: Design and develop interfaces between applications.

Phase 4 GuidanceLegend - Customer, Provider, Shared
1. Create or update Interface Control Documents to describe the functionality including data flow, security and controls, and transfer methods between various legacy systems (P)
2. Leverage standard interfaces and application programming interfaces (APIs) to create connections between applications (S)
3. Coordinate with the interface partner to collaborate and agree on data exchanges, integration methods and unit testing timeframes (S)
4. Code and unit test Interfaces (P)
5. Establish batch jobs to execute interfaces and conduct integration testing (S)

• Requirements Traceability Matrix (RTM)
• Target State Concept of Operations (CONOPS)
• Technical Strategy
• Gap Analysis Report
• Target State Concept of Operations

• Interface Control Document
• Program Manager (C, P)
• Technical Lead/Solution Architect (C, P)
• Development Team (C, P)
• Functional Lead (C, P)
• Network Subject Matter Expert (SME) (C, P)

Best Practice
• Maintain a detailed network architecture to help troubleshoot interface design and development issues
• Conduct frequent checkpoints with interfacing application developers between customer and provider
• Coordinate early with external interface providers to properly plan testing windows