Settlements & Billing / Version: 5.12
Configuration Guide for: Core Reliability Services Non-Coincident Off-Peak / Date: 05/21/10 12/15/10

Settlements & Billing

BPM Configuration Guide:Core Reliability Services Non-Coincident Off-Peak

CC 4502

Version 5.12

CAISO, 2018 / Page 1 of 7
Settlements & Billing / Version: 5.12
Configuration Guide for: Core Reliability Services Non-Coincident Off-Peak / Date: 05/21/10 12/15/10

Table of Contents

1.Purpose of Document

2.Introduction

2.1Background

2.2Description

3.Charge Code Requirements

3.1Business Rules

3.2Predecessor Charge Codes

3.3Successor Charge Codes

3.4Inputs – External Systems

3.5Inputs - Predecessor Charge Codes or Pre-calculations

3.6CAISO Formula

3.7Outputs

4.Charge Code Effective Date

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.1Background

Grid Management Charge Codes are monthly charges assessed to participating Scheduling Coordinators for the purpose of recovering all of the CAISO’s administrative and operating costs. These costs include, but are not limited to, startup, development, financing, and the costs of ongoing operation and maintenance associated with the CAISO’s Control Area operator responsibilities. Grid Management Charges also include costs associated with administering the scheduling, bidding, dispatch, and settlement of all Energy and Ancillary Services.

GMC rates are calculated as set forth in Section 11 of the CAISO Tariff. The formula rate methodology provides Market Participants with the financial security of predictable GMC pricing while ensuring that the CAISO is able to recover its actual costs in a timely manner. The charges are shown as a monthly charge on the Settlements Statements for the last day of each month, with billable quantities being published on daily statements where applicable. GMC charges are one-sided and do not offset with any other charge code for neutrality.

Core Reliability Services are the basic services needed to manage the Control Area reliably and safely. The calculation of the Core Reliability Service Charge Codes shall be reflective of the cost of maintaining operational control at all times of the day and seasons of the year, as well the stress that entities place on the transmission system.

2.2Description

The Charge Code, GMC Core Reliability Services Non-Coincident Off-Peak (NCOP), is determined on a gross basis considering the hours ending between 23 and 6. The monthly NCOP Load Quantity is identified as the hour within in a Trading Month that has he highest metered Demand quantity (excluding export quantities) for a Scheduling Coordinator. A Scheduling Coordinator’s NCOP Demand reflects the burden that the entity places on the operation of the transmission system.

3.Charge Code Requirements

3.1Business Rules

Bus Req ID / Business Rule
1.0 / This charge is a monthly charge settled on the last day of each month.
2.0 / Where input Bill Determinants are not daily, or activity across a Bill Period is required to determine the appropriate Settlement Amount, the Charge Code shall be calculated on a monthly basis and output on the last Settlement Statement for a Trading Month.
3.0 / Either CC 4501 (peak) or CC 4502 (off peak) will be charged, but not both; depending upon in which hour the Scheduling Coordinator’s maximum metered Demand occurs.
3.1 / The system determines the single hour in which the highest/maximum metered Load occurs for a Scheduling Coordinator by examining Trading Hours ending 23 through 6 for all Trading Days within a Trading Month.
4.0 / For adjustments to the Charge Code that cannot be accomplished by correction of upstream data inputs/recalculation or operator override Pass Through Bill Charge logic will be applied.
5.0 / Settlements system shall be able to identify specific registered resources as exempted resources from this Charge Code.
6.0 / A Scheduling Coordinator’s NCOP Demand reflects the burden that the entity places on the operation of the transmission system within a Trading Month.

3.2Predecessor Charge Codes

Charge Code/ Pre-calc Name
Measured Demand Over Control Area Pre-Calculation

3.3Successor Charge Codes

Charge Code/ Pre-calc Name
None

3.4Inputs – External Systems

