MétaCan
Menu
Back to cohort
Record W2022615486 · doi:10.1115/ipc2002-27277

An Overview of Enbridge’s Pipeline Repair Program

2002· article· en· W2022615486 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

Venue4th International Pipeline Conference, Parts A and B · 2002
Typearticle
Languageen
FieldEngineering
TopicStructural Integrity and Reliability Analysis
Canadian institutionsnot available
Fundersnot available
KeywordsPipeline (software)Pipeline transportProcess (computing)EngineeringExcavationPopulationField (mathematics)Transport engineeringConstruction engineeringComputer scienceCivil engineeringMechanical engineering

Abstract

fetched live from OpenAlex

Enbridge Pipelines Inc. operates the world’s longest and most complex liquids pipeline network and terminals that link the producing areas of Western Canada to refineries and markets in Eastern Canada and the U.S. Midwest. As key components of Enbridge’s Integrity Management Program, In-Line Inspections and Repair Programs have been and will continue to be conducted on the more than 15,000 km of pipeline that make up the Enbridge network. Enbridge’s extensive use of internal inspection technology has resulted in the continued evolution and expansion of the Pipeline Repair Program. The Enbridge repair program is built on an established process. This process involves a team within the pipeline integrity group that assesses In-Line Inspection (ILI) information, validate ILI data, define a repair program, establish field repair teams, provide training & provide advice to repair teams, analyze field reports and maintain the program budget. The field repair teams are responsible for location of the repair sites, environmental and safety concerns, site excavation, defect assessment and repair & backfill. This process has to encompass the challenges of a pipeline network that traverses a variety of conditions, including varied soils, rock, water courses, population densities, regional environmental & land issues. These conditions have to be considered when choosing an ILI tool and when analyzing the data. Construction practices and equipment vary from region to region and repair teams have had to design and build equipment to meet these challenges. Field analysis personnel for all areas of the system are required to collect information on the land form, samples of soils, water, deposits on the pipe wall and a complete analysis of the anomaly and exposed seam & girthwelds. This paper will discuss the components of the program and will present the Pipeline Repair Program as a key driver that not only provides the assessment and repair of anomalies, but plays a key role in the development and testing of new technologies for field & office assessment tools.

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 categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.875
Threshold uncertainty score0.999

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.0020.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.064
GPT teacher head0.308
Teacher spread0.244 · 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