1. QSE/RE Transmission Facilities Outage Coordination Workshop

2. Protocol Disclaimer This presentation provides a general overview of the Texas Nodal Market Implementation and is not intended to be a substitute for the ERCOT Nodal Protocols, as amended from time to time. If any conflict exists between this presentation and the ERCOT Nodal Protocols, the ERCOT Nodal Protocols shall control in all respects. For more information, please visit: http://ercot.com 2

3. 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 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. 3

4. This course is intended for: QSEs and REs who submit Resource Entity-Owned Transmission Facility outages TSPs, ERCOT Outage Coordinators and outage coordination support personnel Target Audience 4

5. Course Topics The following topics will be discussed: NPRR 219 Requirements Protocol Definitions Resource Entity-owned Transmission Facility examples Protocol Requirements for Transmission Facility Outages Resource Entity-owned Transmission Facilities Outage process Protocol Requirements for Adding & Removing Facilities Resource Entity Adding Equipment scenario 5

6. Outage Scheduler Training Material Training material pertaining to the Outage Scheduler may currently be found at: http://nodal.ercot.com/training/index.html http://nodal.ercot.com/readiness/markettrials/os/index.html Web-based training modules are also available on the ERCOT Learning Management System 6

7. NPRR 219 Requirements

8. In accordance with Nodal Protocol Revision 219 ERCOT will submit information into the Nodal Outage Scheduler for Resources who own Transmission Facilities and are unable to submit this information into the ERCOT Outage Scheduler. This workshop addresses the Protocol requirements and the process which ERCOT will implement for collecting information and performing this task upon Nodal go-live December 1, 2010. 8

9. RE requirement to designate a Responsible Entity Each Resource Entity is to submit a Notice of Change of Information (NCI) specifying who will responsible for submitting outages on their behalf (designating ERCOT or a TSP). If a RE designates a specific TSP, the NCI Contact Type block is completed with the TSP Single Point of Contact. When the RE designates a TSP, the RE is required to acknowledge to ERCOT either: A signed letter from the TSPs Authorized representative or An email from the TSP Authorized representative acknowledging the TSPs obligation. If a RE confirms ERCOT as the Resource Transmission Facility Outage Coordination point of contact, the contact block does not need to be completed. 9

10. Protocol Definitions

11. Outage The condition of a Transmission Facility or Generation Resource that is: part of the ERCOT Transmission Grid defined in the Network Operations Model has been removed from its normal service excludes the operations of Transmission Facilities associated with the start-up and shutdown of Generation Resources. 11

12. Protocol Definitions Transmission Element A physical Transmission Facility that is either an Electrical Bus, line, transformer, generator, Load, breaker, switch, capacitor, reactor, phase shifter, or other similar device that is part of the ERCOT Transmission Grid and defined in the ERCOT Network Operations Model. Transmission Facilities (1) Power lines, substations, and associated facilities, operated at 60 kV or above, including radial lines operated at or above 60 kV; (2) Substation facilities on the high voltage side of the transformer, in a substation where power is transformed from a voltage higher than 60 kV to a voltage lower than 60 kV or is transformed from a voltage lower than 60 kV to a voltage higher than 60 kV 12

13. Resource Entity-Owned Transmission Facility Discussion

14. Ownership vs. Operatorship Ownership Physical ownership of equipment. There can be more than one owner. Owners may submit model change requests. 14

15. Ownership vs. Operatorship Operatorship The entity responsible for physical operation of the equipment. There can be more than one operator. Operators may also submit model change requests. REs and PUNs must identify the connecting TSP in their RARFs. Currently, only TSP Operators can submit Transmission Facility requests in the Outage Scheduler 15

16. 16 Plant Load

17. 17 TSP Owned

18. 18 TSP Owned

19. 19 TSP Owned

20. 20 TSP Owned

21. 21 TSP Owned

22. Protocol Requirements

