The matrix must also define the sequence and conditions of the response. For example, a simple matrix may show that a smoke alarm in an apartment triggers both a local alarm and a general evacuation. A more complex matrix, however, might implement a staged evacuation . In this scenario, the initial "cause" only triggers a staff alert (Stage 1). If the alarm is not acknowledged within a set time (e.g., 180 seconds), it then triggers a full evacuation (Stage 2). The matrix defines these conditional pathways.
The input has no effect on this specific output. A Simplified Example of a Fire Alarm Matrix Input / Cause Sounders & Beacons Elevator Recall HVAC Shutdown Door Release Ground Floor Smoke Detector Second Floor Pull Station Server Room ASD (Pre-alarm) Server Room ASD (Alarm) fire alarm cause and effect matrix
In traditional domestic systems, the C&E is simplistic: If any detector alarms, Then all sounders go off. However, in large, complex buildings (hospitals, airports, high-rise apartments, data centers, shopping malls), this "one-in, all-out" philosophy is dangerous. It can cause unnecessary evacuation, panic, or business interruption. This is where the matrix becomes sophisticated. The matrix must also define the sequence and
One of the most critical applications of a cause and effect matrix is the "double-knock" (or coincidence detection) sequence, commonly used to prevent accidental discharges in sensitive or highly populated environments. In this scenario, the initial "cause" only triggers
If every burnt piece of toast in a breakroom triggered a total building shutdown and summoned five fire trucks, the system would be a liability. The matrix can be programmed for or "cross-zoning," where two detectors must trip before the most drastic "effects" occur. 3. Regulatory Compliance
| Pitfall | Consequence | |---------|--------------| | | Smoke clears but doors stay locked, fans remain off. | | No distinction between alarm & pre-alarm | Stage 1 (staff alert) triggers full evacuation. | | Ignoring multiple simultaneous causes | Two separate fires in different zones – system may lock out second response. | | Effect overwritten by later cause | Fire in lobby recalls lift. Second fire in upper floor – lift already recalled, matrix doesn't say what happens next. | | Manual call point treated same as detector | MCP should usually give no verification delay – many matrices miss this. |