MétaCan
Menu
Back to cohort
Record W2901507558 · doi:10.1002/prs.12018

Unit reliability and integrity process development and implementation

2018· article· en· W2901507558 on OpenAlexaff
David Hanning

Bibliographic record

VenueProcess Safety Progress · 2018
Typearticle
Languageen
FieldDecision Sciences
TopicRisk and Safety Analysis
Canadian institutionsChevron (Canada)
Fundersnot available
KeywordsDowntimeReliability (semiconductor)Asset (computer security)Reliability engineeringProcess (computing)Unit (ring theory)Process safety managementRisk analysis (engineering)Computer scienceEngineeringComputer securityBusiness

Abstract

fetched live from OpenAlex

A little over 10 years ago, Chevron developed and implemented an Asset Reliability Process with the goal of improving the reliability of our facilities, with a strong focus on improving the availability of our facilities. This was known as URIP or our Unit Reliability Improvement Process. The building blocks of this process include subprocedures for: Design for reliability Reliability opportunity identification and resolution Risk assessment and asset strategy Surveillance and condition monitoring Proactive maintenance Maintenance and failure prevention While we were successful in improving the availability of our facilities with the implementation of URIP, we continued to experience incidents and unplanned downtime associated with the integrity of our assets. As a result, we identified the need to revise our process to place a greater focus on asset integrity. This presentation describes the development and implementation of our revised reliability process, which we have renamed as our Unit Reliability and Integrity Process. The resulting asset care program still includes the subprocedures listed above, with the incorporation of asset integrity requirements. © 2018 American Institute of Chemical Engineers Process Saf Prog 38: e12018, 2019

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 imitation

Not 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.

metaresearch head score (Codex)0.059
metaresearch head score (Gemma)0.113
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.059
Threshold uncertainty score0.314

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0590.113
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0040.002
Science and technology studies0.0020.002
Scholarly communication0.0060.003
Open science0.0050.004
Research integrity0.0020.005
Insufficient payload (model declined to judge)0.0130.008

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.074
GPT teacher head0.440
Teacher spread0.367 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

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".

Quick stats

Citations0
Published2018
Admission routes1
Has abstractyes

Explore more

Same venueProcess Safety ProgressSame topicRisk and Safety AnalysisFrench-language works237,207