Overview#
A vehicle pursuit that starts in one jurisdiction and crosses into two others within four minutes is a routine interoperability test. If the second jurisdiction doesn't know it's coming, units are scrambling. If the third has an incompatible radio system, their dispatcher can't communicate with the pursuing officers at all. The PSAP Interoperability module exists to close those gaps before they cost time or lives.
The module establishes standardised data exchange and communication pathways between PSAPs and partner agencies, ensuring all responders access consistent, real-time incident information regardless of which system they use. CAD-to-CAD integration, cross-jurisdiction dispatch coordination, radio interoperability, and resource sharing across 40+ partner agencies connect through standardised protocols, replacing the communication silos that delay multi-agency response with a unified regional approach to public safety coordination.
Key Features#
- Multi-Agency Data Sharing: Standardised NIEM-compliant data exchange between PSAPs and partner agencies with automatic incident sharing based on geographic, incident type, and priority rules, real-time update propagation, and data translation between disparate CAD systems
- Cross-Jurisdiction Dispatch: Seamless dispatch coordination across jurisdictional boundaries with automatic call routing and transfer, geographic boundary management, coordinated multi-PSAP response, and border area incident handling
- Radio Interoperability: Radio over IP gateways connecting incompatible radio systems (P25, NXDN, DMR, analog) with tactical interoperable communications channels, dispatcher-controlled patches, and National Interoperability Field Operations Guide (NIFOG) channel support
- Mutual Aid Coordination: Automated mutual aid request workflows with configurable trigger rules, resource availability tracking across all partner agencies, response time estimates, and cost allocation tracking for resource sharing agreements
- Hospital & Healthcare Integration: Real-time emergency department bed availability, specialty capability tracking, diversion status, pre-arrival notifications for critical patients, and recommended hospital routing based on patient condition
- Utility & Infrastructure Coordination: Integration with power, gas, water, and transportation agencies for outage notifications, road closure sharing, traffic signal alerts, and coordinated public safety response to infrastructure emergencies
- School & Campus Integration: Emergency notifications to school districts for nearby threats, floor plan and key holder access in dispatch systems, student population data for evacuation planning, and school resource officer coordination
- FirstNet & Broadband Communications: Priority LTE and 5G connectivity for first responders with Mission Critical Push-to-Talk over cellular, mobile CAD interfaces, video streaming from body cameras, and situational awareness applications
Use Cases#
- Multi-Agency Incident Response: Automatically share incident data, unit status, and resource availability across all involved agencies when incidents cross jurisdictional boundaries or require multi-agency coordination
- Vehicle Pursuit Coordination: Automatically notify adjacent jurisdictions during pursuits with real-time location sharing, upcoming jurisdiction pre-arrival notification, and coordinated termination and post-pursuit reporting
- Regional Fire Mutual Aid: Execute pre-planned box alarm mutual aid with automatic unit requests by alarm level, coordinated staging, shared incident command, and resource tracking across participating fire departments
- Mass Casualty Triage: Pool regional EMS resources, coordinate hospital destinations based on real-time bed availability and specialty capabilities, and manage patient transport across jurisdictions
- Consolidated PSAP Operations: Support single-PSAP or virtual consolidation models where multiple jurisdictions share call-taking resources while maintaining individual agency identity for radio dispatch and resource management
Integration#
The module connects with partner agency CAD systems for incident sharing, radio systems and gateways for voice interoperability, GIS systems for jurisdictional boundary data, hospital emergency department status systems, utility company notification systems, transportation agency road closure feeds, and school district emergency notification platforms. Supports NIEM, CAP, EDXL, NENA i3 for NG911, NG112-aligned emergency IP interoperability patterns, and P25 interoperability standards.
Open Standards#
- NENA i3 (NENA-STA-010.3): The module routes emergency calls through i3-compliant Emergency Services IP Networks, implementing the Border Control Function, Emergency Services Routing Proxy, and Emergency Call Routing Function as defined in NENA-STA-010.3.
- NENA Emergency Incident Data Object (EIDO, NENA-STA-021): Cross-agency CAD-to-CAD incident sharing uses EIDO-structured payloads, enabling standardised incident, location, agent, and person objects to be exchanged between disparate systems.
- NIEM 6.0 JSON (National Information Exchange Model): CAD incident records exported to partner agency systems are serialised as NIEM 6.0 JSON, providing a common information model for public safety data exchange across jurisdictions.
- OASIS EDXL-DE 2.0 / EDXL-HAVE / EDXL-TEP / EDXL-SitRep: Federation peer notifications, hospital bed-availability feeds, patient-tracking payloads, and situation reports are wrapped in OASIS Emergency Data Exchange Language envelopes for standards-compliant distribution.
- OASIS Common Alerting Protocol (CAP) 1.2: Alerts and mutual-aid notifications issued to partner agencies, school districts, and utilities are emitted as signed CAP 1.2 XML documents.
- APCO Project 25 (P25 / TIA-102): Radio interoperability gateways connect P25 talkgroups with DMR, NXDN, and analogue radio systems, using Project 25 talkgroup management and inter-RF-subsystem interfaces.
- ETSI TETRA (TS 100 392-2): TETRA SDS messages and GPS polls follow ETSI TS 100 392-2 framing, with Individual Short Subscriber Identity (ISSI) addressing used for unit tracking and dispatch across TETRA networks.
- RFC 5222 (LoST) / RFC 4119 + RFC 5491 (PIDF-LO): Call routing to the correct PSAP jurisdiction is resolved by posting PIDF-LO location objects to an RFC 5222 LoST server, enabling accurate cross-boundary service lookup.
Last Reviewed: 2026-01-09 Last Updated: 2026-01-09