Demand Response

Options Review

Carl Raish

November 27, 2007

22

• ERCOT requires a fifteen (15) minute settlement interval

• Vast majority of Customers do not have this level of granularity

• Profiles are created using adjusted static models• Models estimate customer level interval load based on

• calendar-type data (season, day of week, time of day)• weather data (temperature, wind-speed, cloud-cover, dew-point)

• Backcasted Profiles are generated the day following a trade day and used for all settlements (initial, final and true-up)

• Load Profiling• Converts monthly kWh reads to fifteen (15) minute intervals• Enables the accounting of energy usage in settlements

ERCOT Load Profiling

33

• ERCOT Load Profile Models are documented in Appendix E of the Load Profiling Guide on the ERCOT website

• http://www.ercot.com/mktrules/guides/loadprofiling/current.html

ERCOT Load Profiling

44

• ESI IDs are linked to Load Profile Models by their Load Profile ID

• Rules for assigning ESI IDs to Load Profile ID are also documented in Appendix D of the Load Profiling Guide

http://www.ercot.com/mktrules/guides/loadprofiling/2007/11/AD001/Appendix_D_-_Profile_Decision_Tree_110107.xls

ERCOT Load Profiling

55

3 Load Profile Groups - 10 Segments3 Load Profile Groups - 10 Segments

Residential (2)Residential (2)

Low-Winter RatioLow-Winter Ratio (Non-electric Heat)(Non-electric Heat)High-Winter RatioHigh-Winter Ratio (Electric Heat)(Electric Heat)

Business (6)Business (6)

Low Load FactorLow Load FactorMedium Load FactorMedium Load FactorHigh Load FactorHigh Load FactorNon-DemandNon-DemandIDR DefaultIDR DefaultOGFLTOGFLT

Non-Metered (2)Non-Metered (2)

Lighting (Street Lights)Lighting (Street Lights)Flat (Traffic Signals)Flat (Traffic Signals)

66

8 ERCOT Weather Zones8 ERCOT Weather Zones

77

8 8 Weather Weather

ZonesZones

10 Profile10 ProfileSegmentsSegments

80 Load Profiles80 Load Profiles

Total ProfilesTotal Profiles

88

Profile IDs

• Additional Fields in the Load Profile ID:

– Meter Data Type Code (IDR or NIDR)– Weather Sensitivity Code (NWS or WS)– TOU Schedule Code (NOTOU, TOU01, TOU02, …, TOU12,

TOU13)

• Examples of valid Profile Ids:

RESHIWR_COAST_NIDR_NWS_NOTOU

RESLOWR_SCENT_NIDR_NWS_NOTOU

99

Profiling For Demand Response

• Adjusted static models cannot capture dynamic control events• The Load Profiling Guide specifies that Lagged Dynamic

Profiles will be used to settle demand response programs– Interval data collected from a representative sample of program

participants to capture load impacts of control events as they occur

• Each demand response program will need a unique profile (shape)– ERCOT systems need to accommodate numerous additional

profiles (shapes), and– A method for linking participating ESIIDs to their specific

demand response program

1010

• Demand Response programs will be CR specific

– ERCOT will be assigning each program unique code/codes

• ESIIDs on a DR program will need to be linked to the code assigned by ERCOT for settlement

• PWG has considered a number of options to implement the coding

Summary of PWG Options

1111

Option 1: DR Program Coded in Profile ID Segment

• ESI IDs participation in a DR program indicated in the Load Profile Segment field

– Example:• Profile Type Code before: RESLOWR – (RESLOWR no DR program)

• Profile Type Code after: RESL0001 – (RESLOWR on DR program ‘01’)

1212

Option 2: DR Program Coded in TOU Field

• ESI IDs participation in a DR program indicated in the TOU Schedule field of the Load Profile ID– Examples:

• TOU Schedule before: NOTOU – (No DR program / No TOU)• TOU Schedule after: ‘D0100’ – (DR program ‘01’ / No TOU)• TOU Schedule after: ‘D0203’ – (DR program ‘02’ / TOU Schedule ‘03’)

