Transmission of data status of the grid time series — View NBV
The BIKO assigns and transmits the data status of the NZR to the responsible and the neighboring NB.
Process flow from the perspective of the NB (NBV)
Process steps
Transmission of the data status of the NZR
NB (responsible NB) BIKOCheck identifiers
- 21004 — Status message · AS4
Flow
Message from BIKO · AS4
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 Transmission of the data status of the NZR
BIKO NB (neighbouring NB)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 21004 — Status message · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_0066 | Assign data status after completed balancing group settlement |
| E_0067 | Assign data status after receipt of a grid time series |
Process information
Wording of the consolidated version, profile ch. 5.6.1, p. 54.
Preconditions
The BIKO has the NZR agreed between the two NB.
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 NZR.
Error cases
The algorithm applied by the BIKO for assigning the data status is faulty.
Further requirements
A NZR can receive only the data status „billing data“ or „billing data KBKA“, or, at the billing cut-off dates, the changed data status „billed data“ or „billed data KBKA“.
First message
BIKO sends “Transmission of the data status of the NZR” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The data status of the NZR assigned by the BIKO is available to both NB.
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