How to Size a Demand Response Management System: Three Scenarios, Three Different Answers

I've been specifying energy monitoring and demand response hardware for industrial facilities since 2016. In that time I've personally signed off on six purchases that turned out wrong — roughly $41,000 of budget that either produced data nobody used or, worse, data that was quietly wrong. The checklists I keep today came out of those mistakes, not out of a vendor brochure.

So when someone asks me how to size a demand response management system, I'll tell you up front: there isn't one formula. Anyone who hands you a single "kW → equipment tier" table is either selling that tier or hasn't done this long enough to have been burned. What actually determines your sizing is which of three situations you're in. I'll go through each one, then give you the questions that tell you where you sit.

Why the standard sizing tables keep failing

The "DR is only for big plants" thinking comes from an era when participation required a dedicated curtailment service provider, a 1 MW floor, and about a year of paperwork. That's changed. FERC Order 2222, issued in September 2020, requires wholesale markets to accept aggregated demand response resources, and aggregators now routinely enroll portfolios well below the old floor.

There's a second problem, and it's a causation one. People think sizing means choosing a meter count. Actually, you're choosing how much of your load you're willing to prove is curtailable in a way a program administrator will accept — and the meter count follows from that. The hardware is downstream of the calculation, not the other way around. Get the order backwards and you end up with a beautifully specified monitoring stack reporting against a baseline nobody trusts.

Simple version: sizing is three separate decisions pretending to be one.

  • Telemetry scope — how many points, at what interval, at what accuracy class
  • Platform scope — what the energy management system has to compute, store, and export
  • Curtailment scope — how many kW you can actually drop, for how long, without breaking a process

Most people start at the first item. Start at the third.

Scenario A: One site, one program, under about 500 kW of flexible load

This is a mid-size plant, a cold storage warehouse, a food processor, maybe a campus building. You've got HVAC, pumps, perhaps a compressor bank. Peak load might be 400 kW to 1.2 MW, but the part you can actually interrupt is smaller — somewhere between 100 and 400 kW.

My recommendation: don't buy a demand response platform yet. Buy or rent a three-phase power quality analyzer with IEC 61000-4-30 Class A measurement capability, park it at the service entrance for four to six weeks, and get a real interval load profile with harmonic data attached. Then size everything else against what it sees.

This is the scenario where I made my most expensive beginner mistake. In 2019 we ordered twelve branch-circuit meters for a client in this exact situation — $8,200 plus install. I approved the layout myself. What I missed was that two of the CTs were clamped around a conductor bundle with a parallel neutral run close enough to bias the reading. We spent a quarter arguing with a program administrator about a baseline that was off by roughly 30% on one feeder. The whole dataset got tossed. One Class A analyzer at the main, run for a month, would have told us the same thing for about $600.

To be fair, the meter-based approach is the right long-term answer once you've confirmed your curtailment numbers. It just isn't the first spend.

For the platform itself, at this scale a single-site energy management system with Modbus and BACnet ingestion is usually enough. You don't need a portfolio-grade DR engine with OpenADR VEN capability if you're enrolled in a utility program that still takes a phone call or a PDF form. Don't buy the wholesale-market architecture for a program that doesn't ask for it.

Scenario B: A portfolio of sites, selling into a market or a large aggregator

Here you've got 20 to 60 sites, or one very large campus treated as multiple resource nodes. You're either registered as your own resource or you're a VEN behind an aggregator. Curtailment is being dispatched on a signal, not a phone call.

What changes: telemetry interval, protocol compliance, and audit trail. OpenADR 2.0b is the baseline most aggregators will ask for — either the VEN profile or full 2.0b depending on how much control they want. Telemetry typically needs to be 15 minutes or better, and honestly, on larger loads I'd argue for sub-minute on the controllable circuits so you can prove response within the dispatch window. Your energy management system has to compute per-site curtailment estimates, not just report consumption — and it has to keep a versioned record of the baseline methodology, because baseline disputes are where these programs actually cost money.

