# Device replacement — MSBN view The MSBN of the metering location informs the MSBA of the metering location of its device replacement intent. In its response, the MSBA of the metering location informs the MSBN of the metering location whether it wants to carry out the device removal itself or whether this is to be done by the MSBN of the metering location. The MSBN of the metering location informs the MSBA of the metering location of the point in time at which metering point operation was taken over and informs the relevant market roles of the completed device replacement by means of a master data change. If the measuring equipment itself is affected by the replacement, the MSBN of the metering location transmits, in the event that the MSBA of the metering location does not carry out the removal itself, the meter reading and the point in time of the device removal to the MSBA of the metering location in the case of a kME or mME with active energy metering, and the point in time of the device removal in the case of a kME with registering load curve/feed-in curve metering or a iMS. The point in time is determined by the start of the first fully measured quarter-hour value. ## Process flow from the perspective of the MSB (MSBN) \nSystem diagram: Gerätewechsel — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB (entsprich…\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_GERAETEWECHSEL\n\nAPI\n\n1. Anzeige\nGeräte-wechselabsicht\n\n\nMSB (entspricht MSBA…\n\nAS4\n17009\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort\n\n\nMSB (entspricht MSBA…\n\nAS4\n19015, 19016\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Zeitpunkt Übernahme des\nMessstellenbetriebs\n\n\nMSB (entspricht MSBA…\n\nAS4\n21010\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_ERHEBUNG_MESSWE\nRTE\n\nAPI\n\nLoad data for processing\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\n5. Zählerstand und Zeitpunkt\ndes Geräteausbaus\n\n\nMSB (entspricht MSBA…\n\nAS4\n13017\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n6. Zeitpunkt des\nGeräteausbaus\n\n\nMSB (entspricht MSBA…\n\nAS4\n21036\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Gerätewechsel — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB (entsprich…\n\n\nMSB (entspricht MSBA am O…\n\n\nSTART_GERAETEWECHSEL\nTrigger event\n\n1. Anzeige Geräte-wechselabsicht\nAS4 · PI 17009\n\nUpdate transaction\nUpdate process data\n\n2. Antwort\nAS4 · PI 19015, 19016 · E_0204\nE_0204 — Anzeige Gerätewechselabsicht prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Zeitpunkt Übernahme des Messstellenbetriebs\nAS4 · PI 21010\n\nUpdate transaction\nUpdate process data\n\nSTART_ERHEBUNG_MESSWERTE\nTrigger event\n\n5. Zählerstand und Zeitpunkt des Geräteausbaus\nAS4 · PI 13017\n\nUpdate transaction\nUpdate process data\n\n6. Zeitpunkt des Geräteausbaus\nAS4 · PI 21036\n\nUpdate transaction\nUpdate process data\n"} titel="MSBN" /> ## Process steps ### Notification of device replacement intent
**Check identifiers** - [17009](/en/schnittstellen/202604/pruefi/ORDERS/PI_17009) — Notification of device replacement intent · AS4
**Flow**
  1. **Prozessauslöser** [`START_GERAETEWECHSEL`](/en/api/202604/ausloeser-msb/start-geraetewechsel) \",\n \"lokationsId\": \"\"\n }\n ],\n \"AUFTRAG\": [\n {\n \"ausfuehrungsdatum\": \"\"\n }\n ],\n \"ZAEHLER\": [\n {\n \"geraete\": [\n \"\"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_GERAETEWECHSEL\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **MSB (corresponds to MSBA at the metering location object)** · AS4
  3. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN_BASIS` Updates the existing transaction in the backend once the message has been created.
### Response
**Check identifiers** - [19015](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19015) — Confirmation of device replacement intent · AS4 - [19016](/en/schnittstellen/202604/pruefi/ORDRSP/PI_19016) — Rejection of device replacement intent · AS4
**Flow**
  1. Message from **MSB (corresponds to MSBA at the metering location object)** · AS4
    **Response per decision tree** - `19015`, `19016` → [E_0204](/en/referenz/202604/ebd/E_0204) · Check notification of device replacement intent
  2. **APERAK checks** - `19015`, `19016` → `Z33`
  3. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN_BASIS` Updates the existing transaction in the backend with the data of the incoming message.
