search

flexoffer / flexoffer-specifications

Specifications of FlexOffer
2 stars 2 forks source link

[CCP] offer acceptance conditions #8

Open DuneSe opened 2 years ago

DuneSe commented 2 years ago

Question: What is here the meaning of “acceptance of flex offer”? That the offer (message with its parameters) is OK in terms of data structure, formats and constraints, or that (at least a part of) the offer is activated (demandSchedule.scheduledEnergy is not zero)? “Rejection of the offer” cannot be due to too small quantities or too high prices. The sending of offer can occur before the need for adaptation (request for adaptation sent by BRP, DSO, … to VPS) and at the moment of sending the offer the limits (required quantities, acceptable prices for activation) posed by BRP, DSO are not known yet By: Jure Ratej, Etrel

DuneSe commented 2 years ago

Same question by Anaïs Walle, Trialog: What are the criteria for the acceptance of a FlexOffer? Can a partial FlexOffer be accepted and how to indicate it?

DuneSe commented 1 year ago

Acceptance of FlexOffer is only an acceptance of the full offer, respecting all constraints Acceptance is a business transaction, not an ICT validation of the message Acceptance means that the offer will be activated later on, with a schedule Enables to know what is available in advance and if the schedule will be modified or not

oliviergenest commented 1 year ago

Paragraph to be written (@DuneSe)

cerne739 commented 1 year ago

The acceptance confirms the logically correctness of the flex-offer. It does not confirm that FO will be activated later with the schedule. That is done later with the assignment message

DuneSe commented 1 year ago

Paragraph proposal: "An offer acceptance confirms the logically correctness of the flex-offer, respecting all constraints, and indicated that the offer may be assigned at a latter point in time." Penalities for not activating an accepted offer are described in the long-term contract signed (not part of FlexOffer) To be discussed again between Torben and Gregor

aau-daisy commented 1 year ago

Paragraph proposal: "An offer acceptance confirms the logically correctness of the flex-offer, respecting all constraints, and indicated that the offer may be assigned at a latter point in time." Penalities for not activating an accepted offer are described in the long-term contract signed (not part of FlexOffer) To be discussed again between Torben and Gregor

It's true, that in most cases acceptance is primarily for FlexOffer correctness check/validation. However, these are some other cases of FlexOffer acceptance:

  1. It can be used for long-term asset reservation: e.g., an asset owner may get acceptance from the aggregator 24h hours prior to operation to reserve an asset (or not to reserve - in the case of rejection) . After an asset is reserved, assignment can potentially arrive much later, say 1 hour before the operation.
  2. It can be used in "multi-aggregator setups", where aggregators can decide to accept or reject FlexOffers according to their momentary needs - respectively with or or without FlexOffer scheduling commitments;

In general, the acceptance of a FlexOffer only signifies that the Acquirer of the FlexOffer is going to make use of it at some point in time within the time flexibility offered. The actual assignment may be postponed to a later point in time.

DuneSe commented 1 year ago

(optional state) Depending on the use-case, there will be some business meaning to the acceptance state, defined in the contract