Skip to main content

July 2026 · Energy Management · Updated October 2026

How to Reduce Maximum Demand Charges in a Factory

Reviewed by Ramniwas Gautam, Validation Head, Tech OVN

Maximum demand charges can be a large part of a factory’s monthly electricity bill — and a single 15-minute block of high demand can set the peak for the entire billing period. The good news is that demand charges are among the most controllable cost items on an industrial bill, provided you can see what is driving them. This guide covers the practical measures that reduce demand charges in a factory setting, starting with the most immediate and working toward structural changes. If you first need to understand how the charge itself is computed, start with MD penalty in electricity bill. The prerequisite for all of the measures below is real-time demand monitoring — you cannot cut what you cannot see.

Measure first — the prerequisite every other tactic depends on

Before any demand-reduction measure can be sized, targeted, or verified, you need to know exactly when your peak demand occurs, how high it goes, and which loads are responsible. This sounds obvious, but a surprising number of factories manage demand reactively — they discover the peak on the monthly bill, weeks after it happened, with no information about which equipment caused it or what the trigger was.

Real-time demand monitoring closes this gap. The Titan energy meter (Class 0.5S per IEC 62053-22) computes block and sliding-window demand continuously using the same interval method your DISCOM meter uses. It tracks how much headroom remains before your contract demand limit and sends configurable alerts when demand is on track to exceed that limit before the current interval closes.

That alert — even two or three minutes before the interval ends — gives your operator or energy manager time to defer a compressor start, reduce chiller capacity, or pause a non-critical process. Titan provides the monitoring and the advance warning; the load curtailment itself is an operator or EMS/PLC action. With sub-metering at the feeder level, you can also see which loads are active during each peak interval — the foundation for every targeted intervention that follows.

Stop large loads running at full power together

Maximum demand is the average load over a 15-minute (or 30-minute) block, so it is set by what runs together for most of that block — not by momentary spikes. A large motor started across the line draws several times its running current, but only for a few seconds; spread over a 15-minute average, that inrush adds very little. The peaks that set the month’s maximum demand come from overlapping running loads: the compressor room, chiller plant, furnaces and production lines all at full load in the same block.

The fix is a documented operating sequence. At shift start — a common trigger — bring the compressor room, chiller plant and production lines up in stages so that the period when everything is running at once (often while the plant is pulling down temperature or pressure) is as short as possible. During the shift, avoid running intermittent heavy loads — batch furnaces, large presses, a second compressor — in the same periods as the main production peak.

This needs little or no capital and can start as a written SOP. Its effectiveness is easy to verify from demand monitoring data: compare peak demand before and after the staggered startup protocol is introduced.

Soft-starters and VFDs: what they do and don’t do

A soft-starter or variable frequency drive (VFD) limits inrush current at startup, so the motor ramps up instead of drawing several times rated current for a few seconds. That reduces voltage dips and mechanical stress on couplings and driven equipment — but because inrush contributes so little to a 15-minute average, a soft-starter on its own does not meaningfully cut a maximum demand charge.

A VFD is different where the load itself varies. On cooling fans, pumps on variable-flow systems and similar loads, running the motor slower when full output is not needed reduces the running power drawn — and lower running power during peak periods is what lowers maximum demand. Whether that is worth doing depends on your load profile, so size it from measured data.

Prioritise variable-load motors that run during peak demand periods, are large relative to your contract demand, or show up in your metering data as contributors to peak intervals.

Shift flexible loads away from peak intervals

Not all factory loads need to run at the same time as production. Identify loads that are flexible in their timing — batch processes, tanks filling, compressed-air vessels charging, material drying, water treatment, building HVAC pre-cooling — and schedule them to run during off-peak hours or during intervals when core production demand is lower.

This is particularly effective when combined with time-of-day (ToD) tariff awareness: shifting flexible load away from both the peak demand window and the peak tariff window reduces the bill on two dimensions simultaneously (see how ToD tariffs work in India). A flatter demand profile also raises your load factor, which some DISCOMs reward with a load factor incentive. The energy monitoring platform shows how load is distributed across the day at interval-level granularity — the starting point for identifying which loads can be shifted and by how much.

Common candidates in factory environments include: compressed air top-up cycles, water treatment plant runs, effluent treatment processes, warehouse lighting during non-picking hours, and HVAC pre-cooling in the early morning before the tariff peak window opens.

Use predictive demand alerts — the real-time safety net

Even with staggered startups and load-shift schedules in place, demand spikes can still occur from unplanned events — an unscheduled batch run, an equipment failure that forces a restart sequence, or HVAC and production loads coinciding during an unusually hot afternoon. Predictive demand alerting provides a real-time safety net.

Titan tracks accumulated demand within the current billing interval and projects the end-of-interval value. When the projection crosses a configurable threshold — for example, 88% of contract demand — it sends an alert to the energy manager’s phone or a display in the control room. The alert arrives while there are still several minutes left in the interval: enough time for an operator to hold off a non-urgent load, reduce chiller output, or call the production manager to pause a batch.

