[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ENERGYINTEROP-425) Continuingthoughts for a feedback service.
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Cox updated ENERGYINTEROP-425:
--------------------------------------
Environment: Girish Ghatikar (was: 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. )
Description:
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.
Resolution:
Post 1.0. This is a significant proposed extension to functionality.
1. wd24 EiFeedback services provides means for periodically or one-time measure of demand and energy use. This is historical for the period designated in the EiCreateFeedback service operation.
2. Feedback is response, not prediction. Others (e.g. ASHRAE SPC201P) are workiing on projected use and demand.
3. Projected demand, curtailment, generation availability is post-1.0; collaboration with the ASHRAE technical committee and soliciting comments from their members seems a good way forward.
4. EiDelivery addresses this in part.
> 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: Girish Ghatikar
> Reporter: Girish Ghatikar
> Assignee: William Cox
>
> 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.
--
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]