MétaCan
Menu
Back to cohort
Record W2050492730 · doi:10.1002/prs.11535

Safety system impairment and the need to manage peak risk

2012· article· en· W2050492730 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueProcess Safety Progress · 2012
Typearticle
Languageen
FieldDecision Sciences
TopicRisk and Safety Analysis
Canadian institutionsNova Chemicals (Canada)
Fundersnot available
KeywordsInterimRisk analysis (engineering)Risk assessmentRisk managementResidual riskProcess (computing)EngineeringOperations managementBusinessActuarial scienceComputer scienceReliability engineeringComputer securityFinancePolitical science

Abstract

fetched live from OpenAlex

Abstract The catastrophic incident that occurred at Bhopal is often referenced with respect to inherent safety issues. Did intermediate chemicals need to be present? Should the neighboring community start at the fence line? Although likely not as important as the aforementioned fundamental considerations, the impairment of safety systems also played a significant role with respect to this event. These impairments took what should have been an unlikely incident and made the catastrophic outcome a near certainty. In this article, a methodology is proposed whereby one should consider both the annualized risk and the peak risk involved in various scenarios when managing process hazards. This approach looks at both the impacts of safety system impairments on the total risk and the fluctuations in short‐term risk levels that will occur at the time of any impairment. For organizations where detailed risk assessments have been conducted for safety instrumented systems, such as those values generated through methods like layer of protection analysis, general impairment guidance can be readily assembled. This guidance looks at the type of protection layer and the potential amount of increased risk, which will result from an impairment. The approach then considers both the duration of the impairment with respect to managing annualized risk and the need for interim risk reduction measures during the impairment to manage peak risk. Questions that arise from this approach include: how much fluctuation in risk is appropriate for an organization and how long should an impairment be allowed to go on for? © 2012 American Institute of Chemical Engineers Process Saf Prog, 2012

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.012
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.505
Threshold uncertainty score0.851

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0120.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.002
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.

Opus teacher head0.023
GPT teacher head0.329
Teacher spread0.307 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it