Title Address Unavailability Gap for ERS and Other Minor Clarifications
Next Group
Next Step
Status Approved on 04/09/2019
Effective Dates


Date Gov Body Action Taken Next Steps
04/09/2019 BOARD Approved
03/27/2019 TAC Recommended for Approval Revision Request Consideration
02/14/2019 PRS Recommended for Approval Revision Request Consideration
01/17/2019 PRS Recommended for Approval Impact Analysis Consideration
12/13/2018 PRS Deferred/Tabled Language Consideration

Voting Record

Date Gov Body Motion Result
04/09/2019 BOARD to approve NPRR909 as recommended by TAC in the 3/27/19 TAC Report Passed
03/27/2019 TAC to recommend approval of NPRR909 as recommended by PRS in the 2/14/19 PRS Report Passed
02/14/2019 PRS to endorse and forward to TAC the 1/17/19 PRS Report and Impact Analysis for NPRR909 Passed
01/17/2019 PRS to recommend approval of NPRR909 as submitted Passed
12/13/2018 PRS to table NPRR909 and refer the issue to WMS Passed


Status: Approved
Date Posted: Nov 20, 2018
Sponsor: ERCOT
Urgent: No
Description: This Nodal Protocol Revision Request (NPRR): • Addresses periods of unavailability due to unplanned unavailability for Loads and Generators; • Changes the name reference of “Default Baseline Methodology” to “Demand Response Baseline Methodologies”; • Deletes the reference to post the Qualified Scheduling Entity (QSE) portfolio–level report since it is already listed under required reports in paragraph (3) of Section; • Addresses what happens if a generator fails an event as the current language only addresses failures for a test; • Deletes a sentence that is duplicated in paragraph (2) of Section about meter data for generator availability which is in the event performance section; • Adds language to qualify as a co-located generator as all Time-Periods must match between the Load and generator; • Adds clarifying language about when the recovery period starts; • Specifies the use of the Maximum Megawatt (MW) from all offered Time-Periods for weather sensitive Resources; • Adds clarifying language to specify that weather sensitive Resource testing does not count towards the cumulative deployment limit of eight hours; and • Removes language regarding when to return to normal operations since the language is specific to paragraph (3) of Section

Key Documents

Related Content