Engineering search

Standards Dependent. Present the calculation result separately from compliance. Never label it compliant without a verified adopted standard, jurisdiction and project criterion.

Evergreen fire alarm fault finding guide for engineers covering panel messages, wiring faults, device faults, safe testing and documentation.

A practical fire alarm maintenance checklist covering pre-service review, panel checks, device testing, batteries, records and follow-up actions.

How airflow and ventilation affect fire detector performance, why high air-change rooms matter, and what to check — for UK fire alarm engineers.

When fire alarm detectors and devices need physical protection such as guards or cages, the trade-offs involved, and what to check — for UK fire alarm engineers.

How fire detectors are disposed of responsibly, why ionisation devices need special handling, and what to check — for UK fire alarm engineers.

Why fire alarm devices and panels must be compatible, the risks of mixing manufacturers, and how to check before replacing a device — for UK engineers.

How fire detectors are functionally tested — smoke and heat test equipment, why it proves the whole signal path, and good practice — for UK engineers.

A UK engineer's guide to fire detector types — optical smoke, ionisation, heat and multi-sensor — how each responds to fire and where each belongs.

What multi-sensor fire detectors are, how they help balance sensitivity and false alarms, and what to check — for UK fire alarm engineers.

Choosing between heat, optical smoke, multisensor, CO, beam and aspirating detectors — what each responds to and its strengths and limits — for UK engineers.

How analogue addressable detectors report a value, how drift compensation and sensitivity work, and what to check — for UK fire alarm engineers.

How optical beam smoke detectors work, where they suit large open spaces, and their strengths and limits versus point detectors — for UK fire alarm engineers.

How to tell a detector base fault from a head fault using the swap test, base continuity checks and a safe workflow — for UK fire alarm engineers.

Why fire detectors get contaminated, how it causes false alarms, and the right way to clean or replace them — a practical guide for UK engineers.

Why fire detectors have a working life, how end-of-life and replacement are managed, and what to check — for UK fire alarm engineers.

The principles behind fire detector siting and spacing — coverage, ceiling effects and obstructions — and why the exact figures come from BS 5839-1.

How to diagnose an optical beam smoke detector fault — alignment drift, obscuration and contamination — for UK fire alarm engineers.

How UV and IR flame detectors work, where they suit fast-flaming fire risks, their false-alarm sources, and what to check — for UK fire alarm engineers.

How heat detectors are classified, why matching the class to the environment matters, and what to check — for UK fire alarm engineers.

How optical and ionisation smoke detectors differ, where each responds best, and what to check — for UK fire alarm engineers selecting detection.

A field reference for Apollo Discovery addressable fire alarm faults — device faults, loop communication errors, dirty detector warnings, and step-by-step diagnosis.

When and why detection may be omitted from certain areas under a fire alarm category, how it is justified, and what to check — for UK fire alarm engineers.

Optical chambers accumulate dust, insects, steam residue and decorating debris; the analogue value creeps up until the panel flags contamination or pre-alarm. Check the environment first — a detector near an air-handling vent or in a workshop will foul repeatedly no matter how often it's swapped. Clean or replace per the manufacturer's guidance (many heads are exchange-only), record the analogue values before and after, and note repeat offenders: a location that fouls every few months needs a detection-type review, not another clean. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Start with the event log, not opinions: identify which devices, times and conditions generate the unwanted alarms. Then match the fix to the cause — wrong detector type for the environment (steam, dust, cooking), detector siting too close to vents or kitchens, transient activities without temporary management, or genuine faults presenting as alarms. Multi-sensor or heat detection, relocation, cause-and-effect delays where the standard permits them, and client housekeeping all have their place. Change one thing at a time and monitor the log after each change so you know what actually worked. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Walk the whole building, not the drawings: record construction, ceiling heights and voids, occupancy and sleeping risk, environmental challenges (dust, steam, humidity), existing equipment and its condition, cable routes, and anything that will affect detector choice or coverage. Photograph the panel, a sample of devices, and problem areas. Talk to whoever manages the building — the operational reality they describe is the difference between a design that works and one that false-alarms for a year. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

