Fire & Security FAQ Database

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.

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.

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.

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.

The graded framework matches the system's resistance to the anticipated intruder skill level — higher grades demand more supervision, tamper security and signalling resilience. The grade is set by the risk assessment and, where relevant, insurer requirements, and it drives component selection and signalling: you can't mix a low-grade signalling path with a high-grade requirement and stay compliant. Check the current standard's edition and the insurer's spec before quoting or modifying a graded system. 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.