Request for a value from the NB — MSB-MALO view
By means of an order process, the NB or LF requests interim meter readings from the MSB of the market location that was assigned to the market location for the time period for which the values are required. The MSB of the market location checks the request and fulfils it or, where applicable, rejects it. By means of an order process, the MSB of the market location requests interim meter readings of the metering location from the MSB of the metering location that was assigned to the metering location for the time period for which the values are required. The MSB of the metering location checks the request and fulfils it or, where applicable, rejects it.
Process flow from the perspective of the MSB (MSB-MALO)
Process steps
Request value
MSB (corresponds to MSB at the market location object) NBZ10Z17Z18S_0074 Check request for values (Electricity)19007ANFRAGE_WERTECheck identifiers
- 17004 — Request for values · AS4
Flow
Message from NB · AS4
APERAK checks
17004→Z1017004→Z1717004→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
17004→S_0074— Check request for values (Electricity)
Trigger follow-up process
- 19007 — Rejection of request for values
ANFRAGE_WERTE
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Processing status at termination of the process
MSB (corresponds to MSB at the market location object) NB17004Check identifiers
- 19007 — Rejection of request for values · AS4
Flow
Triggered by incoming message
- 17004 — Request for values
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to NB · AS4
Response per decision tree
19007→ E_0219 · Check request for value
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
Request for value of a metering location
MSB (corresponds to MSB at the market location object) MSB (corresponds to MSB at the metering location object)Check identifiers
- 17004 — Request for values · AS4
Flow
Prozessauslöser
START_ANFORDERUNG_MESSWERTEThe backend triggers this step with this event.
Message to MSB (corresponds to MSB 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
Processing status at termination of the process
MSB (corresponds to MSB at the market location object) MSB (corresponds to MSB at the metering location object)Z33Check identifiers
- 19007 — Rejection of request for values · AS4
Flow
Message from MSB (corresponds to MSB at the metering location object) · AS4
Response per decision tree
19007→ E_0220 · Check request for value
APERAK checks
19007→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
Processing status at termination of the process
MSB (corresponds to MSB at the market location object) NB17004Check identifiers
- 19007 — Rejection of request for values · AS4
Flow
Triggered by incoming message
- 17004 — Request for values
The MACO APP sends this message itself, as a follow-up process after this incoming message.
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
Process information
Wording of the consolidated version, profile ch. 2.6.1, p. 38.
Preconditions
- The MSB knows the metering locations and market location.
- The requesting party is authorised to request and receive interim reading values.
Results
Transmission of the interim meter readings to the authorised parties.
Further requirements
If the MSB changes before the order date in the case of an order placement directed into the future, the order placement sent becomes obsolete. The order placement must be sent again to the MSB then responsible.
Trigger
The trigger for an order placement from NB or LF to the MSB of the market location can be an interim meter reading (see no. 4 in the table „Representation of the values to be transmitted“) for market locations whose metering locations are equipped with kME with active energy metering, mME or iMS. The trigger for an order placement from NB to the MSB of the market location can be a delimitation procedure for metered market locations whose metering locations are equipped with kME with active energy metering or mME (see the requirements of chapter 2.2.2. „Processing and transmission of values“ on the subject of delimitation).
First message
NB sends “Request value” (Step 1). From here on, the party involved on this page takes its turn.
Objective
The NB or LF has requested interim meter readings from the MSB of the market location, or the MSB of the market location has requested interim meter readings from the MSB of the metering location.
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 MSB-MELO — MSB at the metering location object · market role MSB
- View NB — NB
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 own role was already involved in this process, so the transaction already exists.
Applies to: 5