Fault rectification at the metering location — View LF
Process flow from the perspective of the LF
Process steps
Notification of a fault
LF MSBCheck identifiers
- 23001 — Fault notification
Flow
Prozessauslöser
START_VERSAND_STOERUNGSMELDUNGThe backend triggers this step with this event.
Message to MSB
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
LF MSBFlow
Message from MSB
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 about fault at metering location
MSB NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 23005 — Information notification
Result notification
LF MSBCheck identifiers
- 23008 — Result report
Flow
Message from MSB
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
5 Information notification on rectification
MSB NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 23009 — Information notification
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 own role was already involved in this process, so the transaction already exists.