Automated Demand Response (ADR)

ADR eliminates the latency of manual operator intervention by using standardized communication protocols like OpenADR 2.0b to transmit price and reliability signals directly from the utility's control room to the customer's energy management system. The end-to-end process—from event initiation to load shed—completes in seconds, not minutes.

• Machine-to-Machine (M2M): No human in the loop for routine dispatch.
• Continuous Communication: Persistent HTTP or XMPP connections ensure near-instantaneous delivery.
• Opt-Out Logic: Automated systems can be pre-programmed with site-specific constraints, allowing automatic opt-out if critical industrial processes are active.

Interoperability is guaranteed through the OpenADR 2.0b standard, an IEC/PAS 62746-10-1 profile. This XML-based protocol defines a common vocabulary for demand response events, ensuring a utility's server can communicate with any certified client regardless of vendor.

• Event State Machines: Defines strict transitions between far, near, and active event states.
• Reports and Telemetry: Clients must acknowledge signals and can report actual load shed via oadrUpdateReport.
• Security Layer: Utilizes TLS 1.2 with mutual authentication to prevent malicious load control commands.

ADR does not simply trip a main breaker. It enables curtailment at the sub-metered asset level. A signal can target specific non-critical loads like HVAC fan speeds, lighting banks, or pumping schedules while leaving essential production machinery untouched.

• Priority-Based Shedding: Loads are categorized into tiers; Tier 1 (non-critical) sheds first.
• Duty Cycling: Instead of full shutdown, ADR can cycle loads (e.g., 15 minutes off, 15 minutes on) to maintain comfort while reducing average demand.
• Behind-the-Meter Generation: Signals can trigger the discharge of on-site battery storage rather than reducing load, achieving net-zero grid impact.

To settle financial baselines, ADR systems require rigorous Measurement and Verification (M&V). Interval meter data (often 1-minute or 5-minute resolution) is streamed back to the utility to calculate the precise load drop against a pre-agreed customer baseline.

• Baseline Models: Common methods include "10-in-10" (average of the 10 highest recent days) or weather-adjusted regression models.
• Feedback Loops: Real-time telemetry allows the operator to see if the curtailment target is being met and send adjustment signals if needed.
• Settlement Automation: Verified load drops are automatically fed into market settlement systems for capacity or energy payments.

Because ADR commands can physically destabilize the grid if spoofed, security is paramount. The architecture relies on Public Key Infrastructure (PKI) and digital signatures to ensure non-repudiation.

• Mutual TLS: Both the Virtual Top Node (VTN) and Virtual End Node (VEN) present certificates.
• XML Signature: Payloads are digitally signed to prevent injection attacks.
• Role-Based Access: Strict separation between registration, event dispatch, and reporting functions prevents lateral movement within the system.

ADR bridges the gap between retail loads and wholesale ancillary services markets. When economic or emergency triggers are met, the ADR server automates the bidding of aggregated curtailable load into markets traditionally served by generation.

• Ancillary Services: Fast-responding ADR resources can qualify for Frequency Regulation or Spinning Reserve markets.
• Economic Dispatch: When the Locational Marginal Price (LMP) exceeds a threshold, an automated economic curtailment signal is sent to enrolled customers.
• Aggregation: Individual small loads are aggregated into a single Virtual Resource large enough to meet market minimum bid sizes.

The centralized software layer that aggregates, prioritizes, and dispatches load reduction requests across thousands of enrolled assets. Orchestration engines apply constraint-based optimization to select which loads to curtail based on:

• Customer opt-out status and comfort preferences
• Real-time telemetry from building automation systems
• Locational value to resolve specific feeder-level congestion
• Baseline methodologies (e.g., 10-in-10 baseline) to measure performance

A cloud-based aggregation of decentralized energy resources—including curtailable loads, battery storage, and rooftop solar—coordinated via software to behave as a single dispatchable entity. ADR provides the demand-side component of a VPP by modulating consumption to mimic generation. VPPs participate in:

• Wholesale capacity markets (e.g., PJM, CAISO)
• Frequency regulation and spinning reserve markets
• Distribution-level non-wires alternatives to defer infrastructure upgrades

A market-based control paradigm where economic signals replace direct load control commands. Rather than issuing curtailment orders, a transactive system publishes real-time locational marginal prices reflecting grid congestion. Intelligent agents at each node autonomously decide whether to consume or reduce based on:

• Willingness-to-pay functions defined by building operators
• Double-auction market clearing mechanisms executed at distribution substations
• Forward price curves enabling pre-cooling and load shifting strategies Transactive energy represents the evolutionary endpoint of ADR toward fully decentralized coordination.

An automatic last-resort protection scheme that progressively disconnects blocks of customer load when system frequency drops below defined thresholds (typically 59.5 Hz in North America). While UFLS is a blunt emergency measure, ADR provides a precision alternative by:

• Shedding non-critical loads before frequency reaches UFLS trigger points
• Enabling fast frequency response within sub-second timeframes via automated controls
• Preserving service to critical infrastructure that UFLS would indiscriminately disconnect ADR transforms load shedding from a circuit-breaker action into a surgical curtailment.