Restoration of grid connection use at start of supply — View NB
Process flow from the perspective of the NB
Process steps
Information on the reconnection order
NB MSBSTART_AUFTRAGSSTATUSSTART_WIEDERHERST_LBCheck identifiers
- 21040 — Reconnection order info · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_STATUSMITTEILUNG_BASIS
- Read market location
Message to MSB · 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
Result of the reconnection order
NB MSBSTART_AUFTRAGSSTATUSSTART_WIEDERHERST_LBCheck identifiers
- 21039 — Order status (disconnect) · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
Load data for processing
- Read market location
GET /getMarketLocationBasic LESEN_STATUSMITTEILUNG_BASIS
- Read market location
Message to MSB · AS4
Response per decision tree
21039→ E_1020 · NB · Check whether the reconnection order was successful (Based on electricity EBD: E_0487_Check whether the reconnection order was successful)
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_1020 | Check whether the reconnection order was successful (Based on electricity EBD: E_0487_Check whether the reconnection order was successful) |
Process information
Trigger
Runs beforehand: Start of supply — these processes name the one shown here in their result.
First message
The party involved on this page is itself the sender of: „Information on reconnection order“ to MSB (step 1).
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 MSB — MSB
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.
These read accesses are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button.