Fire and Smoke Detection System Maintenance in an Office Building — What's Mandatory, Who's Authorized, and What Gets Tested

A fire and smoke detection system is one of the only systems in a building you pay to maintain every year and hope you'll never see actually working. That's exactly why it's also the easiest to neglect: it's silent, disturbs no tenant, and if one detector is disabled after a tenant fit-out — no one will notice until it's too late. From managing a building month after month, the difference between a system that works at the moment of truth and one that fails is almost never the equipment itself — it's the discipline of maintenance and documentation.

This guide explains what's mandatory under Israeli Standard (SI) 1220 and fire-safety requirements, who is authorized to perform each inspection, what needs to appear in the maintenance file, and which faults recur again and again in the field. If you first want the wide picture of the building's entire maintenance setup, it's worth starting with the complete guide to preventive maintenance in an office building and then returning here for the depth of the detection system.

What the system is made of — and why each component is inspected separately

A "fire detection system" isn't a single box but a chain. Every link in it has to work, and a fault in one link nullifies everything after it. It's worth knowing the components by name, because that's exactly how the maintenance report you receive is structured:

• Smoke and heat detectors — deployed across all spaces, in ceiling voids and cable runs. A smoke detector is sensitive to combustion particles; a heat detector is installed where background smoke (steam, dust) would cause false alarms. This distinction matters: sometimes a technician installs a smoke detector next to a floor's kitchenette and the "inspection passes" — until a kettle boils and produces the quarter's third false alarm.
• Control panel — the brain of the system. It shows which zones are active, which are disabled, and which are in fault. The panel's status is the first thing to check when entering the systems room in the morning — and more than once you'll see a "fault" there that's already a week old with no call opened.
• Manual call points and sounders — break-glass call points along the escape routes, and sounders that raise the alert. The call points themselves are inspected too: someone may have hit a call point, the glass may be damaged, or a cleaning worker may have put back an unsuitable cover.
• Emergency PA system — the voice announcement that directs occupants to evacuate. In an occupied office building this is often the most important link: people with headphones, in meetings, in sealed conference rooms — they don't hear a sounder. The PA is the difference between an orderly evacuation and panic.
• Parking garage CO detection — carbon monoxide sensors that activate the garage ventilation. A completely separate component, with a dedicated maintenance provider and its own maintenance regime. Many building managers wrongly assume the main detection company covers this too.
• Integration interfaces — the outputs that link detection to smoke control, to the elevators (which descend to the discharge floor and open), and to fire doors that close automatically. These are the components that quietly fail after any change to other infrastructure that isn't followed by a repeat integration test.

Note: only the first three components are "visible." The PA, the CO detection, and the integration are precisely the parts where the most silent faults are found — and we'll dwell on them further on.

Who's authorized to do what — and it isn't a single party

The most common mistake by building owners and managers is to assume that the maintenance company handling "fire detection" covers everything. In practice, the requirements split the work among several different authorized parties, each bearing separate responsibility:

• Ongoing maintenance and the annual certificate — must be performed by an authorized maintenance company holding a valid standards mark for fire and smoke detection systems. Not any electrician and not any "detection technician" — a certified standards mark is required. When requesting a quote from a maintenance company, the first thing to ask for is a copy of the standards mark and its expiry date.
• Annual maintenance certificate — the same authorized company issues this document at the end of the annual service cycle. This is the document that the fire authority and licensing authorities expect to see — and there's no flexibility on its expiry date.
• Certified lab inspection — in addition to maintenance, a periodic inspection by a certified laboratory is required — an independent party with no interest in signing off as "sound" if it isn't.
• Integration testing — per Israeli Standard (SI) 1220 Part 3: the initial test and the post-change test are performed by an approved laboratory, while the periodic test is performed by an authorized party. A structural change, an elevator upgrade, an electrical board replacement — each requires a repeat integration test.
• Emergency PA — required under Israeli Standard (SI) 1220 Part 11, with dedicated testing and maintenance for the PA lines and speakers, separate from the sounder test.
• Parking garage CO detection — maintained by a company certified by the manufacturer of the CO system. This may be a completely different company from the one maintaining the main detection.

If one provider claims they "cover everything in fire detection for you" — ask to see, separately: the maintenance standards mark, the lab report, and the integration-testing certificate. In many buildings at least one of the three is missing or expired — and not because anyone hid it, but simply because no one managed the schedule.

The maintenance certificate, lab inspection, and integration testing — three completely different documents

The annual maintenance certificate

A certificate the authorized maintenance company issues at the end of the annual service cycle. It declares that the system was maintained as required and is in sound condition. It's important to understand what it is not: it doesn't replace an independent inspection and doesn't confirm that the integration works. Keep it with a clear issue date — it's valid for a year and licensing authorities check this strictly.

The certified lab inspection

Here an external party enters that doesn't maintain the system and therefore has no interest in signing off as "sound." The lab inspects a sample of detectors, the panel's response, the sounders, and the documentation. The lab report is the strongest objective evidence you have that the system actually works. In practice, building managers who receive a report with deficiencies often put it in a drawer. A deficiency found in a report and not closed is an open debt — and in the event of an incident, it may be the point from which the authorities' investigation begins.

Integration testing — the test that reveals whether everything talks to everything

