Device replacement — MSBA view
Process flow from the perspective of the MSB (MSBA)
Process steps
Notification of device replacement intent
MSBA MSBNZ10Z17Z18Check identifiers
- 17009 — Notification of device replacement intent · AS4
Flow
Message from MSBN · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
17009→Z1017009→Z1717009→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
MSBA MSBNCheck identifiers
Flow
Prozessauslöser
START_ANTWORT_GERAETEWECHSELThe backend triggers this step with this event.
Message to MSBN · AS4
Response per decision tree
19015,19016→E_200819016→ E_2007 · Check notification of device replacement intent and E_2008_Check whether self-installation is desired
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
MSBA MSBNZ10Z17Z18Check identifiers
- 21010 — Status message · AS4
Flow
Message from MSBN · AS4
APERAK checks
21010→Z1021010→Z1721010→Z18
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
MSBA MSBNMSCONSFlow
Message from MSBN · AS4
Load data for the incoming check
- Read meter
GET /getCounterBasic
- Read meter
APERAK checks
13002→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
Point in time of device removal
MSBA MSBNZ10Z17Z18Check identifiers
- 21036 — Status message · AS4
Flow
Message from MSBN · AS4
Load data for the incoming check
- Read metering location
GET /getMeterLocationBasic
- Read metering location
APERAK checks
21036→Z1021036→Z1721036→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 —
Decision trees of this process
| EBD | Name |
|---|---|
| E_2007 | Check notification of device replacement intent and E_2008_Check whether self-installation is desired |
Process information
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 source provides no use case profile for this process — objective, precondition and result are not recorded there.
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.
Step sequence reconstructed
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.
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.
For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body.
Applies to: 3
For these decision trees of the process there is no source in this format version:
E_2008