### Point in time of takeover of metering point operation
**Check identifiers** - [21010](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21010) — Status message · AS4
**Flow**
  1. Message to **MSB (corresponds to MSBA at the metering location object)** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Meter reading and point in time of the device removal
**Check identifiers** - [13017](/en/schnittstellen/202604/pruefi/MSCONS/PI_13017) — Meter reading (electricity) · AS4
**Flow**
  1. **Prozessauslöser** [`START_ERHEBUNG_MESSWERTE`](/en/api/202604/ausloeser-msb/start-erhebung-messwerte) \"\n ],\n \"lokationsId\": \"\"\n }\n ],\n \"ZAEHLER\": [\n {\n \"zaehlernummer\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"anfrageReferenz\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"lokationsTyp\": \"\",\n \"sparte\": \"\",\n \"typ\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ERHEBUNG_MESSWERTE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. **Load data for processing** - `LESEN_ENERGIEMENGE_ZAEHLERSTAND_BASIS` - [Read meter](/en/api/202604/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it
  3. Message to **MSB (corresponds to MSBA at the metering location object)** · AS4
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Point in time of device removal
**Check identifiers** - [21036](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21036) — Status message · AS4
**Flow**
  1. Message to **MSB (corresponds to MSBA at the metering location object)** · AS4
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN_BASIS` Updates the existing transaction in the backend once the message has been created.
Decision trees of this process | EBD | Name | |---|---| | [E_0204](/referenz/202604/ebd/E_0204) | Check notification of device replacement intent |
## Process information Wording of the consolidated version, profile ch. 3.1.1, pp. 41–42.
  1. ### Preconditions - Following a MSB change (use case “[Start of metering point operation](/en/prozessdoku/202604/MSB--MSBN/WiM-Teil1-beginn-messstellenbetrieb)” or use case “[Obligation gMSB](/en/prozessdoku/202604/MSB--GMSB/WiM-Teil1-verpflichtung-gmsb)”), MSBN of the metering location or gMSB of the metering location (shown as MSBN in this use case) intends to replace permanently installed devices. - The use case applies regardless of whether, for example, all technical equipment of the individual metering location relevant to the MSBN of the metering location, only the measuring equipment itself or only other technical equipment (e.g. transformers, SMGW) is to be replaced.
  2. ### Results If the measuring equipment itself is affected by the change, the MSBA of the metering location and MSBN of the metering location carry out the SD „[Processing and transmission of values from the MSB of the metering location](/en/prozessdoku/202604/MSB--MSB-MALO/WiM-Teil2-aufbereitung-und-uebermittlung-von-werten-vom-msb-der-messlokation)“ (WiM part 2).
  3. ### Further requirements - Note: If MSB of other divisions are affected by technical changes to a SMGW, they are informed by MSB of SMGW, as they are not informed within the defined market communication (this information may take place in a format other than EDIFACT). - Note: If the measuring equipment itself is affected by the replacement, MSB of the market location transmits values to NB, LF and ÜNB (WiM Part 2, Chapter 2.4.3. “[SD: Processing and transmission of values by MSB of the market location](/en/prozessdoku/202604/LF/WiM-Teil2-aufbereitung-und-uebermittlung-von-werten-vom-msb-der-marktlokation)”). If a market location has several metering locations and not all metering locations are affected by the device replacement and/or a device takeover, MSB of the market location must, in order to determine the energy quantity of the market location, collect values for the metering location not affected by the device replacement/device takeover and, if necessary, request them from MSB of the metering location.
  4. ### First message The party involved on this page is itself the sender of: „Notification of intended device replacement“ to **MSB (corresponds to MSBA on the metering location object)** (step 1).
  5. ### Objective The interactions for preparing and performing a device replacement between the MSBN of the metering location and the MSBA of the metering location have been completed.
## 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 MSBA](/en/prozessdoku/202604/MSB--MSBA/WiM-Teil1-geraetewechsel) — the transferring MSB · market role MSB *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.* These read accesses are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button. Applies to: [5](#schritt-5) These write calls are not listed in the API catalogue of this format version; the step therefore shows only their command, without address and without button. Applies to: [1](#schritt-1), [2](#schritt-2), [6](#schritt-6)