Title: Resource Node Updated Definitions
Next Group:
Next Step:
Status: Approved on 10/21/2008
Effective Dates:

or per the Nodal Protocol Transition Plan http://www.ercot.com/mktrules/protocols (11/01/08 Nodal Protocols Library)


Date Gov Body Action Taken Next Steps
07/17/2008 PRS Recommended for Approval Review of Impact Analysis for NPRR124.
06/19/2008 PRS Referred Review by TPTF
10/21/2008 BOARD Approved
09/24/2008 PRS Recommended for Approval TAC consideration
10/02/2008 TAC Recommended for Approval Board consideration
05/22/2008 TPTF Recommended for Approval PRS consideration
04/18/2008 PRS Referred Review by TPTF.

Voting Record

Date Gov Body Motion Result
07/17/2008 PRS To recommend approval of NPRR124 as amended by TPTF comments and as revised by PRS. Passed
06/19/2008 PRS To refer NPRR124 to TPTF to clarify the meaning of "logical construct" and consider adding a definition for "logical resource node." Passed
10/21/2008 BOARD The ERCOT Board approved NPRR124 as revised by the ERCOT Board. Passed
09/24/2008 PRS To endorse and forward the PRS Recommendation Report and Impact Analysis to TAC. Passed
10/02/2008 TAC To recommend approval of NPRR124 as recommended by PRS. Passed
05/22/2008 TPTF To endorse forwarding TPTF comments to the Protocol Revision Subcommittee (PRS) with the understanding that ERCOT will bring back to TPTF a procedure detailing the assigning of Resource Nodes using the struck language from the discussion document. Passed
04/18/2008 PRS To refer NPRR124 to TPTF for review. 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: Apr 10, 2008
Sponsor: ERCOT Staff
Urgent: No
Sections: Section 2.1, Definitions
Description: This Nodal Protocol Revision Request (NPRR) clarifies the definition for Resource Node and specifies the different Resource Node types that meet the Nodal Protocol requirements.
Reason: The current definition of Resource Node limits the capabilities of the intended Nodal Market and is inconsistently used within the Protocols based on explicit and implicit requirements. There is a need for more Resource Node types to fully capture the intent of the Protocols.

Key Documents

Related Content