ERCOT Planning Go-Live Introduction and Background

1. ERCOT Planning Go-Live Introduction and Background Jay Teixeira Manager, Model Administration Nodal Planning Go-Live Workshop

2. ERCOT Concerns regarding Planning Go-Live • Topology Processor is in production for CRR • Data, such as connectivity node groups (CNG) must be maintained by ERCOT and TSPs • Equipment IDs and Circuit IDs for all equipment must be populated and unique and are dependent on correct CNG definition • Easier to maintain one model than two Nodal Planning Go-Live Workshop

3. Reasons to Go Live in April 2010 • Date to start building Data Set A cases which are heavily used by ERCOT • Near Term congestion analysis and studies to support ERCOT Operations (SPS, RMR, etc) • Studies simulate planned outages, manual process to map to SSWG cases • Protocols require consistency in all operational models • Value to both ERCOT and Market Participants in moving to a process that satisfies the consistency requirements Nodal Planning Go-Live Workshop

4. Data Set A Uses from June PLWG meeting Nodal Planning Go-Live Workshop

5. Current Process – Separate System for Planning ERCOT/TSP Network Model update via NOMCR NMMS db Case Posted ERCOT Topology Processor for ODMS CRR Top Output Yes TSPs submit RAWD files for their area containing Topology, Load, Voltage Control Case complete? No TSPs submit Changes via IDEV, other ERCOT Dispatch ERCOT Manual Process Planning Case Creation TSP Review Nodal Planning Go-Live Workshop

6. Topology Processor/Model on Demand Integrated System ERCOT/TSP Network Model update via NOMCR NMMS db Case Posted ERCOT Topology Processor for ODMS CRR Topology Output ERCOT Dispatch Profile Yes TSP Profiles Case complete? No TSPs submit Change via MOD Planning Topology Output TSP Standard PMCR ERCOT Model on Demand TSP Review TSP Future PMCR Planning Case Output Nodal Planning Go-Live Workshop

7. Nodal Planning Go-Live Workshop

8. Notes for Previous Slide • AEP 133 added load records appears to separate load into Residential, Wholesale, etc to match SSWG case. Do not get removed by SCR. • LCRA 383 load adds and 324 load deletes appears to be to realign Load ID field to new modeling philosophy. Will be changed in IMM and not necessary to submit as future PMCR • ERCOT is reviewing all “Standard PMCR’s” • Some may be reduced by making changes in IMM • Up to 230 have been found • Some may be just for comparison purposes • May be why changes to IMM were not made Nodal Planning Go-Live Workshop

9. What are PMCR’s? • PMCR’s are not the same as NOMCR’s • NOMCR’s are very detailed xml files • PMCR’s vary from 1 line of data to up to 4 lines of data Nodal Planning Go-Live Workshop

10. Example of PMCR File • <PROJECT>, 30 • AEN_TEST_CASE_10SUM_PMCR_FILE,Standard_PMCR,Active,Make sure Autos are 3-winding • <PHASE>,TEST_PMCR,10/8/2010,10/8/2010, • BUS, DELETE,9281,'TRADPOST1',138,1,0,0,9,709,1,0,190 • BUS, ADD,9025,'HP_STATC',32,1,0,0,9,709,0.9986,-3.2377,100 • LOAD, DELETE,9187,'1',1,9,709,2,0,0,0,0,0,190 • LOAD, ADD,9184,'DG',1,9,709,-2.12,0.597,0,0,0,0,400 • LOAD, MODIFY,9282,'1',1,9,709,20.324,14.287,0,0,0,0,190 • GENERATOR, DELETE,9118,'VC',0,0,110,-80,1.018,0,110,0,9999,0,0,0,1,100,0,0,1,1 • BRANCH, DELETE,7288,-9288,'BC',0,0.0001,0,9999,9999,9999,0,0,0,0,1,0,1,1 • FACTS, ADD,1,9025,0,1,0,0,0.9986,100,9999,0.9,1.1,1.2,100,0.05,100,100,0,0,0 • TRANSFORMER, ADD,9025,9118,0,'1',1,1,1,0,0,1,'STATC1',1,190,1,,,,,, • 0.0025,0.08,100,,,,,,,, • 1,0,-30,120,120,120,0,0,1.5,0.51,1.5,0.51,33,0,0,0 • 1,0,,,,,,,,,,,,,, • TRANSFORMER, MODIFY,9002,9188,0,'1',1,1,1,0,0,2,,1,189,1,,,,,, • 0.00521,0.18106,100,,,,,,,, • 1,13.8,0,139,139,139,0,0,1,1,1.1,0.9,33,0,0,0 • 1,0,,,,,,,,,,,,,, • Q This file contains 10 PMCRS Nodal Planning Go-Live Workshop

11. The effect of SCRs on the number of PMCR’s submitted Nodal Planning Go-Live Workshop

12. TAC Approved Principles of Consistency • Consensus version developed by Joint ROS/TPTF on August 4, 2006 • Approved by TPTF on August 7, 2006 • Approved by ROS on August 11, 2006 • Entitled “Principles of Consistency” applies to: • Annual Planning Models • CRR Network Models • Network Operations Models Nodal Planning Go-Live Workshop

13. TAC Approved Principles of Consistency • Purpose to provide principles to define the term “consistent” as used in sections 3.10 and 3.11 of ERCOT Protocols to describe relationships between the models to which it applies • “The name of existing Transmission Elements including Electrical Buses, lines, transformers, generators, loads, breakers, switches, capacitors, reactors, phase shifters, or other similar devices, if modeled as part of the ERCOT Transmission Grid, must be identical (Protocols Section 3.10 Network Operations Modeling and Telemetry)” Nodal Planning Go-Live Workshop

14. CRR Names use Topology Process Bus Numbers and Names Non-Thermal Constraints Contingencies Monitored Lines and Transformers Nodal Planning Go-Live Workshop

15. TAC Approved Principles of Consistency • “All existing transmission line’s and transformer’s impedances (or equivalent branch circuit impedance) and ratings (Normal, Emergency and 15-Minute, if modeled) shall be identical for equipment without Dynamic Ratings and for equipment with Dynamic Ratings having the same assumed ambient weather conditions, and shall use Dynamic Ratings where implemented according to the nodal protocols ("Identical" as used herein permits only those differences due to the use of different numerical precision)” Nodal Planning Go-Live Workshop

16. TAC Approved Principles of Consistency • “If all normally closed breakers and switches are closed and normally open breakers and switches are open in the CRR Network and Network Operations Model, the calculated line flows between substations in the Annual Planning Model shall be consistent (very close), when all models use the same load magnitude and distribution, generation commitment and dispatch, and voltage profile” Nodal Planning Go-Live Workshop

17. SCR760 Preliminary Impact Analysis Nodal Planning Go-Live Workshop

18. Delivery Plan Nodal Planning Go-Live Workshop

19. Questions? Nodal Planning Go-Live Workshop