Incorporating Environmental Considerations Into Pipeline Integrity Management Programs
Bibliographic record
Abstract
Canada’s extensive pipeline grid can be traced back to the 1950s when major crude oil and natural gas finds in western Canada led to the construction of large pipeline systems [1]. Some of the currently operating pipelines in Canada have been operating for over 60 years. With the objective of ensuring that pipelines are suitable for continued reliable, safe and environmentally responsible service, the National Energy Board (NEB) issued the Onshore Pipeline Regulations (OPR) in 1999 (OPR-99) mandating pipeline companies to develop and implement Integrity Management Programs (IMPs). The OPR-99 allows pipeline companies to tailor the content of the IMPs to particular circumstances. From a life cycle perspective, the majority of pipeline IMPs involve inspection and testing, data management and interpretation, risk assessment, integrity or engineering assessment and pipeline repairs. Despite the evident benefits of implementing IMPs, conducting pipeline repairs can also trigger environmental concerns and permitting requirements. Developing effective Environmental Protection Plans (EPPs) and obtaining federal and provincial environmental permitting in sensitive areas can be time consuming and costly. If these factors and costs are not incorporated to the planning process they can create subsequent delays and financial burdens. Additionally, implementing environmental management practices throughout the life cycle of IMPs will aid pipeline companies in managing environmental issues systematically and effectively while enhancing environmental stewardship and corporate social responsibility. Including environmental setting considerations, identifying regulatory requirements and conducting stakeholder engagement during the earliest stages and throughout the IMP is essential to ensure the sustainability of the Program. This paper describes an integrated management system which incorporates environmental considerations throughout the overall IMP and a strategic approach to information management.
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.012 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.005 | 0.002 |
| Scholarly communication | 0.005 | 0.003 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.012 | 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".