Overview#
Emergency communications centres rarely operate inside clean jurisdictional lines. A crash can sit on a border, a major event can overflow one dispatch centre's capacity, and the nearest available unit may belong to a partner agency. The PSAP Geofence and Dispatch Federation module helps call takers and dispatch supervisors preview jurisdictional coverage, understand partner readiness, and coordinate federated response without over-sharing sensitive operational data.
The module combines geofence preview, agreement-aware routing, federated fleet status, equipment readiness, and masked partner fields. Dispatch teams can see whether a proposed incident location falls inside a coverage agreement, which partners are available, and what level of information can be shared before escalation.
Key Features#
-
Geofence Preview: Dispatchers can preview jurisdictional boundaries, response zones, and agreement coverage before committing a routing or federation decision.
-
Agreement-Aware Federation: Shared-area handling reflects the active operational agreements between agencies, including coverage area, allowed incident classes, and permitted data sharing.
-
Federated Fleet Status: Partner availability can be displayed at the level allowed by agreement, such as unit readiness, service area, and response suitability without exposing unnecessary detail.
-
Equipment Readiness: Dispatch decisions can consider specialist equipment, vehicle capabilities, medical readiness, and communications constraints when routing to local or partner resources.
-
Masked Partner Fields: Sensitive operational data is minimised in the federated view until policy, agreement, and incident context justify broader sharing.
-
Surge Support: During high-load events, supervisors can identify partner capacity, coverage overlaps, and fallback routing options more quickly.
-
After-Action Traceability: Geofence matches, partner views, federation decisions, and data-sharing actions are recorded for review and improvement.
Use Cases#
- Border incidents where the closest practical response may cross a municipal, county, or agency line.
- Major event surge where temporary federation agreements allow partner PSAPs to support call handling or dispatch coordination.
- Specialist resource dispatch where the relevant equipment or trained crew belongs to a partner agency.
- Coverage dispute review where supervisors need to understand why an incident was routed locally, shared, or escalated.
- Privacy-preserving collaboration where agencies coordinate readiness without exposing full unit rosters, locations, or sensitive call details unnecessarily.
Integration#
The module works with incident intake, mapping, dispatch recommendations, partner-agreement configuration, fleet status, equipment readiness, and audit reporting. It is designed to show operationally useful federation context without turning every partner integration into full data replication.
Open Standards#
- NENA i3 and EIDO: Next-generation emergency communications concepts and emergency incident data models inform incident exchange and interoperability expectations.
- GeoJSON (RFC 7946): Geofence boundaries, service areas, and preview overlays can use a widely supported geospatial interchange format.
- PIDF-LO (RFC 4119 and RFC 5491): Location objects for emergency services can align with established presence and civic-location standards.
- ISO 19115: Geospatial metadata concepts support provenance and quality information for jurisdictional boundaries and coverage layers.
- CloudEvents: Federation state changes and operational events can be represented using a standard event envelope when shared with downstream systems.
- OAuth 2.0 and JWT: Partner-to-partner trust can use standard token-based authentication and signed claims without exposing product-specific implementation details.
- ISO 8601: Incident, readiness, agreement, and after-action timestamps use a consistent time format across agencies.
- WCAG 2.2: Map overlays, readiness indicators, and dispatch controls support accessible operator workflows.
Security and Compliance#
Federated dispatch is governed by explicit agreements, masked fields, role-based access, and audit logs. The module minimises data sharing by default, records why partner context was shown, and keeps routing decisions reviewable for supervisors and after-action teams.
Last Reviewed: 2026-06-25 Last Updated: 2026-06-25