Skip to content
From Fire Safety Academy Wiki
Jan (talk | contribs)
Repair new FSE wiki article: Fire alarm system (written by Kimi Code CLI)
Emma (talk | contribs)
Revise Basic article against FSE writing guidelines: sourced explanations, examples and references (GPT-6)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
A '''Fire alarm system''' is an integrated arrangement for detecting a fire, initiating an alarm and notifying people so that they can respond. It can include smoke and heat detectors, manual call points, control equipment, sounders, voice communication and links to other fire-safety systems. Its purpose is to provide timely and intelligible information rather than merely to register a signal.<ref name="Schifiliti-4-1">Schifiliti, Meacham, and Custer (2002), pp. 4-1–4-2.</ref><ref name="IFEG-1.8-7">Australian Building Codes Board et al. (2005), p. 1.8-7.</ref>
A '''fire alarm system''' detects or receives an indication of fire, processes that information and produces the warning or control signals required by its design. The SFPE Handbook describes these functions as detection, processing and signalling. The system can warn occupants and initiate other protective actions, such as smoke control or door closing.<ref name="SMC_4-2_4-3">Schifiliti, Meacham, and Custer (2002), pp. 4-2–4-3.</ref>


System goals can include life safety, property protection, business protection and environmental concerns, with heritage conservation sometimes included. The required detection time, notification method and system reliability should follow those goals. A fire alarm system is therefore designed as part of a complete strategy, not as a collection of independent devices.<ref name="Schifiliti-4-1" />
Its performance depends on the complete sequence from fire development to the intended response. Smoke or heat must reach an automatic detector before it can operate. Processing and verification may introduce further delay, followed by notification or intervention. A detector's activation time is therefore only one part of the system's response time.<ref name="SMC_4-2_4-3__4-21_4-24">Schifiliti, Meacham, and Custer (2002), pp. 4-2–4-3, 4-21–4-24.</ref>


Detection and notification are different stages. A detector can recognise smoke or heat, while the alarm system decides how to warn occupants and other systems. The complete chain must work before occupants can be expected to respond.<ref name="IFEG-1.8-7" /><ref name="CVM2-30">Ministry of Business, Innovation and Employment (2025), p. 30.</ref>
Engineering assessment starts with the safety objective and the fire scenarios against which it will be checked. Detector selection, location, warning arrangements and human response are then considered together. Testing and management support those assumptions, while analysis identifies delays, uncertain inputs and shared failures that could prevent the intended action.<ref name="SMC_4-1_4-3">Schifiliti, Meacham, and Custer (2002), pp. 4-1–4-3.</ref><ref name="IFEG_1.2-24">Australian Building Codes Board et al. (2005), p. 1.2-24.</ref>


== Detection and initiation ==
== Detection, processing and signalling ==


A [[Smoke detector]] responds to smoke particles and can often provide an earlier indication than a heat detector. It uses technologies such as ionisation, light scattering, optical obscuration, projected beams, air sampling and multi-sensor detection. Each has different responses to particle size, colour and smoke entry.<ref name="NUREG-1805-11-3">U.S. Nuclear Regulatory Commission (2005), pp. 11-3–11-4.</ref><ref name="Schifiliti-4-23">Schifiliti, Meacham, and Custer (2002), p. 4-23.</ref>
Schifiliti, Meacham and Custer divide a fire alarm system into three functional elements: detection, processing and signalling. Detection senses a fire characteristic or receives an initiating input. Processing evaluates that input according to the system's configured functions. Signalling then communicates the warning or command required by the design.<ref name="SMC_4-3">Schifiliti, Meacham, and Custer (2002), p. 4-3.</ref>


A [[Heat detector]] responds to convected thermal energy from a fire, commonly through the ceiling jet. Fixed-temperature devices operate at a selected temperature, while rate-of-rise and rate-compensated devices respond to temperature change. Heat detectors can be useful in confined spaces with rapidly growing high-heat fires or where other detection is unsuitable.<ref name="NUREG-1805-12-1">U.S. Nuclear Regulatory Commission (2005), pp. 12-1–12-2.</ref><ref name="IFEG-2.7-2">Australian Building Codes Board et al. (2005), p. 2.7-2.</ref>
An automatic initiating device responds to a physical fire signature: a [[Smoke detector]] responds to particles, while a [[Heat detector]] responds to thermal conditions. A [[Manual call point]] allows a person who recognises a fire to initiate the alarm. These inputs depend on different mechanisms and need not operate at the same time.<ref name="SMC_4-3_4-4">Schifiliti, Meacham, and Custer (2002), pp. 4-3–4-4.</ref><ref name="CVM_28_29">Ministry of Business, Innovation and Employment (2025), pp. 28–29.</ref>


A [[Manual call point]] allows a person to initiate the alarm. C/VM2 expects simple manual systems to activate immediately after the call point is operated, but discovery still relies on human recognition. Manual initiation therefore depends on occupants seeing or otherwise becoming aware of the fire.<ref name="CVM2-28">Ministry of Business, Innovation and Employment (2025), p. 28.</ref>
The outputs can include an [[Evacuation alarm system]] and commands to other protective systems. The SFPE Handbook gives smoke control, lift recall, door closing and signalling to the fire service as examples. Which outputs operate depends on the intended function of the particular installation. An initiating signal and a completed protective action are therefore different events in the analysis.<ref name="SMC_4-2_4-3" />


Other initiation paths can include suppression devices, ultraviolet or infrared detectors and fire-related human cues. The IFEG prefers automatic alarms in many cases but also allows warnings by others and cues such as sound, smell, sight and touch. Selection should reflect the scenario rather than assuming one initiation method is always best.<ref name="IFEG-1.8-7" />
This functional description does not prescribe a particular control-panel arrangement. The handbook treats panel selection and detailed auxiliary control design as outside its detection calculation chapter, and its method instead follows what each function needs to achieve and when. That distinction allows detector performance to be assessed without assuming that every alarm installation has identical hardware.<ref name="SMC_4-3" />


