Title Clarifications to RMR RUC Commitment and Other RMR Cleanups
Next Group
Next Step
Status Approved on 10/11/2016
Effective Dates


Date Gov Body Action Taken Next steps
10/11/2016 BOARD Approved
09/29/2016 TAC Recommended for Approval Board for consideration
09/15/2016 PRS Recommended for Approval TAC for consideration
08/11/2016 PRS Deferred/Tabled PRS for consideration

Voting Record

Date Gov Body Motion Result
10/11/2016 BOARD To approve NPRR793 as recommended by TAC in the 9/29/16 TAC Report Passed
09/29/2016 TAC To recommend approval of NPRR793 as recommended by PRS in the 9/15/16 PRS Report with a recommended effective date of October 12, 2016 Passed
09/15/2016 PRS To grant NPRR793 urgent status; to recommend approval of NPRR793 as amended by the 8/25/16 ERCOT comments; and to forward the Impact Analysis to TAC Passed
08/11/2016 PRS To table NPRR793 and refer the issue to WMS Passed


Status: Approved
Date Posted: Jul 27, 2016
Sponsor: ERCOT
Urgent: Yes
Sections:, 3.9.1,,,,,,, 4.1,, 4.4.8,,,, 5.5.3, 6.4.2,, 6.4.4,,,,, 6.6.10,, 9.19.1, 12.2
Description: The purpose of this Nodal Protocol Revision Request (NPRR) is to: Introduce a process change that ensures Reliability Must-Run (RMR) Resources are not accidentally Reliability Unit Commitment (RUC) committed before other units; Bring RMR Settlement language in line with Board-approved NPRR442, Energy Offer Curve Requirement for Generation Resources Providing Reliability Must-Run Service; Clarify the operational practice that ERCOT will submit Energy Offer Curves for RMR Resources as opposed to Output Schedules; Clarify activities during the contracting and reimbursement process; Require RMR Unit owners to provide monthly updated budget information during the term of the RMR Agreement; Align with the shortened settlements timeline by requiring that actual cost and fuel data be submitted by the 16th day of the month following a given month to be timely for final; Make minor corrections to two RMR Settlement formulas so that they comport with the original intent and the current implementation; and Make other non-substantive revisions to clarify Protocol language for RMR Resources. The current process for committing an RMR Resource lacks clarity and could allow the RUC engine to commit an RMR Resource before other Resources. This would require monitoring by operations personnel to detect and correct. This NPRR would require the Qualified Scheduling Entity (QSE) to show a Resource Status of EMR which makes the Resource unavailable to the RUC engine and requires an operator to manually commit the Resource. NPRR442 removed the ability for RMR Resources to be Day-Ahead Market (DAM) committed, but did not remove the related Settlement language. This NPRR removes Settlement language related to DAM-committed RMR Units. This NPRR also cleans up existing RMR formulas by correcting brackets in paragraph (1) of Section, and adding a summation symbol to paragraph (2) of Section to show the roll-up of 15-minute data to hourly data. These corrections match the current system implementation so no changes to ERCOT systems will be needed for these clarifications. Further revisions are included in this NPRR to provide additional clarity to the RMR contracting and reimbursement processes: Where the RMR Unit owner is required to provide alternatives for Outage Maintenance Costs and Non-Outage Maintenance Costs, an affirmation by the RMR Unit owner would be submitted in instances where no reasonable alternatives are available; Reported actual Eligible Costs must be categorized consistently with budgeted Eligible Costs to ensure accurate Eligible Cost true-up; and the “Hourly Rolling Equivalent Availability Factor” of the RMR Unit, which is used to calculate the Incentive Factor payment, is specified to be based only on hours in which the RMR Unit is intended to be available under the RMR Agreement to better align with instances in which availability is required for non-contiguous time periods.
Reason: Meets Strategic goals / Administrative

Key Documents

Related Content