End of metering point operation — NB 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 NB
Process steps
Deregistration
NB MSB (corresponds to MSBA at the metering location object)Z10Z16Z17Z18E_0202 Check deregistration of metering point operation550525505355168Check identifiers
- 55051 — End MSB · AS4
Flow
Message from MSB (corresponds to MSBA at the metering location object) · AS4
APERAK checks
55051→Z1055051→Z1655051→Z1755051→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
55051→ E_0202 — Check deregistration of metering point operation
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 deregistration
NB MSB (corresponds to MSBA at the metering location object)55051Flow
Triggered by incoming message
- 55051 — End MSB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to MSB (corresponds to MSBA at the metering location object) · 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 once the message has been created.
- Transaction updated — Update process data
Commitment request
NB MSB (corresponds to gMSB at the metering location object)55051Check identifiers
- 55168 — Commitment request / demand · AS4
Flow
Triggered by incoming message
- 55051 — End MSB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read balancing
GET /getAccountingBasic - Read location bundle
GET /getLocationBundleBasic - Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic - Read grid location
GET /getGridLocationBasic - Read controllable resource
GET /getControllableResourceBasic - Read technical resource
GET /getTechnicalResourceBasic - Read tranche
GET /getTrancheBasic - Read meter
GET /getCounterBasic
- Read balancing
Message to MSB (corresponds to gMSB at the metering location object) · 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 MSB (corresponds to gMSB at the metering location object)Z3317002Check identifiers
Flow
Message from MSB (corresponds to gMSB at the metering location object) · AS4
Response per decision tree
55169,55170→ E_0240 · Check commitment request
APERAK checks
55169,55170→Z33
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
Trigger follow-up process
- 17002 — Continued commitment
After processing, the MACO APP starts this follow-up process itself.
Continued commitment of the MSB
NB MSB (corresponds to MSBA at the metering location object)55170Check identifiers
- 17002 — Continued commitment · AS4
Flow
Triggered by incoming message
- 55170 — Rejection commitment request
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to MSB (corresponds to MSBA at the metering location object) · 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 MSB (corresponds to MSBA at the metering location object)Check identifiers
Flow
Message from MSB (corresponds to MSBA at the metering location object) · 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 with the data of the incoming message.
- Transaction updated — Update process data
Request to take over the individual metering location by the gMSB
NB MSB (corresponds to gMSB at the metering location object)55051Check identifiers
- 55168 — Commitment request / demand · AS4
Flow
Triggered by incoming message
- 55051 — End MSB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
- Read balancing
GET /getAccountingBasic - Read location bundle
GET /getLocationBundleBasic - Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic - Read grid location
GET /getGridLocationBasic - Read controllable resource
GET /getControllableResourceBasic - Read technical resource
GET /getTechnicalResourceBasic - Read tranche
GET /getTrancheBasic - Read meter
GET /getCounterBasic
- Read balancing
Message to MSB (corresponds to gMSB at the metering location object) · 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
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
MSB (corresponds to MSBA on the metering location object) sends “Deregistration” (step 1). From here on, the party involved on this side is the one to act.
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.
- View GMSB — default metering point operator · market role MSB
- View MSBA — the transferring MSB · market role MSB
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 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.