Pipeline Integrity Excavation Challenge in a High Consequence Area
Bibliographic record
Abstract
A portion of Enbridge Pipelines 30 inch crude oil/NGL pipeline runs from Bay City, Michigan to Sarnia, Ontario. A geometry tool found a topside dent indication and GPS data indicated that the dent was located in the Saginaw River which is considered Coast-guard navigable. This pipe segment is located within a defined high consequence area making Pipeline and Hazardous Materials Safety Administration (PHMSA) timing applicable. On top of the normal problems associated with digging in a river, the riverbed soil was known to contain dioxin contamination related to its industrial history. This paper provides an overview of the practical problems encountered in completing this dig. Governmental construction permitting proved to be the most difficult aspect of the work. Contaminated soils caused Enbridge to hire a specialized water handling company. Significant engineering challenges included design and installation of a 100 × 50 foot coffer dam with 70 foot long sheets. The coffer dam design required a flood plain erosion study. After many months of permitting process, all required permits were obtained and construction was started. The construction included three major elements, water handling, coffer dam installation and excavation of the suspected defect. After 2 months of work to uncover the suspected dent, it was located and analyzed. The dent did not meet Enbridge repair criteria, but mechanical reinforcement was installed as a precaution. Final steps included backfilling and coffer dam removal. From start to finish the construction portion of the dig took about 5 months to complete.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.002 | 0.001 |
| 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.003 | 0.001 |
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".