ERCOT Nodal Protocols

             Section 3: Management Activities for the ERCOT System

                                 June 1, 2022
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

3	MANAGEMENT ACTIVITIES FOR THE ERCOT SYSTEM	3-1
3.1	Outage Coordination	3-1
3.1.1	Role of ERCOT	3-1
3.1.2	Planned Outage, Maintenance Outage, or Rescheduled Outage Data Reporting	3-4
3.1.3	Rolling 12-Month Outage Planning and Update	3-5
<IP_ADDRESS>	Transmission Facilities	3-5
<IP_ADDRESS>	Resources	3-5
3.1.4	Communications Regarding Resource and Transmission Facilities Outages	3-6
<IP_ADDRESS>	Single Point of Contact	3-6
<IP_ADDRESS>	Method of Communication	3-7
<IP_ADDRESS>	Reporting for Planned Outages, Maintenance Outages, and Rescheduled Outages of Resource and Transmission Facilities	3-8
<IP_ADDRESS>	Management of Resource or Transmission Forced Outages or Maintenance Outages	3-9
<IP_ADDRESS>	Notice of Forced Outage or Unavoidable Extension of Planned, Maintenance, or Rescheduled Outage Due to Unforeseen Events	3-11
<IP_ADDRESS>	Outage Coordination of Potential Transmission Emergency Conditions	3-11
<IP_ADDRESS>	Reporting of Forced Derates	3-12
3.1.5	Transmission System Outages	3-12
<IP_ADDRESS>	ERCOT Evaluation of Planned Outage and Maintenance Outage of Transmission Facilities	3-13
<IP_ADDRESS>	Receipt of TSP Requests by ERCOT	3-15
<IP_ADDRESS>	Timelines for Response by ERCOT for TSP Requests	3-16
<IP_ADDRESS>	Delay	3-17
<IP_ADDRESS>	Opportunity Outage of Transmission Facilities	3-18
<IP_ADDRESS>	Rejection Notice	3-18
<IP_ADDRESS>	Withdrawal of Approval of Approved Planned Outages, Maintenance Outages, and Rescheduled Outages of Transmission Facilities	3-19
<IP_ADDRESS>	Priority of Approved Planned, Maintenance, and Rescheduled Outages	3-21
<IP_ADDRESS>	Information for Inclusion in Transmission Facilities Outage Requests	3-21
<IP_ADDRESS>	Additional Information Requests	3-23
<IP_ADDRESS>	Evaluation of Transmission Facilities Planned Outage or Maintenance Outage Requests	3-23
<IP_ADDRESS>	Submittal Timeline for Transmission Facility Outage Requests	3-25
<IP_ADDRESS>	Transmission Report	3-26
3.1.6	Outages of Resources Other than Reliability Resources	3-26
<IP_ADDRESS>	Receipt of Resource Requests by ERCOT	3-27
<IP_ADDRESS>	Resource Outage Plan	3-28
<IP_ADDRESS>	Additional Information Requests	3-29
<IP_ADDRESS>	Approval of Changes to a Resource Outage Plan	3-29
<IP_ADDRESS>	Evaluation of Proposed Resource Outage	3-30
<IP_ADDRESS>	Timelines for Response by ERCOT for Resource Outages	3-31
<IP_ADDRESS>	Delay	3-32
<IP_ADDRESS>	Resource Outage Rejection Notice	3-33
<IP_ADDRESS>	Withdrawal of Approval or Acceptance and Rescheduling of Approved or Accepted Planned Outages of Resource Facilities	3-34
<IP_ADDRESS>	Opportunity Outage	3-40
<IP_ADDRESS>	Outage Returning Early	3-41
<IP_ADDRESS>	Resource Coming On-Line	3-41
<IP_ADDRESS>	Distribution Facility Outages Impacting Distribution Generation Resources and Distribution Energy Storage Resources	3-42
3.1.7	Reliability Resource Outages	3-43
<IP_ADDRESS>	Timelines for Response by ERCOT on Reliability Resource Outages	3-44
<IP_ADDRESS>	Changes to an Approved Reliability Resource Outage Plan	3-45
3.1.8	High Impact Transmission Element (HITE) Identification	3-45
3.2 	Analysis of Resource Adequacy	3-45
3.2.1	Calculation of Aggregate Resource Capacity	3-45
3.2.2	Demand Forecasts	3-47
3.2.3	Short-Term System Adequacy Reports	3-48
3.2.4	[RESERVED]	3-51
3.2.5	Publication of Resource and Load Information	3-51
<IP_ADDRESS>	Unregistered Distributed Generation Reporting Requirements for Non Opt-In Entities	3-64
<IP_ADDRESS>	Unregistered Distributed Generation Reporting Requirements for Competitive Areas	3-65
<IP_ADDRESS>	Unregistered Distributed Generation Reporting Requirements for ERCOT	3-65
3.2.6	ERCOT Planning Reserve Margin	3-66
<IP_ADDRESS>	Minimum ERCOT Planning Reserve Margin Criterion	3-66
<IP_ADDRESS>	ERCOT Planning Reserve Margin Calculation Methodology	3-66
<IP_ADDRESS>.1	Peak Load Estimate	3-67
<IP_ADDRESS>.2	Total Capacity Estimate	3-69
3.3	Management of Changes to ERCOT Transmission Grid	3-73
3.3.1	ERCOT Approval of New or Relocated Facilities	3-73
3.3.2	Types of Work Requiring ERCOT Approval	3-74
<IP_ADDRESS>	Information to Be Provided to ERCOT	3-74
<IP_ADDRESS>	Record of Approved Work	3-78
3.4	Load Zones	3-78
3.4.1	Load Zone Types	3-78
3.4.2	Load Zone Modifications	3-78
3.4.3	NOIE Load Zones	3-79
3.4.4	DC Tie Load Zones	3-80
3.4.5	Additional Load Buses	3-80
3.5	Hubs	3-81
3.5.1	Process for Defining Hubs	3-81
3.5.2	Hub Definitions	3-82
<IP_ADDRESS>	North 345 kV Hub (North 345)	3-82
<IP_ADDRESS>	South 345 kV Hub (South 345)	3-87
<IP_ADDRESS>	Houston 345 kV Hub (Houston 345)	3-92
<IP_ADDRESS>	West 345 kV Hub (West 345)	3-96
<IP_ADDRESS>	Panhandle 345 kV Hub (Pan 345)	3-100
<IP_ADDRESS>	ERCOT Hub Average 345 kV Hub (ERCOT 345)	3-107
<IP_ADDRESS>	ERCOT Bus Average 345 kV Hub (ERCOT 345 Bus)	3-109
3.5.3	ERCOT Responsibilities for Managing Hubs	3-114
<IP_ADDRESS>	Posting of Hub Buses and Electrical Buses included in Hubs	3-114
<IP_ADDRESS>	Calculation of Hub Prices	3-114
3.6	Load Participation	3-114
3.6.1	Load Resource Participation	3-114
3.6.2	Decision Making Entity for a Resource	3-116
3.7	Resource Parameters	3-117
3.7.1	Resource Parameter Criteria	3-118
<IP_ADDRESS>	Generation Resource Parameters	3-118
<IP_ADDRESS>	Load Resource Parameters	3-118
3.7.2	Changes in Resource Parameters with Operational Impacts	3-119
3.7.3	Resource Parameter Validation	3-120
3.8	Special Considerations for Split Generation Meters, Combined Cycle Generation Resources, Quick Start Generation Resources, Hydro Generation Resources, Energy Storage Resources, Distribution Generation Resources, and Distribution Energy Storage Resources	3-120
3.8.1	Split Generation Resources	3-120
3.8.2	Combined Cycle Generation Resources	3-122
3.8.3	Quick Start Generation Resources	3-124
<IP_ADDRESS>	Quick Start Generation Resource Decommitment Decision Process	3-126
3.8.4	Generation Resources Operating in Synchronous Condenser Fast-Response Mode	3-126
3.8.5	Energy Storage Resources	3-127
3.8.6	Distribution Generation Resources (DGRs) and Distribution Energy Storage Resources (DESRs)	3-128
3.9	Current Operating Plan (COP)	3-131
3.9.1	Current Operating Plan (COP) Criteria	3-132
3.9.2	Current Operating Plan Validation	3-144
3.10	Network Operations Modeling and Telemetry	3-145
3.10.1	Time Line for Network Operations Model Changes	3-150
3.10.2	Annual Planning Model	3-153
3.10.3	CRR Network Model	3-154
<IP_ADDRESS>	Process for Managing Network Operations Model Updates for Point of Interconnection Bus Changes, Resource Retirements and Deletion of DC Tie Load Zones	3-155
3.10.4	ERCOT Responsibilities	3-156
3.10.5	TSP Responsibilities	3-158
3.10.6	QSE and Resource Entity Responsibilities	3-160
3.10.7	ERCOT System Modeling Requirements	3-160
<IP_ADDRESS>	Modeling of Transmission Elements and Parameters	3-160
<IP_ADDRESS>.1	Transmission Lines	3-162
<IP_ADDRESS>.2	Transmission Buses	3-164
<IP_ADDRESS>.3	Transmission Breakers and Switches	3-165
<IP_ADDRESS>.4	Transmission and Generation Resource Step-Up Transformers	3-167
<IP_ADDRESS>.5	Reactors, Capacitors, and other Reactive Controlled Sources	3-169
<IP_ADDRESS>	Modeling of Resources and Transmission Loads	3-170
<IP_ADDRESS>.1	Reporting of Demand Response	3-174
<IP_ADDRESS>.2	Annual Demand Response Report	3-175
<IP_ADDRESS>	Modeling of Private Use Networks	3-178
<IP_ADDRESS>	Remedial Action Schemes, Automatic Mitigation Plans and Remedial Action Plans	3-179
<IP_ADDRESS>	Telemetry Requirements	3-180
<IP_ADDRESS>.1	Continuous Telemetry of the Status of Breakers and Switches	3-182
<IP_ADDRESS>.2	Continuous Telemetry of the Real-Time Measurements of Bus Load, Voltages, Tap Position, and Flows	3-185
<IP_ADDRESS>.3 	Required Telemetry of Voltage and Power Flow	3-188
<IP_ADDRESS>.4	General Telemetry Performance Criteria	3-190
<IP_ADDRESS>.5	Supplemental Telemetry Performance Criteria	3-190
<IP_ADDRESS>.6	TSP/QSE Telemetry Restoration	3-191
<IP_ADDRESS>.7	Calibration, Quality Checking, and Testing	3-192
<IP_ADDRESS>.8	Inter-Control Center Communications Protocol (ICCP) Links	3-192
<IP_ADDRESS>.8.1	Data Quality Codes	3-192
<IP_ADDRESS>.8.2	Reliability of ICCP Associations	3-193
<IP_ADDRESS>.9	ERCOT Requests for Telemetry	3-193
<IP_ADDRESS>.10	ERCOT Requests for Redundant Telemetry	3-195
<IP_ADDRESS>	Use of Generic Transmission Constraints and Generic Transmission Limits	3-196
<IP_ADDRESS>	DC Tie Limits	3-197
3.10.8	Dynamic Ratings	3-198
<IP_ADDRESS>	Dynamic Ratings Delivered via ICCP	3-199
<IP_ADDRESS>	Dynamic Ratings Delivered via Static Table and Telemetered Temperature	3-199
<IP_ADDRESS>	Dynamic Rating Network Operations Model Change Requests	3-200
<IP_ADDRESS>	ERCOT Responsibilities Related to Dynamic Ratings	3-200
<IP_ADDRESS>	Transmission Service Provider Responsibilities Related to Dynamic Ratings	3-201
3.10.9	State Estimator Requirements	3-201
<IP_ADDRESS>	Considerations for State Estimator Requirements	3-202
<IP_ADDRESS>	State Estimator Data	3-203
<IP_ADDRESS>	Telemetry Status and Analog Measurements Data	3-203
<IP_ADDRESS>	State Estimator Performance Requirements	3-203
<IP_ADDRESS>	ERCOT Directives	3-204
<IP_ADDRESS>	Telemetry and State Estimator Performance Monitoring	3-204
3.11	Transmission Planning	3-205
3.11.1	Overview	3-205
3.11.2	Planning Criteria	3-205
3.11.3	Regional Planning Group	3-206
3.11.4	Regional Planning Group Project Review Process	3-207
<IP_ADDRESS>	Project Submission	3-207
<IP_ADDRESS>	Project Comment Process	3-207
<IP_ADDRESS>	Categorization of Proposed Transmission Projects	3-207
<IP_ADDRESS>	Processing of Tier 4 Projects	3-209
<IP_ADDRESS>	Processing of Tier 3 Projects	3-209
<IP_ADDRESS>	Processing of Tier 2 Projects	3-209
<IP_ADDRESS>	Processing of Tier 1 Projects	3-210
<IP_ADDRESS>	Determine Designated Providers of Transmission Additions	3-210
<IP_ADDRESS>	Regional Planning Group Acceptance and ERCOT Endorsement	3-211
<IP_ADDRESS>	Modifications to ERCOT Endorsed Projects	3-212
<IP_ADDRESS>	Customer or Resource Entity Funded Transmission Projects	3-212
3.11.5	Transmission Service Provider and Distribution Service Provider Access to Interval Data	3-213
3.11.6	Generation Interconnection Process	3-213
3.12	Load Forecasting	3-214
3.12.1	Seven-Day Load Forecast	3-214
3.12.2	Study Areas	3-215
3.12.3	Seven-Day Study Area Load Forecast	3-215
3.13	Renewable Production Potential Forecasts	3-216
3.14	Contracts for Reliability Resources and Emergency Response Service Resources	3-217
3.14.1	Reliability Must Run	3-217
<IP_ADDRESS>	Notification of Suspension of Operations	3-219
<IP_ADDRESS>	ERCOT Evaluation Process	3-220
<IP_ADDRESS>.1	ERCOT Evaluation of Seasonal Mothball Status	3-224
<IP_ADDRESS>	ERCOT Board Approval of RMR and MRA Agreements	3-224
<IP_ADDRESS>	Exit Strategy from an RMR Agreement	3-225
<IP_ADDRESS>	Evaluation of Alternatives	3-225
<IP_ADDRESS>	Transmission System Upgrades Associated with an RMR and/or MRA Exit Strategy	3-227
<IP_ADDRESS>	RMR or MRA Contract Termination	3-228
<IP_ADDRESS>	RMR and/or MRA Contract Extension	3-228
<IP_ADDRESS>	Generation Resource Status Updates	3-230
<IP_ADDRESS>	Eligible Costs	3-233
<IP_ADDRESS>	Budgeting Eligible Costs	3-235
<IP_ADDRESS>	Calculation of the Initial Standby Cost	3-238
<IP_ADDRESS>	Updated Budgets During the Term of an RMR Agreement	3-238
<IP_ADDRESS>	Reporting Actual RMR Eligible Costs	3-239
<IP_ADDRESS>	Reporting Actual MRA Eligible Costs	3-239
<IP_ADDRESS>	Reconciliation of Actual Eligible Costs	3-240
<IP_ADDRESS>	Incentive Factor	3-240
<IP_ADDRESS>	Major Equipment Modifications	3-240
<IP_ADDRESS>	Charge for Contributed Capital Expenditures	3-241
<IP_ADDRESS>	Budgeting Fuel Costs	3-242
<IP_ADDRESS>	Reporting Actual Eligible Fuel Costs	3-243
3.14.2	Black Start	3-244
3.14.3	Emergency Response Service	3-246
<IP_ADDRESS>	Emergency Response Service Procurement	3-246
<IP_ADDRESS>	Emergency Response Service Self-Provision	3-253
<IP_ADDRESS>	Emergency Response Service Provision and Technical Requirements	3-254
<IP_ADDRESS>	Emergency Response Service Reporting and Market Communications	3-257
3.14.4	Must-Run Alternative Service	3-259
<IP_ADDRESS>	Overview and Description of MRAs	3-259
<IP_ADDRESS>	Preliminary Review of Prospective Demand Response MRAs	3-262
<IP_ADDRESS>	MRA Substitution	3-263
<IP_ADDRESS>	Commitment and Dispatch	3-263
<IP_ADDRESS>	Standards for Generation Resource MRAs	3-264
<IP_ADDRESS>	Standards for Other Generation MRAs and Demand Response MRAs	3-264
<IP_ADDRESS>.1	MRA Telemetry Requirements	3-264
<IP_ADDRESS>.2	Baseline Performance Evaluation Methodology for Demand Response MRAs	3-265
<IP_ADDRESS>.3	MRA Metering and Metering Data	3-265
<IP_ADDRESS>.4	MRA Availability Measurement and Verification	3-266
<IP_ADDRESS>.5	MRA Event Performance Measurement and Verification	3-267
<IP_ADDRESS>.5.1	Event Performance Measurement and Verification for Co-Located Demand Response MRAs and Other Generation MRAs	3-270
<IP_ADDRESS>	MRA Testing	3-271
<IP_ADDRESS>	MRA Misconduct Events	3-272
<IP_ADDRESS>	MRA Reporting to Transmission and/or Distribution Service Providers (TDSPs)	3-272
3.15	Voltage Support	3-273
3.15.1	ERCOT Responsibilities Related to Voltage Support	3-284
3.15.2	DSP Responsibilities Related to Voltage Support	3-286
3.15.3	Generation Resource Requirements Related to Voltage Support	3-286
3.16	Standards for Determining Ancillary Service Quantities	3-288
3.17	Ancillary Service Capacity Products	3-293
3.17.1	Regulation Service	3-293
3.17.2	Responsive Reserve Service	3-294
3.17.3	Non-Spinning Reserve Service	3-295
3.17.4	ERCOT Contingency Reserve Service	3-296
3.18	Resource Limits in Providing Ancillary Service	3-297
3.19	Constraint Competitiveness Tests	3-300
3.19.1	Constraint Competitiveness Test Definitions	3-300
3.19.2	Element Competitiveness Index Calculation	3-301
3.19.3	Long-Term Constraint Competitiveness Test	3-302
3.19.4	Security-Constrained Economic Dispatch Constraint Competitiveness Test	3-302
3.20	Identification of Chronic Congestion	3-304
3.20.1	Evaluation of Chronic Congestion	3-304
3.20.2	Topology and Model Verification	3-304
3.21	Submission of Emergency Operations Plans, Weatherization Plans, and Declarations of Summer and Winter Weather Preparedness	3-305
3.21.1	Natural Gas Pipeline Coordination Requirements for Resource Entities with Natural Gas Generation Resources for Summer Preparedness and Summer Peak Load Season	3-306
3.22	Subsynchronous Resonance	3-308
3.22.1	Subsynchronous Resonance Vulnerability Assessment	3-308
<IP_ADDRESS> 	Existing Generation Resource Assessment	3-308
<IP_ADDRESS> 	Generation Resource or Energy Storage Resource Interconnection Assessment	3-309
<IP_ADDRESS> 	Transmission Project Assessment	3-310
<IP_ADDRESS> 	Annual SSR Review	3-311
3.22.2	Subsynchronous Resonance Vulnerability Assessment Criteria	3-312
3.22.3 	Subsynchronous Resonance Monitoring	3-314
3.23	Agreements between ERCOT and other Control Area Operators	3-315

