Title: Removal of References to RUC Notifications
Next Group:
Next Step:
Status: Approved on 11/19/2013
Effective Dates:


Date Gov Body Action Taken Next Steps
11/19/2013 BOARD Approved
09/05/2013 TAC Recommended for Approval ERCOT Board consideration of NPRR546
07/18/2013 PRS Recommended for Approval TAC consideration of NPRR546
06/20/2013 PRS Recommended for Approval PRS Impact Analysis review

Voting Record

Date Gov Body Motion Result
11/19/2013 BOARD To approve NPRR546 as recommended by TAC in the 9/5/13 TAC Report. Passed
09/05/2013 TAC To recommend approval of NPRR546 as recommended by PRS in the 7/18/13 PRS Report. Passed
07/18/2013 PRS To endorse and forward the 6/20/13 PRS Report and Impact Analysis for NPRR546 to TAC. Passed
06/20/2013 PRS To recommend approval of NPRR546 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.


Status: Approved
Date Posted: Jun 4, 2013
Sponsor: ERCOT
Urgent: No
Sections: 2.1,, 5.5.2
Description: This Nodal Protocol Revision Request (NPRR) removes outstanding references to "Reliability Unit Commitment (RUC) Notifications." This language is no longer relevant as a result of changes made through NPRR321, Allow Change to Energy Offer Curve MW Amounts in the Adjustment Period, which was approved by the ERCOT Board on 9/20/11.
Reason: NPRR207, Unit Deselection, approved by the ERCOT Board on 7/20/10, introduced the term "RUC Notification" into the Protocols. A RUC Notification is a notification that would be sent out by ERCOT to a Qualified Scheduling Entity (QSE) when a RUC process recommended the QSE’s Resource, but ERCOT Operators opted to deselect the Resource for commitment. The language requiring ERCOT to send out this notification to the individual QSE was later replaced with a requirement for an aggregate report. This was done as part of NPRR321 during discussion at the 6/23/11 PRS meeting.

Key Documents

Related Content