Start of metering point operation — MSBN view
Process flow from the perspective of the MSB (MSBN)
Process steps
Registration
MSBN NBCheck identifiers
- 44042 — Registration MSB · AS4
Flow
Prozessauslöser
START_BEGINN_MSBThe backend triggers this step with this event.
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 registration
MSBN NBZ33Check identifiers
Flow
Message from NB · AS4
Response per decision tree
44044,44043→ E_2002 · Check registration of metering point operation
APERAK checks
44044,44043→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
Load data for the check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
3 Information about preliminary registration confirmation
NB MSBA
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21007 — Status message · AS4
Notification of the overall transaction
MSBN NBFlow
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 notification of the overall transaction
MSBN NBZ33Flow
Message from NB · AS4
Response per decision tree
21011,21012→ E_2003 · Check notification on the overall transaction
APERAK checks
21011,21012→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
Load data for the check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
9 Information on failure of the assignment
NB MSBA
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21013 — Status message · AS4
Notification of the failure of the overall transaction
MSBN NBZ10Z17Z18Check identifiers
- 21013 — Status message · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
21013→Z1021013→Z1721013→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
11 Information on failure of the assignment
NB MSBA
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21013 — Status message · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_2002 | Check registration of metering point operation |
| E_2003 | Check notification on the overall transaction |
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. The numbers are those of the source; where one is missing, it is missing there.
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.
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.