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] Commented: (ENERGYINTEROP-614) EIReports section is still very unclear


    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28466#action_28466 ] 

Ed Koch  commented on ENERGYINTEROP-614:
----------------------------------------

It would help if someone could describe the operations used and show some xml artifacts for the following simple scenario:

VEN is condigued by convention (i.e. no historian or report specifications need be exchanged) to allow the VEN to report the following to the VTN.

VEN is configured to PUSH reports to the VTN perioedically with the following characteristics:

data source = meter1
data set = usage information

data source - meter2
data set = usage information

usage information for both meters is collected at 15 minute intervals and reported every 15 minutes, BUT on occasion
communications goes down for an hour and the next time the VEN pushes a report it must send all the usage infomation that has not been previously transmitted, i.e. instead of normally sending a single meter reading it occasionally sends 4.


> EIReports section is still very unclear
> ---------------------------------------
>
>                 Key: ENERGYINTEROP-614
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-614
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>            Reporter: Ed Koch 
>            Assignee: William Cox
>
> I honestly still do not understand how to use the EIReports to do some of the very simple feedback use cases that I want to support. The sections seems to be a muddled collection of services and it is not clear what services are really required and how you would use them. There seem to be a bunch of bureaucratic services for creating "historians" and "report specifications", but how they are tied together and used is very unclear. If I can't understand this then I honestly don't know how someone coming into this cold has a hope of understanding it.
> For example on line 1707 it says "EiReport is prepared by a Party upon request and supplied to the requesting party. It may also be defined in the expectations of the Market Context."  Does this mean that the only way a report can be generated is by request? The simple use cases deployed today do not require any registrations or report specification services or any of this overhead. The report specifications and what not are created by convention and while some systems may want to employ all these extra meta data services they should not be required.

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