== Alarm and notification ==
[[File:fse-fire-alarm-system-v1.svg|thumb|upright=1.5|alt=Smoke and heat detectors and call point feeding control, sounders, voice and linked systems.|Fire alarm components serve a shared safety goal. Based on Schifiliti, Meacham, and Custer (2002), pp. 4-1–4-3.]]


An [[Evacuation alarm system]] notifies occupants that they should respond or evacuate. It can use sounders, visual signals, voice messages and staff instructions. Notification should be audible and intelligible to the people concerned, with content that explains the situation and the required action.<ref name="Schifiliti-4-32">Schifiliti, Meacham, and Custer (2002), pp. 4-32–4-33.</ref><ref name="Proulx-3-350">Proulx (2002), pp. 3-350–3-351.</ref>
== Defining what the system must achieve ==


A [[Voice alarm system]] can provide specific live information about the incident and its location. Proulx reports that precise live messages and staff instructions prompted movement more reliably than an alarm tone alone, while prerecorded messages were generally less effective. Message content and authority therefore matter as well as audibility.<ref name="Proulx-3-350" />
The system objective determines what counts as sufficiently early detection. For life safety, warning must leave enough time for the intended occupant response before conditions become untenable. Other objectives can concern damage to equipment, business interruption or environmental consequences. The SFPE Handbook begins its design process by identifying these goals.<ref name="SMC_4-1_4-2">Schifiliti, Meacham, and Custer (2002), pp. 4-1–4-2.</ref>


C/VM2 uses a standard notification time of 30 seconds for standard evacuation strategies. Non-standard strategies, such as management investigating sole activation, require the extended notification time to be included. That period is separate from detector response and any pre-travel activity time.<ref name="CVM2-30" />
A performance objective becomes more useful when expressed through measurable conditions. Examples include limiting the fire's heat release rate or preventing damage beyond a specified item. Heat release rate describes how quickly the fire releases energy. The selected objective determines the latest acceptable point for detection and the subsequent response.<ref name="SMC_4-2_4-3" />


Alarm and notification should also connect with other systems. Smoke control, suppression and door or damper operation can be triggered by the same detection path or by manual action. Redundancy can provide alternative paths, but each component still needs a defined response and a way to recognise failure.<ref name="IFEG-1.2-24">Australian Building Codes Board et al. (2005), p. 1.2-24.</ref>
The fire may continue growing after the detector operates. Processing, warning, staff response or suppression initiation can consume additional time. Schifiliti and colleagues therefore distinguish the limiting design fire from the smaller fire that must trigger detection. The difference depends on fire growth during the remaining response period.<ref name="SMC_4-2_4-3" />


== Unwanted fire alarms ==
Several fire scenarios are considered because fuels, growth rates and locations can vary; the handbook describes testing a candidate design against alternative scenarios after establishing its detector type and spacing. A system that satisfies one scenario may fail its objective in another. This examination connects the detection arrangement to the hazards in the actual occupancy.<ref name="SMC_4-3" />


[[Unwanted fire alarms]] include false, nuisance, test and prank activations that do not represent a real emergency. Frequent false alarms reduce credibility and can make occupants less likely to respond to a genuine alarm. System design should address them without making genuine detection less sensitive or timely.<ref name="Proulx-3-350" /><ref name="Proulx-3-351">Proulx (2002), p. 3-351.</ref>
== Fire signatures and detector response ==


Detector algorithms can reduce nuisance alarms and improve matching to a fire signature. These algorithms vary by manufacturer and are often unpublished, making exact response prediction difficult. System evaluation should use product-specific evidence and tests rather than inventing a universal threshold.<ref name="Schifiliti-4-23" />
A fire signature is a measurable effect of combustion that can be sensed by a detector. Smoke particles, elevated temperature and emitted radiation are different signatures, and their strength and transport depend on the fuel and the fire's development. Selecting a detector therefore involves identifying the signature expected before the limiting fire condition occurs.<ref name="SMC_4-3_4-4" />


Heat detectors generally have a low false-alarm rate among automatic detectors, but they usually respond later than smoke detectors. Their temperature rating must suit the ambient environment, including boiler rooms and other hot spaces. Incorrect rating or placement can create premature activation and reduce confidence in the system.<ref name="NUREG-1805-12-1" /><ref name="NUREG-1805-12-3">U.S. Nuclear Regulatory Commission (2005), p. 12-3.</ref>
Heat detection depends on gases transferring energy to a sensing element, and the gas temperature and velocity at the device affect its rate of heating. Smoke detection depends on particle transport, entry into the sensing chamber and the sensor's response to those particles. Neither process is represented completely by a device's nominal alarm threshold alone.<ref name="SMC_4-5_4-8__4-21_4-24">Schifiliti, Meacham, and Custer (2002), pp. 4-5–4-8, 4-21–4-24.</ref>


Frequent false alarms can become a management problem rather than only a technical one. BS DD240, as discussed by Proulx, uses three or more alarms over six months as an example of a high frequency that can undermine response. Regular testing and maintenance should distinguish real incidents from nuisance conditions without suppressing valid alarms.<ref name="Proulx-3-351" />
Ceiling height, beams and other obstructions can change the route taken by fire products, and a higher plume can entrain more air before reaching the ceiling, reducing temperature and concentration. Air currents are particularly relevant to smoke transport during weak early fires. These effects explain why detector location is part of performance assessment.<ref name="SMC_4-4__4-21_4-22">Schifiliti, Meacham, and Custer (2002), pp. 4-4, 4-21–4-22.</ref>


== Fire safety management ==
Product testing supplies evidence about response under defined conditions; the handbook distinguishes this evidence from a calculation of the installed system's response to a particular fire. Test fuels, airflow and geometry may differ from those in the building. A stated installation spacing therefore needs to be interpreted alongside the conditions and objective of the assessment.<ref name="SMC_4-3_4-4__4-22_4-24">Schifiliti, Meacham, and Custer (2002), pp. 4-3–4-4, 4-22–4-24.</ref>


