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-473 Resources - Define Resouce and explore its use Collector
  3. ENERGYINTEROP-448

660 : Account concept in WD24 is under developed.

    Details

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

      Ed Cazalet

    • Proposal:
      Hide

      Change Paragraph 660 to read

      Energy Interoperation provides for the registration of Parties. Each Party must register one or more Accounts which can be used for further identification within a Party.
      Parties may enter into enabling Agreements with Counter Parties. Such Agreements may characterize a tariff by a retailer to a customer or enrollment in a Program such as a DR program. The Agreements would specify the Accounts that a Party and a Counter Party may agree to use.
      Accounts participate directly in energy transactions, using the Semantics from TeMIX. Accounts may enroll Resources with certain capabilities. Some of these Resources may share detailed capability and response information with their counter-party using the EMIX Resource semantics.

      The above will require some schema improvements. For example does a tender refer just to a Party or to a Party and an Account? It could refer to an Account if the Account was uniquely identified with a party. Or we define a PartyAccount that is both the PartyName and the AccountName or number.
      Energy Interoperation provides for the registration of Parties. Each Party must register one or more Accounts which can be used for further identification within a Party.
      Parties may enter into enabling Agreements with Counter Parties. Such Agreements may characterize a tariff by a retailer to a customer or enrollment in a Program such as a DR program. The Agreements would specify the Accounts that a Party and a Counter Party may agree to use.
      Accounts participate directly in energy transactions, using the Semantics from TeMIX. Accounts may enroll Resources with certain capabilities. Some of these Resources may share detailed capability and response information with their counter-party using the EMIX Resource semantics.

      The above will require some schema improvements. For example does a tender refer just to a Party or to a Party and an Account? It could refer to an Account if the Account was uniquely identified with a party. Or we define a PartyAccount that is both the PartyName and the AccountName or number.

      Show
      Change Paragraph 660 to read Energy Interoperation provides for the registration of Parties. Each Party must register one or more Accounts which can be used for further identification within a Party. Parties may enter into enabling Agreements with Counter Parties. Such Agreements may characterize a tariff by a retailer to a customer or enrollment in a Program such as a DR program. The Agreements would specify the Accounts that a Party and a Counter Party may agree to use. Accounts participate directly in energy transactions, using the Semantics from TeMIX. Accounts may enroll Resources with certain capabilities. Some of these Resources may share detailed capability and response information with their counter-party using the EMIX Resource semantics. The above will require some schema improvements. For example does a tender refer just to a Party or to a Party and an Account? It could refer to an Account if the Account was uniquely identified with a party. Or we define a PartyAccount that is both the PartyName and the AccountName or number. Energy Interoperation provides for the registration of Parties. Each Party must register one or more Accounts which can be used for further identification within a Party. Parties may enter into enabling Agreements with Counter Parties. Such Agreements may characterize a tariff by a retailer to a customer or enrollment in a Program such as a DR program. The Agreements would specify the Accounts that a Party and a Counter Party may agree to use. Accounts participate directly in energy transactions, using the Semantics from TeMIX. Accounts may enroll Resources with certain capabilities. Some of these Resources may share detailed capability and response information with their counter-party using the EMIX Resource semantics. The above will require some schema improvements. For example does a tender refer just to a Party or to a Party and an Account? It could refer to an Account if the Account was uniquely identified with a party. Or we define a PartyAccount that is both the PartyName and the AccountName or number.
    • Resolution:
      Hide

      Defer post PR02; delete wording related to Accounts for PR02.

      Show
      Defer post PR02; delete wording related to Accounts for PR02.

      Description

      660: Currently reads –
      Energy Interoperation defines Parties which enroll Accounts with counter-Parties. Some of those
      Accounts participate directly in energy transactions, using the Semantics from TEMIX. Others enroll as
      Resources with certain capabilities. Some of these Resources may share detailed capability and
      response information with their counter-party using the EMIX Resource semantics.

      I can find no specification of Account in the WD24 schema.

      I can find no place where a VTN or VEN is registered or enrolled or otherwise determined by an interaction among Accounts.

        Attachments

          Activity

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

          "Accounts" are similar to "Roles" as described elsewhere in the specification.

          I agree that the concept of "Accounts" is under developed; I suggest deleting it for PR02.

          Change the text to indicate roles, not Accounts, for parties.

          Show
          william.cox William Cox (Inactive) added a comment - "Accounts" are similar to "Roles" as described elsewhere in the specification. I agree that the concept of "Accounts" is under developed; I suggest deleting it for PR02. Change the text to indicate roles, not Accounts, for parties.
          Hide
          Permalink
          toby.considine Toby Considine (Inactive) added a comment -

          Opening all Deferred Items following fote out of WD25 as a CSD for PR

          Show
          toby.considine Toby Considine (Inactive) added a comment - Opening all Deferred Items following fote out of WD25 as a CSD for PR
          Hide
          Permalink
          toby.considine Toby Considine (Inactive) added a comment -

          Accounts are part of enrollemtn, as a sper-odinate above Party.

          For example:

          A VEN enrolls with a VTN and get an Account #
          A VEN in a chain store enerolls with a VTN and get the same account as other members of the chain.

          As we have decided that Enrollment is largely out of scope, so, too, is Account.

          Show
          toby.considine Toby Considine (Inactive) added a comment - Accounts are part of enrollemtn, as a sper-odinate above Party. For example: A VEN enrolls with a VTN and get an Account # A VEN in a chain store enerolls with a VTN and get the same account as other members of the chain. As we have decided that Enrollment is largely out of scope, so, too, is Account.
          Hide
          Permalink
          toby.considine Toby Considine (Inactive) added a comment -

          No further change needed

          Show
          toby.considine Toby Considine (Inactive) added a comment - No further change needed
          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

            People

            • Assignee:
              toby.considine Toby Considine (Inactive)
              Reporter:
              ecazalet Edward Cazalet (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: