Start of metering point operation — NB view
Process flow from the perspective of the NB
Process steps
Registration
NB MSBNG_0053_G_0054 Registration MSB210074404344044Check identifiers
- 44042 — Registration MSB · AS4
Flow
Message from MSBN · AS4
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
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 market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic
- Read market location
Decision tree
44042→G_0053_G_0054— Registration MSB
Trigger follow-up process
- 21007 — Status message
- 44043 — Confirmation of registration MSB
- 44044 — Rejection of registration MSB
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Response to registration
NB MSBN44042Check identifiers
Flow
Triggered by incoming message
- 44042 — Registration MSB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read metering location
GET /getMeterLocationBasic - Read balancing
GET /getAccountingBasic - Read location bundle
GET /getLocationBundleBasic - Read market location
GET /getMarketLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic - Read meter
GET /getCounterBasic
- Read metering location
Message to MSBN · AS4
Response per decision tree
44044,44043→E_2002
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 MSBA44042Check identifiers
- 21007 — Status message · AS4
Flow
Triggered by incoming message
- 44042 — Registration MSB
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 MSBNG_0055 Check notification on the overall transaction2101121012210132101544112Flow
Message from MSBN · AS4
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
Load data for the check
- Read market location
GET /getMarketLocationBasic
- Read market location
Decision tree
21009→G_0055— Check notification of the overall transaction
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 notification of the overall transaction
NB MSBN2100921010Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Load data for processing
- Read metering location
GET /getMeterLocationBasic
- Read metering location
Message to MSBN · AS4
Response per decision tree
21011,21012→E_2003
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 MSBA21009Check identifiers
- 21013 — Status message · AS4
Flow
Triggered by incoming message
- 21009 — Status 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 failure of the overall transaction
NB MSBN21009Check identifiers
- 21013 — Status message · AS4
Flow
Triggered by incoming message
- 21009 — Status message
The MACO APP sends this message itself, as a follow-up process after this incoming message.
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 MSBA21009Check identifiers
- 21013 — Status message · AS4
Flow
Triggered by incoming message
- 21009 — Status 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
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.
Applies to: 1
For these decision trees of the process there is no source in this format version:
E_2002E_2003