How a BMS Guards Your Electricity Bill: Load Shedding and Demand Limiting

Two numbers on the same bill

Imagine two cars that both travel exactly 100 kilometres in a day. One cruises the whole way at a steady, gentle pace. The other crawls, then floors the accelerator, then crawls again. They cover the same distance — but the second car needs a far bigger engine to survive those violent bursts, and it punishes the fuel gauge every time the driver stamps down.

Your electricity bill works in a strikingly similar way. It is not one number. It is two separate charges, and they measure two different things.

- Energy — measured in kilowatt-hours (kWh) — is how much electricity you used over the month. This is the distance travelled.
- Demand — measured in kilowatts (kW) — is how fast you were drawing power at your single busiest moment. This is how hard you floored the accelerator.

We unpacked this distinction in the Electricity Fundamentals course — if the split still feels fuzzy, power vs energy: kW and kWh explained is the anchor. The short version: two buildings can burn identical kWh in a month yet be billed very differently, because one of them spiked hard for fifteen minutes and the other stayed smooth.

This part is about that spike — and how a building automation system (BMS) helps you keep it in check.

Why the peak costs you money

The demand charge exists because the utility has to build for your worst moment, not your average one. Every cable, transformer and generator upstream of your building has to be sized to survive the instant you draw the most power. You reserve that capacity whether you use it for fifteen minutes or fifteen hours — so you pay for it.

Under Malaysia's TNB RP4 tariff structure, demand is billed at roughly RM89.27 to RM97.06 per kW (Capacity plus Network components), effective 1 July 2025. Read that carefully: it is per kW, charged every month, based on your highest sustained demand in that month.

So if your building peaks at 500 kW one afternoon — even briefly — you carry roughly 500 × RM90-odd ringgit on the demand line of that bill. Trim that peak to 450 kW and you have saved around RM4,500 that month, and again the next, and the next. The kWh you burn barely changed. You simply stopped stamping on the accelerator.

That is why peak kW is worth chasing. But there is an honest caveat that matters for this course, because our readers run buildings of very different sizes.

The caveat: it depends on your tariff

Per-kW demand charging applies to maximum-demand (demand-metered) tariffs — the case for most medium and large commercial and industrial sites, typically supplied at medium voltage. If your building is on one of these tariffs, every kW of peak you shave is real money, every month.

Smaller buildings on a plain low-voltage energy tariff may have no per-kW demand charge at all — they pay only for kWh. For them, the lever that matters is total energy, not peak demand, and much of this part is informational rather than a bill you can cut. Before investing in demand-limiting logic, the first question is always: am I actually billed for peak kW? You can get a feel for what your own peak is doing with our maximum-demand calculator.

Everything below assumes you are on a demand-metered tariff.

How a BMS watches demand

A BMS with demand-management enabled does something a human watching a meter never could: it tracks your power draw continuously and does arithmetic on it in real time.

Utilities don't bill on the instantaneous spike of a single second — they bill on demand intervals, a rolling window (often around 15 or 30 minutes) over which power is averaged. This is good news, because it means a brief surge that is quickly pulled back may never register as a new peak at all. The BMS's job is to make sure the average over each interval never climbs past the ceiling you set.

Picture it as a running total inside a fixed time window. As the window fills up with power draw, the BMS forecasts where the average is heading. If the trend line is about to break through your target, it acts — early, before the peak is set, not after. Chasing a peak after it has been recorded is pointless: once that interval closes with a record high, you are billed for it whether you react in the next second or not.

Demand limiting: trimming before the peak is set

Demand limiting is the headline strategy. You (or your facilities team) set a target ceiling in kW. The BMS watches the forecast demand for the current interval, and when it sees the building about to exceed that ceiling, it sheds or defers non-critical loads to stay under the line.

The art is entirely in the phrase "non-critical." A well-configured system carries a priority list — a ranking of which loads it is allowed to touch, and in what order. At the bottom of the list sit loads nobody will notice going quiet for a few minutes: a car-park exhaust fan, a decorative fountain pump, a bank of water heaters, one zone's cooling nudged very slightly. At the top sit loads it must never touch: life-safety systems, lifts, critical process equipment, the server room.

When demand rises toward the ceiling, the BMS walks up the priority list, easing off the least-important loads first, and only reaching for more important ones if the pressure keeps building. The moment the interval resets and headroom returns, it restores everything in reverse order.

Load shedding and duty cycling: flattening without anyone noticing

The best demand management is invisible to the people inside the building. Two techniques make that possible.

