Request for and transmission of the clearing list for the grid operator delta time series between BIKO and NB — BIKO view
The NB can request and receive the clearing list for an NB-DZR only for its own BG.
Process flow from the perspective of the BIKO
Process steps
Request clearing list NB-DZR
BIKO NBCheck identifiers
- 17205 — Req. clearing list DZR · AS4
Flow
Message from NB · AS4
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Error message request not correct
BIKO NBFlow
Message to NB
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Transmission of clearing list NB-DZR
BIKO NBCheck identifiers
- 55069 — Clearing list DZR · AS4
Flow
Message to NB · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Process information
Wording of the consolidated version, profile ch. 13.12.1, p. 203.
Preconditions
- The BIKO has activated a MaBiS-ZP for the NB-DZR.
- The BIKO has sent a version of an NB-DZR.
- The NB needs to view the clearing list in order to check the NB-DZR.
Further requirements
The clearing list is created and sent on request only (no subscription). For the BKA, the exchanged and billing-relevant NB DZR is authoritative, not the detailed data contained in the clearing list. Changes of data status are not carried forward within a clearing list.
First message
NB sends “Request for clearing list NB-DZR” (step 1). From here on, the party involved on this page has the next move.
Objective
The NB has received the clearing list for an NB-DZR and can thus trace the NB-DZR or trigger a clearing.
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 NB — NB
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.