Fire Alarm Systems
Detection, alarm and evacuation systems designed to identify a fire early, tell people precisely where it is, and prove it works — with the documentation to show it.
Overview
A fire alarm system has one job that matters: give people enough warning to leave, and give the building's other systems enough information to react. Everything else — the panel brand, the device count, the price per point — is downstream of whether the detection design is right for the space it is protecting.
Milagre engineers, supplies, installs, tests, commissions and maintains both addressable and conventional fire alarm systems. We work from a detection layout and a written cause-and-effect matrix, not from a device schedule handed over at tender. That distinction is what determines whether the system behaves correctly the first time it is commissioned.
Cause and effect is the written table that says what the system must do when a specific device operates — which sounders activate, which dampers close, which lifts return to ground, which doors release, and which suppression system is held or triggered. If it is not written down before installation, it gets invented during commissioning, and that is where projects lose weeks.
System types we work with
The table below sets out the detection technologies within scope. Where the scope column reads on enquiry, the stages we take on depend on the project rather than being fixed.
| System | Typical application | Milagre scope |
|---|---|---|
| Addressable fire alarm | Most commercial, hospitality and institutional buildings | Design · Supply · Install · Test · Commission · Maintain |
| Conventional fire alarm | Small buildings, simple layouts, limited zoning needs | Design · Supply · Install · Test · Commission · Maintain |
| Aspirating smoke detection | Data centres, clean rooms, high ceilings, cold stores | On enquiry |
| Linear heat detection | Cable tunnels, conveyors, car park decks, tank farms | On enquiry |
| Flame & beam detection | Warehouses, atria, hangars, process areas | On enquiry |
| Voice evacuation / PA-VA | High-rise, malls, hotels, assembly occupancies | On enquiry |
| Graphical monitoring & BMS integration | Campuses and multi-building estates with a central control room | On enquiry |
Applications
Detection design changes substantially with the building. These are the environments we work in most often, and the specific problem each one presents.
- Hotels & resorts
- Hundreds of guest rooms, each needing detection that will not nuisance-alarm from a steamy bathroom, plus evacuation messaging that works for occupants who do not know the building.
- Shopping malls & retail
- Large open volumes and atria where smoke stratifies before reaching ceiling detectors, and tenant fit-outs that change the layout every few months.
- Industrial facilities
- Dust, humidity, vibration and process heat that defeat standard smoke detection, requiring flame, linear heat or aspirating technologies instead.
- Universities & campuses
- Multiple buildings across a site, phased occupancy, and a requirement to see everything from one control room.
- Data centres & server rooms
- Very early warning requirements, because by the time a standard detector operates, the damage is already done. Usually paired with a clean agent suppression system.
- Car parks
- Vehicle exhaust, temperature swings and ventilation currents that make smoke detection unreliable — commonly linear heat detection territory.
Why an engineered approach matters
Fire alarm systems are frequently bought on device count and panel brand. Both are the wrong things to compare, because two systems with identical bills of quantity can behave completely differently depending on how the detection was laid out and how the cause and effect was written.
- Detection that suits the space. The right technology in the right position, so the system alarms on fires and not on cooking, dust or steam.
- A written cause-and-effect matrix. Agreed before installation, verified at commissioning, and handed over as a document you can audit.
- Coordinated interfaces. Because we also deliver suppression, fire fighting and security, the interfaces between them are designed rather than negotiated between three contractors on site.
- Commissioning records that stand up. Every device tested individually, results documented, so an inspector or an insurer can see what was verified and when.
- A system that stays working. Scheduled inspection and testing under a maintenance agreement, so the system is still functional in year five rather than merely installed.
Our process
The same sequence applies to a single floor and to a campus. The scale changes; the order does not.
- 01 · Site survey
- Engineers attend site to record ceiling types and heights, riser routes, ventilation, existing containment and any equipment being retained.
- 02 · Detection design
- Device layout, spacing and technology selection against the governing code and the actual conditions of each space.
- 03 · Cause & effect
- Written matrix defining exactly what the system does on each input, agreed with the consultant, client and authority before anything is ordered.
- 04 · Shop drawings
- Loop schematics, cable schedules, panel layouts and containment routes issued for approval.
- 05 · Supply & installation
- Equipment procured to the approved make and model, installed by our crews to the approved drawings.
- 06 · Testing
- Every detector, call point, sounder and interface functionally tested and recorded — not sampled.
- 07 · Commissioning
- Full cause and effect demonstrated end to end, with the consultant and authority witnessing where required.
- 08 · Handover & training
- As-built drawings, test certificates, O&M manuals and operator training for the people who will live with the system.
- 09 · Maintenance
- Scheduled inspection and testing under an agreement, with records kept for inspection and insurance.
Standards & approvals
Fire alarm design is governed by code, not preference. Systems are designed to NFPA and the Egyptian Fire Code as applicable to each project, and to the requirements of the authority having jurisdiction.
| Standard | What it governs |
|---|---|
| NFPA 72 | National Fire Alarm and Signaling Code — detection spacing, notification, inspection and testing frequencies |
| EN 54 | European product standard series for fire detection and alarm equipment |
| Egyptian Fire Code | National requirements — كود الحماية من الحريق |
| Civil Defence | Local authority approval and inspection |
Milagre holds documented manufacturer authorisations from Velocity, Zeta and Hikvision; the letters are on file and available on request. No quality-management certification and no contractor classification is held, and neither is claimed — what we do not claim sets that out in full. Nothing will be claimed here without a certificate to support it.
Frequently asked questions
What is the difference between an addressable and a conventional fire alarm system?
A conventional system divides the building into zones. When a detector operates, the panel tells you which zone is in alarm — the second floor east wing, say — but not which device. Each zone needs its own wiring circuit back to the panel.
An addressable system gives every device a unique identity on a shared loop. The panel names the specific detector, reports faults per device rather than per zone, and supports programmed cause and effect. It also uses considerably less cable, because devices share the loop instead of each zone needing a dedicated circuit.
Conventional systems are still entirely appropriate for small, simple buildings. For anything with multiple floors, complex layouts or interfaces to other systems, addressable is normally the correct answer.
How often should a fire alarm system be inspected and tested?
Under NFPA 72 the broad pattern is a daily or weekly visual check of the panel by building staff, quarterly inspection of key components, and a full annual test in which every initiating and notification device is functionally tested. Batteries are typically load-tested annually and replaced on a defined interval.
Local authority requirements may be stricter than the code. Where they differ, the more demanding schedule governs. Records should be retained — an untested system with no documentation is treated as an untested system regardless of its actual condition.
Why does my fire alarm system keep giving false alarms?
In our experience nuisance alarms are far more often a detection design problem than a panel fault. The usual causes are smoke detectors sited near kitchens, bathrooms, loading doors or air handling unit discharges; dust ingress during construction or tenant fit-out; detectors past their service life whose sensitivity has drifted; and insects or humidity inside the sensing chamber.
The correct response is to reconsider the detector technology for that environment, relocate it, or adjust sensitivity within permitted limits. Isolating the zone is not a fix — it is a disabled fire alarm system, and it is how buildings end up unprotected for months without anyone noticing.
How long does a fire alarm installation take?
It depends on building size, whether the building is occupied, and how much cabling can run in parallel with other trades. First fix cabling is normally the longest phase and is the one most affected by other contractors' progress.
Testing and commissioning should not be compressed to recover a programme. Every device has to be individually tested and the full cause and effect verified. Where that phase gets squeezed is exactly where systems get handed over with untested interfaces.
Can I upgrade my system without replacing all the cabling and devices?
Sometimes. Moving from an older addressable panel to a newer one in the same manufacturer family can occasionally retain field devices and existing cabling. Moving from conventional to addressable almost always requires recabling, because the loop topology is fundamentally different from zoned radial circuits.
A survey of the existing installation is the only way to know. We would rather tell you the cabling is reusable and reduce the scope than discover mid-project that it is not.
Do I need voice evacuation, or are sounders enough?
This is determined by building type, height, occupancy and the governing code rather than by preference. As a general principle, buildings where occupants are unfamiliar with the layout, or where phased evacuation is planned, benefit from voice systems — a spoken instruction produces faster and more orderly movement than a tone, which people frequently ignore or misinterpret.
High-rise buildings, hotels, malls and assembly occupancies are the usual candidates. The authority having jurisdiction makes the final determination.
Can you take over maintenance of a system another company installed?
Yes, after a survey. An inherited system has to be established before it can be maintained: what is actually installed, what the panel is reporting, which devices have been isolated and left isolated, and whether the as-built documentation matches the building. That survey is the honest first step, and it is often where the real problem turns up.
What we will not do is sign a maintenance contract for a system we have not seen and then discover at the first annual test that half of it does not work.
Related projects
Milagre has delivered fire alarm systems across industrial plant, university campuses, hotels, resorts and shopping malls. All thirteen are named on the projects page, three of them shown in full.
Two different problems. Two different inboxes.
A new installation and a system that has stopped working are not the same urgency, so they do not go to the same place.
Request a quote
An engineer attends site and you receive a scope tied to drawings — not a lump sum with a device count attached to it.
Service & maintenance
A recurring false alarm, a panel in fault, an overdue annual test, or a system you have inherited and are not sure about.
Would rather fill in a form? Use the enquiry form