1. PWG Demand Response Follow Up Jackie Ashbaugh October 23, 2007

2. 2 2 Overview PWG/TX Set Conference Call Things to consider… ERCOT Recommendation Next Steps

3. 3 3 PWG/TX Set Conference Call Option Suggestion of an additional field on the ESIIDSERVICEHIST table or new table to store the ESIID to Demand Response Profile assignment ERCOT has had preliminary discussions on this option and determined the following: –Demand Response program registration processes needed. –Could involve adding a new segment for Demand Response to the Profile ID. More analysis is needed. –Additional field on ESIIDSERVICEHIST table: Must file metadata change request to Lodestar Change to the Siebel to Lodestar, 814_20 and 867_03 business processes in ERCOT systems to ensure data is assigned appropriately for data aggregation regardless of DR profile change occurring in ERCOT systems manually or transactionally Create a validation prior to Data Aggregation to ensure that ESIIDs with Demand Response profiles are associated to the CR that owns the program; if not, what happens? Use standard Load Profile assignment? Change to the SCR 727 ESIID Service History & Usage extract to add new field

4. 4 4 PWG/TX Set Conference Call Option con’t –Additional table: Create a validation prior to Data Aggregation to ensure that ESIIDs with Demand Response profiles are associated to the CR that owns the program; if not, what happens? Use standard Load Profile assignment? Change to Data Aggregation process to gather ESIID data from new table Change to the SCR 727 ESIID Service History & Usage extract to add new table Known –2007-2008 Nodal impacts for resources, business processes, and systems

5. 5 5 Things to consider… PWG has a draft list of options for approaches to Demand Response PWG/TX Set has had a conference call to discuss additional approaches to Demand Response profile codes ERCOT is currently performing analysis on potential options, including those provided by the market considering, but not limited to the following: –Registration process for DR program with ERCOT –Both ERCOT & TDSPs maintaining CR DR program information –Forwarding of data transactionally; how confidential? –Data included in data extracts (ESIIDs & Load); how confidential? –Impacts to data aggregation and settlements –Impacts to Day to Day and Data Extract Variance processes –Impacts to settlements disputes –Impacts to Nodal

6. 6 6 ERCOT Recommendation Demand Response Task Force be created with representation from COPS & RMS subcommittees and working groups to develop options for implementing and managing Demand Response programs focusing on a single solution versus short and long term

7. 7 7 Questions? ON OFF