Start of replacement supply / default supply — LF view
The NB announces the assignment of the E/G to the market location to the E/G.
Process flow from the perspective of the LF
Process steps
Announcement of the assignment of the E/G to the market location
LF (note “corresponds to E/G”) NBZ33E_0615 Check registration E/G5501455015Check identifiers
- 55013 — Registration / assignment EOG · AS4
Flow
Message from NB · AS4
APERAK checks
55013→Z33— APERAK check: Is referenced message known ?
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 market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read market location
Decision tree
55013→ E_0615 — Check registration E/G
Load data for processing
- Read energy supply contract
GET /getEnergySupplyContractBasic - Read location bundle
GET /getLocationBundleBasic - Read metering location
GET /getMeterLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic - Read grid location
GET /getGridLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic - Read meter
GET /getCounterBasic
- 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 announcement of the assignment of the E/G to the market location
LF (note “corresponds to E/G”) NB55013Check identifiers
Flow
Triggered by incoming message
- 55013 — Registration / assignment EOG
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to NB · AS4
Response per decision tree
55014,55015→ E_0615 · LF · Check registration E/G
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
Assignment of the E/G to the market location due to a missing response
LF (note “corresponds to E/G”) NBZ33E_0615 Check registration E/G5501455015Check identifiers
- 55013 — Registration / assignment EOG · AS4
Flow
Message from NB · AS4
APERAK checks
55013→Z33— APERAK check: Is referenced message known ?
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 market location
GET /getMarketLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic
- Read market location
Decision tree
55013→ E_0615 — Check registration E/G
Load data for processing
- Read energy supply contract
GET /getEnergySupplyContractBasic - Read location bundle
GET /getLocationBundleBasic - Read metering location
GET /getMeterLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic - Read grid location
GET /getGridLocationBasic - Read grid usage contract
GET /getGridUsageContractBasic - Read meter
GET /getCounterBasic
- 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.
Decision trees of this process
| EBD | Name |
|---|---|
| E_0615 | Check registration E/G |
Process information
Wording of the consolidated version, profile ch. 2.3.2.1, pp. 33–34.
Preconditions
- This is a consuming market location.
- A statutory substitute supply obligation exists for the market location or
- there is a statutory basic supply obligation for the market location.
- An allocation authorization according to the processes of MaBiS for the BK used by the E/G is available to NB.
Results
- The NB sends the calculation formula to the E/G.
- The NB executes the use cases „Billing data grid usage settlement“ and „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 E/G has not been assigned to the market location:
- The NB must ensure that the energy withdrawn from 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. •
Error cases
- This is a generating market location or a tranche.
Further requirements
- If NB has recorded an allocation end of a LF which is followed by an allocation start of a LF, where the allocation end and the allocation start are not congruent, the gap between the allocation end and the allocation start must be closed by a temporary assignment of the E/G to the market location. This may result, for example, from sending a „Request for the termination of the assignment of LFA to the market location or tranche“ within the use case „Start of supply“.
- Note: The switch from substitute supply to basic supply takes place automatically after three months, provided the E/G is still assigned to the market location at that point in time. Whether the customer is in substitute supply or basic supply is not information relevant to a master data change, so the switch from substitute supply to basic supply does not result in a master data change from the E/G to NB.
- Note: the E/G can terminate the basic supply relationship or the substitute supply relationship by means of the use case „End of supply from LF to NB“.
- This process applies accordingly to cases of contractually agreed replacement delivery or contractually agreed continuation of the substitute supply (subsequent substitute supply).
Trigger
- No LF is assigned to the market location. Reasons may in particular be:
- Termination of the assignment of the LF to the market location due to
- Deregistration of the assignment of the LF to the market location due to termination of the energy supply contract; without subsequent supply
- Contract termination of the supplier framework contract
- 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)
Runs beforehand: Billing data for grid usage settlement, Start of supply, End of supply from LF to NB, End of supply from NB to LF, Creation — these processes name the one shown here in their result.
First message
NB sends “Announcement of the assignment of the E/G to the market location” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The LF (hereinafter referred to as E/G) is assigned to the market location.
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 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.