MIS LOG IN

NPRR752

Summary

Title: Clarification of Revision Request Process
Next Group:
Next Step:
Status: Approved on 06/14/2016
Effective Dates:
07/01/2016

Action

Date Gov Body Action Taken Next Steps
06/14/2016 BOARD Approved
04/28/2016 TAC Recommended for Approval Revision Request Consideration
04/14/2016 PRS Recommended for Approval Revision Request Consideration
03/10/2016 PRS Recommended for Approval Impact Analysis Consideration
02/11/2016 PRS Deferred/Tabled Language Consideration

Voting Record

Date Gov Body Motion Result
06/14/2016 BOARD Approved NPRR752 as recommended by TAC in the 4/28/16 TAC Report. Passed
04/28/2016 TAC To recommend approval of NPRR752 as recommended by PRS in the 4/14/16 PRS Report. Passed
04/14/2016 PRS To endorse and forward to TAC the 3/10/16 PRS Report and the Impact Analysis for NPRR752. Passed
03/10/2016 PRS To recommend approval of NPRR752 as amended by the 2/24/16 ERCOT comments. Passed
02/11/2016 PRS To table NPRR752. 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.

Background

Status: Approved
Date Posted: Jan 22, 2016
Sponsor: ERCOT
Urgent: No
Sections: 21.4.1, 21.4.2, 21.4.4, 21.4.5, 21.4.6, 21.4.7, 21.4.8, 21.4.9, 21.4.10, 21.5, 21.6
Description: This Nodal Protocol Revision Request (NPRR) clarifies Protocol language related to the revision request process to reflect current ERCOT practices. Changes include: • Alignment of Protocol language with NPRR/System Change Request (SCR) submission forms and the Impact Analysis form; • Clarification of initial SCR evaluation by ERCOT; • Clarification of whether Revision Request related documents are distributed to exploders and/or posted to the ERCOT website and which committees/subcommittees they are distributed to; and • Additional administrative changes to align with current ERCOT practices.
Reason: Administrative

Key Documents

Related Content