Title Updates to Language Regarding a QSE Moving Ancillary Service Responsibility Between Resources
Next Group
Next Step
Status Approved on 09/15/2022
Effective Dates


Date Gov Body Action Taken Next steps
09/15/2022 PUCT Approved
08/16/2022 BOARD Recommended for Approval PUCT for consideration
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
09/15/2022 PUCT To approve NPRR1136 and accompanying ERCOT Market Impact Statement as presented in Project No. 52934, Review of Rules Adopted by the Independent Organization Passed
08/16/2022 BOARD To recommend approval of NPRR1136 as recommended by TAC in the 7/27/22 TAC Report Passed
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


Status: Approved
Date Posted: May 18, 2022
Sponsor: ERCOT
Urgent: No
Sections: 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 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 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