[[Fire safety management]] includes testing, maintenance, impairment control, training and procedures. It ensures that detectors, control equipment, sounders and communication links continue to operate and that building changes do not invalidate the design. System reliability depends on those ongoing activities.<ref name="CVM2-13">Ministry of Business, Innovation and Employment (2025), p. 13.</ref><ref name="Schifiliti-4-1" />
== Processing decisions and response delays ==


Testing should cover the complete chain where practicable. A detector can work while a sounder, message or communication link fails, and a control panel can indicate a fault without producing an effective occupant response. Acceptance testing and later functional checks should reflect that complete chain.<ref name="Schifiliti-4-1" /><ref name="CVM2-14">Ministry of Business, Innovation and Employment (2025), p. 14.</ref>
Processing can introduce a delay between an initial detector signal and the required output. Alarm verification is one example discussed in the SFPE Handbook, and it is intended to address nuisance signals, but its delay remains part of the response sequence. A timing calculation that omits it can overstate the time available for intervention.<ref name="SMC_4-2__4-28_4-29">Schifiliti, Meacham, and Custer (2002), pp. 4-2, 4-28–4-29.</ref>


Training must be tailored to the building and its occupants. Proulx notes that people trained in one building may take no action when the alarm sounds in another, so staff need specific procedures and enough personnel to guide occupants. Occupants also need credible information about what the alarm means and what action is expected.<ref name="Proulx-3-350" /><ref name="Proulx-3-351" />
The International Fire Engineering Guidelines (IFEG, 2005) describe coincident detection, which requires two or more detectors to operate before an alarm is recognised. The inputs may come from similar detectors at different locations or from different detector types. Such logic changes the condition required to initiate the output. It must therefore be represented when estimating activation rather than treating the first detector as sufficient.<ref name="IFEG_2.7-2">Australian Building Codes Board et al. (2005), p. 2.7-2.</ref>


Management should address unwanted alarms through investigation rather than silence. Recurrent causes can include unsuitable detector type, ambient temperature, contamination, incorrect placement or inappropriate algorithms. Correcting those causes preserves both credibility and genuine detection.<ref name="NUREG-1805-12-3" /><ref name="Schifiliti-4-23" />
[[Unwanted fire alarms]] and genuine fire response need to be considered together. Schifiliti and colleagues describe signal-processing algorithms intended to reduce nuisance alarms and identify fire signatures, and their operation can vary between products and may not be fully published. A simple threshold calculation may consequently omit part of the actual decision process.<ref name="SMC_4-22_4-24">Schifiliti, Meacham, and Custer (2002), pp. 4-22–4-24.</ref>


== System design and response time ==
A warning or control output is useful only in relation to its intended recipient or equipment; the same initiating event may lead to several different actions in the building. The functional description therefore follows each output to the action relevant to the safety objective. This prevents a control-panel indication from being treated as if evacuation or suppression were already complete.<ref name="SMC_4-2_4-3" />


System design starts with the fire scenario and the required response. Expected fuel, fire growth, enclosure geometry and occupant characteristics determine when detection and notification are needed. The design should compare those times with the time required for evacuation and for the fire to reach critical conditions.<ref name="Schifiliti-4-1" /><ref name="IFEG-1.8-7" />
== Worked example of the response time budget ==


Detector response depends on fire size and transport, not only on device sensitivity. Smoke must reach and enter the detector, heat must reach the sensing element, and any entry resistance or thermal lag changes the response. Detector location and spacing therefore require analysis as well as product selection.<ref name="Schifiliti-4-23" /><ref name="Schifiliti-4-24">Schifiliti, Meacham, and Custer (2002), p. 4-24.</ref>
Example 20 in the SFPE detection chapter considers a hotel ballroom and an intended staff response to a chair fire. It assigns 10 s to the system delay between detector activation and alarm initiation. Alarm verification ranges from 15 s to 60 s in that example. Staff take a further 60 s from the indicated alarm to arrival.<ref name="SMC_4-28">Schifiliti, Meacham, and Custer (2002), p. 4-28.</ref>


Response time has several components. Detection is followed by alarm initiation, notification, recognition, pre-travel activity and movement. C/VM2 separately treats detector activation, notification time and pre-travel activity, so these should not be collapsed into one generic delay.<ref name="CVM2-28" /><ref name="CVM2-30" />
The post-detection subtotal is found by adding these successive delays. Using the longer verification time gives 130 s. Using the shorter verification time gives 85 s. Both calculations exclude the time taken for smoke to reach the detector, which the source identifies separately.<ref name="SMC_4-28_4-29">Schifiliti, Meacham, and Custer (2002), pp. 4-28–4-29.</ref>


Redundancy can support reliability by providing backup detection, notification or control paths. The IFEG nevertheless warns that redundant components need not perform identically and that single points of failure must be identified. A backup is useful only if the overall system still produces an effective response.<ref name="IFEG-1.2-24" />
<math display="block">t_{\mathrm{post}}=t_{\mathrm{system}}+t_{\mathrm{verify}}+t_{\mathrm{staff}}</math>


== Human response and information ==
{| class="wikitable"
! Symbol !! Description !! Unit
|-
| <math>t_{\mathrm{post}}</math> || Subtotal after detector activation, excluding smoke transport || s
|-
| <math>t_{\mathrm{system}}</math> || System delay used in the example || s
|-
| <math>t_{\mathrm{verify}}</math> || Alarm verification delay || s
|-
| <math>t_{\mathrm{staff}}</math> || Time from alarm indication to staff arrival || s
|}


A fire alarm signal is a cue, not a guarantee of evacuation. Proulx reports cases where occupants waited for instructions rather than moving when the alarm sounded, while staff or precise live messages produced immediate compliance. The system must therefore provide meaningful information, not only a tone.<ref name="Proulx-3-350" />
<math display="block">t_{\mathrm{post,long}}=10+60+60=130\ \mathrm{s}</math>
<math display="block">t_{\mathrm{post,short}}=10+15+60=85\ \mathrm{s}</math>