A working demonstration, the documentation pack (certificates, as-fitted drawings, zone chart, cause-and-effect, operation and maintenance instructions), the log book started with commissioning entries, and named training for the people who will actually use the panel — silencing, resetting, testing, and what to do on fire and fault. Record who was trained and when. A handover the client didn't understand generates a call-out within the month. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Judge each defect by its effect on the system's ability to detect and warn: anything that stops detection or alarm in an occupied area, or takes the panel or signalling down, needs immediate action and formal notification to the responsible person. Degraded redundancy, single-device faults and non-urgent wear items follow, with agreed timescales. Put the priority and the consequence in writing — clients act on "this means the second floor has no automatic detection" far faster than on a code. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Confirm which loop or circuit the panel is flagging, then disconnect it at the panel — if the fault clears, the problem is in the field wiring or a device, not the panel. Test the disconnected cable with an insulation-resistance tester, conductor-to-earth on each core, then split the circuit at convenient points (isolators, junction boxes) and re-test each half to close in on the fault. Damp devices, crushed cable, and screws through hidden runs are the usual culprits. Record the readings, not just "fault cleared" — the megger values are your evidence. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

You need four numbers: standby (quiescent) current, full alarm current, required standby duration and required alarm duration — all from the panel documentation, device datasheets or measured at the battery terminals. Capacity = (standby current × standby hours) + (alarm current × alarm hours), then add the safety margin the design standard and panel manufacturer call for (commonly 25%) and round up to the next standard battery size. The classic mistake is using only the panel's quiescent figure and forgetting the loop devices. Confirm durations against the project specification — don't assume 24 hours is always right. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Trigger the alarm condition mapped to the doors and watch them: every held-open door on the interface should release and close fully — a door that releases but doesn't latch hasn't done its job. Confirm re-set behaviour, check local release buttons still work, and verify the interface's monitored wiring reports faults to the panel. Coordinate with the site before testing: releasing every fire door in a busy corridor unannounced doesn't make friends. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Work from the site's approved cause-and-effect matrix — not from memory. Trigger each input condition (or simulate it where live release is unsafe), and confirm every mapped output: sounders, plant shutdowns, door releases, dampers, AOVs, ARC signals. Record each input-output pair as pass/fail with times. Anything that can release suppression or move plant needs isolations agreed in advance and restored afterwards, with the restoration witnessed and recorded. An unversioned or missing matrix is itself a defect worth reporting. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Change default passwords on anything network-connected, restrict remote access to documented, authorised routes, keep firmware current from official sources, and record who holds credentials. Segregate life-safety equipment from general networks where the design allows. Treat engineer access codes as site-specific and confidential — never publish or share defaults. Most compromises of building systems start with a default password nobody changed. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Enough to be safe and useful: how the equipment gets its address (static vs DHCP), what a subnet is, how to ping a device, and how to check a link light before blaming the equipment. Get graphics terminals, gateways and remote monitoring onto documented addresses with the site's IT involved — undocumented static IPs cause outages years later. Never change network settings on shared infrastructure without the client's IT; a fire system that takes down a corporate VLAN is a bad day. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Service effort is weighted by the risk profile of the site and the system's history rather than treated as a uniform checklist: a sleeping-risk premises or a site with recurring faults gets more attention than a low-occupancy unit with a clean record. The maintenance regime still has to meet the recommendations of the applicable standard and the site's fire strategy — risk-based means prioritising within that framework, not cutting visits below it. Document the reasoning so the regime can be defended. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Every panel, PSU, interface and isolation point should carry a durable label matching the site records — device references that agree with the zone chart, circuit references at the distribution board, and warning labels where isolations affect life-safety. Consistent labelling turns a 40-minute hunt into a 2-minute check, and it's what lets a relief engineer work the site safely. Replace missing labels as you find them and note systematic gaps in the service report. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

