Presentation on theme: "Inputs to NIST PAP03 Activity Pricing Information from CIM, SEP 1.0 and OpenADR & Recommendations Contact for further"— Presentation transcript:
Inputs to NIST PAP03 Activity Pricing Information from CIM, SEP 1.0 and OpenADR & Recommendations Contact for further 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 IBMs 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 applications view of the world
CIM Packages Generation Domain Wires LoadModel Core Meas Topology Outage Protection Financial Energy Scheduling Reservation SCADA Core2 Assets Documents Consumer GML Support ERP Support WG13 WG14 Metering Work Mgmt Bid RTO Resource Security Constraints FTR Clearing Results WG16
Class Name usually describes things in the real worldClass Attributes describe significant 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 are assigned a role that describes the relationship
Examples of Bids for Wholesale Market (from CIM – IEC TC57 WG16 – draft and for reference only)
Examples of Settlement for Wholesale Market (from CIM – IEC TC57 WG16 – draft and for reference only)
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 ) 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
Message Payload of End Device Control of IEC XSD Tag Names Are From Relevant Data Elements in the CIM
End Device Control Sample XML _D0AB 3 true 0.2 PRICE RTP T10:30:47Z T09:30:47Z
SE 1.0 Price 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 for communicating Gas, Energy, or Water pricing information within the premise. This pricing information Is distributed to the ESP from either the utilities or from regional energy providers. The ESP conveys the information (via the Price Cluster mechanisms) to both Smart Energy devices in secure method and/or optionally conveys it anonymously in an unsecure to very simple devices that may not be part of the Smart Energy network.
SE Publish Price XSD From SE UML Model
SE Price Publication Sample XML - SCE DR _D0AB T09:30:47Z kWh USD T10:00:00Z kW
While the Approach Varies a Bit, SE Data Elements Map Well to CIM Data Elements [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 the following values: o PRICE_ABSOLUTE – Price number, i.e. $0.25 o PRICE_RELATIVE – Change in price, i.e. -$0.05 o PRICE_MULTIPLE – Multiple of current price, i.e. 1.5 o 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 MW o LOAD_PERCENTAGE – Percentage of load to shed or shift, i.e. 10% o GRID_RELIABILITY – Number from 0–100 signifying the reliability of the grid. 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 it might 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 values during 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 ): Tariff Profile (note that capabilities are much richer than this diagram implies because inherited attributes are not shown) 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