Turning Demand Charges Into a New Revenue Line Across a Mid-Atlantic Portfolio
A developer-operator of mixed-use and light-industrial properties in the mid-Atlantic ran roughly a dozen sites with a familiar problem hiding in plain sight. Demand charges were climbing year over year, and nobody in the organization could say exactly when or where the portfolio was setting its peaks. The utility bills arrived, the numbers looked high, and the response was mostly a shrug. This is how that changed once the operator put interval metering and coordinated demand programs to work through EnergyOS.
The short version: peak alerts trimmed demand charges, an enrolled demand response program opened a new revenue line, and a weather-normalized baseline protected the payout, giving asset managers a cleaner NOI story to bring to investors.
The operator and the NOI pressure
The portfolio was a mix. Some buildings leaned commercial with tenants and shared systems. Others were light-industrial with equipment that pulled hard at unpredictable moments. Across all of them, the operator carried the utility cost, and a meaningful share landed straight against net operating income.
Demand charges were the part that stung. Unlike energy charges, which track how much electricity a building uses over a month, demand charges are set by the single highest interval of load. One coincidence of equipment running at once, and the site locked in a higher charge for the whole billing period. Leadership understood the concept but had no way to see it happening. By the time the bill explained the damage, the peak was weeks in the past.
The challenge
Leadership had heard the pitch on demand response before. Grid operators pay buildings to reduce load during tight periods, and in the mid-Atlantic that means PJM, the regional operator that runs capacity and demand-response programs. The revenue was real, but two worries kept the idea shelved.
The first was operational disruption. Nobody wanted to interrupt tenants or idle production equipment for a program that might net a modest check. The second was the baseline. Demand response pays you for the load you avoid, and that avoidance is measured against a baseline, an estimate of what the site would have used if nothing had changed. Get the baseline wrong and the payout gets shaky. Leadership had heard stories of thin or disputed baselines and did not want to build a revenue line on sand.
Underneath both worries sat the same gap. There was no portfolio visibility into peaks, no shared view of which sites were good candidates, and no system to run any of it without adding headcount.
Demand-charge trimming first
EnergyOS started with metering. Each site was brought to interval-level visibility so load could be seen as it happened rather than reconstructed from a monthly statement. That alone changed the conversation, because for the first time the operator could watch a peak form.
From there the team set demand limits and peak alerts. When a site began trending toward a new monthly peak, EnergyOS fired an alert before the peak was set, with escalation so the right person saw it in time to act. Facility staff could shed a noncritical load, stagger a startup, or hold off on a piece of equipment for a few minutes. Small moves at the right moment kept sites from locking in higher charges.
This piece mattered on its own. Demand-charge reduction is cost avoidance, and it showed up whether or not a site ever enrolled in a paid program. It also built trust, because staff got comfortable making small adjustments, which took the fear out of the bigger conversation.
Demand response as revenue
With peaks under watch and staff used to acting on alerts, the operator enrolled suitable sites in a demand response program. Not every building was a fit. The ones with flexible load and cooperative operations made the best candidates, and the portfolio view made it straightforward to pick them.
EnergyOS handled the program mechanics. It forecast events so the team had lead time instead of a scramble, coordinated curtailment across enrolled sites when an event was called, and tracked performance as it happened. During a PJM event, the platform showed how much each site was reducing against its target in near real time, so the operator could see whether the portfolio was delivering or needed a nudge.
The payment structure rewarded this. Sites earn for capacity and availability, essentially being ready and committed, plus performance for the load they actually drop during events. The availability piece created a steady revenue line, and the performance piece rewarded the coordinated curtailment EnergyOS made possible.
Verification and the baseline
The baseline worry got answered directly, and this is the part leadership cared about most. EnergyOS measured curtailment against a weather-normalized baseline, which accounts for the fact that a hot day and a mild day are not the same starting point. A baseline that ignores weather can understate what a site would have used and quietly shrink the payment. Normalizing for weather produces a defensible number.
After each event, the platform tracked event performance and rolled results into DR revenue accounting, so the operator could reconcile what the program paid against what the sites delivered. Season summaries pulled it together at the end of a program period. Instead of taking a check on faith, the operator had a documented, verifiable record of performance behind every dollar. That verification protected the payout and, just as important, gave finance something they could stand behind.
The portfolio and investor view
All of it fed a portfolio dashboard built for asset managers rather than engineers. Submetering and rollups meant results could be seen site by site or across the whole portfolio, with benchmarking to show which properties led and which lagged. Where tenant submetering was in place, the operator could separate tenant load from base building load cleanly.
For the people who report to investors, this closed the loop. Demand-charge savings and demand response revenue both landed in a view that connected energy performance to NOI. The story stopped being anecdotal and became something an asset manager could put in front of ownership with numbers behind it.
The results
Directionally, and framed as typical for a portfolio of this shape, the operator saw demand charges come down through peak alerts and disciplined load management. Enrolled sites opened a demand response revenue line that had not existed before, combining availability payments with performance earnings. Verified event performance, measured against a weather-normalized baseline, protected those payments from dispute. And the portfolio view gave asset managers a clearer NOI story to carry to investors. The exact figures depend on rates, program terms, and how flexible each site's load turns out to be, which is why the operator now measures rather than guesses.
Closing
The change here was not heroic. It was visibility, a few well-timed alerts, a program run with discipline, and a baseline that held up. Put together, those pieces turned a line-item cost into a managed asset, and in some months a revenue source.
If you operate a portfolio and suspect your demand charges are higher than they need to be, there is a straightforward way to find out. Book a platform walkthrough and see how EnergyOS maps to your sites. Call 215-645-7141.