Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-515 Collector for OpenADR Alliance Comments EI PR02
  3. ENERGYINTEROP-513

The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload.

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: No Action
    • Affects Version/s: wd27
    • Fix Version/s: wd32
    • Component/s: model, schema
    • Labels:
      None
    • Environment:

      OpenADR

    • Proposal:
      Hide

      No action required.

      Show
      No action required.

      Description

      The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload. Oddly it does get returned in eiCreatedAvailPayload. It doesn't seem to make sense that the OpenADR Alliance Comments on EI v1.0, July 8, 2011 Page | 3 VTN would dictate how events get mapped to the VENs availability schedule. More description is needed.

      NOTE 20111002: Per ENERGYINTEROP-512 "Force" has been removed from the enumeration.

      NOTE 20111025: The EiAvailBehaviorType is in EiAvailType, and is sent by the VEN to the VTN. This appears to address the issue. The response (EiCreatedAvail) returns an AvailID.

        Attachments

          Activity

          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 ]
          william.cox William Cox (Inactive) made changes -
          Parent ENERGYINTEROP-515 [ 19370 ]
          Issue Type Improvement [ 4 ] Sub-task [ 5 ]
          toby.considine Toby Considine (Inactive) made changes -
          Assignee Ed Koch [ ed.koch ] William Cox [ william.cox ]
          toby.considine Toby Considine (Inactive) made changes -
          Fix Version/s wd29 [ 10192 ]
          Fix Version/s wd28 [ 10191 ]
          william.cox William Cox (Inactive) made changes -
          Component/s model [ 10150 ]
          Assignee William Cox [ william.cox ] Toby Considine [ toby.considine ]
          Description The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload. Oddly it does get returned in eiCreatedAvailPayload. It doesn't seem to make sense that the OpenADR Alliance Comments on EI v1.0, July 8, 2011 Page | 3 VTN would dictate how events get mapped to the VENs availability schedule. More description is needed. The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload. Oddly it does get returned in eiCreatedAvailPayload. It doesn't seem to make sense that the OpenADR Alliance Comments on EI v1.0, July 8, 2011 Page | 3 VTN would dictate how events get mapped to the VENs availability schedule. More description is needed.

          NOTE 20111002: Per ENERGYINTEROP-512 "Force" has been removed from the enumeration.
          william.cox William Cox (Inactive) made changes -
          Assignee Toby Considine [ toby.considine ] Girish Ghatikar [ gghatikar ]
          william.cox William Cox (Inactive) made changes -
          Proposal No action required.
          Description The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload. Oddly it does get returned in eiCreatedAvailPayload. It doesn't seem to make sense that the OpenADR Alliance Comments on EI v1.0, July 8, 2011 Page | 3 VTN would dictate how events get mapped to the VENs availability schedule. More description is needed.

          NOTE 20111002: Per ENERGYINTEROP-512 "Force" has been removed from the enumeration.
          The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload. Oddly it does get returned in eiCreatedAvailPayload. It doesn't seem to make sense that the OpenADR Alliance Comments on EI v1.0, July 8, 2011 Page | 3 VTN would dictate how events get mapped to the VENs availability schedule. More description is needed.

          NOTE 20111002: Per ENERGYINTEROP-512 "Force" has been removed from the enumeration.

          NOTE 20111025: The EiAvailBehaviorType is in EiAvailType, and is sent by the VEN to the VTN. This appears to address the issue. The response (EiCreatedAvail) returns an AvailID.
          william.cox William Cox (Inactive) made changes -
          Fix Version/s wd32 [ 10200 ]
          Fix Version/s wd29 [ 10192 ]
          Assignee Girish Ghatikar [ gghatikar ] William Cox [ william.cox ]
          Resolution No Action [ 8 ]
          Status Open [ 1 ] Resolved [ 5 ]
          william.cox William Cox (Inactive) made changes -
          Status Resolved [ 5 ] Applied [ 10002 ]
          william.cox William Cox (Inactive) made changes -
          Status Applied [ 10002 ] Closed [ 6 ]

            People

            • Assignee:
              william.cox William Cox (Inactive)
              Reporter:
              toby.considine Toby Considine (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: