Prepare my site brief: worksheet and printable PDF
01
Identification changes; the need for design remains.
A conventional panel typically identifies the affected circuit or zone, not necessarily each detector on it. An addressable architecture can identify a device by address and associate it with a precise label. That precision is useful only when addresses, locations and documentation agree. A detailed but incorrect label can direct attention to the wrong place.
A loop describes a connection arrangement; a zone is a design-defined grouping for location or operation. Addressable systems can therefore still have zones. Neither maximum address count nor circuit count gives a protected floor area. Selection also depends on building use, required functions, interfaces, operation and requirements identified by the designer.
02
Compare four separate questions.
Scroll the table horizontally to compare all three columns.
| Question | Conventional | Addressable |
|---|---|---|
| Where is the event? | Circuit or zone identification according to equipment and records. | Device address and label, whose mapping must be verified. |
| Which equipment can be combined? | Explicitly compatible panel, detectors, bases and devices. | Supported protocol, versions, modules and required functions. |
| How can existing equipment be retained? | Identify and qualify circuits and components before reuse. | Document what a conventional-zone interface actually identifies. |
| How is expansion prepared? | Reassess design, limits, warning and power requirements. | Perform the same checks; spare addresses are insufficient. |
03
Four records to assemble before comparing panels.
Building and use
Collect current plans, space functions, operating conditions and proposed changes. Have competent parties identify environmental constraints and applicable requirements. Floor area alone cannot establish detector count or type; do not fill these unknowns with a sales rule.
Roles and warning
Separate automatic detection, manual initiation, panel processing and warning devices. Request the intended events and functions. Interfaces to access or building management need defined scope and ownership; a comfort-control application does not replace the dedicated fire chain.
Existing system and combinations
Record references, versions, bases, modules, circuits and available documents. A shared brand does not prove a supported combination. Where an interface connects a conventional zone to an addressable loop, ask whether the received information identifies the interface, zone or each point: do not assume individual addressing of existing detectors.
Operation and acceptance
Identify who operates the panel, approves tests, maintains records and follows unresolved items. Request an appropriate test programme and approved instructions. Power, backup and warning design calculations remain in the specialist dossier, not a generic estimate in this guide.
04
A precise address can have a precisely wrong label.
ILLUSTRATIVE EXAMPLE
Fictional document review: devices D-01 and D-02 are in two separate rooms within zone Z-02. Two proposals describe identification differently. Names and results are invented; no placement, sufficient detector count or live test is prescribed.
Respect the zone’s identification limit
The first dossier specifies a conventional “Z-02” indication. It identifies the group, not necessarily the originating device D-01 or D-02. Plans and instructions must support the intended operation. Renaming the quotation cannot turn this result into individual localisation.
Verify the address mapping
In the second dossier, the report associates A-017 with device D-02, but the plan and display say D-01. The address arrives; the location is wrong. The result fails the intended brief until authorised correction and verification of the physical, plan and display mapping. Other addresses do not validate this one.
Do not confuse acknowledgement with return to normal
The record then says “acknowledged” while an active event remains indicated. Acknowledgement proves neither removal of the cause nor return to normal. Retain the active state and its handling by authorised personnel under site instructions. Resetting a building-control interface does not close this item.
These observations explain information limits; they give no acknowledgement, silencing, reset or disable procedure. A real alarm is handled under emergency instructions by competent people, not by following a catalogue example.
05
Three levels of evidence to keep separate.
Documented combination
Retain exact references and support evidence for each detector, base, interface and warning device. A component mark or document alone does not validate design, installation or operation. Restrictions and versions are part of the answer, not optional footnotes.
Observed function
The supervised programme must establish required functions, states and identifier mappings. Keep alarm, fault, test and disabled states distinct in the report. A phone message proves neither all local warning nor every function’s availability. Live test procedures are not described here.
Handover and tracked exceptions
Request current plans, identifiers, equipment documents, results, unresolved items and approved instructions. Identify who authorises changes and updates records. An apparently clean list is not acceptance if required functions were not verified. Regulatory conclusions belong to the appropriate process and competent parties.
06
Prepare the enquiry without inventing the design.
For an initial Inovexia enquiry, state building type, new or existing status, known architecture, identified references and available documents. Mark missing information “to survey” or “designer to validate”. The catalogue supports a technical enquiry; it replaces neither specialist design nor acceptance. Final quantities and combinations must follow the approved dossier.
07
Five answers that prevent shortcuts.
Does an addressable system still have zones?
Yes, depending on the design. An address identifies a device, a zone organises a group and a loop describes a connection. Request a diagram separating these levels rather than just a spare-address count.
Does an interface make every old detector addressable?
Do not assume so. A zone interface can report a conventional group’s state to an addressable panel. Verify identification, reported events and permitted components. An interface address does not establish individual identification of every existing detector.
Do more detectors necessarily mean better coverage?
No. Quantity, type, placement, environment and functions must follow the building-specific design. This guide provides no per-room count or universal spacing. Adding equipment does not automatically correct unsuitable design.
Can a phone notification replace fire warning?
No. Supplementary reporting does not establish the site’s required detection and warning functions. Each channel, recipient and expected response needs explicit definition; this guide promises no response service.
Does a panel certificate approve the whole installation?
No. Equipment documentation and an installation have different scopes. Check the exact product, combinations and complete dossier against applicable requirements. Inovexia infers neither inspection authority nor site compliance from a component logo.
Technical sources
External reading references. These documents explain principles; they do not certify catalogue products or their combination.
- Which fire alarm and detection system to specifyEaton · Sources consulted on
- Zone monitor unit for addressable fire systemsEaton · Sources consulted on
- MAG4 — Conventional fire alarm panelTeletek Electronics · Sources consulted on
- SIMPO — Addressable fire alarm panelTeletek Electronics · Sources consulted on