Deactivation of a MaBiS metering point for the balancing group aggregated time series from the ÜNB to the BIKO and the BKV — BIKO view
The ÜNB deactivates the activated MaBiS-ZP for a BK-SZR (category B) and sends the corresponding information to the BIKO, which is accepted or rejected by the BIKO. After receipt, the BIKO forwards the deactivation of a MaBiS-ZP for a BK-SZR (category B) to the BKV, provided it has accepted the deactivation. The BKV can inform the ÜNB about a deactivation it considers incorrect. In the event of an error message from the BKV, ÜNB and BKV clarify where the error lies and – if necessary – ensure that the error is corrected.
Process flow from the perspective of the BIKO
Process steps
Deactivation of a MaBiS-ZP for BK-SZR (category B)
BIKO ÜNBCheck identifiers
- 55063 — Deactivation of ZP · 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
- 55064 — Response · AS4
Flow
Message to ÜNB · AS4
Response per decision tree
55064→ E_0012 · BIKO · Check MaBiS-ZP deactivation
Write endpoint
- Transaction updated —
AKTUALISIEREN_PROZESSDATEN
Updates the existing transaction in the backend once the message has been created.
- Transaction updated —
Forwarding of the deactivation of the MaBiS-ZP for BK-SZR (category B)
BIKO BKVCheck identifiers
- 55063 — Deactivation of ZP · AS4
Flow
Message to BKV · AS4
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_0012 | Check MaBiS-ZP deactivation |
Process information
Wording of the consolidated version, profile ch. 11.3.1, pp. 144–145.
Preconditions
- The ÜNB has been informed by the NB responsible for the BG about the end of the assignment of the last market location with ÜNB aggregation responsibility, for whose assigned combination of BK, ZRT and RZ/BG a MaBiS-ZP for the BK-SZR (category B) is activated, and this MaBiS-ZP is activated at the BIKO, or
- The order cancellation of the aggregation level of a MaBiS-ZP for the BK-SZR (category B) at the level of the RZ is available from the BKV, and this MaBiS-ZP is activated at the BIKO.
Further requirements
After the point in time of deactivation, the MaBiS-ZP can no longer be used until it is activated again for the BK-SZR (category B).
First message
ÜNB sends “Deactivation of a MaBiS-ZP for BK-SZR (category B)” (step 1). From here on, it is the turn of the party involved on this page.
Objective
- The ÜNB has deactivated the MaBiS-ZP for the BK-SZR (category B) at the BIKO.
- The BIKO has forwarded the deactivation of the MaBiS-ZP for the BK-SZR (category B) to the BKV, and the BKV has accepted it and, in the error case, initiated clearing with the ÜNB where applicable.
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.
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 numbers are those of the source; where one is missing, it is missing there.
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.