23. Protocol 3.1.4.3 Reporting for Planned Outages and Maintenance Outages of Resource and Transmission Facilities Each Resource Entity and TSP shall submit information regarding proposed Planned Outages and Maintenance Outages of Transmission Facilities or Generation Resources under procedures adopted by ERCOT. The obligation to submit that information applies to each Resource Entity that is responsible to operate or maintain a Generation Resource that is part of or that affects the ERCOT System. The obligation to submit that information applies to each TSP or Resource Entity that is responsible to operate or maintain Transmission Facilities that are part of or affect the ERCOT System. 23

24. Protocol 3.1.5.1 ERCOT Evaluation of Planned Outage and Maintenance Outage of Transmission Facilities TSPs and Resource Entities shall request a Planned Outage or Maintenance Outage for their respective Transmission Facilities (i.e. Transmission Facilities owned by such Entities) that are part of the ERCOT Transmission Grid and defined in the Network Operations Model. For Resource Entities within a Private Use Network, this only includes Transmission Facilities at the Point of Interconnection (POI). 24

25. Protocol 3.1.5.1 ERCOT Evaluation of Planned Outage and Maintenance Outage of Transmission Facilities Specifically, such requests shall be made when a relevant Transmission Facility will be removed from its normal service. For TSP requests, the TSPs shall enter such requests in the Outage Scheduler. For Resource Entity requests, ERCOT* shall enter such requests in the Outage Scheduler on behalf of the Resource Entity. * or a designated TSP 25

26. Protocol 3.1.5.1 ERCOT Evaluation of Planned Outage and Maintenance Outage of Transmission Facilities ERCOT’s obligation to enter outage requests for Resource Entities is valid only for the purposes of Transmission Facilities Outage Scheduler entry requirements prescribed by the ERCOT Protocols and Operating Guides. ERCOT’s obligations hereunder do not create any legal obligation or responsibility related to any other legal obligations applicable to a Resource Entity. ERCOT’s obligation shall terminate upon the implementation of system changes that enable Resource Entities to perform this function. 26

27. Protocol 3.1.5.1 ERCOT Evaluation of Planned Outage and Maintenance Outage of Transmission Facilities ERCOT is not deemed to have approved the Outage Schedule associated with the Planned Outage or Maintenance Outage until ERCOT notifies the TSP or Resource Entity of its approval under procedures adopted by ERCOT. Once ERCOT posts a Resource Entity Transmission Facility Outage request on the MIS Secure Area, the Resource Entity shall review the submitted Outage for accuracy and request that ERCOT submit modifications if necessary. 27

28. Resource Entity-Owned Transmission Facility Outage Process

29. NPRR 219 Requirements In accordance with Nodal Protocol Revision 219 ERCOT will submit information into the Nodal Outage Scheduler for Resources who own Transmission Facilities and are unable to submit this information into the ERCOT Outage Scheduler. The following process has been developed by ERCOT for collecting information and performing this task upon Nodal go-live December 1, 2010. 29

30. RE-Owned Transmission Facility Process Each Resource Entity that owns Transmission Elements, that is part of the ERCOT Transmission Grid and defined in the Network Operations Model that has been removed from its normal service, excluding the operation of Transmission Facilities associated with the start-up and shutdown of Generation Resources, must submit Planned, Maintenance and Forced outage schedules for ERCOT approval. Note: the following process does not apply to QSEs/REs with a designated TSP. The designated TSP shall be the responsible entity. 30

31. RE-Owned Transmission Facilities QSEs/REs must coordinate activities with ERCOT or a designated TSP who will enter outages for these facilities. 31

32. RE-Owned Transmission Facility Process 1. The Resource Entity shall coordinate Transmission Facility outage request with its designated single point of contact (QSE) in accordance with Nodal Protocol 3.1.4.1 Single Point of Contact. 32

33. RE-Owned Transmission Facility Process 2. The Resources Entity’s QSE shall submit outage information to ERCOT staff by email using the “Trans Planned-Maintenance Outage Request Form” or the “Transmission Forced Outage Request Form” depending on the type of outage being requested. The “Trans Planned-Maintenance Outage Request Form” and the “Transmission Forced Outage Request Form” are available on ERCOT.com at http://www.ercot.com/gridinfo/transmission/index. http://www.ercot.com/gridinfo/transmission/index This information should be emailed to ResTranOutages@ercot.com.ResTranOutages@ercot.com 33

