Device replacement — MSBA 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 (MSBA)
Process steps
Notification of device replacement intent
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)Z10Z18Check identifiers
- 17009 — Notification of device replacement intent · AS4
Flow
Message from MSB (corresponds to MSBN at the metering location object) · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
17009→Z1017009→Z18
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN_BASIS
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN_BASIS
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Load data for the check
- Read metering location
GET /getMeterLocationBasic - Read meter
GET /getCounterBasic
- Read metering location
Response
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)Check identifiers
Flow
Prozessauslöser
START_ANTWORT_GERAETEWECHSELThe backend triggers this step with this event.
Message to MSB (corresponds to MSBN at the metering location object) · AS4
Response per decision tree
19015,19016→ E_0204 · Check notification of device replacement intent
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN_BASIS
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Point in time of takeover of metering point operation
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)Check identifiers
- 21010 — Status message · AS4
Flow
Message from MSB (corresponds to MSBN 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
Meter reading and point in time of the device removal
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)MSCONSCheck identifiers
- 13017 — Meter reading (electricity) · AS4
Flow
Message from MSB (corresponds to MSBN at the metering location object) · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read metering location
GET /getMeterLocationBasic - Read meter
GET /getCounterBasic
- Read market location
APERAK checks
13017→MSCONS
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
Load data for processing
LESEN_ENERGIEMENGE_ZAEHLERSTAND_BASIS- Read meter
GET /getCounterBasic
Point in time of device removal
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)Z10Check identifiers
- 21036 — Status message · AS4
Flow
Message from MSB (corresponds to MSBN at the metering location object) · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
21036→Z10
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN_BASIS
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN_BASIS
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated —
Decision trees of this process
| EBD | Name |
|---|---|
| E_0204 | Check notification of device replacement intent |
Process information
Wording of the consolidated version, profile ch. 3.1.1, pp. 41–42.
Preconditions
- Following a MSB change (use case “Start of metering point operation” or use case “Obligation 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.
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“ (WiM part 2).
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”). 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.
First message
MSB (corresponds to MSBN on the metering location object) sends “Notification of intended device replacement” (step 1). From here on, the party involved on this side is the one to act.
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 MSBN — the receiving MSB · market role MSB
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.
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
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: 3
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.