Termination of a configuration from the MSB — WMSB view
The MSB of the directly affected location informs the NB or LF about the termination of the configuration for the directly affected location. If further locations of the directly affected location are affected by the termination of the configuration, the MSB also states these further affected locations in the information. 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 metering point operation, it involves the respective further MSB of the further affected locations.
Process flow from the perspective of the MSB (WMSB)
Process steps
1 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
2 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 MSBZ33Check identifiers
- 17129 — Order placement termination of a configuration · AS4
Flow
Message from MSB · AS4
APERAK checks
17129→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
Response
further MSB MSBCheck identifiers
- 19131 — Notification of configuration termination · AS4
Flow
Message to MSB · AS4
Response per decision tree
19131→ 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.6.1, pp. 75–77.
Preconditions
- 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.
- From the point of view of the MSB of the directly affected location, the termination of the configuration is generally possible for the affected locations.
- The configuration to be terminated is a configuration that
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
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. From the point of view of the MSB of the directly affected location, the termination of the configuration is not possible for the affected locations.
- The market partner is not assigned to the affected location at the ordered end of the effective period.
- The termination of the configuration has already been successfully ordered by the NB or LF or a further MSB via the use case „Order placement of the termination of a configuration to MSB“ for the end of the effective period envisaged by the MSB or for an earlier end.
- 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
- The termination of the configuration of an affected location must be carried out without delay; the termination of the configuration must, however, be set up before the end of the effective period. Note: the end of the effective period is the same for all affected locations.
- Note: In the case in which a further MSB wishes to end a configuration, it orders the termination of the configuration from MSB of the directly affected location via the use case “Order placement of the termination of a configuration to 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 MSB of the directly affected location needs a configuration to be ended that is to be ended in the course of this use case. These triggers can be, for example:
- The existing device technology will no longer permit the configuration in future.
- Within the use case „Start of metering point operation“ or the use case „Obligation gMSB“ (WiM part 1), the MSB receives from the NB the information about the reassignment of the metering location to another MSB at a specific point in time, or
- the contract for performing the metering point operation between the MSB and AN or ANN has been terminated.
- In the case of the termination of a configuration that was ordered by LF: The LF assigned to the directly affected location changes.
- In the case of the termination of a configuration that was ordered by NB: The NB assigned to the directly affected location changes.
Runs beforehand: Start of metering point operation, Obligation gMSB — these processes name the one shown here in their result.
First message
MSB sends “End of a configuration for further affected locations” (step 3). From here on, it is the turn of the party involved on this page.
Objective
The configuration (e.g. metering product, tax permit) of the affected locations (e.g. metering location, market location, controllable resource, grid location) has ended.
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 process begins for the own role with their message, so the transaction is created.
Applies to: 3
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.
Applies to: 4