34. Outage Request Forms on ERCOT.Com 34

35. QSE/RE Planned Outages for Resources Submittal Timelines for Resource Planned Outages If QSE submits outage request… ERCOT will approve or reject… 1-2 days priorWithin 8 business hours of receipt* 3-8 days prior Before 1800 hours, two days prior to start of proposed Outage 8+ days prior Must accept, but may discuss reliability and scheduling impacts to minimize hazards/costs * Eight Hour Business Rule Applies

36. TSP/Transmission Facilities Planned Outages Submittal Timelines for Planned Outages If TSP submits outage request… ERCOT will approve or reject… 91+ days*75 days* 46–90 days*30 days* 9–45 days*4 days* 4–8 days*No later than 1800 hours 3 days* 3 days*No later than 1800 hours 2 days* *Prior to Planned Start Date/Time

37. QSE & TSP Maintenance Outages Initiated manually to remove equipment from service to perform work on components Required to prevent a potential forced outage Could be postponed briefly Cannot be postponed until next planned outage Outage Levels Equipment must be removed from service… 1Within 24 hours 2Within 2 – 7 days 3Within 8 – 30 days.

38. QSE Communication If Maintenance Outage occurs: QSE must update Current Operating Plans Verbal communication with ERCOT may be necessary Maintenance Outage

39. Planned and Maintenance Submittal Form 39 Replicates TSP Planned and Maintenance Outage Scheduler submittal format

40. QSE & TSP Forced Outages Initiated by protective relay (or manually) In response to equipment that could lead to a potential event, or poses threat to people, equipment, or public safety Notification RequirementsERCOT Action Verbally communicate outage immediately. Submit into Outage Scheduler as soon as practicable. QSEs must update COP. Default Accept status automatically assigned when submitted.

41. Forced Outage Request Form 41 Replicates TSP Forced Outage Scheduler submittal format

42. RE-Owned Transmission Facility Process 3. The QSE shall confirm receipt [1] and review the Outage request by calling ERCOT Outage Coordination at (512) 248-6842 during normal business hours and calling the ERCOT Shift Engineer at (512) 248-6354 during non-business hours. [1] Phone Confirmation for Forced and Level 1 Maintenance Outage schedules is required. [1]All emails of the “Resource Transmission Outage Request forms” should be verified by a phone call from the QSE to ERCOT. 42

43. RE-Owned Transmission Facility Process 4. ERCOT staff [2] shall enter such requests in the Outage Scheduler on behalf of the Resource Entity as submitted by the QSE. [2] [2]ERCOT shall act as the responsible Entity that will manage Outage Scheduler entries for Transmission Elements owned by the Resource. This excludes entries of Resources since the Resource Entities QSE has sufficient roles and permission to submit outages for Resources that is acts as the designated point of contact for and can submit the Resource outages into the ERCOT outage scheduler. ERCOT’s obligations in regard to submitting Transmission Outages for the Resources Entity and QSE shall terminate upon the implementation of Outage Scheduler system changes and protocol changes that enable Resource Entity QSEs to enter Outages of Transmission Facilities in the Outage Scheduler. 43

44. RE-Owned Transmission Facility Process 5. The Resource Entity shall: Monitor the outage information on the ERCOT MIS Ensure that the correct information was entered by ERCOT Monitor the progression status and identify if the schedule is “Approved” or “Rejected”. https://mis.ercot.com/pps/tibco/mis/Pages/Grid+Information/Transmission Digital Certificate is required 44

45. Market Information System – Accessing Outage Information 45

46. Market Information System – Accessing Outage Information 46

47. Market Information System – Accessing Outage Information 47

48. Market Information System – Accessing Outages 48 Updated files are loaded just after the top of each hour. QSE/RE needs to validate entries submitted into the Outage Scheduler during the previous hour (following format also applies to Proposed and Rejected Outages)

49. Market Information System – Accessing Outages 49

50. MIS – Proposed Outages in.csv format Contains all outages in “Received at ERCOT” (RatE) or Study mode. May use Find, Filters and Data Sorts, etc. to locate outages 50

