[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=25742#action_25742 ] 

William Cox commented on ENERGYINTEROP-425:
-------------------------------------------

Clearly feedback needs to include "present measured demand" as a minimum.

We've also discussion (and I think it's useful) to bundle responses in some way so that you don't have a message from each VEN for each measurement.  (The measurement interval is in the EiFeedback service, as well as a way of making the feedback stop - adding an optional element for the bundling quantity is clear).

Once we have bundling, each feedback item needs a timestamp, and there would be the information structures in place to do Rish's 1b (which bundling does to some extent anyway).

Per discussions in the ASHRAE SPC201P group, it would seem that the demand measures are actually averaged over some interval anyway, so I'm not sure what 1c would do - love a discussion on the topic.

2. Predicted demand. The way SPC201P does this is a confidence level; others have suggest a confidence interval. We've tried this with the EiUsage service, but for curtailment demand makes much more sense.

3. This is addressed in the SPC201 sheddable load descriptions, and if we go this way (I'd suggest post 1.0) we should be careful to coordinate. SPC201 is using EMIX Resources BTW.  

As I've suggested elsewhere, the resource gives the envelope of performance; the Feedback needs to give the "position of the needle" on the gauge.  1 does that function.

4. This is simply resource ID; the Interface defines other things. This is all associated with the Resource IMO.

Assets are out of scope for 1.0, so 4c is post 1.0 at the earliest.

There's no 5.

Not sure about 6 - is this the interval for feedback?



> 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