Transmission of data status for the monthly curtailed energy transfer time series (AAÜZ) between NB and BKV (anfNB) — BKV-ANFNB view
The BIKO transmits the data status for the AAÜZ to the BKV (of the anfNB) and to the ANB.
- after receipt of the AAÜZ from the NB or
- after receipt of the validation notification from the BKV (anfNB) or
- after use of the AAÜZ for the BKA (without KBKA) or the KBKA.
Process flow from the perspective of the BKV (BKV-ANFNB)
Process steps
Data status for the monthly AAÜZ
BKV (of the anfNB) BIKOCheck identifiers
- 21004 — 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 —
2 Data status for the monthly AAÜZ
BIKO NB (ANB)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21003 — Status message · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_0082 | Assign data status AAÜZ after completed BKA |
| E_0083 | Assign data status after receipt of a AAÜZ |
| E_0084 | Assign data status once a validation notification for the AAÜZ is available |
Process information
Wording of the consolidated version, profile ch. 17.3.5.5.1, pp. 280–281.
Results
All systems of BKV, ANB and BIKO hold the same data status for a version of the AAÜZ.
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 AAÜZ.
Error cases
The algorithm applied by the BIKO for assigning the data status is faulty.
First message
BIKO sends “Data status for the monthly AAÜZ” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The data status managed by the BIKO is available to the BKV (of the anfNB and of the ANB) for the AAÜZ.
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.
Applies to: 1