51. MIS – Proposed Outages in.csv format Displays outages in “Received at ERCOT” (RatE) or Study mode. May use Find, Filters and Data Sorts, etc. to locate outages 51

52. Market Information System – Accessing Outage Information 52

53. Market Information System – Accessing Outages 53 Updated files are loaded just after the top of each hour. Depending on the submittal time and the Planned Start of the Outage, it may be several hours or days before Approval or Rejection is posted

54. MIS – Approved & Accepted Outages in.csv format Displays all active and future Outages. May use Find, Filters and Data Sorts, etc. to locate outages 54

55. Market Information System – Accessing Outage Information 55

56. 56 MIS – Rejected Outages in.csv format Lists Rejected outages May use Find, Filters and Data Sorts, etc. to locate outages

57. RE-Owned Transmission Facility Process 6. If the Resource Entity identifies an error has been made: Resource Entity shall resubmit the correct outage information to their QSE QSE shall resubmit the “Trans Planned-Maintenance Outage Request Form” or the “Transmission Forced Outage Request Form” to ERCOT The Outage ID should be included on the resubmittal 57

58. RE-Owned Transmission Facility Process 6. (Continued): QSE will confirm receipt and review the Outage modifications with ERCOT Outage Coordination by calling (512) 248-6842 during normal business hours and calling the ERCOT Shift Engineer at (512) 248-6354 during non-business hours. Phone Confirmation for Forced and Level 1 Maintenance Outage schedules is required. 58

59. RE-Owned Transmission Facility Process 7. If circumstances prevent adherence to these timetables: ERCOT shall discuss the request status and reason for the delay of the approval with the requesting QSE ERCOT will make reasonable attempts to mitigate the effect of the delay on the Resource Entity. 59

60. RE-Owned Transmission Facility Process 8. If the outage is to be “Rejected”: ERCOT staff will contact the QSE by phone and/or email. ERCOT staff will work with the Resource Entity via their QSE for a solution. If no solution can be reached, the ERCOT staff will notify the QSE by phone and by email that the outage was “Rejected” The message shall identify the contingency and the overloaded element, other known issues and solutions. 60

61. RE-Owned Transmission Facility Process 9. For Planned and Maintenance Outages, if the outage is “Approved” and the outage starts: QSE will continue to email ERCOT updated forms to capture the “Actual Start” and “Actual End” times of the Outage. New Planned End times must be submitted before the previously approved Planned End. Phone confirmation is required for New Planned End submittals. The Outage ID should be included on the updated forms. The ERCOT staff will enter all of the updates into the Outage Scheduler. 61

62. Planned and Maintenance Submittal Form 62 Replicates TSP Planned and Maintenance Outage Scheduler submittal format

63. RE-Owned Transmission Facility Process 9. (Continued) For Forced Outages QSE will continue to email ERCOT updated forms to capture the “Actual End” times of the Forced Outage. New Planned End times must be submitted before the previously accepted Planned End. Phone confirmation is required for New Planned End submittals. The Outage ID should be included on the updated forms. The ERCOT staff will enter all of the updates into the Outage Scheduler. 63

64. Forced Outage Request Form 64 Replicates TSP Forced Outage Scheduler submittal format

65. RE-Owned Transmission Facility Process 10. If an outage cannot be performed during the approved time frame: Resource Entity will submit an updated form to their QSE who will provide this information to ERCOT. The Outage ID should be included on the resubmittal ERCOT will enter the information into the Outage Scheduler. Resource Entity should monitor ERCOT’s entries to ensure the correct data has been entered by ERCOT. 65

66. RE-Owned Transmission Facility Process 10. (Continued) If corrections are required then the Resource Entity should resubmit the correct outage information to their QSE and the QSE shall resubmit the correction and confirm receipt QSE will review the Outage modifications by calling ERCOT Outage Coordination at (512) 248-6842 during normal business hours and calling the ERCOT Shift Engineer at (512) 248-6354 during non- business hours. Phone Confirmation for Forced and Level 1 Maintenance Outage schedules is required. 66