This is where an energy monitoring IoT platform like GridSense EMS earns its keep, and I mean that in a specific, unromantic way: not because the dashboards look good, but because the per-site baseline math has to be reproducible six months later when someone questions an event. I've watched a $14,000 portfolio deployment fail an audit not because the meters were wrong but because nobody could reconstruct which baseline method was applied in March versus July.

Size the meter count by controllable circuit, not by building square footage. A 40,000 sq ft facility with three chillers and a compressor bank needs four points, not forty. I've seen the inverse too many times: dense submetering, no curtailment plan, and a platform reporting kilowatts nobody can turn off.

One more thing at this scale — power quality analyzers are not optional. If you're aggregating across sites, one site with bad power factor or elevated harmonic distortion can drag down your portfolio's verified performance, and you won't know which site it is without waveform data. Budget for permanent analyzers at two or three of your highest-value nodes, minimum.

Scenario C: One large industrial load where power quality is the real constraint

This is the counterintuitive one, so I'll say it plainly: at a single large industrial site, your power quality condition often sets your demand response ceiling, not your load profile. You can't reliably curtail through a drive system whose harmonic injection is already close to the IEEE 519-2022 limit at the point of common coupling, because dropping load changes the harmonic spectrum and can push you over. Same story with capacitor banks and resonance points — the curtailment action itself creates the problem.

So the advice here inverts: do the power quality study before you commit to a curtailment number. A Class A analyzer campaign of at least 30 days at the PCC and at each major harmonic-producing feeder. Then size the DR system against the verified headroom, not against nameplate capacity.

And do not count transformer headroom as curtailable capacity. I've heard this proposed more than once — the transformer runs at 60% loading, so we can drop a transformer. That's not how it works. Oil-immersed transformer thermal capacity isn't a controllable load; it's an asset margin that disappears the moment production ramps anyway. If you're sizing around transformer capacity rather than around switchable load, you're building a spreadsheet, not a control system.

On the platform side, this is the scenario where GridSense's custom engineering approach matters. Industrial sites here rarely map cleanly onto a standard template — you'll have legacy PLCs, a mix of protocols, and a curtailment sequence that has to respect process interlocks the vendor has never seen. That's a specification conversation, not a shopping cart one.

How to tell which scenario you're in

Five questions. Answer them in order and stop at the first one that doesn't come back clean.

  1. What's your actual controllable load? Not peak demand. Not transformer rating. The sum of loads you can shed or shift on a signal, verified against process constraints. Under 500 kW, you're likely in A.
  2. Who's paying for the curtailment? A utility program with a form-based enrollment points to A. An aggregator or a market registration points to B. A bilateral industrial contract with penalty clauses usually behaves like C even if the site is small.
  3. Do you already have a trustworthy interval profile? If not, you're not ready to size anything. Rent an analyzer for a month. That order of operations saved me roughly $9,000 the second time I did it properly.
  4. Is your power quality inside limits at the PCC? If it isn't, C applies regardless of size, and the fix sequence is power quality first, curtailment design second.
  5. Can you reproduce a baseline from six months ago? If yes, you can run a portfolio. If no, fix the record-keeping before adding sites.

Looking back, I should have built that five-question list in 2017 instead of 2023. At the time, we were winning work on speed and the checklists felt like friction. They weren't friction — they were the product.

The honest summary: sizing a demand response management system is a data problem dressed up as a procurement problem. The meters, the platform, the protocol compliance — all of it follows from a month of honest measurement. Buy the measurement first and the rest of the specification mostly writes itself. Skip it, and you'll get very precise numbers about the wrong load.

author-avatar
Ingrid Bauer

Ingrid Bauer is an industrial automation and electromechanical systems analyst specializing in variable-frequency drives, motors, pumps, and complete power-drive systems. She applies IEC 61800-9-2 drive-efficiency methods, IEC 60034-30-1 motor efficiency classes, and ISO 9906 pump tests while examining torque-speed duty, harmonics, head, flow, and operating-point efficiency. She helps engineers size drive and pump combinations for real load profiles, cable lengths, ambient conditions, process control, energy use, and maintenance access.

Leave a Reply

Your email address will not be published. Required fields are marked *