Restoration of grid connection use (reconnect) at the instruction of LF — View MSB
Process flow from the perspective of the MSB
Process steps
1 Reconnection order
LF NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 17117 — Reconnection order · AS4
2 Response to reconnection order
NB LF
This step runs between other market partners and is not relevant for this view.
Check identifiers
Response per decision tree
19116,19117→ E_1004 · NB · Check reconnection order (Based on electricity EBD: E_0497_Check reconnection order)
Information on the reconnection order
MSB NBZ10Check identifiers
- 21040 — Reconnection order info · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
21040→Z10
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
4 Result of the reconnection order
NB LF
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21039 — Order status (disconnect) · AS4
Response per decision tree
21039→ E_1005 · NB · Check whether the reconnection order was successful (Based on electricity EBD: E_0499_Check whether the reconnection order was successful)
Result of the reconnection order
MSB NBCheck identifiers
- 21039 — Order status (disconnect) · AS4
Flow
Message from NB · AS4
Response per decision tree
21039→ E_1005 · NB · Check whether the reconnection order was successful (Based on electricity EBD: E_0499_Check whether the reconnection order was successful)
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_1005 | Check whether the reconnection order was successful (Based on electricity EBD: E_0499_Check whether the reconnection order was successful) |
| E_1004 | Check reconnection order (Based on electricity EBD: E_0497_Check reconnection order) |
Process information
Trigger
Runs beforehand: Cancellation of the interruption and restoration of grid connection use on the instruction of the LF — these processes name the one shown here in their result.
First message
NB sends “Information on the reconnection order” (step 3). From here on, it is the turn of the party involved on this page.
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.
Notes on this page
The source provides no use case profile for this process — objective, precondition and result are not recorded there.
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.
Step sequence reconstructed
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.