[OASIS Issue Tracker] Commented: (ENERGYINTEROP-490) Do not supporteiChangeEvent - Use cancel and create to do changes to existing event.

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

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

Ed Koch  commented on ENERGYINTEROP-490:
----------------------------------------

We have actuallly debated this a few times over the years. There are uses cases where a change event is preferred over the two transactions required to first cancel and then re-issue an event. There are dispatch type programs where a dispatch level is given and is designed to stay in effect until told otherwise. It is much more efficient to simply change the existing event to the new dispatch level than to canel it and re-issue a new one. Beyond the communications efficieny issue there is also potentially an issue with the automation equipment itself. Cancelling an event may put the control equipment into it's normal operating mode when in fact all you wanted to do is change the dispatch level. This could cause severe problems wiht the automation equipment if it were to be continuously brought in and out of events just because you wanted to channge the dispatch level. 

I strongly recommend we keep the change event message.

> Do not support eiChangeEvent - Use cancel and create to do changes to existing event.
> -------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-490
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-490
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: wd25
>         Environment:  Psoter, Eugene of PG&E
>            Reporter: Bruce Bartell
>            Assignee: Ed Koch 
>             Fix For: wd28
>
>
> Technical: Regarding the EventServices, if an EiChangeEvent operation is performed, the consumers may have a significant amount of work to do to understand what is changed and then to update all the downstream parties regarding a change. My suggestion would be to not support this operation and if a change to an event was required, that the event be cancelled and a new event created which would trigger a new set of transactions regarding that event.
>  

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