Knogin
[Developers]

Live Unit-on-Incident Command Board

Give your watch-commander a single screen that shows every active incident, every available and assigned unit, and exactly how much response-window time remains, without switching tabs or manually refreshing a list.

Back to All Modules
Category: ModulesLast Updated: May 5, 2026
modulesreal-timecompliance

Overview#

Give your watch-commander a single screen that shows every active incident, every available and assigned unit, and exactly how much response-window time remains, without switching tabs or manually refreshing a list.

The Live Unit-on-Incident Command Board is a real-time operational grid purpose-built for the watch-commander role. Every active incident and every available or assigned unit appears together in one view, with SLA timer chips colour-banded to the ISO 22324 public-warning colour convention. The board supports drag-to-assign dispatch, hover-to-preview, and click-through to the canonical incident detail, so a free unit can be moved onto an incident and the full case opened without leaving the command surface.

Key Features#

  • Single-Screen Operational Picture: Every active incident and every available or assigned unit appears in one grid built for the watch-commander role, removing the need to flick between separate tools.

  • ISO 22324 SLA Colour Banding: Response-window timer chips progress through green, amber, and red bands so time-critical incidents stand out immediately without the operator scanning raw numbers.

  • Drag-to-Assign Dispatch: A free unit can be dragged onto an incident cell to dispatch it. The assignment flows through the canonical dispatch path rather than a parallel write, preserving a single source of truth.

  • Hover-to-Preview and Click-Through: Hovering a cell surfaces an incident snapshot; clicking opens the full canonical incident detail view in the same motion, minimising navigation steps under pressure.

  • Real-Time Subscription with Periodic Re-Authentication: The board subscribes to the live incident channel and re-authenticates on a short rolling interval, keeping the session secure without interrupting the display.

  • Debounced High-Frequency Event Coalescing: High-volume position and status events are coalesced with a minimum debounce window, allowing a single board to support hundreds of concurrent viewers without flicker or wasted renders.

  • Pure Projection of Canonical State: The board never writes its own state. Every cell is sourced from the canonical incident record, dispatch assignment, vehicle position, ePCR encounter, or handoff link, so the view cannot drift from the authoritative record.

  • Auditable SLA Threshold Events: A dedicated SLA-timer worker emits amber and red threshold crossings as first-class timeline events, making colour-state changes auditable rather than purely visual.

  • Accessible Command-Centre Display: The grid targets W3C WCAG 2.2 AAA conformance and uses W3C ARIA Live Regions so assistive technology announces real-time changes alongside the visual update, supporting extended-duty operational environments.

Use Cases#

Ambulance Watch-Commander Oversight#

A duty commander sees the entire active caseload, unit availability, and time pressure on each incident from a single grid, reducing the cognitive load of managing multiple tools simultaneously.

Surge and Major Incident Coordination#

During a demand spike the board makes free capacity and at-risk SLA timers visible at a glance so resources can be reallocated deliberately, with no manual interrogation of separate systems.

Cross-Shift Handover#

An incoming watch-commander reads the live state of every incident and unit without paging through tickets or reports, cutting handover time and reducing the risk of missed context.

Multi-Watcher Operations Floor#

Supervisors, planners, and observers can all subscribe to the same board concurrently and receive the same low-latency view. Event coalescing and the canonical projection keep everyone aligned without additional infrastructure.

Dispatch Action from the Command Surface#

A commander spotting an idle unit near an amber-banded incident can drag the unit onto the incident directly, without switching to a separate dispatch tool, reducing response time.

Integration#

