Transmission of the grid time series — BIKO view
The responsible NB transmits the NZR agreed between the two NB at BG level to the BIKO.
Process flow from the perspective of the BIKO
Process steps
Transmission of NZR
BIKO NBCheck identifiers
- 13003 — Aggregated time series · 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 —
Response
BIKO NBCheck identifiers
- 21002 — Refusal · AS4
Flow
Message to NB · AS4
Response per decision tree
21002→ E_0008 · BIKO · Check NZR
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Decision trees of this process
| EBD | Name |
|---|---|
| E_0008 | Check NZR |
Process information
Wording of the consolidated version, profile ch. 5.5.1, p. 52.
Preconditions
- The MaBiS-ZP for the NZR is activated by the responsible NB at the BIKO for the relevant time period.
- The reconciliation of the NZR between the two NB has taken place.
- The version of the NZR agreed between the NB is known to the responsible NB.
Results
The BIKO can take the NZR into account for the calculation of the NB-DZR and transmit the data status (billing data/billing data KBKA) to the two NB.
Further requirements
The representation of the energy flow directions in the NZR is always transmitted from the point of view of the BG of the responsible NB. Within the BKA, the NZR transmitted to the BIKO is deemed to be the version agreed between the two NB. If there are differences between the agreed version and the NZR transmitted to the BIKO, this is to be clarified bilaterally between the two NB.
First message
NB sends “Transmission NZR” (step 1). From here on, the party involved on this page has the next move.
Objective
The BIKO has the version of the NZR agreed between the two 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 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.