Fault rectification at the metering location — View MSB-MALO
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-MALO)
Process steps
1 Notification of a fault
Fault reporter MSB (corresponds to MSB at the metering location object)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 23001 — Fault notification · AS4
Information about fault at metering location
MSB (corresponds to MSB at the market location object) MSB (corresponds to MSB at the metering location object)Z10Z17Z18Check identifiers
- 23005 — Information notification · AS4
Flow
Message from MSB (corresponds to MSB at the metering location object) · AS4
APERAK checks
23005→Z1023005→Z1723005→Z18
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Information about fault at affected market location
MSB (corresponds to MSB at the market location object) NBCheck identifiers
- 23011 — Information notification · 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 about fault at affected market location
MSB (corresponds to MSB at the market location object) LFCheck identifiers
- 23011 — Information notification · 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 about fault at affected market location
MSB (corresponds to MSB at the market location object) ÜNBCheck identifiers
- 23011 — Information notification · 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
7 Result notification
MSB (corresponds to MSB at the metering location object) Fault reporter
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 23008 — Result report · AS4
Information about result at metering location
MSB (corresponds to MSB at the market location object) MSB (corresponds to MSB at the metering location object)Z33Check identifiers
- 23009 — Information notification · AS4
Flow
Message from MSB (corresponds to MSB at the metering location object) · AS4
APERAK checks
23009→Z33
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 about result of the affected market location
MSB (corresponds to MSB at the market location object) NBCheck identifiers
- 23012 — Information notification · 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 about result of the affected market location
MSB (corresponds to MSB at the market location object) LFCheck identifiers
- 23012 — Information notification · 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 about result of the affected market location
MSB (corresponds to MSB at the market location object) ÜNBCheck identifiers
- 23012 — Information notification · 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
Process information
Wording of the consolidated version, profile ch. 1.1, pp. 5–6.
Preconditions
The party reporting the fault detects a fault.
Results
Functioning technical equipment of the metering location.
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.
First message
MSB (corresponds to MSB on the metering location object) sends “Information on the fault to the metering location” (step 3). From here on, the party involved on this side is the one to act.
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-MELO — MSB at the metering location object · market role MSB
- View LF — LF
- View NB — NB
- View ÜNB — ÜNB · market role UENB
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 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: 3
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: 8