Metering location change from NB to MSB — MSB-MELO view
Process flow from the perspective of the MSB (MSB-MELO)
Process steps
Request for a quotation for the metering location change
MSB (corresponds to MSB at the metering location object) NBZ10Z17Z18Check identifiers
- 35005 — Request for quotation for technical change · AS4
Flow
Message from NB · AS4
APERAK checks
35005→Z1035005→Z1735005→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
Quotation or rejection of the request
MSB (corresponds to MSB at the metering location object) NB35004Check identifiers
Flow
Triggered by incoming message
The MACO APP sends this message itself, as a follow-up process after this incoming message.
Message to NB · AS4
Response per decision tree
21033→ E_0278 · MSB · Check request
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 MSB at the metering location object) NBZ33Z10Z17Z18Check identifiers
- 17011 — Order placement quotation change of technology · AS4
Flow
Message from NB · AS4
APERAK checks
17011→Z3317011→Z1017011→Z1717011→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
Response to order placement
MSB (corresponds to MSB at the metering location object) NBCheck identifiers
Flow
Message to NB · AS4
Response per decision tree
19005,19006→ E_0279 · MSB · 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
Failure of the change
MSB (corresponds to MSB at the metering location object) NBCheck identifiers
- 21027 — Status message · AS4
Flow
Message to NB · AS4
Response per decision tree
21027→ E_0286 · MSB · Carry out metering location change
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_0278 | Check request |
| E_0279 | Check order placement |
| E_0286 | Carry out metering location change |
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 NB — NB
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 process begins for the own role with their message, so the transaction is created.
Applies to: 1
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
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.