Re: [energyinterop] Value of Constraints in DR and Automation.

The behavior adjustments allow flexibility for both the service provider and consumers/participants to participate in an event beyond or within the boundaries of the constraints. Example, if I can participate tomorrow beyond my original constraint set-up, I can just ignore those constraints and accept. This is good for the service provider as they may get more responses from consumes. As we discussed earlier, this has similar exchange patterns from demand-bidding (standing bids and revisions of bids during bid-open period).

Thanks,

-Rish

On Thu, Apr 21, 2011 at 12:50 PM, Toby Considine <Toby.Considine@gmail.com> wrote:

Thanks, Rish

OpenADR Constraints also exchange ConstraintBehavior with each constraint. As translated into the current draft of EnergyInterop, this looks like:

                <xs:element name="eiConstraintBehavior" type="eitc:EiConstraintBehaviorType"/>

                <xs:simpleType name="EiConstraintBehaviorType">
                                <xs:annotation>

                                                <xs:documentation>Modify the DR event parameters so hat they legally fall within the bounds of the onfigured parameters.</xs:documentation>

                                </xs:annotation>
                                <xs:restriction base="xs:string">

                                                <xs:enumeration value="Accept">
                                                                <xs:annotation>

                                                                                <xs:documentation>Simply accept the issued DR event regardless of any conflicts</xs:documentation>

                                                                </xs:annotation>
                                                </xs:enumeration>

                                                <xs:enumeration value="Reject">
                                                                <xs:annotation>

                                                                                <xs:documentation>Reject any DR events that conflict with configured constraints</xs:documentation>

                                                                </xs:annotation>
                                                </xs:enumeration>

                                                <xs:enumeration value="Force">
                                                                <xs:annotation>

                                                                                <xs:documentation>Regardless of what the issued DR events parameters are (even if there is no conflict) force them to be the parameters that were configured as part of the program.</xs:documentation>

                                                                </xs:annotation>
                                                </xs:enumeration>

                                                <xs:enumeration value="Restrict"/>
                                </xs:restriction>

                </xs:simpleType>
.
My question is a business process description of the ConstraintBehavior

"He who fights with monsters should look to it that he himself does not become a monster, and if you stare long into an abyss, the abyss also stares into you."   - Fredrich Nietzche

Toby Considine
TC9, Inc
TC Chair: oBIX & WS-Calendar
TC Editor: EMIX, EnergyInterop
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee


Email: Toby.Considine@gmail.com
Phone: (919)619-2104
http://www.tcnine.com/
blog: www.NewDaedalus.com

From: Girish Ghatikar [mailto:gghatikar@lbl.gov]
Sent: Thursday, April 21, 2011 3:44 PM
To: OASIS-EnergyInteropTC
Subject: [energyinterop] Value of Constraints in DR and Automation.

EI TC,
As per our discussion during April 20 TC meeting, the following is the business context for value of "constraint" services. These were part of OpenADR v1.0. Let me know if you've questions.

Toby -- Please use them as appropriate.

Value of Constraints:

The value of constraints applies to the buildings that participate in the DR programs, to the DR Service Providers (e.g., Utilities or ISOs), etc. with many benefits, including promoting consumer choice.

Within buildings, the service offers the consumers (commercial, industrial, or residential buildings), participants (e.g., facility managers) the confidence to participate in DR programs knowing that they are not subjected to shed when we cannot participate on certain terms (e.g., black-out dates). This service helps consumers more comfortable about participating in the DR programs, especially using automated DR programs where there is no human in the loop. This is an important requirement if we would like the EI standards to be used across a wider consumer-base and automation of DR programs.

This service is also useful for the DR service providers. The information on non-participation allows, them to forecast the availability of loads for sheds for a certain day, time, etc. and schedule their DR events across a consumer-base accordingly. If a constraint says that consumers within certain DR program cannot participate by setting constraints, this information can be used to better estimate shed response and customer participation and make intelligent business decisions prior to issuing the DR event.

Thank you,
-Rish

--
Rish Ghatikar
Lawrence Berkeley National Laboratory
1 Cyclotron Road, MS: 90-3111, Berkeley, CA 94720
GGhatikar@lbl.gov | +1 510.486.6768 | +1 510.486.4089 [fax]

This email is intended for the addressee only and may contain confidential information and should not be copied without permission. If you are not the intended recipient, please contact the sender as soon as possible and delete the email from computer[s].

--
Rish Ghatikar
Lawrence Berkeley National Laboratory
1 Cyclotron Road, MS: 90-3111, Berkeley, CA 94720
GGhatikar@lbl.gov | +1 510.486.6768 | +1 510.486.4089 [fax]

This email is intended for the addressee only and may contain confidential information and should not be copied without permission. If you are not the intended recipient, please contact the sender as soon as possible and delete the email from computer[s].

energyinterop message