Civil Defence Approval for Fire Alarm Systems in Saudi Arabia: What the Submission Needs

Most fire alarm systems that fail Civil Defence approval in Saudi Arabia are not bad systems. They are correct systems with an incomplete submission. The panel is listed, the devices are right, the installation is clean, and the file comes back because the battery calculation is missing or the cause and effect matrix does not match the drawings.

That distinction matters commercially. A design fault costs money to correct. A documentation fault costs time, and on a project where the fire system gates occupancy, time is the expensive one. This note sets out what the submission actually contains, where projects lose weeks, and what we do differently as a result.

Who approves what

The General Directorate of Civil Defence is the authority having jurisdiction for fire detection and alarm in Saudi Arabia. The system is designed to NFPA 72 and the fire provisions of the Saudi Building Code, and the authority reviews the submission, inspects the installation and witnesses the test before issuing approval.

The contractor does not issue the approval and cannot promise one. What a contractor can be held to is that the submission is complete and correct the first time, that the installed system matches what was approved, and that the witnessed test is attended by people who can answer for the system. Treat any supplier who guarantees the approval itself with caution.

What the submission pack contains

A complete pack is more than a layout drawing. Expect all of the following, and expect comments if any one of them is absent.

Drawings

Floor plans showing every device with its address and device type, riser diagrams, panel and sub panel locations, cable routes and containment, and the interface points to other systems. The drawings have to be consistent with each other. A device that appears on the plan and not on the riser is a comment.

Device schedule and addressing

Every initiating and notification device listed with its loop, address, location and type. This is the document the inspector will carry during the site visit, so it has to describe the building as built rather than as drawn eighteen months earlier.

Battery standby calculation

The calculation demonstrating the system will run on batteries for the required quiescent period and then drive the full alarm load, with the ageing and temperature derating factors applied. Underspecified batteries are one of the most common single reasons a pack comes back, and the fix is usually a larger enclosure, which means the fix is not free.

Cause and effect matrix

The document that states, for every input, what every output does. Which air handling units shut down, which fire dampers close, which smoke extract fans start, where the lifts home to and whether they release their doors, which access controlled doors fail open, which stair pressurisation systems start, and what is signalled off site.

This is the part of the submission most often written last and most often wrong. It is also the document that decides whether the building behaves correctly in a real fire, so it deserves more attention than it usually gets.

Equipment listings and compliance statements

Manufacturer data sheets with the UL or FM listing for each item, and a statement of compliance against the applicable clauses. Equipment that is certified but not listed for the specific application will be challenged.

Where projects actually lose time

Detector selection by environment, not by cost

A smoke detector in the wrong place is an unreliable detector, and unreliable detection produces false alarms, which produces a building where people ignore the sounders. The environment decides the device:

  • Kitchens and laundries. Heat detection, not smoke. Cooking aerosol and steam will trip an optical head repeatedly.
  • Car parks. Heat detection or purpose designed detection. Exhaust fumes defeat smoke heads.
  • Dusty industrial areas. Sealed or aspirating detection with filtration, because dust accumulation inside an optical chamber reads as smoke.
  • High ceilings. Above roughly ten to twelve metres a smoke plume cools, loses buoyancy and stratifies into a layer before it reaches a point detector at the roof. Warehouses, hangars, atria and airport concourses need optical beam detection or aspirating systems, positioned at the level the smoke will actually reach.
  • Server rooms and switchrooms. Aspirating detection for early warning, interfaced with the suppression system.

Getting this wrong is not caught at design review. It is caught after handover, by the building operator, every week.

The interface scope nobody priced

The fire alarm system has to talk to the HVAC controls, the lifts, the access control, the smoke extract, the generator and often the building management system. On a project with separate subcontractors for each, the interface is frequently in nobody’s package. It surfaces during commissioning, when all the parties are demobilising.

This is the strongest practical argument for keeping fire detection with the electrical and mechanical packages under one contractor. When the same team owns the damper actuator, the AHU control panel and the fire alarm loop, the cause and effect matrix is a design document rather than a negotiation.

As built drift

Between approval and inspection the building changes. Partitions move, a ceiling is lowered, a room changes use. If the device schedule and drawings are not reissued, the inspector finds devices that are not where the approved drawings say they are, and the visit ends there.

The inspection and witnessed test

Expect the authority to sample devices rather than test all of them, to check that the panel annunciates the correct zone and address, and to verify the cause and effect in practice: trigger a detector and watch the dampers, the fans, the lifts and the doors do what the matrix said they would.

Have the following present on the day: the approved drawings, the as built device schedule, the cause and effect matrix, the battery calculation, the commissioning records, and an engineer who programmed the panel. Sending a technician who can operate the panel but cannot explain a decision is a wasted visit.

Common reasons a pack is returned

  • Battery standby calculation missing, or done without derating
  • Cause and effect matrix absent, generic, or inconsistent with the drawings
  • Device schedule that does not match the installed building
  • Detector type inappropriate for the environment
  • Equipment data sheets without the applicable listing
  • Interfaces shown on the matrix but not wired or not tested
  • Voice evacuation specified without intelligibility considered

None of these are difficult. They are the things that get deferred because they are documentation rather than installation, and then the documentation becomes the critical path.

How we handle it

Green Flash is an authorised EDWARDS fire alarm distributor in Saudi Arabia, so panel selection, device supply, programming and commissioning sit with one party rather than being split between a supplier and an installer. We prepare the drawings, the device schedule, the battery calculation and the cause and effect matrix as a single coordinated set, make the submission, respond to comments and attend the witnessed test.

We also deliver the fire fighting package on the same projects, which means the detection, the suppression and the mechanical interfaces are designed together. Our quality system is certified to ISO 9001:2015 under certificate SCK/01/AWL/25/96/6215, and the inspection and test records that support a Civil Defence submission are produced under it.

If you have a project at design stage, or a system that has already come back with comments, send us the drawings and we will tell you what the submission is missing.

Chat on WhatsApp