# Fault rectification at the metering location — View MSB-MELO The process describes the interactions between the market actors in the case of an established or suspected fault in the technical equipment of the metering location. The party reporting the fault notifies the MSB of the metering location of a fault in the metering. If a fault exists, the MSB of the metering location informs the MSB of the affected market locations. Once the information is available, the MSB of the respective affected market location must inform all market participants authorised for this market location about the fault. The MSB is obliged to remedy the fault at the metering location without delay and thereby to ensure its operation in accordance with the accepted rules of technology. The same procedure must also be carried out after the fault has been remedied. ## Process flow from the perspective of the MSB (MSB-MELO) \nSystem diagram: Störungsbehebung in der Messlokation — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB (entsprich…\n\nMarket partner\n\n\n\n1. Meldung einer Störung\n\nStörungsmelder\n\nAS4\n23001\n\nAPERAK check: Z10, Z17,\nZ18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n2. Antwort\n\n\nStörungsmelder\n\nAS4\n23003, 23004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Information über Störung\nan Messlokation\n\n\nMSB (entspricht MSB a…\n\nAS4\n23005\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n7. Mitteilung Ergebnis\n\n\nStörungsmelder\n\nAS4\n23008\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n8. Information über Ergebnis\nan Messlokation\n\n\nMSB (entspricht MSB a…\n\nAS4\n23009\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Störungsbehebung in der Messlokation — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB (entsprich…\n\n\nStörungsmelder\n\n\nMSB (entspricht MSB am Ob…\n\n\nNB\n\n\nLF\n\n\nÜNB\n\n\n1. Meldung einer Störung\nAS4 · PI 23001\n\nCreate transaction\nCreate process data\n\n2. Antwort\nAS4 · PI 23003, 23004\n\nUpdate transaction\nUpdate process data\n\n3. Information über Störung an Messlokation\nAS4 · PI 23005\n\nUpdate transaction\nUpdate process data\n\n4. Information über Störung an betroffener Markt…\nAS4 · PI 23011\n\n5. Information über Störung an betroffener Markt…\nAS4 · PI 23011\n\n6. Information über Störung an betroffener Markt…\nAS4 · PI 23011\n\n7. Mitteilung Ergebnis\nAS4 · PI 23008\n\nUpdate transaction\nUpdate process data\n\n8. Information über Ergebnis an Messlokation\nAS4 · PI 23009\n\nUpdate transaction\nUpdate process data\n\n9. Information über Ergebnis der betroffenen Mar…\nAS4 · PI 23012\n\n10. Information über Ergebnis der betroffenen Mar…\nAS4 · PI 23012\n\n11. Information über Ergebnis der betroffenen Mar…\nAS4 · PI 23012\n"} titel="MSB-MELO" /> ## Process steps ### Notification of a fault
**Check identifiers** - [23001](/en/schnittstellen/202610/pruefi/INSRPT/PI_23001) — Fault notification · AS4
**Flow**
  1. Message from **fault reporter** · AS4
  2. **APERAK checks** - `23001` → `Z10` - `23001` → `Z17` - `23001` → `Z18`
  3. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/backend-schreiben-msb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
### Response
**Check identifiers** - [23003](/en/schnittstellen/202610/pruefi/INSRPT/PI_23003) — Rejection · AS4 - [23004](/en/schnittstellen/202610/pruefi/INSRPT/PI_23004) — Confirmation · AS4
**Flow**
  1. Message to **fault reporter** · 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 about fault at metering location
**Check identifiers** - [23005](/en/schnittstellen/202610/pruefi/INSRPT/PI_23005) — Information notification · AS4
**Flow**
  1. Message to **MSB (corresponds to MSB at the market 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 about fault at affected market location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [23011](/en/schnittstellen/202610/pruefi/INSRPT/PI_23011) — Information notification · AS4
### Information about fault at affected market location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [23011](/en/schnittstellen/202610/pruefi/INSRPT/PI_23011) — Information notification · AS4
### Information about fault at affected market location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [23011](/en/schnittstellen/202610/pruefi/INSRPT/PI_23011) — Information notification · AS4
### Result notification
**Check identifiers** - [23008](/en/schnittstellen/202610/pruefi/INSRPT/PI_23008) — Result report · AS4
**Flow**
  1. Message to **fault reporter** · 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 about result at metering location
**Check identifiers** - [23009](/en/schnittstellen/202610/pruefi/INSRPT/PI_23009) — Information notification · AS4
**Flow**
  1. Message to **MSB (corresponds to MSB at the market 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 about result of the affected market location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [23012](/en/schnittstellen/202610/pruefi/INSRPT/PI_23012) — Information notification · AS4
### Information about result of the affected market location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [23012](/en/schnittstellen/202610/pruefi/INSRPT/PI_23012) — Information notification · AS4
### Information about result of the affected market location This step runs between other market partners and is not relevant for this view.
**Check identifiers** - [23012](/en/schnittstellen/202610/pruefi/INSRPT/PI_23012) — Information notification · AS4
## Process information Wording of the consolidated version, profile ch. 1.1, pp. 5–6.
  1. ### Preconditions The party reporting the fault detects a fault.
  2. ### Results Functioning technical equipment of the metering location.
  3. ### Further requirements Additional notes: - This process must also be run through if the MSB of the metering location detects the fault itself. In this case process steps 1, 2 and 7 are not run through. - If ÜNB is missing values, the use case “Fault rectification in the metering location” does not take place, but rather the use case “Complaint about values to MSB”. - Additional note: if a register fault (e.g. register standstill, register slowdown, register manipulation) exists at a kME or a mME, a correction energy quantity must be transmitted by MSB at metering location level for the consumption to be corrected. The substitute value calculation for determining the correction energy quantity is carried out in accordance with VDE-AR-N 4400 („Metering Code“). The meter reading read from the measuring equipment is not corrected. The meter reading read and the correction energy quantities are transmitted in accordance with the requirements of the use case „Processing and transmission of values“. In addition, the MSB of the market location must transmit an energy quantity for the energy quantity to be billed at market location level.
  4. ### First message **Fault reporter** sends “Report of a fault” (step 1). From here on it is the turn of the party involved on this page.
  5. ### Objective Rectification of a fault in the technical equipment of the metering location.
## 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 MSB-MALO](/en/prozessdoku/202610/MSB--MSB-MALO/WiM-Teil2-stoerungsbehebung-in-der-messlokation) — MSB at the market location object · market role MSB - [View LF](/en/prozessdoku/202610/LF/WiM-Teil2-stoerungsbehebung-in-der-messlokation) — LF - [View NB](/en/prozessdoku/202610/NB/WiM-Teil2-stoerungsbehebung-in-der-messlokation) — NB - [View ÜNB](/en/prozessdoku/202610/UENB/WiM-Teil2-stoerungsbehebung-in-der-messlokation) — ÜNB · market role UENB *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: [1](#schritt-1)