SaMC / Version: 1.7
Configuration Guide for: MSS Netting / Date: 5/29/07

Settlements & Billing

BPM Configuration Guide:MSS Netting

Pre-calculation

Version 5.10

Confidential / CAISO, 2018 / Page 1 of 55
Settlements & Billing / Version: 5.01
Configuration Guide for: MSS Netting / Date: 04/01/0902/05/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 Dates

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

In the allocation of various payment and charges, the amounts are divided among Business Associates (BAs) in proportion to their relative contribution to the overall Measured Demand quantity (in MWh) over which the allocation is performed. Thus, an allocation of payment or charges requires the following two components calculated for the particular time period over which the allocation is performed:

The overall metered CAISO Demand plus Real-Time Interchange export schedules in the grid sector or area over which the allocated payments and charges apply and

the contribution of each Business Associate to the overall CAISO Demand plus Real-Time Interchange export schedules referenced in the prior item.

To provide the Measured Demand quantities that are used in multiple Charge Code calculations that allocate various payments or charges, the CAISO implements a set of Pre-calculation processes, referred to as Measured Demand Pre-calculations, to calculate particular Measured Demand quantities. There are five (5) Measured Demand Pre-calculation configurations in which an overall Measured Demand quantity is calculated. The five Pre-calculations differ by the composition of the Loads and exports that are included in their Measured Demand outputs. The Measured Demand Pre-calculation process configurations, the Load and export composition of their outputs, and the associated output frequency (10-minute, hourly, etc.) are identified in the following table.

Measured Demand Pre-calculation Configurations
Name / Output Composition and Frequency / Dependent Allocation Charge Codes
MD over Control Area Pre-calculation / Composition:
Measured Demand:
The sum ( as a negative value) of all
(a) metered CAISO Demand
(b) Real-Time Interchange export schedules
Net MSS Measured Demand:
The lesser of
(a) zero (0)
or the net value defined as
(b) the sum of Meter Data (as a negative value) for Demand of all Loads internal to an MSS
plus(+) the sum of
(c) Meter Data representing Generation of all Generating Units for the MSS
to which lesser value is added
(d) the sum of all of the MSS Real-Time Interchange export schedules (as a negative value).
Frequency:
10-minute, hourly, daily / CC 6474 - Real Time Unaccounted for Energy Settlement
CC 6477 - Real Time Imbalance Energy Offset
CC 6480 - Excess Cost Neutrality Allocation
CC 6637 - IFM Bid Cost Recovery Tier 2 Allocation
CC 6678 - Real Time Bid Cost Recovery Allocation
CC 6774 - RT Congestion Offset
CC 6807 - Day Ahead Residual Unit Commitment (RUC) Tier 2 Allocation
CC 6947 - IFM Marginal Losses Surplus Credit Allocation
CC 525 – Yearly FERC Fee Under/Over Recovery
CC 550 – Monthly FERC Fee Settlement
CC 551 – Annual FERC Fee Settlement
CC 4501, 4502 and 4505 (GMC Variants)
CC 4999 – Rounding Adjustment
CC 8999 – Neutrality Adjustment
Pre-calc – Real Time Price
MD over Control Area Excl MSS Energy Pre-calculation / Composition:
Measured Demand:
The sum (as a negative value) of all
(a) metered CAISO Demand
(b) Real-Time Interchange export schedules
The overall Measured Demand output quantity excludes Energy from MSS entities.
Frequency:
10-minute and monthly / CC 1302 - Long-Term Voltage Support Allocation
CC 1303 - Supplemental Reactive Energy Allocation
MD Emissions over Control Area Excl External Exports Pre-calculation / Composition:
Measured Demand (in-state):
The sum (as a negative value) of all
(a) metered CAISO Demand
(b) in-state Real-Time Interchange export schedules
The sum excludes CAISO-external exports and any external contractual Transmission Loss adjustments.
Net MSS Measured Demand (in-state):
The lesser of
(a) zero (0)
or the net value defined as
(b) the sum of Meter Data (as a negative value) for Demand of all Loads internal to an MSS
plus (+) the sum of
(c) Meter Data representing Generation of all Generating Units for the MSS
to which lesser value is added
(d) the sum of all of the MSS in-state Real-Time Interchange export schedules (as a negative value).
The sum excludes CAISO-external exports and any external contractual Transmission Loss adjustments.
Frequency:
Monthly / CC 591 – Emissions Cost Recovery
MD Black Start Excl Exports Pre-calculation / Composition:
Metered CAISO Demand:
the sum (as a negative value) of all metered CAISO Demand.
Net MSS Demand:
The greater of
(a) zero (0)
or the net value defined as
(b) the sum of Meter Data ( as a negative value) for Demand of all Loads internal to an MSS,
Plus (+) the sum of
Meter Data representing Generation of all Generating Units for the MSS.
Frequency:
Hourly / CC 1353- Black Start Energy Allocation
MD over Control Area Excl Transmission Loss Adjustment Pre-calculation / Composition:
Measured Demand:
The sum (as a negative value) of all
(a) metered CAISO Demand
(b) Real-Time Interchange export schedules
The calculated value excludes contractual Transmission Loss adjustments.
Net MSS Measured Demand:
The lesser of
(a) zero (0)
or the net value defined as
(b) the sum of Meter Data for Demand (as a negative value) of all Participating Loads internal to an MSS
plus (+) the sum of
(c) Meter Data representing Generation of all Generating Units for the MSS
to which lesser value is added
(d) the sum of all of the MSS Real-Time Interchange export schedules (as a negative value).
The calculated value excludes contractual Transmission Loss adjustments.
Frequency:
10-minute and Hourly / CC 6977 – Allocation of Transmission Loss Obligation Charge for Real Time Schedules under Control Agreement

