The Evolution of Design Tools for Arctic Subsea Pipelines
Bibliographic record
Abstract
Abstract As the demand for energy resources grew, the oil and gas industry looked north for exploration and development of offshore hydrocarbon resources. Significant discoveries were made in Arctic and sub-Arctic regions; however, these environments can be particularly unforgiving on pipelines and offshore structures with a host of geohazards unique to the area. Burial under the seabed became the common practice of protecting offshore Arctic pipelines. Innovative design considerations including installation techniques, leak detection monitoring of the pipelines during operation, and bundling pipelines together aided in the successful completion of these projects. As design engineers on the three subsea pipelines completed in the US Arctic - Northstar (BP), Oooguruk (Pioneer), and Nikaitchuq (ENI) - all in the Beaufort Sea on the North Slope of Alaska, INTECSEA have been able to progressively improve upon design evaluations, building upon learnings from each of the previous projects. Traditional subsea pipeline design is a stress-based approach with individual pipelines either laying on the seabed or buried to a shallow depth to protect against hazards including fishing gear or dragged anchors or for protection against upheaval buckling. In Arctic pipeline design, the extreme environmental loadings tend to require deeper burials, and due to the short installation windows and high cost of installation on-ice, may lead to the use of pipeline bundles to facilitate installation. Strain-based design is generally used for Arctic subsea pipelines due to the extreme displacement-controlled loading conditions. This paper will discuss the evolution of the design considerations and methodologies for Arctic subsea pipelines subjected to the unique Arctic environmental loadings such as strudel scour, permafrost thaw settlement, and ice gouging. These evolving design methodologies are comprised in INTECSEA's in-house suite of Arctic Tools and pipeline design standards. Focus is also placed on the importance of appropriate environmental and geotechnical data collection, the use of limit states design, and the various trenching and backfilling aspects of pipeline design.
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.005 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.008 | 0.004 |
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".