Quick answer
Changes in electricity use responding to prices, incentives or operator requests; enrollment, baseline, event obligations and compensation depend on the actual program.
Answer: Demand response changes electricity use in response to prices, incentives or an operator’s request. Participants may reduce, shift or control loads, and eligible batteries can change net grid demand under a specific program. Enrollment, measurement, baseline, event obligations and payment rules vary. Participation does not automatically guarantee revenue, unrestricted value stacking or preserved backup duration; those outcomes require the actual program terms and equipment configuration.
Demand response versus a demand charge
Demand charges bill a customer for tariff-defined power demand. Demand response concerns how usage changes in response to a price or request. Reducing demand during a called event does not automatically reduce the monthly billed peak, and lowering a monthly peak does not automatically qualify for an event payment.
FERC’s demand response overview provides the regulatory concept and related resources. Implementation depends on the retail program, utility, aggregator or wholesale market concerned.
Different participation arrangements
Price-responsive behavior can shift consumption toward less expensive periods; the benefit may be bill savings rather than a separate payment. Incentive-based programs can compensate eligible performance or committed availability. Reliability or emergency programs can have specific obligations and non-performance provisions. Automated response describes a communication and control method, not a universal compensation category.
Eversource’s demand-response overview describes its regional programs and managed resources. It does not establish that every battery or customer is eligible, or that another territory offers identical terms. Confirm the current local program and approved equipment before including compensation in a proposal.
What the program measures matters
| Payment or measurement concept | Question to resolve |
|---|---|
| Event energy | Which eligible kWh are credited and at what interval rate? |
| Capacity or performance | Is payment based on committed kW, measured average kW or another quantity? |
| Baseline reduction | How is expected consumption estimated and adjusted? |
| Enrollment or availability | Which qualifying conditions and commitments apply? |
| Settlement | What exclusions, caps, deductions, penalties and payment timing apply? |
Battery nameplate kWh is not a substitute for qualifying average kW. A baseline can differ from both a previous month’s peak and instantaneous pre-event load. Retain the method and meter boundary rather than assuming all inverter discharge earns payment.
Two hypothetical payment examples
If a program explicitly pays $0.50 per eligible kWh and 20 events each deliver an eligible 5 kW for three hours, credited energy is 20 × 5 × 3 = 300 kWh, yielding $150. Delivering 5 kW for three hours requires 15 kWh at the stated output boundary; a 13.5 kWh battery cannot supply that alone without another contribution or different assumptions. Check usable energy, reserves, losses and state of charge.
In a different hypothetical program paying $225 per qualifying average kW for a season, 4 kW qualifying performance yields $900. Multiplying that $/kW rate by a battery’s kWh capacity would use the wrong unit. Neither example states an available program rate or guaranteed performance.
Backup and dispatch interact
Event discharge changes available energy. Check reserve settings, who can alter them, opt-out terms, event duration and the consequences of opting out. An outage can occur before recharging is complete. Do not promise that every program avoids storms, preserves full backup or leaves the customer’s routine unaffected.
Solar can contribute to charging when available, but it is not guaranteed recharge between events and its energy has an opportunity cost. Check import/export restrictions and the approved dispatch topology. Load-control programs can also involve comfort or process trade-offs unrelated to batteries.
Aggregation and value stacking
A virtual power plant coordinates multiple resources, but participation is not automatic nationwide wholesale access. FERC’s Order 2222 fact sheet explains removal of barriers to distributed-resource aggregation in organized markets. Check the actual regional implementation, eligibility and applicable retail/wholesale restrictions.
Using the same battery energy for self-consumption, peak shaving, backup and grid services creates scheduling conflicts. Count benefits using one consistent dispatch and settlement model; do not separately assume the full available capacity supports every service simultaneously. Include costs, degradation effects and relevant program commitments.
A practical enrollment handoff
Designers should retain current terms, eligible equipment, baseline and energy/power assumptions. Installers should configure and test controls under approved manufacturer and program procedures, with connectivity and permission requirements documented. Sales teams should disclose payment conditions, uncertainty and reserve trade-offs. Confirm supported program or software integrations with a demonstration; a generic grid-services description does not prove a SurgePV capability.
Common questions
Does every demand response program pay a separate incentive?
No. Price-based response can provide bill savings rather than a distinct payment.
Do I need PV panels to participate?
Eligibility is program-specific; some programs accept batteries, thermostats or other controllable loads without PV.
Does enrollment guarantee backup energy after an event?
No. Verify reserve and dispatch terms and account for recharge uncertainty.
Can all battery benefits simply be added together?
No. Model dispatch conflicts and participation or compensation restrictions before combining value streams.
Related Glossary Terms
About the Contributors
CEO & Co-Founder · SurgePV
Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