MANAGEMENT ACTIVITIES FOR THE ERCOT SYSTEM
(1)	This section focuses on the management activities, including Outage Coordination, Resource Adequacy, Load forecasting, transmission operations and planning, and contracts for Ancillary Services for the ERCOT System.
3.1	Outage Coordination
(1)	"Outage Coordination" is the management of Transmission Facilities Outages and Resource Outages in the ERCOT System. Facility owners are solely and directly responsible for the performance of all maintenance, repair, and construction work, whether on energized or de-energized facilities, including all activities related to providing a safe working environment.
3.1.1	Role of ERCOT
(1)	ERCOT shall coordinate and use reasonable efforts, consistent with Good Utility Practice, to accept, approve or reject all Outage schedules for maintenance, repair, and construction of both Transmission Facilities and Resources within the ERCOT System.  ERCOT may reject an Outage schedule under certain circumstances, as set forth in these Protocols.
[NPRR1108:  Replace paragraph (1) above with the following upon system implementation:]
(1)	ERCOT shall coordinate and use reasonable efforts, consistent with Good Utility Practice, to accept, approve or reject all requested Outage plans for maintenance, repair, and construction of both Transmission Facilities and Resources within the ERCOT System.  ERCOT may reject an Outage plan under certain circumstances, as set forth in these Protocols.
(2)	ERCOT's responsibilities with respect to Outage Coordination include:
(a)	Approving or rejecting requests for Planned Outages and Maintenance Outages of Transmission Facilities for Transmission Service Providers (TSPs) in coordination with and based on information regarding all Entities' Planned Outages and Maintenance Outages;
[NPRR857:  Replace paragraph (a) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
      (a)	Approving or rejecting requests for Planned Outages and Maintenance Outages of Transmission Facilities for Transmission Service Providers (TSPs) and Direct Current Tie Operators (DCTOs) in coordination with and based on information regarding all Entities' Planned Outages and Maintenance Outages;
(b)	Assessing the adequacy of available Resources, based on planned and known Resource Outages, relative to forecasts of Load, Ancillary Service requirements,  and reserve requirements;
(c)	Coordinating and approving or rejecting schedules for Planned Outages of Resources scheduled to occur within 45 days after request;
[NPRR1108:  Replace paragraph (c) above with the following upon system implementation:]
      (c)	Coordinating all Planned Outage and Maintenance Outage plans and approving or rejecting Outage plans for Planned Outages of Resources;
(d)	Coordinating and approving or rejecting schedules for Planned Outages of Reliability Must-Run (RMR) Units under the terms of the applicable RMR Agreements;
[NPRR1108:  Replace paragraph (d) above with the following upon system implementation:]
      (d)	Coordinating and approving or rejecting Outage plans for Planned Outages of Reliability Must-Run (RMR) Units under the terms of the applicable RMR Agreements;
(e)	Coordinating and approving or rejecting Outages associated with Black Start Resources under the applicable Black Start Unit Agreements;
[NPRR1108:  Replace paragraph (e) above with the following upon system implementation:]
      (e)	Coordinating and approving or rejecting Outage plans associated with Black Start Resources under the applicable Black Start Unit Agreements;
(f)	Coordinating and approving or rejecting Outages affecting Subsynchronous Resonance (SSR) vulnerable Generation Resources that do not have SSR Mitigation in the event of five or six concurrent transmission Outages;
[NPRR1108:  Replace paragraph (f) above with the following upon system implementation:]
      (f)	Coordinating and approving or rejecting Outage plans affecting Subsynchronous Resonance (SSR) vulnerable Generation Resources that do not have SSR Mitigation in the event of five or six concurrent transmission Outages;
(g)	Reviewing and coordinating changes to existing 12-month Resource Outage plans to determine how changes will affect ERCOT System reliability, including Resource Outages not previously included in the Outage plan;
[NPRR1108:  Replace paragraph (g) above with the following upon system implementation:]
      (g)	Coordinating and approving or rejecting changes to existing Resource Outage plans;
(h)	Monitoring how Planned Outage schedules compare with actual Outages;
(i)	Posting all proposed and approved schedules for Planned Outages, Maintenance Outages, and Rescheduled Outages of Transmission Facilities on the Market Information System (MIS) Secure Area under Section <IP_ADDRESS>, Transmission Report;
(j)	Creating aggregated schedules of Planned Outages for Resources and posting those schedules on the MIS Secure Area under Section 3.2.3, Short-Term System Adequacy Reports;
[NPRR1108:  Replace paragraph (j) above with the following upon system implementation:]
      (j)	Creating and posting aggregated MW of Planned Outages for Resources on the MIS Secure Area under Section 3.2.3, Short-Term System Adequacy Reports;
(k)	Monitoring Transmission Facilities and Resource Forced Outages and Maintenance Outages of immediate nature and implementing responses to those Outages as provided in these Protocols;
(l)	Establishing and implementing communication procedures:
(i)	For a TSP to request approval of Transmission Facilities Planned Outage and Maintenance Outage schedules; and
[NPRR857 and NPRR1108:  Replace applicable portions of item (i) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities for NPRR857; or upon system implementation for NPRR1108:]
(i)	For a TSP or a DCTO to request approval of Transmission Facilities Planned Outage and Maintenance Outage plans; and
(ii)	For a Resource Entity's designated Single Point of Contact to submit Outage plans and to coordinate Resource Outages;
(m)	Establishing and implementing record-keeping procedures for retaining all requested Planned Outages, Maintenance Outages, Rescheduled Outages, and Forced Outages; and
(n)	Planning and analyzing Transmission Facilities Outages.
3.1.2	Planned Outage, Maintenance Outage, or Rescheduled Outage Data Reporting
(1)	Each Resource Entity shall use reasonable efforts, consistent with Good Utility Practice, to continually update its Outage Schedule.  All information submitted about Planned Outages, Maintenance Outages, or Rescheduled Outages must be submitted by the Resource Entity or the TSP under this Section.  If an Outage Schedule for a Resource is also applicable to the Current Operating Plan (COP), the Qualified Scheduling Entity (QSE) responsible for the Resource shall also update the COP to provide the same information describing the Outage.  Each TSP shall use reasonable efforts, consistent with Good Utility Practice, to continually update its Outage Schedule, including, but not limited to, submitting the actual start and end date and time for Planned Outages of Transmission Facilities in the Outage Scheduler by hour ending 0800 of the current Operating Day for all scheduled work completed prior to hour ending 0600 of the current Operating Day.
[NPRR857 and NPRR1108:  Replace applicable portions of paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities for NPRR857; or upon system implementation for NPRR1108:]
(1)	Each Resource Entity shall use reasonable efforts, consistent with Good Utility Practice, to continually update its Outage plans for all Outages.  All information submitted about Planned Outages, Maintenance Outages, or Rescheduled Outages must be submitted by the Resource Entity, TSP, or DCTO under this Section.  If an Outage plan for a Resource is also applicable to the Current Operating Plan (COP), the Qualified Scheduling Entity (QSE) responsible for the Resource shall also update the COP to provide the same information describing the Outage.  Each TSP and DCTO shall use reasonable efforts, consistent with Good Utility Practice, to continually update its Outage plan, including, but not limited to, submitting the actual start and end date and time for Planned Outages of Transmission Facilities in the Outage Scheduler by hour ending 0800 of the current Operating Day for all scheduled work completed prior to hour ending 0600 of the current Operating Day.
3.1.3	Rolling 12-Month Outage Planning and Update
<IP_ADDRESS>	Transmission Facilities
(1)	Each TSP shall provide to ERCOT a plan for Planned Outages, Maintenance Outages and Rescheduled Outages in an ERCOT-provided format for the next 12 months updated monthly.  Planned Outage, Maintenance Outage, and Rescheduled Outage scheduling data for Transmission Facilities must be kept current.  Updates must identify all changes to any previously proposed Planned Outages, Maintenance Outages, or Rescheduled Outages and any additional Planned Outages, Maintenance Outages, or Rescheduled Outages anticipated over the next 12 months.  ERCOT shall coordinate in-depth reviews of the 12-month plan with each TSP at least twice per year.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	Each TSP and DCTO shall provide to ERCOT a plan for Planned Outages, Maintenance Outages, and Rescheduled Outages in an ERCOT-provided format for the next 12 months updated monthly.  Planned Outage, Maintenance Outage, and Rescheduled Outage scheduling data for Transmission Facilities must be kept current.  Updates must identify all changes to any previously proposed Planned Outages, Maintenance Outages, or Rescheduled Outages and any additional Planned Outages, Maintenance Outages, or Rescheduled Outages anticipated over the next 12 months.  ERCOT shall coordinate in-depth reviews of the 12-month plan with each TSP at least twice per year.
<IP_ADDRESS>	Resources
(1)	Each Resource Entity shall provide to ERCOT a Planned Outage and Maintenance Outage plan for Generation Resources in an ERCOT-provided format for the next 12 months updated monthly.  Planned Outage and Maintenance Outage scheduling data must be kept current.  Updates, through an electronic interface as specified by ERCOT, must identify any changes to previously proposed Planned Outages or Maintenance Outages and any additional Planned Outages or Maintenance Outages anticipated over the next 12 months.
[NPRR1108:  Replace paragraph (1) above with the following upon system implementation:]
(1)	Each Resource Entity shall provide to ERCOT a Planned Outage and Maintenance Outage plan for Generation Resources in an ERCOT-provided format for at least the next 12 months updated monthly.  Planned Outage and Maintenance Outage plans must be updated as soon as practicable following any change.  Updates, through an electronic interface as specified by ERCOT, must identify any changes to previously proposed Planned Outages or Maintenance Outages and any additional Planned Outages or Maintenance Outages.
(2)	ERCOT shall report statistics monthly on how Resource Planned Outages compare with actual Resource Outages, and post those statistics to the MIS Secure Area.
3.1.4	Communications Regarding Resource and Transmission Facilities Outages
<IP_ADDRESS>	Single Point of Contact
(1)	All communications concerning a Planned Outage, Maintenance Outage, or Rescheduled Outage must be between ERCOT and the designated "Single Point of Contact" for each TSP or Resource Entity.  All nonverbal communications concerning Planned Outages or Rescheduled Outages must be conveyed through an electronic interface as specified by ERCOT.  The TSP or Resource Entity shall identify, in its initial request or response, the Single Point of Contact, with primary and alternate means of communication.  The Resource Entity or TSP shall submit a Notice of Change of Information (NCI) form (Section 23, Form E, Notice of Change of Information) when changes occur to a Single Point of Contact.  This identification must be confirmed in all communications with ERCOT regarding Planned Outage, Maintenance Outage, or Rescheduled Outage requests.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	All communications concerning a Planned Outage, Maintenance Outage, or Rescheduled Outage must be between ERCOT and the designated "Single Point of Contact" for each TSP, DCTO, or Resource Entity.  All nonverbal communications concerning Planned Outages or Rescheduled Outages must be conveyed through an electronic interface as specified by ERCOT.  The TSP, DCTO, or Resource Entity shall identify, in its initial request or response, the Single Point of Contact, with primary and alternate means of communication.  The Resource Entity, TSP, or DCTO shall submit a Notice of Change of Information (NCI) form (Section 23, Form E, Notice of Change of Information) when changes occur to a Single Point of Contact.  This identification must be confirmed in all communications with ERCOT regarding Planned Outage, Maintenance Outage, or Rescheduled Outage requests.
(2)	The Single Point of Contact must be either a person or a position available seven days per week and 24 hours per day for each Resource Entity and TSP.  The Resource Entity shall designate its QSE as its Single Point of Contact.  The designated Single Point of Contact for a Generation Resource that has been split into two or more Split Generation Resources shall be the Master QSE.  The Single Point of Contact for the TSP must be designated under the ERCOT Operating Guides.
[NPRR857:  Replace paragraph (2) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(2)	The Single Point of Contact must be either a person or a position available seven days per week and 24 hours per day for each Resource Entity, TSP, or DCTO.  The Resource Entity shall designate its QSE as its Single Point of Contact.  The designated Single Point of Contact for a Generation Resource that has been split into two or more Split Generation Resources shall be the Master QSE.  The Single Point of Contact for each TSP and DCTO must be designated under the ERCOT Operating Guides.
<IP_ADDRESS>	Method of Communication
(1)	ERCOT, each TSP, and each Resource Entity shall communicate according to ERCOT procedures under these Protocols.  All submissions, changes, approvals, rejections, and withdrawals regarding Outages must be processed through the ERCOT Outage Scheduler on the ERCOT programmatic interface, except for Forced Outages and Maintenance Level I Outages, which must be communicated to ERCOT immediately via the Current Operating Plan if submitted for a Resource and using the Outage Scheduler if submitted by a TSP.  This does not prohibit any verbal communication when the situation warrants it.  ERCOT shall develop guidelines for the types of events that may require verbal communication.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	ERCOT and each TSP, DCTO, and Resource Entity shall communicate according to ERCOT procedures under these Protocols.  All submissions, changes, approvals, rejections, and withdrawals regarding Outages must be processed through the ERCOT Outage Scheduler on the ERCOT programmatic interface, except for Forced Outages and Maintenance Level I Outages, which must be communicated to ERCOT immediately via the Current Operating Plan if submitted for a Resource and using the Outage Scheduler if submitted by a TSP or DCTO.  This does not prohibit any verbal communication when the situation warrants it.  ERCOT shall develop guidelines for the types of events that may require verbal communication.
<IP_ADDRESS>	Reporting for Planned Outages, Maintenance Outages, and Rescheduled Outages of Resource and Transmission Facilities
(1)	Each Resource Entity and TSP shall submit information regarding proposed Planned Outages, Maintenance Outages, and Rescheduled Outages of Transmission Facilities or Planned Outages and Maintenance Outages of 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.  A Resource Entity or TSP is also obligated to submit information for Transmission Facilities or Generation Resources that are not part of the ERCOT System or that do not affect the ERCOT System if that information is required for regional security coordination as determined by ERCOT.
[NPRR857 and NPRR1014:  Replace applicable portions of paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities for NPRR857; and upon system implementation for NPRR1014:]
(1)	Each Resource Entity, TSP, and DCTO shall submit information regarding proposed Planned Outages, Maintenance Outages, and Rescheduled Outages of Transmission Facilities or Planned Outages and Maintenance Outages of Generation Resources or Energy Storage Resources (ESRs) 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 or ESR that is part of or that affects the ERCOT System.  The obligation to submit that information applies to each TSP, DCTO, or Resource Entity that is responsible to operate or maintain Transmission Facilities that are part of or affect the ERCOT System.  A Resource Entity, TSP, or DCTO is also obligated to submit information for Transmission Facilities or Generation Resources or ESRs that are not part of the ERCOT System or that do not affect the ERCOT System if that information is required for regional security coordination as determined by ERCOT.
(2)	Before taking an RMR or Black Start Resource ("Reliability Resources") out of service for a Planned Outage or Maintenance Outage, the Single Point of Contact for that Reliability Resource must obtain ERCOT's approval of the schedule of the Planned Outage or Maintenance Outage.  ERCOT shall review and approve or reject each proposed Planned Outage or Maintenance Outage Schedule under this Section and the applicable Agreements.
[NPRR1120:  Insert paragraph (3) below upon system implementation:]
(3)	A Firm Fuel Supply Service Resource (FFSSR) shall not schedule or request a Planned Outage that would occur during the period of December 1 through March 1.
<IP_ADDRESS>	Management of Resource or Transmission Forced Outages or Maintenance Outages
(1)	In the event of a Forced Outage, after the affected equipment is removed from service, the Resource Entity or QSE, as appropriate, or TSP must notify ERCOT as soon as practicable of its action by:
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	In the event of a Forced Outage, after the affected equipment is removed from service, the Resource Entity or QSE, as appropriate, TSP, or DCTO must notify ERCOT as soon as practicable of its action by:
(a)	For Resource Outages:
(i)	Changing the telemetered Resource Status appropriately, including a text description when it becomes known, of the cause of the Forced Outage; and
(ii)	Updating the COP; and
(iii)	Updating the Outage Scheduler, if necessary.
(b)	For Transmission Facilities Forced Outages:
(i)	Changing the telemetered status of the affected Transmission Elements; and
(ii)	Updating the Outage Scheduler with the expected return-to-service time.
(2)	Forced Outages may require ERCOT to review and withdraw approval of previously approved or accepted, as applicable, Planned Outage, Maintenance Outage, or Rescheduled Outage schedules to ensure reliability.
(3)	For Maintenance Outages, the Resource Entity or QSE, as appropriate, or TSP shall notify ERCOT of any Resource or Transmission Facilities Maintenance Outage according to the Maintenance Outage Levels by updating the COP and Outage Scheduler.  ERCOT shall coordinate the removal of facilities from service within the defined timeframes as specified by the TSP, QSE or Resource Entity in its notice to ERCOT.
[NPRR857:  Replace paragraph (3) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(3)	For Maintenance Outages, the Resource Entity or QSE, as appropriate, TSP, or DCTO shall notify ERCOT of any Resource or Transmission Facilities Maintenance Outage according to the Maintenance Outage Levels by updating the COP and Outage Scheduler.  ERCOT shall coordinate the removal of facilities from service within the defined timeframes as specified by the TSP, DCTO, QSE, or Resource Entity in its notice to ERCOT.
(4)	ERCOT may require supporting information describing Forced Outages and Maintenance Outages.  ERCOT may reconsider and withdraw approvals of other previously approved Transmission Facilities Outage or an Outage of a Reliability Resource as a result of Forced Outages or Maintenance Outages, if necessary, in ERCOT's determination to protect system reliability.  When ERCOT approves a Maintenance Outage, ERCOT shall coordinate timing of the appropriate course of action under these Protocols.
(5)	Removal of a Resource or Transmission Facilities from service under Maintenance Outages must be coordinated with ERCOT.  To minimize harmful impacts to the system in urgent situations, the equipment may be removed immediately from service, provided notice is given immediately, by the Resource Entity or TSP, to ERCOT of such action.
[NPRR857:  Replace paragraph (5) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(5)	Removal of a Resource or Transmission Facilities from service under Maintenance Outages must be coordinated with ERCOT.  To minimize harmful impacts to the system in urgent situations, the equipment may be removed immediately from service, provided the Resource Entity, TSP, or DCTO immediately gives notice of such action to ERCOT.
<IP_ADDRESS>	Notice of Forced Outage or Unavoidable Extension of Planned, Maintenance, or Rescheduled Outage Due to Unforeseen Events
(1)	If a Planned, Maintenance, or Rescheduled Outage is not completed within the ERCOT-approved timeframe and the Transmission Facilities or Resources are in such a condition that they cannot be restored at the Outage schedule completion date, the requesting party shall submit to ERCOT a Forced Outage (unavoidable extension) form describing the extension of the Outage and providing a revised return date.
(2)	Any Forced Outage that occurs in Real-Time must be entered into the Outage Scheduler if it is to remain an Outage for longer than two hours.
(3)	If the QSE is to receive the exemption described in paragraph (6)(d) of Section <IP_ADDRESS>.1, Regulation Service and Generation Resource/Controllable Load Resource Energy Deployment Performance, the QSE will notify ERCOT Operators by voice communication of every Forced Outage, Forced Derate, or Startup Loading Failure within 15 minutes.
<IP_ADDRESS>	Outage Coordination of Potential Transmission Emergency Conditions
(1)	If ERCOT forecasts an inability to meet applicable transmission reliability standards, has exercised all other reasonable options, and there is only one QSE with approved or accepted Resource Outages which could resolve the situation if the start of one or more of the Resource Outages at a single Resource site were delayed or one or more ongoing Resource Outages at a single Resource site were restored early, then ERCOT may contact that QSE and attempt to reach a mutually acceptable solution to delay or reschedule one or more of those Outages.  In this case, ERCOT is not obligated to follow the process described in Section <IP_ADDRESS>, Withdrawal of Approval or Acceptance and Rescheduling of Approved or Accepted Planned Outages of Resource Facilities.  ERCOT shall not provide information to the QSE during these contacts which is not directly related to the QSE's Planned Resource Outage(s) and is not otherwise available to all other Market Participants.
(2)	If ERCOT and the QSE are unable to reach a mutually agreeable solution to change the Resource Outage, ERCOT may issue an Outage Schedule Adjustment (OSA) to the QSE for the Resource.
[NPRR930:  Insert paragraph (3) below upon system implementation and renumber accordingly:]
(3)	If there are Resources at multiple sites with approved or accepted Resource Outages, whose approval or acceptance could be withdrawn to meet the applicable transmission reliability standards, ERCOT shall utilize the process described in Section <IP_ADDRESS>.
(3)	This Section is not intended to restrict ongoing Outage Coordination activities occurring more than seven days in advance of Real-Time.
<IP_ADDRESS>	Reporting of Forced Derates
(1)	The Resource Entity or its designee must enter Forced Derates that are expected to last more than 48 hours into the Outage Scheduler.
[NPRR1097:  Insert Section <IP_ADDRESS> below upon system implementation:]
<IP_ADDRESS>	Resource Forced Outage Report
(1)	Three days after each Operating Day, ERCOT shall post to the ERCOT website a report that identifies each Forced Outage, Maintenance Outage, or Forced Derate of a Generation Resource or Energy Storage Resource (ESR) that occurs during, or that extends into, that Operating Day.  At a minimum, the report shall contain:
      (a)	The Resource name;
      (b)	The Resource unit code;
      (c)	The Resource's fuel type;
      (d)	The type of Outage or derate;
      (e)	The Resource's applicable Seasonal net maximum sustainable rating;
      (f)	The available MW during the Outage or derate;
      (g)	The effective MW reduction due to the Outage or derate;
      (h)	The start date/time and the planned or actual end date/time; and
      (i)	The entry in the "nature of work" field in the Outage Scheduler for each Outage or derate.
3.1.5	Transmission System Outages
<IP_ADDRESS>	ERCOT Evaluation of Planned Outage and Maintenance Outage of Transmission Facilities
(1)	A TSP or Resource Entity shall request a Planned Outage or Maintenance Outage when any Transmission Facility that is part of the ERCOT Transmission Grid and defined in the Network Operations Model will be removed from its normal service.  For Resource Entities within a Private Use Network, this only includes Transmission Facilities at the Point of Interconnection (POI).  For TSP requests, the TSPs shall enter such requests in the Outage Scheduler.  For Resource Entity requests, the Resource Entity shall enter such requests in the Outage Scheduler.  Planned Outages, Maintenance Outages, or Rescheduled Outages for Electrical Buses will be treated as consequentially outaged Transmission Elements.  In those cases where a TSP enters the breaker and switch statuses associated with an Electrical Bus, a downstream topology processor will evaluate the breakers and switches associated with the applicable Electrical Bus to determine if the Electrical Bus is consequentially outaged, and to thereby designate the status of the Electrical Bus.  Proposed Transmission Planned Outage or Maintenance Outage information submitted by a TSP or Resource Entity in accordance with this Section constitutes a request for ERCOT's approval of the Outage Schedule associated with the Planned Outage or Maintenance Outage.  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.  ERCOT shall evaluate requests under Section <IP_ADDRESS>, Evaluation of Transmission Facilities Planned Outage or Maintenance Outage Requests.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	A TSP, DCTO, or Resource Entity shall request a Planned Outage or Maintenance Outage when any Transmission Facility that is part of the ERCOT Transmission Grid and defined in the Network Operations Model will be removed from its normal service.  For Resource Entities within a Private Use Network, this only includes Transmission Facilities at the Point of Interconnection (POI).  For TSP, DCTO, and Resource Entity requests, the requesting Entity shall enter such a request in the Outage Scheduler.  Planned Outages, Maintenance Outages, or Rescheduled Outages for Electrical Buses will be treated as consequentially outaged Transmission Elements.  In those cases where a TSP or DCTO enters the breaker and switch statuses associated with an Electrical Bus, a downstream topology processor will evaluate the breakers and switches associated with the applicable Electrical Bus to determine if the Electrical Bus is consequentially outaged, and to thereby designate the status of the Electrical Bus.  Proposed Transmission Planned Outage or Maintenance Outage information submitted by a TSP, DCTO, or Resource Entity in accordance with this Section constitutes a request for ERCOT's approval of the Outage Schedule associated with the Planned Outage or Maintenance Outage.  ERCOT is not deemed to have approved the Outage Schedule associated with the Planned Outage or Maintenance Outage until ERCOT notifies the TSP, DCTO, or Resource Entity of its approval under procedures adopted by ERCOT.  ERCOT shall evaluate requests under Section <IP_ADDRESS>, Evaluation of Transmission Facilities Planned Outage or Maintenance Outage Requests.
(2)	ERCOT shall review and approve Planned Outages and Maintenance Outages of Transmission Facilities schedules.  ERCOT shall transmit its approvals and rejections to TSPs via the ERCOT Outage Scheduler.  Once approved, ERCOT may not withdraw its approval except under the conditions described in Section <IP_ADDRESS>, Withdrawal of Approval of Approved Planned Outages, Maintenance Outages, and Rescheduled Outages of Transmission Facilities.
[NPRR857:  Replace paragraph (2) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(2)	ERCOT shall review and approve Planned Outages and Maintenance Outages of Transmission Facilities schedules.  ERCOT shall transmit its approvals and rejections to TSPs and DCTOs via the ERCOT Outage Scheduler.  Once approved, ERCOT may not withdraw its approval except under the conditions described in Section <IP_ADDRESS>, Withdrawal of Approval of Approved Planned Outages, Maintenance Outages, and Rescheduled Outages of Transmission Facilities.
(3)	Private Use Network Outage requests submitted pursuant to this Section shall not be publicly posted.
(4)	To the extent authorized by its tariff, an External Load Serving Entity (ELSE) or Non-Opt-In Entity (NOIE) that provides retail service to a Resource Entity that owns or operates a Generation Resource may request that the TSP to which the Generation Resource is interconnected disconnect the Generation Resource due to the Resource Entity's failure to comply with the payment requirements in the ELSE's or NOIE's retail tariff.
(5)	Within five Business Days after receiving a request from a Load Serving Entity (LSE) to disconnect a Generation Resource due to the Resource Entity's failure to comply with LSE's payment requirements, including a request received pursuant to paragraph (4) above, the interconnecting TSP shall enter a request in the Outage Scheduler for an Outage of any Transmission Facilities interconnecting the Generation Resource to the ERCOT System.  Any Outage requested or taken pursuant to this Section shall be treated as a Planned Outage for all purposes under the Protocols.  For any such Outage request, the requesting TSP shall enter a start date that it is at least four days after the date the request is submitted in the Outage Scheduler and shall enter an Outage end date that is 14 days from the date of the requested start date.  Unless storm or system reliability issues prevent immediate dispatch of personnel, for any LSE request to reconnect a Customer that was disconnected pursuant to this section, the interconnecting TSP shall end the Outage and reconnect the Generation Resource the same Business Day if the request is received by 1200, or the next Business Day if the request is received after 1200.  If a reconnect request is not received within four days of the Outage end date, the interconnecting TSP shall enter another request in the Outage Scheduler for an Outage of any Transmission Facilities interconnecting the Generation Resource to the ERCOT System with an Outage end date 14 days beyond the prior Outage end date.  At any time, ERCOT may withdraw approval of the Outage and instruct the TSP to reconnect the Generation Resource if it deems cancellation necessary to address reliability concerns.
<IP_ADDRESS>	Receipt of TSP Requests by ERCOT
(1)	ERCOT shall acknowledge each request for approval of a Transmission Planned Outage or Maintenance Outage schedule within two Business Hours of the receipt of the request.  ERCOT may request additional information or seek clarification from the TSP regarding the information submitted for a proposed Planned Outage or Maintenance Outage for Transmission Facilities.
[NPRR857:  Replace Section <IP_ADDRESS> above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
<IP_ADDRESS>	Receipt of TSP and DCTO Requests by ERCOT
(1)	ERCOT shall acknowledge each request for approval of a Transmission Planned Outage or Maintenance Outage schedule within two Business Hours of the receipt of the request.  ERCOT may request additional information or seek clarification from the TSP or DCTO regarding the information submitted for a proposed Planned Outage or Maintenance Outage for Transmission Facilities.
<IP_ADDRESS>	Timelines for Response by ERCOT for TSP Requests
(1)	For Transmission Facilities Outages, ERCOT shall approve or reject each request in accordance with the following table:
Amount of time between the request for approval of the proposed Outage and the scheduled start date of the proposed Outage:
ERCOT shall approve or reject no later than:
Three days
1800 hours, two days before the start of the proposed Outage
Between four and eight days
1800 hours, three days before the start of the proposed Outage
Between nine days and 45 days
Four days before the start of the proposed Outage
Between 46 and 90 days
30 days before the start of the proposed Outage
Greater than 90 days
75 days before the start of the proposed Outage

(2)	For Outages scheduled at least three days before the scheduled start date of the proposed Outage, ERCOT shall make reasonable attempts to accommodate unusual circumstances that support TSP requests for approval earlier than required by the schedule above.
(3)	If circumstances prevent adherence to these timetables, ERCOT shall discuss the request status and reason for the delay of the approval with the requesting TSP and make reasonable attempts to mitigate the effect of the delay on the TSP.
(4)	When ERCOT rejects a request for an Outage, ERCOT shall provide the TSP, in written or electronic form, suggested amendments to the schedules of a Planned Outage or Maintenance Outage of Transmission Facilities.  Any such suggested amendments accepted by the TSP must be processed by ERCOT as a Planned Outage or Maintenance Outage of Transmission Facilities request under this Section.
[NPRR857:  Replace Section <IP_ADDRESS> above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
<IP_ADDRESS>	Timelines for Response by ERCOT for TSP and DCTO Requests
(1)	For Transmission Facilities Outages, ERCOT shall approve or reject each request in accordance with the following table:
Amount of time between the request for approval of the proposed Outage and the scheduled start date of the proposed Outage:
ERCOT shall approve or reject no later than:
Three days
1800 hours, two days before the start of the proposed Outage
Between four and eight days
1800 hours, three days before the start of the proposed Outage
Between nine days and 45 days
Four days before the start of the proposed Outage
Between 46 and 90 days
30 days before the start of the proposed Outage
Greater than 90 days
75 days before the start of the proposed Outage

(2)	For Outages scheduled at least three days before the scheduled start date of the proposed Outage, ERCOT shall make reasonable attempts to accommodate unusual circumstances that support TSP and DCTO requests for approval earlier than required by the schedule above.
(3)	If circumstances prevent adherence to these timetables, ERCOT shall discuss the request status and reason for the delay of the approval with the requesting TSP or DCTO and make reasonable attempts to mitigate the effect of the delay on the TSP or DCTO.
(4)	When ERCOT rejects a request for an Outage, ERCOT shall provide the TSP or DCTO, in written or electronic form, suggested amendments to the schedules of a Planned Outage or Maintenance Outage of Transmission Facilities.  Any such suggested amendments accepted by the TSP or DCTO must be processed by ERCOT as a Planned Outage or Maintenance Outage of Transmission Facilities request under this Section.
<IP_ADDRESS>	Delay
(1)	ERCOT may delay its approval or rejection of a proposed Planned Outage or Maintenance Outage of a Transmission Facilities schedule if the requesting TSP has not submitted sufficient or complete information within the time frames set forth in these Protocols.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	ERCOT may delay its approval or rejection of a proposed Planned Outage or Maintenance Outage of a Transmission Facilities schedule if the requesting TSP or DCTO has not submitted sufficient or complete information within the time frames set forth in these Protocols.
<IP_ADDRESS>	Opportunity Outage of Transmission Facilities
(1)	Opportunity Outages of Transmission Facilities may be approved under Section <IP_ADDRESS>, Opportunity Outage.
<IP_ADDRESS>	Rejection Notice
(1)	If ERCOT rejects a request, ERCOT shall provide the TSP a written or electronic rejection notice that includes:
(a)	Specific concerns causing the rejection;
(b)	Possible remedies or transmission schedule revisions, if any that might mitigate the basis for rejection; and
(c)	An electronic copy of the ERCOT study case for review by the TSP.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	If ERCOT rejects a request, ERCOT shall provide the TSP or DCTO a written or electronic rejection notice that includes:
      (a)	Specific concerns causing the rejection;
      (b)	Possible remedies or transmission schedule revisions, if any that might mitigate the basis for rejection; and
      (c)	An electronic copy of the ERCOT study case for review by the TSP or DCTO.
(2)	ERCOT may reject a Planned Outage or Maintenance Outage of Transmission Facilities only:
(a)	To protect system reliability or security;
(b)	Due to insufficient information regarding the Outage; or
(c)	Due to failure to comply with submittal process requirements, as specified in these Protocols.
(3)	When multiple proposed Planned Outages, Maintenance Outages, or Rescheduled Outages cause a reliability or security concern, ERCOT shall:
(a)	Communicate with each TSP to see if the TSP will adjust its proposed Planned Outage, Maintenance Outage, or Rescheduled Outage schedule;
(b)	Determine if each TSP will agree to an alternative Outage schedule; or
(c)	Reject, in ERCOT's sole discretion, one or more proposed Outages, considering order of receipt and impact on the ERCOT Transmission Grid.
[NPRR857:  Replace paragraph (3) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(3)	When multiple proposed Planned Outages, Maintenance Outages, or Rescheduled Outages cause a reliability or security concern, ERCOT shall:
      (a)	Communicate with each TSP and DCTO to see if the TSP or DCTO will adjust its proposed Planned Outage, Maintenance Outage, or Rescheduled Outage schedule;
      (b)	Determine if each TSP or DCTO will agree to an alternative Outage schedule; or
      (c)	Reject, in ERCOT's sole discretion, one or more proposed Outages, considering order of receipt and impact on the ERCOT Transmission Grid.
<IP_ADDRESS>	Withdrawal of Approval of Approved Planned Outages, Maintenance Outages, and Rescheduled Outages of Transmission Facilities
(1)	If ERCOT believes it cannot meet the applicable reliability standards and has exercised reasonable options, ERCOT may contact the TSP for more information prior to its withdrawal of the approval for a Planned Outage, Maintenance Outage, or Rescheduled Outage.  ERCOT shall inform the affected TSP both orally and in written or electronic form as soon as ERCOT identifies a situation that may lead to the withdrawal of ERCOT's approval.  If ERCOT withdraws its approval, the TSP may submit a new request for approval of the Planned Outage or Maintenance Outage schedule provided the new request meets the submittal requirements for Outage Scheduling.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	If ERCOT believes it cannot meet the applicable reliability standards and has exercised reasonable options, ERCOT may contact the TSP or DCTO for more information prior to its withdrawal of the approval for a Planned Outage, Maintenance Outage, or Rescheduled Outage.  ERCOT shall inform the affected TSP or DCTO both orally and in written or electronic form as soon as ERCOT identifies a situation that may lead to the withdrawal of ERCOT's approval.  If ERCOT withdraws its approval, the TSP or DCTO may submit a new request for approval of the Planned Outage or Maintenance Outage schedule provided the new request meets the submittal requirements for Outage Scheduling.
(2)	In determining whether to withdraw approval, ERCOT shall duly consider whether the Planned Outage, Maintenance Outage, or Rescheduled Outage affects public infrastructure if ERCOT is made aware of such potential impacts by the TSP (e.g., impacts on highways, ports, municipalities, and counties).
[NPRR857:  Replace paragraph (2) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(2)	In determining whether to withdraw approval, ERCOT shall duly consider whether the Planned Outage, Maintenance Outage, or Rescheduled Outage affects public infrastructure if ERCOT is made aware of such potential impacts by the TSP or DCTO (e.g., impacts on highways, ports, municipalities, and counties).
(3)	Prior to withdrawing the approval of a High Impact Outage (HIO) submitted with greater than 90-days' notice, ERCOT shall coordinate with the TSP and may convert the Planned Outage to a Rescheduled Outage.  The Rescheduled Outage shall retain the same priority as the original Planned Outage.  ERCOT shall attempt to keep the Outage within the same calendar month.
[NPRR857:  Replace paragraph (3) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(3)	Prior to withdrawing the approval of a High Impact Outage (HIO) submitted with greater than 90-days' notice, ERCOT shall coordinate with the TSP or DCTO and may convert the Planned Outage to a Rescheduled Outage.  The Rescheduled Outage shall retain the same priority as the original Planned Outage.  ERCOT shall attempt to keep the Outage within the same calendar month.
<IP_ADDRESS>	Priority of Approved Planned, Maintenance, and Rescheduled Outages
(1)	In considering TSP requests, ERCOT shall give priority to Planned Outages, Maintenance Outages, and Rescheduled Outages in the order of receipt.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	In considering TSP or DCTO requests, ERCOT shall give priority to Planned Outages, Maintenance Outages, and Rescheduled Outages in the order of receipt.
<IP_ADDRESS>	Information for Inclusion in Transmission Facilities Outage Requests
(1)	Transmission Facilities Outage requests submitted by a TSP must include the following Transmission Facilities-specific information:
      (a)	The identity of the Transmission Facilities, in the Network Operations Model, including TSP and location;
      (b)	The nature of the work, by predefined classifications, to be performed during the proposed Transmission Facilities Outage;
      (c)	The preferred start and finish dates for the proposed Transmission Planned or Maintenance Outage;
      (d)	The time required to: (i) finish the Transmission Planned Outage or  Maintenance Outage and (ii) restore the Transmission Facilities to normal operation;
      (e)	Primary and alternate telephone numbers for the TSP's Single Point of Contact, as described in Section <IP_ADDRESS>, Single Point of Contact, and the name of the individual submitting the information;
      (f)	The scheduling flexibility (i.e., the earliest start date and the latest finish date for the Outage);
      (g)	Any Transmission Facilities that must be out of service to facilitate the TSP's request;
      (h)	Any remedial actions or special protection systems necessary during the Outage and the contingency that would require the remedial action or relay action; and
      (i)	Any other relevant information related to the proposed Outage or any unusual risks affecting the schedule.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	Transmission Facilities Outage requests submitted by a TSP or a DCTO must include the following Transmission Facilities-specific information:
      (a)	The identity of the Transmission Facilities, in the Network Operations Model, including TSP or DCTO and location;
      (b)	The nature of the work, by predefined classifications, to be performed during the proposed Transmission Facilities Outage;
      (c)	The preferred start and finish dates for the proposed Transmission Planned or Maintenance Outage;
      (d)	The time required to: (i) finish the Transmission Planned Outage or  Maintenance Outage and (ii) restore the Transmission Facilities to normal operation;
      (e)	Primary and alternate telephone numbers for the TSP's or DCTO's Single Point of Contact, as described in Section <IP_ADDRESS>, Single Point of Contact, and the name of the individual submitting the information;
      (f)	The scheduling flexibility (i.e., the earliest start date and the latest finish date for the Outage);
      (g)	Any Transmission Facilities that must be out of service to facilitate the TSP's or DCTO's request;
      (h)	Any remedial actions or special protection systems necessary during the Outage and the contingency that would require the remedial action or relay action; and
      (i)	Any other relevant information related to the proposed Outage or any unusual risks affecting the schedule.
<IP_ADDRESS>	Additional Information Requests
(1)	The requesting TSP shall comply with any ERCOT requests for more information about, or for clarification of, the information submitted by the TSP for a proposed Outage.
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	The requesting TSP or DCTO shall comply with any ERCOT requests for more information about, or for clarification of, the information submitted by the TSP or DCTO for a proposed Outage.
<IP_ADDRESS>	Evaluation of Transmission Facilities Planned Outage or Maintenance Outage Requests
(1)	ERCOT shall evaluate requests, approve, or reject Transmission Facilities Planned Outages and Maintenance Outages according to the requirements of this section.  ERCOT may approve Outage requests provided the Outage in combination with other proposed Outages does not cause a violation of applicable reliability standards.  ERCOT shall reject Outage requests that do not meet the submittal timeline specified in Section <IP_ADDRESS>, Submittal Timeline for Transmission Facility Outage Requests.  ERCOT shall consider the following factors in its evaluation:
(a)	Forecasted conditions during the time of the Outage;
(b)	Outage plans submitted by Resource Entities and TSPs under Section 3.1, Outage Coordination;
[NPRR857:  Replace item (b) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
      (b)	Outage plans submitted by Resource Entities, TSPs, and DCTOs under Section 3.1, Outage Coordination;
(c)	Forced Outages of Transmission Facilities;
(d)	Potential for the proposed Outages to cause irresolvable transmission overloads or voltage supply concerns based on the indications from contingency analysis software;
(e)	Potential for the proposed Outages to cause SSR vulnerability to Generation Resources that do not have SSR Mitigation in the event of five or six concurrent transmission Outages;
(f)	Previously approved Planned Outages, Maintenance Outages, and Rescheduled Outages;
(g)	Impacts on the transfer capability of Direct Current Ties (DC Ties); and
(h)	Good Utility Practice for Transmission Facilities maintenance.
(2)	When ERCOT approves a Maintenance Outage, ERCOT shall coordinate the timing of the appropriate course of action with the requesting TSP.
[NPRR857:  Replace paragraph (2) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(2)	When ERCOT approves a Maintenance Outage, ERCOT shall coordinate the timing of the appropriate course of action with the requesting TSP or DCTO.
(3)	When ERCOT identifies that an HIO has been submitted with 90-days or less notice, ERCOT may coordinate with TSP to make reasonable efforts to minimize the impact.
[NPRR857:  Replace paragraph (3) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(3)	When ERCOT identifies that an HIO has been submitted with 90-days or less notice, ERCOT may coordinate with the TSP or DCTO to make reasonable efforts to minimize the impact.
<IP_ADDRESS>	Submittal Timeline for Transmission Facility Outage Requests

(1)	TSPs shall submit all requests for Planned Outages and Maintenance Outages or changes to existing approved Outages of Transmission Elements in the Network Operations Model to ERCOT no later than the minimum amount of time between the submittal of a request to ERCOT for approval of a proposed Outage and the scheduled start date of the proposed Outage, according to the following table:
[NPRR857:  Replace paragraph (1) above with the following upon system implementation and satisfying the following conditions: (1) Southern Cross provides ERCOT with funds to cover the entire estimated cost of the project; and (2) Southern Cross has signed an interconnection agreement with a TSP and the TSP gives ERCOT written notice that Southern Cross has provided it with:  (a) Notice to proceed with the construction of the interconnection; and (b) The financial security required to fund the interconnection facilities:]
(1)	TSPs and DCTOs shall submit all requests for Planned Outages and Maintenance Outages or changes to existing approved Outages of Transmission Elements in the Network Operations Model to ERCOT no later than the minimum amount of time between the submittal of a request to ERCOT for approval of a proposed Outage and the scheduled start date of the proposed Outage, according to the following table:

Type of Outage
Minimum amount of time between the Outage request  and the scheduled start date of the proposed Outage:
Minimum amount of time between any change to an Outage request and the scheduled end date an existing Outage:
Forced Outage
Immediate
Immediate
Maintenance Outage Level I
Immediate
Immediate
Maintenance Outage Level II
Two days [[1]]
Two days [[1]]
Maintenance Outage Level III
Three days
Three days
Planned Outage
Three days
Three days
Simple Transmission Outage
One day
One day
Note:
1.	For reliability purposes, ERCOT may reduce to one day on a case-by-case basis.
<IP_ADDRESS>	Transmission Report
(1)	ERCOT shall post on the MIS Secure Area:
(a)	Within one hour of receipt by ERCOT, all Transmission Facilities Outages that have been submitted into the ERCOT Outage Scheduler, excluding Private Use Network transmission Outages;
(b) 	Within one hour of a change of an Outage, all Transmission Facilities Outages, excluding Private Use Network transmission Outages;
(c) 	Once each day, Outage Scheduler notes related to the coordination of Outages;
(d)	At least annually, an updated list of High Impact Transmission Elements (HITEs) pursuant to Section 3.1.8, High Impact Transmission Element (HITE) Identification; and
(e)	Once each day, list of HIOs submitted with 90-days or less notice that are accepted or approved.
3.1.6	Outages of Resources Other than Reliability Resources
(1)	ERCOT shall accept all Outage schedules and changes to Outage schedules for a Resource other than a reliability Resource submitted to ERCOT more than 45 days before the proposed start date of the Outage.
(2)	If a Resource Entity plans to start a Planned or Maintenance Outage within 45 days that has not been previously included in the Resource's written Planned Outage and Maintenance Outage plan, then the Resource Entity must immediately notify ERCOT and include in its notice whether the Outage is a Forced Outage, Maintenance (Level I, II, or III) Outage, or Planned Outage.  ERCOT's response to this notification must comply with these requirements:
(a)	ERCOT shall accept Forced and Levels I, II, and III Maintenance Outage proposals, and ERCOT shall coordinate the Outages within the time frames specified in these Protocols.
(b)	ERCOT shall approve Planned Outage proposals, except that ERCOT shall reject an Outage proposal if it will impair ERCOT's ability to meet applicable reliability standards and other solutions cannot be exercised.
(c)	ERCOT shall accept Forced and Maintenance Outage plans from a Qualifying Facility (QF) that result from the outage of the QF's thermal host facility.
[NPRR1108:  Replace Section 3.1.6 above with the following upon system implementation:]
3.1.6	Outages of Resources Other than Reliability Resources
(1)	Resource Entities should submit a request for a Resource Planned Outage as far in advance of the planned start of the Outage as is practicable but no more than 60 months in advance.
(2)	ERCOT shall approve or reject all requested Outage plans for a Resource other than a Reliability Resource submitted to ERCOT more than 45 days before the proposed start date of the Outage.
      (a)	ERCOT shall approve a requested Outage plan for a Resource other than a Reliability Resource if the proposed approval would not cause the aggregate MW of Resource Outages to exceed the Maximum Daily Resource Planned Outage Capacity at any point during the duration of the proposed Resource Outage, taking into consideration all previously approved Resource Outages.
(3)	If a Resource Entity plans to start a Planned or Maintenance Outage within 45 days, and the Resource Entity has not previously submitted a Resource Outage plan for the Outage, then the Resource Entity must immediately notify ERCOT and include in its notice whether the Outage is a Maintenance (Level I, II, or III) Outage or Planned Outage.  ERCOT's response to this notification must comply with these requirements:
      (a)	ERCOT shall accept Levels I, II, and III Maintenance Outage plans, and ERCOT shall coordinate the Outages within the time frames specified in these Protocols.
      (b)	ERCOT shall approve Planned Outage plans, except that:
            (i)	ERCOT shall reject an Outage plan if the proposed Outage would cause the aggregate MW of Resource Outages to exceed the Maximum Daily Resource Planned Outage Capacity at any point during the duration of the proposed Outage; and
            (ii)	ERCOT shall reject an Outage plan if it will impair ERCOT's ability to meet applicable reliability standards, taking into consideration all previously approved and accepted Outages, and other solutions cannot be exercised.
(4)	The Resource Entity shall not begin a Planned Outage unless it has received approval of its proposed Outage plan.
(5)	ERCOT shall accept Forced Outage plans.
(6)	Notwithstanding any other provision of this Section, ERCOT shall approve a requested Outage plan for a nuclear Generation Resource.
(7)	Notwithstanding any other provision in this Section, ERCOT shall approve an Outage plan for a Generation Resource that is part of an industrial generation facility if the plan states that the Generation Resource is part of an industrial generation facility, as described in subsection (l) of the Public Utility Regulatory Act (PURA), TEX. UTIL. CODE ANN. § 39.151 (Vernon 1998 & Supp. 2007), and that the Outage is necessitated by the operational needs of an industrial Load normally served by the Generation Resource, except that ERCOT is not required to approve the Outage plan if ERCOT determines the Outage will impair ERCOT's ability to ensure transmission security.
<IP_ADDRESS>	Receipt of Resource Requests by ERCOT
(1)	ERCOT shall acknowledge each request for approval of a Resource Planned Outage schedule within two Business Hours of the receipt of the request.  ERCOT may request additional information or seek clarification from the Resource Entity regarding the information submitted for a proposed Planned Outage or Maintenance Outage for Resource Facilities.
[NPRR1108:  Replace paragraph (1) above with the following upon system implementation:]
(1)	ERCOT shall acknowledge each request for approval of a Resource Planned Outage plan within two Business Hours of the receipt of the request.  ERCOT may request additional information or seek clarification from the Resource Entity regarding the information submitted for a proposed Planned Outage or Maintenance Outage for Resource Facilities.
<IP_ADDRESS>	Resource Outage Plan
(1)	Resource Entity Outage requests shall include the following information:
[NPRR1108:  Replace paragraph (1) above with the following upon system implementation:]
(1)	Resource Outage plans shall include the following information:
(a)	The primary and alternate phone number of the Resource Entity's Single Point of Contact for Outage Coordination;
(b)	The Resource identified by the name in the Network Operations Model;
(c)	The net megawatts of capacity the Resource Entity anticipates will be available during the Outage (if any);
(d)	The estimated start and finish dates for each Planned and Maintenance Outage;
(e)	An estimate of the acceptable deviation in the Outage schedule (i.e., the earliest start date and the latest finish date for the Outage); and
(f)	The nature of work to be performed during the Outage.
(2)	When ERCOT accepts a Maintenance Outage, ERCOT shall coordinate the timing of the appropriate course of action within the Resource-specified timeframe.  The QSE shall notify ERCOT of the Outage and coordinate the time.
<IP_ADDRESS>	Additional Information Requests
(1)	ERCOT may request additional information from a Resource Entity regarding the information submitted as part of a Resource Outage plan.  ERCOT may not unnecessarily delay requests for information in terms of the required response time.
<IP_ADDRESS>	Approval of Changes to a Resource Outage Plan
(1)	ERCOT shall accept all changes to a Resource Outage plan submitted by a Resource Entity more than 45 days before the planned start date for the Outage.  Following acceptance, where ERCOT determines that Outage requests are expected to result in a violation of an ERCOT reliability criterion or that may result in a cancellation of a Transmission Facilities Planned Outage, ERCOT may discuss such concerns with Resource Entities or QSEs in an attempt to reach a mutually agreeable resolution, including rescheduling the Outage in a manner agreeable to the Resource Entity.
(2)	A Resource Entity must request approval from ERCOT only for new Resource Outages or changes to a previously accepted planned Resource Outage scheduled to occur within 45 days of the request.
(3)	ERCOT shall approve Planned Outage and Maintenance Outage requests to occur within 45 days, except that ERCOT shall reject proposals if the Outage proposal will impair ERCOT's ability to meet applicable reliability standards.
(4)	When the scheduled work is complete, any Resource may return from a Planned Outage in accordance with Section <IP_ADDRESS>, Outage Returning Early.  ERCOT shall accept this change and, in the event that a Transmission Facilities Outage was scheduled concurrently with the affected Resource(s) Outage, ERCOT shall coordinate between the TSP and the Resource Entity to schedule a time mutually agreeable to both parties for the Resource to be On-Line.  If mutual agreement cannot be reached, then ERCOT shall decide, considering expected impact on ERCOT System security, future Outage plans, and participants.
[NPRR1108:  Replace Section <IP_ADDRESS> above with the following upon system implementation:]
<IP_ADDRESS>	Approval of Changes to a Resource Outage Plan
(1)	A Resource Entity should request approval as soon as practicable from ERCOT for all changes to a previously approved Resource Outage plan.
(2)	A Resource Entity must request approval from ERCOT for all changes to a previously approved Resource Planned Outage.
      (a)	ERCOT shall approve requests for changes to Resource Planned Outages and Maintenance Outages, except that:
            (i)	ERCOT shall reject a Resource Outage plan change request if the proposed approval would cause the aggregate MW of Resource Outages to exceed the Maximum Daily Resource Planned Outage Capacity at any point during the duration of the proposed Resource Outage; and
            (ii)	ERCOT shall reject a Resource Outage plan change request if the proposed approval will impair ERCOT's ability to meet applicable reliability standards, taking into consideration all previously approved and accepted Outages.
(3)	Following approval, where ERCOT determines that the Resource Outage plan is expected to result in a violation of an ERCOT reliability criterion or that may result in a cancellation of a Transmission Facilities Planned Outage, ERCOT may discuss such concerns with the Resource Entity or QSE in an attempt to reach a mutually agreeable resolution, including rescheduling the Outage in a manner agreeable to the Resource Entity.  If the Transmission Facilities Planned Outage was submitted after the approval of the Resource Planned Outage, the Resource Entity is not required to reschedule the Resource Outage.
(4)	When the scheduled work is complete, any Resource may return from a Planned Outage in accordance with Section <IP_ADDRESS>, Outage Returning Early.  ERCOT shall accept this change and, in the event that a Transmission Facilities Outage was scheduled concurrently with the affected Resource(s) Outage, ERCOT shall coordinate between the TSP and the Resource Entity to schedule a time mutually agreeable to both parties for the Resource to be On-Line.  If mutual agreement cannot be reached, then ERCOT shall decide, considering expected impact on ERCOT System security, future Outage plans, and participants.
<IP_ADDRESS>	Evaluation of Proposed Resource Outage
(1)	If a proposed Resource Outage, in conjunction with previously accepted Outages, would cause a violation of applicable reliability standards, ERCOT shall:
(a)	Communicate with the requesting QSE as required under Section <IP_ADDRESS>, Resource Outage Rejection Notice;
(b)	Investigate possible Constraint Management Plans (CMPs) to resolve security violations, based upon security and reliability analysis results and strive to maximize transmission usage consistent with reliable operation; and
(c)	Consider modifying the previous acceptance or approval of one or more Transmission Facilities or reliability Resource Outages, considering order of receipt and impact to the ERCOT System.
(2)	If transmission security can be maintained using an alternative considered in items (1)(b) and (1)(c) above, then ERCOT may, in its judgment, direct the selected alternatives and approve the proposed Resource Outage.
(3)	If ERCOT does not resolve transmission security issues by using the alternatives considered in items (1)(b) and (1)(c) above, then ERCOT shall reject the proposed Resource Outage.
<IP_ADDRESS>	Timelines for Response by ERCOT for Resource Outages
(1)	ERCOT shall approve, accept or reject each request in accordance with the following table:
Amount of time between a request for acceptance of a Planned Outage and the scheduled start of the proposed Outage:
ERCOT shall approve, accept or reject no later than:
Three days
ERCOT shall approve or reject within 1800 hours, two days before the start of the proposed Outage
Between four and eight days
ERCOT shall approve or reject within 1800 hours, three days prior to the start of the proposed Outage
Between nine and 45 days
Five Business Days after submission.  Planned Outages are automatically accepted if not rejected at the end of the fifth Business Day following receipt of request.
Greater than 45 days
ERCOT must accept, but ERCOT may discuss reliability and scheduling impacts to minimize cost to the ERCOT System in an attempt to accomplish minimum overall impact.  Within five Business Days, ERCOT will notify the submitter if there is a conflict with a previously scheduled Outage.
(2)	If circumstances prevent adherence to these timetables, ERCOT shall discuss the request status and reason for the delay of decision with the QSE and make reasonable attempts to mitigate the effect of the delay.
[NPRR1108:  Replace Section <IP_ADDRESS> above with the following upon system implementation:]
<IP_ADDRESS>	Timelines for Response by ERCOT for Resource Planned Outages
(1)	ERCOT shall approve or reject each request in accordance with the following table:
Amount of time between a request for approval of a Planned Outage and the scheduled start of the proposed Outage:
Maximum duration of a Planned Outage that may be approved with this lead time:
ERCOT shall approve or reject no later than:
Three days
Seven days
ERCOT shall approve or reject by 1800 hours, two days before the start of the proposed Outage
Between four and eight days
Seven days
ERCOT shall approve or reject by 1800 hours, three days prior to the start of the proposed Outage
Between nine and 15 days

15 days
ERCOT shall approve or reject four days before the start of the requested Outage
Between 16 and 45 days
180 days
ERCOT shall approve or reject within five Business Days after submission
Greater than 45 days but less than 60 months
180 days
ERCOT shall approve or reject within five Business Days after submission
Greater than 60 months
180 days
ERCOT shall approve or reject within five Business Days once the Outage start dates are within the 60 month window
(2)	If circumstances prevent adherence to these timetables, ERCOT shall discuss the request status and reason for the delay of decision with the QSE and make reasonable attempts to mitigate the effect of the delay.  Furthermore, in its sole discretion, ERCOT may approve Planned Outage durations that exceed the maximum durations prescribed in the table above.
(3)	The maximum duration of Planned Outages does not apply for Resource Outages under a Notification of Suspension of Operations pursuant to Section <IP_ADDRESS>, Notification of Suspension of Operations.
<IP_ADDRESS>	Delay
(1)	ERCOT may delay its acceptance, approval or rejection of a proposed Planned Outage schedule if the requesting Resource Entity has not submitted sufficient or complete information within the time frames set forth in this Section 3.1.6, Outages of Resources Other Than Reliability Resources.  Review periods for Planned Outage consideration do not commence until sufficient and complete information is submitted to ERCOT as described in Section <IP_ADDRESS>, Resource Outage Plan.
[NPRR1108:  Replace paragraph (1) above with the following upon system implementation:]
(1)	ERCOT may delay its approval or rejection of a proposed Planned Outage plan if the requesting Resource Entity has not submitted sufficient or complete information within the time frames set forth in this Section 3.1.6, Outages of Resources Other Than Reliability Resources.  Review periods for Planned Outage consideration do not commence until sufficient and complete information is submitted to ERCOT as described in Section <IP_ADDRESS>, Resource Outage Plan.
<IP_ADDRESS>	Resource Outage Rejection Notice
(1)	If ERCOT rejects a request for a Planned Outage, ERCOT shall provide the QSE a written or electronic rejection notice that includes:
      (a)	Specific reasons causing the rejection; or
      (b)	Possible remedies or Resource schedule revisions, if any, that might mitigate the basis for rejection.
(2)	ERCOT may reject a Planned Outage of Resource facilities only:
      (a)	To protect the reliability or security of the ERCOT System;
      (b)	Due to insufficient information regarding the Outage;
      (c)	Due to failure to comply with submittal process requirements, as specified in these Protocols; or
[NPRR1108:  Insert paragraph (d) below upon system implementation and renumber accordingly:]
      (d)	To stay within the Maximum Daily Resource Planned Outage Capacity; or
      (d)	As specified elsewhere in these Protocols.
(3)	When multiple proposed Planned Outages or Maintenance Outages cause a known capacity conflict, ERCOT shall:
      (a)	Communicate with each QSE to see if the QSE will adjust its proposed Planned Outage schedule;
      (b)	Determine if each QSE will agree to an alternative Outage schedule; or
      (c)	Reject, in ERCOT's sole discretion, one or more proposed Outages, considering order of receipt and impact to the ERCOT System.
<IP_ADDRESS>	Withdrawal of Approval or Acceptance and Rescheduling of Approved or Accepted Planned Outages of Resource Facilities
[NPRR1108:  Replace Section <IP_ADDRESS> title above with the following upon system implementation:]
<IP_ADDRESS>	Withdrawal of Approval and Rescheduling of Approved Planned Outages of Resource Facilities
(1)	If ERCOT believes it cannot meet applicable reliability standards and has exercised all other reasonable options, and the delayed initiation of, or early termination of, one or more approved or accepted Resource Outages not addressed by Section <IP_ADDRESS>, Outage Coordination of Potential Transmission Emergency Conditions, could resolve the situation, then ERCOT shall issue an Advance Action Notice (AAN) pursuant to Section <IP_ADDRESS>.1.1, Advance Action Notice.
[NPRR1108:  Replace paragraph (1) above with the following upon system implementation:]
(1)	If ERCOT believes it cannot meet applicable reliability standards and has exercised all other reasonable options, and the delayed initiation of, or early termination of, one or more approved Resource Outages not addressed by Section <IP_ADDRESS>, Outage Coordination of Potential Transmission Emergency Conditions, could resolve the situation, then ERCOT shall issue an Advance Action Notice (AAN) pursuant to Section <IP_ADDRESS>.1.1, Advance Action Notice.
            (a)	The AAN shall describe the reliability problem, the date and time that the possible Emergency Condition would begin, the date and time that the possible Emergency Condition would end, and a summary of the actions ERCOT believes it might take, including, if applicable, the amount of capacity it would seek from an Outage Adjustment Evaluation (OAE) and OSAs.  The AAN must state the time at which ERCOT will execute an OAE, if an OAE is deemed necessary.
            (b)	ERCOT shall issue the AAN a minimum of 24 hours prior to performing an OAE.  Additionally, unless impracticable pursuant to paragraph (3)(f) below, the OAE should not be performed until eight Business Hours have elapsed following issuance of the AAN.  ERCOT shall not issue an OSA under this Section unless it has first completed an OAE.
            (c)	Following the AAN, ERCOT may communicate with Market Participants about the reliability problem, however, ERCOT may not provide information about market conditions to a subset of Market Participants that is not generally available to all Market Participants.
            (d)	As conditions change, ERCOT shall, to the extent practicable, update the AAN in order to provide simultaneous notice to Market Participants.
            (e)	This section does not limit Transmission and/or Distribution Service Provider (TDSP) access to ERCOT data and communications.
(2)	QSEs shall update their Resource COPs and the Outage Scheduler to the best of their ability before the time stated in the AAN when ERCOT will execute the OAE, to reflect any decisions to voluntarily delay or cancel any Outage prior to the OAE so as to remove the Outage from OAE and OSA consideration.
(3)	If, after the planned OAE execution time has passed as noted in paragraph (1)(b) above, ERCOT continues to forecast an inability to meet applicable reliability standards after the updates to the Resource COPs and Outage Schedules, ERCOT may conduct an OAE and issue one or more OSAs.
            (a)	ERCOT may contact QSEs representing Resources to be included in the OAE for more information prior to conducting an OAE or issuing an OSA.
            (b)	ERCOT may not consider nuclear-powered Generation Resources for an OSA.
            (c)	Prior to the execution of an OAE, a QSE may notify ERCOT that a specific Resource cannot be considered in the OAE, for all or part of the period covered by the AAN, due to Resource reliability, compliance with contractual warranty obligations, or other reasons beyond the QSE's control.  ERCOT will not consider this Resource in the OAE.
[NPRR1108:  Replace paragraph (c) above with the following upon system implementation:]
            (c)	Prior to the execution of an OAE, a QSE may notify ERCOT that a specific Resource cannot be considered in the OAE, for all or part of the period covered by the AAN, due to Resource reliability, compliance with contractual warranty obligations, operational needs of a QF's thermal host facility, or other reasons beyond the QSE's control.  ERCOT will not consider this Resource in the OAE.
            (d)	In order to determine which Outages to delay, ERCOT shall first consider the Outage duration, dividing the Outages in categories of zero to two days, two to four days, four to seven days, or more than seven days, then withdraw approval or acceptance on a last in, first out basis within that duration category, so that shorter Outages are delayed first, and the timing of Outage submissions is considered within that category.
[NPRR1108:  Replace paragraph (d) above with the following upon system implementation:]
      (d)	In order to determine which Outages to delay, ERCOT shall first consider the Outage duration, dividing the Outages in categories of zero to two days, two to four days, four to seven days, or more than seven days, then withdraw approval on a last in, first out basis within that duration category, so that shorter Outages are delayed first, and the timing of Outage submissions is considered within that category.
            (e)	ERCOT may only issue an OSA to the QSE for a Resource that has a COP Resource Status of OUT within the forecasted Emergency Condition described above in this section.
            (f)	If the Resource Outage for which the OSA would be issued is scheduled to begin before eight Business Hours have elapsed following issuance of the AAN, ERCOT may issue the OSA prior to the beginning of the Resource Outage after the end of the 24-hour notice period.
            (g)	Following the receipt of an OSA, during the OSA Period:
                  (i)	The QSE for the Resource may choose to show the Resource as OFF in the COP or may elect to leave the Resource On-Line due to equipment or reliability concerns or if the Resource Category is coal or lignite.  If the Resource remains On-Line, it must utilize a status of ONRUC.
                  (ii)	If the Resource remains On-Line pursuant to paragraph (i) above, it must remain at Low Sustained Limit (LSL) unless deployed above LSL by Security-Constrained Economic Dispatch (SCED).  In addition, the QSE must update the Resource's Energy Offer Curve to $4,500 for all MWs above LSL.
[NPRR930:  Replace paragraph (ii) above with the following upon system implementation:]
                  (ii)	If the Resource remains On-Line pursuant to paragraph (i) above, it must remain at Low Sustained Limit (LSL) unless deployed above LSL by Security-Constrained Economic Dispatch (SCED).
                  (iii)  	If the Resource chooses to show the Resource as OFF in the COP, the Resource may not be self-committed during the OSA Period and shall only be available for commitment by Reliability Unit Commitment.
(4)	ERCOT shall work in good faith with the QSEs to reschedule any delayed or canceled Outages resulting from an AAN under paragraph (1) above, regardless of whether the Resource took voluntary actions or received an OSA.  The Outage must be rescheduled so that it is completed within 120 days of the end of the OSA Period.
[NPRR1108:  Replace paragraph (4) above with the following upon system implementation:]
(4)	ERCOT shall work in good faith with the QSEs to reschedule any delayed or canceled Outages resulting from an AAN under paragraph (1) above, regardless of whether the Resource took voluntary actions or received an OSA.  The Outage must be rescheduled so that it is completed within 120 days of the end of the OSA Period.  ERCOT, in its sole discretion, may approve any Outage that is rescheduled due to an AAN or OSA even if it would cause the aggregate MW of approved Resource Outages to exceed the Maximum Daily Resource Planned Outage Capacity.
            (a)	If ERCOT issues an OSA, the QSE may submit a new request for approval of the Planned Outage schedule, however the new Outage may not begin prior to the end time of the OSA Period.
            (b)	If a transmission Outage was scheduled in coordination with a Resource Outage that is delayed, ERCOT shall also delay that transmission Outage when necessary.
(5)	If insufficient capacity to meet the need described in the AAN is made available through the processes described in paragraphs (2) and (3) above, ERCOT may contact QSEs having Resources with a Resource Status of OUT in the most recently submitted COP to determine if it is feasible for the Outage of those Resources to be ended by the time of the possible Emergency Condition described in the AAN.  ERCOT may issue an OSA to the QSE for any Resource that the QSE agrees can feasibly be returned to service during the period of the possible Emergency Condition described in the AAN.
(6)	If system conditions change such that the need described in the AAN increases, ERCOT shall update the AAN and may repeat the process described in this section.  For any subsequent iterations of this process, ERCOT shall issue the updated AAN with as much lead time as is practical prior to starting any subsequent OAE, but with a minimum of two hours' notice.
(7)	ERCOT must perform a planning assessment to determine whether to issue an AAN or OSA.  The planning assessment may not assume total renewable production lower than the sum of the selected Wind-powered Generation Resource Production Potential (WGRPP) and PhotoVoltaic Generation Resource Production Potential (PVGRPP) forecasts for each hour less any reasonably expected severe weather impacts.  The available capacity in ERCOT's planning assessment must include targeted reserve levels and include forecasted capacity available through DC Tie imports or curtailment of DC Tie exports, forecasted capacity provided from Settlement Only Distributed Generators (SODGs) and Settlement Only Transmission Generators (SOTGs), and forecasted capacity from price-responsive Demand based on information reported to ERCOT in accordance with Section <IP_ADDRESS>.1, Reporting of Demand Response.  ERCOT must post the following inputs of the planning assessment to the ERCOT website within an hour of issuing an AAN, including but not limited to:
            (a)	The Load forecast;
            (b)	Load forecast vendor selection;
            (c)	Wind forecast;
            (d)	Wind forecast vendor selection;
            (e)	Solar forecast;
            (f)	Solar forecast vendor selection;
            (g)	Expected severe weather impacts forecast;
            (h)	Targeted reserve levels;
            (i)	DC Tie import forecast;
            (j)	DC Tie export curtailment forecast;
            (k)	SODG and SOTG forecasts;
            (l)	The forecast of capacity provided by price-responsive Demand;
            (m)	Any aggregate derating of Resource(s) and/or Forced Outage assumptions in total MWs; and
            (n)	Any aggregate fuel derating assumptions in total MWs.
[NPRR995:  Replace paragraph (7) above with the following upon system implementation:]
(7)	ERCOT must perform a planning assessment to determine whether to issue an AAN or OSA.  The planning assessment may not assume total renewable production lower than the sum of the selected Wind-powered Generation Resource Production Potential (WGRPP) and PhotoVoltaic Generation Resource Production Potential (PVGRPP) forecasts for each hour less any reasonably expected severe weather impacts.  The available capacity in ERCOT's planning assessment must include targeted reserve levels and include forecasted capacity available through DC Tie imports or curtailment of DC Tie exports, forecasted capacity provided from Settlement Only Distributed Generators (SODGs), Settlement Only Transmission Generators (SOTGs), Settlement Only Distribution Energy Storage Systems (SODESSs), and Settlement Only Transmission Energy Storage Systems (SOTESSs), and forecasted capacity from price-responsive Demand based on information reported to ERCOT in accordance with Section <IP_ADDRESS>.1, Reporting of Demand Response.  ERCOT must post the following inputs of the planning assessment to the ERCOT website within an hour of issuing an AAN, including but not limited to:
      (a)	The Load forecast;
      (b)	Load forecast vendor selection;
      (c)	Wind forecast;
      (d)	Wind forecast vendor selection;
      (e)	Solar forecast;
      (f)	Solar forecast vendor selection;
      (g)	Expected severe weather impacts forecast;
      (h)	Targeted reserve levels;
      (i)	DC Tie import forecast;
      (j)	DC Tie export curtailment forecast;
      (k)	SODG, SOTG, SODESS, and SOTESS forecasts;
      (l)	The forecast of capacity provided by price-responsive Demand;
      (m)	Any aggregate derating of Resource(s) and/or Forced Outage assumptions in total MWs; and
      (n)	Any aggregate fuel derating assumptions in total MWs.
(8)	Notwithstanding anything in this Section, ERCOT need not comply with any other requirement in this Section if the occurrence of an unforeseen Real-Time condition requires that ERCOT withdraw approval of one or more Resource Outages in order to meet applicable reliability standards.  The unforeseen Real-Time condition cannot be the result of changes that Ancillary Services are procured to address.  In exercising its discretion under this paragraph, ERCOT is not required to issue an AAN or OAE before issuing an OSA, but shall:
            (a)	Issue the OSA to the QSE of the Resource for the purpose of make whole compensation; and
            (b)	Present the justification for the out of market action to the Technical Advisory Committee (TAC) at its next meeting that is at least 14 Business Days after the OSA.
<IP_ADDRESS>	Opportunity Outage
(1)	Opportunity Outages for Resources are a special category of Planned Outages that may be approved by ERCOT when a specific Resource has been forced Off-Line due to a Forced Outage and the Resource has been previously accepted for a Planned Outage during the next eight days.
[NPRR1108:  Replace paragraph (1) above with the following upon system implementation:]
(1)	Opportunity Outages for Resources are a special category of Planned Outages that may be approved by ERCOT when a specific Resource has been forced Off-Line due to a Forced Outage and the Resource has been previously approved for a Planned Outage during the next two days.
(2)	When a Forced Outage occurs on a Resource that has an accepted or approved Outage scheduled within the following eight days, the Resource may remain Off-Line and start the accepted or approved Outage earlier than scheduled.  The QSE must give as much notice as practicable to ERCOT.
[NPRR1108:  Replace paragraph (2) above with the following upon system implementation:]
(2)	When a Forced Outage occurs on a Resource that has an approved Outage scheduled within the following two days, the Resource may remain Off-Line and start the approved Outage earlier than scheduled.  The QSE must give as much notice as practicable to ERCOT.
(3)	Opportunity Outages of Transmission Facilities may be approved by ERCOT when a specific Resource is Off-Line due to a Forced, Planned or Maintenance Outage.  A TSP may request an Opportunity Outage at any time.
(4)	When an Outage occurs on a Resource that has an approved Transmission Facilities Opportunity Outage request on file, the TSP may start the approved Outage as soon as practical after receiving authorization to proceed by ERCOT.  ERCOT must give as much notice as practicable to the TSP.
<IP_ADDRESS>	Outage Returning Early
(1)	A Resource that completes a Planned Outage early and wants to resume operation shall notify ERCOT of the early return prior to resuming service by making appropriate entries in the Current Operating Plan or Outage Scheduler if applicable as much in advance as practicable, but not later than at least two hours prior to beginning startup.  Within two hours of receiving such request, ERCOT shall either:
(a) 	Approve the request unless, as a result of complying with the request, ERCOT cannot maintain system reliability or security with the Resource injection.  In such a case, ERCOT shall issue a Verbal Dispatch Instruction (VDI) to the Resource's QSE to stay Off-Line; or
(b) 	Coordinate between the TSP and Resource Entity to schedule a time agreeable to both parties for the Resource to be Off-Line in the event if that a Transmission Facilities Outage requires the affected Resource to be Off-Line. If mutual agreement is not reached, then ERCOT shall decide on the appropriate time, after considering expected impacts on system security, future Outage plans, and participants and issue a VDI to the Resource's QSE to stay Off-Line.
(2)	Before an early return from an Outage, a Resource Entity or QSE may inquire of ERCOT whether the Resource is expected to be decommitted by ERCOT upon its early return.  If a Resource Entity or QSE is notified by ERCOT that the Resource will be decommitted if it returns early and the Resource Entity or QSE starts the Resource within the previously accepted or approved Outage period, then the QSE representing the Resource will not be paid any decommitment compensation as otherwise would be provided for in Section 5.7, Settlement for RUC Process.
<IP_ADDRESS>	Resource Coming On-Line
(1)	Before start-up and synchronizing On-Line, a Resource Entity or QSE may inquire of ERCOT whether the Resource is expected to be decommitted by ERCOT upon its coming On-Line.  If a Resource Entity or QSE is notified by ERCOT that the Resource will be decommitted if the Resource comes On-Line and the Resource Entity or QSE starts the Resource, then the QSE representing the Resource will not be paid any decommitment compensation as otherwise would be provided for in Section 5.7.3, Payment When ERCOT Decommits a QSE-Committed Resource.
[NPRR1108:  Insert Section <IP_ADDRESS> below upon system implementation and renumber accordingly:]
<IP_ADDRESS>	Maximum Daily Resource Planned Outage Capacity
(1)	ERCOT shall calculate a maximum capacity of Resource Planned Outages, excluding Outages of nuclear-powered generation facilities and Outages of Qualifying Facilities that are subject to the exemption in paragraph (7) of Section 3.1.6, Outages of Resources Other than Reliability Resources, that should be allowed on each day of the next 60 months.
      (a)	For days more than seven days ahead of the Operating Day, the calculation of this Maximum Daily Resource Planned Outage Capacity will be based on seasonal assumptions, planned Resources that have met the criteria in Planning Guide Section 6.9, Addition of Proposed Generation to the Planning Models, Planned Outages of nuclear Generation Resources, Planned Outages of Qualifying Facilities that are subject to the exemption in paragraph (7) of Section 3.1.6, and the long-term load forecast.  ERCOT shall update the calculation of the Maximum Daily Resource Planned Outage Capacity for the next 60 months twice per month.
      (b)	For days that are seven days or less prior to the Operating Day, the calculation of this Maximum Daily Resource Planned Outage Capacity will be based on the inputs used for the planning assessment for an Outage Adjustment Evaluation described in Section <IP_ADDRESS>, Withdrawal of Approval and Rescheduling of Approved Planned Outages of Resource Facilities.  ERCOT shall update the calculation of the Maximum Daily Resource Planned Outage Capacity for each hour of the next seven days on a rolling daily basis.
      (c)	ERCOT shall post the Maximum Daily Resource Planned Outage Capacity and aggregate MW of approved Resource Planned Outages at least twice per day on the ERCOT website for each day of the next 60 months.
      (d)	ERCOT shall post the Maximum Daily Resource Planned Outage Capacity and aggregate MW of approved Resource Planned Outages hourly on the ERCOT website for each hour of the next seven days.
(2)	ERCOT may adjust the Maximum Daily Resource Planned Outage Capacity if, at any point in time, the actual aggregate Forced Outages and Maintenance Outages exceed the amount that is used in the assessment of the Maximum Daily Resource Planned Outage Capacity.
(3)	ERCOT shall post on the ERCOT website the methodology it uses to calculate the Maximum Daily Resource Planned Outage Capacity in accordance with the parameters established by paragraphs (1) and (2) above.  The methodology and any revisions thereto shall be approved by the ERCOT Board of Directors.  ERCOT shall issue a Market Notice describing any revision and the justification for such revision and shall provide at least 14 days for stakeholder comment on the proposed revision unless ERCOT determines that, due to an actual or anticipated Emergency Condition, a shorter comment period is warranted.  Upon adopting a change to the methodology, ERCOT shall post the revised methodology on the ERCOT website and issue a Market Notice announcing the posting.
<IP_ADDRESS>	Distribution Facility Outages Impacting Distribution Generation Resources and Distribution Energy Storage Resources
(1)       	A Distribution Service Provider (DSP) must notify the party designated by the Distribution Generation Resource (DGR) or Distribution Energy Storage Resource (DESR) (Resource Entity or QSE) if the DSP plans to take an outage on any distribution facility that will impact the operation of a DGR or DESR.  The Resource Entity for the DGR or DESR shall submit a Planned or Maintenance Resource Outage, as appropriate, to reflect the unavailability of the Resource due to the DSP outage.  ERCOT may not reject a DGR or DESR Outage taken due to a DSP system outage, nor may ERCOT require the DSP to reschedule the outage.  However, ERCOT may consult with the DSP about rescheduling the outage.
3.1.7	Reliability Resource Outages
(1)	ERCOT shall evaluate requests for approval of an Outage of a Reliability Resource to determine if any one or a combination of proposed Outages may cause ERCOT to violate applicable reliability standards.  ERCOT's evaluations shall take into consideration factors including the following:
[NPRR1108:  Replace paragraph (1) above with the following upon system implementation:]
(1)	ERCOT shall evaluate requests for approval of an Outage of a Reliability Resource to determine if any one or a combination of proposed Outages may cause ERCOT to violate applicable reliability standards or exceed the Maximum Daily Resource Planned Outage Capacity.  ERCOT's evaluations shall take into consideration factors including the following:
(a)	Load forecast;
(b)	All other known Outages; and
(c)	Potential for the proposed Outages to cause irresolvable transmission overloads or voltage supply concerns based on the indications from contingency analysis software.
<IP_ADDRESS>	Timelines for Response by ERCOT on Reliability Resource Outages
(1)	ERCOT shall approve requests for Planned Outages of Reliability Resources unless, in ERCOT's determination, the requested Planned Outage would cause ERCOT to violate applicable reliability standards.  ERCOT shall approve or reject each request in accordance with the following table:
Amount of time between a Request for approval of a proposed Planned Outage and the scheduled start date of the proposed Outage:
ERCOT shall approve or reject no later than:
No less than 30 days
15 days before the start of the proposed Outage
Greater than 45 days
30 days before the start of the proposed Outage

[NPRR1108:  Replace paragraph (1) above with the following upon system implementation:]
(1)	ERCOT shall approve requests for Planned Outages of Reliability Resources unless, in ERCOT's determination, the requested Planned Outage would cause ERCOT to violate applicable reliability standards or exceed the Maximum Daily Resource Planned Outage Capacity.  ERCOT shall approve or reject each request in accordance with the following table:
Amount of time between a Request for approval of a proposed Planned Outage and the scheduled start date of the proposed Outage:
ERCOT shall approve or reject no later than:
No less than 30 days
Five Business Days after submission
Greater than 45 days
Five Business Days after submission

(2)	ERCOT shall approve requests for Outages, other than Forced Outages or Level I Maintenance Outages, of Reliability Resources unless, in ERCOT's determination, the requested Outage would cause ERCOT to violate applicable reliability standards.  ERCOT shall approve or reject Maintenance Outages on Reliability Resources as follows:
Amount of time between a Request for approval of a proposed Outage and the scheduled start date of the proposed Outage:
ERCOT shall approve or reject no later than:
Between three and eight days
0000 hours, two days before the start of the proposed Outage
Between nine and 30 days

Four days before the start of the proposed Outage

[NPRR1108:  Replace paragraph (2) above with the following upon system implementation:]
(2)	ERCOT shall approve requests for Outages, other than Forced Outages or Level I Maintenance Outages, of Reliability Resources unless, in ERCOT's determination, the requested Outage would cause ERCOT to violate applicable reliability standards or exceed the Maximum Daily Resource Planned Outage Capacity.  ERCOT shall approve or reject Maintenance Outages on Reliability Resources as follows:
Amount of time between a Request for approval of a proposed Outage and the scheduled start date of the proposed Outage:
ERCOT shall approve or reject no later than:
Between three and eight days
0000 hours, two days before the start of the proposed Outage
Between nine and 30 days

Four days before the start of the proposed Outage

(3)	ERCOT shall not be deemed to have approved the Outage request associated with the Planned Outage until ERCOT notifies the Single Point of Contact of its approval.  ERCOT shall transmit approvals electronically.
[NPRR1108:  Insert paragraph (4) below upon system implementation:]
(4)	ERCOT, at its sole discretion, may relax the submission timing requirements in this Section.
<IP_ADDRESS>	Changes to an Approved Reliability Resource Outage Plan
(1)	Once ERCOT has approved a Reliability Resource Planned Outage, the Resource Entity for the Reliability Resource may submit to ERCOT a change request by entering the change in the Outage Scheduler no later than 30 days before the scheduled start date of the approved Outage.  ERCOT shall approve or reject the proposed change within 15 days of receiving the change request form.  ERCOT may, at its discretion, relax the 30 day Notice requirement.
3.1.8	High Impact Transmission Element (HITE) Identification
(1)	ERCOT, with input from Market Participants, shall develop a list of HITEs for review and approval at least annually by the Technical Advisory Committee (TAC).
3.2 	Analysis of Resource Adequacy
3.2.1	Calculation of Aggregate Resource Capacity
(1)	ERCOT shall use Outages in the Outage Scheduler and, when applicable, the Resource Status from the Current Operating Plan (COP) to calculate the aggregate capacity from Generation Resources and Load Resources projected to be available in the ERCOT Region and in Forecast Zones in ERCOT.  "Forecast Zones" have the same boundaries as the 2003 ERCOT Congestion Management Zones (CMZs).  Each Resource will be mapped to a Forecast Zone during the registration process.
[NPRR1014 and NPRR1029:  Replace applicable portions of paragraph (1) above with the following upon system implementation:]
(1)	ERCOT shall use Outages in the Outage Scheduler and, when applicable, the Resource Status from the Current Operating Plan (COP) to calculate the aggregate capacity from Generation Resources, Energy Storage Resources (ESRs), and Load Resources projected to be available in the ERCOT Region and in Forecast Zones in ERCOT.  "Forecast Zones" have the same boundaries as the 2003 ERCOT Congestion Management Zones (CMZs).  Each Resource will be mapped to a Forecast Zone during the registration process.
(2)	Monthly, ERCOT shall calculate the aggregate weekly Generation Resource capacity for the ERCOT Region and the Forecast Zones projected to be available during the ERCOT Region peak Load hour of each week for the following 36 months, starting with the second week and the aggregate weekly Load Resource capacity for the ERCOT Region projected to be available during the ERCOT Region peak Load hour of each week for the following 36 months, starting with the second week.
[NPRR1014 and NPRR1029:  Replace applicable portions of paragraph (2) above with the following upon system implementation:]
(2)	Monthly, ERCOT shall calculate the aggregate weekly Generation Resource capacity and ESR capacity for the ERCOT Region and the Forecast Zones projected to be available during the ERCOT Region peak Load hour of each week for the following 36 months, starting with the second week and the aggregate weekly Load Resource capacity for the ERCOT Region projected to be available during the ERCOT Region peak Load hour of each week for the following 36 months, starting with the second week.
(3)	On a rolling hourly basis, ERCOT shall calculate the aggregate hourly Generation Resource capacity and Load Resource capacity in the ERCOT Region and Forecast Zones projected to be available during each hour for the following seven days.
[NPRR1014 and NPRR1029:  Replace applicable portions of paragraph (3) above with the following upon system implementation:]
(3)	On a rolling hourly basis, ERCOT shall calculate the aggregate hourly Generation Resource capacity, ESR capacity, and Load Resource capacity in the ERCOT Region and Forecast Zones projected to be available during each hour for the following seven days.
(4)	Projections of Generation Resource capacity from Intermittent Renewable Resources (IRRs) shall be consistent with capacity availability estimates, such as the effective Load carrying capability of wind, developed jointly between ERCOT and the appropriate Technical Advisory Committee (TAC) subcommittee and approved by the ERCOT Board or typical production expectations consistent with expected wind profiles as appropriate for the scenario being studied.
[NPRR1029:  Replace paragraph (4) above with the following upon system implementation:]
(4)	Projections of generation capacity from Intermittent Renewable Resources (IRRs) and the intermittent renewable generation components of DC-Coupled Resources shall be consistent with capacity availability estimates, such as the effective Load carrying capability of wind, developed jointly between ERCOT and the appropriate Technical Advisory Committee (TAC) subcommittee and approved by the ERCOT Board or typical production expectations consistent with expected wind profiles as appropriate for the scenario being studied.
(5)	ERCOT shall publish procedures describing the IRR forecasting process on the ERCOT website.
3.2.2	Demand Forecasts
(1)	Monthly, ERCOT shall develop the weekly peak hour Demand forecast for the ERCOT Region and for the Forecast Zones based on the 36-Month Load Forecast as described in Section 3.12, Load Forecasting, for the following 36 months, starting with the second week.  During the development of this forecast, ERCOT may consult with Qualified Scheduling Entities (QSEs), Transmission Service Providers (TSPs), and other Market Participants that may have knowledge of potential Load growth.