Inputs to NIST PAP03 Activity

Pricing Information from CIM, SEP 1.0 and OpenADR & Recommendations

Contact jzhou@xtensible.net for further information

Note: Major portion of slides regarding CIM/SEP/OpenADR are produced by Greg Robinson and Steve Van Ausdall;

Information contained in this presentation are extracted from various existing documents and may not represent the actual standards or their future

direction, and should be used for discussion purpose only.

Key Points for Consideration

• Electricity wholesale market price are determined by bids from supply and demand resources with security constraints, and are settled thereafter.

• Consumers cost of electricity is governed by tariff by PUC or price structure determined by an ESP in a deregulated retail market. Settled price on the wholesale market is not the same as the tariff or retail price that a consumer would pay. Only a few large C&I customers may participate directly in the wholesale market.

• There might be some shared attributes between the bid/settlement at the wholesale level and the tariff/pricing at the retail level. But they are fundamentally different concepts. The wholesale price will obviously affect the retail price, but not in a direct way because there are middleman here (utility, ESP, aggregator etc.)

What Objectives?

• Are we to standardize bids and settlement at the wholesale market level across the country? What benefits do we expect to achieve if so?

• Are we to expect that there will be millions of market participants in the future electricity market, therefore requiring a market environment that supports high volume/speed transactions?

• Are we really to standardize the tariff/pricing model from utility and/or service provider down to the end consumers?

• What/how do we expect the pricing translation (from business terms) from wholesale to retail in the future in each of the jurisdictions in USA? Will disparity continue or uniformity prevail?

A Bit of Background on the IEC Common Information Model (CIM)

• A Unified Modeling Language (UML) based information model representing real-world objects and information entities exchanged within the value chain of the electric power industry

– Has been maintained in IBM’s Rational Rose modeling tool, but is transitioning to Enterprise Architect

– Available in many formats (mdl, cat, eap, xmi, html, owl)

• Enable integration of applications/systems– Provides a common model behind all messages exchanged between

systems– Basis for defining information exchange models

• Enable data access in a standard way– Common language to navigate and access complex data structures in any

database– Inspiration for logical data schemas (e.g., for an operational data store)

• Not tied to a particular application’s view of the world

CIM Packages

Generation

Domain

Wires

LoadModel

Core

Meas

Topology

Outage Protection

Financial

EnergyScheduling

Reservation

SCADA

Core2

Assets Documents

Consumer

GMLSupport

ERPSupport

WG13

WG14

MeteringWorkMgmt

Bid

RTO

Resource

SecurityConstraints

FTR

ClearingResults

WG16

class training01

Assets::Pole{leaf}

+ baseKind: PoleBaseKind [0..1]+ breastBlock: Boolean [ 0..1]+ construction: String [0..1]+ jpaReference: String [0..1]+ preservativeKind: PolePreservativeKind [0..1]+ treatedDate: AbsoluteDateT ime [0..1]+ treatmentKind: PoleT reatmentKind [0..1]::Struct ure+ fum igantAppl iedDate: AbsoluteDate [0..1]+ fum igantName: String [0..1]+ height: ShortLength [0..1]+ materialKind: StructureMaterialKind [0..1]+ removeWeed: Boolean [0..1]+ weedRemovedDate: AbsoluteDate [0..1]::Asset+ appl ication: String [0..1]+ category: String [0..1]+ code: String [0..1]+ cri tical : Boolean [0..1]+ ini tialCondition: String [0..1]+ ini tialLossOfLi fe: PerCent [0..1]+ instal lationDate: AbsoluteDateT ime [0..1]+ lotNumber: String [0..1]+ manufacturedDate: AbsoluteDateT ime [0..1]+ purchasePrice: Money [0..1]+ serialNumber: String [0..1]+ testDate: AbsoluteDateT ime [0..1]+ testStatus: Boolean [ 0..1]+ testT ype: String [0..1]+ utcNumber: String [0..1]::Identi fiedObject+ al iasName: String [0..1]+ description: String [0..1]+ localName: String [0..1]+ mRID: String [0..1]+ name: String [0..1]+ pathName: String [0..1]

