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-260) Section 5:Energy Interoperation Services: Suggest edits to first three paragraphs toprovide balance to Demand Response and Transactive Services overview.



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

Girish Ghatikar  commented on ENERGYINTEROP-260:
------------------------------------------------

We will have to flush out details on how an asset can interact directly with the VTN. The asset can have an virtual ESI to communicate -- need some architecture references.

> Section 5: Energy Interoperation Services:  Suggest edits to first three paragraphs to provide balance to Demand Response and Transactive Services overview.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-260
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-260
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>    Affects Versions: wd17
>            Reporter: Edward Cazalet 
>            Assignee: William Cox
>             Fix For: wd18
>
>
> Suggest replacing 
> In the following sections, we define Energy Interoperation services and operations. All communication between the VTN and the VEN is through the ESI. 
> From the perspective of the VTN, each ESI is the interface to a dispatchable resource (Resource), that is to a single logical entity. A Resource may or may not expose any subordinate Assets.
> An Asset is an end device that is capable of shedding load in response to Demand Response Events, Electricity Price Signals or other system events (e.g. under frequency detection). Assets are under the control of a Resource, and the resource has chosen to expose it to the VTN. The VTN can query the State of an Asset, and can call on an asset for a response. The Resource (VEN) mediates all Asset interactions, as per its agreement with the VTN. Assets, by definition, are only capable of consuming Direct Load Control and Pricing messages, and then only as mediated by the Resource.
> If an Asset, in turn, has its own Assets, it does not reveal them through the VEN. The Asset has not direct interactions with the VTN.
> with
> In the following sections, we define Energy Interoperation services and operations. All communication between the VTN and the VEN is through the ESI. 
> From the perspective of the VTN, each ESI is the interface to a dispatchable resource (Resource), that is to a single logical entity. A Resource may or may not expose any subordinate Assets.
> An Asset is an end device that is capable of shedding load in response to Demand Response Events, Electricity Price Signals or other system events (e.g. under frequency detection). Assets are under the control of a Resource, and the resource has chosen to expose it to the VTN. The VTN can query the State of an Asset, and can call on an asset for a response. The Resource (VEN) mediates all Asset interactions, as per its agreement with the VTN. Assets, by definition, are only capable of consuming Direct Load Control and Pricing messages, and then only as mediated by the Resource.
> If an Asset, in turn, has its own Assets, it does not reveal them through the VEN. The Asset has not direct interactions with the VTN.

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