67. 67

68. Adding or Removing Transmission Facilities Protocol Section 3.3.2.1

69. 3.3.2.1 Information to Be Provided to ERCOT The energization or removal of a Transmission Facility or Generation Resource in the Network Operations Model requires an entry into the Outage Scheduler by a TSP or Resource Entity. The Resource Entity shall make entries in the Outage Scheduler for Outages of new or relocated Generation Resources. ERCOT * shall submit entries into the Outage Scheduler on behalf of the Resource Entity, for any energization or removal of Transmission Facilities owned by the Resource Entity. * or the designated TSP 69

70. 3.3.2.1 Information to Be Provided to ERCOT Once ERCOT posts a Resource Entity Transmission Facility Outage request on the MIS Secure Area, the Resource Entity shall review the submitted Outage for accuracy of information and request that ERCOT submit modifications if necessary. If any changes in system topology or telemetry are expected, then the TSP or Resource Entity shall notify ERCOT in accordance with the schedule in Section 3.3.1, ERCOT Approval of New or Relocated Facilities. 70

71. 3.3.1 ERCOT Approval of New or Relocated Facilities Before energizing and placing into service any new or relocated facility connected to the ERCOT Transmission Grid, a TSP, QSE, or Resource Entity shall enter appropriate information in the Outage Scheduler and coordinate with, and receive written notice of approval from, ERCOT. 71

72. Outage Scheduling Requirements As per Protocol section 3.3.1, Planned Outages must be input by TSPs and QSEs to the ERCOT Outage Scheduler to account for gaps between: Model-ready and field-energization dates for equipment additions, upgrades, relocations, etc. Field-retirement and model-retirement dates for equipment being retired or permanently removed. 72

73. 3.10.1 Time Line for Network Operations Model Changes (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: 73

74. 74 Deadline to Submit Information to ERCOT Model Complete and Available for Test Updated Network Operations Model Testing Complete Update Network Operations Model Production Environment Target Physical Equipment In- Service Month 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)

75. Both are used to submit network model change requests NOMCR vs. RARF 75

76. RARF to NOMCR Conversion REs must provide adequate cushion to account for validation and conversion to NOMCR by ERCOT RE may be asked to revise and resubmit if model validation fails after successful conversion to NOMCR May become an Interim Update if model submittal deadline has passed. REs must still observe Protocol 3.14.1.1 Notification of Suspension of Operations when removing a Resource from operation. 76

77. Resource Entity adding a Combustion Turbine Scenario

78. RE Adding a new Combustion Turbine B4B5B6 B1B2B3 TSP Owned CD02 SD01 Resource RARF Submittal L01 L02 L03 L04 S010S020S030 S040 C 200 S 100 CT02 ST01 XT02 XT01 MT02 MT01 CD03 C 300 CT03 MT03 New Combustion Turbine Train 78

79. RE adding a Combustion Turbine to an existing facility A RE plans to add a new combustion turbine CT03 to an existing facility Planned energization date for CD03 and MT03 is Friday, April 15 th at 1400 hours New CT03 will synchronize to the grid for start-up testing on Wednesday, April 20 th at 0800

80. 80 In advance of Equipment Energization Market ParticipantsERCOT At least 4+ months Establish in-service/energization date for new equipment Check Model Change Schedule to establish:  Minimum RARF submittal date - required at least 3 months prior to in-service month. Recommend submitting 3+ weeks prior to 1 st of month deadline to allow for conversion to NOMCR, corrections, revisions, etc.  Desired Model Ready Date – recommend selecting a model load date at least 2 model loads prior to energization for schedule flexibility and to facilitate the Approval to Energize process. At least 90+ days Submit RARF using the minimum submittal and Model Ready dates determined above 7 days after NOMCR creation New equipment will be added to the Outage Scheduler Equipment Names list 91+ down to 46 days in advance of the equipment energization date Submit Outage Requests.  Planned Start will always be 0000 hours on the Model Ready Date  Planned End will be the desired energization date and time  Applies to Resource and Transmission Facility submittals 7 days prior Begin the Approval to Energize pre-check On the Model Ready date Prior to 0030 Hours  Submit actual Start for new equipment just loaded into the Network Operations Model At 0000 Hours  Load updated Network Operations Model On the Equipment Energization date Contact ERCOT Real Time Shift Supervisor for final Approval to Energize. After equipment is energized  Submit Actual End times NMMS OS Timeline for Adding Resource Facilities - Sequence of Events

