Device takeover — MSBA view
Process flow from the perspective of the MSB (MSBA)
Process steps
Request device takeover quotation
MSBA MSBNZ10Z17Z18Check identifiers
- 35001 — Request for device takeover quotation · AS4
Flow
Message from MSBN · 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
MSBA MSBNCheck 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 MSBN · 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
MSBA MSBNZ33G_0061_G_0074 Check order placement (Gas)1900119002Check identifiers
- 17001 — Order placement device takeover quotation · AS4
Flow
Message from MSBN · 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→G_0061_G_0074— Check order placement (Gas)
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
MSBA MSBN17001Check 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 MSBN · AS4
Response per decision tree
19001,19002→ E_2011 · 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
Decision trees of this process
| EBD | Name |
|---|---|
| E_2011 | Check order placement |
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.
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.
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.