Obligation gMSB — View NB
Process flow from the perspective of the NB
Process steps
Confirmation of the takeover of metering point operation
NB gMSBZ33Z10Z16Z17Z18Check identifiers
- 44169 — Confirmation commitment request · AS4
Flow
Message from gMSB · AS4
APERAK checks
44169→Z3344169→Z1044169→Z1644169→Z1744169→Z18
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
Information on reassignment
NB gMSBCheck identifiers
- 44112 — Non-bal.rel. change from NB · AS4
Flow
Message from gMSB · AS4
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
Process information
Trigger
Runs beforehand: End of metering point operation — these processes name the one shown here in their result.
First message
gMSB sends “Confirmation of the takeover of metering point operation” (step 3). From here on, it is the turn of the party involved on this page.
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
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: 3
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: 4
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: 3