Uploaded image for project: 'OASIS Energy Interoperation TC'
  1. OASIS Energy Interoperation TC
  2. ENERGYINTEROP-494

EiQuote Service issues and errors

    XMLWordPrintable

    Details

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

      William Cox and Ed Cazalet

    • Proposal:
      Hide

      RequestQuote and SentQuote in Fig 6-5 line 939 are going the wrong direction - reverse.

      Add to specification something along the lines of: "EiQuote is to distribute (say) index prices out of ISO market day ahead; could be part of a service that a residential customer sees, tied to that quote with modification for retail. That information, a quote, becomes a tender."

      Terminology could be better aligned. Transactive state is "IndicationOfInterest" (quote) -945 TransactiveState True for all quotes. BITEL Tender should also be Tender TransactiveState

      TransactiveState must be documented. For example, in quote typically TransState is IndicationOfInterest. For Tenders, should be "Tender". Cearing and other prices should be "Publication"

      CreatedQuote should have the same semantics as for EiTender (see other item). Same except for Transactive State - services and payloads should be identical. With a tender have a quantity, quote I don't.

      Quantity in a publication SHALL be ignored.

      The requestor is responsible for setting transactive state appropriately as above.

      State that the quoteID has the same value as the returned emixBase:uid (e.g. in EiCreatedQuote).

      CanceledQuotePayuloadType is used except for cancel of DistributedQuote

      RequestQuote - must be quantity, think forward usage purchase.

      ADD requestor party to RequestQuote.

      Change cardinality of quoteID in Created to 0.., in Cancel t0 1...

      Adapt EiEvent mutli-response pattern.

      Show
      RequestQuote and SentQuote in Fig 6-5 line 939 are going the wrong direction - reverse. Add to specification something along the lines of: "EiQuote is to distribute (say) index prices out of ISO market day ahead; could be part of a service that a residential customer sees, tied to that quote with modification for retail. That information, a quote, becomes a tender." Terminology could be better aligned. Transactive state is "IndicationOfInterest" (quote) -945 TransactiveState True for all quotes. BITEL Tender should also be Tender TransactiveState TransactiveState must be documented. For example, in quote typically TransState is IndicationOfInterest. For Tenders, should be "Tender". Cearing and other prices should be "Publication" CreatedQuote should have the same semantics as for EiTender (see other item). Same except for Transactive State - services and payloads should be identical. With a tender have a quantity, quote I don't. Quantity in a publication SHALL be ignored. The requestor is responsible for setting transactive state appropriately as above. State that the quoteID has the same value as the returned emixBase:uid (e.g. in EiCreatedQuote). CanceledQuotePayuloadType is used except for cancel of DistributedQuote RequestQuote - must be quantity, think forward usage purchase. ADD requestor party to RequestQuote. Change cardinality of quoteID in Created to 0.. , in Cancel t0 1.. . Adapt EiEvent mutli-response pattern.
    • Resolution:
      Hide

      RequestQuote and SentQuote in Fig 6-5 line 939 are going the wrong direction - reverse.

      Add to specification something along the lines of: "EiQuote is to distribute (say) index prices out of ISO market day ahead; could be part of a service that a residential customer sees, tied to that quote with modification for retail. That information, a quote, becomes a tender."

      Transactive state is "IndicationOfInterest" (quote) -945 TransactiveState True for all quotes. BITEL Tender should also be Tender TransactiveState

      TransactiveState must be documented. For example, in quote typically TransState is IndicationOfInterest. For Tenders, should be "Tender". Cearing and other prices should be "Publication"

      CreatedQuote should have the same semantics as for EiTender (see ENERGYINTEROP-493 ) except for Transactive State - services and payloads should be identical. With a tender have a quantity, quote does not.

      Quantity in a publication SHALL be ignored. Add to conformance and spec.

      The requestor is responsible for setting transactive state appropriately as above. Add to spec.

      State that the quoteID has the same value as the returned emixBase:uid (e.g. in EiCreatedQuote). Add to spec.

      CanceledQuotePayuloadType is used except for cancel of DistributedQuote. Indicate in the spec.

      RequestQuote - must be quantity, think forward usage purchase.

      ADD requestor party to RequestQuote.

      Change cardinality of quoteID in Created to 0.., in Cancel t0 1...

      Adapt EiEvent mutli-response pattern.

      Show
      RequestQuote and SentQuote in Fig 6-5 line 939 are going the wrong direction - reverse. Add to specification something along the lines of: "EiQuote is to distribute (say) index prices out of ISO market day ahead; could be part of a service that a residential customer sees, tied to that quote with modification for retail. That information, a quote, becomes a tender." Transactive state is "IndicationOfInterest" (quote) -945 TransactiveState True for all quotes. BITEL Tender should also be Tender TransactiveState TransactiveState must be documented. For example, in quote typically TransState is IndicationOfInterest. For Tenders, should be "Tender". Cearing and other prices should be "Publication" CreatedQuote should have the same semantics as for EiTender (see ENERGYINTEROP-493 ) except for Transactive State - services and payloads should be identical. With a tender have a quantity, quote does not. Quantity in a publication SHALL be ignored. Add to conformance and spec. The requestor is responsible for setting transactive state appropriately as above. Add to spec. State that the quoteID has the same value as the returned emixBase:uid (e.g. in EiCreatedQuote). Add to spec. CanceledQuotePayuloadType is used except for cancel of DistributedQuote. Indicate in the spec. RequestQuote - must be quantity, think forward usage purchase. ADD requestor party to RequestQuote. Change cardinality of quoteID in Created to 0.. , in Cancel t0 1.. . Adapt EiEvent mutli-response pattern.

      Description

      WD26

      DistributeQuote - where do I send the operation? No response required - so is this a specialized Party? (the broadcast party). Say distribute to N Calif, only certain sizes of consumer. Also send as internet msssage to a list of registred IP addresses. Possibly multicast. Distinguish by Geolocation, or other means. (Say received a multicast).

      Require a respose from each "Broadcast/Distribute Agent", NOT from each Party that gets the broadcast.

      RequestQuote and SentQuote in Fig 6-5 line 939 are going the wrong direction.

      Distribute in that diagram should show a lighning

      bolt and broadcast

      EiQuote is to distribute (say) index prices out of ISO market day ahead; could be part of a service that a residential customer sees, tied to that quote with modification for retail. That information, a quote, becomes a tender.

      Ter,inology could be better aligned. Transactive state is an IndicationOfInterest (quote) -945 TransactiveState True for all quotes. BITEL Tender should also be Tender TransactiveState

      NOTE: Clearing price at a node - not closing price. That use of quote is not an indication of interest but more like a publication. Use that transactive state. Intercontinental Exchange, NYMEX create an index (computations) use for MTM for portfolios. Could use to supp...for that hour as def in day ahead clearing.

      CreatedQuote should have the same semantics as for EiTender (see other item). Same except for Transactive State - services and payloads should be identical. With a tender have a quantity, quote I don[t.

      Quantity in a publication SHALL be ignored.

      requestOr or reequestEr? Is responsible for setting transactive state appropriately as above.

      Should the quoteID be the uid?

      Keep CanceledQuotePayuloadType (except for cancel of DistributedQuote)

      RequestQuote - must be quantity, think forward usage pruchase. TransState - IndicationOfItnerest.

      ADD requestor party

      NOTE that request/sent is different from other services.

      DistributedQuotePayloadType with a response (from the distribution agent) Distribution agent is in our space, the distribution itself is not.

      Change cardinality of quoteID in Created to 0.., in Cancel t0 1... Adapt EiEvent mutli-response pattern.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: