Title: Standing Non-Spin Deployment in the Operating Hour for Generation Resources Providing On-Line Non-Spin
Next Group:
Next Step:
Status: Approved on 12/12/2011
Effective Dates:


Date Gov Body Action Taken Next Steps
12/12/2011 BOARD Approved
12/01/2011 TAC Recommended for Approval ERCOT Board consideration of NPRR426
11/17/2011 PRS Recommended for Approval TAC consideration of NPRR426

Voting Record

Date Gov Body Motion Result
12/12/2011 BOARD To approve NPRR426 as recommended by TAC in the 12/1/11 TAC Report. Passed
12/01/2011 TAC To recommend approval of NPRR426 as recommended by PRS in the 11/17/11 PRS Report. Passed
11/17/2011 PRS To recommend approval of NPRR426 as revised by PRS, to recommend an effective date of January 5, 2012, and to forward NPRR426 to TAC. 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: Nov 9, 2011
Sponsor: ERCOT
Urgent: Yes
Description: This Nodal Protocol Revision Request (NPRR) requires Qualified Scheduling Entity (QSE) action that routinely releases certain On-Line Non-Spinning Reserve (Non-Spin) energy to Security-Constrained Economic Dispatch (SCED) without the need for ERCOT to issue a Non-Spin deployment instruction. The changes in Section do not invalidate any other existing requirements contained in this section. Those Generation Resources not subject to the provisions contained in paragraph (5) of Section must respond to any Non-Spin deployment or recall instruction issued by ERCOT Operators in accordance with the Technical Advisory Committee (TAC)-approved Non-Spinning Reserve Service Deployment and Recall Procedure. There will not be any validation rules to verify the requirements added by this NPRR. The onus is on all QSEs to make the submission/telemetry changes needed to implement these new requirements.
Reason: To address concerns raised at the October 27, 2011 PUCT Open Meeting regarding Project No. 37897.

Key Documents

Related Content