A Structured Approach for Managing Engineering Assessments
Bibliographic record
Abstract
Alliance Pipeline, (Alliance), an integrated Canadian and U.S. high-pressure rich natural gas transmission pipeline system, conducts Engineering Assessments for a variety of reasons related to integrity activities such as investigative digs, right-of-way crossings, encroachments and program review; however, the need for a consistent and systematic approach to perform work of this nature was identified. As such, the company launched an initiative to develop a structured approach for undertaking, reviewing and approving Engineering Assessments. The specific challenge in developing a framework for conducting Engineering Assessments is twofold: the framework must be scalable, to address a broad range of situations, while remaining practical to use and understand. In light of these requirements, Alliance chose to adopt a “Tiered” approach to identifying requirements associated with each engineering assessment. The Tier of the Engineering Assessment is defined based on two primary factors: the complexity of the analysis (i.e., whether the methodology of the analysis is well established or not) and the nature of the underlying assumptions (i.e., whether the assumptions associated with the analysis are within established parameters). Once the appropriate Tier has been selected, the framework then provides guidance regarding the specific requirements in the areas of: responsibilities and qualifications of individuals for preparation, review and approval of the assessment as well as documentation. The implementation and use of the structured approach was intended to ensure the Engineering Assessments undertaken within pipeline integrity were technically sound, while recognizing that a broad range of technical complexity, skill level and decision making are associated with Engineering Assessment. Overall, this approach will allow Alliance to achieve a degree of uniformity of its Engineering Assessments in order to manage risks effectively, while addressing the needs of a broad range of scenarios that rely on the methodology.
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.068 | 0.073 |
| Meta-epidemiology (narrow) | 0.003 | 0.003 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.012 | 0.008 |
| Science and technology studies | 0.008 | 0.006 |
| Scholarly communication | 0.025 | 0.017 |
| Open science | 0.010 | 0.018 |
| Research integrity | 0.005 | 0.008 |
| Insufficient payload (model declined to judge) | 0.018 | 0.010 |
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".