# 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](/en/prozessdoku/202610/LF/WiM-Teil1-beginn-messstellenbetrieb)“ 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) \nSystem diagram: Ersteinbau eines iMS in eine bestehende Messlokation — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB (entsprich…\n\nMarket partner\n\n\n\n1. Vorabinformation zum\nGerätewechsel\n\nMSB (entspricht wMSB…\n\nAS4\n21029\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Information\nBestandsschutz /\nEigenausbau iMS\n\n\nMSB (entspricht wMSB…\n\nAS4\n21030, 21031\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Vorabinformation zum\nGerätewechsel\n\n\nLF\n\nAS4\n21029\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Vorabinformation zum\nGerätewechsel\n\n\nNB\n\nAS4\n21029\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n6. Information über Scheitern\ndes Gerätewechsels\n\n\nMSB (entspricht wMSB…\n\nAS4\n21027\n\nAPERAK check: Z10, Z17,\nZ18\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n9. Information kein\nGerätewechsel auf iMS\n\n\nLF\n\nAS4\n21025\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n10. Information kein\nGerätewechsel auf iMS\n\n\nNB\n\nAS4\n21027\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Ersteinbau eines iMS in eine bestehende Messlokation — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB (entsprich…\n\n\nMSB (entspricht wMSB am O…\n\n\nLF\n\n\nNB\n\n\n1. Vorabinformation zum Gerätewechsel\nAS4 · PI 21029\n\nUpdate transaction\nUpdate process data\n\n2. Information Bestandsschutz / Eigenausbau iMS\nAS4 · PI 21030, 21031 · E_0233\nE_0233 — Prüfung Selbsteinbau oder Bestandsschutz nach §19 Abs. 5 MsbG\n\nUpdate transaction\nUpdate process data\n\n3. Vorabinformation zum Gerätewechsel\nAS4 · PI 21029\n\nUpdate transaction\nUpdate process data\n\n4. Vorabinformation zum Gerätewechsel\nAS4 · PI 21029\n\nUpdate transaction\nUpdate process data\n\n6. Information über Scheitern des Gerätewechsels\nAS4 · PI 21027\n\nUpdate transaction\nUpdate process data\n\n9. Information kein Gerätewechsel auf iMS\nAS4 · PI 21025\n\nUpdate transaction\nUpdate process data\n\n10. Information kein Gerätewechsel auf iMS\nAS4 · PI 21027\n\nUpdate transaction\nUpdate process data\n"} titel="GMSB" /> ## Process steps ### Advance information on the device replacement
**Check identifiers** - [21029](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21029) — Advance information · AS4
**Flow**
  1. Message to **MSB (corresponds to wMSB at the metering location object)** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Information on grandfathering / own installation iMS
**Check identifiers** - [21030](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21030) — iMS initial installation status · AS4 - [21031](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21031) — Grandfathering / self-installation iMS · AS4
**Flow**
  1. Message from **MSB (corresponds to wMSB at the metering location object)** · AS4
    **Response per decision tree** - `21030`, `21031` → [E_0233](/en/referenz/202610/ebd/E_0233) · MSB · Check of self-installation or grandfathering under §19 Abs. 5 MsbG
  2. **APERAK checks** - `21030`, `21031` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Advance information on the device replacement
**Check identifiers** - [21029](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21029) — Advance information · AS4
**Flow**
  1. Message to **LF** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Advance information on the device replacement
**Check identifiers** - [21029](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21029) — Advance information · AS4
**Flow**
  1. Message to **NB** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Information on failure of the device replacement
**Check identifiers** - [21027](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21027) — Status message · AS4
**Flow**
  1. Message from **MSB (corresponds to wMSB at the metering location object)** · AS4
  2. **APERAK checks** - `21027` → `Z10` - `21027` → `Z17` - `21027` → `Z18`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Information on no device replacement to iMS
**Check identifiers** - [21025](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21025) — Status message · AS4
**Flow**
  1. Message to **LF** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Information on no device replacement to iMS
**Check identifiers** - [21027](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21027) — Status message · AS4
**Flow**
  1. Message to **NB** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
Decision trees of this process | EBD | Name | |---|---| | [E_0233](/referenz/202610/ebd/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.
  1. ### 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.
  2. ### 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).
  3. ### 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. - [View WMSB](/en/prozessdoku/202610/MSB--WMSB/WiM-Teil1-ersteinbau-eines-ims-in-eine-bestehende-messlokation) — further metering point operator · market role MSB - [View LF](/en/prozessdoku/202610/LF/WiM-Teil1-ersteinbau-eines-ims-in-eine-bestehende-messlokation) — LF - [View NB](/en/prozessdoku/202610/NB/WiM-Teil1-ersteinbau-eines-ims-in-eine-bestehende-messlokation) — NB *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](#schritt-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](#schritt-2), [6](#schritt-6) 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](#schritt-1), [2](#schritt-2), [3](#schritt-3), [4](#schritt-4), [6](#schritt-6), [9](#schritt-9), [10](#schritt-10)