Transmission of data status for the balancing area aggregate time series from BIKO to ÜNB and NB — View NB
The BIKO transmits the data status to the ÜNB and NB for the BG-SZR (category B)
- after receipt of the BG-SZR (category B) from the ÜNB or
- after receipt of the validation notification from the NB 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 NB
Process steps
Data status
NB BIKOZ33Check identifiers
- 21004 — Status message · AS4
Flow
Message from BIKO · AS4
Response per decision tree
APERAK checks
21004→Z33
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
2 Data status
BIKO ÜNB
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21003 — Status message · AS4
Response per decision tree
Decision trees of this process
| EBD | Name |
|---|---|
| E_0053 | Assign data status after completed balancing group settlement |
| E_0054 | Assign data status after receipt of a balancing area aggregate time series (category B) |
| E_0055 | Assign data status once a validation notification is available |
Process information
Wording of the consolidated version, profile ch. 9.9.1, pp. 116–117.
Preconditions
- The BIKO has a BG-SZR (category B) transmitted by the ÜNB.
- The BIKO has forwarded the BG-SZR (category B) transmitted by the ÜNB to the NB.
Results
All systems of NB, 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 BG-SZR (category B).
Error cases
The algorithm applied by the BIKO for assigning the data status is faulty.
First message
BIKO sends “Data status” (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 at the ÜNB and at the NB for the BG-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 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 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.
Applies to: 1