OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Market Communications Factoring - eiAvailabilityType


Do we still need this? It came from OpenADR, but I am not clear that

1)      It fits in the current model

2)      If it does fit, I am not clear it is in the correct service

3)      See questions below

 

            <!-- 3.6 Availability  Behavior -->

            <xs:element name="eiAvailBehavior" type="eitc:EiAvailBehaviorType">

                        <xs:annotation>

                                    <xs:documentation>When an Event is issued by the VTN, it is validated against the parameters and constraints that were established when the program was set up, i.e., the program was configured to support Events between 12:00 and 16:00.  If the Event is not within 12:00 and 16:00 then VEN must take some action to resolve the conflict. </xs:documentation>

                        </xs:annotation>

            </xs:element>

            <xs:simpleType name="EiAvailBehaviorType">

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

 

 

1)      Is this a willingness to be tweaked indicated by the VEN during Avail and Opt services?

2)      Is this a market requirement that applied everywhere within a particular market context?

 

I don’t think it should be event by event.

 


“The single biggest problem in communication is the illusion that it has taken place.”
– George Bernard Shaw.


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

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]