Voice communication and staff instructions can explain the incident, location and required action. Their credibility depends on being heard, understood and accepted as authoritative. Message content should be tailored to the building and, where needed, to different occupant groups or phased responses.<ref name="Proulx-3-350" /><ref name="Proulx-3-351" />
These are source-specific example inputs, not standard delays for fire alarm systems. The difference illustrates why a processing feature can change the time available for the intended intervention. The complete assessment must still account for fire development and transport to the detector. It must also justify which verification and staff-response assumptions apply to the scenario.<ref name="SMC_4-28_4-29" />


Familiarity and training influence response. Occupants familiar with the building and its evacuation procedure are more likely to start quickly, while visitors may wait for guidance. Staff presence and clear instructions become especially important in buildings where occupants cannot see what others are doing.<ref name="Proulx-3-350" /><ref name="Proulx-3-351" />
[[File:fse-fire-alarm-system-v2.svg|thumb|upright=1.5|alt=Timeline split into detection, initiation, notification, pre-travel and movement.|A response-time budget separates each delay. Based on Ministry of Business, Innovation and Employment (2025), pp. 26–30.]]


Repeated false alarms can reduce that response still further. People may become less receptive to the alarm and to other cues, making timely and accurate information essential. A well-designed system therefore manages both the technical signal and its credibility over time.<ref name="Proulx-3-351" />
== Connecting the alarm to occupant response ==


== Reliability and limitations ==
Notification is the point at which information reaches the occupants, not the moment at which an automatic detector first senses a fire. New Zealand's C/VM2, second edition (2025), separates detection time from notification time, and it also distinguishes pre-travel activity after notification from movement towards safety. These periods perform different roles in its required safe egress time calculation.<ref name="CVM_26">Ministry of Business, Innovation and Employment (2025), p. 26.</ref>


A fire alarm system does not guarantee detection or evacuation. Detection can be delayed by smoke transport, entry resistance and sensing principles, while notification can fail through equipment, audibility or human response. Each stage needs its own evidence and acceptance criteria.<ref name="Schifiliti-4-23" /><ref name="Proulx-3-350" />
For standard evacuation strategies, C/VM2 assigns 30 s to notification. Where management investigates an activation before notifying occupants, the method requires the extended notification period to be considered. Its pre-travel activity values also vary with occupant group, location and warning type. These are provisions of the New Zealand method rather than universal properties of alarm equipment.<ref name="CVM_29_30">Ministry of Business, Innovation and Employment (2025), pp. 29–30.</ref>


Detector sensitivity does not eliminate unwanted alarms. Ambient conditions, test activations and non-fire signatures can create false indications, and too many can reduce credibility. Correct detector selection, rating and management are necessary to balance sensitivity and reliability.<ref name="NUREG-1805-12-3" /><ref name="Proulx-3-351" />
A [[Voice alarm system]] can supply information that a tone alone does not convey. Proulx describes the influence of informative messages, staff instructions and familiarity on the decision to start moving. Audibility and intelligibility both affect whether a spoken warning can serve its purpose. The alarm's electrical operation and the occupant's response therefore require separate evidence.<ref name="P_3-349_3-351">Proulx (2002), pp. 3-349–3-351.</ref>


Redundancy does not remove every single point of failure. Components can share power, control or communication paths, and those common dependencies can defeat the intended backup. Reliability analysis should include those dependencies and the system's failure indication.<ref name="IFEG-1.2-24" />
Occupants may also receive direct fire cues or warnings from other people. IFEG requires the cue used in an evacuation analysis to be identified and its selection justified. Different groups in different enclosures can receive different information. Treating every occupant as responding immediately to the first panel signal would bypass this part of the assessment.<ref name="IFEG_1.8-7_1.8-9">Australian Building Codes Board et al. (2005), pp. 1.8-7–1.8-9.</ref>


Finally, an alarm tone is not an instruction. Occupants need to know what is happening and what to do, and messages must be credible and intelligible. The system is successful only when it produces an appropriate response within the available time.<ref name="Proulx-3-350" /><ref name="Schifiliti-4-1" />
== Reliability and shared dependencies ==


A response-time budget should show detection, alarm initiation, notification, recognition and pre-travel activity separately. This makes it possible to see which part of the chain consumes the available time and which improvement would actually help. A detector upgrade alone cannot correct a delay caused by unclear notification or occupant behaviour.<ref name="CVM2-28" /><ref name="CVM2-30" />
Several initiating routes can support the same protective action. IFEG gives a shopping-centre example involving detection by people, smoke detectors or sprinklers. Smoke control can likewise receive automatic or manual activation signals. These alternatives provide useful redundancy only when the complete functional paths are considered.<ref name="IFEG_1.2-24" />


System goals should be translated into measurable criteria. Life safety can require activation before a tenability threshold, while property or business protection can require a different response or a different location. Those criteria determine the detector type, placement and the evidence needed for acceptance.<ref name="Schifiliti-4-1" /><ref name="IFEG-1.8-7" />
A redundancy study looks for single points of failure within apparently separate arrangements. If several paths depend on one component, failure of that component can remove their shared function. IFEG therefore asks what backup remains after an individual failure. Counting initiating devices alone does not establish the independence of the resulting warning or control actions.<ref name="IFEG_1.2-24" />


For automatic detection, the fire scenario should include fuel, growth, enclosure and transport. A detector can be highly sensitive and still alarm late if smoke or heat arrives slowly, while a suitable manual cue can be immediate when the fire is visible. Choosing between them requires scenario evidence rather than a general preference.<ref name="IFEG-1.8-7" /><ref name="Schifiliti-4-23" />
The same assessment distinguishes failure from reduced performance. A delayed response can matter even when the equipment eventually operates. IFEG describes sensitivity studies that vary important inputs and uncertainty studies that examine confidence in the outcome. These methods support an explicit treatment of the timing and reliability assumptions used in the design.<ref name="IFEG_1.2-24" />


For manual initiation, the analysis must include human recognition and access. C/VM2 expects immediate activation after operation, but it does not guarantee that a person will see the fire and operate the call point. That distinction should remain visible in the response-time budget.<ref name="CVM2-28" /><ref name="Proulx-3-350" />
The analysis also considers whether failure would be recognised by those responsible for the building. In IFEG's example, the objective includes avoiding unrecognised equipment failure and retaining a backup route, and this connects technical reliability to the arrangements for operating and managing the building. An alternative activation path cannot help if its availability is only assumed.<ref name="IFEG_1.2-24" />


