Start of metering point operation — LF view
The process describes the interactions between the market participants in the case where a single metering location is to be assigned to the registering MSB for carrying out metering point operation. This applies in particular when
- it is the initial commissioning or the recommissioning of an individual metering location,
- the metering point operation for this metering location is to be assigned to a wMSB for the first time or
- the individual metering location is to be assigned to a MSB other than the previous one.
Process flow from the perspective of the LF
Process steps
1 Registration
MSBN NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55042 — Registration MSB · AS4
3 Information about preliminary registration confirmation
NB MSBA
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21007 — Status message · AS4
Information about preliminary registration confirmation
LF NBZ10Z17Z18Check identifiers
- 21007 — Status message · AS4
Flow
Message from NB · AS4
APERAK checks
21007→Z10— APERAK check: Is location known ?21007→Z1721007→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 failure of the assignment
LF NBZ10Z17Z18Check identifiers
- 21011 — Status message · AS4
Flow
Message from NB · AS4
Response per decision tree
21011→ E_0232 · Check notification on the overall transaction
APERAK checks
21011→Z10— APERAK check: Is location known ?21011→Z1721011→Z18
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
16 Notification of the failure of the overall transaction
NB MSBN
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21013 — Status message · AS4
17 Information on failure of the assignment
NB MSBA
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21013 — Status message · AS4
Information on failure of the assignment
LF NBZ10Z17Z18Check identifiers
- 21013 — Status message · AS4
Flow
Message from NB · AS4
APERAK checks
21013→Z10— APERAK check: Is location known ?21013→Z1721013→Z18
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0232 | Check notification on the overall transaction |
| E_0201 | Check registration of metering point operation |
Process information
Wording of the consolidated version, profile ch. 2.3.1, p. 22.
Preconditions
Conclusion 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.
- The NB sends the calculation formula to the MSBN.
- 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).
First message
NB sends “Information on the preliminary registration confirmation” (step 4). From here on, it is the turn of the party involved on this page.
Objective
The MSB is assigned to a metering location ( as part of 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 NB — NB
- View MSBA — the transferring MSB · market role MSB
- View MSBN — the receiving 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: 4
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.
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.