Activation 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 activates a MaBiS-ZP of a AAÜZ and sends the corresponding information to the BIKO, which the BIKO accepts or rejects after a formal check (master data). Once received, the BIKO forwards the activation of a MaBiS-ZP for a AAÜZ to the BKV (of the LF), provided the activation was correct. The BKV (of the LF) can inform the ANB about an activation it considers faulty. In the event of an error message from the BKV (of the LF), the NB and the BKV (of the LF) clarify where the error lies and – if necessary – ensure that the error is corrected.
Process flow from the perspective of the NB (ANB)
Process steps
Activation of a MABIS-ZP for the monthly AAÜZ
NB (ANB) BIKOCheck identifiers
- 55203 — Activation 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
- 55204 — Response to activation ZP · AS4
Flow
Message from BIKO · AS4
Response per decision tree
55204→ E_0071 · BIKO · Check MaBiS-ZP AAÜZ activation
APERAK checks
55204→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 activation
BIKO BKV (of the LF)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55205 — Forwarding activation ZP · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_0071 | Check MaBiS-ZP AAÜZ activation |
Process information
Wording of the consolidated version, profile ch. 17.3.3.1.1, pp. 249–250.
Preconditions
The NB has a BK with a possible redispatch measure for which no MaBiS-ZP has been activated yet for the AAÜZ.
Results
The BIKO and the BKV (of the LF) can assign the AAÜZ to the MaBiS-ZP.
Error case
Result in the error case
In the error case, the BKV (of the LF) can initiate the clearing process with the NB.
First message
The party involved on this page sends this itself: “Activation of a MABIS-ZP for the monthly AAÜZ” to BIKO (step 1).
Objective
- The NB has activated the MaBiS-ZP for the corresponding AAÜZ at the BIKO.
- The BIKO has forwarded the MaBiS-ZP for the AAÜZ 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.
- 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.