[OASIS Issue Tracker] Commented: (ENERGYINTEROP-425) Continuingthoughts for a feedback service.

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

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

Girish Ghatikar  commented on ENERGYINTEROP-425:
------------------------------------------------

I. Let's start with an elemental feedback as a response from VEN to VTN with no intermediaries. In this case the VEN is also a resource:

1. Measured demand in real-time from a resource
a. Specified interval period (1, 5, 15-minute?)
b. Associated schedule.

2. Predicted demand - important for A/S markets. 
a. Associated schedule.

3. DR Availability (hour, 24-hour, etc.) - important for A/S markets.
b. Associated schedule. 

4. Resource identifiers
a. VEN ID [1..1]
b. Resource ID [1..1]
c. [Assett ID?]

II. If we want to extend this to a campus scenario, #4 would additionally have
4. Resource ID
a. VEN ID [1..*]
b. VTN ID [1..*] -- assumes that the signals come from multiple resources/meters  (VEN) and  then gets distributed to centralized location (VTN), which will send it to the service provider (originating VTN)

III. If we want to extend this to an intermediary/ies (aggregator w/ I or II above), #4 would additionally have:
4. Resource ID
a. VEN ID [1..*]
b. VTN ID [1..*]

In either of the scenarios, we need to differentiate the trail of VTN IDs to the final destination VTN, which issued the signals in the first place. 

> Continuing thoughts for a feedback service.
> -------------------------------------------
>
>                 Key: ENERGYINTEROP-425
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-425
>             Project: OASIS Energy Interoperation TC
>          Issue Type: New Feature
>          Components: service
>    Affects Versions: wd24
>         Environment: Feedback Service:
> The feedback service is intended to meet the Smart Grid's need from resources (think VEN) to address the DR program requirements across different markets (think VTN). The following are some of the services to get started. These can potentially vary depending on the DR signal traversal from VEN to the final designated VTN. It is not intended to be be exclusive requirement under one service of EI and can be supported by different standards/PAP activities such as PAP 10/OpenADE, PAP 17/ASHRAE, etc.:
> 1. Measured demand. 
> a. Current (for load shed verification/settlement)
> b. Historical (for baseline, forecast, etc.)
> c. Optionally, can include peak values (although it can be extrapolated from above).
> 2. Predicted demand (this parameter can be a calculated data point or estimated by a VEN to VTN)
> 3. DR Availability (also includes any DER availability for DR)
> a. How much is available in next hour?
> b. How much is available in next 24-hours?
> c. Optionally, how much is available next week?
> 4. Resource location identifier 
> a. Meter (s), 
> b. Locational information (e.g., address, grid location indicator, sub-station, etc.)
> c. Optionally, assets. 
> 6. Schedule information to above as appropriate. 
>            Reporter: Girish Ghatikar 
>            Assignee: William Cox
>


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