Skip to content
From Fire Safety Academy Wiki
Sanne (talk | contribs)
New FSE wiki article: Performance-based code (written by GPT-6)
 
Peter (talk | contribs)
Wiki review: corrected 3 errors: grammar (3) (Claude Opus 5.5)
 
(One intermediate revision by one other user not shown)
Line 5: Line 5:
== From objectives to criteria ==
== From objectives to criteria ==
[[Fire safety objectives]] describe the intended protection of people, property or other valued outcomes. [[Acceptance criteria]] identify the conditions used to assess whether a proposed design meets those objectives. Methods then estimate the relevant performance under selected conditions. The handbook separates these tasks because choosing a model cannot itself determine what level of safety is acceptable. <ref name="FPH-0bb7a67f">Cote et al. (2008), §3.10, pp. 3-167, 3-173–3-174.</ref>
[[Fire safety objectives]] describe the intended protection of people, property or other valued outcomes. [[Acceptance criteria]] identify the conditions used to assess whether a proposed design meets those objectives. Methods then estimate the relevant performance under selected conditions. The handbook separates these tasks because choosing a model cannot itself determine what level of safety is acceptable. <ref name="FPH-0bb7a67f">Cote et al. (2008), §3.10, pp. 3-167, 3-173–3-174.</ref>
[[File:fse-performance-based_code-v1.svg|thumb|upright=1.5|alt=Performance-based code: Goal, Objective, Performance criterion, Evaluation method|From objectives to criteria for a performance-based code.]]


A [[Systems approach to fire-safe design]] considers how prevention, fire control and protection of exposed people or property contribute to an objective. Performance evaluation examines the proposed arrangement against criteria. The handbook stresses that evaluation does not automatically generate the design concept. Engineering judgement is still needed to select and coordinate the measures being assessed. <ref name="FPH-a9c1d364">Cote et al. (2008), §1.9, p. 1-159.</ref>
A [[Systems approach to fire-safe design]] considers how prevention, fire control and protection of exposed people or property contribute to an objective. Performance evaluation examines the proposed arrangement against criteria. The handbook stresses that evaluation does not automatically generate the design concept. Engineering judgement is still needed to select and coordinate the measures being assessed. <ref name="FPH-a9c1d364">Cote et al. (2008), §1.9, p. 1-159.</ref>
Line 10: Line 11:
== Relationship to prescriptive regulation ==
== Relationship to prescriptive regulation ==
[[Equivalency]] can permit a performance assessment within a framework otherwise containing prescriptive requirements. It requires an identified reference and evidence that the alternative meets the relevant level of safety. The [[International Building Code]] belongs to the wider model-code setting discussed by the handbook, but the existence of alternative methods does not make all its provisions performance based. A particular assessment may retain many prescriptive elements. <ref name="FPH-da24e488">Cote et al. (2008), §1.3, pp. 1-58, 1-67; §3.10, p. 3-177.</ref>
[[Equivalency]] can permit a performance assessment within a framework otherwise containing prescriptive requirements. It requires an identified reference and evidence that the alternative meets the relevant level of safety. The [[International Building Code]] belongs to the wider model-code setting discussed by the handbook, but the existence of alternative methods does not make all its provisions performance based. A particular assessment may retain many prescriptive elements. <ref name="FPH-da24e488">Cote et al. (2008), §1.3, pp. 1-58, 1-67; §3.10, p. 3-177.</ref>
[[File:fse-performance-based_code-v2.svg|thumb|upright=1.5|alt=Performance-based code: Prescriptive provisions, Analysed alternatives, Defined assumptions|Relationship to prescriptive regulation for a performance-based code.]]


