- Home
- Market Rules
- Issues
NPRR379
Summary
| Title | EILS Dispatch Sequence and Performance Criteria Upgrades |
|---|---|
| Next Group | |
| Next Step | |
| Status | Approved on 09/20/2011 |
| Effective Dates |
10/01/2011
All sections except for Section 3.14.3(4) and Section 6.5.9.4.2(2)(a)(iii) 07/01/2012
All remaining sections |
Action
| Date | Gov Body | Action Taken | Next Steps |
|---|---|---|---|
| 09/20/2011 | BOARD | Approved | |
| 08/04/2011 | TAC | Recommended for Approval | ERCOT Board Consideration |
| 07/21/2011 | PRS | Recommended for Approval | TAC Consideration |
| 06/23/2011 | PRS | Recommended for Approval | PRS IA Review |
Voting Record
| Date | Gov Body | Motion | Result |
|---|---|---|---|
| 09/20/2011 | BOARD | To approve NPRR379 as amended by the 9/7/11 ERCOT comments | Passed |
| 08/04/2011 | TAC | To recommend approval of NPRR379 as amended by the 8/2/11 ERCOT comments | Passed |
| 07/21/2011 | PRS | To endorse and forward the 6/23/11 PRS Report as amended by the 7/14/11 ERCOT comments and the Impact Analysis and Cost Benefit with a priority of High and rank of 14.5 to TAC | Passed |
| 06/23/2011 | PRS | To recommend approval of NPRR379 as revised by PRS | Passed |
Background
| Status: | Approved |
|---|---|
| Date Posted: | Jun 7, 2011 |
| Sponsor: | ERCOT |
| Urgent: | No |
| Sections: | 2.1, 3.14.3, 6.5.9.4.2, 6.6.11.1, 8.1.3.1, 8.1.3.2, 8.1.3.3, 8.1.3.3.1 |
| Description: | This Nodal Protocol Revision Request (NPRR) improves the operational value of Emergency Interruptible Load Service (EILS); and strengthens and clarifies a number of performance criteria for EILS by: Providing ERCOT Operators with enhanced flexibility for managing grid conditions during an Energy Emergency Alert (EEA) by requiring dispatch of EILS prior to or in conjunction with dispatch of Load Resources providing Responsive Reserve (RRS) in EEA Level 2; Improving dispatch of EILS by expanding the Dispatch Instruction to include an XML message in addition to the current Verbal Dispatch Instruction (VDI). This would make EILS dispatch consistent with Load Resource dispatch and would remove any potential ambiguity about dispatch status; Strengthening the 10-minute deployment requirement for EILS by establishing more specific metrics for both Qualified Scheduling Entities (QSEs) and EILS Load-level performance during the first interval of the deployment event, and affirming that a failure to meet the 10-minute requirement constitutes a violation of the Protocols; Establishing an availability "settlement weighting factor" that places higher emphasis on an EILS Load’s event performance over availability in an EILS Contract Period where EILS is deployed. For settlement purposes, availability would be weighted at 25% in an EILS Contract Period in which EILS was deployed but not exhausted. Availability would be weighted at between 0% and 25% in a Contract Period in which EILS was exhausted, via a sliding scale based on how early in the Contract Period EILS was exhausted; Allowing an EILS Load to be reassigned to a default baseline type if it was assigned to the alternate baseline prior to an EILS Contract Period due to a lack of sufficient historical meter data; Changing the event performance criteria for EILS Loads assigned to the alternate baseline to parallel the event performance calculation used for EILS Loads on a default baseline; Establishing conditions under which an EILS Load that falls short of an event performance factor of 0.95, yet demonstrably performs in an EILS deployment event, may avoid a six-month suspension. In such cases the payment to the QSE will be based on the actual event performance factor; these provisions apply to suspensions only; Simplifying availability requirements and settlement calculations for EILS by combining an EILS Load’s Time Period availability factors into a unified Load-weighted and time-weighted availability factor for a Contract Period; Adding clarity to QSE portfolio performance criteria; Establishing a list of QSE-specific documents that ERCOT shall be required to post to the Market Information System (MIS) Certified Area; and Making additional clarifying changes to EILS. |
| Reason: | ERCOT Operators may prefer to deploy EILS earlier in the EEA sequence in order to preserve the RRS capacity provided by Load Resources equipped with high-set under frequency relays. Under-frequency relay-equipped capacity provides a valuable backstop against frequency excursions. This NPRR does not impact ERCOT Real-Time desk procedures which provide for deployment of Load Resources providing RRS for frequency restoration in an event that could potentially violate a North American Electric Reliability Corporation (NERC) Reliability Standard. Many of the other NPRR provisions can be described as "lessons learned" from the 28-hour-long EILS deployment event of February 2-3, 2011, and would result in clarification and simplification of the compliance requirements for QSEs and EILS Loads. |
Key Documents
Jun 8, 2011 - doc - 255.5 KB
Jun 8, 2011 - doc - 58.5 KB
Jun 20, 2011 - doc - 220 KB
Jun 21, 2011 - doc - 38 KB
Jun 28, 2011 - doc - 268.5 KB
Jul 14, 2011 - doc - 232.5 KB
Jul 14, 2011 - doc - 60 KB
Jul 20, 2011 - xls - 118 KB
Jul 27, 2011 - doc - 276.5 KB
Jul 28, 2011 - xls - 118 KB
Jul 28, 2011 - doc - 231.5 KB
Aug 2, 2011 - doc - 233 KB
Sep 9, 2011 - doc - 276.5 KB
Sep 7, 2011 - doc - 235 KB
Sep 21, 2011 - doc - 281 KB