Reduce demand charges by controlling peaks, smoothing loads, and shifting flexible usage (beginner-friendly, not engineering advice)
Important: This is operational guidance, not engineering advice. Work with qualified professionals for controls changes and safety-critical systems.
Use this when:
For one site:
kWh = how much electricity you used over time
kW = how fast you used it at a moment (power draw)
Demand charges often bill you based on your highest measured kW during a window.
Beginner rule: You can lower demand charges without lowering total kWh by reducing peak spikes.
If demand charges are small, focus elsewhere. If demand charges are large or rising, proceed.
You don't need years of data. A few months is enough to find peak patterns.
Common peak drivers:
Examples:
Examples:
Examples:
You need:
| Site | Month | Total $ | Demand charges $ | Demand share % | Peak kW (if shown) | Notes | |---|---|---:|---:|---:|---:|---|
Subject: Request: interval electricity usage data — Account [#] Hello, Please provide interval electricity data for account [#] for the period [start–end], including: - interval length (15-min/hourly) - timestamps - kW or kWh per interval CSV export preferred. Thanks, [Name]
| Site | Peak date | Peak time window | Peak kW | Suspected driver | Evidence link | Notes | |---|---|---|---:|---|---|---|
Low/no-cost tactics: - Stagger equipment start times - Adjust warm-up/cool-down sequences - Schedule enforcement (turn off unused loads) - Shift flexible loads off-peak - EV charging caps in peak windows Medium-cost: - Demand limiting controls - BAS sequence updates - Setpoint optimization with constraints Hardware: - Battery storage (peak shaving) - Equipment upgrades (motors, VFDs) - Onsite generation (site dependent)
Peak Target Plan Site: Current observed peak (kW): Target peak (kW): Why this target is feasible: Tactics to implement: Implementation date: Owner: Measurement method:
Peak Demand M&V Summary Site: Baseline period: Post period: Changes made: Result: - peak kW change: - demand charges change: Confidence (High/Med/Low) and why:
v1.0 (2026-01): Latest release