Forwarding of EEG transfer time series — View BIKO
Process flow from the perspective of the BIKO
Process steps
Forwarding of transfer time series
BIKO BKV (NB)Flow
Message to BKV (NB) · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Forwarding of transfer time series
BIKO BKV (ÜNB)Flow
Message to BKV (ÜNB) · AS4
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Information on transfer time series
BIKO NBFlow
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
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
- View BKV-NB — balance responsible party of the grid operator · market role BKV
- View BKV-UENB — balance responsible party of the transmission system operator · market role BKV
Notes on this page
The source provides no use case profile for this process — objective, precondition and result are not recorded there.
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.
Step sequence reconstructed
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.
The source does not yet name the event that triggers these steps.
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.