Start of metering point operation — NB 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 NB
Process steps
Registration
NB MSBNE_0201 Check registration of metering point operation210075504355044Check identifiers
- 55042 — Registration MSB · AS4
Flow
Message from MSBN · AS4
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
Load data for the check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read metering point operation contract
GET /getMeasuringPointOperationContractBasic
- Read market location
Decision tree
55042→ E_0201 — Check registration 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 registration
NB MSBN55042Check identifiers
Flow
Triggered by incoming message
- 55042 — Registration 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 meter
GET /getCounterBasic
- Read balancing
Message to MSBN · AS4
Response per decision tree
55043,55044→ E_0201 · Check registration 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
Information about preliminary registration confirmation
NB MSBA55042Check identifiers
- 21007 — Status message · AS4
Flow
Triggered by incoming message
- 55042 — Registration MSB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to MSBA · 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
Information about preliminary registration confirmation
NB LF55042Check identifiers
- 21007 — Status message · AS4
Flow
Triggered by incoming message
- 55042 — Registration MSB
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to LF · 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
Notification of the overall transaction
NB MSBNE_0232 Check notification on the overall transaction2101121012Flow
Message from MSBN · AS4
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
Load data for the check
- Read market location
GET /getMarketLocationBasic
- Read market location
Decision tree
21009→ E_0232 — Check notification on the overall transaction
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 notification of the overall transaction
NB MSBN2100921010Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Load data for processing
- Read metering location
GET /getMeterLocationBasic
- Read metering location
Message to MSBN · AS4
Response per decision tree
21011→ E_0232 · Check notification on the overall transaction
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
Information on failure of the assignment
NB MSBA21009Check identifiers
- 21011 — Status message · AS4
Flow
Triggered by incoming message
- 21009 — Status message
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to MSBA · AS4
Response per decision tree
21011→ E_0232 · Check notification on the overall transaction
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
Information on failure of the assignment
NB LF21009Check identifiers
- 21011 — Status message · AS4
Flow
Triggered by incoming message
- 21009 — Status message
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to LF · AS4
Response per decision tree
21011→ E_0232 · Check notification on the overall transaction
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
Notification of the failure of the overall transaction
NB MSBNCheck identifiers
- 21013 — Status message · AS4
Flow
Message to MSBN · 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
Information on failure of the assignment
NB MSBACheck identifiers
- 21013 — Status message · AS4
Flow
Message to MSBA · 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
Information on failure of the assignment
NB LFCheck identifiers
- 21013 — Status message · AS4
Flow
Message to LF · 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_0201 | Check registration of metering point operation |
| E_0232 | Check notification on the overall transaction |
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
MSBN sends “Registration” (step 1). 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 LF — LF
- 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.