OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Created: (ENERGYINTEROP-617) Change EiDelivery to use EMIXBase and change Service names to Request and Reply.


Change EiDelivery to use EMIXBase and change Service names to Request and Reply.
--------------------------------------------------------------------------------

                 Key: ENERGYINTEROP-617
                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-617
             Project: OASIS Energy Interoperation TC
          Issue Type: Improvement
          Components: spec
            Reporter: Edward Cazalet 
            Assignee: William Cox
             Fix For: wd33


EiDelivery

EiDelivery is basically a request to a meter at an EMIXInterface, or to a data service hosting the meter data.  The request is for the energy delivered for in each measurement interval during a request interval.  The requestorParty is any authorized Party.  The MarketContext will specify the measurement interval duration, units, injection Boolean, etc.  Effectively, the payload for each measurement interval will be MarketContextUID, StartTime, and Quantity

It would seem that the only two services required are EIRequestDelivery and EiReplyDelivery.  The current spec uses EiCreateDelivery and EiCreatedDeliver which is confusing.

If we think of CreateDelivery as creating the delivery record in memory it the meter or in a database, then CreateDelivery is out of scope, I assume.

Having reviewed the application of the simplified report structure and its use of streams, I can see no benefit and perhaps complexity and cost to that structure over EMIXBase for this application.  Also since EiReport is new, I suggest we use EMIXBase for EiDelivery.  EiReport can still be used by practitioners if it meets their needs for delivery information.

Note the UML Diagrams for EiDelivery are out of date.


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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]