Deactivation of a MaBiS-ZP for the monthly curtailed energy transfer time series (AAÜZ) between NB and BKV (of the LF) — ANB view
The NB deactivates the activated MaBiS-ZP for a AAÜZ and sends the corresponding information to the BIKO, which the BIKO accepts or rejects. Once received, the BIKO forwards the deactivation of a MaBiS-ZP for a AAÜZ to the BKV (of the LF), provided it has accepted the deactivation. The BKV (of the LF) can inform the NB about a deactivation it considers faulty.
Process flow from the perspective of the NB (ANB)
Process steps
Deactivation of a MABIS ZP for the monthly AAÜZ
NB (ANB) BIKOCheck identifiers
- 55206 — Deactivation ZP monthly AAÜZ · AS4
Flow
Message to BIKO · AS4
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend once the message has been created.
- Transaction updated — Update process data
Response
NB (ANB) BIKOZ33Check identifiers
- 55207 — Response to deactivation ZP · AS4
Flow
Message from BIKO · AS4
Response per decision tree
55207→ E_0072 · BIKO · Check MaBiS-ZP AAÜZ deactivation
APERAK checks
55207→Z33
Write endpoint
- Transaction updated — Update process data
POST /updateProcessData
Updates the existing transaction in the backend with the data of the incoming message.
- Transaction updated — Update process data
4 Forwarding of the deactivation
BIKO BKV (of the LF)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55208 — Forwarding deactivation ZP · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_0072 | Check MaBiS-ZP AAÜZ deactivation |
Process information
Wording of the consolidated version, profile ch. 17.3.3.2.1, pp. 253–254.
Preconditions
- The NB has ended the assignment of the last market location with possible redispatch measures at the BKV, for whose assigned combination of BK, BG and BKV a MaBiS-ZP for the AAÜZ is activated.
Results
- The BIKO can initiate the forwarding of the deactivated MaBiS-ZP to the BKV (of the LF).
Error case
Result in the error case
- In the error case, BKV (of LF) can initiate the clearing process with NB.
- In the event of an error message from the BKV (of the LF), NB and BKV (of the LF) clarify where the error lies and – if necessary – arrange for the error to be corrected.
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
The party involved on this page is itself the sender of: „Deactivation of a MABIS-ZP for the monthly AAÜZ“ to BIKO (step 1).
Objective
The NB has deactivated the MaBiS-ZP for the AAÜZ with the BIKO. The BIKO has forwarded the deactivation of the MaBiS-ZP for the AAÜZ to the BKV (of the LF), and the BKV (of the LF) has adopted it and, in the error case, triggered a clearing with the NB where necessary.
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 BIKO — BIKO
- View BKV-LF — balance responsible party of the supplier · 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 source does not yet name the event that triggers these steps.
Applies to: 1
The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists.
Applies to: 2
For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body.