Assets::Structure

Assets::AssetContainer

Assets::Asset

Core::IdentifiedObj ect

ElectricalAsset

AssetsPointOriented::Streetlight{leaf}

+AttachedT oPole

0..1

+SupportStreetl ights

0..*

Class Name usually describes things in the real world

Class Attributes describesignificant aspects about the thing

This Specialization indicates that a “Pole” is a type of“Structure.” Since a “Structure” is a type of “Asset,” the Pole inherits all of the attributes from both Structure and Asset

Associations connect classes and areassigned a role that describes the relationship

Examples of Bids for Wholesale Market (from CIM – IEC TC57 WG16 – draft and for reference only)

class Bid

LoadBid{leaf}

+ dropRampRate: Float [0..1]+ minLoad: ActivePower [0..1]+ minLoadReduction: ActivePower [0..1]+ minLoadReductionCost: Money [0..1]+ minLoadReductionInterval: Minutes [0..1]+ minTimeBetLoadRed: Minutes [0..1]+ pickUpRampRate: Float [0..1]+ reqNoticeTime: Minutes [0..1]+ shutdownCost: Money [0..1]

Core::Curv e

+ curveStyle: CurveStyle [0..1]+ xMultipl ier: UnitMultipl ier [0..1]+ xUnit: UnitSymbol [0..1]+ y1Multipl ier: UnitMultipl ier [0..1]+ y1Unit: UnitSymbol [0..1]+ y2Multipl ier: UnitMultipl ier [0..1]+ y2Unit: UnitSymbol [0..1]

DocumentInheritance::Document

+ comments: String [0..1]+ createdDateTime: AbsoluteDateTime [0..1]+ docStatus: String [0..1]+ docStatusDate: AbsoluteDateTime [0..1]+ docTitle: String [0..1]+ docType: String [0..1]+ lastModified: AbsoluteDateTime [0..1]+ revisionNumber: String [0..1]+ subject: String [0..1]

ResourceBid

+ commodityType: String [0..1]+ energyMaxDay: ActivePower [0..1]+ energyMinDay: ActivePower [0..1]+ shutDownsMaxDay: Integer [0..1]+ shutDownsMaxWeek: Integer [0..1]+ startUpsMaxDay: Integer [0..1]+ startUpsMaxWeek: Integer [0..1]+ virtual: Boolean [0..1] = "false"

NotificationTimeCurv e{leaf}

StartUpTimeCurv e{leaf}

BidSet{leaf}

StartUpCostCurv e{leaf}

GeneratingBid{leaf}

+ downTimeMax: Minutes [0..1]+ maxEmergencyMW: ActivePower [0..1]+ maximumEconomicMW: ActivePower [0..1]+ minEmergencyMW: ActivePower [0..1]+ minimumDownTime: Minutes [0..1]+ minimumEconomicMW: ActivePower [0..1]+ noLoadCost: Money [0..1]+ notificationTime: Minutes [0..1]+ operatingMode: String [0..1]+ startUpRampRate: Float [0..1]+ startupTime: Minutes [0..1]+ startUpType: Integer [0..1]+ upTimeMax: Minutes [0..1]+ upTimeMin: Minutes [0..1]

RegisteredGenerator{leaf}

Core::Curv eData{root,leaf}

+ xvalue: Float [0..1]+ y1value: Float [0..1]+ y2value: Float [0..1]

LoadReductionPriceCurv e{leaf}

EnergyScheduling::EnergyProfile

{leaf}

RegisteredLoad{leaf}

BidPriceCurv e{leaf}

MarketFactorsMarketProduct

{leaf}

ProductBid{leaf}

Market{leaf} Bid

+ marketType: String [0..1] = "DA"+ startTime: AbsoluteDateTime [0..1]+ stopTime: AbsoluteDateTime [0..1]

Pnode{leaf}

+ beginPeriod: AbsoluteDateTime [0..1]+ endPeriod: AbsoluteDateTime [0..1]+ isPublic: Boolean [0..1] = "true"+ type: String [0..1]+ usage: String [0..1]

