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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

                 Key: EMIX-130
                 URL: http://tools.oasis-open.org/issues/browse/EMIX-130
             Project: OASIS Energy Market Information Exchange (eMIX) TC
          Issue Type: Improvement
          Components: model
    Affects Versions: csprd01 Public Review Draft
         Environment: Language in the specification and the model
            Reporter: Edgardo Luzcando 
            Assignee: William Cox


[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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira