Methodology for Threat Assessment and Mitigation Planning for Pipeline Integrity
Bibliographic record
Abstract
Abstract Engineering Assessments represent one of the most holistic and comprehensive evaluations of a pipeline’s integrity and maintenance history. As per regulations and industry standards, engineering assessments are required to support operational changes to pipelines, including reactivation of a discontinued pipeline, significant increases to operating pressure, or changes in service fluid. In addition, engineering assessments are often included in operational audits – both internal and external – to evaluate the effectiveness of a pipeline’s integrity management program and can provide a basis for planning future inspection and risk mitigation activities. When properly executed, an engineering assessment will validate existing threat and hazard mitigation and will also identify unmanaged threats and areas where little information exists, facilitating improvement to integrity management. Engineering assessments are complex, multidisciplinary reports that require careful planning to ensure that all potential threats to a pipeline’s integrity have been considered and assessed in accordance with industry standards and requirements. This paper describes an in-depth methodology for carrying out engineering assessments on pipelines. It will outline industry best-practices for evaluating threats and provide criteria for planning future integrity management activities based on the assessment’s findings. Several case studies are also presented to highlight principles covered.
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.008 | 0.020 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.006 | 0.002 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.004 | 0.002 |
| Open science | 0.003 | 0.003 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.012 | 0.002 |
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".