[OASIS Issue Tracker] Created: (ENERGYINTEROP-228) Line 618: Needto be clear that events can be raised for any valid reason agreed to by theparties to a transaction.

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

Line 618: Need to be clear that events can be raised for any valid reason agreed to by the parties to a transaction.
--------------------------------------------------------------------------------------------------------------------

                 Key: ENERGYINTEROP-228
                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-228
             Project: OASIS Energy Interoperation TC
          Issue Type: Improvement
          Components: spec
    Affects Versions: wd16
            Reporter: Edward Cazalet 
            Assignee: William Cox


For transactive services, two parties may enter into a call option, for example. Invocation of the call option by the promissee party on the promissor party can be thought of as raising an event. But typically the promissee may raise the event at his discretion as long as the call is within the terms of the call option.

An ISO that has awarded an ancillary services contract to a party may issue dispatch orders which can also be viewed as events.

We need to make clear in the text that these types of events are covered.  

The EventInfoTypeID refers to loads but not generators as used in Ancillary Services dispatch.  And the event points to a program but not to an option or ancillary services transaction. Changes to extend the EventInfoType and to point to a transaction instead of or in addtition to a Program should be straightforward.


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