Reliability Assessment of Pipeline Third Party Damage
Bibliographic record
Abstract
Abstract Pipeline failure statistics indicate that mechanical damage caused by third-party excavation represents the largest threat to the integrity of onshore oil and gas pipelines in North America. In 1999, PRCI developed a reliability model that quantifies the pipeline probability of failure due to the 3rd party damage threat. The model employs a fault tree approach comprised of four main elements: the probability of excavation occurring on the pipeline alignment, the effectiveness of damage preventive measures, the probability that the excavation depth exceeds the depth of cover, and the probability that the excavator force is sufficient to fully penetrate the pipe wall. The PRCI model has been implemented by numerous operating companies over the past two decades. Despite this large contribution, there has been a gap in quantitative assessment techniques regarding the effectiveness of the methods used to prevent mechanical damage, and the pipelines resistance to the impact loads applied to pipelines by excavation equipment. In 2020 Enbridge applied this model to its 25,000+ km liquid pipeline system. During implementation numerous learnings and areas for improvement were identified. Correspondingly, the model was expanded to improve consideration of four important 3rd party damage threats that are not currently included within the model: agricultural activity, vehicle crossings, pipeline exposures, and mitigation activities. The results of this updated model showed that the probability of failure’s due to 3rd party damage were generally increased at locations with high population density, agricultural land use, and road crossings, that exhibited shallow cover. It is expected that this updated model will assist in prioritizing the mitigation of various locations that are potentially susceptible to the 3rd party damage threat in alignment with operator expectations. This paper discusses the data gathering steps required for implementation, example probability of failure results, and provides the details of the model updates which may be incorporated by other operators.
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.002 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".