Fire Alarm Cause & Effect Matrix for DCD Approval
A fire alarm cause and effect (C&E) matrix is a table that maps every alarm input — a specific detector, zone or device — to every automatic output it must trigger, such as sounders, lift homing, HVAC damper closure, pump start and the Hassantuk signal. For DCD approval in Dubai it is a required deliverable, and each sequence is functionally tested and witnessed before sign-off.
DCD-approved · 12+ years in Dubai fire safety · Hassantuk-integrated · 18,000+ customers served
The blueprint for how the system reacts
The C&E matrix is where fire detection stops being a set of devices and becomes a coordinated response. It lists every input against every output so there is no ambiguity about what the building does when a specific detector activates — and it is exactly what DCD checks the installed behaviour against.
- Maps each detector, zone and device to its required outputs.
- Covers sounders, strobes, lift homing and door release.
- Defines HVAC and damper responses for smoke control.
- Specifies fire-pump start and suppression release logic.
- Includes the DCD 24x7 and Hassantuk signalling interface.
A required deliverable, not optional paperwork
Under the UAE Fire and Life Safety Code, addressable systems in large buildings must support complex cause-and-effect sequences, and every interface must be witnessed before sign-off. The matrix is the reference DCD inspectors test against — no matrix, or a matrix that does not match reality, means no approval.
- Addressable systems must support cause-and-effect sequences.
- Every interface is witnessed before DCD acceptance.
- Functional testing applies whenever devices or circuits change.
- Inspectors test installed behaviour against the approved matrix.
- Mismatches between matrix and site are a common inspection fail.
Design, program and prove every sequence
QSERV authors the matrix from the fire strategy, programs it into the panel, and then witnesses each sequence during acceptance testing — including the awkward cross-system interfaces where poorly integrated packages usually fail on the first inspection.
- Matrix authored directly from the approved fire strategy.
- Panel programmed to match the documented sequences.
- Cross-system interfaces tested, not assumed to work.
- Generator override and pump-start logic proven under test.
- Full C&E records prepared for the DCD closure package.
Services & Guides For This Topic
Frequently Asked Questions
Answers on the cause and effect matrix DCD requires for fire alarm approval in Dubai.
What is a fire alarm cause and effect matrix?
It is a table mapping every alarm input — a detector, zone or device — to every automatic output it must trigger, such as sounders, lift homing, damper closure, pump start and the Hassantuk signal. It defines exactly how the building responds to each alarm condition.
Why does DCD require a cause and effect matrix?
The UAE Fire and Life Safety Code requires addressable systems in large buildings to support complex cause-and-effect sequences, and every interface must be witnessed before sign-off. The matrix is the approved reference DCD inspectors test the installed system against.
What interfaces belong in the matrix?
Typically sounders and strobes, lift homing and door release, HVAC shutdown and smoke-damper operation, fire-pump start, suppression release, and the DCD 24x7 and Hassantuk signalling link — every automatic output the fire strategy calls for.
What happens if the installed system does not match the matrix?
It is a common cause of inspection failure. If a witnessed sequence behaves differently from the approved matrix, DCD will not accept the system until the panel programming and the matrix are reconciled and re-tested.
Is the matrix tested or just submitted?
Both. It is submitted as part of the design package and then functionally tested and witnessed during acceptance. Under NFPA 72, functional testing applies whenever devices or circuits are added or changed, so the matrix stays a live document.
Does the matrix matter after hand-over?
Yes. It is the reference for future testing and any modification. When devices or circuits are added during the building's life, the affected sequences must be re-tested against the matrix, which is why it forms part of the O&M records.