[OASIS Issue Tracker] Commented: (ENERGYINTEROP-622) EIQuote payloads and interaction patterns need to be made consistent with EIEvent.

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

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

Toby Considine commented on ENERGYINTEROP-622:
----------------------------------------------

If we take Ed's example:

One can certainly define a Historian whose purpose is to measure Real Power at an Emix Interface at a granularity of 15 minute intervals.
One can define a reportBack Duration for that historian of every 15 minutes.
If the [VTN] is unreachable, the application could keep or toss the reading. It is a conformance spec to declare the application should save un-delivered reading for eventual delivery instead of discarding. I think specifying that behavior is out of scope. I am open to adding a flag.

So: That says we can define the report. When we define a report and create a schedule, we have a request and therefore a reportRequestID. That could be standardized. Let's say its name is OpenADR20-favorite.

We can specify that a VEN must deliver OpenADR20-favorite and put it in the market context. It can be Requested, so folks can find out what it is. It can be a pre-loaded into every Alliance-certified system so it is always known.

That is a reasonable white-paper topic. Is there anything else we need?

> EIQuote payloads and interaction patterns need to be made consistent with EIEvent.
> ----------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-622
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-622
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>    Affects Versions: wd33
>            Reporter: Ed Koch 
>            Assignee: Ed Koch 
>            Priority: Blocker
>             Fix For: wd34
>
>
> EIQuote payloads and interaction patterns need to be made consistent with EIEvent. Once the EIEvent have stabalized then we willneed to apply the same changes to EIQuote.

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