EnergyScheduling::EnergyTransaction

TransactionBid{leaf}

+ EnergyTransId: String [0..1]

+BidPriceCurve 0..1

+ProductBids 0..*

+MarketFactors

0..*+Market

0..1

+MarketProducts

1..*+Market

0..1

+EnergyProfi les

1..*

+TransactionBid

1

+ProductBids

1..*

+Bid

1

+EnergyProfi les 1..*+EnergyTransaction 1

+Bids

0..*

+Market

1

+Delivery_Pnode 0..1

PointOfDelivery

+TransactionBids 0..*

+Receipt_Pnode 0..1

PointOfReceipt

+TransactionBids 0..*

+Pnode0..*

+AggregatePnodes0..*

+EnergyTransId

0..*

+EnergyTransId

0..1

+MarketProduct 1

+ProductBids 0..*

+GeneratingBids 1..*

+BidSet 0..1

+toDocuments0..* DocDocRole

+fromDocuments0..*

+RegisteredLoad 0..1

+LoadBids 0..*

+StartUpCostCurves 0..*

+RegisteredGenerators 0..*

+LoadBids 0..*

+LoadReductionPriceCurve 0..1

+GeneratingBids 0..*

+NotificationTimeCurve 0..1

+GeneratingBids 0..*

+StartUpTimeCurve 0..1

+RegisteredGenerator 0..1

+GeneratingBids 0..*

+CurveScheduleDatas 0..*

+CurveSchedule 1

+StartUpCostCurve 0..1

+GeneratingBids 0..*

Examples of Settlement for Wholesale Market (from CIM – IEC TC57 WG16 – draft and for reference only) class Settlement and Market Clearing

Market{leaf}

+ dst: Boolean [0..1]+ end: AbsoluteDateTime [0..1]+ localTimeZone: String [0..1]+ rampIntervalEnergy: Minutes [0..1]+ rampIntervalNonSpinRes: Minutes [0..1]+ rampIntervalReg: Minutes [0..1]+ rampIntervalSpinRes: Minutes [0..1]+ start: AbsoluteDateTime [0..1]+ timeIntervalLength: Minutes [0..1]+ type: String [0..1]

DocumentInheritance::Document

+ comments: String [0..1]+ createdDateTime: AbsoluteDateTime [0..1]+ docStatus: String [0..1]+ docStatusDate: AbsoluteDateTime [0..1]+ docTitle: String [0..1]+ docType: String [0..1]+ lastModified: AbsoluteDateTime [0..1]+ revisionNumber: String [0..1]+ subject: String [0..1]

TopLevel::Organisation

+ costCenterFlag: Boolean [0..1]+ currentStatus: String [0..1]+ governmentID: String [0..1]+ industryID: String [0..1]+ marketRole: String [0..1]+ mode: String [0..1]+ optOut: Boolean [0..1] = "false"+ organisationCode: String [0..1]+ organisationType: String [0..1]+ profitCenterFlag: Boolean [0..1]+ statusDate: AbsoluteDateTime [0..1]

EnergyScheduling::EnergyTransaction

+ congestChargeMax: Money [0..1]+ deliveryPointP: ActivePower [0..1]+ energyMin: ActivePower [0..1]+ firmInterchangeFlag: Boolean [0..1]+ reason: String [0..1]+ receiptPointP: ActivePower [0..1]+ state: String [0..1]

EnergyScheduling::Profile

Meas::Measurement

Meter{leaf}

Pnode{leaf}

+ beginPeriod: AbsoluteDateTime [0..1]+ endPeriod: AbsoluteDateTime [0..1]+ isPublic: Boolean [0..1] = "true"+ type: String [0..1]+ usage: String [0..1]

SchedulingCoordinator{leaf}

ERP_Support::ErpInvoiceLineItem

