Quick answer

What to Know First

Organize initiating events, outputs, interfaces, timing, reset and test requirements.

  • List every initiating event against every required output in one controlled matrix.
  • Separate alarm, pre-alarm, fault, supervisory, isolation and manual behaviour.
  • Include delays, feedback, latching, reset and failure states.
Test how your system responds
01 Cause
02 Logic and timing
03 Effect
04 Feedback and record

What the matrix is for

A cause-and-effect table shows what your system should do when an event occurs. For example, a detector alarm may trigger sounders or close a fire door. Each row lists an event, and the columns show the actions you can test.

Use plain labels that match drawings, panel text and physical equipment.

Include the cases people forget

Do not document only a confirmed fire. Include pre-alarm, fault, disabled points, power loss, manual override, abort, feedback failure and restoration.

State whether delays restart, cancel or continue when a second event occurs.

  • Normal, alarm, fault and supervisory states
  • Automatic and manual initiation
  • Coincidence and cross-zone logic
  • Feedback timeout and failed response
  • Silence, reset and post-discharge actions

Make it the test script

Assign a unique test reference to each row. During integrated testing, record the actual time and result for every output, including local indication and remote monitoring.

Revise the matrix when software, devices or interfaces change.

Before You Specify or Buy

Project Checklist

01
Inputs

Devices, zones, release panels, manual controls and external systems.

02
Outputs

Sounders, lifts, doors, fans, dampers, suppression and notifications.

03
Logic

Timing, coincidence, priority, feedback, latching and reset.

04
Testing

Witness steps, expected indication, revision and sign-off responsibility.

Frequently Asked Questions

Who should own the cause-and-effect matrix?

The responsible designer should control the approved intent; the integrator configures it and the project team witnesses the result.

Official references

NFPA 72 - National Fire Alarm and Signaling Code
Technical information notice

Information is based on reviewed sources and our experience at the date shown. Use it at your own risk and verify current codes, certificates and project conditions. Report an issue or suggest a correction.