Transmission of the settlement aggregated time series for balancing group settlement from BIKO to NB — NB view
The BIKO determines a preliminary NB-DZR of a BG within the BKA, assigns it to the BK named by the NB and transmits it to the NB. After the BKA has expired, the BIKO determines the final NB-DZR of a BG, assigns it to the BK named by the NB and transmits it to the NB.
Process flow from the perspective of the NB
Process steps
Transmission of NB-DZR
NB BIKOCheck identifiers
- 13003 — Aggregated time series · AS4
Flow
Message from BIKO · AS4
Load data for the incoming check
- Read market location
GET /getMarketLocationBasic - Read meter
GET /getCounterBasic
- Read market location
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
Process information
Wording of the consolidated version, profile ch. 13.9.1, pp. 196–197.
Preconditions
- The NB has named a BK for its BG to which the NB-DZR is assigned.
- The MaBiS-ZP for the NB-DZR was activated by the BIKO at the NB.
- The BIKO has determined the NB-DZR.
Results
The NB starts analysing the causes of the energy allocation as early as the transmission of the preliminary NB-DZR for the BKA and initiates the clearing with the market partners.
First message
BIKO sends “Transmission NB-DZR” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The settlement aggregated time series has been transmitted by the BIKO to the 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.
- View BIKO — BIKO
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