+ accountGL: String [0..1]+ dateGL: AbsoluteDateTime [0..1]+ end: AbsoluteDateTime [0..1]+ lineAmount: Float [0..1]+ lineNumber: String [0..1]+ lineType: String [0..1]+ lineVersion: String [0..1]+ netAmount: Float [0..1]+ previousAmount: Float [0..1]+ start: AbsoluteDateTime [0..1]+ status: String [0..1]+ statusDateTime: AbsoluteDateTime [0..1]+ statusRemarks: String [0..1]

BillDeterminant{leaf}

+ calculationLevel: String [0..1]+ configVersion: String [0..1]+ numberInterval: Integer [0..1]+ precisionLevel: String [0..1]+ unitOfMeasure: String [0..1]

Settlement{leaf}

+ tradeDate: AbsoluteDateTime [0..1]

MarketStatement{leaf}

+ end: AbsoluteDateTime [0..1]+ referenceNumber: String [0..1]+ start: AbsoluteDateTime [0..1]+ tradeDate: AbsoluteDateTime [0..1]+ transactionDate: AbsoluteDateTime [0..1]

ERP_Support::ErpLedgerEntry{leaf}

+ accountID: String [0..1]+ accountType: String [0..1]+ amount: Float [0..1]+ postedDate: AbsoluteDateTime [0..1]+ transactionDate: AbsoluteDateTime [0..1]

MarketStatementLineItem{leaf}

+ currentAmount: Float [0..1]+ currentISOAmount: Float [0..1]+ currentISOQuantity: Float [0..1]+ currentPrice: Float [0..1]+ currentQuantity: Float [0..1]+ intervalDate: AbsoluteDateTime [0..1]+ intervalNumber: String [0..1]+ netAmount: Float [0..1]+ netISOAmount: Float [0..1]+ netISOQuantity: Float [0..1]+ netPrice: Float [0..1]+ netQuantity: Float [0..1]+ previousAmount: Float [0..1]+ previousISOAmount: Float [0..1]+ previousISOQuantity: Float [0..1]+ previousQuantity: Float [0..1]+ previsouPrice: Float [0..1]+ quantityUOM: String [0..1]

PassThroughBill{leaf}

+ amount: Money [0..1]+ billedTo: String [0..1]+ billEnd: AbsoluteDateTime [0..1]+ billRunType: String [0..1]+ billStart: AbsoluteDateTime [0..1]+ effectiveDate: AbsoluteDateTime [0..1]+ isDisputed: Boolean [0..1]+ isProfiled: Boolean [0..1]+ paidTo: String [0..1]+ previousEnd: AbsoluteDateTime [0..1]+ previousStart: AbsoluteDateTime [0..1]+ price: Money [0..1]+ productCode: String [0..1]+ providedBy: String [0..1]+ quantity: Float [0..1]+ serviceEnd: AbsoluteDateTime [0..1]+ serviceStart: AbsoluteDateTime [0..1]+ soldTo: String [0..1]+ taxAmount: Money [0..1]+ timeZone: String [0..1]+ tradeDate: AbsoluteDateTime [0..1]+ transactionDate: AbsoluteDateTime [0..1]+ transactionType: String [0..1]

ChargeProfile{leaf}

+ frequency: String [0..1]+ numberInterval: Integer [0..1]+ type: String [0..1]+ unitOfMeasure: String [0..1]

«Datatype»Domain2::UserAttribute

{root,leaf}

+ multiplier: UnitMultiplier [0..1]+ Name: String [0..1]+ Sequence: String [0..1]+ unit: String [0..1]+ Value: String [0..1]

ChargeProfileData{root,leaf}

+ sequence: Integer [0..1]+ timeStamp: AbsoluteDateTime [0..1]+ value: Float [0..1]

RegisteredResource

+ rtoID: String [0..1]

+ComponentMarketStatementLineItem 0..*

+ContainerMarketStatementLineItem0..1

+Settlements 0..*

+ErpInvoiceLineItems 0..*

+Settlements 0..*

+ErpLedgerEntries 0..* +ErpLedgerEntries

0..*

+AttributeLists

0..*

+ErpLedgerEntries

0..*

+AttributeList

0..*

+ChargeProfiles

0..*

+PassTroughBill

