Most people think an electricity bill is about how much energy was used, but for industrial customers a large part of it is about the single hardest moment of the month. A demand meter captures that moment. Rather than totalizing energy, it records the maximum average power drawn over a defined window, and that peak, often called peak demand, sets a significant share of what a large facility pays. This guide explains what a demand meter measures and how it differs from an energy meter, why the recorded peak drives demand charges, and why plants watch demand in SCADA. It has nothing to do with the safety-system demand modes discussed elsewhere; this is electrical utility demand.
Demand Meter in one line: A demand meter is a metering function that records the maximum average power a facility drew over a defined interval during a billing period, rather than the total energy consumed. It works by averaging power across a demand interval, such as a set number of minutes, and remembering the highest such average as the peak demand. That peak matters because utilities levy demand charges on it, so a large facility's bill depends heavily on its single worst interval, not only on how much energy it used. This electrical utility demand is entirely distinct from the demand mode of a safety instrumented system.
A demand meter answers a different question from an energy meter. An energy meter asks how much was used in total and reports an ever-growing kilowatt-hour figure. A demand meter asks how hard the facility pulled at its hardest and reports a peak power figure in kilowatts. Crucially, it does not simply catch the highest instantaneous spike; it captures the highest average power sustained over a defined interval. A very brief surge that lasts a fraction of the interval is diluted by the quieter time around it, whereas a heavy load held across a whole interval registers as high demand. The meter is looking for sustained draw, not momentary flickers.
The mechanism is straightforward once the interval idea is clear. Over each demand interval the meter computes the average power drawn during that window, and it keeps the largest of these averages seen during the billing period in a maximum demand register. As the period progresses, whenever an interval produces a higher average than any before it, the register is updated to that new peak. At the end of the period the register holds the single highest sustained draw the facility reached, which is the number that will be billed.
This is why demand is fundamentally about a moment rather than a total. A facility could use a modest amount of total energy yet still record a high peak demand if, on one occasion, a great deal of equipment ran at once for the length of an interval. Conversely a facility could use a lot of energy spread evenly and record a lower peak. The demand meter isolates the intensity of consumption at its worst, a quantity the total energy figure simply cannot express, and it is that intensity the utility cares about for demand billing.
Utilities charge for demand because the supply system, the wires, transformers, and generation capacity, has to be sized to handle the highest draw a customer makes, not the average. A facility that peaks hard forces the utility to provision for that peak even if it sits quiet the rest of the time, and demand charges recover the cost of that reserved capacity. This is why, for many industrial customers, the demand portion of the bill is large and sometimes rivals or exceeds the energy portion: it is paying for the strain of the worst interval, which is a real cost regardless of total consumption.
The consequence is that a single bad interval can be expensive out of all proportion to the energy it involved. If several large pieces of equipment happen to start together and run for the length of one demand interval, the peak they create can set the demand charge for the entire period, so the facility pays for that intensity long after the moment has passed. Some tariffs even carry the peak forward so that a high demand in one period influences charges in later ones, sharpening the incentive to avoid ever reaching a new peak unnecessarily.
Because of this, managing demand is a distinct discipline from saving energy. Reducing total consumption lowers the energy charge, but flattening the peaks, spreading heavy loads out so they do not all coincide within a single interval, lowers the demand charge, and the two do not automatically go together. A facility can cut its demand bill significantly without using any less energy overall, simply by never letting its coincident load pile up into one worst interval. Understanding what the demand meter records is the first step to controlling that cost.
Plants monitor demand in SCADA precisely because the peak that sets the bill is created in real time and, once an interval closes with a new high, it cannot be undone. A cloud SCADA platform such as Merobix can bring in the demand meter's registers and the underlying power readings, giving operators a live view of how the current interval's average draw is developing rather than discovering the peak only when the invoice arrives. Seeing demand as it builds turns an after-the-fact charge into something the operation can actually influence while there is still time to act.
With that visibility a facility can watch the accumulating average against the peaks it wants to avoid and take action before an interval closes on a new high. If the current interval is trending toward a costly peak, operators can defer or stagger a large load so that everything does not run coincidentally within the same window, keeping the interval's average below the level that would set a new demand charge. This is the operational payoff of monitoring demand: the peak is not fate, it is the result of choices made during the interval, and those choices can be informed by a live SCADA view.
It is worth stressing again that this electrical demand is a completely different concept from the demand terminology used in safety instrumented systems, where demand mode and demand rate describe how often a safety function is called upon to act. The only thing the words share is the term itself. In electrical metering, demand means the peak average power a facility draws, the quantity a demand meter records and a utility bills, and it is that quantity a SCADA system surfaces so a plant can keep its worst interval, and therefore its demand charge, under control.
An energy meter records total energy consumed, reporting an ever-growing kilowatt-hour figure for usage billing. A demand meter records the maximum average power drawn over a defined interval, the peak demand, for demand billing. One captures how much was used in total; the other captures how hard the facility pulled at its hardest. A large facility's bill depends on both, and the demand portion can be substantial.
Because the utility must size its wires, transformers, and generation to handle a customer's highest draw, not its average, and demand charges recover the cost of that reserved capacity. A facility that peaks hard forces provisioning for that peak even if it is quiet the rest of the time. A single interval where many loads run at once can set the demand charge for the whole period, so managing peaks is separate from saving energy.
No, they only share the word. In electrical metering, demand means the peak average power a facility draws over an interval, which a demand meter records and a utility bills. In safety instrumented systems, demand mode and demand rate describe how often a safety function is called on to act. The two concepts are unrelated, and this page concerns electrical utility demand, not safety-system demand.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.