Sections: |
2.1, 2.1, 3.14, 3.14.3, 3.14.3.1 (new), 3.14.3.2 (new), 3.14.3.3 (new), 3.14.3.4 (new), 6.5.9.4, 6.5.9.4.2, 6.5.9.4.3, 6.6.11, 6.6.11.1, 6.6.11.2, 8.1.3, 8.1.3.1, 8.1.3.1.1 (new), 8.1.3.1.2 (new), 8.1.3.1.3 (new), 8.1.3.1.3.1 (new), 8.1.3.1.3.2 (new), 8.1.3.1.3.3 (new), 8.1.3.1.4 (new), 8.1.3.2 |
Reason: |
Project 39948 proposes a repeal of P.U.C. Subst. Rule 25.507 provisions governing EILS, to be replaced with the renamed product Emergency Response Service (ERS). The purpose of ERS, as stated in the Project 39948, is to "promote reliability during energy emergencies through provisions that provide ERCOT flexibility in the implementation and administration of ERS." A large portion of the existing Protocols related to EILS will be maintained over the transition to ERS. The most significant changes enabled by the new P.U.C. Subst. Rule 25.507 and by this NPRR are as follows:
Allows participation by generators and defines the types of generation units that will be eligible to participate and establishes performance criteria for deployment events, availability, and testing.
The minimum amount that may be offered for ERS is changed from one MW to one-tenth (0.1) MW.
The current ceiling of 1,000 MW for procurement of ERS is removed.
Establishes processes for enabling ERCOT to initiate additional ERS Contract Periods in cases where ERS Resources’ obligations are exhausted, such as they were during the February 2-3, 2011, EILS deployment. Qualified Scheduling Entities (QSEs) will be allowed to designate ERS Resources for automatic renewal, under similar terms as the original contract, in order to maintain the maximum number of reliability tools during sustained weather events or other capacity-short situations.
Creates a more equitable system for compliance with the Protocols by requiring ERCOT to evaluate QSE ERS portfolio performance as the first step in determining compliance.
Deletes Appendices A and B of Section 22G - The provisions of these contract-related documents are adequately covered elsewhere and are not required to be part of the Nodal Protocols. |