Transmission of the balancing group aggregated time series from NB to BIKO and BKV — BIKO view
The NB delivers the BK-SZR (category A) for the time period under consideration to the BIKO. The BIKO forwards the BK-SZR (category A) to the BKV, provided it is not to be rejected.
Process flow from the perspective of the BIKO
Process steps
Transmission of BK-SZR (category A)
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_0038 · BIKO · Check balancing group aggregated time series (category A)
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Forwarding of BK-SZR (category A)
BIKO BKVCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message to BKV · 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_0038 | Check balancing group aggregated time series (category A) |
Process information
Wording of the consolidated version, profile ch. 10.9.1, pp. 133–134.
Preconditions
The NB has activated the MaBiS-ZP for the BK-SZR (category A) with the BIKO for the time period under consideration.
Results
The BIKO can determine the data status (the data status depends on the receipt date of the data at the BIKO).
Error case
Error cases
- The deadline has been exceeded.
- The MaBiS-ZP is not active.
Further requirements
Irrespective of the balancing procedure, the NB has to transmit the DBA for the respective BG to the BIKO. Aggregated time series that are received by the BIKO after the clearing deadline of the BKA (without KBKA) has expired and whose version differs from the highest version with “billing data” enter the clearing phase for the KBKA and are given the data status “check data”.
First message
NB sends “Transmission BK-SZR (category A)” (step 1). From here on, the party involved on this page has the next move.
Objective
- The BK-SZR (category A) formed by NB is available to BIKO.
- The BKV has received the BK-SZR (category A) 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.