It must let a stranger — a responding fire officer or a relief engineer — find any device quickly: clear building orientation, zone boundaries that match reality, device locations and addresses, and a revision date. Update it whenever devices are added, moved or re-addressed. A zone chart that no longer matches the installation is worse than none, because people trust it. Flag an out-of-date chart as a defect in your service report. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

What you found, what you tested, what you changed, what remains outstanding, and what the client should do next — with device references and readings, not vague phrases. "Fault cleared" is only acceptable when the report shows the checks that prove it. Record impairments and isolations explicitly, get outstanding defects in writing to the responsible person, and keep the site history so recurring problems are visible across visits rather than rediscovered each time. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Survey what exists: loop protocols and device compatibility, cause-and-effect logic, interfaces to other systems (doors, dampers, plant, ARC), network arrangements, and the state of the as-fitted records. Decide what is being reused and verify the new panel genuinely supports it — protocol compatibility claims deserve testing, not trust. Plan the changeover window, temporary cover while the system is down, retesting scope, and handover documentation. The panel swap is the easy part; the interfaces are where jobs overrun. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Prove the chain: alarm input → control output → damper movement → position feedback to the panel or BMS. Witness the damper actually travel where access allows, don't just trust the status LED. Check the fail-safe state matches the design (open or closed varies by strategy), and that damper faults report somewhere someone watches. Record which dampers were exercised — on large sites rotate through them across the maintenance programme with the ventilation contractor where needed. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Enough for the next engineer to understand the system without you: as-fitted drawings, zone chart, cause-and-effect matrix, device schedule with addresses and locations, loop test results, battery calculations, sound-level results, soak-test outcome, outstanding variations, and the commissioning certificate. Version everything and leave copies on site and in the office file. Half of the difficult service visits trace back to commissioning information that was never handed over. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Radio conditions decide whether a wireless system is viable in that building, on that day, with those contents — and steelwork, stock levels and refurbishments change them. Survey with the manufacturer's tool before design, record signal margins per device location, and re-check when the building use changes or when devices start reporting communication faults. Fit devices at surveyed positions, not convenient ones; a device moved half a metre behind a steel beam can drop off the network. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

The mechanical side kills more doors than the electronics: check closer adjustment, alignment and lock engagement before blaming controllers. Verify the door reports its states honestly (open, forced, held), test the fire-alarm release interface where fitted, and confirm standby battery condition. Review the event log for doors generating constant forced/held events — that's usually alignment or user behaviour, and it trains security staff to ignore real alerts. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

A detector responding to the optical signature of flame (IR and/or UV), used for fast-developing fuel fires where smoke detection is too slow.

A detector combining sensing principles (typically optical and heat) to improve discrimination between real fire signatures and nuisance sources.

A point detector sensing light scattered by smoke particles in its chamber; effective on smouldering fires, more prone to dust and steam nuisance alarms.

An optical detector projecting a beam across a large space, signalling when smoke obscures it; alignment and building movement are its main maintenance issues.

A detector operating on fixed temperature, rate of temperature rise, or both; used where smoke detection would false-alarm, at the cost of slower response.

A passive infrared movement detector; siting, mounting height and environment (heat sources, pets, draughts) determine its reliability.

A fire signal from anything other than a real fire — cooking, steam, dust, works, faults or malicious operation; managed by matching detection type and siting to the environment.

A fire alarm system in which each device has a unique address, letting the panel identify exactly which detector, call point or interface generated an event.

The European product standards for fire detection and alarm system components — panels, power supplies, detectors, call points, sounders, isolators and radio devices each have their own part.

A system that continuously draws air through sampling pipework to a central high-sensitivity detector, used for early warning or difficult spaces.

Requiring two independent detectors in alarm before an output operates — standard practice ahead of suppression release.

The primary fire safety legislation for most non-domestic premises in England and Wales, placing duties on the responsible person including maintenance of fire safety systems.

The raw reading an addressable detector returns to the panel (e.g. chamber obscuration), used to judge sensitivity, drift and contamination.

A detector function that gradually adjusts for chamber contamination to hold sensitivity stable, flagging a fault when the adjustment limit is reached.

A panel warning that a detector's reading has risen above normal but below the alarm threshold — often early contamination, steam or a developing condition.

