MétaCan
Menu
Back to cohort
Record W4409509079 · doi:10.5006/c2008-08672

Development of an Equipment Integrity Management System for the Long Lake SAGD Commercial Facility

2008· article· en· W4409509079 on OpenAlexaff
Daryl Foley, Ray Goodfellow

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicTechnology Assessment and Management
Canadian institutionsNexen (Canada)
Fundersnot available
KeywordsIntegrity managementPetroleum engineeringEnvironmental scienceWaste managementEngineeringEnvironmental engineeringPipeline transport

Abstract

fetched live from OpenAlex

Abstract Establishing an equipment integrity management system (IMS) requires focused effort from many disciplines in an organization to ensure that it is fully integrated and sustainable. Integrity Management System manuals have been developed as the guiding documents for equipment integrity programs. The systems necessary to manage inventory, schedule inspections and capture inspection data are key elements of the IMS. Inspection planning should be developed during the design process and capture engineering decisions and risk based life cycle decisions. Business processes and procedures are critical to ensure that inspection and corrosion monitoring tasks are undertaken in an effective manner and documented to maintain control of equipment condition. The program goals are best achieved through maintaining simplicity and ensuring alignment with engineering and maintenance planning processes. Industry standards exist that will guide the IMS development and legislation that dictates minimum requirements to ensure that static process equipment and pipeline systems are managed in a safe and diligent manner.

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 imitation

Not 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.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.002
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: Other design
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.011
Threshold uncertainty score0.036

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0010.000
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0110.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.

Opus teacher head0.036
GPT teacher head0.254
Teacher spread0.218 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designOther design
Domainnot available
GenreEmpirical

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".

Quick stats

Citations1
Published2008
Admission routes1
Has abstractyes

Explore more

Same topicTechnology Assessment and ManagementFrench-language works237,207