Order placement for termination of a configuration from the additional MSB to the MSB — WMSB view
The NB or LF orders the termination of 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 termination of the configuration, the NB or LF also states these further affected locations in the order placement (if, for example, the LF no longer wishes to apply its own metering time period definition of the LF, then in the order placement for the termination of the corresponding configuration at market location level the LF has to order the termination not only for the market location but also for all metering locations of the market location). The MSB checks the order placement. If the termination of the configuration is generally possible for the affected locations, the MSB confirms the order placement to the NB or LF; otherwise it rejects the order placement. If further locations of the directly affected location are affected by the termination of 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. This use case also allows a further MSB to order the termination of a configuration from the MSB of the directly affected location. If the termination of the configuration is generally possible for the affected locations, the MSB of the directly affected location confirms the order placement to the further MSB, involves further affected MSB where necessary and informs the NB or LF about the termination of the configuration.
Process flow from the perspective of the MSB (WMSB)
Process steps
Order placement for the termination of a configuration at the level of the directly affected location
further MSB MSB17121Check identifiers
Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to 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
Response to order placement
further MSB MSBZ33Check identifiers
Flow
Message from MSB · AS4
Response per decision tree
19131,19127→ E_0539 · MSB · Check termination
APERAK checks
19131,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
3 Information about the termination of a configuration
MSB NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21044 — Order termination · AS4
4 Information about the termination of a configuration
MSB LF
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21044 — Order termination · AS4
Termination of a configuration for further affected locations
further MSB MSBZ33Z10Z17Z18Check identifiers
Flow
Message from MSB · AS4
APERAK checks
17129→Z3317118→Z1017118→Z1717118→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
Response
further MSB MSBCheck identifiers
Flow
Message to MSB · AS4
Response per decision tree
19131,19127→ E_0539 · MSB · Check termination
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_0539 | Check termination |
Process information
Wording of the consolidated version, profile ch. 1.3.5.1, pp. 65–68.
Preconditions
- When ordering the termination of a configuration from the NB to the MSB:
- The configuration to be terminated is a configuration that
- the NB has successfully placed an order via the use case „Order placement of a configuration from the NB or LF to MSB“ and
- is to be terminated via this use case (e.g. tax permit of the NB).
- The order placement of the termination of a configuration contains only the locations that were contained in the order placement of the NB to the MSB for this configuration now to be terminated.
- The configuration to be terminated is a configuration that
- When ordering the termination of a configuration from the LF to the MSB:
- The configuration to be terminated is a configuration that
- the LF has successfully placed an order via the use case „Order placement of a configuration from the NB or LF to MSB“ and
- is to be terminated via this use case (e.g. a tax permit of the LF or a configuration that contains a metering time period definition of the LF).
- The order placement of the termination of a configuration contains only the locations that were contained in the order placement of the LF to the MSB for this configuration now to be terminated.
- The configuration to be terminated is a configuration that
- When ordering the termination of a configuration from the further MSB to the MSB:
- The configuration to be terminated is a configuration that
- was successfully ordered via the use case “Order placement of a configuration from the NB or LF to the MSB” and
- is to be terminated via this use case (e.g. a tax permit or a configuration that contains a metering time period definition of the LF).
- The order placement of the termination of a configuration contains only the locations that were contained in the order placement of the NB or LF to the MSB for this configuration now to be terminated.
- The configuration to be terminated is a configuration that
- When ordering the termination of a configuration from the NB to the MSB:
Results
- The MSB of the respective affected location carries out the use case „Master data change“ (here: SD „Master data change initiated by the MSB (responsible)“) (GPKE part 4), provided that a master data change is required for the respective location due to the termination of the configuration.
- In the case of a chargeable configuration: The final invoice can be issued 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 or a further MSB checks whether a new order issuance for the termination of the configuration is required.
Error cases
- The configuration to be terminated is a configuration that
- was not successfully ordered via the use case „Order placement of a configuration from the NB or LF to MSB“ or
- is not to be ended via this use case.
- The order placement of the termination of a configuration does not contain exactly the locations contained in the order placement of the NB or LF to the MSB
- The market partner is not assigned to the affected location at the ordered end of the effective period.
- Not all parameters or incorrect parameters are available for the termination of the configuration.
- The configuration to be terminated is a configuration that
Further requirements
- Note: In the case in which MSB of the directly affected location wishes to end a configuration, MSB of the directly affected location ends the configuration via the use case “Termination of a configuration by MSB”.
- On termination of a transmission of values: if values are received by the MSB of the directly affected location or by NB or LF after the end of the effective period, these values are not to be processed.
Trigger
- The NB or LF or a further MSB needs to terminate a configuration that is to be terminated in the course of this use case. This can be, for example:
- In the case of the order placement of a termination of a configuration that contains a metering time period definition of LF: LF wishes to state in the order placement that a metering time period definition of LF that has already been implemented for the metering time period usage purpose “end customer” is to be mapped by the metering time period definition of NB with the metering time period usage purpose “grid usage”. This is the case, for example, if LF no longer wishes to use its own metering time period definition of LF for the metering time period usage purpose “end customer”.
- In the case of the order placement of a termination by a further MSB: For a location affected by the configuration for which the further MSB performs the metering point operation, this results, for example, in the following:
- The existing device technology will no longer permit the configuration in future.
- As part of the use case „Start of metering point operation“ or the use case „Commitment gMSB“ (WiM part 1), the additional MSB receives from the NB the information about the reassignment of the metering location to another MSB at a specific point in time.
- The contract for performing metering point operation between the additional MSB and AN or ANN has been terminated.
First message
The party involved on this page is itself the sender of: „Order placement for the termination of a configuration at the level of the directly affected location“ to MSB (step 1).
Objective
The order placement for the termination of 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.
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.