Registration Data Collection September Window Kick Off Meeting August 28, 2009 http://nodal.ercot.com 1

Antitrust Admonition ANTITRUST ADMONITION ERCOT strictly prohibits Market Participants and their employees who are participating in ERCOT activities from using their participation in ERCOT activities as a forum for engaging in practices or communications that violate the antitrust laws. The ERCOT Board has approved guidelines for members of ERCOT Committees, Subcommittees and Working Groups to be reviewed and followed by each Market Participant attending ERCOT meetings. If you have not received a copy of these Guidelines, copies are available at the Client Relations desk. Please remember your ongoing obligation to comply with all applicable laws, including the antitrust laws. DISCLAIMER All presentations and materials submitted by Market Participants or any other Entity to ERCOT staff for this meeting are received and posted with the acknowledgement that the information will be considered public in accordance with the ERCOT Websites Content Management Operating Procedure. http://nodal.ercot.com 2 http://nodal.ercot.com 2

RARF Screening Process / Reference Materials Data Collection Details Agenda Objective and Scope Project Logistics Approach / Schedule RARF Screening Process / Reference Materials Data Collection Details Modified Reactive Requirements for Wind Transmission Data Transmission Data Tab’s Background Pre-populated RARFs Inventory of Transmission Asset Forms Planning and Protection Data Sub Synchronous Data Load Resource Registration Changes Next Steps September window specific date Final Phase for Resource Node and Meter Mapping (Formerly MP-10) Q&A / Open Forum http://nodal.ercot.com 3

Objective and Scope Objective – to finalize the Nodal Resource Entity Registration Data Collection effort prior to Market Trials Scope of the remaining data collection: Resource Entity Owned Transmission, Planning and Protection Data September Window will include Wind Sites and all remaining sites http://nodal.ercot.com 4

Project Logistics - Approach / Schedule Kick off for September Window 8/28/09 Receive Audit Report and pre-populated RARF during the week of 9/1/09 Conference call with Account Managers starting week of 9/8/09 Iteration 1 submissions due 9/30/09 (20 business days) Iteration 2 submissions (if needed) due 10/27/09 (15 business days) Iteration 3 submissions (if needed) due 11/16/09 (10 business days) http://nodal.ercot.com 5

Project Logistics - Approach / Schedule 2009 MAR APR MAY JUN JUL AUG SEP OCT NOV DEC Private Use Network Transmission Data Collection 85% Prod Quality - Iteration 1 - Iteration 2 - Iteration 3 95% Prod Quality 98% Prod Quality Private Use Network Planning and Protection Data Collection June Window - Non-Wind Transmission / Planning / Protection Data Collection - Iteration 1 - Iteration 2 - Iteration 3 85% Prod Quality 95% Prod Quality 98% Prod Quality September Window - Wind / All Remaining Sites Transmission / Planning / Protection Data Collection Kick Off Market Call Kick Off Market Call - Iteration 1 - Iteration 2 - Iteration 3 85% Prod Quality 95% Prod Quality 98% Prod Quality EIS 1.19 to EDS 8/10 SEM GO-LIVE 8/31 MP-10 Phase 2 Final Validation http://nodal.ercot.com 6

Project Logistics - Approach / Schedule Approach for this phase will be similar to the resource data collection in 2008 the Window will be broken up into 3 iterations each with increasing goals of production quality Iteration 1 – 85% production quality Iteration 2 – 95% production quality Iteration 3 – 98% production quality Iteration 1 will begin with ERCOT sending each RE assigned to the September Window a pre-populated RARF and an audit report Audit reports will detail each error in the RARF and the violated business rules ERCOT will provide pre-populated RARFs containing data previously submitted through various artifacts (transmission data slides will discuss in greater detail) This pre-populated RARF must be used going forward for all changes Each RE’s Account Manager will schedule a formal conference call to discuss errors on the audit report http://nodal.ercot.com 7

Project Logistics - Approach / Schedule Approach for this phase will be similar to the resource data collection in 2008 (continued) Iteration 2 and 3 will include interim audit reports as revisions are submitted by REs Account Manager’s will schedule conference calls in Iteration 2 and 3 on an as-needed basis At the close of each iteration, a formal production quality metric will be published to the readiness center A dashboard with the status of each RE will be published weekly http://nodal.ercot.com 8

Project Logistics - Approach / Schedule The September Window will officially begin 9/1/09 REs will receive their pre-populated RARFs the week of 9/1/09 ERCOT Account Managers will schedule calls to start the week of 9/8/09 End of Resource Registration data collection is November 16, 2009 http://nodal.ercot.com 9

Project Logistics - RARF Screening Process / Reference Materials Registration Audit Process http://nodal.ercot.com 10

Data Collection Details – Reactive Data Modified Reactive Requirements for Wind MW1 should be <= Unit Min output or LRL (> 0) MW4 should be >= Unit Max output or HRL MW5 – removed Reactive curve is for turbine group only, Caps and Reactors on separate tab Wind Reactive rules under review and will be updated in the guide when finalized New addendum For wind resources that have multiple groupings of turbines, an Addendum will be necessary to provide one, consolidated reactive curve for the unit Addendum will be sent with the RARF http://nodal.ercot.com 11

