Settlements & Billing / Version: 5.10
Configuration Guide for: CRR Auction Transaction Settlement / Date: 094/2901/09

Settlements & Billing

BPM Configuration Guide: CRR Auction Transaction Settlement

CC 6798

Version 5.10

ÓCAISO, 2009 / Page 2 of 9
Settlements & Billing / Version: 5.10
Configuration Guide for: CRR Auction Transaction Settlement / Date: 094/2901/09

Table of Contents

1. Purpose of Document 3

2. Introduction 3

2.1 Background 3

2.2 Description 4

3. Charge Code Requirements 4

3.1 Business Rules 4

3.2 Predecessor Charge Codes 6

3.3 Successor Charge Codes 6

3.4 Inputs – External Systems 6

3.5 Inputs - Predecessor Charge Codes or Pre-calculations 7

3.6 CAISO Formula 8

3.7 Outputs 8

4. Charge Code Effective Dates 9

1.  Purpose of Document

The purpose of this document is to capture the requirements and design specification for a SaMC Charge Code in one document.

2.  Introduction

2.1  Background

Consistent with the adoption of Locational Marginal Pricing (LMP) under the new market design in place of zonal pricing under the current zonal market design, the current Congestion hedging instrument, Firm Transmission Rights (FTR), will be replaced with a new instrument called Congestion Revenue Rights (CRRs). In effect, zones will be eliminated and the new instrument will make use of CRR source(s) and CRR sink(s) that are based on nodes or group of nodes.

FERC orders have approved the ISO’s proposal to allocate CRRs to load-serving entities (LSEs) that serve customers located within the ISO control area, and to certain other parties described in the CAISO white paper on CRR Allocation Rules. “The central principle behind allocation of CRRs to LSEs serving internal customers is that these customers have supported and continue to support the embedded costs of the transmission system through their payment of access charges, which entitles them to utilize the grid to bring power from their power sources to the points where they take power off the grid without being exposed to additional charges for such use of the grid. This principle is made operational by allocating financial hedging instruments – CRRs – that enable the LSE to hedge the charges for grid Congestion that are assessed in their regular settlements with the ISO.” [CAISO White Paper: CRR Allocation Rules, 06/14/05]

CRRs may come from allocations by CAISO, given free of charge to select market participants. CRRs may also come from auctions by CAISO for any remaining available CRR capacities after the allocations. CRRs from auctions are bought at a Market Clearing Price. Furthermore, the CRRs can be subdivided and can be traded in the secondary market but no new CRRs are released by CAISO in the secondary market.

CAISO conducts an annual CRR Allocation once a year for the entire year. The annual CRR Allocation releases Seasonal CRRs for four seasonal periods. The CAISO also conducts monthly CRR Allocation twelve times a year in advance of each month. In addition, CAISO also conducts yearly and monthly CRR Auctions which can release monthly as well as seasonal CRRs. There is also a special type of CRRs - the Long-Term CRRs (LT-CRR) – which have a validity of ten years as opposed to the short–term ones. These LT-CRRs are seasonal in nature and are released via the annual CRR allocation process but not through CRR Auction.

Ownership of a CRR may change hands. However, only one entity can own the CRR in any Trading Hour and CAISO will settle with that owner.

CRR Settlement occurs hourly but it is possible that some of the entitlement amounts for the hour – because of insufficient funds – are deferred. These deferred entitlement amounts are trued up completely in the CRR monthly clearing process. When Congestion revenues are more than sufficient to settle the CRRs hourly, the excess revenues will be tracked internally through a CRR Balancing Account and will be used to true up deferred entitlement amounts in the CRR monthly clearing process.

The CRR charge codes, consisting of CC 6798 (CRR Auction Transaction Settlement), CC 6700 (CRR Hourly Settlement), CC 6728 (CRR Monthly Clearing), and CC 6790 (CRR Balancing Account), and CC 6791 (CRRBA Accrued Interest Allocation) shall conform towith the Tariff language on CRR Settlements (Section 11.2.4) and Full Funding of CRRs (Section 36.2.8).