For unwanted alarms, the assessment should track frequency and consequences. A rising number can indicate an environmental or installation problem, and occupants can already be responding less. Correcting the cause is preferable to accepting a noisy system or reducing sensitivity without evaluating the effect on genuine detection.<ref name="Proulx-3-351" /><ref name="NUREG-6850-S1-13-5">U.S. Nuclear Regulatory Commission (2010), p. 13-5.</ref>
[[File:fse-fire-alarm-system-v3.svg|thumb|upright=1.5|alt=Two detection and notification paths sharing one power and control dependency.|Redundant paths can share a single point of failure. Based on Australian Building Codes Board et al. (2005), p. 1.2-24.]]


For final acceptance, the whole chain should be tested under realistic conditions. Detection, control, sounders, messages and backup paths must produce the intended response, and faults must be recognisable. This makes the alarm system a verifiable part of the fire-safety strategy rather than a list of components.<ref name="Schifiliti-4-1" /><ref name="IFEG-1.2-24" />
== Testing, management and the limits of models ==


For final acceptance, the evidence should distinguish detection sensitivity from system effectiveness. A detector can respond correctly while the control, alarm or message fails, and a backup can share the same dependency. The system must therefore be assessed as a complete operational chain rather than as a sensor with an alarm attached.<ref name="Schifiliti-4-1" /><ref name="IFEG-1.2-24" />
[[Fire safety management]] supports the response credited to the installed system. Staff who receive an indication need procedures consistent with the assumed action and timing. Proulx links training to the particular building and its evacuation arrangements. The modelled benefit of staff intervention therefore depends on more than the presence of an alarm output.<ref name="P_3-350_3-351">Proulx (2002), pp. 3-350–3-351.</ref>


The response-time budget should also identify the most effective improvement. Earlier detection can help if it is the largest delay, but clearer instructions, better staff response or fewer unwanted alarms can save more time in other scenarios. This keeps design effort focused on the actual limitation.<ref name="Proulx-3-350" /><ref name="CVM2-30" />
A specialised example appears in the 2010 supplement to NUREG/CR-6850 for United States nuclear facilities, and its very early warning detection assessment depends on acceptance testing, maintenance, calibration and documented settings. It distinguishes an incipient alert from a later fire alarm. These conditions belong to that nuclear cabinet application and are not presented as general building rules.<ref name="N10_13-5_13-7">U.S. Nuclear Regulatory Commission and Electric Power Research Institute (2010), pp. 13-5–13-7.</ref>


A final report should state the goals, the scenario, the initiation and notification paths, and the criteria used for acceptance. It should also record which failure modes were tested and which remain uncertain. That makes the alarm system's role and limitations clear to designers, reviewers and building managers.<ref name="Schifiliti-4-1" /><ref name="CVM2-13" />
The same report requires reductions in sensitivity to be assessed for their effect on early detection. It also relates the credited benefit to personnel locating the source and taking the intended action. This example demonstrates how an engineering claim can depend on both equipment and operating procedures. Changing either can change the performance assumed in the assessment.<ref name="N10_13-6_13-7">U.S. Nuclear Regulatory Commission and Electric Power Research Institute (2010), pp. 13-6–13-7.</ref>


For final acceptance, the complete chain should be demonstrated under the expected operating conditions. Detection, initiation, notification and backup must all produce the intended response, and any fault must be visible to those responsible for the building. This makes reliability a property of the whole system rather than of an individual detector.<ref name="Schifiliti-4-1" /><ref name="IFEG-1.2-24" />
A verification method can prescribe analysis inputs that differ from the characteristics of the installed product. In New Zealand, C/VM2 (2025) requires its tabulated detector values to be used regardless of make or model. Its heat-detector representation uses an activation temperature of 57 °C and a response time index of 30 m<sup>1/2</sup>s<sup>1/2</sup>. The response time index characterises the thermal lag of the sensing element.<ref name="CVM_27">Ministry of Business, Innovation and Employment (2025), p. 27.</ref><ref name="SMC_4-6">Schifiliti, Meacham, and Custer (2002), p. 4-6.</ref>


The response-time budget should also be checked against the fire's development. An alarm can be technically correct and still arrive too late if recognition or pre-movement activity dominates the delay. Reviewing those human stages alongside detector response is necessary for a credible life-safety conclusion.<ref name="Proulx-3-350" /><ref name="CVM2-30" />
The same table assigns an optical density of 0.097 m<sup>−1</sup> at alarm for its smoke-detector representation. Optical density describes attenuation of light by smoke along a specified distance. Projected-beam detectors are treated separately using the beam length and total obscuration setting. These distinctions concern the calculation required by that method, so they do not establish universal product sensitivities.<ref name="CVM_27_28">Ministry of Business, Innovation and Employment (2025), pp. 27–28.</ref>


For final acceptance, the evidence should show that the alarm achieves its intended goal. Life-safety detection must arrive before the relevant hazard threshold, while property or business objectives can require a different response. Evaluating every activation against the same criterion would obscure those different purposes.<ref name="Schifiliti-4-1" /><ref name="IFEG-1.8-7" />
A performance report therefore distinguishes prescribed analysis values, measured device characteristics and assumptions about system operation. Each answers a different question about the proposed arrangement. The handbook's detector calculations need suitable fire and sensor inputs, whereas the New Zealand method specifies some of those inputs directly. Reporting their origin makes the calculation reproducible and exposes where a different method could produce a different result.<ref name="SMC_4-21_4-24">Schifiliti, Meacham, and Custer (2002), pp. 4-21–4-24.</ref><ref name="CVM_27_28" />


