NPRR180

Title:	Reconciliation of CRR Related Protocol Language
Next Group:
Next Step:
Status:	Approved on 08/18/2009

Date	Gov Body		Next Steps
08/18/2009	Board of Directors	Approved
08/06/2009	TAC	Recommended for Approval	Board consideration
07/23/2009	PRS	Recommended for Approval	TAC consideration
06/18/2009	PRS	Recommended for Approval	PRS consider the Recommendation Report
			PRS consideration

Date	Gov Body	Motion	Result
08/18/2009	Board of Directors	Approved NPRR180 as recommended by TAC in the 8/6/09 TAC Recommendation Report	Passed
08/06/2009	TAC	To recommend approval of NPRR180 as recommended by PRS	Passed
07/23/2009	PRS	To endorse and forward the PRS Recommendation Report and Impact Analysis for NPRR180 to TAC.	Passed
06/18/2009	PRS	To recommend approval of NPRR180 as submitted.	Passed

Status:	Approved
Date Posted:	06/10/2009
Sponsor:	Steve Reedy
Urgent:	No
Sections:	3.10.3, CRR Network Model 7.1, Function of Congestion Revenue Rights 7.3, Types of Congestion Revenue Rights to Be Auctioned
Description:	This Nodal Protocol Revision Request (NPRR) makes the following Nodal Protocol changes: o Removes the Section 3.10.3 requirement to hold Congestion Revenue Right (CRR) models static for two months prior to the auction, thus enabling CRR group to perform updates to CRR model until publication of said model. o Revises Section 7.1(2)(d) to state that the facilitation of bilateral trades will occur on the Market Information System (MIS) Certified Area, not the Secured Area. o Removes the wording in Section 7.1(2)(d) to clarify that bilateral trades of Point- to-Point (PTP) Options with Refund and PTP Obligations with Refund will not occur in Day-Ahead Market (DAM). Amends Section 7.3(1)(c) to clarify that all available Flowgate Right (FGR) capacity (that is consistent with the simultaneous feasibility test described in Section 7.5.5.4, Simultaneous Feasibility Study) is available in CRR Auctions, not just that offered by CRR Account Holders.
Reason:	Removes of out of date language which does not provide for the current needs of CRR Account Holders, and reconciles minor differences of CRR application behavior with Nodal Protocols.