0..1

+MarketStatementLineItem 0..*

+MarketStatement 1

+BillDeterminants 0..*

+AttributeList 0..*

+PassThroughBills

0..*

+AttributeLists 0..*

+PassThroughBill 0..1

+MarketStatementLineItem 0..1

+ChargeProfile 0..1

+ChargeProfileData 0..*

+ChargeProfile

0..1

+BillDeterminant

0..1

+ErpStatementLineItems

0..*

+AttributeList

0..*

+Meters 0..*

+RegisteredResource 0..1

+Market 0..1

+Settlements 0..*

+Documents

0..*

DocOrgRole

+Organisations

0..*

+toDocuments0..* DocDocRole

+fromDocuments0..*

+Organisation

0..1+RegisteredResources

0..*

+Child_Organisation0..* OrgOrgRole

+Parent_Organisation0..*

+BillDeterminant 0..1

+ChargeProfileData 0..*

+Measurements

0..*

+Pnode

0..1

+Pnode

1+RegisteredResources 0..*

+Pnode0..*

+AggregatePnodes0..*

+ErpInvoiceLineItems

0..*

+AttributeLists

0..*

+ComponentErpInvoiceLineItem0..*

+ContainerErpInvoiceLineItem0..1

+Markets 0..*

+RegisteredResources 0..*

+Measurements 0..*

+Documents 0..*

Looking at an Example Usage - Support for Real-Time Pricing in CIM

• Real-time pricing signals and/or schedules can be sent to a meter via the AMI System. – There are several ways this can be

accomplished, such as:• Price signal issued in real-time identifying a price

for a given time interval• Time of use (TOU) schedules published, which

cause changes in the accumulation for each TOU Tier

• Energy price schedules published in advance.

Example of Real-Time Pricing using CIM-Based Services (IEC 61968-9)

1. In this example, a price signal is being sent from Network Operations to the Meter System (MS).

2. The MS then acts as a network service provider to communicate the price in real time to meters and other equipment.

Message Shown on Next Slides

Some Key Classes for “End Device Control”

class part9: EndDeviceControls message type

Ident ifiedObject

M etering::EndDeviceControl

Ident ifiedObject

M etering::DemandResponseProgram

AssetContainer

M etering::EndDeviceAsset

Ident ifiedObject

M etering::EndDeviceGroup

«Compound»Common::

DateT imeInterval

+EndDev iceGroup

0..1

+EndDev iceControls0..*

+EndDev iceGroups0..*

+EndDev iceAssets

0..*

+DemandResponseProgram

1

«informative»

+EndDev iceGroups0..*

+DemandResponseProgram

1

+EndDev iceControls0..*

+EndDev iceControls0..* +EndDev iceAsset

0..1

Message Payload of “End Device Control” of IEC 61968-9

XSD Tag Names AreFrom Relevant DataElements in the CIM

“End Device Control” Sample XML<?xml version="1.0" encoding="UTF-8"?>

