SCC Inspection and Mitigation Program on Suncor OSPL Pipeline: Field Data Trends and Observations
Bibliographic record
Abstract
This paper reviews a recent extensive Stress Corrosion Cracking (SCC) inspection and mitigation program on Suncor Energy’s NPS 16 Oilsands Pipeline (OSPL). The primary focus of the paper will be on the findings, trends, and observations obtained from the actual “as found” field data. Suncor’s SCC management philosophy will also be discussed, including in-line inspection, engineering analysis, data collection and defect mitigation. Suncor Energy owns and operates the 426 km NPS 16” (406.4 mm) OSPL system from the Suncor Oilsands site north of Fort McMurray to Edmonton, Alberta, Canada. The pipeline operates as a batched system and transports a range of products from heavy viscous crude oil, light synthetic crude, naptha and diesel to natural gas liquids (NGL). This pipeline experienced a rupture in August of 2004. The cause of failure was determined to be near-neutral pH Stress Corrosion Cracking (SCC). An extensive excavation and inspection program was undertaken following a comprehensive in-line inspection (ILI) program to detect any crack, metal loss and geometry features. A total of 282 crack field and crack-like features as well as 57 notch-like and non-decidable features were excavated and inspected. A number of trends and observations were identified during the inspection and assessment program. Most of the SCC occurred in an area immediately downstream of a newly commissioned pump station. Also, all SCC was detected in thin wall pipe sections and no SCC was identified in heavy wall pipe sections. Most of the SCC occurred in locations with moderate well to rapidly drained glaciofluvial sands and loamy sands. Field observations and findings along with post rupture metallurgical analysis agreed with recent published developments in the mechanism of near-neutral pH SCC. Suncor completed an extensive integrity program in a relatively short period of time (less than a year). All crack-field and crack-like defects as identified by the UltraScan CD tool were mitigated. Suncor plans to continue their integrity program to ensure the continued safety and integrity of their pipeline facilities.
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.003 | 0.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".