Use of eiQuote to represent Time-of-Use and Consumption Block rates

    • Type: Task
    • Resolution: Fixed
    • Priority: Major
    • wd25
    • Affects Version/s: wd22
    • Component/s: schema
    • None
    • Hide

      Need to have working session to resolved how the actual payload would look, and supporting structures and compliance rules enforced by schema.

      Show
      Need to have working session to resolved how the actual payload would look, and supporting structures and compliance rules enforced by schema.
    • Hide

      EMIX addresses block and tier price information, and EiQuote delivers an EMIX artifact.

      (See e.g. resolutions to EMIX-129, EMIX-400, EMIX-472, EMIX-304.)

      Ensure that EiQuote indicates in text (it's already in payloads) that the payload is any emix artifact.

      Show
      EMIX addresses block and tier price information, and EiQuote delivers an EMIX artifact. (See e.g. resolutions to EMIX-129 , EMIX-400 , EMIX-472 , EMIX-304 .) Ensure that EiQuote indicates in text (it's already in payloads) that the payload is any emix artifact.

      Structure to support Time-of-Use in conjunction with Consumption Block Rates is not apparent.
      The Consumption Block is represented by type blockPowerFullRequirementsProductDescription which is a type of productDescription referernced by the wsCalendar-attach.
      The interval and gluon structures are parallel in emixBase to the productDescrpiton. I think the interval and gluon can represent the same structures as part of a recursive structure. If these contain the date/time ranges that would have the productDescription embedded in the the list, then I think this could represent the TOU with each occurance containing the block rates.

            Assignee:
            William Cox (Inactive)
            Reporter:
            Bruce Bartell (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: