An environmental team can file an air or GHG report on time and still have to rebuild the inventory when someone who was not in the room asks how a reported emissions figure was produced. Consider a hypothetical gas plant that has already been reported for a year. A colleague can find the operations equipment list, last year’s inventory, the permit, the lab file, and the monthly operating reports. The lab file includes a gas analysis from a March sample. The operating reports include engine hours. Nothing in those files says which equipment the sample was applied to, or which months of hours entered the engine calculation.
A repeatable emissions data process connects the emissions sources included in a reporting period to the operational records, calculation inputs, methods, and assumptions used to quantify their emissions. Someone who was not involved in preparing those calculations should be able to see how they were prepared and reproduce them from those same inputs and methods.
At the plant, the greenhouse gas calculation for the year includes the compressor engines and the flare. That set of sources, for that period, is the source population. The heater did not operate. Operations may still track it, and the permit may still name it. The team records the heater’s status and how it was treated. Whether a heater with no operating time stays in the population at zero or drops out depends on the program being filed.
Three records commonly help establish which sources are included, and they answer different questions. The operations list describes the equipment on the site. Last year’s inventory describes the sources someone calculated then. The permit describes the equipment the permit names. The team reviews the records relevant to the reporting period and writes down which ones informed the population. The source population may differ between reporting programs.
Equipment installed, removed, or idle during the year may belong in some months and not in others. The team records that status against the emissions source. Seeing the heater on the operations list or on the permit does not settle whether it is in this calculation. Commissioning notes, shutdown records, or other operating documents may be what establishes the status. If the permit’s equipment list is being treated as this period’s source population, check what the permit contains against the inventory for this period.
Throughput or fuel volumes, gas analyses, operating hours, survey measurements, and event records such as blowdowns are common inputs. A laboratory file, an operations report, a historian series, and a contractor survey can each be the right record for the job that system was built to do. For each value an emissions calculation used, the team records the emissions source it was applied to, the reporting period it was applied to, where the value came from, and the value itself. The calculation method and assumptions are documented alongside those inputs.
At the plant, the operating reports provide monthly hours for the compressor engines. The hours are tied to those engines and to the months the engines ran. A laboratory analysis records the composition of a gas sample collected in March. The collection date alone does not say which sources the analysis applies to, or which part of the year it covers. The team documents which sources and reporting periods the sample applies to, along with the calculation method that supports that use.
The flare may take its volume from another record. If the flare’s emissions calculation requires a gas analysis and the team cannot locate one that applies, that input remains unresolved. A gas analysis collected elsewhere at the facility cannot automatically fill that gap. It can apply to the flare if the sample represents the flare gas for the relevant period and the calculation method permits that use.
A blowdown log may record a volume and a date, but the calculation still needs to identify the relevant emissions source and reporting period.
|
What to keep with the calculation |
What it establishes |
|---|---|
|
Facility and emissions source |
The physical source this calculation covers |
|
Reporting period |
When that source is included and when its inputs apply |
|
Originating record |
Where the measurement, volume, analysis, or event was recorded |
|
Calculation input |
The value used from that record |
|
Relationship to the source |
How that value applies to the source and period |
|
Unresolved gaps |
Expected inputs that remain unavailable or unresolved |
The table summarizes the information needed to reconstruct an emissions calculation. It is not a required database layout.
Operating hours sometimes arrive as a historian series rather than a line in the monthly report. Whether that series is fit to use as an emissions input is explained in SCADA data for emissions reporting. When those relationships survive only because someone rebuilds them in a workbook every period, the team is relying on spreadsheets and email to carry the emissions calculations from one year to the next.
The same plant records can support more than one program. A state air inventory applies its own source list, pollutants, and methods, and it may treat the heater differently from the greenhouse gas calculation. A voluntary request can ask for another total from the same facility. Sharing the underlying records does not produce one reported emissions figure. Each program determines which sources, pollutants, boundaries, and methods apply.
The in-house reporting program covers who may accept a value, and why two reported emissions figures drawn from the same activity can both be right.
Take a period the team has already calculated. At the plant, that is the reporting year. Ask someone who wasn’t involved in preparing the report to reproduce the emissions calculations from the documentation alone.
The test succeeds when that person can identify the emissions sources in the population, find the records that supplied the inputs, confirm the periods those inputs apply to, see the calculation method and assumptions, and tell an unresolved input from a value that was used. A shared folder of operating reports and lab files fails when those associations were never written down. Reproducing the emissions calculations from that documentation does not, by itself, show that the calculated emissions were accurate, compliant, or independently verified.
Documenting a missing input does not resolve it. If the team cannot locate an applicable flare analysis, the remaining inputs and calculation records can still be documented. Whether the calculated emissions for the flare can be finalized depends on the applicable reporting requirements and any permitted procedures for handling missing data. Missing data in air and GHG reporting covers that treatment.
Existing files may be sufficient when they preserve enough information for another reporter to reproduce the emissions calculations for the reporting period.
When a later reporter cannot follow the source population, the inputs, and the calculation method from those files, Air & GHG emissions software can keep them with the emissions calculations, beside the operations and laboratory records the company already uses.
For a broader discussion of carbon data management practices (with Verdantix), see Carbon data management in 2024.
Which emissions sources were included for the period, which records and values were used, which periods those values cover, and which calculation method and assumptions were applied. An expected input that never arrived should still be visible.
The underlying records can be shared. Each program still sets its own sources, pollutants or gases, boundary, and method.
Leave the missing input visible against the emissions source and the reporting period. Whether the calculated emissions can be finalized depends on the program and any permitted missing-data procedure.