Element 09 · IOGP 510

Monitoring, Reporting and Learning

To define how performance, events, weak signals and lessons are captured, reported and learned from. This is also where findings originate that feed into the MoC process in Element 5.

"A weak Element 9 reveals itself in two ways: the organisation either doesn't know it has a problem, or it knows but the information cannot travel to a decision-maker. The deeper test: when this element produces a finding, does it actually trigger an MoC? If not, the framework is leaking."
  • ·KPI frameworks and performance dashboards (Engineering KPI Framework, Supplier KPI Framework, HR KPIs)
  • ·Non-conformance and failure reporting (Technical Failure Reporting, Incident & Near Miss Reporting)
  • ·Lessons-learned systems (Lessons Learned Register, Offset Well Reviews)
  • ·Trend and reconciliation reporting (Reserves Reconciliation, Production vs Forecasting Analysis, Spend Analysis Dashboard)
  • ·Action tracking
  • ·Engagement and exit feedback (Engagement Surveys, Exit Interview Process)
  • →The targets the KPIs measure againstE1 Commitment
  • →The MoC process itself — findings here feed into MoC, but the process lives inE5 Risk
  • →The independent challenge of the dataE10 Assurance
IOGP 510 source content

Successful implementation of an OMS depends on clearly understanding whether or not risk controls/barriers are functioning well and operations are delivering planned performance. This requires vigilant monitoring, accurate and complete reporting, and insightful analysis.

  • 1.Processes monitor, measure, verify, validate and record characteristics of operations and products.
  • 2.Incidents, events and non-conformances are reported, recorded, classified and investigated.
  • 3.Processes learn from incidents and implement remedial actions (with application of MoC as appropriate); verify closure of actions.
  • 4.Processes establish leading and lagging KPIs.
  • 5.KPIs are regularly reviewed for meaningful information; data quality is reviewed.