<!--Sample XML file generated by XMLSpy v2009 sp1 (http://www.altova.com)-->

<m:EndDeviceControls xsi:schemaLocation="http://iec.ch/TC57/2009/EndDeviceControls# EndDeviceControls.xsd" xmlns:m="http://iec.ch/TC57/2009/EndDeviceControls#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<m:EndDeviceControl>

<m:mRID>53185955_D0AB</m:mRID>

<m:drProgramLevel>3</m:drProgramLevel>

<m:drProgramMandatory>true</m:drProgramMandatory>

<m:priceSignal>0.2</m:priceSignal>

<m:type>PRICE</m:type>

<m:DemandResponseProgram>

<m:type>RTP</m:type>

</m:DemandResponseProgram>

<m:scheduledInterval>

<m:end>2001-12-17T10:30:47Z</m:end>

<m:start>2001-12-17T09:30:47Z</m:start>

</m:scheduledInterval>

</m:EndDeviceControl>

</m:EndDeviceControls>

SE 1.0Price Cluster Server Example

SE 1.0 Publish Price:•Provider ID•Rate Label•Issuer Event ID•Current Time•Unit of Measure•Currency•Price Trailing Digit and Price Tier•Number of Price Tiers & Register Tier•Start Time•Duration In Minutes•Price •Price Ratio•Generation Price•Generation Price Ratio•Alternate Cost Delivered•Alternate Cost Unit•Alternate Cost Trailing Digit

The Price Cluster provides the mechanism forcommunicating Gas, Energy, or Water pricing information within the premise. This pricing informationIs distributed to the ESP from either the utilities or from regional energy providers. The ESP conveys the information (via the Price Cluster mechanisms) to bothSmart Energy devices in secure method and/or optionally conveys it anonymously in an unsecure tovery simple devices that may not be part of the Smart Energy network.

Cluster/Payload Element Name

Price Cluster

Server AttributesTierNPriceLabel where N=1 through 6

Server Commands Received Get Current Price

Get Scheduled Prices

Server Commands Generated Publish Price

SE “Publish Price”

XSDFrom

SE UML Model

SE “Price Publication” Sample XML<?xml version="1.0" encoding="UTF-8" ?>

<!-- Sample XML file generated by XMLSpy v2009 sp1 (http://www.altova.com)  --> - <PublishPrice xsi:noNamespaceSchemaLocation="PricePublication1.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">  <ProviderID>SCE</ProviderID>   <RateLabel>DR</RateLabel>   <IssuerEventID>53185955_D0AB</IssuerEventID>   <CurrentTime>2001-12-17T09:30:47Z</CurrentTime>   <UnitOfMeasure>kWh</UnitOfMeasure>   <Currency>USD</Currency>   <PriceTier>1</PriceTier>   <NumberOfPriceTiers>2</NumberOfPriceTiers>   <RegisterTier>1</RegisterTier>   <StartTime>2001-12-17T10:00:00Z</StartTime>   <DurationInMinutes>60</DurationInMinutes>   <Price>0.2</Price>   <PriceRatio>0.5</PriceRatio>   <GenerationPrice>0.2</GenerationPrice>   <GenerationPriceRatio>0.5</GenerationPriceRatio>   <AlternateCostDelivered>0</AlternateCostDelivered>   <AlternateCostUnit>kW</AlternateCostUnit>   </PublishPrice>

While the Approach Varies a Bit, SE Data Elements Map Well

to CIM Data Elements

SE 1.0 Publish Price:· Provider ID· Rate Label· Issuer Event ID· Current Time· Unit of Measure· Currency· Price Trailing Digit and Price Tier· Number of Price Tiers & Register Tier· Start Time· Duration In Minutes· Price · Price Ratio· Generation Price· Generation Price Ratio· Alternate Cost Delivered· Alternate Cost Unit· Alternate Cost Trailing Digit

Mapping to CIM Elements· ServiceSupplier.mRID· TariffProfile.name· TimeTariffInterval.mRID· ReadingValue.timeStamp· AccountingUnit.energyUnit· AccountingUnit.monetaryUnit· AccountingUnit.multiplier· (derived)· TimeTariffInterval.startDateTime· (Derived)· Charge.fixedPortion (Charge.kind="ConsumptionCharge")· Charge.variablePortion (Charge.kind="ConsumptionCharge")· Charge.fixedPortion (Charge.kind="demandCharge")· Charge.variablePortion (Charge.kind="demandCharge")· Charge.fixedPortion (Charge.kind="auxiliaryCharge")· AccountingUnit.energyUnit· AccountingUnit.multiplier

[Refer to the “Price” tab of the SE- CIM Mapping Spreadsheet]

ADR Data Model:Utility

Configuration Entities

typeID – this identifies the type of information and may take on one of thefollowing values:o PRICE_ABSOLUTE – Price number, i.e. $0.25o PRICE_RELATIVE – Change in price, i.e. -$0.05o PRICE_MULTIPLE – Multiple of current price, i.e. 1.5o LOAD_LEVEL – Amount of load based on an enumeration, i.e. moderate,high, etc.o LOAD_AMOUNT – Fixed amount of load to shed or shift, i.e. 5 MWo LOAD_PERCENTAGE – Percentage of load to shed or shift, i.e. 10%o GRID_RELIABILITY – Number from 0–100 signifying the reliability of thegrid. 100 signifies the highest level of reliability while 0 is the lowest.

DR programs and dynamic pricing are typically designed to use a variety of information to cause reactions by participants to DR events that are issued by the utility or ISO. In some cases prices are used to trigger responses to the DR events while in other case itmight be a shed or shift level.

scheduleType – This specifies how a schedule may be associated with the DR event information is defined and may take on the following values:o NONE – There is no schedule and thus EventInfo does not change valuesduring the entire DR event ACTIVE state.o DYNAMIC–The time schedule is not fixed during configuration, but can be set when the DR event is issued.o STATIC–The schedule is fixed when the DR program is configured within the DRAS Schedule – If the scheduleType is STATIC, this is the configured schedule. A schedule is a sequence of time slots that are valid over the entire ACTIVE period of a DR event.

ADR: Utility Issued

DR Event Entity

ADR:Participant

Configuration Entities

CIM (IEC 61968-11):Tariff Profile

(note that capabilities are much richer than this diagram implies because inherited attributes are

not shown)

Document

Customers::PricingStructure

Document

Customers::Tariff

Document

TariffProfile

+ tariffCycle: String [0..1]

TimeTariffInterval

+ sequenceNumber: Integer [0..1]+ startDateTime: AbsoluteDateTime [0..1]

ConsumptionTariffInterval

+ sequenceNumber: Integer [0..1]+ startValue: RealEnergy [0..1]

IdentifiedObject

Charge

+ kind: ChargeKind [0..1]+ fixedPortion: AccountingUnit [0..1]+ variablePortion: PerCent [0..1]

+PricingStructures 0..*

+Tariffs 0..*

+Tariffs 0..*

+TariffProfiles 0..*

+TariffProfiles

0..*

+TimeTariffIntervals

0..*

+TariffProfiles

0..*

+ConsumptionTariffIntervals

0..*

+TimeTariffIntervals0..*

+Charges

0..*

+ConsumptionTariffIntervals0..*

+Charges

0..*

+ParentCharge0..1

+ChildCharges0..*

One of a sequence of intervals defined in terms of consumption

quantity of a service such as electricity, water, gas, etc.

It is typically used in association with TariffProfile to define the steps or blocks in a step tariff structure, where startValue

simultaneously defines the entry value of this step and the closing

value of the previous step.

A schedule of charges; structure associated with Tariff that allows

the definition of complex tarif structures such as step and time of use when used in conjunction

with TimeTariffInterval and Charge.

One of a sequence of time intervals defined in terms of

real time. It is typically used in

association with TariffProfile to define the intervals in a time of use tariff structure,

where startDateTime simultaneously determines

the starting point of this interval and the ending point

of the previous interval.

CIM Classes Applicable for “Pricing Configuration”

class part9: PricingStructureConfi g message type

Document

Customers::PricingStructure

Document

Customers::Tariff

Document

PaymentM etering::Tariff Profi le

PaymentM etering::ConsumptionTariff Interval

PaymentM etering::T imeTariff Interval

Ident ifiedObject

PaymentM etering::Charge

Ident ifiedObject

Customers::ServiceCategory

«Compound»Common::Status

«Compound»PaymentM etering::

AccountingUnit

+Serv iceCategory

1

+PricingStructures

0..*

+ParentCharge 0..1

+ChildCharges 0..*

+T imeTariff Intervals

0..*

+Charges

0..*

+ConsumptionTariff Intervals

0..*

+Charges0..*

+Tariff Profiles

0..*

+T imeTariff Intervals

0..*

+Tariff Profiles

0..*

+ConsumptionTariff Intervals

0..*

+Tariff s

0..*

+Tariff Profiles

0..*+PricingStructures

0..*

+Tariff s

0..*

Pricing Structure

for “Richer

Capabilities”

Tariff Profile

Time Intervals

ConsumptionIntervals