Interruption of grid connection use (disconnect) at the instruction of LF — View LF
Process flow from the perspective of the LF
Process steps
Disconnection order
LF NBSTART_ANFRAGE_SPERRUNGSTART_SPERRAUFTRAGCheck identifiers
- 17115 — Disconnection order · AS4
Flow
Process trigger
The backend triggers this step with one of these events.
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 disconnection order
LF NBZ33Check identifiers
Flow
Message from NB · AS4
Response per decision tree
19116,19117→ E_1000 · NB · Check disconnection order (Based on electricity EBD: E_0470_Check disconnection 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 Request
NB MSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 17116 — Request disconnection · AS4
4 Response to request
MSB NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
Response per decision tree
19118,19119→ E_1001 · MSB · Check request (Based on electricity EBD: E_0488_Check request)
Result of the disconnection order
LF NBZ10Check identifiers
- 21039 — Order status (disconnect) · AS4
Flow
Message from NB · AS4
Response per decision tree
21039→ E_1002 · NB · Check rejection, perform clearing if necessary (Based on electricity EBD: E_0501_Check rejection, perform clearing if necessary)21039→ E_1003 · NB · Check whether the disconnection order was successful (Based on electricity EBD: E_0472_Check whether the disconnection 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 ?
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
6 Result of the disconnection 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_1003 · NB · Check whether the disconnection order was successful (Based on electricity EBD: E_0472_Check whether the disconnection order was successful)
Decision trees of this process
| EBD | Name |
|---|---|
| E_1000 | Check disconnection order (Based on electricity EBD: E_0470_Check disconnection order) |
| E_1002 | Check rejection, perform clearing if necessary (Based on electricity EBD: E_0501_Check rejection, perform clearing if necessary) |
| E_1003 | Check whether the disconnection order was successful (Based on electricity EBD: E_0472_Check whether the disconnection order was successful) |
| E_1001 | Check request (Based on electricity EBD: E_0488_Check request) |
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: „Disconnection 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