Transmission of the delta time series carry-over from ÜNB to BIKO and NB — NB view
The ÜNB delivers the DZÜ for the time period under consideration to the BIKO. The BIKO forwards the DZÜ to the NB, provided it is not to be rejected.
Process flow from the perspective of the NB
Process steps
1 Transmission of DZÜ
ÜNB BIKO
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 13003 — Aggregated time series · AS4
Forwarding of DZÜ
NB BIKOCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message from BIKO · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read meter
GET /getCounterBasic
- Read market location
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
Decision trees of the other parties involved
| EBD | Name |
|---|---|
| E_0029 | Check delta time series carry-over |
Process information
Wording of the consolidated version, profile ch. 12.5.1, p. 172.
Preconditions
- The ÜNB has activated the MaBiS-ZP for the DZÜ at the BIKO for the time period under consideration.
Results
- The NB can check the plausibility of the DZÜ on the basis of the data of the DZÜ list.
- The BIKO can determine the data status.
First message
BIKO sends “Forwarding of DZÜ” (step 3). From here on, it is the turn of the party involved on this page.
Objective
- The DZÜ formed by the ÜNB is available at the BIKO.
- The NB has received the DZÜ from the BIKO and can check it against its data.
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.
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 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: 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.
Applies to: 3