Quotation for invoice handling of metering point operation via the LF by the MSB — MSB-MALO view
The MSB of the market location has the option to
- after a device replacement has taken place in the course of which a iMS or mME was installed in the metering location(s) of a market location, or
- after a new LF has been assigned to the market location, for whose metering location(s) the MSB performs the metering point operation by means of iMS or mME, or
- if the number of services or the consumption group of the POG changes for the metering point operation that is equipped with iMS or mME, or
- as gMSB, in the event that it has continued to engage the previous wMSB (note: the wMSB settles directly with the gMSB), to submit a quotation to the LF for handling the billing via the LF. If the MSB of the market location makes use of this option, the LF must either accept or reject the quotation within 8 WT.
Process flow from the perspective of the MSB (MSB-MALO)
Process steps
Quotation for invoice processing of metering point operation via the LF
MSB (corresponds to MSB at the market location object) LFCheck identifiers
- 15002 — Quotation billing metering point operation MSB · AS4
Flow
Message to LF · 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 the quotation
MSB (corresponds to MSB at the market location object) LFCheck identifiers
Flow
Message from LF · AS4
Response per decision tree
21032→ E_0205 · LF · Check quotation
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0205 | Check quotation |
Process information
Wording of the consolidated version, profile ch. 3.6.3.4.1, pp. 70–71.
Preconditions
- For a market location with one assigned metering location, that metering location must be equipped with a mME or iMS.
- For a market location with at least two assigned metering locations, at least one metering location must be equipped with a mME/a iMS
- The LF is assigned to the market location of the metering location(s).
- No agreement on the point in time of the offer validity exists yet.
Results
- The MSB of the market location can invoice the LF for the metering point operation, or
- the MSB of the market location can contact the AN or
- for iMS, the MSB of the market location has already set up the billing of the metering point operation via another LF of a market location affected by the POG determination.
- The invoice handling applies from the confirmation of the offer, with effect from the requested start of billing, for an indefinite period. Any invoice handling towards the same LF already confirmed beforehand that would begin after the start of billing is therefore void.
Error case
Error cases
- The metering location could not be identified.
- The LF is not assigned to the market location.
Further requirements
If the AN changes in the course of a start-of-supply or E/G process (GPKE part 2), but the LF does not, no new quotation is sent to the LF by the MSB of the market location on account of this, because this change is not apparent to the MSB of the market location.
First message
The party involved on this page sends this itself: “Quotation for invoice processing of metering point operation via the LF” to LF (step 1).
Objective
The LF is the payer of the metering point operation or the LF is not the payer of the metering point operation.
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 LF — LF
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 source does not yet name the event that triggers these steps.
Applies to: 1
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
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: 1