[OASIS Issue Tracker] Issue Comment Edited: (ENERGYINTEROP-211)Critical: Provide mechanism for dynamic pricing EventInfoTypeID (WD15, pg642-644)

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

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

William Cox edited comment on ENERGYINTEROP-211 at 11/21/10 8:52 PM:
---------------------------------------------------------------------

One issue in this discussion is the combining of primary DR communications as "events". We've tried to more carefully define "event" as the performance under an agreement ("program"), and separate price distribution as "quotes".

I believe that the point in the comments is that there are changes in prices that may have similar effects to a curtailment reliability event, but that applies to price changes however communicated. And price communication only does not have all the attributes of an Event.

So "price quote events" is a mixture of terminology - there are Events (that cause something to be done under the overarching Agreement) and Quotes (that communicate a value/current/future price in a tender or a contract).

Other comments have suggested combining the sending of price with the sending or calling of an event as an optimization. See 237 for an example.

Finally, EiQuote can deliver price information. That information is understood in the context of the overarching Agreement (see other comments and wd17 for the clarified terminology). The acceptance took place when the overarching Agreement (including a Program) was accepted, so there's no need for a separate offer and acceptance, only receipt of the quote.

      was (Author: william.cox):
    One issue in this discussion is the combining of primary DR communications as "events". We've tried to more carefully define "event" as the performance under an agreement ("program"), and separate price distribution as "quotes".

I believe that the point in the comments is that there are changes in prices that may have similar effects to a curtailment reliability event, but that applies to price changes however communicated. And price communication only does not have all the attributes of an Event.

So "price quote events" is a mixture of terminology - there are Events (that cause something to be done under the overarching Agreement) and Quotes (that communicate a value/current/future price in a tender or a contract).

Other comments have suggested combining the sending of price with the sending or calling of an event as an optimization. See 237 for an example.
  
> Critical: Provide mechanism for dynamic pricing EventInfoTypeID (WD15, pg 642-644)
> ----------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-211
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-211
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>    Affects Versions: wd15, wd16
>            Reporter: Girish Ghatikar 
>            Assignee: William Cox
>             Fix For: wd17
>
>
> Add PRICE_MULTIPLE, PRICE_RELATIVE, PRICE_ABSOLUTE simple pricing mechanism for DR events as part of DR event/program as section 6 includes transactive pricing. Currently, the document (WD 16, ln 692, 693) says, it "needs an offer and acceptance to reach a contract." 
> The DR CPP and PDP pricing that use above suggested pricing mechanism does not need offer or acceptance. 

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