Cancellation of the interruption and restoration of grid connection use at the instruction of LF — View NB
Process flow from the perspective of the NB
Process steps
Cancellation
NB LFZ33E_1006 Check cancellation (Based on electricity EBD: E_0468_Check cancellation)191281912939001Check identifiers
- 39000 — Cancellation of disconnection/reconnection order · AS4
Flow
Message from LF · AS4
APERAK checks
39000→Z33
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
Load data for the check
- Read market location
GET /getMarketLocationBasic
- Read market location
Decision tree
39000→ E_1006 — Check cancellation (Based on electricity EBD: E_0468_Check cancellation)
Trigger follow-up process
- 19128 — Confirmation of cancellation of disconnection/reconnection order
- 19129 — Rejection of cancellation of disconnection/reconnection order
- 39001 — Forwarding of the cancellation
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response to cancellation
NB LF39000Check identifiers
Flow
Triggered by incoming message
- 39000 — Cancellation of disconnection/reconnection order
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to LF · AS4
Response per decision tree
19128,19129→ E_1006 · NB · Check cancellation (Based on electricity EBD: E_0468_Check cancellation)
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
Forwarding of the cancellation
NB MSB39000Check identifiers
- 39001 — Forwarding of the cancellation · AS4
Flow
Triggered by incoming message
- 39000 — Cancellation of disconnection/reconnection order
The MACO APP sends this message itself, as a follow-up process after this incoming message.
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_1006 | Check cancellation (Based on electricity EBD: E_0468_Check cancellation) |
Process information
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 process begins for the own role with their message, so the transaction is created.
Applies to: 1