kW and kWh look almost identical and are constantly swapped by mistake, yet they measure genuinely different things, and confusing them leads straight to misread bills and misconfigured tags. A kilowatt is a rate, how fast energy is being used at this instant, while a kilowatt-hour is a quantity, how much energy has been used over a stretch of time. The cleanest analogy is flow: kW is like the flow rate through a pipe and kWh is like the total volume that has passed. This guide separates the two clearly, shows how a meter derives one from the other, and explains why a SCADA historian handles the two kinds of tag differently.
kW vs kWh in one line: kW, the kilowatt, is a unit of power, the instantaneous rate at which electrical energy is being used at a given moment. kWh, the kilowatt-hour, is a unit of energy, the total amount used accumulated over time, obtained by integrating power over the hours it flows. The relationship is exactly that of flow rate to totalized volume: kW is how hard energy is flowing right now, and kWh is how much has flowed in total. One drives demand charges based on peak rate, while the other drives usage charges based on total consumption.
The distinction between kW and kWh is the distinction between a rate and a quantity, and the flow analogy makes it intuitive. Imagine water moving through a pipe. The flow rate, how many litres per second are passing at this instant, is analogous to kW: it describes how hard the water is flowing right now and can rise and fall from moment to moment. The totalized volume, how many litres have passed in total, is analogous to kWh: it only ever accumulates, and it captures the whole amount that has gone through regardless of how the rate varied along the way.
Carry that back to electricity and the picture is the same. A kilowatt tells you the rate at which energy is being drawn at this moment: a heavier load draws more kilowatts, a lighter load fewer, and the figure changes continuously as equipment starts and stops. A kilowatt-hour tells you how much energy has actually been consumed over some period, the accumulated result of that changing rate acting over time. A device drawing a steady one kilowatt for one hour consumes one kilowatt-hour; the same device drawing two kilowatts for half an hour also consumes one kilowatt-hour, because the total energy is the rate combined with the time.
This is why the two can never be substituted for each other. Saying a facility uses a certain number of kilowatts describes a moment, an instantaneous demand, while saying it uses a certain number of kilowatt-hours describes an accumulation over a period. Asking how many kilowatts were used in a month is as ill-formed as asking how many litres per second flowed in total; the month calls for an energy figure in kilowatt-hours, and the instantaneous draw calls for a power figure in kilowatts. Keeping rate and quantity straight is the whole of understanding these units.
A meter derives energy from power by integrating over time. At every instant the meter knows the power being drawn, the kilowatts, and energy is simply that power accumulated across the hours it flows. In effect the meter continuously adds up power multiplied by the small slices of time that pass, so that the kilowatt-hour register climbs steadily whenever any load is present and climbs faster when the load is heavier. This is the same operation as a flow totalizer summing flow rate over time to produce total volume; energy is the time integral of power, exactly as volume is the time integral of flow.
Because kWh is an accumulation, its register only goes up; it never falls back on its own. This is why energy is read as a running total and why consumption over a period is found by subtracting the register reading at the start from the reading at the end. Power, by contrast, is read as a live value that rises and falls with the load and has no memory of the past. The meter holds both: a present-rate figure in kilowatts that reflects the moment, and an ever-increasing total in kilowatt-hours that reflects everything consumed since the register began.
The billing consequence follows directly from this pair. The accumulated kilowatt-hours drive usage charges, the part of the bill that pays for the total energy delivered, because that is literally the quantity consumed. The instantaneous power, in the form of peak demand measured over defined intervals, drives demand charges, which reflect the strain the highest draw places on the supply system rather than the total amount used. A facility that uses the same energy but in sharper peaks pays the same usage but more demand, precisely because the two units capture different aspects of how it consumes.
In SCADA the difference between rate and quantity shapes how each value is stored, and a cloud SCADA platform such as Merobix treats the two kinds of tag differently for good reason. An instantaneous power tag in kilowatts is a live analog value that goes up and down, so it is sampled at intervals to capture how the load moves, and its history is a trace of the rate over time from which peaks, averages, and trends can be read. Nothing is lost if a sample lands between changes, because the tag simply reflects the current rate whenever it is read.
A totalizer tag in kilowatt-hours is stored with different care, because it is a monotonically increasing counter rather than a fluctuating measurement. Consumption over any interval is derived by differencing the totalizer across that interval, so the historian must preserve the running total faithfully rather than treating it like an ordinary analog point. It also has to handle rollover, the moment a counter reaches its maximum and wraps back to zero, so that the wrap is recognised as the meter continuing to count upward and is not mistaken for a sudden drop in consumption. Handling rollover correctly is essential to getting accurate energy totals from a totalizer.
Keeping the two tag types distinct lets an operation answer both kinds of question from its historian. The power tags reveal how hard equipment is drawing at any moment and expose the peaks that matter for demand, while the energy totalizers reveal how much has been consumed over any chosen span for usage accounting and cost allocation. Confusing the two, sampling a totalizer as if it were a live rate or totalizing a rate as if it were a counter, produces meaningless numbers, so a well-built SCADA system stores instantaneous kilowatts and accumulated kilowatt-hours as the different quantities they genuinely are.
No. A kilowatt (kW) is a unit of power, the instantaneous rate at which energy is used, while a kilowatt-hour (kWh) is a unit of energy, the total amount used over time. The relationship is like flow rate versus total volume: kW is how hard energy is flowing right now, and kWh is how much has flowed in total. A device drawing one kilowatt for one hour consumes one kilowatt-hour.
It integrates power over time. At every instant the meter knows the power being drawn in kilowatts, and it continuously accumulates that power across the slices of time that pass, so the kilowatt-hour register climbs whenever a load is present and climbs faster under heavier load. This is the same operation as a flow totalizer summing flow rate to produce total volume; energy is simply power accumulated over the hours it flows.
Because they drive different charges. Accumulated kilowatt-hours drive usage charges for the total energy consumed, since that is literally the quantity delivered. Peak power in kilowatts, measured over defined demand intervals, drives demand charges that reflect the strain the highest draw places on the supply, not the total used. Two facilities can consume the same energy yet pay different demand charges if one draws it in sharper peaks.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.