Overview#
Jurisdiction boundaries matter most when an incident is moving. A vehicle pursuit crosses from one PSAP area into another. A wildfire evacuation zone touches three agencies. A caller is near a boundary and the first dispatcher needs to know who else must be notified before seconds are lost. PSAP Geofence Dispatch Federation gives dispatch teams a shared, standards-based way to preview geographic responsibility and coordinate handoff or mutual aid.
The module combines geofence preview, jurisdiction matching, federation partner visibility, dispatch handoff context, and audit logging. Dispatchers can see which agencies are implicated by an incident area before they transfer, notify, or federate the call.
Key Features#
- Geofence Preview: Show which jurisdictions, response zones, mutual-aid areas, or special districts intersect an incident point or polygon before dispatch action is taken.
- Federated Dispatch Context: Package the incident summary, location, priority, caller context, resources requested, and handling notes for a partner agency.
- Partner Agency Visibility: Present candidate partner agencies based on geography, capability, and configured federation rules.
- Boundary-Aware Handoff: Reduce ambiguity when incidents occur near borders or move across agency areas.
- Mutual Aid Coordination: Support structured assistance requests while keeping each agency's own records and authority intact.
- Status Reconciliation: Track acknowledgements, acceptance, rejection, and follow-up status from partner agencies.
- Audit and Review: Record preview, selection, handoff, and acknowledgement actions for quality assurance and after-action review.
Use Cases#
- Cross-Boundary Pursuit: A pursuit crosses a jurisdiction line and the dispatcher can identify and notify the receiving PSAP with structured context.
- Wildfire Evacuation: A hazard polygon intersects multiple response zones, prompting federated coordination before public alerts are issued.
- Borderline Caller Location: A mobile caller plots near a PSAP boundary, and the call-taker can verify the responsible agency before transferring.
- Mutual Aid Request: A small agency requests specialist resources from a neighbouring agency with location, priority, and tasking preserved.
- Regional Exercise: Multiple dispatch centres run a simulated incident and review handoff timing, acknowledgement quality, and boundary logic afterward.
Integration#
PSAP dispatch federation connects to CAD incidents, geospatial layers, agency directories, mutual aid, resource requests, call session records, public alerting, and immutable audit logging. It complements existing PSAP interoperability by adding a geographic decision layer that makes handoff and federation choices visible before they are committed.
Open Standards#
- GeoJSON, RFC 7946: Incident areas, jurisdiction boundaries, and preview geometries are exchanged using a standard geographic format.
- WGS 84, EPSG:4326: Coordinates use the global latitude and longitude reference system expected by public safety mapping tools.
- NENA i3: Federation workflows align with modern IP-based emergency service architecture and PSAP routing concepts.
- EDXL-RM: Mutual aid and resource requests can align with the Emergency Data Exchange Language Resource Messaging model.
- NIEM: Incident and agency context can be mapped to National Information Exchange Model structures for interagency sharing.
- Common Alerting Protocol, OASIS CAP v1.2: Public alerting triggered by federated incidents can use CAP-compatible messages.
- ISO 8601: Preview, handoff, acknowledgement, and status timestamps use standard date-time formatting.
Last Reviewed: 2026-06-26 Last Updated: 2026-06-26