MIS LOG IN

NPRR1148

Summary

Title Language Cleanup Related to ERCOT Contingency Reserve Service (ECRS)
Next Group
Next Step
Status Approved on 01/26/2023
Effective Dates
06/09/2023

Action

Date Gov Body Action Taken Next Steps
01/26/2023 PUCT Approved
12/20/2022 BOARD Recommended for Approval PUCT for consideration
10/26/2022 TAC Recommended for Approval Board for consideration
10/13/2022 PRS Recommended for Approval TAC for consideration
09/15/2022 PRS Recommended for Approval PRS for Impact Analysis consideration

Voting Record

Date Gov Body Motion Result
01/26/2023 PUCT To approve NPRR1148 and accompanying ERCOT Market Impact Statement as presented in Project No. 54445, Review of Rules Adopted by the Independent Organization Passed
12/20/2022 BOARD To recommend approval of NPRR1148 as recommended by TAC in the 10/26/22 TAC Report Passed
10/26/2022 TAC To recommend approval of NPRR1148 as recommended by PRS in the 10/13/22 PRS Report Passed
10/13/2022 PRS To endorse and forward to TAC the 9/15/22 PRS Report and 8/30/22 Impact Analysis for NPRR1148 Passed
09/15/2022 PRS To recommend approval of NPRR1148 as submitted Passed

Background

Status: Approved
Date Posted: Aug 30, 2022
Sponsor: ERCOT
Urgent: No
Sections: 4.4.7.2.1, 6.5.7.3.1, and 6.5.7.6.2.4
Description: This NPRR addresses Protocol gaps found during the creation of the ECRS system change requirements. Specific changes include: Language was added to Section 4.4.7.2.1 to align NPRR863, Creation of ERCOT Contingency Reserve Service and Revisions to Responsive Reserve, implementation to a pre-Real-Time Co-Optimization (RTC) system design. Clarification was added about simultaneous awarding and Real-Time provision of Responsive Reserve (RRS), ECRS, and Non-Spinning Reserve (Non-Spin) by Load Resources that are not Controllable Load Resources; Language was added to paragraph (1) of Section 6.5.7.6.2.4 to clarify that ECRS will also be deployed to provide energy upon detection of insufficient available capacity for net load ramps. (Such use is in addition to the uses already included in the Protocols: use for frequency restoration, energy during an Energy Emergency Alert (EEA), or as a backup to Regulation Up Service (Reg-Up)); and Language was added to paragraph (2)(e) of Section 6.5.7.3.1 to clarify that ECRS deployments from Load Resources that are not Controllable Load Resources will be considered at a ten-minute linear ramp for the calculation of the Real-Time On-Line Reliability Deployment Price Adder. This is similar to the approach taken with RRS deployments from Load Resources that are not Controllable Load Resources.
Reason: Market efficiencies or enhancements

Key Documents

Related Content