Twenty years of performance-based fire protection design: challenges faced and a look ahead
Bibliographic record
Abstract
A review of two decades of worldwide experience using standards, codes and guidelines related to performance-based fire protection design for buildings has identified shortcomings in the interpretation, application and implementation of the performance-based design process, apparent inconsistency in the resulting levels of performance achieved and several opportunities to enhance the process. In a constantly evolving building environment, technical challenges have to be overcome because fire safety engineering still depends greatly on knowledge gained from scientific and engineering research across a broad range of disciplines (e.g., better understanding of the fire phenomena, the behavior and response of the building occupants/contents/structure to the fire, tools for engineering analysis and all the necessary data needed to support tool application). Political challenges also need to be considered as performance-based fire protection design requires the approval of the authority having jurisdiction and other involved stakeholders, at several of its different steps (design, construction, original usage, modifications of usage). The review presented here has been undertaken from an engineering perspective rather than a regulatory perspective. Two key outcomes of this engineering review are that several of the challenges that have been identified are strongly linked to the application of generic guidance to specific problems, which results in critical details being missed, and that some of the engineering issues are treated within a political context, while they should be addressed as purely technical issues.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.040 | 0.030 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.002 | 0.007 |
| Scholarly communication | 0.009 | 0.015 |
| Open science | 0.004 | 0.004 |
| Research integrity | 0.007 | 0.007 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".