NG911 Core Services Recurring Data Updates (FY26 Q4)

[chriswnek]

Benefit

Recurring updates will ensure that 911 call-routing is based on the latest PSAP boundary and addressing data

Acceptance Criteria

• Data is updated to account for municipal boundary changes, new address points, and new roads
• Data is pushed from Spatial Station ArcMap add-in or sent to 911 Datamasters/Motorola Solutions
• Data is staged in Spatial Central
• Data is imported from Spatial Central

Notes

• Main data layers to update in priority order:
  • PSAP Boundaries
  • Address Points
  • Road Centerlines
  • Law Boundaries (as time allows)
• Dependencies:
  • Visual Studio 22 installed and all are scripts working
  • Address point updates
  • Road centerline updates
  • Municipal boundary updates

Process is outlined in the Update NG911 Dataset document

Risks

• Delayed updates could cause 911 call-routing issues
• Bad data from an update could degrade 911 call-routing
• Issues with data scripts or software installs

Issue Reference

• NG911 Core Services Recurring Data Updates (FY26 Q3) #850

[eneemann]

FY26Q4 Sprint 1

• Completed routine updates for address points and road centerlines

[eneemann]

FY26Q4 Sprints 3-4

• Completed rebuild of PSAP boundaries to account for recent annexations
  • Filled out change request form and send to UCA, Motorola, cell carriers
  • Published web app showing new boundaries
  • Awaiting data to be staged in SpatialCentral
  • Target implementation date of 6/16/2026
• Reviewed and updated statewide emergency service boundaries (Law, Fire, EMS)
  • Coordinated with UCA/Motorola for PSAP to review boundaries and provide feedback for adjustments
  • Published web app for PSAPs to review data and created spreadsheet for change tracking
  • Recorded video describing web app and spreadsheet to guide PSAP reviews

[eneemann]

FY26Q4 Sprints 4-5

• Updates and coordination on statewide emergency service boundaries (Law, Fire, EMS)
• PSAPs providing inputs and request adjustments
• Edits made and annotated in the spreadsheet for change tracking
• Topology reviewed and cleaned up
• 4-5 PSAPs have not responded yet, awaiting guidance from UCA/Motorola on whether or not send latest data or wait

[eneemann]

FY26 Q4 Sprint 6

• PSAP boundary update to capture recent annexations imported on 6/16/2026
• All PSAPS confirmed emergency response boundary updates
• Submitted new geodatabase to Motorola for Vesta NXT Router preparation
  • Includes updated and reviewed Fire, Law, and EMS boundaries
  • Imported into NG911 Core Services on 6/24
• Created new PSAP boundary dataset for upcoming Davis-Layton consolidation (30 Sep)
  • Includes buffers around freeways through Bountiful PSAP boundary for routing to Layton
  • Published web app for PSAPs to review
  • Drafted MOP Change Request document to submit 90 days prior to implementation