End of metering point operation from the MSB to the NB — MSBA view
Process flow from the perspective of the MSB (MSBA)
Process steps
Deregistration
MSBA NBCheck identifiers
- 44051 — End of MSB · AS4
Flow
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 deregistration
MSBA NBZ33Flow
Message from NB · AS4
Response per decision tree
44053,44052→ E_2005 · Check deregistration of metering point operation
APERAK checks
44053,44052→Z33
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 Commitment request
NB gMSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 44168 — Commitment request / demand · AS4
Continued commitment of the MSB
MSBA NBZ10Z17Z18Check identifiers
- 17002 — Continued commitment · AS4
Flow
Message from NB · AS4
APERAK checks
17002→Z1017002→Z1717002→Z18
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
Response to continued commitment
MSBA NBCheck identifiers
Flow
Message to NB · AS4
Response per decision tree
19003,19004→ E_2004 · Check continued commitment
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
7 Request to take over the metering location by the gMSB
NB gMSB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 44168 — Commitment request / demand · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_2004 | Check continued commitment |
| E_2005 | Check deregistration of metering point operation |
| E_2006 | Check continued commitment |
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 source does not yet name the event that triggers these steps.
Applies to: 1
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.
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.