Skip to main content
M3 Playbook > Phase 4: Migration > 4.8 Configure Systems
Play Icon

4.8 : Configure Systems

Technology
  1. Provider

    Document Configuration Workbook/Blueprint to understand data & system layouts

  2. Provider

    Create baseline system configuration and execute unit test to validate configuration changes

  3. Provider

    Assess and define batch jobs

  4. Provider

    Define and verify business process controls framework

  5. Shared

    Baseline and sign-off on functional and technical requirements

  6. Provider

    Develop functional and technical specifications for enhancement based on requirements

  7. Provider

    Code and unit test enhancements

  8. Shared

    Validate configuration & controls with customer Functional and Technical SMEs to validate enhancements meet needs

4.8 Lessons Learned

  • Leverage functional specifications to support contact center team, test case, script development, training development, and user guide development
  • Conduct Configuration Workbook validation after Conference Room Pilots (CRPs) to help the customer better understand the configuration options
  • Consider hiring or staffing independent Enterprise Resource Planning (ERP) experts to provide unbiased configuration alternatives for the customer

Stakeholders

Recommended stakeholders, inputs, & outputs may vary by implementation; however, agencies that contributed to this Playbook reported these factors as increasing the likelihood of success.

Customer

  • Functional Lead
  • Functional SME

Provider

  • Program Manager
  • Functional Lead
  • Functional SME
  • Technical Lead/Solution Architect
  • Configuration Lead
  • Development Team

Inputs

Outputs

Return to top

USSM.GSA.gov

An official website of the General Services Administration

Looking for U.S. government information and services?
Visit USA.gov