• TOU Schedule before: D0103 – (DR program ‘01’ / TOU Schedule ‘03’)• TOU Schedule after: ‘D0100’ – (DR program ‘01’ / No TOU)• TOU Schedule after: ‘NOTOU’ – (No DR program / No TOU)• TOU Schedule after: ‘TOU03’ – (No DR program / TOU Schedule ‘03’)

• TOU Schedule before: TOU05 – (No DR program / TOU Schedule ‘05’)• TOU Schedule after: ‘D0105’ – (DR program ‘01’ / TOU Schedule ‘05’)• TOU Schedule after: ‘D0200’ – (DR program ‘02’ / No TOU)

1313

Option 3: DR Program Coded in Weather Sensitivity Field

• ESI IDs participation in a DR program indicated in the Weather Sensitivity field of the Load Profile ID

• First position of WS code ‘D’ for all participants on a DR program

– Examples:• Weather Sensitivity Code before: NWS – (No DR program / Non WS)

• Weather Sensitivity Code after: ‘D01’ – (DR program ‘01’ Not WS)

• Weather Sensitivity Code before: ‘D01’ – (DR program ‘01’ Not WS)

• Weather Sensitivity Code after : ‘NWS’ – (No DR program / Non WS)

1414

Option 4: DR Program Coded in Profile ID Segment (Modified)

• ESI IDs participation in a DR program indicated in the Load Profile Segment field of the Load Profile ID

– Very similar to Option 1– Definition of the Profile Group changed to always be the first 3

positions – Fourth position would be a Profile Segment Letter– Last 4 positions for DR programs

– Example:• Profile Type Code before: RESL0000 – (RESLOWR no DR program)

• Profile Type Code after: RESL0001 – (RESLOWR on DR program ‘01’)

1515

Option 5: DR Program Coded in Weather Sensitivity Field (Modified)

• ESI IDs participation in a DR program indicated in the Weather Sensitivity field of the Load Profile ID– First position of WS code ‘W’ for Weather Sensitive ESI IDs and

‘N’ for Non-Weather Sensitive ESI IDs– Last two positions for DR program

– Examples:• Weather Sensitivity Code before: NWS – (No DR program Non WS)

• Weather Sensitivity Code after: ‘N01’ – (DR program ‘01’ Not WS)

• Weather Sensitivity Code after : ‘W01’ – (DR program ‘01’ WS)

• Weather Sensitivity Code before : N01 – (DR program ‘01’ Not WS)

• Weather Sensitivity Code after : ‘NWS’ – (No DR program Non WS)

• Weather Sensitivity Code after : ‘W01’ – (DR program ‘01’ WS)

1616

Option 6: Texas Set Change to Allow Dynamic Profile ID Changes

• Texas Set changes to automatically update Profile IDs in response to changes to DR program participation– Switch – MoveIn– MoveOut

1717

Option 7: IDR Settlement for DR Programs

• IDR settlement is currently available for DR program participants

• No Lagged Dynamic Profile would be needed• No DR program coding necessary

1818

Option 8: DR Program Coded in a New Profile ID Field

• Extend length of Profile ID field to add a new field for coding DR participation

1919

Option 9: Lookup Table to Flip Profile ID Before Settlement

• Create lookup table to link CRs to DR programs • Used in conjunction with Option 1• ESIIDs with invalid CR to DR program relationships

identified – Profile Id modified prior to settlement– Profile Ids reverted to original values after settlement

completes

2020

Option Brief Description ERCOT Impact1 DR program in the Profile ID Segment Less2 DR program in the TOU field Affects Nodal3 DR program in the Weather Sensitivity field Affects Nodal4 DR program in the Profile ID Segment (modified) Affects Nodal5 DR program in the Weather Sensitivity field (modified) Affects Nodal6 Texas Set change to allow dynamic Profile ID changes Long Term7 IDR Settlement for DR programs < 50 k IDRs None8 DR program in a new Profile ID field Affects Nodal9 Lookup table to flip Profile ID before settlement Less

2121

Questions?

ON

OFF