Demand Response & Aggregation
Stage D, Multi-asset and portfolio specialisation. Level 8 of 10.
Building distributed and behind-the-meter flexibility into a single dispatchable aggregated unit, including availability assurance across many sites.
118 chapters · 11 modules · every chapter one 8 to 10 minute explainer · builds on: Course 05, Course 08, Course 09
One chapter is one idea taken to the point of use
Each chapter covers one idea to the point where you can use it, and comes two ways: a narrated explainer, and a deep dive audio discussion of around thirty minutes that works the same material at depth.
Self-paced throughout, and the same chapters can be taught as a cohort. Chapters run in order: each one assumes only what the chapters before it taught, and capability belonging to a later course is named and deferred rather than half-covered.
11 modules · 118 chapters
Open any module for its full chapter list, in teaching order.
M0 What an Aggregated Unit Is, and Whose Promise It Carries Ch 1-10
- The Promise an Aggregator Makes and Cannot Itself Keep
- One Unit, Many Owners, One Seat of Liability
- Why Aggregation Is a Construction Problem
- Behind the Meter, In Front of the Meter, and Why It Matters
- Turning Down Consumption Against Turning Up Output
- What a System Operator Will Not Buy From Many Small Things
- Whether Aggregation Is Even Permitted Where You Stand
- Three Capabilities Carried In, None Retaught
- Where the Customer Contract and the Portfolio Begin
- The Five Assumptions This Method Rests On
M1 The Resources You Can Actually Recruit Ch 11-21
- Reading a Site as a Flexibility Resource
- Refrigeration and Cold Store Thermal Inertia
- Heating, Ventilation and Comfort as a Negotiable Load
- Water, Wastewater and Pumping Schedules
- Electric Vehicle Charging as Interruptible Demand
- Small Behind-the-Meter Batteries in a Fleet
- Standby Generation Brought Into the Market
- Industrial Process Load and the Production Plan
- Domestic Hot Water and Space Heating at Scale
- On-Site Solar and the Export Boundary
- Choosing Which Resource Families to Build On
M2 Qualifying and Registering the Aggregated Unit Ch 22-31
- Market Access Routes for Third-Party Load
- Great Britain's Virtual Lead Party Route
- The United States Order on Distributed Resource Aggregation
- Minimum Size, Minimum Granularity and the Qualifying Threshold
- Drawing the Unit Boundary Across a Network
- Metering Standards for a Site You Do Not Own
- Telemetry Obligations the Fleet Must Satisfy
- Prequalifying a Unit Whose Membership Changes
- Registering the Same Site in Two Places
- A Qualification Pack Assembled and Submitted
M3 Measurement and the Aggregate Baseline Ch 32-42
- Proving a Reduction That Nobody Can See
- Baseline Families and What Each One Assumes
- Adjustment Factors and the Hours Before Dispatch
- Summing Many Site Baselines Into One Unit Baseline
- Treating the Baseline as Stable, and What Breaks It
- Baseline Decay Under Repeated Dispatch
- Gaming a Baseline and Why Rules Punish It
- Measuring at the Boundary or at the Equipment
- Two Markets, Two Verdicts on the Same Event
- Where the Individual Customer's Baseline Is Settled
- A Measured Event Reconciled Line by Line
M4 Control Architecture and Dispatch Allocation Ch 43-53
- The Path From One Instruction to Many Sites
- Central Dispatch Against Local Autonomous Response
- Assuming One Instruction Reaches Everywhere at Once
- Choosing Which Sites to Call First
- Rotation, Fairness and Keeping Hosts Willing
- Over-Calling on Purpose to Hit a Target
- Ramping a Fleet Rather Than a Machine
- Holding a Response for Its Full Duration
- The Rebound After the Event
- Communications Failure as a Commercial Event
- A Dispatch Allocated and Delivered, Worked
M5 Availability Assurance Across Many Sites Ch 54-65
- Declaring Capability You Do Not Operate
- Site Availability as a Standing State, Not a Promise
- Adding Availabilities Up, and Where That Breaks
- Diversification as a Tendency Rather Than a Law
- Correlated Unavailability Inside One Weather System
- One Network Region Instructed Together
- Shared Shift Patterns and Clustered Customer Types
- Headroom Held Back Against Non-Response
- Testing Availability Without Calling the Fleet
- Revising a Declaration Mid-Delivery
- The Availability Figure a Desk Should Actually Declare
- A Declaration Built and Then Stress-Tested
M6 Recruitment, Churn and the Standing Fleet Ch 66-75
- The Cost of Acquiring a Megawatt of Flexibility
- Onboarding Lead Time and the Season You Miss
- Why Recruited Sites Leave
- Attrition as a Planning Input
- The Site That Leaves Inside a Contracted Season
- Treating Membership as Fixed, and What Breaks It
- The Minimum Site Worth Recruiting
- Recruiting for Depth or Recruiting for Speed
- Channel Partners and Recruiting Through Somebody Else
- A Recruitment Plan Sized Against a Sold Volume
M7 Paying the Sites and Keeping the Margin Ch 76-85
- Buying Availability From Many, Selling It to One
- Fixed Payment, Revenue Share or Pay for Performance
- Paying for Being Ready Against Paying for Responding
- Whether a Penalty Reaches the Host
- The Aggregator's Own Balance Sheet in the Middle
- The Host's Bill Saving as a Competing Payment
- Platform, Hardware and the Fixed Cost of Running a Fleet
- Where the Margin Actually Comes From
- Settling With Hosts After the Market Settles
- A Month of Unit Economics, Worked
M8 When the Unit Does Not Perform Ch 86-96
- Attributing a Shortfall to a Site
- The One Site That Fails the Whole Unit
- Partial Delivery and Scaled Payment
- Absorbing the Penalty or Passing It Down
- Derating After a Failed Event
- Suspension and Losing the Unit Altogether
- Disputing the Operator's Measured Figure
- Rebuilding a Baseline After a Bad Season
- A Failure That Was Nobody's Fault
- Reporting Performance Honestly Inside the Business
- A Failed Event Traced to Its Cause
M9 The Aggregator Among Other Parties Ch 97-106
- The Supplier Whose Customer You Just Dispatched
- Compensating a Supplier for Volume It Did Not Sell
- The Independent Aggregator Argument and Its Assumptions
- Two Operators Instructing the Same Fleet
- Local Flexibility Tenders as a Second Customer
- Consent, Data and the Household You Control
- Switching Suppliers Without Losing the Site
- Aggregators Competing for the Same Premises
- Where Reform Is Heading and Why It Matters
- Mapping the Parties Around One Recruited Site
M10 A Worked Unit, End to End, and the Limits Ch 107-118
- The Worked Mandate: What Has Been Sold
- The Worked Unit: Recruiting to the Target
- The Worked Unit: Qualification and the Declaration
- The Worked Unit: A Mild Month
- The Worked Unit: A Cold Week and a Correlated Failure
- The Worked Unit: The Penalty Apportioned
- The Same Obligation Built Two Ways
- A Unit That Met Every Rule and Still Failed
- The Five Simplifications, Gathered and Answered
- What Aggregation Cannot Make Firm
- Handing the Unit to the Contract and the Portfolio
- A Dispatchable Unit Against a Lucky One
The brochure gives each of these 118 chapters a paragraph on what it covers and what you can do once you have worked through it.
This is course 15 of twenty
It stands alone, and it is also the entry point to the Battery and Flexibility Desk Academy pathway.