The [[Authority having jurisdiction]] participates in defining and reviewing the demonstration. The IFEG describes agreement on objectives, analysis methods and criteria through the fire engineering brief. This supports a traceable connection between the problem, the proposed design and the decision. It also gives changes in assumptions a visible place in the review process. <ref name="FPH-3ad43543">Cote et al. (2008), §3.10, p. 3-174.</ref><ref name="IFEG-7b5b1bab">Australian Building Codes Board (2005), §1.2, pp. 1.2-2–1.2-3.</ref>
The [[Authority having jurisdiction]] participates in defining and reviewing the demonstration. The IFEG describes agreement on objectives, analysis methods and criteria through the fire engineering brief. This supports a traceable connection between the problem, the proposed design and the decision. It also gives changes in assumptions a visible place in the review process. <ref name="FPH-3ad43543">Cote et al. (2008), §3.10, p. 3-174.</ref><ref name="IFEG-7b5b1bab">Australian Building Codes Board (2005), §1.2, pp. 1.2-2–1.2-3.</ref>
Line 22: Line 24:
== How the regulatory framework is applied ==
== How the regulatory framework is applied ==
A model document and the law applicable to a particular building are separate parts of the regulatory framework. In the United States context described by the NFPA handbook, a jurisdiction can adopt a model code and modify it. Adoption by reference identifies the document without reproducing its entire text. Local additions, deletions and other changes can affect the resulting obligations. The document title alone therefore does not identify every requirement that applies at a location. The adopted edition and amendments form part of that identification. <ref name="FPH-9371e727">Cote et al. (2008), §1.3, pp. 1-65–1-67.</ref>
A model document and the law applicable to a particular building are separate parts of the regulatory framework. In the United States context described by the NFPA handbook, a jurisdiction can adopt a model code and modify it. Adoption by reference identifies the document without reproducing its entire text. Local additions, deletions and other changes can affect the resulting obligations. The document title alone therefore does not identify every requirement that applies at a location. The adopted edition and amendments form part of that identification. <ref name="FPH-9371e727">Cote et al. (2008), §1.3, pp. 1-65–1-67.</ref>
[[File:fse-performance-based_code-v3.svg|thumb|upright=1.5|alt=Performance-based code: Model document, Adoption and amendments, Applicable requirements, Local implementation|How the regulatory framework is applied for a performance-based code.]]


Referenced standards add another layer. A building code can require a system while a separate standard describes its design, installation or testing. Incorporating that standard by reference can give its specified provisions legal significance within the adopting framework. The relationship depends on the reference and its scope. A reference to one method does not automatically make every statement in the source document a universal requirement. This distinction also explains why several organisations' documents may govern different parts of the same project. <ref name="FPH-532450b7">Cote et al. (2008), §1.3, p. 1-61.</ref>
Referenced standards add another layer. A building code can require a system while a separate standard describes its design, installation or testing. Incorporating that standard by reference can give its specified provisions legal significance within the adopting framework. The relationship depends on the reference and its scope. A reference to one method does not automatically make every statement in the source document a universal requirement. This distinction also explains why several organisations' documents may govern different parts of the same project. <ref name="FPH-532450b7">Cote et al. (2008), §1.3, p. 1-61.</ref>

Latest revision as of 00:37, 16 November 2026

A performance-based code is a regulatory document that expresses required outcomes and provides a framework for demonstrating that they are achieved. It differs in form from provisions that specify a particular material, dimension or arrangement. The NFPA handbook describes performance regulation through goals, objectives and criteria for judging a proposed solution. [1]

The distinction concerns how requirements are expressed, not whether safety is required. Performance-based design is the engineering process used to develop and assess a solution. A code supplies the regulatory basis within which that process operates. The SFPE Handbook's account of risk analysis adds the need to identify the consequences being controlled and the uncertainties in the evidence. A numerical result is meaningful only in relation to those questions. [2][3]

From objectives to criteria

Fire safety objectives describe the intended protection of people, property or other valued outcomes. Acceptance criteria identify the conditions used to assess whether a proposed design meets those objectives. Methods then estimate the relevant performance under selected conditions. The handbook separates these tasks because choosing a model cannot itself determine what level of safety is acceptable. [4]

Performance-based code: Goal, Objective, Performance criterion, Evaluation method
From objectives to criteria for a performance-based code.

A Systems approach to fire-safe design considers how prevention, fire control and protection of exposed people or property contribute to an objective. Performance evaluation examines the proposed arrangement against criteria. The handbook stresses that evaluation does not automatically generate the design concept. Engineering judgement is still needed to select and coordinate the measures being assessed. [5]

