Activation of a MaBiS metering point for the balancing group aggregated time series from the NB to BIKO and BKV — BKV view
The NB activates the MaBiS-ZP of a BK-SZR (category A) and sends the corresponding information to the BIKO, which the BIKO accepts or rejects. Once received, the BIKO forwards the activation of a MaBiS-ZP for a BK-SZR (category A) to the BKV, provided the activation was correct. The BKV can inform the NB about an activation it considers faulty. In the event of an error message from the BKV, the NB and the BKV clarify where the error lies and – if necessary – ensure that the error is corrected.
Process flow from the perspective of the BKV
Process steps
1 Activation of a MaBiS-ZP for the BK-SZR (category A)
NB BIKO
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55062 — Activation of ZP · AS4
Forwarding of the activated MaBiS-ZP for the BK-SZR (category A)
BKV BIKOCheck identifiers
- 55062 — Activation of ZP · AS4
Flow
Message from BIKO · AS4
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Decision trees of the other parties involved
| EBD | Name |
|---|---|
| E_0034 | Check MaBiS-ZP activation |
Process information
Wording of the consolidated version, profile ch. 10.4.1, pp. 123–124.
Preconditions
- The NB assigns the first market location with NB aggregation responsibility to a combination of BK, ZRT and BG for which no MaBiS-ZP for the BK-SZR (category A) is activated yet.
Results
- The BIKO and the BKV can assign the BK-SZR (category A) to a MaBiS-ZP.
First message
BIKO sends “Forwarding of the activated MaBiS-ZP for the BK-SZR (category A)” (step 4). From here on, it is the turn of the party involved on this page.
Objective
- The NB has activated the MaBiS-ZP for the corresponding BK-SZR (category A) at the BIKO.
- The BIKO has forwarded the MaBiS-ZP for the BK-SZR (category A) 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: 4
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.
Applies to: 4