CC 6700 settles the entitlement amounts (payments and charges) of all valid CRR holdings for each Trading Hour. This is funded by the CRR Balancing Account (CC 6790). The CRRBA is a daily account consisting of the IFM Congestion Fund, which is composed of hourly congestion revenues from Day-Ahead AS imports and Energy schedules and of CRR Charges. In addition, the CRRBA contains the net revenues from CRR Auctions applicable to each day. At the end of each day, the CRRBA is cleared through distribution of surplus or allocation of shortfall to Measured Demand excluding Measured Demand associated with valid ETC, TOR, and CVR Self-Schedules. Furthermore, at each month-end, accrued interest from investment of auction revenues shall be allocated to monthly Measured Demand excluding Measured Demand associated with valid ETC, TOR, and CVR Self-Schedules.

2.2  Description

This Charge Code settles the transaction amounts per Business Associate (BA) for each CRR Auction market. This charge shall be included in the same Invoice for Market, GMC, TAC, and/or FERC charges, to allow for netting of this Charge Code with the others.

For each year, CAISO conducts a yearly auction (actually consisting of several sub-auctions for each season) in advance of the year for which the CRRs are valid; and a monthly auction in advance of each month. Each auction is identified by an Auction Market Name and each auction consists of two time of use (TOU) - referring to the on-peak and off-peak hours classification of CRRs released in these auctions.

Market participants who buy or sell in these auctions have to settle transaction amounts with CAISO for CRRs they have obtained in the auctions. The net proceeds of the transaction amounts of each auction are forwarded to the CRR Balancing Account. Each monthly auction’s net transaction amounts plus a portion of the net proceeds of the seasonal auction for the season containing the same Trade Month shall be forwarded to the relevant CRRBA daily monthly accounts of the same month. The seasonal on-peak and off-peak net auction revenues shall be allocated to each month of the season in proportion to the number of on-peak and off-peak hours, respectively, in each month.

3.  Charge Code Requirements

3.1  Business Rules

Bus Req ID / Business Rule /
1.0 / This Charge Code settles the transaction amounts of Business Associates (BAs) who participate in each CRR Auction market.
1.1 / Each auction market is represented by an Auction Market Name.
1.2 / For each year, there will be seasonal auction markets and monthly auction markets.
1.2.1 / The seasonal auction markets, which release seasonal CRRs, are collectively termed the yearly auction. All the seasonal auction markets for the same year are conducted before the start of the year.
1.2.2 / There are monthly auctions which release monthly CRRs, and where each monthly auction is conducted in advance of the applicable month.
1.3 / This Charge Code shall be settled at the CRR ID level in each auction market.
1.4 / Each Auction Market Name can have CRR IDs with a time of use (TOU) of off-peak or on-peak.
2.0 / An external system shall provide all the CRR Auction results, the transaction dates per auction, and the transaction amounts for CRRs bought at the auction.
2.1 / Positive transaction amount represent a charge to a Business Associate who participated in the CRR Auction.
2.2 / Negative transaction amount represent payment to a Business Associate who participated in the CRR Auction.
2.3.1 / Payments and charges to BAs must be invoiced as soon as possible after the CRR Auction transaction data is made available to Settlements.
2.3.2 / This charge code has a daily frequency, although on as needed basis.
2.3.3 / The daily settlement trade date shall be set in such a way that the CRR auction transaction settlement will be included in the next nearest monthly invoice - whether that be a monthly initial market or a monthly recalc market invoice.
3.0 / The transaction amount per source or sink resource per CRR ID, per TOU per auction market name shall be provided for validation purposes.
4.0 / This Charge Code shall be included in the same Invoice for Market, GMC, TAC, and/or FERC charges, to allow for netting of this Charge Code with the others.
5.0 / PTB charge adjustment is not allowed for this charge code.
6.0 / Each monthly auction’s net transaction amounts plus a portion of the net proceeds of the seasonal auction for the season containing the same Trade Month shall be forwarded to the relevant CRRBA daily monthly accounts of the same month.
6.1 / The seasonal on-peak and off-peak net auction revenues shall be allocated to each month of the season in proportion to the number of on-peak and off-peak hours, respectively, in each month.
6.2 / The net auction transaction amounts shall be differentiated based on the time of use of each CRR holding. On-peak amounts shall be computed from CRR auction holdings with on-peak time of use, while off-peak amounts shall be computed from CRR auction holdings with off-peak time of use.

3.2  Predecessor Charge Codes

Charge Code/ Pre-calc Name /
None

3.3  Successor Charge Codes

Charge Code/ Pre-calc Name /
CC 6790 - CRR Balancing Account /

3.4  Inputs – External Systems