Some of the Measured Demand configurations listed above recognize exemptions to the calculation for various Business Associates and resources. In some instances a Measured Demand configuration may produce multiple outputs, each one recognizing a particular exemption or set of exemptions. For each Measured Demand calculation, its exemptions are determined and defined by the requirements of the allocations in which the Measured Demand Pre-calculation outputs are employed.

2.2Description

Some of the Measured Demand Pre-calculation configurations identified in the table of Measured Demand Pre-calculations presented in the prior section require a net MSS Measured Demand quantity or a net MSS Demand quantity. Net MSS Demand (in MWh as a negative value) is calculated as the lesser of zero (0) or the sum of Meter Data for Demand (in MWh as a negative value) of all Participating Loads internal to the MSS plus the Meter Data representing the Generation (in MWh as a positive value) of all MSS Generating Units. Net MSS Demand does not include the Energy of Real-Time Interchange export schedules. Net MSS Measured Demand (in MWh as a negative value), on the other hand, is defined to be the lesser of zero (0) or Net MSS Demand, to which lesser value is added the sum of the Energy (in MWh as a negative value) for all Real-Time Interchange export schedules. To satisfy the varying requirements of different Measured Demand Pre-calculations, the MSS Netting calculates Net MSS Measured Demand or net MSS Demand quantities in various output configurations.

Reflecting the difference in the requirements for each output based on transmission components and output frequency, the MSS Netting offers seven different net Measured Demand outputs (with one of the outputs actually representing a net MSS Demand quantity due to its omission of export Energy). The outputs differ in their representation of net Measured Demand based on the inclusion or exclusion of in-state Real-Time Interchange exports, net exports and contractual Transmission Losses. Each output from the MSS Netting is resolved to a particular combination of three (3) levels – the MSS entity, the Business Associate scheduling Energy for the MSS entity, and the output frequency. Net MSS Measured Demand quantities are output in multiple frequencies – 10-minute and hourly, The outputs are generated for the successor Measured Demand Pre-calculations, where a net MSS Measured Demand or MSS Demand value at a specific frequency is required in the calculation of a Measured Demand output.

3.Charge Code Requirements

3.1Business Rules

