Fire-alarm zoning and cause-and-effect: writing the matrix the building actually obeys

A fire-alarm panel is a small piece of hardware that controls a very large coordinated response. On a single trigger from a single detector in a single zone, the panel may need to home four lifts to ground, release fourteen magnetic door-holders, close eighteen AHU dampers, broadcast a zone-specific evacuation announcement, hand the access-control system into evacuation mode, signal the BMS to pre-start the sprinkler pumps, and pre-record on twenty-three CCTV cameras pointed at the affected corridor. None of this is automatic. All of it is programmed against a written cause-and-effect matrix that someone wrote, someone reviewed, someone signal-tested, and someone signed. If that matrix does not exist in writing, the response does not exist in practice — it lives in someone's head, and it disappears the day they leave.

## What the matrix actually is

A cause-and-effect matrix is a table. Rows are inputs — every detector zone, every manual call-point, every sprinkler flow-switch, every duct detector. Columns are outputs — every sounder zone, every door-holder relay, every AHU damper, every lift-homing circuit, every PA broadcast, every BMS interlock. The cells are the actions: 'on alarm input from Zone 3, sound Zone 3 + Zone 4, release Zone 3 door-holders, home Lifts 1 and 2 to ground, close AHU-1 damper, broadcast voice-evacuation message E-3 to Zones 3 and 4, switch Access-Group A to evacuation, pre-record CCTV cameras 12-18 for 60 seconds before alarm'. Every cell is reviewable, testable and revisable.

Most fire-alarm panels we audit pre-retrofit have a matrix that exists implicitly in the panel programming but has never been extracted into a written document. The site engineers can describe the response in conversation but cannot produce a table. That gap is the operational risk the matrix exists to close. We extract the as-is matrix from the panel's programming on every audit, walk it through with the operations team to confirm it matches their understanding, identify the gaps and the contradictions, and produce a written document that becomes the spec for any subsequent change.

## Zoning is the first decision and the hardest to revisit

Fire-alarm zoning decides what 'Zone 3' means in the matrix. It is the partition of the building into discrete addressable groups that the panel reports against, and it is what the AHJ signs against. Zoning that is too coarse loses forensic localisation (a 5,000 sq m floor reported as one zone is a single haystack the security desk has to search). Zoning that is too fine produces a matrix with so many rows the operations team cannot mentally hold it.

We zone by occupancy and by compartmentation: each fire compartment is at minimum its own zone, and within a compartment we zone by occupancy character (a ward zone is separate from the nurse station, even if they share a compartment, because the response is different). The IS 2189 and NBC 2016 default — one zone per 1,500 sq m, with sub-zoning where the compartmentation requires — is the floor; we frequently zone tighter for clinical, civic and educational occupancies. The zoning decision is made before the panel is procured, because the panel's loop and address budget has to fit it.

## The seam-level integrations are where matrices fail

Most matrices we audit pass the in-system tests cleanly — the fire-alarm panel reads the input, the sounders sound, the door-holders release. They fail at the seams: the AHU damper does not close because the BMS controller went into a maintenance mode three months ago and nobody noticed; the lift-homing circuit was disabled during a service visit and nobody re-enabled it; the PA broadcast plays the wrong message because the message library was reorganised and the matrix references the old message ID.

We mitigate this with two disciplines. First, the matrix carries a per-output 'verification source' — the controller, the relay address and the test method that proves the output is in service. Second, we cause-and-effect test at every system change, not just at original commissioning, with a written test record signed by the system owner. The matrix is a living document, not a commissioning artefact.

## The AHJ signs the matrix, not the wiring diagram

On every project, the matrix is what the Authority Having Jurisdiction (the local fire department, in most Indian contexts) signs. The wiring diagram is the implementation; the matrix is the spec. We prepare the matrix in the format the local AHJ recognises — usually a tabular form with the building's actual zone names, the actual device addresses and the actual output relays — and we walk the AHJ through it before any field installation begins. The AHJ's sign-off is on the matrix; we then implement the matrix and demonstrate it on commissioning.

## Callout — what buyers most miss

**The matrix is the deliverable, not the panel.** Most fire-alarm tenders are written around the panel specification — addressable, the loop count, the device count, the brand. The matrix is the actual deliverable. A panel without a written matrix is a piece of hardware looking for a programme. Tender for the matrix discipline as well as the panel; the difference is what separates a system that responds correctly to its first real event from one that does not.

## Reference deployment context

The Tinsukia Medical College & Hospital fire-alarm matrix runs to 320 input rows and 184 output columns across the addressable loop count, with the surgical-anaesthesia override on AHU-1, AHU-2 and AHU-7 captured explicitly so the OT team can acknowledge before the dampers close on a fire alarm. The matrix is signed by the hospital's clinical engineering lead, the fire-safety officer, and the AHJ. We re-test the cause-and-effect on every quarterly AMC visit; the test record is in the AMC log.

## References

1. IS 2189-2008 — *Code of practice for installation of automatic fire detection and alarm system*.

2. National Building Code of India 2016, Volume 2, Chapter 1 — fire and life-safety provisions.

3. NFPA 72 (2022 edition) — *National Fire Alarm and Signaling Code*.

4. IS 16102:2014 — *Voice Alarm Systems — Sound systems for emergency purposes*.