Row # / Variable Name / Description
1 / GMCCoreReliabilityServiceNonCoincidentOffPeakRate / FERC approved GMC rate from settlements standing data based on applicable start and end dates.
2 / PTBChargeAdjustmentGMCCoreReliabilityServicesNonCoincidentOffPeakSettlementAmountBJm / PTB adjustment variable for this Charge Code, amount per SC. ($)
3 / TORExceptionFlag B / Flag indicating exception from Charge Code, where exception is represented by “1”.

3.5Inputs - Predecessor Charge Codes or Pre-calculations

Row # / Variable Name / Predecessor Charge Code/
Pre-calc Configuration
1 / BAHourlyTotalGrossMeteredCAISODemandQuantity_GMC_MDOverCA Bmdh / Measured Demand Over Control Area Pre-Calculation

3.6CAISO Formula

3.6.1IF TORExceptionFlag B = 1

THEN

GMCCoreReliabilityServicesNonCoincidentOffPeakSettlementAmountBm = 0

ELSE

GMCCoreReliabilityServicesNonCoincidentOffPeakSettlementAmountBm

= MonthlyGMCNonCoincidentOffPeakLoadQuantityBmh * GMCCoreReliabilityServiceNonCoincidentOffPeakRate

3.6.1.1Where

MonthlyGMCNonCoincidentOffPeakLoadQuantityBmh =Abs(Min(0,BAHourlyTotalGrossMeteredCAISODemandQuantity_GMC_MDOverCA Bmdh))

where h m

NOTE: This calculation is performed through the use of custom function. This function identifies the MonthlyGMCNonCoincidentOffPeakLoadQuantity, MonthlyGMCNonCoincidentOffPeakLoadTradeDayHour Bm represents the Trade Hour, and MonthlyGMCNonCoincidentOffPeakLoadTradeDay Bm represents the day in which the MonthlyGMCNonCoincidentOffPeakLoadQuantity was identified.

3.6.1.1.1Where

BAHourlyTotalGrossMeteredCAISODemandQuantity_GMC_MDOverCA Bmdh is within Trading Hour ( h ) 23 through HE 6 for Trading Month (m).

3.6.1.2Where

GMCCoreReliabilityServiceNonCoincidentOffPeakRateis the current FERC approved rate for the CAISO Control Area

3.7Outputs

Output Req ID / Name / Description
In addition to any outputs listed below, all inputs shall be included as outputs.
1 / GMCCoreReliabilityServicesNonCoincidentOffPeakSettlementAmountBm / The total amount charged to a Scheduling Coordinator for Core Reliability Services Non Coincident Off Peak in Trading Month m.
2 / MonthlyGMCNonCoincidentOffPeakLoadQuantityBmh / The maximum hourly load quantity for a Scheduling Coordinator in Trading Month m, excluding exemptions.
In order to help participants validate the Billable Quantity, the output file will include:
Interval 1: Quantity
Interval 2: Trade Hour
Interval 3: Day within the Trade Month is identified.
3 / MonthlyGMCNonCoincidentOffPeakLoadTradeDayHour Bm / Trade Hour within the Trade Day in which the Coincident Peak Quantity was identified
-- Informational Only --
4 / MonthlyGMCNonCoincidentOffPeakLoadTradeDay Bm / Trade Day within the Trade Period in which the Coincident Peak Quantity was identified
-- Informational Only --

4.Charge Code Effective Date

Charge Code/
Pre-calc Name / Document Version / Effective Start Date / Effective End Date / Version Update Type
CC 4502 – GMC Core Reliability Services Non-Coincident Off Peak / 5.0 / 04/01/09 / 03/31/09 / Documentation Edits Only
CC 4502 – GMC Core Reliability Services Non-Coincident Off Peak / 5.1 / 04/01/09 / Open 3/31/09 / Configuration Impacted
CC 4502 – GMC Core Reliability Services Non-Coincident Off Peak / 5.2 / 04/01/09 / Open / Configuration Impacted
CAISO, 2018 / Page 1 of 7