Bus Req ID / Business Rule
1.0 / The MSS Netting shall perform a set of calculations to determine and output net MSS Measured Demand in different output configurations based on the inclusion or exclusion of in-state exports and contractual Transmission Losses, per the requirements of successor Measured Demand Pre-calculation processes.
1.1 / The Net MSS Measured Demand calculations shall include calculations for net MSS Demand, net MSS Supply and net MSS Energy.
1.1.1 / Each net MSS Measured Demand output shall be <= 0
1.1.2 / When MSS Supply exceeds Demand in a net MSS Demand calculation, the net MSS Demand output(s) shall = 0.
1.1.3 / When MSS Demand exceeds Supply in a net MSS Supply calculation, the net MSS Supply output(s) shall = 0.
1.1.4 / MSS Energy shall be calculated as the difference between MSS Supply and MSS Demand.
1.1.4.1 / MSS Energy shall be > 0 when MSS Supply exceeds MSS Demand.
1.1.4.2 / MSS Energy shall be < 0 when MSS Demand exceeds MSS Supply.
1.1.4.3 / MSS Energy shall be = 0 when MSS Supply equals MSS Demand.
1.2 / Net MSS Measured Demand shall be calculated and output for each Trading Hour for each combination of MSS entity and Business Associate scheduling Energy for the MSS entity.
1.3 / Net MSS Measured Demand shall be calculated and output for each (10-minute) Settlement Interval for each combination of MSS entity and Business Associate scheduling Energy for the MSS entity.
1.4 / Net MSS Measured Demand with exports restricted to in-state destinations shall be calculated and output for each Trading Hour for each combination of MSS entity and Business Associate scheduling Energy for the MSS entity.
1.5 / Net MSS Measured Demand with exports restricted to in-state destinations shall be calculated and output for each (10-minute) Settlement Interval for each combination of MSS entity and Business Associate scheduling Energy for the MSS entity.
1.6 / Net MSS Measured Demand with the exclusion of contractual Transmission Loss Energy shall be calculated and output for each (10-minute) Settlement Interval for each combination of MSS entity and Business Associate scheduling Energy for the MSS entity.
1.7 / Net MSS Demand shall be calculated and output for each Trading Hour for each combination of MSS entity, Aggregated Pricing Node, Aggregated Pricing Node Type, and Business Associate scheduling energy for the MSS entity.
1.8 / Net MSS Demand shall be calculated and output for each (10-minute) Settlement Interval for each combination of MSS entity, Aggregated Pricing Node, Aggregated Pricing Node Type, and Business Associate scheduling energy for the MSS entity.
1.9 / The MSS Netting Pre-calculation shall calculate and output the Metered CAISO Demand value of a resource r for each combination of attribute subscriptsBrtuT’I’Q’M’AA’F’R’pPW’QS’d’Nz’VvHn’L’mdhif.
1.9.1 / The MSS Netting Pre-calculation shall perform its Metered CAISO Demand calculation with meter input data of either 5-minute, 10-minute or 1-hour resolution, with the exact input data frequency dependent on the exact resource to which the data applies.
1.9.2 / The Metered CAISO Demand value shall be output on both a Dispatch Interval basis (i.e., as 5-minute data) and Settlement Interval basis (i.e., as 10-minute data), regardless of the frequency of the meter input data.
1.10 / The MSS Netting Pre-calculation shall calculate and output the Metered Generation value of a resource r for each combination of attribute subscriptsBrtuT’I’Q’M’AA’F’R’pPW’QS’d’Nz’VvHn’L’mdhif.
1.10.1 / The MSS Netting Pre-calculation shall perform its Metered Generation calculation with meter input data of either 5-minute, 10-minute or 1-hour resolution, with the exact input data frequency dependent on theresource to which the data applies.
1.10.2 / The Metered Generation value shall be output on both a Dispatch Interval basis (i.e., as 5-minute data) and Settlement Interval basis (i.e., as 10-minute data), regardless of the frequency of the meter input data.
1.11 / Pump units that provide nonspin Energy shall have a single meter that reflects metered Demand for the pump Load netted with the pump’s Generation. (Fact)
1.11.1 / The MSS Netting Pre-calculation data mapping process shall separate pump Generation (nonspin Energy) from pump metered Demand forthe single input that provides net-Metered Demand (net ofGeneration)for a pump unit. The separation shall result in 2 inputs, one (the metered Demand input) that reflects pump Load Demand, and another one (the metered Generation input) that reflects the pump’s Generation.
1.11.1.1 / The data mapping process shall provide separate metered Demand and metered Generation inputs for a pump unit by using the pump’s DA (IFM) Load schedule and its instructed real-time Energy as well as the pump’s single net-Metered Demand input.
2.0 / Contractual Transmission Losses, representing the Energy of Transmission Losses that are covered by agreements between transmission line operators and the CAISO, shall be included as export Energy in the calculation of a particular net MSS Measured Demand quantity, unless otherwise indicated in the associated output formula(s) for the net MSS Measured Demand quantity.
3.0 / PTB Charge Adjustment does not apply to the MSS Netting Pre-calculation process. (Fact)

3.2Predecessor Charge Codes

Charge Code/ Pre-calc Name
Allocation of Transmission Losses under Operating Agreements
System Resource Deemed Delivered Energy Quantity

3.3Successor Charge Codes