Data Collection Details - Transmission Data Transmission Data Tabs Background These are derived from 2 artifacts TDF (Transmission Data Form) used in zonal and Resource Node Meter Mapping GSU Transformer and Transmission Assets tabs revamped from the original RARF These artifacts were then integrated into the RARF at the request of TPTF (reviewed by TPTF in September 2008) Some fields were added / removed based on ERCOT data requirements Resource Entities have provided much of this data in previous activities This effort will focus on closing gaps and validating data already provided Audit Reports will detail only errors or warnings. REs should review all pre-populated data to ensure accuracy in previous submittals http://nodal.ercot.com 12

Data Collection Details - Transmission Data Process of Pre-populating RARFs Initial population baselines data from the zonal model, including updates made through the Resource Node Meter Mapping process The process then updates this baseline with data submitted via the old GSU Transformer and the Transmission Assets tabs In short, ERCOT will provide all data we have on file to Resource Entities in a pre-populated RARF http://nodal.ercot.com 13

Data Collection Details - Transmission Data Common issues encountered during preliminary transmission data reviews: Device names (lines, breaker, transformers, etc) do not match the ERCOT Mnemonic In these cases, ERCOT cannot update data submitted via RARF We will have to work with Resource Entities individually to resolve these One-lines do not agree with registered assets (resources, transmission data, etc) In some cases it was not possible to distinguish between TSP and RE owned assets In these cases, REs are asked to simply remove them from their RARF Most commonly these are lines going from a Gen Site to a TSP substation http://nodal.ercot.com 14

Data Collection Details - Transmission Data Inventory of Transmission Data Forms (high level lists) Lines Breakers and Switches Capacitors and Reactors Transformers Static Var Compensators Series Devices Load Data (non-puns will provide Aux / Site Service Load) http://nodal.ercot.com 15

Data Collection Details - Planning and Protection Data Planning and Protection data was originally targeted for late 2009 / early 2010 Schedule accelerated in order to minimize iterations with Resource Entities Schedule accelerated also to avoid conflicts with other activities such as re-qualification of QSEs and Market Trials The following changes made to the planning and protection data: Protection Only change is adding a 4th time point to each section (Underfrequency, Overfrequency, Overvoltage, Undervoltage) http://nodal.ercot.com 16

Data Collection Details - Planning and Protection Data The following changes made to the planning and protection data (cont): Planning: Several data elements removed from generator details Generator Auxiliary Load is now optional except for Combined Cycle Units PSSE Model files Method of submittal will now be a zip file accompanied by the RARF submittal in the SR (or alternative email process) Some files are noted in the RARF as optional based on the details of that site Note that the PSSE templates are located at http://www.ercot.com/gridinfo/generation/ Necessary if PSSE template for specific turbine does not exist Note that all changes will be included in the pre-populated RARF sent to all REs at the start of the September Window http://nodal.ercot.com 17

Data Collection Details - Planning and Protection Data Business Rules for Planning and Protection ERCOT team has added these to the Resource Registration Guide Note: Protection Voltage in P.U. instead of kV. Posted at http://www.ercot.com/services/rq/re under Key Documents http://nodal.ercot.com 18

Data Collection Details - Sub Synchronous Data Sub Synchronous data will be requested of Resource Entities that have already collected this data For Resource Entities that do not have this data available, it will be required at a later time if their site is impacted by / included in a Reactive Management Study Note that REs can follow current RFPs by reviewing the status updates provided to the Regional Planning Group (RPG) RFP for Study may define additional data from REs beyond that which is requested in the current RARF form There are no changes to this RARF tab http://nodal.ercot.com 19

Data Collection Details - Load Resource Registration Changes NPRR162 - Change the Sign Convention of Net Real Power Consumption, LPC and MPC of Load Resources (formerly titled “Change the Sign Convention for Load Resources”) Previously Load Resources Have submitted these values as negative numbers to signify consumption ERCOT systems require that these be expressed as positive numbers ERCOT has temporarily changed this in the model Load Resources need to officially make this modification to their Load RARF ERCOT requires that each Load Resource be mapped to a physical TSP load ERCOT will compile information it has available and contact each registered Load Resource Entity to confirm and update their Load RARF http://nodal.ercot.com 20

What’s Next – Remaining MP-10 Activities This will be further detailed at a future WebEx Background MP-10 began in 2008 with initial validation of one-lines, gen site topology and mapping to EPS meter(s) and resource node(s) REs were sent MP-10 packages and asked to respond with required changes Early 2009, ERCOT executed changes and in some cases identified re-work required by REs September 2009 (Post SEM Go Live), REs will be asked to: Perform final verification on changes made by ERCOT <OR> Perform re-work so that ERCOT c ERCOT will ask for a final sign-off by the RE’s Authorized Representative. http://nodal.ercot.com 21

Next Steps – Updates and Communication ERCOT will be hosting a market call every 2 weeks Standing Agenda: Project Updates Production quality metric Common issues / Frequently Asked Questions Q&A These meetings will be our primary means of communication These meetings will continue to be posted to the Registration and Qualification calendar at http://www.ercot.com/committees/nodal/rq/ The next Registration Market Call will occur on Friday 9/11/09 All questions should be routed to nodalmarkettransition@ercot.com Questions sent directly to your Account Manager, should also copy nodalmarkettransition@ercot.com as well http://nodal.ercot.com 22

Q&A / Open Forum Q&A / OPEN FORUM http://nodal.ercot.com 23