Data foundation
The inventory is computed bottom-up from operators' monthly activity returns and each facility's fluid properties, with factors and parameter distributions from a published factor set. This page says where each input comes from and how it is checked.
- Facilities reporting
- 3 of 3
- Facility-months
- 297
- Record
- 1 Jan 2018 to 1 Mar 2026
Inputs
Four kinds of input, each with its own provenance. Everything else on the platform is derived from them.
- Monthly activity returns
- Per facility and month: producing days, oil, gas produced, flared, used as fuel, exported and reinjected, produced water and cargoes lifted. Metered production reporting to the Petroleum Commission, filed by the operator through the portal or the API and accepted by a reviewer.
- Fluid properties
- Per facility, dated: oil API gravity, gas specific gravity, methane fraction, heating value, separator conditions and the cargo-loading basis. A change is a new dated row, so a past month is always computed with the properties valid then.
- Factor set
- Emission factors and the distribution of every uncertain parameter, with the provenance of each — measured at the facility, from a published source, or assumed within a documented range. One set is in force at a time; publishing a new one is an audited act.
- Satellite retrievals
- Top-down methane observations, imported with their provider and licence. A cross-check only: a divergence raises a question for a reviewer and never changes an inventory figure.
Quality now
Read live from the platform.
- Returns by evidence basis
- 297 measured
- Submissions by status
- none yet
- Flags by status
- none
How a return is checked
Every return, however it arrives, is validated against one published catalogue before a reviewer sees it. An error returns it to the operator; a warning is shown to the reviewer.
- errorDispositions reported with zero production
balance.dispositions_without_production - warningGas balance is near the tolerance limit
balance.gas_close_to_tolerance - errorGas dispositions do not sum to produced gas
balance.gas_does_not_close - errorA required field was left blank
completeness.missing_field - errorExport exceeds produced gas
consistency.export_exceeds_production - errorPeriod must be the first day of a month
format.period_not_month_start - errorThe file could not be read as the published template
format.unreadable - errorProducing days exceeds the calendar month
range.days_exceed_month - errorProducing days is zero
range.days_zero - warningAlmost all produced gas is reported as flared
range.flaring_near_total - errorA reported volume is negative
range.negative - warningWater cut exceeds the 98% modelling cap
range.water_cut_above_cap - errorA period appears more than once
structure.duplicate_period - errorThe submission contains no rows
structure.empty - errorA row is for a different facility than the submission
structure.facility_mismatch - errorA period is missing from the range
structure.missing_period - errorA row falls outside the submission's declared period
structure.period_outside_submission - warningA large month-on-month movement
trend.step_change
The gas balance closes when flared, fuel, exported and reinjected gas sum to gas produced within 2%; a balance off by more than 1% but inside the limit is flagged for the reviewer. A movement above 60% in oil, gas produced or gas flared between consecutive months of a file is a warning, not an error: a shutdown or a well coming on is a real event.
History is never overwritten
A corrected return supersedes the one it replaces; it does not delete it.
Each stored row carries whether it is current. A resubmission marks the earlier rows superseded and points at their replacement, so any figure published from them can be reconstructed exactly. Views can be read as of a past date, and an export can include the history.