MétaCan
Menu
Back to cohort
Record W1977303000 · doi:10.1002/prs.10427

LOPA onions: Peeling back the outer layers

2011· article· en· W1977303000 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 · 2011
Typearticle
Languageen
FieldDecision Sciences
TopicRisk and Safety Analysis
Canadian institutionsNova Chemicals (Canada)
Fundersnot available
KeywordsRisk analysis (engineering)Process (computing)EngineeringReliability (semiconductor)Reliability engineeringRisk assessmentOperations researchComputer scienceComputer securityBusiness

Abstract

fetched live from OpenAlex

Abstract Layer of protection analysis (LOPA) has quickly gained acceptance in the chemical processing industries and has risen to be one of the leading risk assessment techniques used for process safety studies. LOPA generally uses more rigor and science than what is encountered with qualitative risk assessments, while still not becoming overly onerous when compared with detailed quantitative risk assessments. In the interest of balancing time and resources against science and accuracy, certain tradeoffs and assumptions are made within the LOPA assessment. In turn, these tradeoffs and assumptions can lead to inaccurate conclusions. For example, one issue that arises is with the treatment of protection layers associated with mitigation of consequences. LOPA teams have a choice to account for mitigation layers in the consequence assignment or alternatively treat these layers as independent protection layers (IPLs). Although this may appear to be an inconsequential decision, it can in fact result in very different conclusions. In the course of treating mitigation layers as IPLs, organizations must ensure the necessary inspection, testing, and preventive maintenance practices are in place for these layers. Furthermore, recognizing this dichotomy in treatment, one can also show that these mitigation layers should be designed so as to achieve a balance between consequence reduction and desired reliability. This article discusses alternative treatments of risk mitigation layers that are commonly applied by LOPA teams and demonstrates their impacts through case studies. © 2011 American Institute of Chemical Engineers Process Saf Prog, 2011

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.004
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.782
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

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

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.153
GPT teacher head0.381
Teacher spread0.227 · 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