[OASIS Issue Tracker] Commented: (ENERGYINTEROP-585) Multi-address event delivery

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

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

Ed Koch  commented on ENERGYINTEROP-585:
----------------------------------------

The characterization of this issue may not be correct depending upon the defintion of a VEN. What was suggested is the following use case whcih is supported today:

- EdKea is a customer of PG&E

- EdKea signs up for PG&E's CPP DR program and offers one of his stores as a DR resource into that program. From  PG&E's perspective the EdKea store is the only service delivery point and is the only thing eligible to offered up as a resource in the program and will be what PG&E dispatchs against.

- EdKea installs multiple devices (i.e. endpopints, one on each floor) in his store, each receiving their own DR signal from PG&E's servers.

Based upon recent discussions the EI entities in this relationship are not clear. I'm not convinced that EdKea is a single VEN. As soon as we map the following real world entities into into EI's definitions then hopefully the solution is more evident. Here is my cut at it:


(1) PG&E (party and VTN?)
(2) EdKea the customer (i.e party)
(3) EdKea's the store (i.e. resource)
(4) EdKea's devices for receiving DR signals (?)

In NAESB and OpenADR Taskforce terminology and use cases (4) are assets. EI did not want to adopt assets, but wanted to do some sort of resource heirarchy so in that repsect I guess they are resources from EdKea's perspective, but not from PG&E's perspective. How those map to VEN's is still a little unclear.

> Multi-address event delivery
> ----------------------------
>
>                 Key: ENERGYINTEROP-585
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-585
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>            Reporter: Toby Considine
>            Assignee: Ed Koch 
>
> It has been stated that it is desirable to sign up a single VEN at a single address and send Events (and signals) directly to multiple IP addresses/ resources.
> Please make a suggestion as to how we do this in the Registration/Enrollment process.

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