The Approach
Your largest emissions probably happened when nobody was measuring
Surveys and routine inventories capture what a site does in steady state. The largest releases rarely happen in steady state. Blowdowns, pigging runs, upsets, and unplanned venting are over in hours, sometimes minutes, and they drive a disproportionate share of a site's annual total.
They are also what gets noticed. Flyovers, satellites, and regulators catch events, not averages.
When one gets flagged, three questions follow: what happened, how much was released, and can you show it. Answering them takes the event reconstructed from your operating data, not estimated after the fact from a factor.
Systems
Emissions at one point are often caused at another
A relief valve lifting at a station is frequently the end of a chain that started somewhere else: a pressure excursion upstream, a compressor trip, a control set point that no longer fits how the system runs.
Looking at a single site will find the release. Looking at the system finds the reason. That takes people who understand how stations and gathering systems actually operate, which is the part of this work that separates an explanation from a guess.
Why it matters
Events are the gap in every reconciliation
When a top-down site measurement disagrees with a bottom-up inventory, the difference is usually events that were never captured. Documenting them is what closes the gap under OGMP 2.0 Level 5, EU MRV requirements, and the reconciliation protocols buyers and verifiers are adopting.
The same record answers a super-emitter notification, supports routine GHG reporting, and gives you a basis for evaluating any third-party detection that lands on your acreage.
This work pairs directly with our field measurement. Measurement captures what the site emits continuously. Event analysis captures what it emits when something happens. Together they make up the full emission profile.
Process
How an engagement works
- Define the question. A specific event, a third-party detection, or a system-wide profile.
- Gather operating data. SCADA, pressure and flow records, maintenance logs, and operator accounts.
- Reconstruct and quantify. Event volumes and timelines calculated from what the system actually did.
- Reconcile. Results checked against measured data where it exists.
- Report and recommend. Documentation built for the audience reviewing it, with operational changes worth considering.