This real-time layer is the difference between managing demand proactively and discovering the penalty on the bill. It is also the enabler that makes it practical to set contract demand closer to actual operating demand — the tighter the safety margin, the more important the alert.

Consider DG or BESS for peak clipping

Where demand spikes are frequent, predictable, and cannot be eliminated by operational changes alone, a behind-the-meter diesel generator (DG) or battery energy storage system (BESS) can clip peaks by supplying part of the load locally during the spike interval, reducing the demand seen by the utility meter.

The economics depend on the cost of DG running hours or battery capex versus the demand charge saving, which in turn depends on how often peaks occur, how far they exceed the contract demand limit, and your state tariff’s specific demand charge rate. These numbers are only available from detailed demand monitoring data — another reason measurement must come first.

DG peak clipping is a well-established practice in Indian industry, particularly at sites with existing standby DGs that are already available and permitted. BESS peak clipping is increasingly viable as battery costs fall, and avoids the emissions and fuel cost of DG operation. In either case, the DG or battery controller needs a reliable demand signal to know when to dispatch. Titan supplies the measurement and alerts; the dispatch logic sits in the DG/BESS controller or your EMS/PLC.

Right-size contract demand — both ways

Contract demand is not a set-and-forget figure. It should be reviewed periodically against actual operating patterns and revised when there is a sustained mismatch — in either direction.

If maximum demand consistently stays well below contract demand, the facility may be paying minimum demand charges on capacity it never uses. Reducing contract demand through a formal DISCOM application lowers the minimum billing floor. The risk is that if operating demand later increases — a new production line, a capacity expansion — you may face exceedances again. Use at least six to twelve months of demand data before applying for a downward revision, and factor in seasonal variation and planned expansions.

If maximum demand regularly approaches or crosses contract demand, and operational measures cannot reliably keep it under the limit, a formal upward revision may be more cost-effective than paying repeated exceedance penalties. Compare the extra demand charge on the higher contract demand against the excess-demand penalties you have actually been paying to decide.

DISCOM procedures for demand revision, any restrictions on revision frequency, and applicable fees vary by state. Keep power factor in view too: where demand is billed in kVA, poor PF raises kVA demand for the same kW (see power factor penalties). The demand monitoring data from Titan gives you the historical evidence base to make either case objectively.

Frequently Asked Questions

Common questions about cutting maximum demand charges in Indian factories.

The fastest single intervention is usually scheduling large loads so they do not run at full power at the same time — for example, bringing the compressor room, chiller plant and production lines up in sequence rather than together, and keeping flexible loads out of known peak periods. This needs a documented operating sequence rather than capital. The second is real-time demand monitoring with pre-crossing alerts, so your team gets a warning while there is still time in the current interval to defer a flexible load. Structural changes like load shifting, peak clipping or demand revision take more planning.
No. Titan is a monitoring and measurement device. It computes real-time demand using the same block or sliding-window method your DISCOM uses, tracks headroom against your contract demand limit, and sends configurable alerts when demand is trending toward a breach. The load curtailment action — deferring a compressor start, reducing chiller capacity, pausing a batch process — is taken by your operator, energy manager, or connected EMS/BMS/PLC. Titan provides the visibility and advance warning that makes that action timely.
That depends entirely on your tariff and how far your current contract demand is from your actual operating pattern. If your maximum demand consistently runs well below your contracted figure, you may be paying minimum demand charges on capacity you never use. Reducing contract demand lowers that floor. Conversely, if you are regularly exceeding contract demand and paying penalties, you may be better off revising demand upward and managing loads to stay under the new limit. Review at least six to twelve months of demand data before applying for a revision; DISCOM procedures and any restrictions on revision frequency vary by state.
Load staggering means scheduling large electrical loads so they do not all run at full power through the same 15- or 30-minute billing interval. Maximum demand is an average over the interval, so it is set by the loads that are running together for most of it — compressors, chillers, furnaces, presses and HVAC all at full load at once. A motor's starting inrush lasts only seconds and adds very little to a 15-minute average; what matters is the sustained running load that overlaps. Staggering means sequencing and interlocking equipment so peaks do not coincide, and keeping flexible loads out of the busiest periods.
Yes — behind-the-meter DG or battery energy storage can reduce grid-drawn demand during peak intervals by supplying part of the load locally. The economics depend on the cost of DG running hours or battery capex versus the demand charge saving, which in turn depends on your tariff and how frequently you exceed the limit. Monitoring is a prerequisite: you need to know exactly when and by how much demand peaks are occurring before you can size a peak-clipping resource correctly.
Sub-metering at the feeder or equipment level is the answer. A main incomer meter tells you total demand; feeder-level meters tell you which loads are active during peak intervals. With per-feeder data you can identify whether the peak is driven by HVAC, a particular production line, utility loads, or a combination — and target the staggering or deferral accordingly. Titan supports multi-meter deployments that aggregate feeder data into a single demand view.

Cut demand charges with real-time headroom visibility

Titan tracks live demand against your contract limit, alerts before a breach, and attributes peaks to individual feeders — so you can act, not react.