MIS LOG IN

NPRR387

Summary

Title Hydro RRS Deployment Under Frequency Relay Set Point
Next Group
Next Step
Status Approved on 07/19/2011
Effective Dates
08/01/2011

Action

Date Gov Body Action Taken Next steps
07/19/2011 BOARD Approved
07/07/2011 TAC Recommended for Approval ERCOT Board Consideration
06/23/2011 PRS Recommended for Approval TAC Consideration

Voting Record

Date Gov Body Motion Result
07/19/2011 BOARD To approve NPRR387 as recommended by TAC in the 7/7/11 TAC Report Passed
07/07/2011 TAC To recommend approval of NPRR387 as recommended by PRS in the 6/23/11 PRS Report Passed
06/23/2011 PRS To recommend approval of NPRR387 as revised by PRS and to forward NPRR387 to TAC Passed

Background

Status: Approved
Date Posted: Jun 15, 2011
Sponsor: LCRA
Urgent: Yes
Sections: 3.8, 3.8.4, 3.10.7.2, 3.10.7.5.2, 3.18, 4.4.9.2.2, 6.5.9.2, 8.1.1.4.2
Description: This Nodal Protocol Revision Request (NPRR) clarifies that for hydro Generation Resources operating in the synchronous condenser fast-response mode to provide Responsive Reserve (RRS), the initiation setting of the automatic under frequency relay setting shall not be lower than 59.80 Hz. It also includes language to address the instances when a hydro Generation Resource operating in synchronous condenser fast-response mode is triggered by an under frequency relay device without a corresponding RRS deployment by ERCOT. Additionally, this NPRR is a companion to Nodal Operating Guide Revision Request (NOGRR) 068, Hydro-Responsive Reserve, and has been prepared in coordination with ERCOT Staff. Changes to revise the use of "hydro-powered Resource" to "hydro Generation Resource" and revisions to Section 3.8 references are also proposed in this NPRR.
Reason: This NPRR establishes the minimum set point at which a hydro Generation Resource must set it’s under frequency relay device for automatic response to an ERCOT System frequency event and also clarifies that same Resource will not be deemed out of compliance when tripped by under frequency relay without corresponding RRS deployment.

Key Documents

Related Content