Order placement for a configuration from the NB to the MSB — MSB view
The NB or LF orders a configuration for the directly affected location from the MSB of the directly affected location. If further locations of the directly affected location are affected by the configuration, the NB or LF also states these further affected locations in the order placement (for example, in the order placement for the change of the balancing procedure at market location level, the NB has to order not only the market location but also all metering locations of the market location from the MSB of the market location). Before a chargeable order placement can be made, the NB or LF has to request a quotation from the MSB of the directly affected location for setting up the configuration. The MSB checks the order placement and informs the NB or LF of the further procedure for the order placement. If further locations of the directly affected location are affected by the configuration for which the MSB of the directly affected location does not perform the metering point operation, it involves the respective further MSB for these further affected locations.
Process flow from the perspective of the MSB
Process steps
Request for a configuration at the level of the directly affected location
MSB NBZ10Z17Z18E_0524 Check request1500421033Check identifiers
- 35004 — Request for a configuration · AS4
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read grid location
GET /getGridLocationBasic - Read controllable resource
GET /getControllableResourceBasic
- Read market location
APERAK checks
35004→Z1035004→Z1735004→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
Load data for the check
- Read metering location
GET /getMeterLocationBasic - Read grid location
GET /getGridLocationBasic - Read price sheet
GET /getPriceSheetBasic LESEN_STEUERBARE_RESOURCE_BASIS
- Read metering location
Decision tree
35004→ E_0524 — Check request
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.
Quotation for/ rejection of the request
MSB NB35004Check identifiers
Flow
Triggered by incoming message
- 35004 — Request for a configuration
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to NB · AS4
Response per decision tree
21033→ E_0524 · MSB · Check request
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
Order placement for a configuration at the level of the directly affected location
MSB NBZ33E_0526 Check order placement19132Check identifiers
- 17131 — Order placement quotation for a configuration · AS4
Flow
Message from NB · AS4
APERAK checks
17131→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
Load data for the check
LESEN_ANGEBOT_BASISLESEN_DEFINITION_LST_KURVEN- Read switching time definition
GET /getDefinitionSwitch - Read metering time period definition
GET /getDefinitionCounting - Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read grid location
GET /getGridLocationBasic - Read price sheet
GET /getPriceSheetBasic LESEN_STEUERBARE_RESOURCE_BASIS
Decision tree
17131→ E_0526 — Check order placement
Trigger follow-up process
- 19132 — Notification of configuration order placement
After processing, the MACO APP starts this follow-up process itself.
Order placement for a configuration at the level of the directly affected location
MSB NBZ10Z17Z18Z33E_0526 Check order placement171181912019132Check identifiers
Flow
Message from NB · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read grid location
GET /getGridLocationBasic - Read controllable resource
GET /getControllableResourceBasic
- Read market location
APERAK checks
17130,17121→Z1017130,17121→Z1717130,17121→Z1817130→Z33
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
LESEN_DEFINITION_LST_KURVEN- Read switching time definition
GET /getDefinitionSwitch - Read metering time period definition
GET /getDefinitionCounting - Read metering location
GET /getMeterLocationBasic - Read price sheet
GET /getPriceSheetBasic - Read tranche
GET /getTrancheBasic
Decision tree
17130,17121→ E_0526 — Check order placement
Trigger follow-up process
- 17118 — Order placement of a configuration change
- 19120 — Notification of change
- 19132 — Notification of configuration order placement
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Notification on the further procedure for the order placement
MSB NB171211713017131Check identifiers
Flow
Triggered by incoming message
- 17121 — Order placement change
- 17130 — Order placement of a configuration
- 17131 — Order placement quotation for a configuration
The MACO APP sends this message itself, as a follow-up process after one of these incoming messages.
Message to NB · AS4
Response per decision tree
19132,19120→ E_0526 · MSB · Check order placement
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
Order placement for a configuration for further affected locations
MSB further MSB17121Check identifiers
Flow
Triggered by incoming message
- 17121 — Order placement change
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to further MSB · 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
MSB further MSBZ33Check identifiers
Flow
Message from further MSB · AS4
Response per decision tree
19132,19127→ E_0527 · MSB · Order placement
APERAK checks
19132,19127→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
Response to order placement
MSB further MSBCheck identifiers
- 21043 — Order response / notification · AS4
Flow
Message to further MSB · AS4
Response per decision tree
21043→ E_0528 · MSB · Check implementation of the configuration
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
Response to order placement
MSB NBCheck identifiers
- 21043 — Order response / notification · AS4
Flow
Message to NB · AS4
Response per decision tree
21043→ E_0529 · MSB · Assessment of the overall process
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
MSB further MSBCheck identifiers
- 21043 — Order response / notification · AS4
Flow
Message to further MSB · AS4
Response per decision tree
21043→ E_0529 · MSB · Assessment of the overall process
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_0524 | Check request |
| E_0526 | Check order placement |
| E_0527 | Order placement |
| E_0528 | Check implementation of the configuration |
| E_0529 | Assessment of the overall process |
Process information
Wording of the consolidated version, profile ch. 1.3.3.1, pp. 42–46.
Preconditions
- In the case in which the order placement is preceded by a quotation process:
- This is a chargeable configuration.
- The article IDs relevant for the configuration are listed in price sheet A of MSB.
- The metering point operation is carried out at all affected locations by the same MSB; i.e. the MSB of the directly affected location is the MSB of all further affected locations, where applicable.
- In the case in which the order placement is not preceded by a quotation process:
- This is not a chargeable configuration. This would be the case, for example, with an order placement for a transmission of values according to type 1.
- In the case of the order placement of a configuration from LF to NB: NB has received an order placement of the configuration from LF via the use case “Order placement of a configuration from LF to NB” (e.g. the order placement of a change of the balancing method or the order placement of a configuration for which a metering time period definition of NB is required) for which the setup of the configuration is generally possible from the point of view of NB.
- The device technology available at the ordered point in time permits the configuration to be set up. In the case of an order placement for a configuration that requires a metering time period definition of LF, for example, this means that all metering locations of the market location are equipped with iMS.
- In the case of the order placement of a tax permit:
- The order placement is only possible for one location (controllable resource, grid location).
- The location is equipped with a iMS and a control device that communicates via the SMGW.
- In the case of the order placement of a configuration that enables the transmission of values directly from iMS to NB or LF:
- The order placement is only possible for one location.
- The location is equipped with a iMS.
- 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 is required: This concerns a consuming market location.
- In the case in which the order placement is preceded by a quotation process:
Results
- If the configuration was set up successfully for all affected locations, MSB of the respective affected location carries out the use case “Master data change” (here: SD “Master data change originating from MSB (responsible)”) (GPKE Part 4), provided a master data change is required for the respective location due to the setup of the configuration.
- In the case of the order placement of a configuration from LF to NB: NB forwards the confirmation to LF.
- In the case in which the order placement was preceded by a quotation process: The billing of the article ID can be carried out via the use case “Billing of services of price sheet A of MSB" by MSB to NB or LF.
Error case
Result in the error case
- The NB or LF checks whether a renewed order issuance for the configuration is required.
- In the case of the order placement of a configuration from LF to NB: NB forwards the rejection to LF.
- The existing configuration remains in place. If the ordered configuration has already been set up for an affected location, the original state prior to the order placement is restored for that location.
Error cases
- In the case in which the order placement is preceded by a quotation process:
- This is not a chargeable configuration or
- the article IDs relevant to the configuration are not listed in price sheet A of the MSB or
- the metering point operation is not performed by the same MSB at all affected locations; i.e. the MSB of the directly affected location is not the MSB of all further affected locations.
- In the case in which the order placement is not preceded by a quotation process: This concerns 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 an order placement for a configuration that requires a metering time period definition of LF, for example, this means: not all metering locations of the market location are equipped with iMS.
- In the case of the order placement of a tax permit:
- More than one location is specified in the order placement or
- The location is not equipped with a iMS and a control device that communicates via the SMGW.
- In the case of the order placement of a configuration that enables the transmission of values directly from iMS to NB or LF:
- More than one location is specified in the order placement or
- The location is not equipped with a iMS.
- In the case of the order placement of a configuration for which a metering time period definition, switching time definition or power curve definitions are 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 definition”.
- In the case of the order placement of a configuration for which a metering time period definition is required: This concerns a generating market location or a tranche.
- Not all parameters or incorrect parameters are available for the setting up of the configuration.
Further requirements
- If the device technology available at the ordered point in time does not permit the setup of the configuration, the change of the device technology is not to 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 use cases for the metering location change (WiM Part 1).
- Via this use case, the LF can also transmit an order placement of a configuration to the future MSB.
- Configurations of NB are communicated by NB to MSB in the use case “Start of metering point operation” (WiM Part 1) in process step 2 within the minimum parameters for the metering location(s). An order placement of a configuration contained in the minimum parameters is not necessary via the use case described here. In addition to the configurations communicated in the minimum parameters, NB can transmit an order placement of a configuration to the future MSB using the use case described here. Note: If a metering time period definition of NB is communicated to MSB within the minimum parameters in the use case “Start of metering point operation” (WiM Part 1) that MSB has not received in advance via the use case “Transmission of a definition of NB by NB”, the energy is to be recorded in one register at the metering location(s) and the associated market location for the metering time period usage purpose “grid usage”.
Trigger
- The NB needs to have a configuration set up, or
- The LF needs a configuration to be set up which the LF has to order directly from the MSB and not via the NB. This can be, for example:
- In the case of the order placement of a configuration for which a metering time period definition of NB is required: NB wishes to change the existing configuration of a market location and its associated metering locations for the metering time period usage purpose “grid usage”.
- In the case of the order placement of a configuration for which a metering time period definition of LF is required: LF wishes to state in the order placement
- that it wants to order a metering time period definition of the LF with the metering time period usage purpose “end customer” that differs from the existing configuration with the metering time period usage purpose “grid usage” or
- that it wants to change the existing configuration for the metering time period usage purpose “end customer” to a different metering time period definition of the LF.
First message
NB sends “Request for a configuration at the level of the directly affected location” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The order placement for the configuration (e.g. metering product, tax permit) for the affected locations (e.g. metering location, market location, controllable resource, grid location) has been confirmed by the MSB of the directly affected 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.
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.
These read accesses are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button.
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: 7
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.