Relationship to prescriptive regulation

Equivalency can permit a performance assessment within a framework otherwise containing prescriptive requirements. It requires an identified reference and evidence that the alternative meets the relevant level of safety. The International Building Code belongs to the wider model-code setting discussed by the handbook, but the existence of alternative methods does not make all its provisions performance based. A particular assessment may retain many prescriptive elements. [6]

Performance-based code: Prescriptive provisions, Analysed alternatives, Defined assumptions
Relationship to prescriptive regulation for a performance-based code.

The Authority having jurisdiction participates in defining and reviewing the demonstration. The IFEG describes agreement on objectives, analysis methods and criteria through the fire engineering brief. This supports a traceable connection between the problem, the proposed design and the decision. It also gives changes in assumptions a visible place in the review process. [7][8]

Scenarios and retained prescriptive provisions

A fire scenario is a description of a credible sequence involving ignition, development, protection and occupant response. The handbook treats scenarios as a way to examine linked conditions that cannot be represented by one isolated parameter. A scenario therefore needs enough detail to identify the event being evaluated. The same nominal fire size can have different consequences in different locations or with different protection available. The code's performance criteria and the selected scenarios work together. A favourable calculation for an unspecified event would not establish what part of the design had been assessed. [9]

The handbook's life-safety evaluation process retains some prescriptive requirements within the performance route. This demonstrates that performance and prescription need not be mutually exclusive systems. The proposed design includes both the retained features and the alternatives subject to analysis. Assumptions about the building and occupants also form part of the evaluation. Their inclusion makes the analysis a description of a particular system rather than a free-standing numerical exercise. A change in one of those conditions may require reassessment even when the performance criterion itself has not changed. [10]

An unsuccessful comparison can lead to a revised design and another evaluation. The handbook presents this as an iterative process, with documentation following an acceptable result. The criterion does not have to be redefined simply because an initial proposal fails. Instead, the design, evidence or assumptions can be examined to understand why it falls short. The IFEG similarly treats the brief as a basis for communication through the work. Together, these approaches preserve the connection between the agreed objective and the eventual justification offered for the proposed building. [10][8]

How the regulatory framework is applied

A model document and the law applicable to a particular building are separate parts of the regulatory framework. In the United States context described by the NFPA handbook, a jurisdiction can adopt a model code and modify it. Adoption by reference identifies the document without reproducing its entire text. Local additions, deletions and other changes can affect the resulting obligations. The document title alone therefore does not identify every requirement that applies at a location. The adopted edition and amendments form part of that identification. [11]

Performance-based code: Model document, Adoption and amendments, Applicable requirements, Local implementation
How the regulatory framework is applied for a performance-based code.

Referenced standards add another layer. A building code can require a system while a separate standard describes its design, installation or testing. Incorporating that standard by reference can give its specified provisions legal significance within the adopting framework. The relationship depends on the reference and its scope. A reference to one method does not automatically make every statement in the source document a universal requirement. This distinction also explains why several organisations' documents may govern different parts of the same project. [12]

Construction and continued occupation raise related but different regulatory questions. The handbook describes building codes as principally addressing initial construction and major alterations. Fire prevention codes also address conditions during use, including the maintenance of exits and protection equipment. These responsibilities can involve different officials, although the handbook emphasises cooperation between them. The allocation of authority varies among jurisdictions. An inspection or approval has to be understood in the context of the official's assigned powers. [11]

Existing buildings require particular care in interpreting scope. The handbook distinguishes the treatment of new construction from provisions that apply to existing premises. It identifies NFPA 101 as a code that addresses both, including some requirements imposed without planned construction work. This historical description does not establish the legal status of a later edition. Instead, it explains why the date of construction cannot alone determine the complete fire safety framework. Occupancy, alterations and the adopted provisions remain relevant. [13]

