Start of supply (GPKE Teil 2)
Start of supply — LFA view
LFA · Market role LFGPKE Teil 2 · 2.1.2Strom8 steps
A LFN registers an assignment of the LFN to a market location or tranche with the NB. In the course of the process
- the NB terminates, where applicable, the assignment of the LFA to the market location or tranche.
- the NB cancels, where applicable, the assignment of the LFZ to the market location or tranche.
Process flow from the perspective of the LF (LFA)
Process steps
2 Information about existing assignment
NB LFN
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55036 — Existing assignment · AS4
Request for termination of the assignment of the LFA to the market location or tranche
LFA NBBackend
MACO APP · LFA
Market partner
Receive message “55010 — Request for termination of the assignment”
AS455010
NB
BackendRead market locationRead tranche
API
Load data for the incoming check
APERAK check
Z10Z44Create process data
API
Create transaction
BackendRead energy supply contractRead market locationRead grid usage contract
API
Load data for the check
Decision tree
E_0624 Check request for termination of the assignmentBackendRead energy supply contractRead grid usage contract
API
Load data for processing
Trigger follow-up process
5501155012Check identifiers
- 55010 — Request for termination of the assignment · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read tranche
GET /getTrancheBasic
- Read market location
APERAK checks
55010→Z10— APERAK check: Is location known ?55010→Z44— APERAK check: Does object property match?
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
Load data for the check
- Read energy supply contract
GET /getEnergySupplyContractBasic - Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read energy supply contract
Decision tree
55010→ E_0624 — Check request for termination of the assignment
Load data for processing
- Read energy supply contract
GET /getEnergySupplyContractBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read energy supply contract
Trigger follow-up process
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response to request for termination of the assignment of the LFA to the market location or tranche
LFA NBBackend
MACO APP · LFA
Market partner
Triggered by incoming message
55010BackendRead balancingRead market locationRead grid usage contract
API
Load data for processing
Send one of these messages55011 — Confirmation of termination of the assignment55012 — Rejection of termination of the assignment
AS455011, 55012
NB
Update process data
API
Update transaction
Check identifiers
Flow
Triggered by incoming message
- 55010 — Request for termination of the assignment
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read balancing
GET /getAccountingBasic - Read market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read balancing
Message to NB · AS4
Response per decision tree
55011,55012→ E_0624 · LF · Check request for termination of the assignment
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
6 Rejection of the registration of an assignment of the LFN to the market location or tranche
NB LFN
This step runs between other market partners and is not relevant for this view.
Check identifiers
Termination of the assignment of the LFA to the market location or tranche
LFA NBBackend
MACO APP · LFA
Market partner
Receive message “55037 — Termination of the assignment”
AS455037
NB
BackendRead market locationRead tranche
API
Load data for the incoming check
APERAK check
Z10Z44Create process data
API
Create transaction
Update process data
APItransaktionsgrundergaenzung = ZW4
Update transaction
Create process data
APItransaktionsgrundergaenzung = ZW3
Create transaction
Check identifiers
- 55037 — Termination of the assignment · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read tranche
GET /getTrancheBasic
- Read market location
APERAK checks
55037→Z10— APERAK check: Is location known ?55037→Z44— APERAK check: Does object property match?
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
transaktionsgrundergaenzung = ZW4→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Write endpoint
transaktionsgrundergaenzung = ZW3→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
13 Cancellation of the assignment of the LFZ to the market location or tranche
NB LFZ
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55038 — Cancellation of a fut. assignment · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_0624 | Check request for termination of the assignment |
| E_0622 | Check whether the registration can be rejected directly |
| E_0623 | Check start of supply |
Process information
Wording of the consolidated version, profile ch. 2.1.1, pp. 12–15.
Preconditions
- In the case of a consuming market location:
- Conclusion of an energy supply contract between LFN and the final customer.
- In the case of a generating market location or a tranche:
- Conclusion of an electricity purchase agreement between LFN and the EZ. Three business transactions are considered here:
- Business transaction 1: LFN is fully assigned to a market location (complete (100%) assignment). This business transaction is also to be applied for the change from a tranched market location to a non-tranched market location.
- Business transaction 2: LFN is fully assigned to an existing tranche (complete (100%) assignment). This business transaction is to be applied in the case of a direct transition, i.e. a seamless allocation end and allocation start and while retaining the tranche.
- Business transaction 3: LFN is assigned to a tranche to be newly formed (partial assignment procedure with formation of new tranches). In addition, a change of the tranche size assigned to LF must be reported with this process/business transaction 3.
- The previous and the new EZ must be identical.
- 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.
- The use case is not to be started by the grid operator company in its role as LF.
- Conclusion of an electricity purchase agreement between LFN and the EZ. Three business transactions are considered here:
- An allocation authorization according to the processes of MaBiS for the BK used by LFN is available to NB.
- This is not the initial commissioning of a market location (creation).
- The MaLo-ID of the market location is known or, in business transaction 2, the MaLo-ID of the tranche is known.
- In the case of a consuming market location:
Results
- In the case of a consuming market location:
- The NB executes the use cases „Billing data grid usage settlement“ and „Billing data balancing group settlement“.
- Any allocation gaps that arise are closed by NB by assigning the E/G to the market location, applying the use case „Start of the replacement supply / default supply“.
- If the market location is disconnected, NB carries out the use case “Restoration of grid connection use at start of supply”.
- In the case of a generating market location or a tranche:
- The NB executes the use case „Billing data balancing group settlement“.
- Any allocation gaps that arise are closed by NB within the use case „Establishing a 100% LF assignment to a generating market location“.
- 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 sends the calculation formula to the LFN.
- 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 LFN carries out the use case „Master data change“ (here: SD „Master data change initiated by the LF (responsible)“) (GPKE part 4).
- In the case of a consuming market location:
Error case
Result in the error case
- The LFN has not been assigned to the market location or tranche.
- The LFA remains assigned to the market location or tranche, provided that its assignment has not already been ended as part of another use case (e.g. „End of supply from LF to NB).
- In the case of a consuming market location: NB carries out the use case “Start of replacement supply / default supply” if necessary.
- In the case of a generating market location or a tranche: NB carries out the use case “Establishing a 100% LF assignment to a generating market location” if necessary.
- If required, the LFN sends a registration to the NB again.
Error cases
- This is the initial commissioning of a market location (creation).
- In the case of a generating market location or a tranche:
- The previous and the new EZ are not identical.
- 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.
- The use case is started by the grid operator company in its role as LF.
- An allocation authorization according to the processes of MaBiS for the BK used by LFN is not available to NB.
Further requirements
- Gaps in assignment must be avoided by coordinating registration and deregistration in time.
- Note: A change of generator at a generating market location or a change of plant operator at a technical resource is not handled within the processes described here. Their bilateral handling between NB and EZ takes place in accordance with the relevant provisions of NB.
- Note: The assignment of LF to the market location or tranche when a market location is commissioned (creation) takes place via the use case “Creation”, “Start of replacement supply / default supply” or “Establishing a 100% LF assignment to a generating market location”.
- Note: If the device technology available at the allocation start does not permit the registration, a corresponding change of the device technology must be arranged by LFN, the final customer or the EZ with MSB. LFN can commission the change of the device technology via the WiM use case for the metering location change (WiM Part 1).
- Note on generating market locations and on tranches: for a change of the marketing type (without a simultaneous assignment of LF to the generating market location or to the tranche), LF applies the use case "Order placement of a change of billing data".
Trigger
- In the case of a consuming market location:
- Supplier switch without simultaneous move-in of the final customer
- Supplier switch with simultaneous move-in of the final customer
- Assignment of the previous LF without simultaneous move-in of the final consumer (after a termination of the assignment of LF to the market location, e.g. due to the use case "End of supply from LF to NB")
- Assignment of the previous LF with simultaneous move-in of the final consumer.
- In the case of a generating market location or a tranche:
- Supplier switch without change of generator
- Assignment of the previous LF without a change of producer (after a termination of the assignment of LF to the market location or tranche, e.g. due to the use case "End of supply from LF to NB").
Runs beforehand: Billing data for grid usage settlement, Determination of the MaLo ID of the market location, Creation — these processes name the one shown here in their result.
- In the case of a consuming market location:
First message
NB sends “Request to end the assignment of the LFA to the market location or tranche” (step 3). From here on, the party involved on this page has the next move.
Objective
The LFN is assigned to the market location or tranche.
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 LFN — the receiving supplier · market role LF
- View LFZ — future supplier · market role LF
- View NB — NB
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.