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

Incorporate use of emix price models into EiEvent (WD16 - 642, 709)

    Details

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

      Ed Koch

    • Proposal:
      Hide

      We should expand the EventInfo types within EiEvent to include a price model in addition to the LOAD level types. This can be accomplished in a couple of ways that is completely consistent with the EIQuote service. We can either expand the EventInfo types to include the appropriate references to emix just like we have done in the EIQuote service payloads OR if we find that the price based data model used for EiQuote and EIEvent are identical then I recommend we create a common data model that can be used with BOTH the EIEvent and the EIQuote. This would maintain consistency between the models for prices and how emix is used, but allow prices to be sent using more than one service which I think solves our problem of how emax is used for both priced based DR programs and the newer transactional based interactions described in section 6.

      Show
      We should expand the EventInfo types within EiEvent to include a price model in addition to the LOAD level types. This can be accomplished in a couple of ways that is completely consistent with the EIQuote service. We can either expand the EventInfo types to include the appropriate references to emix just like we have done in the EIQuote service payloads OR if we find that the price based data model used for EiQuote and EIEvent are identical then I recommend we create a common data model that can be used with BOTH the EIEvent and the EIQuote. This would maintain consistency between the models for prices and how emix is used, but allow prices to be sent using more than one service which I think solves our problem of how emax is used for both priced based DR programs and the newer transactional based interactions described in section 6.
    • Resolution:
      Hide

      Consider a PRICE EiEvent type. Associate an emix object with the EIEvent payload

      We (or profilers) may consider constraining the use of the emix object within this context to keep it simple. If we need anything more complicated or transactional in nature then we use the EIQuote service.

      Show
      Consider a PRICE EiEvent type. Associate an emix object with the EIEvent payload We (or profilers) may consider constraining the use of the emix object within this context to keep it simple. If we need anything more complicated or transactional in nature then we use the EIQuote service.

      Description

      Many DR programs (i.e. CPP) don't need all the transactional services defined in section 6 and specifying the sending of prices in a single service like EiQuote which is seperate from EiEvent unncessarily complicates the interactions with devices that use EiEvent and makes it harder for them to migrate between price based and non-price based DR programs.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          william.cox William Cox (Inactive) added a comment - - edited

          The later part of the proposal seems to suggest that EiQuote messages can be bundled with EiEvent messages, and that they should be able to be decoupled. The proposed solution is worth investigating.

          Please clarify.

          Show
          william.cox William Cox (Inactive) added a comment - - edited The later part of the proposal seems to suggest that EiQuote messages can be bundled with EiEvent messages, and that they should be able to be decoupled. The proposed solution is worth investigating. Please clarify.
          Hide
          Permalink
          toby.considine Toby Considine (Inactive) added a comment -

          Will investigate "Bundling" of services (Events, Program Calls, Prices) into a single service after the services gel.

          Show
          toby.considine Toby Considine (Inactive) added a comment - Will investigate "Bundling" of services (Events, Program Calls, Prices) into a single service after the services gel.
          Hide
          Permalink
          ed.koch Ed Koch (Inactive) added a comment -

          I'm re-opening this issue becasue this is my proposal for how we include price communcitions in the EIEvent data type.

          Although bundling was proposed as one way of dealing with this, I propose that we do not use the currently proposed bundling mechanism as in my opinion it is more complicated than necessary and will obsolete the EiEvent service. I proposes that we simply create a PRICE EiEvent type and reference an emix object from with the EIEvetn strcuture. Further I propose that we profile the use of the emix object within this context to keep it simple. If we need anything more complicated or transactional in nature then we use the EIQuote service.

          Show
          ed.koch Ed Koch (Inactive) added a comment - I'm re-opening this issue becasue this is my proposal for how we include price communcitions in the EIEvent data type. Although bundling was proposed as one way of dealing with this, I propose that we do not use the currently proposed bundling mechanism as in my opinion it is more complicated than necessary and will obsolete the EiEvent service. I proposes that we simply create a PRICE EiEvent type and reference an emix object from with the EIEvetn strcuture. Further I propose that we profile the use of the emix object within this context to keep it simple. If we need anything more complicated or transactional in nature then we use the EIQuote service.
          Hide
          Permalink
          toby.considine Toby Considine (Inactive) added a comment -

          Assigning to Cox to implement as Ed suggested

          Show
          toby.considine Toby Considine (Inactive) added a comment - Assigning to Cox to implement as Ed suggested
          Hide
          Permalink
          william.cox William Cox (Inactive) added a comment -

          Added an association to an emix class from EiEvent.

          Left (for further review) the PRICE_RELATIVE and PRICE_MULTIPLE in the EventInfoTypeID, but I think they should possibly be removed.

          Show
          william.cox William Cox (Inactive) added a comment - Added an association to an emix class from EiEvent. Left (for further review) the PRICE_RELATIVE and PRICE_MULTIPLE in the EventInfoTypeID, but I think they should possibly be removed.
          Hide
          Permalink
          william.cox William Cox (Inactive) added a comment -

          Applied to 20110305 EI model; text changes will follow.

          Show
          william.cox William Cox (Inactive) added a comment - Applied to 20110305 EI model; text changes will follow.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: