Typical scenario

The first alarm was treated as the exact time the fire started

If a fire review identifies the panel's first message as the ignition time, the timeline may need clarification. Smoke appears earlier on video, but camera and panel clocks may differ. The export also combines alarm, fault and operator-acknowledgment messages without explaining what each event means.

What needs to be clarified

Determine which time boundaries independent records support, distinguishing system registration of a signal from the inferred start of burning and the operator's subsequent actions in the available materials.

Materials to prepare

  • Original panel event export with code definitions and time settings
  • Original video files with metadata and camera-clock information
  • Dispatch log and system inspection record describing its condition

What to compare

Message types, recording sequence, time zones and supported clock offsets are compared. File continuity and shared events that can align timelines are checked. Visible smoke, detector activation and operator action are treated separately; uncertainty intervals remain explicit when source records do not establish one exact timestamp.

Possible outcome of the analysis

A reconciled timeline may show time intervals, references to original records and unresolved discrepancies, helping formulate further questions about the event's development and the adequacy of available evidence.

Limits of the conclusions

An alarm timestamp does not automatically establish fire onset or cause. Unsynchronized clocks may prevent an exact sequence; record analysis does not certify the system's past operability.

Fire investigation: cause, origin, electrical systems, alarms and report reviews
Write to usDiscuss your task ↗