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

Line 706: OptOut equivalent in IRC model includes: economic, emergency, must run, not participating, outage run status, override status, participating.

    Details

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

      Bruce Bartell wd15 line 706

    • Proposal:
      Hide

      The proposed resolution then is to leave everything as is, and get confirmation from the IRC that this meets their needs. (see comment below)

      Show
      The proposed resolution then is to leave everything as is, and get confirmation from the IRC that this meets their needs. (see comment below)
    • Resolution:
      Hide

      (Public review 1 resolution that was not agreed upon by the committee: Added Reason string to OptOuts. A later activity will permit definition of constrained sets of strings.) [included in model]

      Use wscal:Vavailability to define Opt In, Opt Out and constraints (acceptSchedule and notAcceptSchedule)
      Add optReason string to renamed EiEoptInOut but not to EiConstraint

      Standard strings (as per IRC) plus x-strings

      Defined strings are
      economic
      emergency
      mustRun
      notParticipating
      outageRunStatus
      overrideStatus
      participating

      Show
      (Public review 1 resolution that was not agreed upon by the committee: Added Reason string to OptOuts. A later activity will permit definition of constrained sets of strings.) [included in model] Use wscal:Vavailability to define Opt In, Opt Out and constraints (acceptSchedule and notAcceptSchedule) Add optReason string to renamed EiEoptInOut but not to EiConstraint Standard strings (as per IRC) plus x-strings Defined strings are economic emergency mustRun notParticipating outageRunStatus overrideStatus participating

      Description

      Group should respond on actual requirement. Does Retail DR really have opt-in programs? Are the remaining items applicable?
      Recommend expanding Option to be equivalent to commit or dispatch status and revising the service names accordingly.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          8 older comments
          Hide
          Permalink
          david.holmberg David Holmberg (Inactive) added a comment -

          I discussed this issue with Bill Cox, Toby, Bruce, and EdK. There is apparently a requirement in the NAESB req docs for an "Opt-In" approach, but Ed Koch did not know the source of that, whether there is really a need, or simply it was a use case discussed that might be useful. OpenADR is the basis for the current Constraint and Opt-Out approach, and the current approach has the blessing of the OpenADR TF (I believe). Bill pointed out that the EiConstraint service actually has both positive (acceptSchedule) and negative (notAcceptSchedule) views of the constraints, but Bill thought adding this positive/negative element to OptOut (or changing the name to something like "tempConstraint") would be problematic.

          To the issue of text strings, which are presently covered with the "reason" attribute in the EiOptout class, Bruce didn't like the name "reason" since maybe it didn't express the idea of the project codes that would be passed in this text string (such as the IRC text items mentioned here, i.e., "economic, emergency, must run, not participating, outage run status, override status, participating.") We can change the name if there is a better suggestion that everyone agrees to.

          The proposed resolution then is to leave everything as is, and get confirmation from the IRC that this meets their needs.

          Show
          david.holmberg David Holmberg (Inactive) added a comment - I discussed this issue with Bill Cox, Toby, Bruce, and EdK. There is apparently a requirement in the NAESB req docs for an "Opt-In" approach, but Ed Koch did not know the source of that, whether there is really a need, or simply it was a use case discussed that might be useful. OpenADR is the basis for the current Constraint and Opt-Out approach, and the current approach has the blessing of the OpenADR TF (I believe). Bill pointed out that the EiConstraint service actually has both positive (acceptSchedule) and negative (notAcceptSchedule) views of the constraints, but Bill thought adding this positive/negative element to OptOut (or changing the name to something like "tempConstraint") would be problematic. To the issue of text strings, which are presently covered with the "reason" attribute in the EiOptout class, Bruce didn't like the name "reason" since maybe it didn't express the idea of the project codes that would be passed in this text string (such as the IRC text items mentioned here, i.e., "economic, emergency, must run, not participating, outage run status, override status, participating.") We can change the name if there is a better suggestion that everyone agrees to. The proposed resolution then is to leave everything as is, and get confirmation from the IRC that this meets their needs.
          Hide
          Permalink
          william.cox William Cox (Inactive) added a comment -

          Planned resolution is to use the constraints from EMIX, align the Ei Constraints (slow moving), and add OptIn in addition to OptOut. Needs careful definition of priority, e.g. Opt-In/Opt-Out beats Constraints, Relationship and conformance for incompatible Contraint In/Out and Opt In/Out must be addressed.

          Show
          william.cox William Cox (Inactive) added a comment - Planned resolution is to use the constraints from EMIX, align the Ei Constraints (slow moving), and add OptIn in addition to OptOut. Needs careful definition of priority, e.g. Opt-In/Opt-Out beats Constraints, Relationship and conformance for incompatible Contraint In/Out and Opt In/Out must be addressed.
          Hide
          Permalink
          toby.considine Toby Considine (Inactive) added a comment -

          Use WS-Calendar vavailability (EMIX Business Calendar) to define Opt In, Opt Out.
          Add a Reason string to Opt Out
          Standard strings (as per IRC) plus x-strings

          Show
          toby.considine Toby Considine (Inactive) added a comment - Use WS-Calendar vavailability (EMIX Business Calendar) to define Opt In, Opt Out. Add a Reason string to Opt Out Standard strings (as per IRC) plus x-strings
          Hide
          Permalink
          william.cox William Cox (Inactive) added a comment -

          Included in 20110305 model.

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

          Are these addressed and the standard strings used?

          Show
          william.cox William Cox (Inactive) added a comment - Are these addressed and the standard strings used?

            People

            • Assignee:
              toby.considine Toby Considine (Inactive)
              Reporter:
              bbartell Bruce Bartell (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: