Implementing IOGP 423 - HSE Management Guidelines for Working together in a Contract Environment
Bibliographic record
Abstract
Abstract Contractor HSE Management is a vital process and aligning our efforts is a benefit to all. The 2017 IOGP guide for HSE management throughout a contract lifecycle (IOGP Report 423) place further emphasis on the collaboration between clients and contractors, and their respective responsibilities – including subcontracting; and focus on risk management and assurance mechanisms. Since the publication of 423, an IOGP taskforce has been working on materials to support and facilitate implementation in the Oil & Gas and Energy industry, and to assist with coordination and facilitation of local country implementation workshops. Norwegian members in the taskforce, agreed to pilot the Norwegian implementation. This paper summarizes the material prepared by the taskforce for global implementation, and the planning and key learnings from the Norwegian implementation efforts. Our experience is that stakeholder management requires special attention. In addition, we discuss the specific challenges in the Norwegian context, such as tripartite collaboration and language. This experience is worth sharing for a successful implementation in other countries. The paper also gives some insight into the IOGP guidance content and purpose, supporting contractor HSE management throughout the contracting lifecycle. We will discuss how the IOGP Report 423 provides a risk-based approach, aiming to improve contractor HSE management in alignment with the current Operating Management System (OMS) framework. We discuss the way forward, and propose how an implementation plan can be developed, including; use of the methodology, carry out capability assessments, establish contract requirements and assess and plan training. This paper concludes that the use of IOGP taskforce practical implementation guidance on various 423 topics, will eventually lead to clients and contractors working together, and help to meet the vision that the industry implements and use the 423 guidance with minimum deviations, hence working more safely and saving millions. the IOGP Taskforce agreed not only to deliver the updated guidance, but also paid special attention and time on implementation. However, the implementation journey has proved to be demanding, as you can read throughout this paper.
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.156 | 0.119 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.006 | 0.004 |
| Science and technology studies | 0.009 | 0.010 |
| Scholarly communication | 0.021 | 0.012 |
| Open science | 0.008 | 0.015 |
| Research integrity | 0.011 | 0.009 |
| Insufficient payload (model declined to judge) | 0.012 | 0.007 |
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".