Restoration of grid connection use at start of supply — View MSB
Process flow from the perspective of the MSB
Process steps
Information on the reconnection order
MSB NBZ10Z17Z18Check 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→Z1021040→Z1721040→Z18
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
Result of the reconnection order
MSB NBZ10Z17Z18Check identifiers
- 21039 — Order status (disconnect) · AS4
Flow
Message from NB · 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)
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
21039→Z1021039→Z1721039→Z18
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_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
NB sends “Information on the reconnection order” (step 1). 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.
- View NB — NB
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.
For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body.