End of metering point operation from the MSB to the NB — NB view
Process flow from the perspective of the NB
Process steps
Deregistration
NB MSBACheck identifiers
- 44051 — End of MSB · AS4
Flow
Message from MSBA · 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
Response to deregistration
NB MSBAFlow
Message to MSBA · AS4
Response per decision tree
44053,44052→E_2005
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
Commitment request
NB gMSBCheck identifiers
- 44168 — Commitment request / demand · AS4
Flow
Load data for processing
- Read metering point operation contract
GET /getMeasuringPointOperationContractBasic - Read meter
GET /getCounterBasic
- Read metering point operation contract
Message to gMSB · 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 commitment request
NB gMSBCheck identifiers
- 44169 — Confirmation commitment request · AS4
Flow
Message from gMSB · AS4
Response per decision tree
44169→E_2006
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
Continued commitment of the MSB
NB MSBA55170Check identifiers
- 17002 — Continued commitment · 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
Response to continued commitment
NB MSBACheck identifiers
Flow
Message from MSBA · AS4
Response per decision tree
19003,19004→E_2004
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
Request to take over the metering location by the gMSB
NB gMSBCheck identifiers
- 44168 — Commitment request / demand · AS4
Flow
Load data for processing
- Read metering point operation contract
GET /getMeasuringPointOperationContractBasic - Read meter
GET /getCounterBasic
- Read metering point operation contract
Message to gMSB · 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.
- View GMSB — default metering point operator · market role MSB
- View MSBA — the transferring MSB · market role MSB
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 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.
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.
For these decision trees of the process there is no source in this format version:
E_2004E_2005E_2006