Case 3: LF assignment for KWKG market location with DV obligation or non-EEG/non-KWKG market location and market location is mapped without tranches — NB view
The NB gives the LFN notice of contract termination in the case of
- for a EEG market location without DV obligation or KWKG market location without DV obligation, the assignment of the LFN (here: LF of the grid operator company) to the market location or tranche (residual quantity) (see case 1 of the SD).
- for a EEG market location with DV obligation, the assignment of the LFN (here: LF of the grid operator company) to the market location (see case 2 of the SD). In the case of a previously tranched market location, the NB ends the assignment of the LFA to the respective tranche due to the prohibition of pro rata assignment under § 38 EEG 2014 or under § 21 (1) no. 2 EEG 2017, 21b (2) sentence 2 EEG 2021 or EEG 2023.
- of a KWKG market location with DV obligation or non-EEG/non-KWKG market location after the bilateral clarification
- the assignment of the LFN to the market location (see case 3 of the SD) or
- the assignment of the LFN to the tranche (see case 4 of the SD). Case 4 of the SD must be carried out separately for each LFN for a tranche of the market location. In the course of the process, the NB ends the assignment of a LFA to a tranche where applicable. Note: after the bilateral clarification, the LFN can be the LF of the grid operator company.
Process flow from the perspective of the NB
Process steps
Announcement of the assignment of the LFN to the market location
NB LFNCheck identifiers
- 55607 — Announcement assignment / assignment of the LF to the MaLo/ tranche · AS4
Flow
Prozessauslöser
START_ZUORDNUNG_ERZ_MALO_TRANCHEThe backend triggers this step with this event.
Message to LFN · AS4
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Response to announcement of the assignment of the LFN to the market location
NB LFNZ33Check identifiers
Flow
Message from LFN · AS4
Response per decision tree
55608,55609→ E_0605 · LF · Check assignment
APERAK checks
55608,55609→Z33
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
Assignment of the LFN to the market location due to a missing response
NB LFNCheck identifiers
- 55607 — Announcement assignment / assignment of the LF to the MaLo/ tranche · AS4
Flow
Prozessauslöser
START_ZUORDNUNG_ERZ_MALO_TRANCHEThe backend triggers this step with this event.
Message to LFN · AS4
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Termination of the assignment of the LFA to the tranche
NB LFA5500155011Check identifiers
- 55037 — Termination of the assignment · AS4
Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages. In addition, the backend can trigger this step with an event — the next item.
Prozessauslöser
START_ENDE_ZUORDNUNGThe backend triggers this step with this event.
Message to LFA · AS4
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Decision trees of this process
| EBD | Name |
|---|---|
| E_0605 | Check assignment |
Process information
Wording of the consolidated version, profile ch. 2.4.2.1, pp. 38–40.
Preconditions
- This is a generating market location or a tranche.
- The energy of a market location that is to be assigned in full or in part to the marketing type of a DV must be measured with a quarter-hourly resolution.
- An allocation authorization according to the processes of MaBiS for the BK used by LFN is available to NB.
Results
- The NB sends the calculation formula to the LFN.
- The NB executes the use case „Billing data balancing group settlement“.
- The NB carries out the use case „Master data change“ (here: SD „Master data change initiated by the NB (responsible)“) (GPKE part 4).
- The NB executes the use case „Set-up of the configurations due to an assignment of a LF to a market location or tranche“ (GPKE part 3).
- The LF carries out the use case „Master data change“ (here: SD „Master data change initiated by the LF (responsible)“) (GPKE part 4).
Error case
Result in the error case
- The NB must ensure that the energy generated by the market location is assigned to a BK, or
- the NB has to carry out the interruption of grid connection use at the market location.
- The LFN has not been assigned to the market location or tranche. In the case of a tranched market location, not every tranche is assigned to a LF.
Error cases
- This is a consuming market location.
- The energy of a market location that is to be assigned in full or in part to the marketing type of a DV cannot be measured with a quarter-hourly resolution.
- An allocation authorization according to the processes of MaBiS for the BK used by LFN is not available to NB.
Further requirements
- For a KWKG market location subject to DV obligation or a non-EEG/non-KWKG market location, the interruption of grid connection use at the market location by the NB may also be considered as part of the bilateral clarification. The NB is under no obligation to take commercial delivery of the electrical energy.
- If LFZ are assigned to the market location or tranche, the following applies: The allocation end of LFN is determined by the allocation start of the LFZ whose allocation start is closest in time to the allocation start of LFN and whose share (here: 1 to 100 %) of the energy quantity of the generating market location is affected by the share of LFN. In this case the allocation end of LFN corresponds to the allocation start of this LFZ.
Trigger
- For a EEG market location without DV obligation, a KWKG market location without DV obligation or a EEG market location subject to DV obligation, the following applies:
- No LF is assigned to the non-tranched market location, or
- the tranches of a market location are in total not assigned exactly 100% to LF.
- For a KWKG market location subject to DV obligation or a non-EEG/non-KWKG market location, the following applies:
- No LF is assigned to the non-tranched market location, or
- the tranches of a market location are in total not assigned exactly 100% to LF and the bilateral clarification between the NB and the EZ shows that the NB
- maps the (tranched or non-tranched) market location as non-tranched or
- maps the (tranched or non-tranched) market location as tranched. Reasons may in particular be:
- Termination of the assignment of the LF to the market location or tranche due to
- Deregistration of the assignment of the LF to the market location or tranche due to termination of the electricity purchase agreement; without subsequent supply
- Information about the contract termination of the balancing group contract carried out by ÜNB
- Expiry of the allocation authorization granted by BKV to LF
- changed time series type and no valid allocation authorization for the new time series type
- initial commissioning of a market location (creation)
- For a EEG market location without DV obligation, a KWKG market location without DV obligation or a EEG market location subject to DV obligation, the following applies:
First message
The party involved on this page is itself the sender of: „Announcement of the assignment of the LFN to the market location“ to LFN (step 1).
Objective
The LFN is assigned to the market location or tranche. In the case of a market location divided into tranches, each tranche is assigned to a LF.
Other views of the process
The same process through the eyes of the other parties involved: the same steps, each read from their point of view.
- View LFA — the transferring supplier · market role LF
- View LFN — the receiving supplier · market role LF
Notes on this page
The steps are the possible messages of this process, not a sequence — the source lists neither conditions nor alternatives. The small box on the step names the own view on the left: with ← it receives, with → it sends. Collapsed steps run between other market partners. The numbers are those of the source; where one is missing, it is missing there.