Order placement for the aggregation level of the balancing group aggregated time series at control area level — ÜNB view
The BKV orders the BK-SZR (category B) at RZ level from the ÜNB for the specified BK as of the first of a month. The ÜNB records that the aggregation level RZ is agreed for this BK from that point in time and that the BKV therefore expects the BK-SZR (category B) at RZ level for this BK from that point in time.
Process flow from the perspective of the ÜNB
Process steps
Order placement for the RZ aggregation level
ÜNB BKVCheck identifiers
- 17207 — Order cancellation/placement BK-SZR at aggregation level RZ · AS4
Flow
Message from BKV · AS4
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Response
ÜNB BKVCheck identifiers
- 19204 — Rejection of order placement/withdrawal of the aggregation level · AS4
Flow
Message to BKV · AS4
Response per decision tree
19204→ E_0003 · ÜNB · Check order placement of aggregation level RZ
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_0003 | Check order placement of aggregation level RZ |
Process information
Wording of the consolidated version, profile ch. 11.8.1, p. 154.
Preconditions
A valid BK contract exists for the BK at the stated time of change.
Results
The ÜNB activates the MaBiS-ZP for the BK-SZR (category B) as well as all LF-SZR (category B) that are assigned to the MaBiS-ZP of the BK-SZR (category B), at RZ level from the agreed point in time for the BK.
First message
BKV sends “Order placement for the aggregation level RZ” (step 1). From here on, it is the turn of the party involved on this page.
Objective
The ÜNB knows the BK and the point in time from which it has to send the BK-SZR (category B) to the BKV at RZ level via the BIKO.
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 BKV — BKV
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.