Implementation of Interoperable Incident Data Interfaces (UCRI, WDX3 & EDXL-SitRep) #5

New issue

Open

opened 2026-03-02 09:16:46 +00:00 by jkeffects · 0 comments

jkeffects commented

2026-03-02 09:16:46 +00:00

Owner

Problem Description
Currently, incident reports must be filled out manually. To increase efficiency and data quality, the system should be able to receive incident data from CAD systems automatically.

Proposed Solution
Implement a modular interface architecture that supports modern standards (UCRI), legacy formats (WDX3), and an optional internal data model.

Core Requirements

UCRI Implementation
Implement a REST-compliant endpoint following the UCRI (Universal Control Room Interface) standard (JSON-based).
WDX3 Legacy Support
Create a "Compatibility Ingestor" for WDX3 (XML).
Since WDX3 varies by vendor, this should be implemented as a transformational middleware/module that maps XML fields to our internal data model.
Internal Generic Ingest API
A dedicated, well-documented JSON-API that reflects the internal data model.
This interface should be the most comprehensive, allowing data fields that might not be covered by UCRI.
Alignment with EDXL-SitRep (Situation Reporting) logic for structured situational updates.
Automated Reporting & PDF Workflow
Incoming data should pre-fill the incident report.
If no PDF is provided, trigger the internal PDF-Generator to create a draft report based on the received metadata.

**Problem Description** Currently, incident reports must be filled out manually. To increase efficiency and data quality, the system should be able to receive incident data from CAD systems automatically. **Proposed Solution** Implement a modular interface architecture that supports modern standards (UCRI), legacy formats (WDX3), and an optional internal data model. **Core Requirements** 1. UCRI Implementation Implement a REST-compliant endpoint following the UCRI (Universal Control Room Interface) standard (JSON-based). 2. WDX3 Legacy Support Create a "Compatibility Ingestor" for WDX3 (XML). Since WDX3 varies by vendor, this should be implemented as a transformational middleware/module that maps XML fields to our internal data model. 3. Internal Generic Ingest API A dedicated, well-documented JSON-API that reflects the internal data model. This interface should be the most comprehensive, allowing data fields that might not be covered by UCRI. Alignment with EDXL-SitRep (Situation Reporting) logic for structured situational updates. 4. Automated Reporting & PDF Workflow Incoming data should pre-fill the incident report. If no PDF is provided, trigger the internal PDF-Generator to create a draft report based on the received metadata.