Application and challenges of layers of protection analysis (LOPA) in mining processes: Insights into benefits and limitations
Bibliographic record
Abstract
Abstract Layers of protection analysis (LOPA) is a semiquantitative technique widely used in process industries for assessing hazardous scenarios and supporting risk‐informed decision making. It provides a balance between the simplicity of qualitative analysis and the detail of quantitative analysis. This paper discusses the authors' experiences with the application of LOPA in the mining and metals (M&M) industry, combined with traditional methods like HAZOP and HAZID, to identify risks. Several of LOPA's limitations became evident, and scenarios involving human factors, natural events, and asset integrity were excluded from analysis. Certain M&M processes, often complex and heavily reliant on manual operations, pose unique challenges to LOPA's effectiveness due to difficulties in isolating independent protection layers: for example, those involving induction furnaces where overheat scenarios can lead to explosive phase transitions upon contact with water and molten metal. Despite these challenges, the advantages of LOPA, such as enhanced understanding of protection layers and fostering effective safety improvements, are significant. The paper anticipates continued use of LOPA within the company, complemented by safety critical task analysis to manage human errors and enhance safety controls in critical situations.
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.033 | 0.039 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.002 | 0.004 |
| Scholarly communication | 0.008 | 0.008 |
| Open science | 0.002 | 0.005 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
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".