A complete evaluation therefore connects the fire scenario, detector response, notification, occupant behaviour and acceptance criteria. It shows where delays and failures occur and which changes improve the result. This makes the fire alarm system a designed safety function rather than a collection of devices with a shared name.<ref name="Schifiliti-4-1" /><ref name="Proulx-3-350" />
Detector models also have limits independent of maintenance. Schifiliti and colleagues identify uncertainty in smoke properties, transport and manufacturer response algorithms. Simplified response estimates need to be interpreted within those limits. Where the required evidence is unavailable, a precise calculated time does not by itself establish precise system performance.<ref name="SMC_4-21_4-24" />


== See also ==
== See also ==


* [[Reliability of fire protection systems]]
* [[Flame detector]]
* [[Aspirating smoke detection]]
* [[Aspirating smoke detection]]
* [[Beam smoke detector]]
* [[Fire curtain]]
* [[Multi-sensor detector]]


== Notes ==
== Notes ==
Line 113: Line 125:
== References ==
== References ==


* Australian Building Codes Board, National Research Council of Canada, International Code Council, & Department of Building and Housing New Zealand. (2005). ''International fire engineering guidelines'' (2005 ed.). Australian Building Codes Board.
* Australian Building Codes Board, National Research Council of Canada, International Code Council, & Department of Building and Housing New Zealand. (2005). ''International fire engineering guidelines''. Australian Building Codes Board.
* Grant, C. C. (2002). Halon design calculations. In P. J. DiNenno (Ed.), ''SFPE handbook of fire protection engineering'' (3rd ed.). National Fire Protection Association.
* Ministry of Business, Innovation and Employment. (2025). ''C protection from fire: Verification method C/VM2'' (2nd ed.).
* Ministry of Business, Innovation and Employment. (2025). ''C protection from fire: Verification method C/VM2'' (2nd ed.). New Zealand Government.
* Proulx, G. (2002). Movement of people: The evacuation timing. In P. J. DiNenno (Ed.), ''SFPE handbook of fire protection engineering'' (3rd ed., pp. 3-342–3-366). National Fire Protection Association.
* Proulx, G. (2002). Movement of people: The evacuation timing. In P. J. DiNenno (Ed.), ''SFPE handbook of fire protection engineering'' (3rd ed.). National Fire Protection Association.
* Schifiliti, R. P., Meacham, B. J., & Custer, R. L. P. (2002). Design of detection systems. In P. J. DiNenno (Ed.), ''SFPE handbook of fire protection engineering'' (3rd ed., pp. 4-1–4-43). National Fire Protection Association.
* Schifiliti, R. P., Meacham, B. J., & Custer, R. L. P. (2002). Design of detection systems. In P. J. DiNenno (Ed.), ''SFPE handbook of fire protection engineering'' (3rd ed.). National Fire Protection Association.
* U.S. Nuclear Regulatory Commission, & Electric Power Research Institute. (2010). ''Fire probabilistic risk assessment methods enhancements'' (NUREG/CR-6850, Supplement 1).
* U.S. Nuclear Regulatory Commission. (2005). ''Fire dynamics tools: Quantitative fire hazard analysis methods for the U.S. nuclear regulatory commission fire protection inspection program'' (NUREG-1805). Author.


[[Category:Detection & Alarm]]
[[Category:Detection & Alarm]]

Latest revision as of 19:42, 2 November 2026

A fire alarm system detects or receives an indication of fire, processes that information and produces the warning or control signals required by its design. The SFPE Handbook describes these functions as detection, processing and signalling. The system can warn occupants and initiate other protective actions, such as smoke control or door closing.[1]

Its performance depends on the complete sequence from fire development to the intended response. Smoke or heat must reach an automatic detector before it can operate. Processing and verification may introduce further delay, followed by notification or intervention. A detector's activation time is therefore only one part of the system's response time.[2]

Engineering assessment starts with the safety objective and the fire scenarios against which it will be checked. Detector selection, location, warning arrangements and human response are then considered together. Testing and management support those assumptions, while analysis identifies delays, uncertain inputs and shared failures that could prevent the intended action.[3][4]

Detection, processing and signalling

Schifiliti, Meacham and Custer divide a fire alarm system into three functional elements: detection, processing and signalling. Detection senses a fire characteristic or receives an initiating input. Processing evaluates that input according to the system's configured functions. Signalling then communicates the warning or command required by the design.[5]

An automatic initiating device responds to a physical fire signature: a Smoke detector responds to particles, while a Heat detector responds to thermal conditions. A Manual call point allows a person who recognises a fire to initiate the alarm. These inputs depend on different mechanisms and need not operate at the same time.[6][7]

The outputs can include an Evacuation alarm system and commands to other protective systems. The SFPE Handbook gives smoke control, lift recall, door closing and signalling to the fire service as examples. Which outputs operate depends on the intended function of the particular installation. An initiating signal and a completed protective action are therefore different events in the analysis.[1]

This functional description does not prescribe a particular control-panel arrangement. The handbook treats panel selection and detailed auxiliary control design as outside its detection calculation chapter, and its method instead follows what each function needs to achieve and when. That distinction allows detector performance to be assessed without assuming that every alarm installation has identical hardware.[5]

Smoke and heat detectors and call point feeding control, sounders, voice and linked systems.
Fire alarm components serve a shared safety goal. Based on Schifiliti, Meacham, and Custer (2002), pp. 4-1–4-3.

Defining what the system must achieve

The system objective determines what counts as sufficiently early detection. For life safety, warning must leave enough time for the intended occupant response before conditions become untenable. Other objectives can concern damage to equipment, business interruption or environmental consequences. The SFPE Handbook begins its design process by identifying these goals.[8]

A performance objective becomes more useful when expressed through measurable conditions. Examples include limiting the fire's heat release rate or preventing damage beyond a specified item. Heat release rate describes how quickly the fire releases energy. The selected objective determines the latest acceptable point for detection and the subsequent response.[1]

The fire may continue growing after the detector operates. Processing, warning, staff response or suppression initiation can consume additional time. Schifiliti and colleagues therefore distinguish the limiting design fire from the smaller fire that must trigger detection. The difference depends on fire growth during the remaining response period.[1]

