MIS LOG IN

NPRR1136

Summary

Title: Updates to Language Regarding a QSE Moving Ancillary Service Responsibility Between Resources
Next Group: BOARD
Next Step: Board for consideration
Status: Pending

Action

Date Gov Body Action Taken Next Steps
07/27/2022 TAC Recommended for Approval Board for consideration
07/13/2022 PRS Recommended for Approval TAC for consideration
06/09/2022 PRS Recommended for Approval PRS for Impact Analysis consideration

Voting Record

Date Gov Body Motion Result
07/27/2022 TAC To recommend approval of NPRR1136 as recommended by PRS in the 7/13/22 PRS Report Passed
07/13/2022 PRS To endorse and forward to TAC the 6/9/22 PRS Report and 5/18/22 Impact Analysis for NPRR1136 with a recommended priority of 2023 and rank of 3720 Passed
06/09/2022 PRS To recommend approval of NPRR1136 as submitted Passed

Vote tallies here reflect individual votes, not the weight of the votes by market segment. Affirmative votes are not recorded in these vote tallies. For additional details on the voting record, please consult the Recommendation or Action Report, or the official vote tally if available, as posted in the key documents.

Background

Status: Pending
Date Posted: May 18, 2022
Sponsor: ERCOT
Urgent: No
Sections: 4.4.7.3 and 6.4.7
Description: This Nodal Protocol Revision Request (NPRR) makes changes to reflect the logic that will be in place after the implementation of Fast Frequency Response (FFR) Advancement project, the next phase of implementation for NPRR863, Creation of ERCOT Contingency Reserve Service and Revisions to Responsive Reserve. Specifically, the NPRR adds new paragraph (5) of Section 4.4.7.3 to align with language in Section 6.4.7. These changes are for clarity only, and do not modify the system design. The new paragraph (6) of Section 4.4.7.3 is an additional check that needs to be in place to ensure a QSE does not replace a Regulation Service with Fast Responding Regulation Service (FRRS). This section does not need to be addressed in the FFR Advancement implementation, and it is ERCOT’s intent to implement this logic change in a future project.
Reason: Addresses current operational issues

Key Documents

Related Content