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

It is unclear exactly how the EiAvail force filter works.

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: wd27
    • Fix Version/s: wd29
    • Component/s: schema
    • Labels:
      None
    • Environment:

      OpenADR

    • Proposal:
      Hide

      Eliminate Force

      Show
      Eliminate Force
    • Resolution:
      Hide

      Eliminate Force

      Show
      Eliminate Force

      Description

      What would happen if a DR event intersects with more than one availability period when Force in in effect? What if the VEN is always available? Is the intersect between the availability and the DR event time frame that triggers a "FORCE" the start of the event, then end of the event, or any point during the event time frame? More description is needed

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          toby.considine Toby Considine (Inactive) created issue -
          toby.considine Toby Considine (Inactive) made changes -
          Field Original Value New Value
          Assignee Toby Considine [ toby.considine ] Ed Koch [ ed.koch ]
          toby.considine Toby Considine (Inactive) made changes -
          Fix Version/s wd28 [ 10191 ]
          Status New [ 10000 ] Open [ 1 ]
          Hide
          Permalink
          ed.koch Ed Koch (Inactive) added a comment -

          I can see where this can get a little complicated I think we have the following options:

          (1) The force constraints is applied to any availability period that intersects with the active event period and if there is more than one of them then the event start time is the beginning of the fist availability period that the event intersects with and the end of the event period is the end of the last availability period that it interacts with.

          (2) We eliminate the force altogether. I think I like this option the most.

          Show
          ed.koch Ed Koch (Inactive) added a comment - I can see where this can get a little complicated I think we have the following options: (1) The force constraints is applied to any availability period that intersects with the active event period and if there is more than one of them then the event start time is the beginning of the fist availability period that the event intersects with and the end of the event period is the end of the last availability period that it interacts with. (2) We eliminate the force altogether. I think I like this option the most.
          toby.considine Toby Considine (Inactive) made changes -
          Fix Version/s wd29 [ 10192 ]
          Fix Version/s wd28 [ 10191 ]
          toby.considine Toby Considine (Inactive) made changes -
          Proposal Eliminate Force
          Resolution Eliminate Force
          toby.considine Toby Considine (Inactive) made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          toby.considine Toby Considine (Inactive) made changes -
          Assignee Ed Koch [ ed.koch ] Girish Ghatikar [ gghatikar ]
          Hide
          Permalink
          william.cox William Cox (Inactive) added a comment - - edited

          See ENERGYINTEROP-513 :

          Show
          william.cox William Cox (Inactive) added a comment - - edited See ENERGYINTEROP-513 :
          toby.considine Toby Considine (Inactive) made changes -
          Status Resolved [ 5 ] Applied [ 10002 ]
          Hide
          Permalink
          toby.considine Toby Considine (Inactive) added a comment -

          Moved to closed per unanimous vote (Aaron no longer present) in TC Meeting 2011-11-09

          Show
          toby.considine Toby Considine (Inactive) added a comment - Moved to closed per unanimous vote (Aaron no longer present) in TC Meeting 2011-11-09
          toby.considine Toby Considine (Inactive) made changes -
          Status Applied [ 10002 ] Closed [ 6 ]

            People

            • Assignee:
              gghatikar Girish Ghatikar (Inactive)
              Reporter:
              toby.considine Toby Considine (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: