Transmission of the balancing group aggregated time series from NB to BIKO and BKV — NB 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 NB
Process steps
Transmission of BK-SZR (category A)
NB BIKOCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message to BIKO · AS4
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Response
NB BIKOCheck identifiers
- 21002 — Refusal · AS4
Flow
Message from BIKO · AS4
Response per decision tree
21002→ E_0038 · BIKO · Check balancing group aggregated time series (category A)
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
3 Forwarding of BK-SZR (category A)
BIKO BKV
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 13003 — Aggregated time series · AS4
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
The party involved on this page is itself the sender of: „Transmission of BK-SZR (category A)“ to BIKO (step 1).
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 source does not yet name the event that triggers these steps.
Applies to: 1
The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists.
Applies to: 2
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.