MIS LOG IN

NPRR1090

Summary

Title ERS Winter Storm Uri Lessons Learned Changes and Other ERS Items
Next Group
Next Step
Status Approved on 10/28/2021
Effective Dates
12/01/2021

Sections 3.14.3.1, 8.1.3.1.3.1, 8.1.3.1.3.2, 8.1.3.1.3.3, 8.1.3.1.4, 8.1.3.2, and 8.1.3.3.3

06/27/2024

All remaining sections

Action

Date Gov Body Action Taken Next Steps
10/28/2021 PUCT Approved
10/22/2021 BOARD Recommended for Approval Revision Request Consideration
09/29/2021 TAC Recommended for Approval Revision Request Consideration
09/16/2021 PRS Recommended for Approval Revision Request Consideration
08/12/2021 PRS Deferred/Tabled Language Consideration

Voting Record

Date Gov Body Motion Result
10/28/2021 PUCT To approve NPRR1090 and accompanying ERCOT Market Impact Statement as presented in Project No. 52307, Review of Rules Adopted by the Independent Organization in Calendar Year 2021 Passed
10/22/2021 BOARD to recommend approval of NPRR1090 as recommended by TAC in the 9/29/21 TAC Report Passed
09/29/2021 TAC to recommend approval of NPRR1090 as recommended by PRS in the 9/16/21 PRS Report; and the Revised Impact Analysis Passed
09/16/2021 PRS to grant NPRR1090 Urgent status; to recommended approval of NPRR1090 as amended by the 9/7/21 WMS comments as revised by PRS; and to forward to TAC NPRR1090 and the Impact Analysis with a recommended priority of 2021 and rank of 3360 Passed
08/12/2021 PRS to table NPRR1090 and refer the issue to WMS Passed

Background

Status: Approved
Date Posted: Jul 28, 2021
Sponsor: ERCOT
Urgent: Yes
Sections: 2.1, 3.14.3.1, 3.14.3.3, 6.5.9.4.2, 8.1.3.1.3.1, 8.1.3.1.3.2, 8.1.3.1.3.3, 8.1.3.1.4, 8.1.3.2, 8.1.3.3
Description: This Nodal Protocol Revision Request (NPRR) makes a number of revisions pertaining to Emergency Response Service (ERS) that addresses items 48 and 102 of TAC’s Emergency Conditions List, including: 1) Modifying the requirement of issuing an Extensible Markup Language (XML) message followed by a Verbal Dispatch Instruction (VDI) for ERS deployments by using only the XML message and eliminating the VDI from the requirement; 2) Modifying and clarifying language related to the beginning and end of ERS Contract Periods for ERS renewals; 3) Removing the limit on the maximum number of deployments per ERS Contract Period, the three-hour maximum limit per single deployment event, and modifying language related to the cumulative deployment obligation time requirement for Weather-Sensitive ERS Resources; 4) Eliminating the options for ERS Resources to be excluded from an ERS deployment event or to exclude intervals from event and availability performance with properly noticed scheduled unavailability and planned maintenance for up to 2% of their obligated intervals without payment reductions; 5) Modifying language related to short ERS Contract Period availability calculations for ERS Resources to account for short Contract Periods in which no exhaustion occurs and modifying the formula for the ratio of Availability Factor Hours to the total awarded hours in the ERS Standard Contract Term to include all awarded hours in the Standard Contract Term; 6) Removing the requirement to reduce the time-weighting factor for intervals by 25% after eight hours for Qualified Scheduling Entity (QSE)-level event performance; 7) Removing language related to the first full interval of an ERS deployment event from the ERS Resource-level event performance criteria and modifying language related to successful performance during ERS deployment events to satisfy annual testing requirements; 8) Removing language related to testing ERS Generators for failing self-tests; and 9) Modifying QSE-level event performance to be both time and capacity weighted.
Reason: Market efficiencies or enhancements; Addresses current operational issues

Key Documents

Related Content