Fire alarm system - Revision history

Emma: Revise Basic article against FSE writing guidelines: sourced explanations, examples and references (GPT-6)

2026-11-02T18:42:34Z

Revise Basic article against FSE writing guidelines: sourced explanations, examples and references (GPT-6)

Sanne: Add diagrams fse-fire-alarm-system-v1.svg, fse-fire-alarm-system-v2.svg, fse-fire-alarm-system-v3.svg (level-1 visual plan)

2026-11-02T07:09:21Z

Add diagrams fse-fire-alarm-system-v1.svg, fse-fire-alarm-system-v2.svg, fse-fire-alarm-system-v3.svg (level-1 visual plan)

← Older revision		Revision as of 08:09, 2 November 2026
Line 2:		Line 2:

	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" />		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" />
			[[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-2.]]

	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>		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>
Line 52:		Line 53:

	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" />		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" />
			[[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. 28–30.]]

	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" />		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" />
Line 72:		Line 74:

	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" />		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" />
			[[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.]]

	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" />		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" />

Jan: Repair new FSE wiki article: Fire alarm system (written by Kimi Code CLI)

2026-11-02T04:24:04Z

Repair new FSE wiki article: Fire alarm system (written by Kimi Code CLI)

← Older revision		Revision as of 05:24, 2 November 2026
Line 103:		Line 103:
	== See also ==		== See also ==

	* [[~~Detector activation time~~]]		* [[Aspirating smoke detection]]
	* [[~~Evacuation alarm system~~]]		* [[Beam smoke detector]]
	* [[~~Unwanted fire alarms~~]]		* [[Multi-sensor detector]]

	== Notes ==		== Notes ==

Jan: New FSE wiki article: Fire alarm system (written by Kimi Code CLI)

2026-11-02T01:16:03Z

New FSE wiki article: Fire alarm system (written by Kimi Code CLI)

New page

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>

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" />

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>

== Detection and initiation ==

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>

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>

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>

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" />

== Alarm and notification ==

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>

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" />

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" />

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>

== Unwanted fire alarms ==

[[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>

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" />

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>

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" />

== Fire safety management ==

[[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" />

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>

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" />

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" />

== System design and response time ==

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" />

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>

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" />

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" />

== Human response and information ==

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" />

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" />

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" />

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" />

== Reliability and limitations ==

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" />

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" />

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" />

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" />

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" />

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" />

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" />

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" />

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>

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" />

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" />

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 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" />

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" />

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" />

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 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" />

== See also ==

* [[Detector activation time]]
* [[Evacuation alarm system]]
* [[Unwanted fire alarms]]

== Notes ==

<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.
* 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.). 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.). 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. (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]]