Load shedding is the direct move: temporarily switch a load off, or ease its setpoint, to drop power draw. In a tropical building the biggest, most flexible electrical loads are almost always in the cooling plant — chillers, pumps and air-handling fans. A brief, small relaxation of a cooling setpoint — letting a zone drift up by half a degree for a few minutes during a demand peak — sheds real kW while the space stays comfortable. Thermal mass is your ally here: a large air-conditioned space holds its temperature for a while, so a short trim rides through unnoticed. (This is a light, deliberate touch — nothing like the setpoint drift up when a space is empty that we covered under unoccupied setback in an earlier part.)

Duty cycling rotates loads instead of cutting them outright. If you have several similar pieces of equipment — say four cooling-tower fans or a bank of small units — the BMS can cycle them: a few minutes on, a few minutes off, in a rotating pattern, so that they are never all drawing power at the same instant. The total cooling delivered stays roughly the same; the simultaneous peak comes down because the machines take turns. Rotating which unit rests also evens out wear across the fleet — a quiet maintenance bonus.

Neither technique reduces how much work the building does. They reshape when that work draws power — pushing the jagged peaks down into the valleys, so the demand curve rides flatter.

The connection back to scheduling: staggered start-up

There is one demand-management tool you have already met, even if it wasn't labelled that way. In the scheduling part earlier in this course, we talked about staggered start-up — bringing chillers and large motors online one at a time instead of all at once.

That is demand limiting in its purest form. A large chiller compressor pulls a heavy surge of current the instant it starts. Simultaneous start-up of several chillers or compressors is one of the most common causes of an avoidable demand peak — the whole plant lunges for power in the same few seconds at, say, 8 a.m., and that synchronized lunge can set the month's billing peak before the building is even properly occupied.

Staggering the starts — first chiller, wait, second chiller, wait, third — spreads that surge across several minutes. The building reaches the same steady-state cooling; it just never all grabs for power at once. (These large centrifugal compressors, incidentally, are often driven by medium-voltage three-phase motors and started through a variable-speed drive rather than thrown straight onto the line — the soft-start behaviour we explored via power electronics: rectifiers and inverters and how electric motors work. A soft ramp is gentler on demand than a hard across-the-line start.)

So scheduling and demand limiting are two views of the same discipline: control when things happen so the peak never towers.

The honest limit: a BMS shows and executes — it doesn't decide for you

Here is the part that keeps this course honest, and it matters.

A BMS does not, by itself, lower your bill. It has no opinion about your tariff and no magic that makes kilowatts cheaper. What it actually does is two concrete things:

1. It reports — it makes your demand visible, interval by interval, so you can finally see where your peak comes from instead of guessing.
2. It executes — it carries out, tirelessly and on time, whatever limiting strategy you configure.

The intelligence still lives in the strategy: which loads are sheddable, what ceiling to hold, how far to let a setpoint drift, when comfort must win over savings. Set the ceiling too low and you starve the building of cooling; set it too high and you save nothing. The BMS is the hand on the levers — a very fast, very reliable hand — but you decide where the levers should sit. It shows you where to act, and then acts exactly as told. That is the whole, honest deal.

Grounding it in ringgit

Let's close the loop on the money, because this is where control meets the tariff and the numbers get real.

If you are on a demand-metered RP4 tariff at roughly RM90 per kW per month, then:

- Shaving a 20 kW avoidable start-up spike is worth about RM1,800 every month — over RM21,000 a year — for control logic that already exists in the BMS you own.
- That saving stacks on top of any kWh you save by running plant more efficiently. Demand and energy are separate charges, remember — trimming the peak and trimming the total are two different wins on two different lines of the same bill.

None of this requires new hardware. It requires knowing your peak, setting a sensible ceiling, and letting the system hold it.

And knowing your peak is exactly where measurement earns its place: turning one lump-sum utility bill into a breakdown that shows where the peak actually comes from is a monitoring job, and it's precisely what an independent energy-monitoring layer like CobiNeural is built to surface — so you can point your BMS's demand logic at the loads that are genuinely setting your bill.

The takeaway

Your electricity bill charges you twice: for how much you use (kWh) and — if you are on a demand-metered tariff — for how hard you peaked (kW). A BMS can't make electricity cheaper, but it can watch your rising demand and quietly trim, defer or rotate non-critical loads before a new peak is set, using demand limiting, load shedding, duty cycling and staggered start-up. Under RP4's roughly RM90-per-kW charge, every peak kW you keep off the meter is real money back every month — provided you tell the system where to act and where to hold the line.

Next, we look at the human side of all this control: alarms, dashboards and the graphical screens that let an operator actually see and command the building — the part where the BMS finally shows its face.