Several fire scenarios are considered because fuels, growth rates and locations can vary; the handbook describes testing a candidate design against alternative scenarios after establishing its detector type and spacing. A system that satisfies one scenario may fail its objective in another. This examination connects the detection arrangement to the hazards in the actual occupancy.[5]

Fire signatures and detector response

A fire signature is a measurable effect of combustion that can be sensed by a detector. Smoke particles, elevated temperature and emitted radiation are different signatures, and their strength and transport depend on the fuel and the fire's development. Selecting a detector therefore involves identifying the signature expected before the limiting fire condition occurs.[6]

Heat detection depends on gases transferring energy to a sensing element, and the gas temperature and velocity at the device affect its rate of heating. Smoke detection depends on particle transport, entry into the sensing chamber and the sensor's response to those particles. Neither process is represented completely by a device's nominal alarm threshold alone.[9]

Ceiling height, beams and other obstructions can change the route taken by fire products, and a higher plume can entrain more air before reaching the ceiling, reducing temperature and concentration. Air currents are particularly relevant to smoke transport during weak early fires. These effects explain why detector location is part of performance assessment.[10]

Product testing supplies evidence about response under defined conditions; the handbook distinguishes this evidence from a calculation of the installed system's response to a particular fire. Test fuels, airflow and geometry may differ from those in the building. A stated installation spacing therefore needs to be interpreted alongside the conditions and objective of the assessment.[11]

Processing decisions and response delays

Processing can introduce a delay between an initial detector signal and the required output. Alarm verification is one example discussed in the SFPE Handbook, and it is intended to address nuisance signals, but its delay remains part of the response sequence. A timing calculation that omits it can overstate the time available for intervention.[12]

The International Fire Engineering Guidelines (IFEG, 2005) describe coincident detection, which requires two or more detectors to operate before an alarm is recognised. The inputs may come from similar detectors at different locations or from different detector types. Such logic changes the condition required to initiate the output. It must therefore be represented when estimating activation rather than treating the first detector as sufficient.[13]

Unwanted fire alarms and genuine fire response need to be considered together. Schifiliti and colleagues describe signal-processing algorithms intended to reduce nuisance alarms and identify fire signatures, and their operation can vary between products and may not be fully published. A simple threshold calculation may consequently omit part of the actual decision process.[14]

A warning or control output is useful only in relation to its intended recipient or equipment; the same initiating event may lead to several different actions in the building. The functional description therefore follows each output to the action relevant to the safety objective. This prevents a control-panel indication from being treated as if evacuation or suppression were already complete.[1]

Worked example of the response time budget

Example 20 in the SFPE detection chapter considers a hotel ballroom and an intended staff response to a chair fire. It assigns 10 s to the system delay between detector activation and alarm initiation. Alarm verification ranges from 15 s to 60 s in that example. Staff take a further 60 s from the indicated alarm to arrival.[15]

The post-detection subtotal is found by adding these successive delays. Using the longer verification time gives 130 s. Using the shorter verification time gives 85 s. Both calculations exclude the time taken for smoke to reach the detector, which the source identifies separately.[16]

tpost=tsystem+tverify+tstaff

Symbol Description Unit
tpost Subtotal after detector activation, excluding smoke transport s
tsystem System delay used in the example s
tverify Alarm verification delay s
tstaff Time from alarm indication to staff arrival s

tpost,long=10+60+60=130 s tpost,short=10+15+60=85 s

These are source-specific example inputs, not standard delays for fire alarm systems. The difference illustrates why a processing feature can change the time available for the intended intervention. The complete assessment must still account for fire development and transport to the detector. It must also justify which verification and staff-response assumptions apply to the scenario.[16]

Timeline split into detection, initiation, notification, pre-travel and movement.
A response-time budget separates each delay. Based on Ministry of Business, Innovation and Employment (2025), pp. 26–30.

Connecting the alarm to occupant response

Notification is the point at which information reaches the occupants, not the moment at which an automatic detector first senses a fire. New Zealand's C/VM2, second edition (2025), separates detection time from notification time, and it also distinguishes pre-travel activity after notification from movement towards safety. These periods perform different roles in its required safe egress time calculation.[17]

For standard evacuation strategies, C/VM2 assigns 30 s to notification. Where management investigates an activation before notifying occupants, the method requires the extended notification period to be considered. Its pre-travel activity values also vary with occupant group, location and warning type. These are provisions of the New Zealand method rather than universal properties of alarm equipment.[18]

A Voice alarm system can supply information that a tone alone does not convey. Proulx describes the influence of informative messages, staff instructions and familiarity on the decision to start moving. Audibility and intelligibility both affect whether a spoken warning can serve its purpose. The alarm's electrical operation and the occupant's response therefore require separate evidence.[19]

Occupants may also receive direct fire cues or warnings from other people. IFEG requires the cue used in an evacuation analysis to be identified and its selection justified. Different groups in different enclosures can receive different information. Treating every occupant as responding immediately to the first panel signal would bypass this part of the assessment.[20]

Reliability and shared dependencies

Several initiating routes can support the same protective action. IFEG gives a shopping-centre example involving detection by people, smoke detectors or sprinklers. Smoke control can likewise receive automatic or manual activation signals. These alternatives provide useful redundancy only when the complete functional paths are considered.[4]

A redundancy study looks for single points of failure within apparently separate arrangements. If several paths depend on one component, failure of that component can remove their shared function. IFEG therefore asks what backup remains after an individual failure. Counting initiating devices alone does not establish the independence of the resulting warning or control actions.[4]

The same assessment distinguishes failure from reduced performance. A delayed response can matter even when the equipment eventually operates. IFEG describes sensitivity studies that vary important inputs and uncertainty studies that examine confidence in the outcome. These methods support an explicit treatment of the timing and reliability assumptions used in the design.[4]

The analysis also considers whether failure would be recognised by those responsible for the building. In IFEG's example, the objective includes avoiding unrecognised equipment failure and retaining a backup route, and this connects technical reliability to the arrangements for operating and managing the building. An alternative activation path cannot help if its availability is only assumed.[4]

Two detection and notification paths sharing one power and control dependency.
Redundant paths can share a single point of failure. Based on Australian Building Codes Board et al. (2005), p. 1.2-24.

