Order placement for a configuration from the LF to the NB — LF view
The LF orders a configuration for the directly affected location from the NB. The NB checks the order placement, informs the LF of the further procedure for the order placement and, where necessary, orders the required configuration from the MSB of the directly affected location using the use case “Order placement of a configuration from the NB or LF to the MSB”. The NB forwards the response message of the MSB to the LF.
Process flow from the perspective of the LF
Process steps
Order placement for a configuration at the level of the directly affected location
LF NBSTART_BESTELLUNG_AEND_PROGNOSEGRUNDLAGESTART_BESTELLUNG_ZAEHLZEITDEFINITIONCheck identifiers
Flow
Process trigger
The backend triggers this step with one of these events.
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
Notification on the further procedure for the order placement
LF NBZ33Check identifiers
Flow
Message from NB · AS4
Response per decision tree
19121,19124→ E_0523 · NB · Check order placement
APERAK checks
19121,19124→Z33— APERAK check: Is referenced message known ?
Write endpoint
19124→ Transaction created — Create process dataPOST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
Write endpoint
19121→ Transaction updated — Update process dataPOST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
Forwarding of the notification on the further procedure for the order placement from the MSB of the directly affected location
LF NBZ33Check identifiers
- 21043 — Order response / notification · AS4
Flow
Message from NB · AS4
Response per decision tree
21043→ E_0526 · MSB · Check order placement
APERAK checks
21043→Z33— APERAK check: Is referenced message known ?
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
Forwarding of the response to the order placement from the MSB of the directly affected location
LF NBZ33Check identifiers
- 21043 — Order response / notification · AS4
Flow
Message from NB · AS4
Response per decision tree
21043→ E_0529 · MSB · Assessment of the overall process
APERAK checks
21043→Z33— APERAK check: Is referenced message known ?
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 trees of this process
| EBD | Name |
|---|---|
| E_0523 | Check order placement |
| E_0526 | Check order placement |
| E_0529 | Assessment of the overall process |
Process information
Wording of the consolidated version, profile ch. 1.3.2.1, pp. 37–38.
Preconditions
- This is not a chargeable configuration.
- The device technology available at the ordered point in time permits the configuration to be set up. In the case of a change of the balancing procedure, for example, this means that all metering locations of the market location with kME are equipped with RLM.
- In the case of the order placement of a configuration for which a metering time period definition, switching time definition or power curve definition is required: The definition relevant for the configuration (e.g. metering time period definition of NB) was exchanged within the use cases of the chapter “Exchange regarding metering time, switching time and power curve definitions”.
- In the case of the order placement of a configuration for which a metering time period definition of NB is required:
- The metering time period definition of NB requested by LF has been marked as „orderable“.
- This is a consuming market location.
- In the case of the order placement of a configuration for which a metering time period definition of NB is required:
Results
- If the setup of the configuration makes a change of the billing data (e.g. change of the balancing method) (GPKE Part 2) or of further master data (GPKE Part 4) necessary, NB carries out the corresponding use case.
Error case
Result in the error case
- The LF checks whether a renewed order issuance for the configuration is required.
- The existing configuration remains in place.
Error cases
- This is a chargeable configuration.
- The market partner is not assigned to the affected location at the ordered start of the effective period.
- The device technology available at the ordered point in time does not permit the configuration to be set up. In the case of a change of the balancing procedure, for example, this means that not all metering locations of the market location with kME are equipped with RLM.
- In the case of the order placement of a configuration for which a metering time period definition, switching time definition or power curve definition is required: The definition relevant for the configuration (e.g. metering time period definition of NB) was not exchanged within the use cases of the chapter “Exchange regarding metering time, switching time and power curve definitions”.
- In the case of the order placement of a configuration for which a metering time period definition of NB is required:
- The metering time period definition of NB requested by LF has not been marked as „orderable“.
- This is a generating market location or a tranche.
- The LF wants to order a metering time period definition of the LF.
- Not all parameters or incorrect parameters are available for the configuration.
Further requirements
If the device technology present at the ordered point in time does not allow the configuration to be set up, the change of the device technology must not be ordered via this use case. A corresponding change of the device technology can be commissioned as part of a device replacement or via the WiM use cases for changing the metering location (WiM part 1).
Trigger
- The LF needs to have a configuration set up for which the NB is responsible.
- In the case of the order placement of a configuration for which a metering time period definition of NB is required: LF wishes to change the existing configuration of a market location for the metering time period usage purpose “grid usage” (incl. return to single-tariff logic).
Runs beforehand: Transmission of a definition of the NB by the NB — these processes name the one shown here in their result.
First message
The party involved on this page is itself the sender of: „Order placement for a configuration at the level of the directly affected location“ to NB (step 1).
Objective
The order placement for the configuration (e.g. metering product) for the affected locations (e.g. metering location, market location) has been confirmed by the NB.
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
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: 2