ERCOT·WATCH Search ercot.com  ⌕
NPRR #379 · Revision Request

NPRR379  EILS Dispatch Sequence and Performance Criteria Upgrades

Approved sponsor ERCOT posted 2011-06-07 ercot.com
ReasonERCOT 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.
Created2011-06-23
Approved2011-09-20
Sections Affected
2.13.14.36.5.9.4.26.6.11.18.1.3.18.1.3.28.1.3.38.1.3.3.1
Summary
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.
Action Log 4 milestones
Amendments
DateBodyMotionResult
Jun 23 '11PRS To recommend approval of NPRR379 as revised by PRSPassed
Jul 21 '11PRS 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 TACPassed
Aug 4 '11TAC To recommend approval of NPRR379 as amended by the 8/2/11 ERCOT commentsPassed
Sep 20 '11BOARD To approve NPRR379 as amended by the 9/7/11 ERCOT commentsPassed
Documents 15
NameTypePostedClassification
379NPRR-01 EILS Dispatch Sequence and Performance Criteria Upgra doc Jun 8 '11 Revision Request
379NPRR-02 Preliminary Impact Analysis 060811 doc Jun 8 '11 Staff Report
379NPRR-03 WMS Comments 062011 doc Jun 20 '11 Revision Request Comments
379NPRR-04 ROS Comments 062111 doc Jun 21 '11 Revision Request Comments
379NPRR-05 PRS Report 062311 doc Jun 28 '11 Committee Report
379NPRR-06 ERCOT Comments 071411 doc Jul 14 '11 Revision Request Comments
379NPRR-07 Impact Analysis 071411 doc Jul 14 '11 Staff Report
379NPRR-08 Cost Benefit Analysis 072011 xls Jul 20 '11 Staff Report
379NPRR-09 PRS Report 072111 doc Jul 27 '11 Committee Report
379NPRR-10 Revised Cost Benefit Analysis 072811 xls Jul 28 '11 Staff Report
379NPRR-11 ERCOT Comments 072811 doc Jul 28 '11 Revision Request Comments
379NPRR-12 ERCOT Comments 080211 doc Aug 2 '11 Revision Request Comments
379NPRR-13 TAC Report 080411 doc Sep 9 '11 Committee Report
379NPRR-14 ERCOT Comments 090711 doc Sep 7 '11 Revision Request Comments
379NPRR-15 Board Report 092011 doc Sep 21 '11 Committee Report
Meetings That Took It Up 11
DateMeetingCommitteeStatus
Oct 6 '11 TAC Meeting TAC Concluded
Sep 30 '11 Demand Side Working Group Meeting DSWG Concluded
Sep 20 '11 Board of Directors Meeting BOARD Concluded
Sep 15 '11 ROS Meeting ROS Concluded
Aug 17 '11 Operations Working Group (OWG) Meeting OWG Concluded
Aug 4 '11 TAC Meeting TAC Concluded
Jul 21 '11 PRS Meeting PRS Concluded
Jul 20 '11 Operations Working Group (OWG) Meeting OWG Concluded
Jun 23 '11 PRS Meeting PRS Concluded
Jun 16 '11 ROS Meeting ROS Concluded
Jun 15 '11 WMS Meeting WMS Concluded