Integration of Pipeline Specifications, Material, and Construction Data: A Case Study
Bibliographic record
Abstract
This paper introduces the concept of a Pipe Data Log (Pipe Log). The idea is not new but a Pipe Log is rarely created for new pipeline projects. A Pipe Log is frequently created as part of the post-construction process and is intended for Integrity purposes. However, creating and populating the Pipe Log as construction proceeds can provide multiple benefits: • Progress of all aspects of construction can be tracked. • Anomalies in data received can be identified immediately and rectified before the project proceeds. • Missing information can be captured before the project is completed and crews are demobilized. • The field engineer can compare with design to verify that the project is being constructed as it was designed. • When construction is complete the Pipe Log will be as well. WorleyParsons Canada Services Ltd., acting as Colt Engineering, worked on behalf of Enbridge Pipelines Inc. and created a detailed Pipe Data Log for the Canadian portion of the Southern Lights LSr Project. The Pipe Log was created using Microsoft® Excel with a line item for each individual piece of pipe that was welded in the pipeline. Information corresponding to the location of each pipe segment, welds performed, material, terrain, coating, protection, and testing was recorded. The Pipe Data Log is excellent for auditing data as the information is being entered. Information collected by the surveyor can be matched to that provided by the pipe mill and by weld and NDE inspectors. Missing or questionable information can be corrected during construction much easier than post-construction. At post-construction, the Pipe Log allows the Integrity team to quickly determine if there are other areas of concern that have similar properties to another problem area.
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.012 | 0.023 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.004 | 0.008 |
| Science and technology studies | 0.003 | 0.002 |
| Scholarly communication | 0.004 | 0.004 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.003 | 0.002 |
| 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".