In short: a fire alarm system is only as good as the thinking behind it. Java Fire Protection follows NFPA 72 and complies with Lebanon's public safety decree. We start from the building and its risks, design and maintain each system to one recognised standard as Lebanese law requires, treat the cause-and-effect as seriously as the hardware, and consider a system reliable only when it is inspected, tested and maintained throughout its life.
We wrote this guide for building owners, facilities, HSE and operations managers, consultants and MEP contractors in Lebanon. Where it helps, we point to the references behind our practice: NFPA 72, the National Fire Alarm and Signaling Code, and Lebanon's public safety decree.
The 10 things at a glance
- Start from the building and its risks, not from the equipment.
- Work to one standard per system, as Lebanese law requires.
- Match detection and warning to the type of building.
- Choose conventional or addressable to suit the building.
- Design the cause-and-effect as seriously as the hardware.
- Commission the system step by step.
- Plan for the conditions that degrade systems in Lebanese buildings.
- Treat false alarms as an engineering problem.
- Inspect and test at NFPA 72 frequencies, or tighter.
- Make maintenance cover the whole system, and put it in the contract.
1. Start from the building and its risks, not from the equipment
The starting point is an understanding of the building, the people in it, its hazards and how it must respond when a fire is detected. The equipment follows from those answers.
An office, a warehouse, a hotel, an automotive workshop and an industrial facility may all require fire detection, but they should not necessarily be treated in the same way.
The 5 things we look at when we survey a building:
- The occupancy. Business, residential, assembly, health care, industrial or storage.
- The people. How many there are, whether they are awake or asleep, whether they know the building, and whether they can leave unaided.
- The activities. Cooking, vehicle movement, welding, and processes that produce dust, steam or fumes.
- The layout. Ceiling heights, voids above false ceilings, atria, racking and escape routes.
- The particular hazards. Generator and fuel rooms, battery rooms, server rooms and high-value stock.
We then ask how the building should respond. A school evacuates everyone at once. A hospital usually defends in place and moves patients progressively. A hotel or a mall needs clear voice instructions for people who do not know the building. That answer shapes the notification strategy, the zoning and the interfaces with other systems.
This is also how the codes are built. NFPA 101, the Life Safety Code, sets out in Section 9.6 and in its occupancy chapters when a fire alarm system is required and how occupants are to be notified. NFPA 72, Chapter 23, then governs the system itself.
The equipment matters, but the thinking behind the equipment matters more.
How Java complies: Java surveys every building against these five points before selecting any equipment, following NFPA 101, Section 9.6, and NFPA 72, Chapter 23.
2. Work to one standard per system, as Lebanese law requires
Lebanon's public safety decree sets the obligations; we turn them into engineering practice. The decree is Decree No. 14293 of 11 March 2005, as amended in full by Decree No. 7964 of 7 April 2012. It makes public-safety requirements mandatory for new building projects, and for alterations, additions and changes of use of existing buildings.
The 4 provisions of the decree that guide our work directly:
- One standard per system (Articles 1(10) and 3). Article 1(10) applies Lebanon's mandatory national standards, and where none exist, the standards adopted in the European Union, the United States or Canada. Article 3 requires a single source for each public-safety subject. This is why we design, install, test and maintain each fire alarm system to one coherent reference, such as NFPA 72, rather than a mix of US and European requirements.
- Revisit the design whenever a building changes (Article 4(1)). Modifications of and additions to existing buildings, and any change of use, fall within the decree, even when no floor area is added. A fit-out or a new tenant is a moment to look at the fire alarm again.
- Support the owner's maintenance responsibility (Article 4(4)). The owner, or the owners' association, is responsible for the periodic maintenance of the building and its equipment. Our inspection reports and records are designed to document that responsibility.
- Prepare designs for technical control (Articles 5 and 9). An accredited technical control bureau approves the design and execution drawings, and any changes during construction, for buildings where control is mandatory. The decree phased this in by building category, starting with Category 1. Published commentary dates the phases from December 2012, 2014 and 2016.
For existing buildings that are extended or change use, Article 4(6) allows the owner to request an exemption from certain fire-prevention provisions from a special committee formed by the Minister of Public Works and Transport. The committee can accept alternative solutions, provided protection elsewhere in the building is not reduced. In older buildings this is often where engineering judgement matters most.
This is our practical reading for building owners and managers, not legal advice. Project-specific requirements should be confirmed with the technical control bureau and the design engineer.
How Java complies: Java complies with Decree 14293/2005, as amended by Decree 7964/2012, by designing, installing, testing and maintaining each system to one coherent standard, such as NFPA 72.
3. Match detection and warning to the type of building
Occupancy determines the detector type, the zoning, the way people are warned and the systems the alarm must control. The table below shows our usual starting points for 11 building types. Every building still gets its own assessment.
| Building | What we look at first | Detection we typically use | How occupants are warned | Interfaces we typically include |
|---|---|---|---|---|
| Office | Open plan, false ceilings, ceiling voids | Spot smoke detectors | Sounders and visual alarms | HVAC shutdown, access control release |
| Warehouse | High ceilings, racking, large volumes | Beam or aspirating smoke detection | High-output sounders and beacons | Sprinkler flow and valve supervision |
| Hotel | Sleeping guests unfamiliar with the building | Smoke detection in rooms and corridors | Low-frequency (520 Hz) sounders in rooms; voice evacuation | Door holders, lifts, HVAC |
| Automotive workshop | Exhaust fumes and vapours | Heat or multi-sensor detectors | Sounders and beacons | Ventilation, fuel and paint areas |
| Industrial facility | Process hazards, dust, heat | Heat, flame or aspirating detection | Sounders and beacons above process noise | Suppression release, plant shutdown |
| Hospital | Defend in place, staged evacuation | Smoke detection throughout | Staged alarm and voice messages | Smoke dampers, door release |
| School | Large populations, regular drills | Smoke detection and manual call points | A clear, distinctive evacuation signal | Access control, public address |
| Mall | Large public spaces, unfamiliar visitors | Beam and spot smoke detection | Voice evacuation | Smoke control, escalators, shutters |
| Bank branch | Public banking hall, cash and records areas | Spot smoke detection and manual call points | Sounders and visual alarms; remote signalling | Access control, intruder alarm interface |
| Server and IT room | High-value equipment, high airflow, business continuity | Aspirating smoke detection (early or very early warning) | Local alarm and remote signalling | Clean agent release, HVAC shutdown |
| Heritage building | Appearance, limited cable routes | Discreet or wireless devices | Sounders and visual alarms | Minimal intervention |
The 3 NFPA 72 chapters behind these choices:
- Chapter 17 governs detector selection and siting, including the nominal 9.1 m (30 ft) spacing for spot smoke detectors on smooth ceilings.
- Chapter 18 requires audible signals to be clearly heard above average ambient sound. It also requires low-frequency (520 Hz) signals in sleeping areas, which wake people more reliably, and sets how visible notification performs where it is needed, for example for people with hearing impairment.
- Chapter 24 governs emergency communications, including voice evacuation.
How Java complies: Java follows NFPA 72, Chapters 17, 18 and 24, when selecting and siting detectors, sounders, visual alarms and voice evacuation for each type of building.
4. Choose conventional or addressable to suit the building
Neither is universally better, and we recommend whichever suits the building. An addressable system identifies the exact device in alarm. It is our usual recommendation for larger or more complex buildings, and wherever interfaces and fault-finding matter. A conventional system identifies only the zone and can suit a smaller, simpler building.
| Conventional | Addressable | |
|---|---|---|
| How a fire is located | By zone (a group of devices) | By individual device, with its location shown on the panel |
| Wiring | Radial circuits, one per zone | Loops (signaling line circuits) serving many devices |
| Fault finding | Technician searches the zone | Panel reports the specific device and fault |
| Unwanted-alarm management | Basic, applied per zone | Drift compensation and sensitivity settings per device |
| Expansion | New zones and cabling | Devices added to existing loops within capacity |
| Interfaces and cause-and-effect | Zone-based, less flexible | Programmable per device, zone or condition |
| Where we typically use it | Small offices, shops, small residential buildings | Hotels, hospitals, malls, industrial sites, multi-storey and multi-building sites |
The 5 steps we follow to upgrade an older conventional system to addressable:
Many of the buildings we visit still run conventional systems installed decades ago.
- Survey the existing cabling. We check whether it can serve the required pathway class. NFPA 72, Chapter 12, defines the pathway classes (such as Class A, B and X), which determine whether a single wiring fault can disable devices.
- Plan a phased migration. Often zone by zone, so the building is never left unprotected.
- Replace the field devices. Conventional detectors cannot be connected directly to an addressable loop. During the transition, existing zones can stay in service through listed conventional-zone interface modules, without individual addressing.
- Rewrite the cause-and-effect. We use the full flexibility of addressable programming.
- Acceptance-test the new system. We test it to NFPA 72, Chapter 14, reacceptance-test any parts we keep, and issue a new record of completion.
For a leading airport and airline service provider, we surveyed and drew the entire estate. We then designed a centralised addressable detection architecture to NFPA to replace multiple legacy conventional panels.
How Java complies: Java follows NFPA 72, Chapters 12 and 14, on every upgrade, and keeps the building protected zone by zone throughout the migration.
5. Design the cause-and-effect as seriously as the hardware
The cause-and-effect decides what the building actually does in a fire. It is the documented sequence of operations for every input. It sets out which detector triggers which sounders, which zones evacuate, and which building systems shut down, release or report. We design it on two sides.
What the system commands (NFPA 72, Chapter 21, emergency control functions):
- HVAC shutdown and smoke damper control.
- Lift recall.
- Release of access-controlled doors and magnetic door holders.
Where the fire alarm releases a suppression system, for example a clean agent system in a server room, the releasing function falls under NFPA 72, Chapter 23. The pre-alarm, delay and abort arrangements follow the agent standard, such as NFPA 2001, the Standard on Clean Agent Fire Extinguishing Systems.
What the system monitors:
- Sprinkler waterflow and valve-supervisory (tamper) devices, which are inspected and tested under NFPA 25 and NFPA 72, Chapter 14.
- The status of kitchen suppression systems and gas shut-off valves.
- Generator and power-transfer signals.
We document the sequence of operations as part of the record set required by NFPA 72, Chapter 7. We verify it at commissioning, following NFPA 3, the Standard for Commissioning of Fire Protection and Life Safety Systems, and through integrated, end-to-end testing under NFPA 4, the Standard for Integrated Fire Protection and Life Safety System Testing. In our experience, every detector can pass its individual test while the building still fails to respond as intended. Interfaces have to be tested together.
How Java complies: Java documents every sequence of operations to NFPA 72, Chapter 7, and verifies it to NFPA 3 and NFPA 4.
6. Commission the system step by step
Commissioning is where a design becomes a working system. Our 8 commissioning steps:
- Design review. We confirm the design against the occupancy, the chosen standard and, where applicable, the drawings approved by the technical control bureau (Decree 14293, Article 5).
- Installation inspection. We check cabling against NFPA 70, the National Electrical Code, Article 760 (Fire Alarm Systems). We check device siting and coverage against NFPA 72, Chapter 17.
- Device testing. We functionally test 100% of initiating devices and notification appliances.
- Cause-and-effect verification. We confirm every programmed input and output.
- Integrated testing. We test with the other life-safety and building systems.
- Secondary power. We verify that the batteries can run the system for 24 hours in standby and then 5 minutes in alarm, or 15 minutes of alarm for voice evacuation systems, as NFPA 72, Chapter 10, requires. Our battery calculations apply the 1.25 ageing factor introduced in the 2022 edition.
- Documentation. We hand over the record of completion, as-built drawings, the sequence of operations and the battery calculations (Chapter 7).
- Training and handover. We make sure the building team can read the panel, respond to alarms and faults, and knows who to call.
How Java complies: Java takes every system through all 8 commissioning steps and complies with NFPA 72, Chapter 10, on secondary power, including the 1.25 ageing factor.
7. Plan for the conditions that degrade systems in Lebanese buildings
Installation is only the beginning of the life of a fire alarm system. A system that was properly designed and commissioned several years ago may no longer perform as originally intended. Detectors may have been damaged or removed, building layouts may have changed, faults may have been ignored, batteries may have deteriorated or interfaces may no longer be operating correctly. This is why inspection, testing and preventive maintenance are so important.
The 5 conditions we meet most often in Lebanese buildings:
- Power cuts and generator changeovers. They cycle standby batteries far more often than a stable supply would, and heat shortens battery life further. The 2022 edition of NFPA 72 requires each battery to carry a replacement-date label no more than four years from installation.
- Dust, construction debris and humidity. Dust and debris contaminate smoke detectors and shift their sensitivity. Humidity and condensation cause unwanted alarms.
- Fit-outs and changes of use. New partitions and false ceilings change detector coverage. Where the works amount to a modification of the building or a change of use, Article 4(1) of the decree applies.
- Covers and disabled zones. Detector covers fitted during works are left on. Zones switched off to stop nuisance alarms stay disabled.
- Abandoned devices. Old devices stay on ceilings and walls. NFPA 72 requires them to be marked "not in service" until they are removed.
How Java complies: Java plans its maintenance around these five conditions and replaces every battery by its labelled date, as NFPA 72 requires.
8. Treat false alarms as an engineering problem
In our experience, unwanted alarms usually have 3 causes: the wrong detector for the environment, contaminated or ageing detectors, or devices sited where steam, fumes or air movement reach them.
The 3 fixes we apply:
- We use heat or multi-sensor detectors near kitchens, car parks and workshops.
- We clean and sensitivity-test smoke detectors.
- We re-site devices after layout changes.
Where NFPA 72 permits it, we enable alarm verification on smoke detectors only. The conditions include a delay of no more than one minute and a record of the setting. Alarm verification supports correct detector selection; it does not replace it. We never accept disabling a zone as a fix: a disabled zone is an impaired system.
How Java complies: Java follows NFPA 72 on alarm verification and never disables a zone to stop unwanted alarms.
9. Inspect and test at NFPA 72 frequencies, or tighter
We follow the frequencies set by NFPA 72, Chapter 14, and tighten them where conditions call for it. Table 14.3.1 sets the intervals for visual inspection and Table 14.4.3.2 those for testing. Most initiating devices and notification appliances are functionally tested every year. Smoke detector sensitivity is checked within one year of installation and every alternate year after that.
| What we inspect or test | NFPA 72 reference | Frequency or requirement |
|---|---|---|
| Control equipment, devices and appliances (visual inspection) | Chapter 14, Table 14.3.1 | At the intervals set in the table |
| Smoke detectors, manual call points, sounders and visual alarms (functional test) | Chapter 14, Table 14.4.3.2 | Annually (heat detectors follow their own regime in the same table) |
| Smoke detector sensitivity | Chapter 14 | Within 1 year of installation, then every alternate year |
| Batteries and charger | Chapter 10; Table 14.4.3.2 | Tested at the intervals in the table; replaced by the labelled date, no more than 4 years after installation |
| The system after any change, including site-specific software | Chapter 14 | Reacceptance testing, with a qualified person on site |
| Records | Chapters 7 and 14 | Retained and available to the owner |
The 2022 edition also introduced an informative annex on colour-coded tagging. A yellow tag flags deficiencies; a red tag flags an impaired or inoperable system.
These are minimums. Frequent power interruptions, dust and regular fit-outs lead us to recommend a tighter preventive routine for many Lebanese buildings. Our references are to the 2022 edition. The 2025 edition is now current, so we confirm with the technical control bureau which edition each project applies.
How Java complies: Java applies the NFPA 72, Chapter 14, inspection and testing frequencies as a minimum, and tightens them for Lebanese conditions.
10. Make maintenance cover the whole system, and put it in the contract
When we maintain a system, our objective is not simply to arrive on site, perform a few tests and leave behind a service sticker. We want the customer to understand whether the system, as a whole, is ready to perform when it is actually needed.
The 9 checks in every Java maintenance visit:
- The control panel. Its operation, event log, and history of faults, alarms and disablements.
- Power. The primary supply, the standby batteries (date label and capacity), the charger, and the system's behaviour during generator changeover.
- Detectors. Function, sensitivity, cleanliness, and coverage against the current layout.
- Manual call points. Operation and accessibility.
- Sounders and visual alarms. Audibility and visibility in the spaces they serve.
- Interfaces. A sample of the cause-and-effect, including shutdowns, releases and lift recall.
- Wiring. Pathway integrity and earth faults.
- Documentation. Updated drawings and device lists.
- The report. A written report that classifies deficiencies and recommends actions.
The 9 things a fire alarm maintenance contract in Lebanon should include:
- Scope. Every panel, device and interface, including connections to suppression, HVAC, lifts and access control.
- Frequencies. A visit and test schedule based on NFPA 72, Chapter 14.
- Records. Written reports kept for the life of the system.
- Response. Defined response times for faults, alarms and impairments.
- Impairments. A procedure for planned and unplanned impairments, so the building is never unknowingly unprotected.
- Batteries and spares. A battery replacement schedule and access to listed spare parts.
- Building changes. A review of fit-outs and changes of use before and after works.
- Continuity. A named engineer who knows the building and its history.
- The owner's duty. Documentation that supports the owner's periodic-maintenance responsibility under Article 4(4) of the decree.
How Java complies: Java checks all 9 areas at every maintenance visit and issues a written report that supports the owner's periodic-maintenance responsibility under Article 4(4) of the decree.
How Java applies these 10 points
Java Fire Protection follows all 10 points on every fire alarm project, from the first survey to long-term maintenance.
| # | The point | What Java does |
|---|---|---|
| 1 | Start from the building | We survey occupancy, people, activities, layout and hazards before selecting any equipment. |
| 2 | One standard per system | We design, install, test and maintain each system to one coherent reference, such as NFPA 72. |
| 3 | Match the building type | We choose detection, warning and interfaces for each occupancy, then assess each building individually. |
| 4 | Conventional or addressable | We recommend what suits the building, and upgrade older systems zone by zone without leaving them unprotected. |
| 5 | Cause-and-effect | We document the sequence of operations and test interfaces together, not just devices one by one. |
| 6 | Commissioning | We follow 8 steps, from design review to training and handover. |
| 7 | Lebanese conditions | We plan for power cuts, dust, fit-outs, disabled zones and abandoned devices. |
| 8 | False alarms | We fix the cause; we never accept disabling a zone. |
| 9 | Inspection and testing | We follow NFPA 72, Chapter 14, and tighten the routine where conditions call for it. |
| 10 | Maintenance | We check 9 areas at every visit and issue a written report. |
Our approach
At Java, we prefer to begin with an understanding of the building and its use before deciding what technology should be installed. We look at the occupancy, the applicable requirements, the required detection philosophy and how the alarm system should interact with the rest of the fire-protection strategy. Only after that do we move into equipment selection and detailed design.
Java Fire Protection was founded in Beirut in 1957 and has been family-led for three generations. Our NFPA-certified fire protection specialists (CFPS) design to recognised codes. We install UL-listed and FM-approved equipment from our US and European partners. Through our Systems & Alarms and Consultancy business lines, we act as one accountable partner from design and commissioning through to long-term maintenance, including through our Priority Partner programme.
For us, the philosophy is quite simple: understand the risk, design the right system, commission it properly and remain involved throughout its life. Fire detection should not be treated as a one-time installation. It is a protection system that needs to remain reliable every day.
Planning a new system, a fit-out or an upgrade, or reviewing an existing installation? Speak with our engineers about a fire alarm design review or maintenance assessment.
Frequently asked questions
Do fire alarm systems keep working during power cuts in Lebanon?
Yes, when the standby batteries are correctly sized and maintained. NFPA 72 requires batteries that can run the system for 24 hours and then sound the alarm for 5 minutes, or 15 minutes for voice evacuation systems. Because outages and generator changeovers age batteries faster in Lebanon, we test battery capacity and replace batteries by their labelled date.
Can an old conventional fire alarm be upgraded to addressable?
Yes. We survey the existing cabling, replace the panel and field devices, migrate zone by zone so the building stays protected, rewrite the cause-and-effect and acceptance-test the new system under NFPA 72, Chapter 14.
Who is legally responsible for maintaining a fire alarm system in a Lebanese building?
Under Article 4(4) of Decree 14293/2005, as amended in full by Decree 7964/2012, the owner or the owners' association is responsible for the periodic maintenance of the building and its equipment. Our inspection reports and records support that responsibility.
Does a fit-out or change of use affect our fire alarm system?
Usually, yes. Under Article 4(1) of the decree, modifications of and additions to existing buildings, and any change of use (even without added floor area), fall within the decree. Even a minor fit-out changes detector coverage, so we review the design and the cause-and-effect and retest the system.
Should a fire alarm in Lebanon follow NFPA or EN standards?
Where no mandatory Lebanese standard exists, the decree applies the standards adopted in the EU, the US or Canada, and requires a single source per safety subject. We therefore design each system to one coherent standard, such as NFPA 72, from design through maintenance.
Do hotels and malls in Lebanon need voice evacuation?
We recommend voice evacuation for large buildings where many people do not know the building. Clear spoken instructions move people more effectively than tones alone. Whether it is required depends on the occupancy and the applicable code. NFPA 72, Chapter 24, governs the design of emergency communications systems.
How do we choose a fire alarm panel?
We choose listed and approved equipment that is supported locally with spare parts, trained technicians and full documentation. The panel must suit the building's size, the standard the system is designed to and the interfaces it must control.
References
- Decree No. 14293 of 11 March 2005 on public safety in buildings and facilities, lift installations, and protection against fire and earthquakes (Official Gazette No. 13, 24 March 2005), as amended in full by Decree No. 7964 of 7 April 2012 (Lebanon).
- NFPA 72, National Fire Alarm and Signaling Code, 2022 edition (the 2025 edition is now current).
- NFPA 101, Life Safety Code.
- NFPA 70, National Electrical Code, Article 760.
- NFPA 3, Standard for Commissioning of Fire Protection and Life Safety Systems.
- NFPA 4, Standard for Integrated Fire Protection and Life Safety System Testing.
- NFPA 25, Standard for the Inspection, Testing, and Maintenance of Water-Based Fire Protection Systems.
- NFPA 2001, Standard on Clean Agent Fire Extinguishing Systems.