MétaCan
Menu
Back to cohort
Record W2048331374 · doi:10.1115/ipc2010-31555

Application of Reliability Based Design and Assessment to Maintenance and Protection Decisions for Natural Gas Pipelines

2010· article· en· W2048331374 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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsTransCanada (Canada)
Fundersnot available
KeywordsReliability engineeringPipeline transportReliability (semiconductor)Pipeline (software)Computer scienceMaintenance engineeringEngineeringRisk analysis (engineering)Mechanical engineering

Abstract

fetched live from OpenAlex

This paper describes a detailed assessment that was carried out to investigate the practical implications of using the Reliability Based Design and Assessment (RBDA) methodology, as described in Annex O of CSA Z662, as a basis for evaluating existing pipelines and making decisions on maintenance planning and damage prevention strategies. Two key pipeline failure threats are addressed, namely corrosion and equipment impact. The assessment was based on a number of test cases covering a wide range of diameters, grades, pressures, location classes and corrosion severities. The reliability levels associated with these cases were calculated as a function of time and compared to the reliability targets. Cases that did not meet the targets were re-analyzed with increasingly enhanced maintenance measures until the targets were met. Maintenance actions considered included higher maintenance frequencies and more stringent repair criteria for corrosion, and enhancements to such parameters as right-of-way patrol frequency and condition, public awareness programs and dig notification response for equipment impact. The results demonstrate that the reliability targets can be met through the implementation of reasonable and practical maintenance measures for the cases considered. The impact of using RBDA on the expected failure rates is discussed. In addition, the diameter and class ranges of pipelines requiring enhanced maintenance over the current norm 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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.881
Threshold uncertainty score0.241

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.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.015
GPT teacher head0.272
Teacher spread0.257 · 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