Change cardinality of EventInfo within EiEvent (WD16- 642)

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • wd17
    • Affects Version/s: wd16
    • Component/s: service
    • None
    • Environment:

      Ed Koch wd16 line 642

    • Hide

      Further clarify how sequenes of EventInfo values are tied to wscalendar and depending upon how that is done allow for mutliple EventInfo types (i.e. multiple EventInfo sequences). In order to support mutiple EventInfo types within a single EiEvent we need to add an additioan name parameter so that if the two EventInfo types are the same base type (i.e. LOAD_AMOUNT) they can be differentiated. For example there may be one EventInfo instance called "Local Generation" level that has a type of LOAD_AMOUNT while there may also be another EventInfo type called "Local Load" ALSO of type LOAD_AMOUNT. "Local Generation" would have its own sequence of scheduled values, while "Local Load" may have its own set of scheduled values. The 1.0 version of OpenADR supports this mechanism.

      Show
      Further clarify how sequenes of EventInfo values are tied to wscalendar and depending upon how that is done allow for mutliple EventInfo types (i.e. multiple EventInfo sequences). In order to support mutiple EventInfo types within a single EiEvent we need to add an additioan name parameter so that if the two EventInfo types are the same base type (i.e. LOAD_AMOUNT) they can be differentiated. For example there may be one EventInfo instance called "Local Generation" level that has a type of LOAD_AMOUNT while there may also be another EventInfo type called "Local Load" ALSO of type LOAD_AMOUNT. "Local Generation" would have its own sequence of scheduled values, while "Local Load" may have its own set of scheduled values. The 1.0 version of OpenADR supports this mechanism.
    • Hide

      Cardinality 1..* for EventInfo (which should probably be EiEventInfo).

      Also, a 1..1 association to a schedule is part of each EventInfo.

      Done

      Show
      Cardinality 1..* for EventInfo (which should probably be EiEventInfo). Also, a 1..1 association to a schedule is part of each EventInfo. Done

      The cardinalty of EventInfo shold not be 1..1. For a particular instance of an EventInfo there can be a sequence of EventInfo values between the Start and End time of an event. For example an EventInfo type of LOAD_AMOUNT may take on a scheduled sequence of values between the start and end time of the event. Furthermore the OpernADR 1.0 spec supports multiple EventInfo types defined for a single EiEvent instance so that there would be a sequence of values associated with each type.

            Assignee:
            William Cox (Inactive)
            Reporter:
            Ed Koch (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: