Every producing asset has a production number it could have hit and a number it actually hit, and the space between them is where a great deal of quietly lost value lives. Deferment tracking is the practice of measuring that gap, attributing it to specific causes, and reporting it, so that lost barrels and lost mcf are managed with the same rigor as the barrels that were sold. This guide defines production deferment, explains how the loss is broken down by cause, and shows how SCADA downtime and well-potential data feed automated deferment reports.
Deferment Tracking in one line: Deferment tracking is the accounting of lost production, the gap between an asset's potential production and its actual production over a period. Potential is what the well, facility, or field would have produced running normally, and deferment is the shortfall caused by downtime, restrictions, or constraints. The practice attributes those lost volumes to specific causes, such as equipment failure, well problems, facility limits, or market and export constraints, so operators can see where production is being lost and prioritize the fixes that recover the most volume.
Deferment is defined as potential production minus actual production. Actual production is straightforward: it is what was measured and allocated. Potential is the harder and more important half, because it is an estimate of what the asset would have produced had it run normally, without the downtime or constraints that reduced it. Setting a credible potential is the foundation of the whole exercise, since deferment is only as meaningful as the baseline it is measured against.
Potential is usually built from a well's expected rate, drawn from its latest well test or a decline model, extended over the time in the period, so a well capable of 100 barrels a day has a potential of 3,000 barrels over a 30-day month. If it actually produced 2,400, the deferment is 600 barrels, a fifth of its capacity lost. The same logic aggregates upward: a facility's potential is the sum of its wells' potentials, and its deferment is the sum of the losses, though facility-level constraints can defer production even when no single well failed.
The value of framing it this way is that deferment converts scattered downtime into a single comparable currency, lost volume. An hour of downtime on a high-rate well costs far more than an hour on a marginal one, and a rate restriction that never fully stops a well can defer more than a short complete outage. Expressing everything as deferred barrels or mcf lets an operator compare and rank losses that would otherwise look incommensurable, which is exactly what makes deferment actionable rather than merely descriptive.
Knowing the total deferment is useful, but knowing why it happened is what drives improvement, so deferment tracking attributes each slice of lost volume to a cause. Common cause categories separate losses by where the problem lay: equipment or facility failures such as a downed compressor or a failed pump, well problems such as a workover or a pump-off condition, planned activities such as maintenance or well tests, and external constraints such as a full sales line, a shut-in export route, or market limits. Each deferred barrel is tagged to one of these so the total can be broken down.
That breakdown reveals patterns a single deferment number hides. A field losing most of its volume to compressor trips has a very different problem, and a very different fix, from one losing it to a constrained export line or to slow well restarts after power dips. Attribution also distinguishes losses the operator can act on, like chronic equipment failures, from those largely outside its control, like a market or third-party pipeline constraint, so improvement effort is aimed where it can actually recover volume.
For attribution to be trustworthy, the cause categories have to be applied consistently and every material loss has to be captured, not just the dramatic outages. Slow, partial losses, a well choked back, a facility running below capacity, often add up to more than the headline failures but are the easiest to miss because nothing ever fully stopped. A disciplined deferment process therefore captures both complete outages and rate restrictions, and assigns each to a cause, so the resulting picture reflects where production is really being lost.
Deferment tracking done by hand is laborious and tends to capture only the obvious outages, which is why it benefits so much from automation off live field data. A cloud SCADA such as Merobix provides both halves of the deferment calculation: the actual production from allocated volumes and metering, and the raw material for potential and downtime from continuously historized well status, rates, and runtimes read over Modbus, DNP3, OPC UA, or MQTT. Continuous state capture in particular means every stop, however brief, is recorded rather than depending on someone to notice and log it.
With well potential expressed as an expected rate and actual runtime known from state history, the platform can compute deferred volume automatically as the potential over the downtime, and do it for every well without manual tallying. Because the downtime events are time-stamped, they can be tied to cause codes, either entered by operators or inferred from the pattern, so the deferment is not just quantified but attributed, turning a stream of status changes into a categorized loss report.
The payoff is a deferment report that is current, complete, and consistent across a large asset base, rather than a partial monthly reconstruction. An operator can see today's lost volume by well and by cause, rank the biggest recoverable losses, and confirm whether a fix actually restored the rate, all from the same live data used to run the field. Capturing the small, partial losses that manual tracking misses is often where the automation pays back most, because those quiet restrictions frequently account for more deferred production than the few outages everyone already knew about.
Production deferment is lost production, defined as the gap between an asset's potential production and its actual production over a period. Potential is what the well or facility would have produced running normally, and deferment is the shortfall caused by downtime, restrictions, or constraints. Tracking it lets operators see how much production is being lost, not just how much was sold, and manage the losses accordingly.
Each slice of lost volume is tagged to a cause category that reflects where the problem lay, such as equipment or facility failure, well problems, planned maintenance, or external constraints like a full sales line. This breakdown shows whether losses come mostly from equipment, wells, the facility, or the market, and separates losses the operator can act on from those outside its control. Consistent categorization and capturing partial rate restrictions, not just full outages, are what make the attribution reliable.
SCADA supplies both inputs to the deferment calculation: actual production from allocated volumes and metering, and the downtime and runtime needed to compute lost volume against a well's potential. Because a cloud SCADA continuously historizes well status and rates, every stop is recorded automatically, including brief and partial ones that manual tracking often misses. Time-stamped downtime events can then be tied to cause codes, so deferment reports are computed and attributed automatically rather than reconstructed by hand.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.