Gas is often bought and sold not by volume but by energy, in MMBtu or dekatherms, because a cubic foot of rich gas carries more heating value than a cubic foot of lean gas. To report energy, a flow computer has to combine two things it tracks separately, the corrected volume flowing and the heating value of the gas, and accumulate their product over time. That process is energy summation: for each short calculation interval, the flow computer multiplies the volume moved in that interval by the heating value applicable to it and adds the result to a running total. It sounds like simple arithmetic, but the daily energy figure depends on how the averaging period is handled, on whether a live or a contract heating value is used, and on which volume basis feeds the multiply. This guide explains those dependencies and why a historian should store volume, heating value, and energy together per interval.
Energy Summation in one line: Energy summation is the operation a gas flow computer performs to turn volume and heating value into an energy total: for each calculation interval it multiplies the corrected volume that flowed by the gross heating value of the gas and accumulates the products into an energy quantity in MMBtu or dekatherms. The daily energy figure depends on the length and handling of the averaging period, on whether the heating value used is a live analyzer value or a fixed contract value, and on which volume basis is multiplied. Because those choices affect the result, the volume, heating value, and energy for each interval should be stored together so the total can be independently reconstructed.
The mechanics of energy summation are a repeated multiply-and-accumulate. A flow computer runs its measurement calculation many times through the day, typically on a short fixed cycle, and for each cycle it determines how much corrected volume passed during that slice of time. Energy summation multiplies that per-interval volume by the gross heating value in effect for the interval, giving the energy that flowed in that slice, and adds it to a running energy accumulator. Over a day the accumulator sums thousands of these small products into the daily energy total. Doing it interval by interval, rather than multiplying a daily volume by a single daily heating value, is what lets the total correctly reflect the fact that both the flow rate and the gas quality change through the day.
This distinction matters whenever the volume and the heating value are not both constant. If the gas quality shifts while the flow rate also shifts, then the periods of high flow may coincide with a particular heating value, and only a summation that multiplies the matched volume and heating value in each interval captures that correctly. Multiplying a whole day's volume by a whole day's average heating value would be right only if the two never varied together, which is rarely true in practice. The per-interval product is the honest way to weight the heating value by exactly the volume it applied to, and it is why the flow computer accumulates energy continuously rather than once a day.
The output of the summation is an energy quantity in the units the contract uses, most often MMBtu or dekatherms, where a dekatherm is a defined multiple of Btu. The energy accumulator sits alongside the volume accumulators the flow computer already maintains, and at the close of each accounting period the incremental energy for that period is recorded as the energy total. The relationship between the energy total, the volume total, and the heating value is not an afterthought reported separately; it is built into the summation, so the three quantities are internally consistent by construction when the summation is done correctly.
The averaging period is the first thing that shapes the daily energy figure. The heating value used in each interval's multiply has to come from somewhere, and if the analyzer updates less often than the flow computer calculates, the flow computer holds the last heating value between analyses. How that held value is averaged and applied, and how the summation weights heating value across the day, affects the total. GPA 2172 and related guidance describe how heating value and energy should be computed and averaged so that the energy total is defensible, including how a flow-weighted average heating value relates to the summed energy, and following that guidance is what keeps different parties computing the same figure from the same data.
Whether the heating value is live or contract is the second lever. Some arrangements feed the summation a live heating value from an on-site chromatograph, so the energy total tracks the actual gas quality interval by interval. Others use a fixed contract heating value, a single agreed number applied regardless of the real-time analysis, or a value from a sample analyzed later. These produce different energy totals for the same volume whenever the real gas quality differs from the contract number, and neither is wrong in the abstract; the point is that the basis must match what the contract specifies, and a mismatch, such as a flow computer using a live value where the contract expects a fixed one, silently changes the energy billed.
The volume basis feeding the multiply is the third lever and an easy one to get subtly wrong. Energy summation should multiply the heating value by the corrected volume at the same base conditions the heating value is referenced to, because heating value is itself quoted per unit volume at a base condition. If the volume used is at one base and the heating value is referenced to another, the product carries a base-condition inconsistency that biases the energy. Ensuring the volume basis and the heating value basis agree is a quiet but essential part of a correct summation, and it is one of the things a measurement review checks when an energy total does not reconcile with the volume and heating value on their own.
The reason a historian should keep volume, heating value, and energy together for each interval is that custody measurement has to be independently verifiable. An energy total on a statement is only as trustworthy as the ability to reconstruct it, and reconstruction requires knowing, for each interval, both the volume that flowed and the heating value applied to it, because those are the two factors the summation multiplied. If a historian stores only the energy total, an auditor cannot check whether the summation was done correctly; if it stores volume and heating value per interval alongside the energy, the auditor can redo the multiply-and-accumulate and confirm the total.
A cloud SCADA platform such as Merobix is well suited to holding this triplet at interval resolution across a fleet of meters. When the corrected volume, the gross heating value, and the resulting energy are all recorded together per interval, the energy total for any period can be recomputed from the stored volume and heating value and compared against the flow computer's accumulated energy. Agreement confirms the summation; a discrepancy points to something specific, a heating value that was held stale, a base-condition mismatch between volume and heating value, or a contract-versus-live basis error. Because the platform holds the components, the diagnosis does not require pulling raw data from the flow computer in the field.
Storing the triplet also protects the record over time and across the parties who rely on it. Buyer and seller, and any auditor between them, can each independently reconstruct the energy from the same stored volume and heating value, so the energy total is not a black box but a reproducible result. If a dispute arises about a month's energy, the interval-level triplet is the evidence that settles it, showing exactly which volume was multiplied by which heating value to reach the total. Keeping those three quantities linked per interval is what turns energy summation from a number the flow computer asserts into a calculation anyone with the data can verify.
Because both the flow rate and the gas heating value change through the day, and only multiplying the matched volume and heating value in each short interval captures how they vary together. Multiplying a whole day's volume by a single daily heating value would be correct only if neither varied, which is rarely true. The per-interval multiply-and-accumulate correctly weights each heating value by exactly the volume it applied to, producing an energy total consistent with the volume and heating value.
Yes, whenever the real gas quality differs from the contract number. A live heating value from an on-site chromatograph makes the energy total track the actual gas quality interval by interval, while a fixed contract heating value applies one agreed number regardless of the real-time analysis. Both are valid depending on the contract, but they produce different energy totals for the same volume, so the basis the flow computer uses must match what the contract specifies or the energy billed will be quietly wrong.
It must store the corrected volume, the gross heating value, and the resulting energy for each interval, not just the final energy total. The summation multiplies volume by heating value each interval, so reconstructing the total requires both factors at interval resolution. With the volume and heating value stored per interval, an auditor can redo the multiply-and-accumulate and confirm the energy, and any discrepancy points to a specific cause such as a stale heating value or a base-condition mismatch.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.