Transmission of the monthly curtailed energy transfer time series (AAÜZ) — BKV-LF view
The ANB delivers the curtailed energy transfer time series for the time period under consideration to the BIKO; the BIKO forwards the monthly AAÜZ to the BKV (of the LF). The BKV have received the aggregated AAÜZ and check them. The curtailed energy per TR is aggregated per market location and totaled across all market locations of the suppliers of the balancing group.
Process flow from the perspective of the BKV (BKV-LF)
Process steps
1 Monthly AAÜZ
NB (ANB) BIKO
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 13020 — Curtailed energy transfer time series · AS4
Forwarding of the monthly AAÜZ
BKV (LF) BIKOCheck identifiers
- 13020 — Curtailed energy transfer time series · 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 the other parties involved
| EBD | Name |
|---|---|
| E_0073 | Check AAÜZ |
Process information
Wording of the consolidated version, profile ch. 17.3.3.3.1, pp. 257–258.
Preconditions
- Master data has been exchanged.
- Curtailed energy has been determined by the grid operator per balancing group (right of first proposal).
Results
- In balancing terms, the BKV (of the LF) of the installation is placed as if the redispatch measure had not taken place.
- The balancing group settlement for the BKV (of the LF) can be carried out.
- The BKV (of the LF) checks the monthly AAÜZ.
Further requirements
The BIKO books the AAÜZ into the redispatch BK of the BKV (of the NB).
First message
BIKO sends “Forwarding of the monthly AAÜZ” (step 3). From here on, it is the turn of the party involved on this page.
Objective
The monthly AAÜZ determined by the grid operator is available to the BIKO and to the BKV (of the LF).
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: 3
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: 3