Initial installation of a iMS in an existing metering location — GMSB view
The gMSB informs the MSB, the NB and the LF about the intention and the planned point in time of the first device replacement with a iMS. The device replacement takes place within eight weeks from the planned point in time. The time period thus resulting is referred to below as the “planned time period”. The following cases are distinguished:
- Successful installation within the planned time period: after the device replacement to a iMS has taken place, MSB informs NB, LF and gMSB about the device replacement via the master data change process. If a wMSB does not carry out the device replacement to a iMS at a metering location, gMSB takes over the metering point operation at the metering location by applying the use case „Start of metering point operation“ and the corresponding subsequent processes in accordance with WiM electricity. In this case gMSB states the reason „Takeover due to iMS installation not carried out“. In this case MSBA has no right of rejection.
- Successful installation after postponement of the planned time period: if an extension of the time period for the installation of a iMS becomes necessary because the installation was not possible within the originally planned time period, the process starts again without renewed consideration of the announcement deadline of 3 months.
- Device replacement not possible: if no device replacement to a iMS is possible within the planned time period, or if it is established during the process for the device replacement to a iMS that no installation is possible, gMSB informs NB and LF that there is no longer a device replacement intent. If gMSB schedules the metering location again at a later point in time for an initial installation with a iMS, the process starts again. Delimitation: the process does not apply in the event that the initial installation is initiated on account of a customer request (not because of the roll-out).
Process flow from the perspective of the MSB (GMSB)
Process steps
Advance information on the device replacement
MSB (corresponds to gMSB at the metering location object) MSB (corresponds to wMSB at the metering location object)Check identifiers
- 21029 — Advance information · AS4
Flow
Message to MSB (corresponds to wMSB at the metering location object) · 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
Information on grandfathering / own installation iMS
MSB (corresponds to gMSB at the metering location object) MSB (corresponds to wMSB at the metering location object)Check identifiers
Flow
Message from MSB (corresponds to wMSB at the metering location object) · AS4
Response per decision tree
21030,21031→ E_0233 · MSB · Check of self-installation or grandfathering under §19 Abs. 5 MsbG
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
Advance information on the device replacement
MSB (corresponds to gMSB at the metering location object) LFCheck identifiers
- 21029 — Advance information · 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
Advance information on the device replacement
MSB (corresponds to gMSB at the metering location object) NBCheck identifiers
- 21029 — Advance information · AS4
Flow
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
Information on failure of the device replacement
MSB (corresponds to gMSB at the metering location object) MSB (corresponds to wMSB at the metering location object)Check identifiers
- 21027 — Status message · AS4
Flow
Message from MSB (corresponds to wMSB at the metering location object) · AS4
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
Information on no device replacement to iMS
MSB (corresponds to gMSB at the metering location object) LFCheck identifiers
- 21025 — Status message · 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
Information on no device replacement to iMS
MSB (corresponds to gMSB at the metering location object) NBCheck identifiers
- 21027 — Status message · AS4
Flow
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0233 | Check of self-installation or grandfathering under §19 Abs. 5 MsbG |
Process information
Wording of the consolidated version, profile ch. 3.5.1, pp. 59–60.
Results
- The NB must check whether a change of the balancing procedure is necessary for the affected market location.
- The NB must check whether the affected market location has to be reported to the ÜNB for aggregation.
First message
The party involved on this page is itself the sender of: „Advance information on the device replacement“ to MSB (corresponds to wMSB on the metering location object) (step 1).
Objective
All market partners involved are informed in advance about the intended initial installation of a iMS in an existing metering location and, at the end, about the result of the process of installing a iMS.
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 numbers are those of the source; where one is missing, it is missing there.
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.