Overview#
Command centres and field teams both need their screens to reflect the real world as it changes, not five minutes after it changes. The Operations WebSocket module delivers live operational events directly to dashboards, mobile devices, and coordination surfaces, keeping outage maps, crew locations, work queues, and safety signals current without any polling delay. Every stream is tenant-scoped, and session security scales up for long-lived operational channels.
Key Features#
- Tenant-Scoped Event Streams: Deliver live operational events only to the organisations and users entitled to receive them
- Persistent Real-Time Channels: Keep dashboards, field workflows, and coordination surfaces current without polling-driven delay
- Encrypted Session Establishment: Support stronger protection when long-lived operational channels are created and maintained
- Operational Event Coverage: Stream outages, work orders, crew movement, telemetry alarms, emergency events, and safety alerts through one transport model
- Resilient Reconnection: Restore live context cleanly after intermittent connectivity loss in control rooms or field environments
- Field and Command Readiness: Serve both desktop operations surfaces and mobile or field-execution experiences
- Delivery Governance: Preserve the access controls and operational boundaries required for live multi-tenant systems
Use Cases#
Relevant sectors include critical infrastructure, law enforcement, and defence.
- Live Operations Monitoring: Keep command and operations dashboards current as incidents and assignments evolve
- Field Coordination: Push the latest work, outage, location, and safety context to field users without manual refresh
- Persistent Command Workspaces: Maintain live state inside decision-support and mission-control environments
- Secure Real-Time Services: Support deployments that require stronger trust in long-lived operational channels
Integration#
- Operational dashboards, mobile responder, and mission-control workspaces
- Alerting, outage, work-order, telemetry, and safety services
- Secure-session and post-quantum protection workflows
- Identity, access-control, and audit-governance systems
Open Standards#
- RFC 6455 (WebSocket Protocol): The sole transport layer; close codes (e.g., 1008 policy violation for origin and authentication failures) are used directly per the specification.
- JSON (ECMA-404 / RFC 8259): All operational event messages, work orders, outages, crew locations, alarms, lone-worker alerts, are serialised and exchanged as JSON text frames over the WebSocket connection.
- JWT (RFC 7519): Session authentication is performed by validating a JWT carried in a secure HTTP-only cookie before the WebSocket upgrade is accepted.
- NIST FIPS 203 (ML-KEM-768 / Kyber-768): Post-quantum key encapsulation mechanism used in the hybrid per-session key exchange to protect against harvest-now-decrypt-later attacks.
- NIST FIPS 204 (ML-DSA-65 / Dilithium-3): Post-quantum digital signature scheme combined with ECDSA-P256 to provide hybrid signing for session integrity.
- NIST FIPS 197 / SP 800-38D (AES-256-GCM): Authenticated encryption applied to sensitive message types (profile updates, investigation events, entity notifications) once the session key is established.
- GraphQL Subscriptions Specification: Queue-based topic subscriptions back the GraphQL real-time subscription transport, enabling clients to receive operational events through a standards-aligned subscription model.
Last Reviewed: 2026-03-25 Last Updated: 2026-04-14