[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] Re: "Opt Out" (really cancel during an event in progress)
Not sure what the exact issue is or if what I am about to say is going to add anything to what has already been said in the numerous email threads, but here is my input. There are the following requirements: (1) The VEN be able to opt out of a particular event and they notify the VTN of the fact that they want to opt out of that event. As Rish has stated this is important for the VTN to know and yes since they are opting out of a specific event then the VEN won’t notify the VTN that it is opting out until after the event is initiated. Note that I used the word “initiated” and not “started”. Initiated means that an event is queued up and the VEN has been notified of that fact. Typically this is if the highest value with DR programs which have long notification periods so the VTN will know well in advance of the event actually starting that the VEN is opting out. (2) The VEN be able to opt out of an event via the CreatedEvent response that it sends back to the VTN when it receives the EIEvent from the VTN. This specifically allows the device to opt out of an event without having to implement the more complex Opt service. This wasn’t in the original OpenADR 1.0 spec, but enough vendors asked for it that we added it. In OpenADR 1.0 a VEN could opt out of a specific event either through the Opt service or through the CreatedEvent response operation. If we support the opting out of a specific event through the CreatedEvent response then we probably don’t need to also support it in the Opt service. This is where I thought we were going last week so I didn’t respond. Thanks, -ed Koch From: Girish Ghatikar [mailto:gghatikar@lbl.gov] Hi Bill, Within the context of VEN opting out and the function of notification to VTN is one aspect of it. While the ability to opt-out of an active event by VEN in itself a significant need (with any subsequent penalties), the notification serves the purpose of providing immediate alert to VTN to find alternate resources to meet the reduced response from a VTN or a set of VTNs. In OpenADR, there are following is the language for additional opt-out conditions to the participant (VEN): A participant may choose to opt‐out or override participating in DR events. The participant does this by using the OptOutState entity to set up one or more conditions within the DRAS that define when the participant will not participate in a DR event. The OptOutState may have the following attributes: · Which DR programs the conditions apply to. If not specified, it defaults to all programs. · Which DRAS Clients the conditions apply to. If not specified, it defaults to all DRAS Clients. · Which DR event the conditions apply to. If not specified, it defaults to all DR events. · A schedule which defines when the conditions apply. The facility manager opts out of the DR program. At any time, the facility manager can opt‐out of the DR program on the DRAS. When in an opt‐out condition, DR events are not propagated to the DRAS Client. The opt‐out can be either for the entire program or a single event or a specific event‐mode (e.g. normal, moderate, high) Thanks, -Rish On Sat, Jul 2, 2011 at 9:14 PM, William Cox <wtcox@coxsoftwarearchitects.com> wrote: Please take a look at http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-423 . I've just added extensive comments. I think this is post PR02, and maybe post 1.0. --
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]