End of metering point operation — MSBA 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 (MSBA)
Process steps
Deregistration
MSB (corresponds to MSBA at the metering location object) NBCheck identifiers
- 55051 — End MSB · AS4
Flow
Prozessauslöser
START_ENDE_MSBThe backend triggers this step with this event.
Message to NB · 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 deregistration
MSB (corresponds to MSBA at the metering location object) NBFlow
Message from NB · AS4
Response per decision tree
55052,55053→ E_0202 · Check deregistration of metering point operation
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
3 Commitment request
NB MSB (corresponds to gMSB at the metering location object)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55168 — Commitment request / demand · AS4
Continued commitment of the MSB
MSB (corresponds to MSBA at the metering location object) NBCheck identifiers
- 17002 — Continued commitment · AS4
Flow
Message from NB · 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
Response to continued commitment
MSB (corresponds to MSBA at the metering location object) NBCheck identifiers
Flow
Message to NB · AS4
Response per decision tree
19003,19004→ E_0203 · Check continued commitment
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
7 Request to take over the individual metering location by the gMSB
NB MSB (corresponds to gMSB at the metering location object)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55168 — Commitment request / demand · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_0202 | Check deregistration of metering point operation |
| E_0203 | Check continued commitment |
| E_0240 | Check commitment request |
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
The party involved on this page sends this itself: “Deregistration” to NB (step 1).
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.
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: 5