Transmission of data status for the balancing group aggregated time series from BIKO to ÜNB and BKV — BIKO view
The BIKO transmits the data status to ÜNB and BKV for the BK-SZR (category B)
- after receipt of the BK-SZR (category B) from the ÜNB or
- after receipt of the validation notification from the BKV 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 BIKO
Process steps
Data status
BIKO BKVCheck identifiers
- 21004 — Status message · AS4
Flow
Message to BKV · AS4
Response per decision tree
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Data status
BIKO ÜNBCheck identifiers
- 21003 — Status message · AS4
Flow
Message to ÜNB · AS4
Response per decision tree
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_0026 | Assign data status after completed balancing group settlement |
| E_0042 | Assign data status after receipt of a balancing group aggregated time series (category B) |
| E_0043 | Assign data status once a validation notification is available |
Process information
Wording of the consolidated version, profile ch. 11.11.1, pp. 160–161.
Preconditions
- The BIKO has a BK-SZR (category B) transmitted by the ÜNB.
- The BIKO has forwarded the BK-SZR (category B) transmitted by the ÜNB to the BKV.
Results
All systems of BKV, 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 BK-SZR (category B).
Error cases
The algorithm applied by the BIKO for assigning the data status is faulty
First message
The party involved on this page is itself the sender of: „Data status“ to BKV (step 1).
Objective
The data status managed by the BIKO is available at the ÜNB and at the BKV for the BK-SZR (category B).
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 source does not yet name the event that triggers these steps.
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.