MétaCan
Menu
Back to cohort
Record W2900216291 · doi:10.1115/ipc2018-78597

Are Integrity Management Programs Making a Difference?

2018· article· en· W2900216291 on OpenAlex
Joe Paviglianiti, Alan Murray, Tijani Elabor

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.
fundA Canadian funder is recorded on the work.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsCanada Energy Regulator
FundersInfrastructure Canada
KeywordsIntegrity managementRisk analysis (engineering)Pipeline (software)Computer scienceData integrityPipeline transportStress corrosion crackingComputer securityBusinessEngineeringCorrosion

Abstract

fetched live from OpenAlex

As a result of numerous stress corrosion cracking incidents in the 1980s and early 1990 the National Energy Board (NEB) held an Inquiry1 in 1995 on the SCC failure mechanism and how to prevent failures. One of the recommendations of the Inquiry was Companies were to develop a SCC management program to proactively identify and mitigate SCC. Based on the apparent success of the SCC programs in significantly reducing SCC failures, the NEB revised its Onshore Pipeline Regulations in 1999 (OPR-99)2 to require companies to develop an integrity management program (IMP) for all hazards. This paper discusses the evolution of integrity management program (IMP) requirements and evaluates incident rates and other performance metrics to determine if there is evidence that IMPs have contributed to the improvement of safety of pipelines. The paper highlights the challenges associated with gathering incident and IMP performance metrics and evaluating the data to determine if there is a correlation between the implementation of IMP and pipeline safety. In addition, the analysis discusses the challenges associated with comparing data between different countries and regulatory jurisdictions. Suggestions for future improvement are identified.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.872
Threshold uncertainty score0.606

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.032
GPT teacher head0.263
Teacher spread0.231 · 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