Charge Code/ Pre-calc Name
CC 711 Intermittent Resources Net Deviations Settlement
CC 1407 MSS Positive Deviation Penalty
CC 2407 MSS Negative Deviation Penalty
CC 6474 Real Time Unaccounted for Energy Settlement
Pre-calculation Measured Demand over Control Area
Pre-calculation Measured Demand over Control Area Excl MSS Energy
Pre-calculation Measured Demand Emissions over Control Area Excl External Exports
Pre-calculation Measured Demand Black Start Excluding Exports
Pre-calculation Measured Demand over Control Area ExcludingTransmission Loss Adjustment
Pre-calculation Metered Energy Adjustment Factor
Pre-calculation Ancillary Services
Pre-calculation ETC/TOR/CVR Quantity
Pre-calculation HVAC Metered Load
Pre-calculation RealTime Energy Quantity
Pre-calculation Real Time Price

3.4Inputs – External Systems

Row # / Variable Name / Description
1 / BAResEntityDispatchIntervalMeteredQuantity BrtuT’I’Q’M’AA’m’F’R’pPW’QS’d’Nz’VvHn’L’mdhif / Metered quantity (in MWh) provided by OMAR for resource ID r, where the resource type t = ‘GEN’ or ‘LOAD’ ,or where the Entity Component Type F’ = ‘NETMD’. Demand quantities are represented as negative values, while supply quantities are represented as positive values.
The input represents 5-minute meter data received from OMAR MV-90 Channel ID m’ for a resource having resource ID r, resource type t, entity component type F’ and entity component subtype S’, where r is associated with UDC/MSS u of entity type T’ and gross/net settlement type I’, having MSS Emissions Pay Flag W’, RUC Participation Flag V, Load Following Selection Flag L’, Aggregated Pricing Node A of Aggregated Pricing Node Type A’, and MSS subgroup M’.The resource is scheduled by Business Associate B for Dispatch Interval f of Settlement Interval i, Trading Hour h, Trading Day d and Trading Month m.
Data Mapping Considerations for OMAR Payload data having Meter Channel ID m’ = 1:
When the Meter Channel ID m’ = 1, the input is generated by data mapping for resource ID values r (as identified by the OMAR meter data) in cases where
(a)resource type t = ‘LOAD’ and F’ > ‘NETMD’, where the t and F’ values associated with r are determined through Master File data, or
(b) T’ = MSS and F’ = ‘NETMD’ and either
  1. S’ = ‘ND’ for cases of net MSS Demand (where MSS Demand exceeds MSS Generation), or
  2. S’ = ‘GL’ for cases where the input represents MSS gross load,
    or
(c)F’ = ‘PMPST’ or F’ = ‘PMPP’.
In the preceding conditions, values for B, t, T’, F’ and S’ are obtained through Master File associations with resource ID r.
For preceding condition (a), where the Master File value t = ‘LOAD’, in mapping input BAResEntityDispatchIntervalMeteredQuantity BrtuT’I’Q’M’AA’m’F’R’pPW’QS’d’Nz’VvHn’L’mdhif the data mapping process shall set the input’s t value to ‘LOAD’, except as defined otherwise below for cases where F’ is ‘PMPP’ or ‘PMPST’.
For preceding condition (b).a, where the Master File value for S’ = ‘ND’, in mapping input BAResEntityDispatchIntervalMeteredQuantity BrtuT’I’Q’M’AA’m’F’R’pPW’QS’d’Nz’VvHn’L’mdhif the data mapping process shall set the input’s S’ value to ‘ND’ and its t value to ‘LI’.
For preceding condition (b).b (where the Master File value for S’ = ‘GL’), in mapping input BAResEntityDispatchIntervalMeteredQuantity BrtuT’I’Q’M’AA’m’F’R’pPW’QS’d’Nz’VvHn’L’mdhif the data mapping process shall set the input’s value for S’ to ‘NPL’ and its t value to ‘LOAD’. Thus, the input will represent a MSS Gross Load resource (with Resource ID r) when F’ = ‘NETMD’ and S’ = ‘NPL’.
For preceding condition (c), where the Master File value F’ = ‘PMPST’, in mapping input BAResEntityDispatchIntervalMeteredQuantity BrtuT’I’Q’M’AA’m’F’R’pPW’QS’d’Nz’VvHn’L’mdhif the data mapping process shall set the input’s t value as defined below in the data mapping instructions specific to pump and pump storage devices.
Data Mapping Considerations for OMAR Payload data having Meter Channel ID m’ = 4:
Similarly, when the Meter Channel ID m’ = 4, the input is generated by data mapping for resource ID values r (as identified by the OMAR meter data) in cases where
(a)resource type t = ‘GEN’, where the t value associated with r is determined through Master File data, or