OASIS Energy Interoperation TCIcon indicating the project type

OASIS Energy Interoperation TC

Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-325 Service Defintion Improvements collector
  3. ENERGYINTEROP-300

May need to define the enumerated values for the EiEvent Status (line 892)

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Proposal:
      Hide

      far, near, initiated, completed, cancelled

      Show
      far, near, initiated, completed, cancelled
    • Resolution:
      Hide

      After Ed Koch, with changes:
      If there's a restricted set of strings (or pre-defined strings) it should be in the specification, not only conformance.

      • EIEvent.status should be of type string and have the following [restricted] values (lower case; extensibility is indicated by an "x-" prefix)

      o none - meaning no event pending.
      o far - meaning event pending in the far future. The exact definition of how far in the future this refers is dependent upon the DR program, but typically means the next day.
      o near - meaning event pending in the near future. The exact definition of how near in the future the pending event is active is dependent on the DR program
      o active - The event has been initiated and is currently active.
      o completed - The event has completed.
      o canceled - The event has been canceled.

      These predefined strings have the defined meaning, which should be inserted in the document and schemas, but it must be an extensible list.

      See also ENERGYINTEROP-333 and its references for documentation of the overall solution.

      Show
      After Ed Koch, with changes: If there's a restricted set of strings (or pre-defined strings) it should be in the specification, not only conformance. • EIEvent.status should be of type string and have the following [restricted] values (lower case; extensibility is indicated by an "x-" prefix) o none - meaning no event pending. o far - meaning event pending in the far future. The exact definition of how far in the future this refers is dependent upon the DR program, but typically means the next day. o near - meaning event pending in the near future. The exact definition of how near in the future the pending event is active is dependent on the DR program o active - The event has been initiated and is currently active. o completed - The event has completed. o canceled - The event has been canceled. These predefined strings have the defined meaning, which should be inserted in the document and schemas, but it must be an extensible list. See also ENERGYINTEROP-333 and its references for documentation of the overall solution.

      Description

      Try to pin down the enumerated values of EiEvent:status.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          bbartell Bruce Bartell (Inactive) added a comment -

          Identified in OSG model as:
          cancelled
          completed
          far
          initiated
          near

          SEP 2.0 is (as of November 2010)
          Bit Type

          0 Scheduled
          1 Active
          2 Modified
          3 Cancelled
          4 Cancelled with Randomization
          5 Other

          SEP does not modify an event. It is cancelled and re-scheduled. This is for DRLC, only, so it would seem mappability may not be an issue.

          Show
          bbartell Bruce Bartell (Inactive) added a comment - Identified in OSG model as: cancelled completed far initiated near SEP 2.0 is (as of November 2010) Bit Type 0 Scheduled 1 Active 2 Modified 3 Cancelled 4 Cancelled with Randomization 5 Other SEP does not modify an event. It is cancelled and re-scheduled. This is for DRLC, only, so it would seem mappability may not be an issue.
          Hide
          Permalink
          david.holmberg David Holmberg (Inactive) added a comment -

          dgh-needs discussion in committee.

          Show
          david.holmberg David Holmberg (Inactive) added a comment - dgh-needs discussion in committee.
          Hide
          Permalink
          david.holmberg David Holmberg (Inactive) added a comment -

          Propose a set of enumerated values that meets the SEP and OpenADR needs.

          Show
          david.holmberg David Holmberg (Inactive) added a comment - Propose a set of enumerated values that meets the SEP and OpenADR needs.
          Hide
          Permalink
          david.holmberg David Holmberg (Inactive) added a comment -

          Also, how do we address "no event", in a pull architecture?

          Show
          david.holmberg David Holmberg (Inactive) added a comment - Also, how do we address "no event", in a pull architecture?
          Hide
          Permalink
          ed.koch Ed Koch (Inactive) added a comment -

          It might be ok to put the specifications for this in the conformance section. Currently I am doing this for OpenADR and am making as per the following:

          • The EIEvent.status should have the following restricted values:
          o NONE - meaning no event pending.
          o FAR - meaning event pending in the far future. The exact definition of how far in the future this refers is dependent upon the DR program, but typically means the next day.
          o NEAR - meaning event pending in the near future. The exact definition of how near in the future the pending event is active is dependent on the DR program
          o ACTIVE - The event has been initiated and is currently active.
          o COMPLETED - The event has completed.
          o CANCELLED - The event has been cancelled.

          Show
          ed.koch Ed Koch (Inactive) added a comment - It might be ok to put the specifications for this in the conformance section. Currently I am doing this for OpenADR and am making as per the following: • The EIEvent.status should have the following restricted values: o NONE - meaning no event pending. o FAR - meaning event pending in the far future. The exact definition of how far in the future this refers is dependent upon the DR program, but typically means the next day. o NEAR - meaning event pending in the near future. The exact definition of how near in the future the pending event is active is dependent on the DR program o ACTIVE - The event has been initiated and is currently active. o COMPLETED - The event has completed. o CANCELLED - The event has been cancelled.
          Hide
          Permalink
          bbartell Bruce Bartell (Inactive) added a comment -

          Why do we need an Ei in front of these values?

          Show
          bbartell Bruce Bartell (Inactive) added a comment - Why do we need an Ei in front of these values?
          Hide
          Permalink
          william.cox William Cox (Inactive) added a comment -

          Agree with Bruce. The strings should be (lower case) as Ed defined in his comment; I'm updating the resolution and putting in the model and spec.

          Show
          william.cox William Cox (Inactive) added a comment - Agree with Bruce. The strings should be (lower case) as Ed defined in his comment; I'm updating the resolution and putting in the model and spec.
          Hide
          Permalink
          william.cox William Cox (Inactive) added a comment -

          Applied in 20110305 model

          Show
          william.cox William Cox (Inactive) added a comment - Applied in 20110305 model

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              ed.koch Ed Koch (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: