Start of metering point operation — NB view
Process flow from the perspective of the NB
Process steps
Registration
NB MSBNZ14Z15Z16Check identifiers
- 44042 — Registration MSB · AS4
Flow
Message from MSBN · AS4
APERAK checks
44042→Z1444042→Z1544042→Z16
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
Response to registration
NB MSBNCheck identifiers
Flow
Message to MSBN · AS4
Response per decision tree
44044,44043→ E_2002 · Check registration of metering point operation
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
Information about preliminary registration confirmation
NB MSBA55042Check identifiers
- 21007 — Status message · AS4
Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to MSBA · 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
Notification of the overall transaction
NB MSBNZ10Z16Z17Z18Flow
Message from MSBN · AS4
APERAK checks
21009,21010→Z1021009,21010→Z1621009,21010→Z1721009,21010→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 notification of the overall transaction
NB MSBNFlow
Message to MSBN · AS4
Response per decision tree
21011,21012→ E_2003 · Check notification on the overall transaction
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
Information on failure of the assignment
NB MSBACheck identifiers
- 21013 — Status message · AS4
Flow
Message to MSBA · 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
Notification of the failure of the overall transaction
NB MSBNCheck identifiers
- 21013 — Status message · AS4
Flow
Message to MSBN · 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
Information on failure of the assignment
NB MSBACheck identifiers
- 21013 — Status message · AS4
Flow
Message to MSBA · 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_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.
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
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.
Applies to: 6
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.