Transmission of data status of the delta time series transfer from BIKO to ÜNB and NB — View ÜNB
The BIKO transmits the data status to the ÜNB and NB for the DZÜ
- after receipt of the DZÜ from the ÜNB (start with status „check data or
- after receipt of the validation notification from the NB or
- after use of the aggregated time series for the BKA (without KBKA) or the KBKA. The data status is sent regardless of whether it has changed or not.
Process flow from the perspective of the ÜNB
Process steps
1 Data status
BIKO NB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21004 — Status message · AS4
Data status
ÜNB BIKOCheck identifiers
- 21003 — Status message · AS4
Flow
Message from BIKO · AS4
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Decision trees of this process
| EBD | Name |
|---|---|
| E_0059 | Assign data status after completed balancing group settlement |
| E_0061 | Assign data status once a validation notification is available |
Process information
Wording of the consolidated version, profile ch. 12.7.1, pp. 176–177.
Preconditions
- The BIKO has a DZÜ transmitted by the ÜNB.
- The BIKO has forwarded the DZÜ transmitted by the ÜNB to the NB.
Results
All systems of NB, BIKO and ÜNB hold the same data status for a version of the aggregated time series.
Error case
Result in the error case
The BIKO informs all affected market participants and, after the error has been corrected, ensures that the correct data status is assigned to all affected DZÜ.
Error cases
The algorithm applied by the BIKO for assigning the data status is faulty.
First message
BIKO sends “Data status” (step 2). From here on, it is the turn of the party involved on this page.
Objective
The data status managed by the BIKO is available at the ÜNB and at the NB for the DZÜ.
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: 2
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.
Applies to: 2
For these decision trees of the process there is no source in this format version:
E_0060