Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: wd15
    • Fix Version/s: wd25
    • Component/s: spec
    • Labels:
      None
    • Environment:

      Bruce Bartell wd16 lines 598-604

    • Proposal:
      Hide

      Add defintion for interaction in appropriate section. Replace in this section with something related to the table below.

      Show
      Add defintion for interaction in appropriate section. Replace in this section with something related to the table below.
    • Resolution:
      Hide

      Resolve per sibling subtask ENERGYINTEROP-216

      Show
      Resolve per sibling subtask ENERGYINTEROP-216

      Description

      Is this similar or equivalent to DR Program Enrollment?

        Attachments

          Activity

          bbartell Bruce Bartell (Inactive) created issue -
          toby.considine Toby Considine (Inactive) made changes -
          Field Original Value New Value
          Status New [ 10000 ] Open [ 1 ]
          william.cox William Cox (Inactive) made changes -
          Environment Bruce Bartell wd16 lines 598-604
          Hide
          toby.considine Toby Considine (Inactive) added a comment -

          I think this should be expressed in the language of the EMIX Option, i.e., a business schedule during which execution calls can be mase with a warranted response time.

          Show
          toby.considine Toby Considine (Inactive) added a comment - I think this should be expressed in the language of the EMIX Option, i.e., a business schedule during which execution calls can be mase with a warranted response time.
          william.cox William Cox (Inactive) made changes -
          Resolution Defer. Standing bids in a subsequent draft.
          Status Open [ 1 ] Deferred [ 10001 ]
          toby.considine Toby Considine (Inactive) made changes -
          Fix Version/s wd19 [ 10125 ]
          Status Deferred [ 10001 ] Open [ 1 ]
          william.cox William Cox (Inactive) made changes -
          Parent ENERGYINTEROP-325 [ 18294 ]
          Issue Type Improvement [ 4 ] Sub-task [ 5 ]
          william.cox William Cox (Inactive) made changes -
          Fix Version/s wd19 [ 10125 ]
          Resolution Defer. Standing bids in a subsequent draft. Resolve per sibling subtask ENERGYINTEROP-216
          william.cox William Cox (Inactive) made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          william.cox William Cox (Inactive) made changes -
          Assignee William Cox [ william.cox ] Girish Ghatikar [ gghatikar ]
          Hide
          toby.considine Toby Considine (Inactive) added a comment -

          Clarify DR Standing Bid.

          Show
          toby.considine Toby Considine (Inactive) added a comment - Clarify DR Standing Bid.
          Hide
          gghatikar Girish Ghatikar (Inactive) added a comment -

          In a demand-bidding scenario for DR, a standing bid is typically set by the VEN (e.g., DR participant) within a particular DR service provider program with option to adjust or cancel the bid. If the bid is not adjusted/canceled, the standing bid will be submitted at the end of the bid period. This is also sometimes called (in Auto-DR terminology) as "auto bid, auto shed," meaning you set the bid one time (standing bid) and it will be submitted without any actions from the participant.

          Page 83 of OpenADR 1.0 specifications state the following on standing bid – "A standing bid is a bid that will be submitted by the DRAS for a participant if no other bid is submitted by the participant. The ability to automatically submit standing bids increases the level of participation in programs that require bidding. In some case the utility's or ISO's IT infrastructure will already support the notion of standing bids and in those cases it is not necessary for the DRAS to provide this functionality. In fact there may be scenarios where there are programs that require bidding, but all the bidding is handled by a different system than the DRAS, including the handling of standing bids. In this case, from the DRAS point of view, the program will not require bidding and all the DR events are simply issued by the utility or ISO as in the case of programs with no bidding. The utility or ISO will simply handle all the bidding as they normally would and use the DRAS to issue the DR events."

          Show
          gghatikar Girish Ghatikar (Inactive) added a comment - In a demand-bidding scenario for DR, a standing bid is typically set by the VEN (e.g., DR participant) within a particular DR service provider program with option to adjust or cancel the bid. If the bid is not adjusted/canceled, the standing bid will be submitted at the end of the bid period. This is also sometimes called (in Auto-DR terminology) as "auto bid, auto shed," meaning you set the bid one time (standing bid) and it will be submitted without any actions from the participant. Page 83 of OpenADR 1.0 specifications state the following on standing bid – "A standing bid is a bid that will be submitted by the DRAS for a participant if no other bid is submitted by the participant. The ability to automatically submit standing bids increases the level of participation in programs that require bidding. In some case the utility's or ISO's IT infrastructure will already support the notion of standing bids and in those cases it is not necessary for the DRAS to provide this functionality. In fact there may be scenarios where there are programs that require bidding, but all the bidding is handled by a different system than the DRAS, including the handling of standing bids. In this case, from the DRAS point of view, the program will not require bidding and all the DR events are simply issued by the utility or ISO as in the case of programs with no bidding. The utility or ISO will simply handle all the bidding as they normally would and use the DRAS to issue the DR events."
          toby.considine Toby Considine (Inactive) made changes -
          Fix Version/s wd25 [ 10149 ]
          Status Resolved [ 5 ] Applied [ 10002 ]
          Hide
          toby.considine Toby Considine (Inactive) added a comment -

          As voted in meeting

          Show
          toby.considine Toby Considine (Inactive) added a comment - As voted in meeting
          toby.considine Toby Considine (Inactive) made changes -
          Status Applied [ 10002 ] Closed [ 6 ]

            People

            • Assignee:
              gghatikar Girish Ghatikar (Inactive)
              Reporter:
              bbartell Bruce Bartell (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: