Inside a flow computer measuring orifice gas, the volume does not appear all at once; it is built up second by second from a small quantity that captures the instantaneous driving force of the flow. That quantity is the integral multiplier value, often just called the integral value or the extension, and it is the square root of the differential pressure multiplied by the static pressure. The flow computer integrates this term continuously, and the accumulated integral, combined with the averaged coefficients, becomes the reported volume. Because the integral value sits at the heart of the calculation and is preserved in the audit trail, understanding it is the key to verifying that a reported volume was actually integrated correctly.
Integral Multiplier Value (IMV) in one line: The integral multiplier value, also called the integral value or extension, is the term the flow computer integrates each second to build orifice volume, equal to the square root of the differential pressure times the static pressure. The flow computer sums this term over the period, and multiplying the accumulated integral value by the averaged coefficients yields the reported volume. It appears in the API 21.1 audit trail so that recalculating volume from the stored integral value and averages must reproduce the reported total.
Orifice flow depends on two pressures: the differential pressure across the orifice, commonly written as hw, and the static or flowing pressure, commonly written as Pf. The instantaneous flow is proportional to the square root of the product of those two, and that square root term is the integral value. Each measurement cycle, typically once a second, the flow computer reads hw and Pf, forms the square root of their product, and adds it to a running sum. Over an hour or a day that running sum, the integral of the term over the period, captures the total driving force that produced the flow, and it is deliberately separated from the slower-changing coefficients that scale it into volume.
Separating the fast-changing extension from the slow-changing multiplier is the whole architecture of the calculation. The extension, the square root of hw times Pf, changes rapidly as flow varies, so it must be sampled and integrated frequently to capture every fluctuation. The multiplier, which bundles the orifice geometry, the gas properties, the compressibility, and the correction factors, changes slowly, so it can be computed less often from averaged inputs. Volume for the period is essentially the accumulated integral value times the averaged multiplier, which is why the integral value has to be integrated at high frequency while the multiplier only needs periodic recalculation. This split is what lets a modest flow computer keep an accurate running total without recomputing the entire flow equation every second.
The name integral multiplier value reflects exactly this structure: there is an integral part, the accumulated extension, and a multiplier part, the coefficient that scales it, and the volume is their product. Different vendors and standards use slightly different names, calling the extension the integral value, the IV, or the flow extension, but the physics is the same square root of hw times Pf integrated over time. Recognizing that the reported volume is fundamentally this accumulated square-root term scaled by a coefficient demystifies what the flow computer is doing and gives you a handle on how to check it.
The electronic gas measurement standard requires that a flow computer preserve enough of its intermediate calculation that an auditor can reconstruct the reported volume from stored data, and the integral value is a central part of that record. In the audit trail, the accumulated integral value for each interval is stored alongside the averaged variables such as temperature, pressure, and differential, and the coefficients that were in force. This is not decorative; it is what makes the measurement auditable. The stored integral value is the evidence that the flow computer actually accumulated the driving force it claims, and it is the quantity an auditor recalculates the volume from.
The essential check the audit trail enables is recalculation. Taking the stored integral value for an interval and multiplying it by the multiplier computed from the stored averages must reproduce the reported volume for that interval, within rounding. If it does not, something is wrong: the integration may have hiccuped, a coefficient may have been applied inconsistently, or the stored averages may not be the ones actually used. This recalculation is the backbone of a measurement audit, because it does not take the reported total on faith but rebuilds it from the preserved integral value and averages. A volume that survives this reconstruction is defensible; one that does not points straight at where the calculation went astray.
Because the integral value is preserved per interval, it also localizes problems in time. If the daily total is wrong, comparing the per-interval integral values against the per-interval reported volumes narrows the discrepancy to specific hours, which is far more useful than knowing only that the day does not balance. The integral value effectively timestamps the driving force, so an integration error that occurred during a particular pressure excursion or a particular hour shows up as an interval where the recalculation fails while its neighbors pass. This granularity is exactly why the standard insists the integral value be stored rather than discarded once the volume is computed.
Traditionally, checking the integral value meant going to the flow computer, pulling its stored records, and reconstructing volume by hand, which is why integration errors often went unnoticed until an audit or a monthly reconciliation. If the integral value and the averaged inputs are pulled into a SCADA layer instead, a measurement technician can see the same intermediate quantities without a site trip. Surfacing the per-interval integral value alongside the reported volume lets someone verify that volume divided by integral value gives a sensible multiplier, and that the multiplier is stable from interval to interval, which is a quick sanity check on the whole calculation.
A cloud SCADA platform such as Merobix can bring the integral value forward as a first-class trend rather than leaving it buried in the flow computer. Trending the per-interval integral value against differential and static pressure makes integration problems visible: if the pressures were high but the integral value did not accumulate proportionally, the integration stalled or the sampling faltered, and that shows up as a break in the expected relationship. Because the integral value is the accumulated driving force, watching it move with hw and Pf is a direct check that the flow computer is doing its arithmetic, and it exposes a stuck or under-sampled integration long before the daily total is audited.
The operational payoff is catching integration errors early and locally. A measurement tech watching per-interval integral values in a dashboard can spot the interval where the integral value went flat while flow was clearly present, or where it spiked implausibly, and investigate that specific flow computer without pulling it out of service or waiting for the monthly close. Reconciling the reported volume against the stored integral value and averages, which is exactly the API 21.1 recalculation, becomes a continuous background check rather than a once-a-month forensic task. Making the integral value visible turns the audit trail from a compliance artifact into a live diagnostic that keeps the volume trustworthy day to day.
The integral value, or extension, is the square root of the differential pressure across the orifice multiplied by the static flowing pressure, commonly written as the square root of hw times Pf. The flow computer forms this term each measurement cycle and integrates it over the period, and the accumulated integral value scaled by the averaged coefficients becomes the reported volume. It captures the fast-changing driving force of the flow separately from the slow-changing coefficients.
Because the measurement standard requires that a reported volume be reconstructable from preserved intermediate data, and the accumulated integral value is the core of that record. An auditor recalculates volume by multiplying the stored integral value for an interval by the multiplier from the stored averages, and it must reproduce the reported total within rounding. Storing the integral value per interval also localizes any discrepancy to specific hours rather than leaving only a wrong daily total.
The integral value is the accumulated driving force, so it should move in step with differential and static pressure. Trending the per-interval integral value in a dashboard lets a technician see when it goes flat despite clear flow, or spikes implausibly, which signals a stalled or under-sampled integration. That check is the same reconciliation an auditor performs, but done continuously and remotely, so problems are caught early and traced to a specific flow computer without a site trip.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.