Resource Entity Owned Transmission Asset Data Collection

1. Resource Entity Owned Transmission Asset Data Collection Kick Off Meeting Feb 27, 2009 http://nodal.ercot.com 1

2. 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. http://nodal.ercot.com 2

3. Agenda • Overview and Objective • Review Project Details • Review ERCOT Preparation Activities • Scope of Transmission Data to be Collected • Review Project Approach / Schedule • Review Artifacts (separate documents) • Sample Audit Report • RARF Guide • Transmission Asset Registration Forms (in RARF) • What is not included in this effort • Next Steps • Q&A / Open Forum http://nodal.ercot.com 3

4. Overview and Objective • Project Objective is to complete the transmission asset registrationprior to EDS activities in Feb 2010 • Today’s focus will primarily be on Private Use Networks • History of transmission data tabs • These are derived from 2 artifacts • TDF (Transmission Data Form) used in zonal and MP-10 • 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) • This effort has added some fields and clarified others • Review of the Transmission Data Forms to occur later in the presentation • Much of the data for these tabs have been provided by Resource Entities during other activities (such as MP-10), and will now be validated against ERCOT business rules once RE’s verify and fill in any gaps / errors on their audit reports http://nodal.ercot.com 4

5. Review Project Details -Review ERCOT Preparation Activities • ERCOT has completed and are finalizing the following items: • Update and re-write of transmission data sections in the RARF Guide • Each section will contain a short narrative regarding that section • Each section will contain 100% of all screening business rules that will be applied to each field in the RARF • ERCOT will also be working to make these modifications to the resource data sections in the guide as well. This will be completed at a later date. • Updated version will be posted by EOB 3/4/09 at the following URL:http://nodal.ercot.com/readiness/rq/documents/index.html • Update of the RARF Glossary • Added / modified sections to align with the RARF tabs and fields • New version will be posted by EOB 3/5/09 at the following URL:http://nodal.ercot.com/readiness/rq/documents/index.html • Develop audit reports for the transmission data tabs • In total we have defined and automated ~350 business rules • Audit report will use the same format as with the resource data collection http://nodal.ercot.com 5

6. Review Project Details - Review ERCOT Preparation Activities • ERCOT has completed and are finalizing the following items (continued) • Created a process for pre-populating all RARF with current transmission data in the current model • The process baselines the RARF with data from current model employed by Zonal(Note: Topology updates submitted through MP-10 have been installed into the zonal model. The zonal model is then used to “seed” nodal.) • The process then updates the baseline with any data submitted through the RARF form via the GSU Transformer and the Transmission Assets tabs from the previous rounds of RARF data collection • In short, ERCOT will provide all data we have on file to Resource Entities in a pre-populated RARF. • Created a process to load all RARF transmission data into the RARF Database • Common issues encountered during preliminary 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) http://nodal.ercot.com 6

7. Review Project Details – Scope of Transmission Data to be Collected • Scope of Transmission Data Assets (high level lists) • Lines • Breakers and Switches • Capacitors and Reactors • Transformers • Static Var Compensators • Series Devices • Loads • * PUN Load 168 hr Profiles • Out of Scope for this phase • Protection • SubSync • Planning * Note that updates Resource Data to resource data will be accepted during this period as well * Note that most PUN’s have turned in their PUN Load 168 hr Profiles. We will take this opportunity to correct any issues on these during this phase http://nodal.ercot.com 7

8. Review Project Details – Scope of Transmission Data to be Collected • Clarifying statements on which assets need to be registered / modeled Note: This is specific to PUN’s. Specifics on other resource entities will be addressed on a later call • All assets which are between a generator and the point of interconnect to ERCOT • All Load • Loads which are connected on a Bus greater than or equal to 60kV need to be modeled individually • Loads connected at less than 60kV may be aggregated into an “equivalent load” at the 69kV Bus • Auxiliary and Site Service Load may be combinedNote: Auxiliary load is defined as that which is only present when the generator is running • In some cases it will be necessary for ERCOT and the Private Network to review specific assets and/or sites to make a determination on whether or not it is required to be registered / modeled • These cases will be addressed during a WebEx coordinated by the RE’s Account Manager http://nodal.ercot.com 8

9. Review Process – Review Project Approach / Schedule • Receipt of the pre-populated RARF and the first Audit Report will mark the start of the project • The project will take the same approach as the collection of Resource Data in 2008 • We will use an iterative approach, employing 3 iterations • Iteration 1 – 85% production quality • Iteration 2 – 95% production quality • Iteration 3 – 98% production quality • Each iteration will begin with a formal audit report sent to each Resource Entity • We will continue to provide interim reports as corrections are made and RARF’s are resubmitted • Iteration 1 will also include the pre-populated RARF – this RARF must be used going forward for any/all updates • Resource Entity’s Account Manager will schedule a conference call in each iteration to review the audit report (unless all issues have been resolved) http://nodal.ercot.com 9

10. Review Process – Review Project Approach / Schedule • The project will take the same approach as the collection of Resource Data in 2008 (continued) • At the end of each iteration ERCOT will publish production quality metric • Note that production quality is defined as: • The RARF data can be loaded into the model and consumed by the applications by means of being screened with defined business rules • There will be cases where issues are found later during testing which may not have been possible to screen via the audit report process • Production quality will focus on Reliability Needs and does not guarantee optimal performance in the Real Time and Day Ahead Markets • Scorecard Nodal Readiness Metrics • ERCOT will detail the schedule of updates to readiness metrics and weekly status reporting at a future meeting http://nodal.ercot.com 10

11. Review Process – Review Project Approach / Schedule Registration Audit Process http://nodal.ercot.com 11

12. Review Process – Review Project Approach / Schedule • Project Schedule / Key Points • 3/5 Starts Iteration 1 with the Private Use networks • 4/2 is the final day to turn in PUN RARF’s for iteration 1 • First production quality metric will be published 4/6 when iteration 2 begins • ERCOT will hold a special session to communicate dates for non-PUN RE’s http://nodal.ercot.com 12

13. Review Artifacts • Artifacts to be reviewed (high level) • Sample Audit Report • RARF Guide • Transmission Asset Registration Forms (in RARF) • What is not included in this effort (out of scope forms) http://nodal.ercot.com 13

14. Next Steps • ERCOT will be hosting a market call every 2 weeks • Agenda: • Project Updates • Production quality metric • Common issues / Frequently Asked Questions • Q&A • In general, these meetings will be our primary means of communication • A Market Notice will be sent out when this meeting is added to the Registration and Qualification calendar on www.ercot.com • The first Market Meeting will occur on Friday 3/13/09 • Each PUN will receive their Pre-Populated RARF’s and Audit Report on Thursday 3/5/09 • Although ERCOT will focus on the PUN’s for this leg of the project, other RE’s may request to start earlier and receive a pre-populated RARF • Turn around time may be slower during this period • Electing to start earlier will provide more time to resolve issues • Account Managers will begin scheduling meetings the following week • 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 14

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