Loss of communication with the panel.

Keedian loses its read connection to the fire-alarm panel — the panel's heartbeat is no longer received. The system's state can no longer be seen, so a supervisory or trouble condition arising during the outage would go unnoticed. For a life-safety system this is escalated, not assumed normal.

01 Detail

Trigger, action plan, and escalation criteria.

optimization_metric fire_safety urgent essential tier AI: hybrid

Related metric: fire_system_readiness
Trigger: panel_heartbeat lost for > comms_timeout (raises unmonitored escalation)
Value drivers: Operational continuity
Preconditions: A panel heartbeat / poll over the monitoring interface with a configurable comms_timeout, so a brief network blip is distinguished from a sustained loss of the feed.
Human role: Primary — Keedian detects the loss of the panel feed and escalates; restoring the panel interface is coordinated with the customer and the licensed provider. Operators confirm the loss is the integration and not a wider fault and drive it to restoration.
Action plan: (1) Confirm the loss is sustained past comms_timeout, not a transient network blip. (2) Escalate — a fire system Keedian cannot read is a compliance and safety gap; report the panel state as unknown rather than assumed normal. (3) Coordinate restoration of the interface with the customer and the licensed provider; keep the outage window on record.
Escalation: (1) Loss sustained beyond the agreed window → escalate to the customer immediately; do not hold for the routine report. (2) Recurrent loss on the same panel → flag the integration path (gateway, relay board, network) for a permanent fix.
Prevention: (1) Confirm the heartbeat / poll and comms_timeout per panel at onboarding. (2) Monitor the integration path health so a degrading link surfaces before it drops entirely.