Row # / Variable Name / Description /
1 / BAResourceCRRAuctionTransactionAmt BrtzN’t’UU’md / Transaction amount for CRR z for its source or sink node resource r at Auction Market Name N’ with a TOU of t’ for Business Associate B for bill_period_start U’ and bill_period_end U’, with an auction completion date of Trading Day d of Trade Month m. ($)
Note: Sign flipping is necessary for sink node resource transaction amounts. Attribute t shall always be null or empty for the input. The source node and sink nodes of CRR auction holdings are mapped as attribute r in this input.
Also, a special mapping rule is provided on how to generate U’U’ as well as the values for the splitting of original seasonal transaction amount records into monthly records.
Creation of BAResourceCRRAuctionTransactionAmt BrtzN’t’UU’md :
For each CRR Auction Transaction Amount and specific TOU, the data mapping splits the records such that each record represents a single bill period with the bill_period_start and bill_period_end attributes representing the start and stop dates of the bill period within the auction duration. The original amount is prorated based on the number of matching TOU hours within the bill period vs. the number of matching TOU hours within a particular CRR Auction. For example, for the AUC_AN_20080401_20080630_TC and assuming this is for TOU of “ON” with $300 proceeds from the auction. Using the current TOU hours definition to pro-rate, having 416 on-peak hours for April 2008, 416 on-peak hours for May 2008, and 400 on-peak hours for June 2008, and a total of 1232 on-peak hours for the season, then data mapping will generate 3 records for April, May and June, with $101.3, $101.3, and $97.4 as the interval values, respectively.
No prorata is required for the monthly or one-time auctions, however, data mapping still needs to generate bill_period_start and bill_period_end attributes parsed from the auction market name.

3.5  Inputs - Predecessor Charge Codes or Pre-calculations

Row # / Variable Name / Predecessor Charge Code/ Pre-calc Configuration
None

3.6  CAISO Formula

3.6.1  The settlement amount to Business Associate B for CRR ID z at Auction Market N’ :

BACRRAuctionTransactionAmount BzN’md =

BAResourceCRRAuctionTransactionAmt BrtzN’t’UU’md

3.6.2  BAResourceCRRAuctionAmount BrtzN’t’md =

BAResourceCRRAuctionTransactionAmt BrtzN’t’UU’md

3.6.3  CAISOCRRAuctionMarketTOUTotalRevenueforMonthAmount U’Ut; =

BAResourceCRRAuctionTransactionAmt BrzN’t’UU’md

Implementation Note: This value summed over all auction market names N’ having the same bill period start and bill period end (i.e., the same month, more accurately the monthly auction contribution and the monthly contribution from a seasonal auction for the same month) would correspond to the CAISO-wide net transaction amounts that must go to CRR Balancing account for the relevant month. Attributes m and d of BAResourceCRRAuctionTransactionAmount BrtzN’t’UU’md shall be ignored, particularly that attribute m in this input would not necessarily correspond to the month bounded by U’ and U.

CAISOCRRAuctionMarketTOUTotalRevenueforMonthAmount UU’t’ shall be used in CC6790 and will be shown in that charge code as CAISOMonthlyCRRAuctionMarketTOUTotalRevenueAmount t’m, where m in the latter is the converted month period bounded by U’ and U.

3.6.4  CAISODailyCRRAuctionMarketTotalRevenueforMonthAmount U’U =The amount of net auction proceeds going into the relevant CRR Balancing Account (CRRBA) monthly account identified by the month period bounded by U (bill_period_start) and U’ (bill_period_end):

CAISODailyCRRAuctionMarketTotalRevenueforMonthAmount UU’ =

CAISOCRRAuctionMarketTOUTotalRevenueforMonthAmount UU’t;BAResourceCRRAuctionTransactionAmt BrtzN’t’UU’md

Implementation Note: This value summed up over all auction market names N’ having the same bill period start and bill period end (i.e., the same month, more accurately the monthly auction contribution and the monthly contribution from a seasonal auction for the same month) would correspond to the CAISO-wide net transaction amounts that must go to CRR Balancing account for the relevant month. Attributes m and d of BAResourceCRRAuctionTransactionAmount BrtzN’t’UU’md shall be ignored, particularly that attribute m in this input would not necessarily correspond to the month bounded by U and U’. The above sum of CAISOCRRAuctionMarketTOUTotalRevenueforMonthAmount U’Ut; for time of use t’ for on-peak (1) and off-peak (0) corresponds to the total monthly auction revenues, which is invested by CAISO if held more than a month and accrues interest. The interest is allocated in CC 6791, CRRBA Accrued Interest Allocation.