Obligation gMSB — View NB
The NB obliges the gMSB to take over the individual metering location and any assigned market location. The gMSB decides whether it wishes to carry out a device replacement and/or a device takeover and, once carried out, confirms the takeover of the metering point operation to the NB. The use cases “Device replacement” and “Device takeover” can be triggered by the gMSB in parallel or one after the other. The NB subsequently informs the wMSB about the reassignment.
Process flow from the perspective of the NB
Process steps
Confirmation of the takeover of metering point operation
NB MSB (corresponds to gMSB at the metering location object)Z10Z16Z17Z18Check identifiers
- 21010 — Status message · AS4
Flow
Message from MSB (corresponds to gMSB at the metering location object) · AS4
APERAK checks
21010→Z1021010→Z1621010→Z1721010→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 MSB (corresponds to MSBA at the metering location object)Check identifiers
- 21018 — Status message · AS4
Flow
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
Process information
Wording of the consolidated version, profile ch. 2.5.1, pp. 35–36.
Preconditions
- The maximum term for the continued commitment of the deregistering wMSB within the use case „End of metering point operation“ has expired and there is no new MSB for the metering location or market location or
- as part of the use case „End of metering point operation“, the NB seeks an assignment of the gMSB.
Results
- The NB can distribute the master data changed as a result at the metering location and, where applicable, the market location of a location bundle to the authorised parties.
- The NB sends the calculation formula to the gMSB.
- If the transmission of values to ESA is carried out, MSBA ends the transmission of values to ESA.
- If MSBA has to end a configuration ordered by a NB or LF,
- and the MSBA is the MSB of the directly affected location of the configuration to be ended, the MSBA carries out the use case „Ending a configuration by the MSB“ (GPKE part 3).
- and, in the case that the MSBA is a „further MSB“ of the configuration to be ended, the MSBA carries out the use case „Order placement for ending a configuration to MSB“ (GPKE part 3).
Further requirements
If a wMSB registers the metering point operation before the „Takeover of the metering point operation“ is confirmed in the use case „Commitment gMSB“, the use case „Start of metering point operation“ must be carried out in this case and the use case „Commitment gMSB“ must be aborted.
Trigger
Runs beforehand: End of metering point operation — these processes name the one shown here in their result.
First message
MSB (corresponds to gMSB on the metering location object) sends “Confirmation of the metering point operation takeover” (step 3). From here on, the party involved on this side is the one to act.
Objective
The gMSB is assigned to a metering location and, if applicable, to the market location (for determining the energy quantities of the market location) within a location bundle.
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 numbers are those of the source; where one is missing, it is missing there.
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
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.