[EMIX-130] Model should use (CIM) ServiceDeliveryPoint notion where it is trying to use ServiceLocation - OASIS Technical Committees Issue Tracker

Details

Type: Improvement
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: csprd01 Public Review Draft
Fix Version/s: wd17
Component/s: model
Labels:
None
Environment:

IRC Language in the specification and the model

Proposal:

Hide

Include the use of ServiceDeliveryPoint (see IRC model) to work in conjunction with ServiceLocation and metering associations (e.g. readings) and update the specification language accordingly.

Show
Include the use of ServiceDeliveryPoint (see IRC model) to work in conjunction with ServiceLocation and metering associations (e.g. readings) and update the specification language accordingly.
Resolution:

Hide

Added ServiceDeliveryPoint to choices for interfacePricingPoint in power.xsd. InterfacePricingPoint is the base type used for price and event communications. THis type is now defined as follows:

<xs:complexType name="type-interfacePricingPoint">
<xs:annotation>
<xs:documentation>Either pNode or Service Delivery Point or geographic location or region</xs:documentation>
</xs:annotation>
<xs:choice>
<xs:element name="pnode" type="power:type-transactionNode">
<xs:annotation>
<xs:documentation>A pricing node is directly associated with a connectivity node. It is a pricing location for which market participants submit their bids, offers, buy/sell CRRs, and settle.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="apnode" type="power:type-transactionNode"/>
<xs:element name="serviceLocation" type="power:type-transactionNode">
<xs:annotation>
<xs:documentation>Service location. For residential or most businesses, it is typically the location of the meter on the utility customer's premises. For transmission, it is the point(s) of interconnection on the transmission provider's transmission system where capacity and/or energy transmitted by the transmission provider is made available to the receiving party.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="serviceDeliveryPoint" type="power:type-transactionNode">
<xs:annotation>
<xs:documentation>Logical point on the network where the ownership of the service changes hands. It is one of potentially many service points within a ServiceLocation, delivering service in accordance with a CustomerAgreement. Used at the place where a meter may be installed.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="serviceArea" type="emix:type-geolocation">
<xs:annotation>
<xs:documentation>For broadcast prices, DR Events, et c., information can be directed to a geographic area which can contain many customers, meters and transaction nodes.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:choice>
</xs:complexType>

Show
Added ServiceDeliveryPoint to choices for interfacePricingPoint in power.xsd. InterfacePricingPoint is the base type used for price and event communications. THis type is now defined as follows: <xs:complexType name="type-interfacePricingPoint"> <xs:annotation> <xs:documentation>Either pNode or Service Delivery Point or geographic location or region</xs:documentation> </xs:annotation> <xs:choice> <xs:element name="pnode" type="power:type-transactionNode"> <xs:annotation> <xs:documentation>A pricing node is directly associated with a connectivity node. It is a pricing location for which market participants submit their bids, offers, buy/sell CRRs, and settle. </xs:documentation> </xs:annotation> </xs:element> <xs:element name="apnode" type="power:type-transactionNode"/> <xs:element name="serviceLocation" type="power:type-transactionNode"> <xs:annotation> <xs:documentation>Service location. For residential or most businesses, it is typically the location of the meter on the utility customer's premises. For transmission, it is the point(s) of interconnection on the transmission provider's transmission system where capacity and/or energy transmitted by the transmission provider is made available to the receiving party.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="serviceDeliveryPoint" type="power:type-transactionNode"> <xs:annotation> <xs:documentation>Logical point on the network where the ownership of the service changes hands. It is one of potentially many service points within a ServiceLocation, delivering service in accordance with a CustomerAgreement. Used at the place where a meter may be installed.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="serviceArea" type="emix:type-geolocation"> <xs:annotation> <xs:documentation>For broadcast prices, DR Events, et c., information can be directed to a geographic area which can contain many customers, meters and transaction nodes.</xs:documentation> </xs:annotation> </xs:element> </xs:choice> </xs:complexType>

Description

[On behalf of Sean Crimmins] The existing EMIX model uses the notion of ServiceLocation to represent associations to Assets, Resources, etc. It would be more appropriate and alingned with the CIM (and IRC's model based on the CIM) to use ServiceDeliveryPoint as specified in the Metering package. By using only ServiceLocation to represent the places where one could have meters that are associated to assets, the model could fall short to represent all the use cases of multiple meters at a ServiceLocation (or facility). Using the CIM notion of a ServiceLocation having one or more ServiceDeliveryPoints to represent associations to meters and meter readings better satisfies the IRC requirements.

Model should use (CIM) ServiceDeliveryPoint notion where it is trying to use ServiceLocation

Details

Description

Attachments

Activity

People

Dates