End of metering point operation — GMSB view
The use case describes the interactions between the market participants on the occasion of a termination of metering point operation to be initiated by the MSB. The process is also to be applied when a single metering location is decommissioned by a wMSB and gMSB. The NB must ensure uninterrupted metering by involving the gMSB in good time.
Process flow from the perspective of the MSB (GMSB)
Process steps
1 Deregistration
MSB (corresponds to MSBA at the metering location object) NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55051 — End MSB · AS4
Commitment request
MSB (corresponds to gMSB at the metering location object) NBZ10Z17Z18S_0064 Rejection of commitment requestS_0063 Confirmation of commitment request5516955170Check identifiers
- 55168 — Commitment request / demand · AS4
Flow
Message from NB · AS4
APERAK checks
55168→Z1055168→Z1755168→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
Decision tree
55168→S_0064— Rejection of commitment request55168→S_0063— Confirmation of commitment request
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 commitment request
MSB (corresponds to gMSB at the metering location object) NB55168Check identifiers
Flow
Triggered by incoming message
- 55168 — Commitment request / demand
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to NB · AS4
Response per decision tree
55169,55170→ E_0240 · Check commitment request
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
5 Continued commitment of the MSB
NB MSB (corresponds to MSBA at the metering location object)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 17002 — Continued commitment · AS4
Request to take over the individual metering location by the gMSB
MSB (corresponds to gMSB at the metering location object) NBZ10Z17Z18S_0064 Rejection of commitment requestS_0063 Confirmation of commitment request5516955170Check identifiers
- 55168 — Commitment request / demand · AS4
Flow
Message from NB · AS4
APERAK checks
55168→Z1055168→Z1755168→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
Decision tree
55168→S_0064— Rejection of commitment request55168→S_0063— Confirmation of commitment request
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.
Decision trees of this process
| EBD | Name |
|---|---|
| E_0240 | Check commitment request |
| E_0202 | Check deregistration of metering point operation |
| E_0203 | Check continued commitment |
Process information
Wording of the consolidated version, profile ch. 2.4.1, p. 30.
Preconditions
Termination of a MSB contract
Results
- The NB can distribute the master data changed as a result at the metering or market location of a location bundle to the authorised parties (e.g. the wMSB is in a continued commitment), or
- the gMSB can serve the use case „Obligation gMSB“.
Error case
Error cases
The metering location was not assigned to the MSB.
Trigger
Runs beforehand: Contract termination of metering point operation — these processes name the one shown here in their result.
First message
NB sends “Commitment request” (step 3). From here on, it is the turn of the party involved on this page.
Objective
The MSB is no longer assigned to a metering location or has been obliged to continue performing metering point operation.
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 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.