Prescriptive and performance approaches also differ in the evidence they require. A prescriptive provision specifies a solution, such as a construction feature or arrangement. A performance approach identifies an outcome and evaluates whether a proposed design can achieve it under specified conditions. The handbook describes projects that combine both approaches. An analysis addressing a particular departure does not demonstrate that every unrelated requirement has been satisfied. Its boundary remains part of the approval question. [14]

The sources used here describe the regulatory arrangements available when they were published. They provide the historical basis for the terminology and the relationships between documents. Specific numerical obligations belong to the applicable country, document, edition and adoption. This is particularly relevant when a handbook discusses several code families together. Similar aims do not make their classifications, exceptions or detailed provisions interchangeable. [15]

What the assessment has to establish

An assessment starts by identifying what could be harmed and how a fire could produce that harm. Life, property, continuity of operations, heritage and the environment can all be relevant. These objectives overlap, but they do not describe the same outcome. A building that allows everyone to escape can still suffer a loss that stops its activities. Equally, preserving the structure does not necessarily preserve its contents or services. Meacham's account of building fire risk analysis makes these distinctions part of defining the problem. [3]

A hazard assessment then identifies possible ignition sources, combustible materials and the conditions through which fire could spread. The arrangement matters as well as the quantity of material. The description includes the building, its compartments and the protection systems that may affect the event. A hazard assessment asks what could happen under specified conditions. A risk assessment adds consideration of how likely those conditions and consequences are. A calculated consequence therefore does not, by itself, establish a probability of loss. [3]

The people affected need to be described with similar care. An occupancy name provides a useful starting point, but does not fully describe an individual's ability to respond. The NFPA handbook treats occupancy classification as a substitute description for a collection of life safety characteristics. Detailed assessment needs more information when those characteristics determine the result. Age, mobility, awareness, familiarity and available assistance can change the protection that an occupant needs. A category suitable for organising code requirements is therefore not a complete prediction of an evacuation. [16]

Different forms of evidence answer different questions. Inspection can identify an obstruction or an unprotected opening. A calculation can explore a fire scenario under stated assumptions. Historical records can indicate recurring causes or consequences. None of these sources removes the need to check whether the evidence applies to the particular building and activity. Meacham identifies changing materials, uncertain data and future changes in use as limitations when past experience informs a new assessment. [17]

Assessment also includes the behaviour of safeguards when conditions are unfavourable. A review can examine a failed component, an unavailable protection system or an action that does not occur as intended. Fault trees work backwards from an unwanted event towards possible causes. Event trees work forwards from an initiating event through possible outcomes. Their structure can clarify dependencies before reliable numerical probabilities are available. Assigning a number to each branch is a separate evidential step. [18]

The resulting judgement depends on the purpose of the assessment and the acceptance criteria. A result that answers a narrow equipment question may leave wider building risks unresolved. Stakeholders can also value consequences differently, especially where life safety, economic loss and irreplaceable heritage are involved. Recording the scope makes the meaning of an acceptable result visible. It also identifies which changes in use, population or protection would require the assessment to be reconsidered. [3][19]

Evidence, review and the limits of a decision

A fire safety decision needs a defined question before calculations or inspections can resolve it. The International Fire Engineering Guidelines describe a fire engineering brief as the agreed basis for an analysis. It records the scope, relevant stakeholders, building and occupant characteristics, objectives and methods. Acceptance criteria and proposed designs are considered as part of that process. The brief is a technical basis for the assessment, rather than simply the commercial agreement for the work. Its detail varies with the complexity of the problem. [8]

The distinction between an objective and a test of that objective is significant. Protecting occupants states an aim. A criterion identifies a condition against which the design can be evaluated. The calculation method then estimates the quantities needed for that comparison. These steps cannot be replaced by selecting software and accepting its output. The NFPA handbook states that verification methods help evaluate a solution; the design and approval decisions remain with the responsible people. [4]

An analysis depends on its assumptions even when the output appears precise. Input data may be incomplete, the model may simplify a physical process, and actual conditions may vary. The handbook distinguishes uncertainty caused by limited knowledge from variation inherent in the conditions being represented. Additional information can reduce some uncertainties, but cannot remove all variation. Identifying the source of uncertainty makes it possible to judge which further evidence would change the decision. [20]

