OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-505) Suggested supplementary optional data classes with additional (optional) data types, detailed below


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

Toby Considine commented on ENERGYINTEROP-505:
----------------------------------------------

Anything that you can get feedback on, you might set a baseline for. In WD29 WIp1, the schemas for both BaseLine and Feedback include ItemBase (instead of PowerReal) as their core "thing". ItemBase already covers many of the above, and could be extedned to cover the rest.

There is another aspect of each, Instantaneous vs Rolling Average vs Peak ... that could be defined in another attibute. If we go down that road, we should make Feeback and Baselines to be similar in how we specify and report.




> Suggested supplementary optional data classes with additional (optional) data types, detailed below
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-505
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-505
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Sub-task
>          Components: spec
>    Affects Versions: wd27
>         Environment: Steffes
>            Reporter: Toby Considine
>            Assignee: William Cox
>             Fix For: wd29
>
>
> In order to provide optimum value and control and to meet the requirements of the ISO/utility, our units are required to send the following power data to the ISO/utility:
> 1) Regulation Set Point Feedback - a repeat of the control value sent from the ISO/utility,
> 2) Up Regulation Capacity Available - the up regulation capacity available to the ISO/utility,
> 3) Down Regulation Capacity Available - the down regulation capacity available to the ISO/utility,
> 4) Current Regulation Set Point - the regulation service that is currently being provided to the ISO/utility,
> 5) Baseline Power - the system load that would exist were the system not providing regulation services,
> 6) Instantaneous Power Flow, and
> 7) 15-Minute Rolling Average of Power Flow
> One embodiment of the use of these parameters is outlined in Appendix I: http://lists.oasis-open.org/archives/energyinterop-comment/201108/bin00000.bin.
> Additionally, new control strategies would allow the ability to provide several energy parameters important to energy storage applications, including:
> 8) Stored Energy - amount of energy currently stored
> 9) Target Energy Storage - desired energy storage level
> 10) Available Energy Storage - capacity available for further energy storage
> The Energy Interoperation v1.0 specification currently supports two data classes: PowerFeedbackType and EnergyFeedbackType (from Figure 8-8, line 1110 of working draft).  Steffes requests that consideration be given to supplement these two data classes with the above-listed 10 parameters as optional data classes within the standard. These data types are necessary to facilitate frequency regulation and other Smart Grid Control for ISO/Utilities.

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