1. October 29, 2012 RARF Workshop 2 Introduction to ERCOT Modeling Process Jay Teixeira Manager, Model Administration

2. 2 RARF Workshop 2October 29, 2012 Purpose of Meeting The purpose of the meeting is to discuss data requirements that present and future Resource Entities (RE) have via the Resource Asset Registration Form (RARF) or Generation Interconnection Process (pre-RARF) Define specific data items required to be submitted by REs to make it consistent with Operations and Planning Model expectations Identify RARF data that REs are having problems submitting for various reasons Determine a path to resolve these data items so that ERCOT Models have the data needed to run studies

3. 3 RARF Workshop 2October 29, 2012 Why is data needed? The data being submitted in the RARF and pre-RARF are used directly in the Steady State and System Protection Planning Models –All data from POI down: Units Lines Transformers Reactive Devices Connectivity ERCOT assigns Connectivity Node Group nodes, bus numbers and bus names, and zones –Future Unit data is from pre-RARF or previous Generation Interconnection data sheet Some are not complete and some contain questionable data Contact Information not valid

4. 4 RARF Workshop 2October 29, 2012 Generation Interconnection to Planning Model

5. 5 RARF Workshop 2October 29, 2012 Existing Generation to Planning Model

6. 6 RARF Guide for Generation Interconnections - Generation RARF Workshop 2October 29, 2012

7. 7 RARF Guide for Generation Interconnections - Transmission RARF Workshop 2October 29, 2012

8. 8 RARF Workshop 2October 29, 2012 3.7Resource Parameters (6)The QSE or Resource Entity must update any Resource Parameter for a specific Resource: (a)Within ten Business Days of completion of a Net Dependable Capability test to reflect the results of the test; (b)Within ten Business Days of completion of a reactive capability test to reflect the results of the test; (c)Within ten Business Days of a request by ERCOT to check or update a specific Resource Parameter; and (d)Within ten Business Days of a known change to any Resource Parameter. Protocol 3.7 Resource Parameters

9. 9 RARF Workshop 2October 29, 2012 5.1System Modeling Information Information on existing and future ERCOT System components and topology is necessary for ERCOT to create databases and perform tests as outlined in these criteria. To ensure that such information is made available to ERCOT, the following actions by Market Participants are required: (c)Each Generation Resource, or its Designated Agent, shall provide accurate modeling information for each existing or proposed Generation Resource meeting the criteria for inclusion in the SSWG, DWG, and SPWG base cases for which it is the majority owner. The information provided shall include, but not be limited to, the following: (i)Information necessary to represent the Generation Resource’s generation and interconnection facilities in any model of the ERCOT System whose creation has been approved by ERCOT, including modeling information detailed in procedures of the SSWG, DWG, and SPWG; and (ii)Identification of a designated contact person responsible for providing answers to questions ERCOT may have regarding the information provided. (d)Typical or representative information may be provided for planned facility additions or modifications for use in the SSWG, DWG, and SPWG base cases, but such information shall be revised using actual design or construction information in accordance with the time line for Network Operations Model changes outlined in Protocol Section 3.10.1, Time Line for Network Operations Model Changes. Operating Guide System Modeling Information

10. 10 RARF Workshop 2October 29, 2012 Protocol Section 3.10.1 Deadline to Submit Information to ERCOT Note 1 Model Complete and Available for Test Note 2 Updated Network Operations Model Testing Complete Note 3 Paragraph (5) Update Network Operations Model Production Environment Target Physical Equipment included in Production Model Note 4 Jan 1Feb 15March 15April 1Month of April Feb 1March 15April 15May 1Month of May March 1April 15May 15June 1Month of June April 1May 15June 15July 1Month of July May 1June 15July 15August 1Month of August June 1July 15August 15September 1Month of September July 1August 15September 15October 1Month of October August 1September 15October 15November 1Month of November September 1October 15November 15December 1Month of December October 1November 15December 15January 1Month of January (the next year) November 1December 15January 15February 1Month of February (the next year) December 1January 15February 15March 1Month of March (the next year) 3.10.1Time Line for Network Operations Model Changes (2) For a facility addition, revision, or deletion to be included in any Network Operations Model update, all technical modeling information must be submitted to ERCOT pursuant to the ERCOT NOMCR process or the applicable Resource asset registration process for Resource Entities. (3)TSPs and Resource Entities shall submit Network Operations Model updates at least three months prior to the physical equipment change. ERCOT shall update the Network Operations Model according to the following table:

11. 11 RARF Workshop 2October 29, 2012 5.7Interconnection Data, Fees, and Timetables 5.7.1Generation Resource Data Requirements (1)The Interconnecting Entity (IE) shall submit with its Generation Interconnection or Change Request (GINR) the most current actual facility information (generation, substation, and transmission/subtransmission if applicable) or best available expected performance data for the physical and electrical characteristics of all proposed facilities (in sufficient detail to provide a basis for modeling) up to the Point of Interconnection (POI) with a Transmission Service Provider (TSP). (2)Failure to supply the required data may delay ERCOT processing of the interconnection application and studies. Recommendations resulting from these studies that are based on outdated, false, or bad data may adversely affect the safety and reliability of the ERCOT System and can result in damage to generation or transmission equipment. The IE and subsequently, the Resource Entity associated with any approved Generation Resource, must promptly submit any updates to ERCOT to ensure the long- term adequacy, reliability, and safety of the ERCOT System, as required by the Protocols, this Planning Guide, the Operating Guides, and North American Electric Reliability Corporation (NERC) Reliability Standards. Failure to comply may result in financial penalties. Planning Guide Generation Resource Data Requirements

12. 12 RARF Workshop 2October 29, 2012 MOD-010-0 Requirement R1 (MOD-012-0 for Dynamic Data Similar) The Transmission Owners, Transmission Planners Generator Owners, and Resource Planners (specified in the data requirements and reporting procedures of MOD-011-0_R1) shall provide appropriate equipment characteristics, system data, and existing and future Interchange Schedules in compliance with its respective Interconnection Regional steady-state modeling and simulation data requirements and reporting procedures as defined in Reliability Standard MOD-011-0_R1. MOD-011-0 Requirement R1 (MOD-013-1 for Dynamic Data Similar) The Regional Reliability Organizations within an Interconnection, in conjunction with the Transmission Owners, Transmission Planners, Generator Owners, and Resource Planners, shall develop comprehensive steady-state data requirements and reporting procedures needed to model and analyze the steady-state conditions for each of the NERC Interconnections: Eastern, Western, and ERCOT. Within an Interconnection, the Regional Reliability Organizations shall jointly coordinate the development of the data requirements and reporting procedures for that Interconnection. The Interconnection-wide requirements shall include the following steady-state data requirements: NERC Reliability Standards Requirements

13. Questions? October 29, 2012RARF Workshop 2