# PSAP EIDO Context Augmentation

## Overview

An incoming emergency incident often needs more than caller details and a map pin. Dispatchers may need to know which nearby responders are already in range, whether a marine or aviation asset is relevant, and what partner-agency context should travel with the incident from the start. That is where incident augmentation becomes useful rather than just descriptive.

The EIDO Context Augmentation module enriches active incident objects with nearby responder, maritime, and aviation context so the dispatcher sees a broader operational picture immediately. It is built for PSAP workflows where the same incident may need to move across CAD, shared operational views, and NG911 / NG112-style call handling without losing context.

```mermaid
flowchart TD
    A[Active Emergency Call or Incident] --> B[Incident Location Established]
    B --> C[Nearby Responder and Asset Query]
    C --> D[Road Units]
    C --> E[Maritime Assets]
    C --> F[Aviation Assets]
    D --> G[EIDO Context Package]
    E --> G
    F --> G
    G --> H[Dispatcher Console and CAD]
    G --> I[Shared Operational Picture]
```

**Last Reviewed:** 2026-04-22
**Last Updated:** 2026-04-22

## Key Features

- **Incident-Linked Context Enrichment**: Attach surrounding operational context directly to the active incident rather than leaving dispatchers to query separate systems.

- **Nearby Unit and Asset Augmentation**: Surface relevant road, maritime, and aviation assets that may matter to the same incident area.

- **Cross-Domain Incident View**: Support calls that span land, coastal, and air environments without forcing each domain into its own disconnected workflow.

- **Operational Context for Complex Calls**: Give the dispatcher an earlier picture of the resources and partner entities already near the event.

- **Standards-Based Incident Packaging**: Keep augmented incident context aligned with open emergency incident object patterns.

- **Audit of Enrichment Inputs**: Preserve when external context influenced the live incident package.

## Use Cases

- **Coastal Emergency Dispatch**: A dispatcher sees nearby road, marine, and rescue-air assets relevant to a waterside incident.

- **Rural or Regional PSAP**: A remote centre can enrich a call with partner resources that may arrive from beyond the immediate road fleet.

- **Search and Rescue Escalation**: A live incident package carries nearby specialist assets into the operational picture from the outset.

- **Cross-Agency Incident Handover**: Enriched incident context travels with the case when another team or command role takes over.

## Integration

- **NG911 / NG112 Call Handling**: Augmented context can be attached to incident objects flowing through modern emergency communications workflows.

- **Dispatcher Console and CAD**: The enriched incident package becomes part of the operational view used for call-taking and dispatch.

- **AVL and Partner Asset Feeds**: Context augmentation draws from the normalised responder and partner-location sources already connected to the platform.

- **Shared Operational Picture**: The same enrichment can support wider command, multi-agency, and cross-domain views.

## Open Standards

- **NENA EIDO**: incident augmentation aligns with the emergency incident data object model used in modern emergency communications ecosystems.

- **OGC SensorThings API**: nearby responder and partner observations can be consumed using open geospatial and sensor-fusion patterns.

- **WGS 84 / EPSG:4326**: all incident and asset positions use the common latitude and longitude reference model expected by modern mapping systems.

- **HTTPS / TLS**: incident context moves using the standard secure web transport baseline.

- **JSON**: enriched incident objects remain easy to exchange across dispatcher, CAD, and partner systems using a common structured format.