Restoration of grid connection use (reconnect) at the instruction of LF — View LF
Process flow from the perspective of the LF
Process steps
Reconnection order
LF NBCheck identifiers
- 17117 — Reconnection order · AS4
Flow
Prozessauslöser
START_ENTSPERRAUFTRAGThe backend triggers this step with this event.
Message to NB · 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
Response to reconnection order
LF NBZ33Check identifiers
Flow
Message from NB · AS4
Response per decision tree
19116,19117→ E_1004 · NB · Check reconnection order (Based on electricity EBD: E_0497_Check reconnection order)
APERAK checks
19116,19117→Z33— APERAK check: Is referenced message known ?
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
3 Information on the reconnection order
NB MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21040 — Reconnection order info · AS4
Result of the reconnection order
LF NBZ10Z17Z18Check 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
APERAK checks
21039→Z10— APERAK check: Is location known ?21039→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
5 Result of the reconnection order
NB MSB
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)
Decision trees of this process
| EBD | Name |
|---|---|
| E_1004 | Check reconnection order (Based on electricity EBD: E_0497_Check reconnection order) |
| E_1005 | Check whether the reconnection order was successful (Based on electricity EBD: E_0499_Check whether the reconnection order was successful) |
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
The party involved on this page is itself the sender of: „Reconnection order“ to NB (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.
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.
The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists.
Applies to: 2
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.
Applies to: 4