Deactivation of a MaBiS-ZP for the monthly curtailed energy transfer time series (AAÜZ) between NB and BKV (anfNB) — BIKO view
The ANB deactivates the activated MaBiS-ZP for a AAÜZ 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 AAÜZ to the BKV (of the anfNB), provided it has accepted the deactivation. The BKV (of the anfNB) can inform the ANB about a deactivation it considers incorrect. In the event of an error message from the BKV (of the anfNB), ANB and BKV (of the anfNB) 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 the monthly AAÜZ
BIKO NB (ANB)Check identifiers
- 55212 — Deactivation ZP monthly AAÜZ · AS4
Flow
Message from NB (ANB) · 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 NB (ANB)Check identifiers
- 55213 — Response to deactivation ZP · AS4
Flow
Message to NB (ANB) · AS4
Response per decision tree
55213→ E_0079 · BIKO · Check MaBiS-ZP AAÜZ 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
BIKO BKV (of the anfNB)Check identifiers
- 55214 — Forwarding deactivation ZP · AS4
Flow
Message to BKV (of the anfNB) · 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_0079 | Check MaBiS-ZP AAÜZ deactivation |
Process information
Wording of the consolidated version, profile ch. 17.3.5.2.1, pp. 271–272.
Preconditions
- The ANB has no redispatch measure in the grid area that the BKV (of the anfNB) has requested; however, a MaBiS-ZP for the AAÜZ is still activated.
Results
- The BIKO can initiate the forwarding of the deactivated MaBiS-ZP to the BKV (of the anfNB).
Error case
Result in the error case
- In the error case, BKV (of the anfNB) can initiate the clearing process with ANB.
Further requirements
After the point in time of deactivation, the MaBiS-ZP can no longer be used until it is activated again for the AAÜZ.
First message
NB (ANB) sends “Deactivation of a MABIS-ZP for the monthly AAÜZ” (step 1). From here on, it is the turn of the party covered by this page.
Objective
- The NB has deactivated the MaBiS-ZP for the AAÜZ at the BIKO.
- The BIKO has forwarded the deactivation of the MaBiS-ZP for the AAÜZ to the BKV (of the anfNB), and the BKV (of the anfNB) has accepted it. Error cases could be resolved between the BKV (of the anfNB) and NB via clearing.
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 ANB — connecting grid operator · market role NB
- View BKV-ANFNB — balance responsible party of the requesting grid operator · market role 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 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.