Skip to content
Cycle Steward · independent PSAP workspace
Cycle Steward Portal
All guides

Two tracks, one cutover

Coordinate CPE with NG9-1-1 migration

CPE money does not buy network. Network money does not buy CPE. A refresh that lands in a migrating ESInet window still needs a joint kickoff so 9-1-1 does not drop.

Align CPE install clock with regional NG milestones

Flow

  1. 01 →

    Name the tracks

    CPE = call handling (MPA). Network = ESInet / NGCS (separate contracts).

  2. 02 →

    Read regional status

    Bridge vs migrating vs i3-live changes the coordination load.

  3. 03 →

    Pick one CPE model

    Cloud or on-prem — not both at one PSAP. Both must be i3-capable.

  4. 04 →

    SOW language

    Cite NENA i3 + Cal OES ICD. CAMA→i3 conversion at migration at no added State cost.

  5. 05 →

    Joint kickoff

    PSAP + CPE vendor + network provider + Advisor.

  6. 06 →

    Facility

    Power, HVAC, NG demarc. Site mods are typically PSAP-funded.

  7. 07

    Cutover plan

    Fallback, test calls, answer-time watch, outage SOP.

Checklist

0 of 8 complete

Required documents

  • CPE SOW
  • Network order / provider record
  • NG readiness guide
  • Cutover runbook
  • Chapter II / XI as needed

Common mistakes

  • 'Our network upgrade uses CPE money'

    Usually false. Different contracts and pots.

  • Skipping the network provider

    Install day is too late for a first introduction.

  • Deploying cloud and on-prem together

    New SOW does not allow both at one PSAP.