81. 81 Network Operations Model Change Schedule on ERCOT.Com

82. 82 Network Operations Model Change Schedule on ERCOT.Com

83. MIS – Accessing Network Operations Model Change Schedule To be added: Network Operations Model Change Schedule 83

84. 84 Network Operations Model Change Schedule

85. 85 For the Red-flagged months: Equipment being energized on the 1 st and/or 2 nd day of these months must meet the submittal deadline for the previous week.

86. 86 Sample Model-ready dates from the posted Network Operations Model Change Schedule In-Service Month Model Deadline Market Validation Final Tests Scheduled Loads Supplemental Loads APRJan 1Feb 15Mar 15Apr 1 Apr 6 Apr 12 Apr 20 MAYFeb 1Mar 15Apr 15May 2 May 9 May 16 May 23 April 15th

87. 4/6/2011 Model-ready dates only (includes Supplemental database loads) from the Nodal DB Column Important Note: NOMCR Energization Date = a Model-ready Date!

88. Outage Submission Timeline New equipment names will be available in Outage Scheduler equipment list 7 days after NOMCR submittal Outage requests submitted…* ERCOT will approve or reject…* 91+ days75 days 46–90 days30 days *Prior to Planned Start Date/Time 88

89. RE Adding a new Combustion Turbine B4B5B6 B1B2B3 TSP Owned CD02 SD01 Normal Energization – 2 Steps L01 L02 L03 L04 S010S020S030 S040 C 200 S 100 CT02 ST01 XT02 XT01 MT02 MT01 CD03 C 300 CT03 MT03 Step 1 Step 2 89

90. RE Adding a new Combustion Turbine B4B5B6 B1B2B3 TSP Owned CD02 SD01 L01 L02 L03 L04 S010S020S030 S040 C 200 S 100 CT02 ST01 XT02 XT01 MT02 MT01 CD03 C 300 CT03 MT03 Transmission Facilities Resource 90

91. Energization Date for New CD03 & MT03 Jan Mar Apr May Feb 12 21 28 Model Load Model Load Model Load Model Load Model Load 15 6 Outages for CD03 & MT03 Outages in the Outage Scheduler Outage for C300 7 RARF to NOMCR Model-ready date for CD03, MT03, C300 & CT03 Model Load Startup date for CT03 Outage for CT03 QSE T Fac 20 RE Adding a new Combustion Turbine

92. 92 Interval begins at 00:00 hours on the Model-ready date and ends at 23:59 on the day prior to the next model-ready date. For example: Using the April 6th Model-ready date – the interval begins at 00:00 hours on April 6 th and ends at 23:59 on April 11 th (one minute prior to the next Model-ready date)

93. RequestorEquipmentOutage Scheduler Planned Start Outage Scheduler Planned End T FacCD03April 0600:00 T FacMT03April 0600:00 T FacC300April 0600:00 QSECT03April 0600:00 CD03 C 300 CT03 MT03 April 15thApril 20th Model-ready April 6 th at 00:00 Planned Energization Dates

94. RequestorEquipmentOutage Scheduler Planned Start Outage Scheduler Planned End T FacCD03April 0600:00April 1514:00 T FacMT03April 0600:00April 1514:00 T FacC300April 0600:00 QSECT03April 0600:00 CD03 C 300 CT03 MT03 April 15thApril 20th Planned Energization Dates

95. RequestorEquipmentOutage Scheduler Planned Start Outage Scheduler Planned End T FacCD03April 0600:00April 1514:00 T FacMT03April 0600:00April 1514:00 T FacC300April 0600:00April 2008:00 QSECT03April 0600:00April 2008:00 CD03 C 300 CT03 MT03 April 15thApril 20th Planned Energization Dates

