Overview#
During a major storm, a national emergency coordinator needs to know at a glance how many outages, PSAP events, and lone worker alerts are active across all participating utilities, without seeing the individual records of any single organisation. The National Telemetry domain delivers exactly that view: aggregate-only data from consenting tenants, with access restricted by role and every query written to an audit trail.
Key Features#
- Cross-tenant aggregate dashboards for national-level situational awareness
- Per-organisation consent management with granular category controls
- Four aggregate categories: outage, telemetry alarms, PSAP events, and worker safety
- National dashboard totals with consenting tenant count
- Role-based access control with four permitted national roles
- Access audit logging for all national queries
- Consent grant and revoke operations with history preservation
- Aggregate-only data sharing to prevent individual record exposure across tenants
Use Cases#
Relevant sectors include critical infrastructure, national emergency coordination, and public safety communications.
- Providing national emergency coordinators with a cross-organisation situational overview
- Managing per-organisation consent for voluntary data sharing participation
- Monitoring aggregate outage, alarm, PSAP, and worker safety metrics across multiple utilities
- Auditing access to national-level data for compliance and oversight
Integration#
The National Telemetry domain integrates with Outage Management for outage aggregates, Utility Telemetry for alarm data, PSAP for event summaries, and Lone Worker for worker safety metrics. It uses role-based access from the user domain for national query authorisation.
Open Standards#
- GraphQL (June 2018 specification): all national telemetry queries and mutations are exposed as a typed GraphQL API, with Strawberry-generated schema types for each aggregate category and explicit permission classes on every resolver.
- JSON Web Token (RFC 7519) with RS256 / JSON Web Key Sets (RFC 7517): every request to the national dashboard is authenticated by verifying an RS256-signed JWT against a JWKS endpoint; the platform rejects any token that does not use RS256.
- OAuth 2.0 Bearer Token Usage (RFC 6750): the JWT is presented as a Bearer token in the Authorization header, conforming to the OAuth 2.0 bearer token framework for API access control.
- Role-Based Access Control (NIST SP 800-207 / INCITS 359-2004 RBAC): access to cross-tenant aggregates is gated on four defined national roles (including NATIONAL_EMERGENCY_COORDINATOR), enforced via a centralised RBAC service evaluated on every query and mutation.
- GDPR (EU Regulation 2016/679): the per-organisation consent model implements explicit opt-in, granular per-category controls, revocation with timestamped history, and an access audit trail, all of which align with GDPR lawful-basis and accountability requirements for cross-organisational data sharing.
- NENA NG9-1-1 / NENA-STA-010.3 (Emergency Incident Data Object): the PSAP aggregate category surfaces counts derived from NENA EIDO-compliant incident records ingested by the upstream PSAP domain, preserving interoperability with NG9-1-1 dispatch systems.
- SQL:2011 (ISO/IEC 9075): aggregate-only data sharing is implemented entirely through PostgreSQL materialised views refreshed via a standard SQL function, ensuring individual tenant records are never exposed across the cross-tenant boundary.
Last Reviewed: 2026-02-24 Last Updated: 2026-04-14