Interruption of grid connection use (disconnect) at the instruction of LF — View MSB
Process flow from the perspective of the MSB
Process steps
1 Disconnection order
LF NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 17115 — Disconnection order · AS4
2 Response to disconnection order
NB LF
This step runs between other market partners and is not relevant for this view.
Check identifiers
Response per decision tree
19116,19117→ E_1000 · NB · Check disconnection order (Based on electricity EBD: E_0470_Check disconnection order)
Request
MSB NBZ10E_1001 Check request (Based on electricity EBD: E_0488_Check request)1911819119Check identifiers
- 17116 — Request disconnection · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
APERAK checks
17116→Z10
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 tree
17116→ E_1001 — Check request (Based on electricity EBD: E_0488_Check request)
Trigger follow-up process
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response to request
MSB NB17116Check identifiers
Flow
Triggered by incoming message
- 17116 — Request disconnection
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
LESEN_ANFRAGE_BASISLESEN_AUFTRAG_BASIS
Message to NB · AS4
Response per decision tree
19118,19119→ E_1001 · MSB · Check request (Based on electricity EBD: E_0488_Check request)
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
5 Result of the disconnection order
NB LF
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_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)
Result of the disconnection order
MSB NBCheck identifiers
- 21039 — Order status (disconnect) · AS4
Flow
Message from NB · 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)
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic
- Read market location
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_1001 | Check request (Based on electricity EBD: E_0488_Check request) |
| E_1003 | Check whether the disconnection order was successful (Based on electricity EBD: E_0472_Check whether the disconnection order was successful) |
| 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) |
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
NB sends “Request” (step 3). 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.
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.
Applies to: 4