🎓 Lesson 5
D3
DR Event Lifecycle: From Signal to Settlement
DR Event Lifecycle is the step-by-step journey of a demand response signal—from when the grid operator sends it, through building system reactions, to final energy reduction and verification.
🎯 Learning Objectives
- ✓ Explain each phase of the DR Event Lifecycle and map it to corresponding IEC 62746-2 and OpenADR 2.0b state transitions
- ✓ Analyze a time-series building load profile to identify compliance with DR event timing windows (e.g., notice-to-start, duration, ramp-up/down)
- ✓ Design a DR-ready control logic flowchart that enforces mandatory pause periods and measurement & verification (M&V) data capture per ASHRAE Guideline 135-2022
- ✓ Calculate baseline-adjusted load reduction for settlement using the FERC-approved 'Simple Average' method and verify against ISO-NE/CAISO tolerance thresholds
📖 Why This Matters
Demand response isn’t just ‘turning off lights’—it’s a mission-critical, time-synchronized service that helps prevent blackouts, integrates renewables, and reduces fossil fuel peaker plant use. Understanding the full DR Event Lifecycle ensures engineers design systems that reliably deliver megawatts *when promised*, avoid penalty charges, and qualify for incentive payments—turning energy flexibility into measurable value.
📘 Core Principles
The DR Event Lifecycle comprises six interoperable phases: (1) Signal Initiation (by ISO/utility), (2) Notification & Validation (via OpenADR or IEEE 2030.5), (3) Pre-Event Readiness (system health check, baseline confirmation), (4) Active Response Execution (load reduction/shift per pre-agreed strategy), (5) Real-Time Monitoring & Adaptation (telemetry, anomaly detection), and (6) Settlement & Verification (M&V, deviation reporting, payment reconciliation). Each phase has defined timing constraints, data requirements, and failure-handling protocols—grounded in standards like NAESB WEQ, OpenADR 2.0b, and FERC Order No. 2222. Misalignment in any phase risks non-compliance, revenue loss, or grid instability.
📐 Baseline-Adjusted Load Reduction
This formula quantifies actual delivered DR performance by comparing measured load during the event to a statistically validated baseline, adjusted for weather and occupancy. It is the foundation for financial settlement and regulatory reporting.
Net Load Reduction (NLR)
NLR = (BL + PreAdj) − MEAS − ReboundAdjQuantifies verified load reduction delivered during a DR event, adjusted for pre-cooling and post-event rebound effects.
Variables:
| Symbol | Name | Unit | Description |
|---|---|---|---|
| BL | Baseline Load | kW | Statistically derived load estimate for the event period absent DR action |
| PreAdj | Pre-Event Adjustment | kW | Load increase intentionally added before event (e.g., thermal storage charging) |
| MEAS | Measured Event Load | kW | Average real-time load during the official DR event window |
| ReboundAdj | Post-Event Rebound Adjustment | kW | Load increase occurring immediately after event due to deferred consumption |
Typical Ranges:
Commercial office building (2-hr event): 50 – 300 kW
Data center with thermal storage: 200 – 2000 kW
💡 Worked Example
Problem: A commercial building receives a 2-hour DR event (13:00–15:00). Baseline load (calculated per CAISO Method 1) is 425 kW. Measured load during event averages 298 kW. Pre-event HVAC pre-cooling added 15 kW to baseline; post-event rebound adds 12 kW during recovery hour. Calculate NLR.
1.
Step 1: Identify baseline (BL) = 425 kW, measured event load (MEAS) = 298 kW, pre-cooling adjustment = +15 kW, rebound correction = −12 kW (since rebound occurs *after* event window and must be subtracted from reduction credit).
2.
Step 2: Apply NLR = (BL + Pre-cooling Adj.) − MEAS − Rebound Adj. = (425 + 15) − 298 − 12 = 440 − 298 − 12 = 130 kW.
3.
Step 3: Verify against CAISO tolerance: |NLR − contracted MW| ≤ 10% of contract. If contracted was 120 kW, deviation = 10 kW (8.3%) → compliant.
Answer:
The Net Load Reduction is 130 kW, which meets CAISO’s ±10% performance tolerance for a 120 kW commitment.
🏗️ Real-World Application
In summer 2023, PG&E activated a 100 MW DR program during a heatstorm. A Bay Area hospital deployed its DR-ready BMS to shed non-critical loads (chiller staging, lighting dimming, EV charger throttling) within 10 minutes of OpenADR 2.0b signal receipt. Its automated M&V system logged 15-second interval meter data, confirmed 92 kW reduction (vs. 90 kW contracted), passed CAISO’s 15-minute averaging window, and triggered automatic settlement via the PG&E DR Portal—all within 72 hours. Failure to capture pre-event baseline or misalign timing would have voided $12,400 in incentives.
🔧 Interactive Calculator
🔧 Open Grid-Interactive Building Energy Systems Calculator📋 Case Connection
📋 Austin Energy Smart Schools Initiative
Need scalable, low-cost grid-interactive solution compatible with aging HVAC and lighting infrastructure; budget capped...