MétaCan
Menu
Back to cohort
Record W1992610389 · doi:10.1115/ipc2006-10183

Implications of Integrity Management Regulations on a Provincially Regulated Pipeline Operator

2006· article· en· W1992610389 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueVolume 1: Project Management; Design and Construction; Environmental Issues; GIS/Database Development; Innovative Projects and Emerging Issues; Operations and Maintenance; Pipelining in Northern Environments; Standards and Regulations · 2006
Typearticle
Languageen
FieldComputer Science
TopicDiverse Research and Applications
Canadian institutionsnot available
Fundersnot available
KeywordsPipeline (software)Integrity managementCorporationPipeline transportRisk analysis (engineering)Computer scienceAsset (computer security)Quality (philosophy)BusinessEngineeringComputer securityFinanceMechanical engineering

Abstract

fetched live from OpenAlex

Recent changes in Alberta pipeline regulations have created a need for provincially regulated companies to embrace broader quality management principals when considering the management of asset integrity. While larger federally regulated transmission pipeline operators have long been regulated towards this quality management approach, smaller provincially regulated operators, (including Exploration & Production companies with pipeline assets) will now be required to move their integrity management programs in a similar direction. Given the diversity in focus, resources, and business objectives of these provincially regulated energy companies, a simple, focused means to execute this transformation is required. This paper reviews the general processes and specific steps undertaken by Pembina Pipeline Corporation in making this transition towards compliance with the revised EUB pipeline regulations. While the approach and initiatives discussed in this paper relate specifically to Alberta pipeline regulations, the general principals are broadly applicable to pipeline operators seeking to develop compliance with goal-oriented regulation.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.475
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0000.001
Open science0.0000.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.

Opus teacher head0.016
GPT teacher head0.264
Teacher spread0.248 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it