Title: CRR Trading in Blocks Only
Next Group:
Next Step:
Status: Approved on 10/17/2006
Effective Dates:

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


Date Gov Body Action Taken Next Steps
06/28/2007 TAC
06/12/2007 PRS Recommended for Approval Review of B1G1 Impact Analysis
10/17/2006 BOARD Approved Effective Upon Texas Nodal Market Implementation
10/06/2006 TAC Recommended for Approval Board consideration
09/21/2006 PRS Recommended for Approval TAC consideration

Voting Record

Date Gov Body Motion Result
06/28/2007 TAC No Action.
06/12/2007 PRS To recommend approval of B1G1 Impact Analysis Passed
10/17/2006 BOARD To approve as recommended by TAC. Passed
10/06/2006 TAC To recommend approval of NPRR028 as recommended by PRS. Passed
09/21/2006 PRS To recommend approval of NPRR028 as submitted. 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: Sep 14, 2006
Sponsor: ERCOT Staff
Urgent: No
Sections: 7.2,,, 7.8
Description: Revise how CRRs may be traded in the bilateral market and in CRR Auctions. This revision would limit CRR trading to time-of-use blocks for a particular date and CRR Offers in CRR Auctions to time-of-use blocks. With this revision, CRR Account Holders would not be able to trade a particular hour or a block of hours that is not one of the defined time-of-use blocks in Section 7.3 (6).
Reason: The vendor (Nexant) CRR system does not support the flexibility of bilaterally trading CRRs for each hour and offering CRRs for particular hour or hours (except time-of-use blocks in Section 7.3 (6)) in CRR Auctions. Vendor estimates a cost of $395,000 for adding this flexibility to their system due to required fundamental changes in the following: data interfaces; Market User Interface functionality (new Java based editor, bilateral trading system, portfolio editor, downloads): Market Operator Interface functionality (command manager); Database Subsystem; testing; and documentation. In addition to the development costs, the CRR team believes there might be other long-term costs associated with the maintenance of the CRR System due to increased complexity, possible need for increased H/W costs for performance and storage, increased auditing overhead, archiving requirements, etc. These long-term costs are not very easy to assess and have not yet been quantified.

Key Documents

Related Content