An orifice flow computer derives flow from the square root of differential pressure, and that square root behaves badly near zero. A tiny amount of transmitter noise when the line is barely moving gets amplified into a stream of small phantom flow that accumulates into a real, but false, volume. The low-flow cutoff is the threshold below which the flow computer simply calls the flow zero. This guide explains why the cutoff exists, how the square-root relationship creates the problem, how a cutoff is chosen, and the tradeoff between setting it too high and too low.
Low-Flow Cutoff in one line: A low-flow cutoff is a differential pressure threshold below which a flow computer treats the flow as zero rather than calculating it. It exists because flow is proportional to the square root of differential pressure, so small transmitter noise near zero differential is amplified into phantom flow that would otherwise accumulate into a false volume. The cutoff is set just above the transmitter's noise floor so that genuine low flow is still counted while sensor noise at no-flow conditions is suppressed.
In orifice measurement, flow rate is proportional to the square root of the differential pressure across the plate. The square root function is steepest near zero: a small change in differential produces a disproportionately large change in the square root when the differential is tiny. Far from zero this is unremarkable, but at the bottom of the range it means that even a fraction of a unit of differential pressure translates into a meaningful apparent flow.
Now add the reality that no transmitter reads perfectly still. When the line is not actually flowing, the differential pressure signal hovers around zero with a little noise from the sensor, from vibration, and from small pressure fluctuations in the impulse lines. That noise is symmetric around zero in the raw signal, but the flow calculation takes its square root, and the square root of a small positive number is not small in flow terms. Because the calculation cannot take the root of a negative number, the negative excursions are effectively lost while the positive ones are amplified, so the noise does not average out to zero. Instead it produces a persistent trickle of small positive flow.
That trickle is the phantom flow the cutoff exists to kill. Left alone, it integrates minute after minute into a false accumulated volume on a meter that is genuinely shut in or barely moving. Over a shut-in well or an idle run, a day of amplified noise can register as a non-trivial quantity that never physically flowed, which is exactly the kind of error a custody measurement cannot tolerate.
The cutoff is set as a differential pressure value, and the goal is to place it just above the noise floor of the differential transmitter under real field conditions. Below that value the computer forces the calculated flow to zero and stops accumulating; above it, the calculation proceeds normally. Choosing the value therefore starts with knowing how much the differential signal wanders at genuine no-flow, which depends on the transmitter, the installation, and the environment.
A well-chosen cutoff sits high enough to swallow that no-flow wander but low enough that the smallest flow the meter is genuinely expected to see still exceeds it. On a meter sized appropriately for its flow range, there is usually a comfortable gap between the noise floor and the minimum real flow, and the cutoff is placed inside that gap. Where the gap is narrow, because the meter is oversized for the actual flow, the cutoff becomes a harder compromise and is often a sign the orifice or meter should be resized rather than tuned around.
The cutoff is a documented configuration parameter, not a hidden constant, because it directly affects reported quantities. It belongs in the flow computer's configuration record so that an auditor can see what threshold was in force, and any change to it is an event that should be logged, since raising or lowering the cutoff changes how much volume the meter reports at the low end.
Setting the cutoff too high loses real gas. Any genuine flow whose differential falls below the threshold is counted as zero, so a meter that spends time in low-flow conditions, such as a well late in its decline or a run at the tail of a swing in demand, will under-report. The lost volume is silent: nothing alarms, the total simply comes out low, and the gas that moved is never billed. On a large run the effect may be negligible, but on a low-rate meter a high cutoff can shave off a meaningful fraction of production.
Setting the cutoff too low lets the phantom flow back in. If the threshold sits inside the transmitter's noise band, amplified noise at no-flow accumulates into volume that was never delivered, over-reporting on an idle or shut-in meter. The two failure modes pull in opposite directions, which is why the cutoff is a deliberate compromise placed between the noise floor and the minimum expected flow rather than at either extreme.
A cloud SCADA such as Merobix helps keep that compromise honest by making low-end behavior visible across many meters at once. An operator can spot a run that is accumulating small volume while its differential pressure sits in the noise, suggesting a cutoff set too low, or a shut-in meter that reports flow it should not. Trending differential pressure alongside the accumulated volume lets a measurement technician confirm that the cutoff is doing its job, and surfacing the configured cutoff value from each flow computer means a threshold that was set wrong on one site does not stay hidden until reconciliation.
Because flow is proportional to the square root of differential pressure, and the square root is steepest near zero. At no-flow, small transmitter noise around zero differential gets amplified, and since the calculation cannot use negative values, the positive noise excursions do not cancel out. The result is a persistent small positive flow that accumulates into a false volume unless a cutoff suppresses it.
The meter loses real gas. Any genuine flow whose differential pressure falls below the threshold is counted as zero, so the meter under-reports whenever it operates at low rates. The lost volume is silent because nothing alarms, which makes a cutoff set too high a quiet source of under-measurement on low-rate meters.
They are related but not identical. A deadband generally suppresses small changes around a value, while a low-flow cutoff specifically forces flow to zero below a differential pressure threshold to defeat square-root noise amplification near no-flow. The cutoff is a custody-relevant configuration parameter that should be recorded in the flow computer's configuration log because it directly affects reported quantities.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.