Transmission of the delta time series carry-over from ÜNB to BIKO and NB — BIKO 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 BIKO
Process steps
Transmission of DZÜ
BIKO ÜNBCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message from ÜNB · AS4
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Response
BIKO ÜNBCheck identifiers
- 21002 — Refusal · AS4
Flow
Message to ÜNB · AS4
Response per decision tree
21002→ E_0029 · BIKO · Check delta time series carry-over
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Forwarding of DZÜ
BIKO NBCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message to NB · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Decision trees of this process
| 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
ÜNB sends “Transmission DZÜ” (step 1). 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: 1
For this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button.