This is the most important test — and the most neglected. Integration testing checks the full chain: a detector senses smoke ← the panel receives it ← the PA is activated ← smoke control kicks in ← the elevators descend to the discharge floor and open ← the fire doors close. It's possible for every component to work perfectly on its own and yet for the chain to break in the middle — and that's exactly where the dangerous failure lies.

Per Israeli Standard (SI) 1220 Part 3, the initial and post-change tests are done by an approved laboratory, and the periodic test by an authorized party. From direct experience, buildings that upgraded their elevators and didn't order a repeat integration test discovered six months later that the elevators don't descend in a fire scenario — because the "signal" from the panel wasn't reconfigured after the elevator control board was changed. Don't give up on orderly documentation of the result of every scenario tested.

What needs to appear in the maintenance file — a checklist

The maintenance file is your legal and operational protection. If a fire breaks out and the system didn't function, the first question anyone asks — the authorities, the insurer, the tenants — will be "where's the documentation." Here's what needs to be in the file, up to date and valid:

If any of these rows is missing — it's not a bureaucratic problem, it's a real weakness in the system. Orderly management of this file is exactly what separates preventive maintenance from break-fix: you want to discover the dead detector at the periodic inspection, not in a fire.

What actually goes wrong — the five faults that recur again and again

1. Zones left disabled after a tenant fit-out

This is the number-one failure, no contest. A tenant does a floor fit-out, the contractor disables detectors so dust and welding work don't trigger false alarms — and then leaves the building without reinstating them. The panel keeps showing "sound" because the disabling is registered as intentional, months go by, and a whole floor is simply unprotected. Every completed tenant job must end with reinstating all zones to operation and a written confirmation. If you manage floor handovers, fold this into the handover checklist.

2. Dead PA lines that no one knows about

The sounder works, the panel detects — but the speakers on a certain floor are silent. A PA line was severed in ceiling work, an amplifier was damaged, a connection came loose. Without a dedicated PA test — where you announce in each zone separately and verify in the field that it's audible — no one will discover this. In a routine maintenance test they check that "the system beeps," not that every real zone is audible. That's the difference between an inspection and a verification.

3. The integration chain that quietly breaks

Detection works, the PA works — but smoke control doesn't receive the signal, or the elevators don't descend to the discharge floor. This happens after any change to a linked system (an electrical board replacement, an elevator upgrade, a software change in a control panel) that wasn't followed by a repeat integration test. Rule of thumb: any change to any of the linked systems requires re-testing the integration — not just testing that system in isolation.

4. Power backup that's never tested

The detection system must operate even during a power outage. The panel's backup batteries wear out over time, and if the generator isn't connected to a coordinated test — in a real power outage the system may fail exactly when you need it. It's worth coordinating the detection test schedule with the building's electrical and generator maintenance, so the power-outage scenario is tested end to end and not each system in isolation.

5. False alarms that train occupants to ignore

A smoke detector placed next to a kitchenette, an air vent, or an industrial coffee machine produces recurring false alarms. The real danger isn't the noise — it's that occupants learn to ignore and not evacuate. If there's an area with recurring false alarms, the solution is to switch to a more suitable heat detector or move the detector — not to disable it. Disabling is a temporary solution that becomes permanent.

Important questions to ask the maintenance provider before signing a contract

Not all maintenance companies cover the same scope. Before signing an annual agreement, it's worth asking explicitly:

• Is your standards mark valid? Ask to see it in writing, with an expiry date. A company that hesitates on this question — stop here.
• Who performs the lab inspection? Is it included in the agreement or outside it? Will they arrange coordination with a certified lab, or is that your responsibility?
• Will you test the integration? Who performs it, at what frequency, and how are the scenarios documented?
• What's included in the PA test? Do you test each zone separately in the field, or just that the system "responds"?
• Who handles parking garage CO detection? Is it a separate company, and who manages the interface between you?

A good company will know how to answer each of these questions without hesitation — and will also be able to explain to you exactly what's included in the agreement and what isn't.

How to build a maintenance routine that actually holds over time

The detection system doesn't live alone. It's part of the building's fire-safety setup, so it's right to plan its maintenance alongside sprinkler and suppression system maintenance — the two systems are sometimes inspected by different providers, but they need to work together in a real fire scenario.

Three operational recommendations that work in the field:

• Manage by expiry dates, not by "when the provider shows up." Record on a calendar the expiry date of the maintenance certificate, the lab report, and the integration testing. Schedule the inspection before the expiry, not after — most buildings where gaps are found discovered them precisely because they waited for the provider to initiate.
• Close every deficiency with a cause and a date. A report that ends with "deficiencies found" without closure documentation is an open debt. Every deficiency needs a handling date, a completion confirmation, and a closure confirmation — three stages, not one.
• Tie every change in the building to a detection test. A completed tenant fit-out, an elevator upgrade, a board replacement — each should trigger an automatic reminder to check that the zones were reinstated and that the integration is still intact. It's not "another inspection" — it's an integral part of the handover.

A well-maintained fire detection system is transparent 99% of the time and irreplaceable in the remaining 1%. What it demands of you isn't an extra expense but documentation discipline: knowing who inspected, what was inspected, when, and what's still open. If you keep this file orderly and valid — you've done the hard part.