Device takeover — MSBA view
The MSBN of the metering location requests a device takeover quotation from the MSBA of the metering location. The MSBA of the metering location transmits, free of charge, a quotation for the purchase or use of the technical equipment of the individual metering location requested by the MSBN of the metering location, for the takeover date desired by the MSBN of the metering location. The components of the measuring equipment can be offered individually or in full. The MSBN of the metering location accepts the overall quotation or quotations for individual technical equipment as part of an order placement. Acceptance with regard to individual technical equipment at the same time constitutes implied rejection with regard to the remaining technical equipment offered by the MSBA of the metering location. The MSBA of the metering location confirms the ordered device takeover. If the measuring equipment itself is affected by the device takeover, the MSBA of the metering location transmits the meter reading for the device takeover to the MSBN of the metering location in the case of a kME or mME with active energy metering.
Process flow from the perspective of the MSB (MSBA)
Process steps
Request device takeover quotation
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)Z10Z17Z18Check identifiers
- 35001 — Request for device takeover quotation · 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 market location
APERAK checks
35001→Z1035001→Z1735001→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
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
Load data for the check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
Load data for processing
LESEN_ANFRAGE_BASIS- Read metering location
GET /getMeterLocationBasic
Device takeover quotation
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)Check identifiers
- 15001 — Quotation device takeover · AS4
Flow
Prozessauslöser
START_ANGEBOT_GERAETEUEBERNAHMEThe backend triggers this step with this event.
Load data for processing
- Read metering location
GET /getMeterLocationBasic - Read meter
GET /getCounterBasic
- Read metering location
Message to 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 once the message has been created.
- Transaction updated — Update process data
Order placement
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)Z33E_0247 Check order placement1900119002Check identifiers
- 17001 — Order placement device takeover quotation · AS4
Flow
Message from MSB (corresponds to MSBN at the metering location object) · AS4
APERAK checks
17001→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
Load data for the check
LESEN_ANGEBOT_BASIS
Decision tree
17001→ E_0247 — Check order placement
Trigger follow-up process
After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
Order confirmation
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)17001Check identifiers
Flow
Triggered by incoming message
- 17001 — Order placement device takeover quotation
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Load data for processing
LESEN_ANFRAGE_BASISLESEN_AUFTRAG_BASIS
Message to MSB (corresponds to MSBN at the metering location object) · AS4
Response per decision tree
19001,19002→ E_0247 · Check order placement
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
Meter reading for the device takeover
MSB (corresponds to MSBA at the metering location object) MSB (corresponds to MSBN at the metering location object)Check identifiers
- 13017 — Meter reading (electricity) · AS4
Flow
Prozessauslöser
START_ERHEBUNG_MESSWERTEThe backend triggers this step with this event.
Load data for processing
LESEN_ENERGIEMENGE_ZAEHLERSTAND_BASIS- Read meter
GET /getCounterBasic
Message to 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 once the message has been created.
- Transaction updated — Update process data
Decision trees of this process
| EBD | Name |
|---|---|
| E_0247 | Check order placement |
Process information
Wording of the consolidated version, profile ch. 3.2.1, pp. 48–49.
Preconditions
As a result of a MSB change (use case „Start of metering point operation“ or use case „Commitment gMSB“), the MSBN of the metering location or gMSB (represented in this use case as MSBN) of the metering location intends a device takeover.
Results
If the measuring equipment itself is affected by the device takeover, 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 the measuring equipment itself is affected by the device takeover, the MSB of the market location transmits values to the NB, LF and ÜNB (WiM part 2, chapter 2.4.3. „SD: Processing and transmission of values from the 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, the MSB of the market location must, in order to determine the energy quantity of the market location, collect values for the metering locations not affected by the device replacement/device takeover and, where necessary, request them from the MSB of the metering location.
First message
MSB (corresponds to MSBN on the metering location object) sends “Request for device takeover quotation” (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 takeover 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.
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.