The board integrates with the Knogin Argus platform through standard developer-facing interfaces.

  • Live GraphQL Subscription: The board consumes a real-time GraphQL subscription channel that delivers canonical incident and unit state as events arrive. Developers can attach their own subscribers to the same channel to drive external dashboards or reporting tools.

  • OAuth 2.0 and JWT Authentication: All subscription and mutation calls are authenticated with scoped bearer tokens issued by the platform's OAuth 2.0 authorisation service. Tokens carry organisation and role claims that enforce per-tenant data boundaries at the transport layer.

  • Canonical Incident Projection: The board reads from the platform's canonical incident model, which normalises data arriving from heterogeneous ingress channels (PSAP voice, NG911, TETRA, mobile, alert, and external webhooks) into a single consistent shape before the board ever sees it.

  • Dispatch Mutations via GraphQL: Drag-to-assign actions are submitted as standard GraphQL mutations against the platform's unified command schema, which validates JESIP-compliant command structure and per-tenant data sovereignty before committing the assignment.

  • CloudEvents Timeline: State-change events emitted by the board's SLA timer and by the canonical incident pipeline use the CloudEvents 1.0 envelope, making them consumable by any CloudEvents-compatible subscriber outside the platform.

  • Per-Organisation State Aggregation: Board state is aggregated on a per-organisation basis at the platform tier, so each watch-commander's view is scoped to the incidents and units within their authorised organisational boundary.

  • Webhook and External System Fanout: The same live-incident event stream that drives the board can be fanned out to external command systems or CAD integrations via configured webhooks, supporting interoperability with third-party platforms.

Open Standards#

  • ISO 22324: SLA timer colour banding follows the ISO 22324 public-warning colour convention (green, amber, red), communicating urgency without language dependence.

  • ISO 22320: The board's command and coordination model aligns with ISO 22320 (Emergency Management, Incident Command System), including the role and resource structures used for dispatch and command assignment.

  • ICS / JESIP: The unified command framework underlying the board enforces Incident Command System (ICS) role structure and validates Joint Emergency Services Interoperability Programme (JESIP) compliance requirements for multi-agency dispatch.

  • CloudEvents 1.0: All timeline events, including SLA threshold crossings and state changes, are wrapped in the CNCF CloudEvents 1.0 envelope, enabling standard consumption by any CloudEvents-compatible subscriber.

  • EDXL-SitRep: Canonical incident state values (notified, assessing, etc.) are mapped to the Emergency Data Exchange Language Situation Report (EDXL-SitRep) state vocabulary, supporting inter-system interoperability.

  • EDXL-RM: External webhook ingress from other command systems can carry EDXL Resource Messaging (EDXL-RM) payloads, which the platform normalises into the canonical incident model before surfacing on the board.

  • NG911 / i3 ESInet (NENA i3): The underlying incident ingress layer accepts NG911 SIP signals from i3 Emergency Services IP Networks, meaning incidents originating from Next Generation 9-1-1 infrastructure appear on the board automatically.

  • TETRA SDS: Incidents arriving via TETRA Short Data Service messages are normalised and surfaced on the board alongside those from other ingress channels.

  • AsyncAPI 2.6: The live incident WebSocket subscription channel is documented using the AsyncAPI 2.6 specification, allowing external developers to discover, validate, and integrate against the live feed using standard tooling.

  • GraphQL (June 2018 specification): All board queries, mutations, and subscriptions are exposed through a typed GraphQL schema, giving integrators strong contracts and introspection capability.

  • OAuth 2.0 (RFC 6749) and JWT (RFC 7519): Platform authentication uses OAuth 2.0 authorisation flows with signed JWT bearer tokens for secure, scoped access to board subscriptions and dispatch mutations.

  • W3C WCAG 2.2 (AAA): The command-centre display targets the highest Web Content Accessibility Guidelines conformance level, ensuring usability in extended-duty and high-stress operational environments.

  • W3C ARIA Live Regions: Real-time board updates are announced through ARIA Live Regions so the surface remains fully usable with screen readers and assistive technology, not only as a visual display.

Security & Compliance#

Per-tenant data sovereignty is enforced at every layer: the OAuth 2.0 token's organisation claim is validated against the request body on every mutation, and the board's state aggregation is scoped so one organisation's incidents and units are never visible to another. SLA threshold crossings are persisted as first-class auditable timeline events, satisfying audit-trail and data-lineage requirements. All WebSocket sessions are secured with short-lived signed tokens and re-authenticated on a rolling interval to limit the exposure window of any compromised credential.

Last Reviewed: 2026-05-05 / Last Updated: 2026-05-05

Ready to Build?

Get started with our APIs or contact our integration team for support.