Sensitivity analysis explores how changing an input changes the result. It can reveal that an apparently minor assumption controls a conclusion. A separate assessment can examine the point at which a result changes from acceptable to unacceptable. These methods help explain the margin between a prediction and the acceptance criterion. They do not create evidence for an input that has no defensible basis. The scale of the uncertainty and the significance of the outcome remain relevant to interpreting the margin. [7]

Review also has an organisational dimension. A reviewer needs enough information to understand the proposed arrangement and the reasons offered for accepting it. The handbook places the authority having jurisdiction within the performance design process from an early stage. The IFEG similarly describes consultation and revision of the brief as the work develops. Early agreement on scope can identify disagreements before they become hidden within a finished calculation. It also makes departures from the original assumptions visible. [7][21]

Professional competence and independence affect the quality of this evidence. Van Rossum explains that complex analyses can be difficult for a reviewing body to check fully. Commercial or organisational interests may also favour a particular result. A technically convincing report therefore depends on competent work and an honest account of assumptions and limitations. These issues concern the integrity of the assessment, alongside the correctness of individual calculations. They cannot be resolved merely by making a report longer or its numerical output more detailed. [22]

See also

Notes

  1. ↑ Cote et al. (2008), §1.3, pp. 1-57–1-58; §3.10, p. 3-167.
  2. ↑ Cote et al. (2008), §3.10, pp. 3-167, 3-173.
  3. ↑ 3.0 3.1 3.2 3.3 Meacham (2002), pp. 5-153–5-155.
  4. ↑ 4.0 4.1 Cote et al. (2008), §3.10, pp. 3-167, 3-173–3-174.
  5. ↑ Cote et al. (2008), §1.9, p. 1-159.
  6. ↑ Cote et al. (2008), §1.3, pp. 1-58, 1-67; §3.10, p. 3-177.
  7. ↑ 7.0 7.1 7.2 Cote et al. (2008), §3.10, p. 3-174.
  8. ↑ 8.0 8.1 8.2 Australian Building Codes Board (2005), §1.2, pp. 1.2-2–1.2-3.
  9. ↑ Cote et al. (2008), §20.1, p. 20-13.
  10. ↑ 10.0 10.1 Cote et al. (2008), §20.1, pp. 20-13–20-14.
  11. ↑ 11.0 11.1 Cote et al. (2008), §1.3, pp. 1-65–1-67.
  12. ↑ Cote et al. (2008), §1.3, p. 1-61.
  13. ↑ Cote et al. (2008), §1.3, p. 1-65; §4.3, p. 4-74.
  14. ↑ Cote et al. (2008), §1.3, pp. 1-57–1-58; §3.10, p. 3-177.
  15. ↑ Cote et al. (2008), §1.3, pp. 1-61, 1-65–1-67.
  16. ↑ Cote et al. (2008), §20.1, p. 20-9.
  17. ↑ Meacham (2002), pp. 5-154–5-156.
  18. ↑ Meacham (2002), p. 5-156.
  19. ↑ Australian Building Codes Board (2005), §1.2.4, pp. 1.2-6–1.2-7.
  20. ↑ Cote et al. (2008), §3.10, p. 3-173.
  21. ↑ Australian Building Codes Board (2005), §1.2, p. 1.2-2.
  22. ↑ Van Rossum (2027), §§2.1–2.3.

References

  • Australian Building Codes Board. (2005). International fire engineering guidelines.
  • Cote, A. E., Grant, C. C., Hall, J. R., Jr., & Solomon, R. E. (Eds.). (2008). Fire protection handbook (20th ed.). National Fire Protection Association.
  • Meacham, B. J. (2002). Building fire risk analysis. In P. J. DiNenno (Ed.), SFPE handbook of fire protection engineering (3rd ed., Section 5, Chapter 12, pp. 5-153–5-175). National Fire Protection Association.
  • Van Rossum, E. (2027). Introduction to Fire Safety Engineering. Fire Safety Academy.