Testing, management and the limits of models

Fire safety management supports the response credited to the installed system. Staff who receive an indication need procedures consistent with the assumed action and timing. Proulx links training to the particular building and its evacuation arrangements. The modelled benefit of staff intervention therefore depends on more than the presence of an alarm output.[21]

A specialised example appears in the 2010 supplement to NUREG/CR-6850 for United States nuclear facilities, and its very early warning detection assessment depends on acceptance testing, maintenance, calibration and documented settings. It distinguishes an incipient alert from a later fire alarm. These conditions belong to that nuclear cabinet application and are not presented as general building rules.[22]

The same report requires reductions in sensitivity to be assessed for their effect on early detection. It also relates the credited benefit to personnel locating the source and taking the intended action. This example demonstrates how an engineering claim can depend on both equipment and operating procedures. Changing either can change the performance assumed in the assessment.[23]

A verification method can prescribe analysis inputs that differ from the characteristics of the installed product. In New Zealand, C/VM2 (2025) requires its tabulated detector values to be used regardless of make or model. Its heat-detector representation uses an activation temperature of 57 °C and a response time index of 30 m1/2s1/2. The response time index characterises the thermal lag of the sensing element.[24][25]

The same table assigns an optical density of 0.097 m−1 at alarm for its smoke-detector representation. Optical density describes attenuation of light by smoke along a specified distance. Projected-beam detectors are treated separately using the beam length and total obscuration setting. These distinctions concern the calculation required by that method, so they do not establish universal product sensitivities.[26]

A performance report therefore distinguishes prescribed analysis values, measured device characteristics and assumptions about system operation. Each answers a different question about the proposed arrangement. The handbook's detector calculations need suitable fire and sensor inputs, whereas the New Zealand method specifies some of those inputs directly. Reporting their origin makes the calculation reproducible and exposes where a different method could produce a different result.[27][26]

Detector models also have limits independent of maintenance. Schifiliti and colleagues identify uncertainty in smoke properties, transport and manufacturer response algorithms. Simplified response estimates need to be interpreted within those limits. Where the required evidence is unavailable, a precise calculated time does not by itself establish precise system performance.[27]

See also

Notes

  1. ↑ 1.0 1.1 1.2 1.3 1.4 Schifiliti, Meacham, and Custer (2002), pp. 4-2–4-3.
  2. ↑ Schifiliti, Meacham, and Custer (2002), pp. 4-2–4-3, 4-21–4-24.
  3. ↑ Schifiliti, Meacham, and Custer (2002), pp. 4-1–4-3.
  4. ↑ 4.0 4.1 4.2 4.3 4.4 Australian Building Codes Board et al. (2005), p. 1.2-24.
  5. ↑ 5.0 5.1 5.2 Schifiliti, Meacham, and Custer (2002), p. 4-3.
  6. ↑ 6.0 6.1 Schifiliti, Meacham, and Custer (2002), pp. 4-3–4-4.
  7. ↑ Ministry of Business, Innovation and Employment (2025), pp. 28–29.
  8. ↑ Schifiliti, Meacham, and Custer (2002), pp. 4-1–4-2.
  9. ↑ Schifiliti, Meacham, and Custer (2002), pp. 4-5–4-8, 4-21–4-24.
  10. ↑ Schifiliti, Meacham, and Custer (2002), pp. 4-4, 4-21–4-22.
  11. ↑ Schifiliti, Meacham, and Custer (2002), pp. 4-3–4-4, 4-22–4-24.
  12. ↑ Schifiliti, Meacham, and Custer (2002), pp. 4-2, 4-28–4-29.
  13. ↑ Australian Building Codes Board et al. (2005), p. 2.7-2.
  14. ↑ Schifiliti, Meacham, and Custer (2002), pp. 4-22–4-24.
  15. ↑ Schifiliti, Meacham, and Custer (2002), p. 4-28.
  16. ↑ 16.0 16.1 Schifiliti, Meacham, and Custer (2002), pp. 4-28–4-29.
  17. ↑ Ministry of Business, Innovation and Employment (2025), p. 26.
  18. ↑ Ministry of Business, Innovation and Employment (2025), pp. 29–30.
  19. ↑ Proulx (2002), pp. 3-349–3-351.
  20. ↑ Australian Building Codes Board et al. (2005), pp. 1.8-7–1.8-9.
  21. ↑ Proulx (2002), pp. 3-350–3-351.
  22. ↑ U.S. Nuclear Regulatory Commission and Electric Power Research Institute (2010), pp. 13-5–13-7.
  23. ↑ U.S. Nuclear Regulatory Commission and Electric Power Research Institute (2010), pp. 13-6–13-7.
  24. ↑ Ministry of Business, Innovation and Employment (2025), p. 27.
  25. ↑ Schifiliti, Meacham, and Custer (2002), p. 4-6.
  26. ↑ 26.0 26.1 Ministry of Business, Innovation and Employment (2025), pp. 27–28.
  27. ↑ 27.0 27.1 Schifiliti, Meacham, and Custer (2002), pp. 4-21–4-24.

References

  • Australian Building Codes Board, National Research Council of Canada, International Code Council, & Department of Building and Housing New Zealand. (2005). International fire engineering guidelines. Australian Building Codes Board.
  • Ministry of Business, Innovation and Employment. (2025). C protection from fire: Verification method C/VM2 (2nd ed.).
  • Proulx, G. (2002). Movement of people: The evacuation timing. In P. J. DiNenno (Ed.), SFPE handbook of fire protection engineering (3rd ed., pp. 3-342–3-366). National Fire Protection Association.
  • Schifiliti, R. P., Meacham, B. J., & Custer, R. L. P. (2002). Design of detection systems. In P. J. DiNenno (Ed.), SFPE handbook of fire protection engineering (3rd ed., pp. 4-1–4-43). National Fire Protection Association.
  • U.S. Nuclear Regulatory Commission, & Electric Power Research Institute. (2010). Fire probabilistic risk assessment methods enhancements (NUREG/CR-6850, Supplement 1).