The UK convention describing system objectives: L categories protect life, P categories protect property, M is manual-only; the category drives detection coverage.

The UK code of practice for fire detection and alarm systems in non-domestic premises, covering design, installation, commissioning and maintenance recommendations.

The UK code of practice for fire detection and alarm systems in domestic premises, including the grade and category conventions for dwellings.

The monitored centre receiving fire and fault signals from site transmission equipment and initiating the agreed response.

The UK code of practice for actuation of release mechanisms for doors — the fire-alarm-to-door-release interface and its categories of actuation.

Fire detection devices and protocols documented through Apollo's official technical library.

Voice alarm and public address equipment represented only at documented product family level.

Fire alarm control equipment documented on Global Fire Equipment's official product pages.

Fire detection control equipment represented from Fike's official product information.

Fire detection devices and systems represented from Nittan Europe's official product information.

Aspirating smoke detection systems represented through official Xtralis product resources.

Fire alarm control equipment documented through official FireClass and Johnson Controls product resources.

Addressable fire detection equipment supported by Eaton product documentation and declarations.

Wireless fire detection systems represented from EMS product and support information.

Fire detection systems covered through Honeywell's official Gent brand resources.

Fire detection devices and systems covered through Hochiki Europe's official document library.

Fire detection control equipment documented by Honeywell Notifier product resources.

Fire detection control equipment documented through Protec's official product, support, software and lifecycle resources.

Fire detection control equipment documented on Siemens' official Cerberus PRO product pages.

Fire detection control equipment documented through official Simplex and Johnson Controls product resources.

Fire alarm control equipment with official product support and technical documentation.

Addressable fire alarm control equipment documented in Bosch product pages and system manuals.

Fire alarm and life safety equipment covered through C-TEC's official support documentation.

Fire alarm control equipment documented in Honeywell's ESSER product and technical libraries.

Fire alarm control equipment represented from Haes Systems product information.

Official videos from Apollo Fire Detectors. Use this official Apollo Fire Detectors resource as a primary route to videos information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official training from Apollo Fire Detectors. Use this official Apollo Fire Detectors resource as a primary route to training information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official videos from Apollo Fire Detectors. Use this official Apollo Fire Detectors resource as a primary route to videos information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Technical support from Apollo Fire Detectors. Use this official Apollo Fire Detectors resource as a primary route to support information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official training from EMS. Use this official EMS resource as the primary starting point for FireCell. It is most useful for training information and should be checked against the exact installed model, document revision and site configuration.

Manuals and documentation from Apollo Fire Detectors. Use this official Apollo Fire Detectors resource as a primary route to manuals information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Technical bulletins from Apollo Fire Detectors. Use this official Apollo Fire Detectors resource as a primary route to bulletins information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Product catalogue from Protec. Use this official Protec resource as a primary route to products information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official training from Honeywell. Use this official Honeywell resource as a primary route to training information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Manuals and documentation from Eaton. Use this official Eaton resource as a primary route to manuals information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official website from Johnson Controls. Use this official Johnson Controls resource as a primary route to website information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official website from EMS. Use this official EMS resource as a primary route to website information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Product catalogue from Xtralis. Use this official Xtralis resource as the primary starting point for VESDA-E VES. It is most useful for products information and should be checked against the exact installed model, document revision and site configuration.

Product catalogue from Xtralis. Use this official Xtralis resource as the primary starting point for VESDA-E VEP. It is most useful for products information and should be checked against the exact installed model, document revision and site configuration.

Official training from Hochiki Europe. Use this official Hochiki Europe resource as a primary route to training information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Product catalogue from Protec. Use this official Protec resource as a primary route to products information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official training from Advanced. Use this official Advanced resource as a primary route to training information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official website from Johnson Controls. Use this official Johnson Controls resource as a primary route to website information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Manuals and documentation from Johnson Controls. Use this official Johnson Controls resource as a primary route to manuals information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Manuals and documentation from Johnson Controls. Use this official Johnson Controls resource as a primary route to manuals information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.