Demand response is one of the most important tools available for maintaining the stability and efficiency of modern electricity grids. As renewable generation increases, the grid's ability to match supply and demand in real time depends increasingly on the flexibility of the demand side — the ability of consumers to reduce, shift, or increase their electricity consumption in response to grid conditions.
IoT (Internet of Things) infrastructure is the enabling technology that makes demand response practical at scale. Without IoT devices to monitor energy consumption, receive and relay signals, automate load adjustments, and verify performance, demand response would remain a manual, slow, and unreliable process. This article explores how IoT infrastructure supports every stage of the demand response cycle and what capabilities are needed to participate effectively in modern demand response programs.
What Is Demand Response?
Demand response (DR) refers to changes in electricity consumption by end-use customers in response to changes in the price of electricity or incentive payments, or in response to grid reliability signals. In practice, demand response means temporarily reducing or shifting energy consumption during periods of high demand (peak periods) or grid stress, in exchange for financial compensation.
Demand response serves several critical functions in the electricity system:
- Peak shaving: Reducing demand during peak periods avoids the need to activate expensive peaking power plants (often gas-fired turbines) and reduces wholesale electricity prices for all consumers.
- Grid balancing: As intermittent renewable generation (wind and solar) increases, demand response provides flexibility to absorb surplus generation or reduce demand when generation falls short.
- Congestion management: Local demand response can alleviate congestion on specific parts of the distribution or transmission network, avoiding or deferring costly network upgrades.
- Frequency regulation: Fast-acting demand response can provide ancillary services such as frequency containment reserves, helping to maintain the grid frequency within its normal operating band.
Types of Demand Response
Economic Demand Response
In economic DR programs, participants receive a financial incentive (either a direct payment or a reduced tariff) for reducing their consumption when called upon. The most common model is a capacity-based program, where participants commit to providing a specified amount of demand reduction (e.g., 100 kW) and are paid a monthly or annual capacity fee for their availability, plus an activation fee each time they are called upon to curtail. Economic DR programs are typically administered by transmission system operators (TSOs), aggregators, or utility companies.
Emergency Demand Response
Emergency DR is activated when the grid is under severe stress — for example, when available generation is insufficient to meet demand and there is a risk of blackouts. Participants in emergency DR programs are contractually obligated to curtail their load when called, and penalties may apply for non-compliance. Emergency DR is a last resort before involuntary load shedding (rolling blackouts).
Price-Responsive Demand Response
In markets with dynamic pricing (real-time pricing, time-of-use tariffs, or critical peak pricing), consumers can voluntarily adjust their consumption in response to price signals. When prices are high (reflecting high demand or low supply), consumers reduce consumption to save money. This type of DR does not require a formal program or aggregator — it is driven purely by price incentives and requires the consumer to have visibility into their real-time consumption and the current price.
Ancillary Services
Demand response can also participate in ancillary service markets, providing services such as frequency containment reserves (FCR), automatic frequency restoration reserves (aFRR), and manual frequency restoration reserves (mFRR). These services require fast response times (seconds to minutes) and precise, verified delivery of the committed load adjustment. Ancillary services typically command the highest payments but also impose the most stringent technical requirements.
How IoT Enables Automated Demand Response
The traditional approach to demand response involved phone calls, emails, or pager alerts to building managers, who would then manually turn off equipment. This approach is slow, unreliable, and does not scale. Automated Demand Response (ADR) uses IoT infrastructure to automate the entire process, from signal delivery to load curtailment to performance verification.
Signal Delivery
The first step in any demand response event is delivering the signal from the grid operator, aggregator, or price feed to the consumer's site. The most widely adopted standard for this is OpenADR (Open Automated Demand Response), an open communication protocol developed by Lawrence Berkeley National Laboratory. OpenADR uses standard internet protocols (HTTP/XML or HTTP/JSON) to deliver DR event signals, including the event start time, duration, signal level, and expected curtailment.
An IoT gateway at the customer's site receives the OpenADR signal (or a proprietary signal from an aggregator) and translates it into local actions. The gateway must be always-on, always-connected, and capable of receiving and processing signals with low latency — typically within seconds of the signal being sent.
Load Monitoring
Before, during, and after a demand response event, accurate, high-resolution energy monitoring is essential. IoT energy monitoring devices (such as EpiSensor's wireless electricity monitors) provide real-time visibility into the site's total consumption and the consumption of individual loads that are candidates for curtailment. This data is used for:
- Baseline calculation: Determining the site's expected consumption in the absence of the DR event. Common baseline methods include the "10 of 10" (average consumption from the 10 most recent similar days) or regression-based models.
- Real-time curtailment tracking: During a DR event, real-time monitoring shows the actual consumption against the baseline, allowing the site to verify that it is meeting its curtailment commitment.
- Post-event M&V: After the event, metering data is used to calculate the actual demand reduction achieved, which determines the financial settlement.
Automated Load Control
IoT devices can go beyond monitoring to actively control loads. When a DR signal is received, the gateway can send commands to building management systems (BMS), HVAC controllers, lighting systems, EV chargers, or industrial process equipment to reduce consumption. Common automated DR strategies include:
- HVAC setpoint adjustment: Raising the cooling setpoint by 1-2°C during a DR event can reduce HVAC energy consumption by 10-20% with minimal impact on occupant comfort.
- Lighting reduction: Dimming non-critical lighting by 20-30% reduces consumption while maintaining adequate illumination.
- EV charging deferral: Pausing or slowing EV charging during a DR event shifts flexible load to a later period.
- Process load scheduling: In industrial facilities, batch processes or non-time-critical operations can be rescheduled to avoid peak periods.
- Battery dispatch: Discharging on-site battery storage during a DR event reduces grid demand while maintaining critical loads.
Measurement and Verification Requirements
Demand response programs require credible, auditable measurement and verification (M&V) to confirm that participants actually delivered the demand reduction they committed to. The M&V requirements vary by program, but typically include:
Metering Requirements
- Interval metering: Most DR programs require metering data at 15-minute or shorter intervals. Some ancillary service products require 1-minute or even 4-second interval data.
- Accuracy: Metering used for DR settlement should be Class 1 or better (per IEC 62053), depending on the program requirements and the value of the curtailment.
- Data availability: Metering data must be available to the DR program administrator within a specified timeframe after the event — typically within 24 hours for economic DR, or in near-real-time for ancillary services.
Baseline Methodologies
The baseline represents what the site's consumption would have been without the DR event. Common methodologies include:
- Unadjusted average: Average consumption over a defined number of recent similar days (e.g., same day of week, similar weather).
- Weather-adjusted regression: A statistical model that predicts consumption based on weather variables (outdoor temperature, humidity, solar radiation), providing a more accurate baseline for weather-sensitive loads like HVAC.
- Same-day adjustment: A pre-event window (e.g., the hour before the DR event) is used to adjust the baseline for day-specific conditions.
Accurate baseline calculation requires historical metering data at high temporal resolution — another reason why continuous, IoT-based energy monitoring is a prerequisite for effective DR participation.
The IoT Infrastructure Stack for Demand Response
An effective demand response deployment requires a complete IoT infrastructure stack:
- Sensors and meters: Wireless energy monitors, CTs, pulse counters, and environmental sensors deployed across the site to measure electricity consumption, temperature, and other relevant parameters.
- Local network: A reliable wireless network (such as EpiSensor's ZigBee mesh) connecting sensors and meters to the local gateway.
- Gateway: An on-site gateway that aggregates sensor data, receives DR signals (via OpenADR, MQTT, or API), executes local control logic, and communicates with upstream platforms.
- Cloud platform: A cloud-based platform for data storage, analytics, baseline calculation, event scheduling, and reporting.
- Integration layer: APIs and protocols to connect with aggregator platforms, BMS systems, DR program administrators, and settlement systems.
How EpiSensor Supports Demand Response
EpiSensor's wireless energy monitoring infrastructure provides the monitoring and connectivity layer that demand response programs require:
- Real-time energy monitoring: EpiSensor's wireless electricity monitors provide high-resolution, Class 1 accurate energy data at configurable intervals, delivering the metering data needed for baseline calculation, real-time event tracking, and post-event M&V.
- Multi-point sub-metering: By deploying monitors at individual circuits and loads, EpiSensor enables site operators to identify and quantify the contribution of each load to the total curtailment, supporting targeted DR strategies that minimise operational impact.
- Gateway with edge intelligence: The EpiSensor gateway can host local applications that receive DR signals and execute control logic at the edge, ensuring fast response even if cloud connectivity is temporarily interrupted.
- Open integration: EpiSensor's gateway supports MQTT, HTTP, and Modbus TCP, enabling integration with aggregator platforms, OpenADR servers, BMS systems, and cloud analytics platforms.
- Reliable data delivery: The self-healing ZigBee mesh network and local data buffering ensure that metering data is delivered reliably, even during the high-stress conditions that often coincide with DR events (e.g., extreme weather, high building occupancy).
- Scalable deployment: For aggregators and ESCOs managing demand response across a portfolio of buildings, EpiSensor's standardised hardware and consistent data format simplifies the deployment and management of monitoring infrastructure at scale.
The Growing Importance of Demand Response
Demand response is becoming increasingly important as electricity systems worldwide transition to higher penetrations of renewable generation. The European Union's Clean Energy Package explicitly recognises demand response as a resource that should be able to compete with generation in electricity markets. National regulations — such as Germany's Section 14a EnWG, Ireland's DS3 system services, and the UK's Demand Flexibility Service — are creating new frameworks and incentives for demand-side flexibility.
For building owners, facility managers, and energy service companies, the ability to participate in demand response programs represents a significant revenue opportunity and a contribution to grid decarbonisation. But effective participation requires the right IoT infrastructure: accurate metering, reliable communication, and the ability to automate and verify demand reduction at scale.
Summary
IoT infrastructure is the backbone of modern demand response. From signal delivery to load monitoring, from automated curtailment to measurement and verification, every stage of the demand response cycle depends on connected devices, reliable communication, and accurate data.
EpiSensor provides the monitoring and connectivity layer that demand response programs require — delivering high-resolution, accurate energy data from a reliable wireless network that can be deployed quickly and scaled across a portfolio of buildings. As demand response programs grow in scope and sophistication, the value of having a robust, flexible IoT infrastructure in place will only increase.