96. Desired Energization Date & Time Model-ready Date @ 00:00 RE-Owned Transmission Facility outage request

97. Desired Energization Date & Time Model-ready Date @ 00:00 RE-Owned Transmission Facility outage request

98. RE submitted outage on the new Combustion Turbine 98 Model-ready Date @ 00:00 Desired Energization Date & Time Must enter Zero’s for Off-line status

99. Energization Date for New CD03 & MT03 Jan Mar Apr May Feb 12 21 28 Model Load Model Load Model Load Model Load Model Load 15 6 Outages for CD03 & MT03 Outages in the Outage Scheduler Outage for C300 A2E 7 RARF to NOMCR Model-ready date for CD03, MT03, C300 & CT03 Model Load Startup date for CT03 Outage for CT03 QSE T Fac 20 RE Adding a new Combustion Turbine Approval to Energize process begins 7 days prior to transmission facilities energization

100. Approval to Energize NMMS/OS Coordination

101. Slide 101 Approval to Energize Process What is Approval to Energize? Last step to ensure all aspects of equipment have been accurately and consistently incorporated into all ERCOT Network Models Outages Ratings Characteristics Connectivity Telemetry mapping

102. Required prior to energization for: Newly installed, removed or relocated facilities Upgraded or revised ratings Slide 102 Approval to Energize Process ERCOT requires at least 7 calendar days prior to energization to complete the process and confirm that equipment is accurately modeled.

103. Slide 103 Approval to Energize Process Beginning 7 days prior to the Energization Date, ERCOT Operations: Follows a check list of actions Approves or rejects request

104. Approval to Energize Process ERCOT Check List for Approval Modeled and observable in SCADA Modeled in State Estimator Outages properly modeled Energization simulated in Power Flow study case Confirmed there are no unresolved security issues Ascertained that model recognizes new equipment Market Participant contacted to convey tentative approval Slide 104

105. Slide 105 Approval to Energize Process Reasons for Rejection Requested Element not modeled correctly Requested Element supposed to be but not in SCADA Unresolved security issues related to Energization of Requested Element Requested Equipment not in State Estimator Note: ERCOT will contact the requestor to discuss reasons for rejection.

106. Approval to Energize Process Energization of new equipment in the production environment must be preceded by the following two conditions: The new equipment must be in the production model prior to energization Planned Outages with end times corresponding to the energization of the new equipment must be in the Outage Scheduler 106

107. Approval to Energize Process Pre-Check On a daily basis, ERCOT Operations will: Check the Outage Scheduler for new equipment being energized in 7 days. Perform tests on new equipment in the current production model. 107

108. Approval to Energize Process Pre-Check On a daily basis (Continued) If no problems are anticipated, ERCOT will email the Market Participant stating that the Approval to Energize is expected to occur on the requested energization date. If problems are found, the Market Participant will be notified by email with the details of the problem and a statement that the Approval to Energize could be delayed if the issues are not fixed prior to the requested energization date. Email 108

109. Approval to Energize Process Pre-Check If the equipment to be energized is not in the current production model: Market Participant will receive a notice that the equipment is not in the current model and that approval may be delayed. Market Participant is required to call ERCOT Operations and provide details as to when the equipment is expected to be loaded in the model. With appropriate communications, the energization date will not be delayed. Phone Call 109

110. Approval to Energize Process NOTE: If changes in the field energization date are anticipated, Market Participants should contact ERCOT Operations with the updated information by phone. Phone Call 110

111. Slide 111 Approval to Energize Process On the day of energization: Market Participant contacts the ERCOT Shift Supervisor by telephone Requests permission to energize equipment Phone Call

112. Model & Outage Submission Timeline Recommendations Outages can span multiple Model Load dates (recommend two model-ready dates prior to energization or following de-energization) Submit outages 91+ to 46 days in advance. 112 Field Energization or De-energization Dates Jan Mar Apr May Feb 9 1926 Model Load Model Load Model Load 15 3 NOMCR Model-ready Date 7 Outages in the Outage Scheduler 91+ to 46 days in advance NOMCR Model-ready Date Model Load Dec 15 Days A2E

113. 113