# Activation of a MaBiS-ZP for the monthly curtailed energy transfer time series (AAÜZ) between NB and BKV (anfNB) — BIKO view The ANB activates a MaBiS-ZP of a AAÜZ and sends the corresponding information to the BIKO, which is accepted or rejected by the BIKO. On receipt, the BIKO forwards the activation of a MaBiS-ZP for a AAÜZ to the BKV (of the anfNB), provided the activation was correct. The BKV (of the anfNB) can inform the ANB of an activation that it considers faulty. In the event of an error message from the BKV, ANB and BKV (of the anfNB) clarify where the error lies and – if necessary – arrange for the error to be corrected. ## Process flow from the perspective of the BIKO \nSystem diagram: Aktivierung eines MaBiS-ZP für die monatliche Ausfallarbeitsüberführungszeitreihe (AAÜZ) zwischen NB und BKV (anfNB) — view of BIKO\n\n\nCustomer backend system\n\nMACO APP · BIKO\n\nMarket partner\n\n\n\n1. Aktivierung eines\nMABIS-ZP für die monatliche\nAAÜZ\n\nNB (ANB)\n\nAS4\n55209\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n2. Antwort\n\n\nNB (ANB)\n\nAS4\n55210\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Weiterleitung der\nAktivierung\n\n\nBKV (des anfNB)\n\nAS4\n55211\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Aktivierung eines MaBiS-ZP für die monatliche Ausfallarbeitsüberführungszeitreihe (AAÜZ) zwischen NB und BKV (anfNB) — view of BIKO\n\n\nBackend (customer)\n\n\nMACO APP · BIKO\n\n\nNB (ANB)\n\n\nBKV (des anfNB)\n\n\n1. Aktivierung eines MABIS-ZP für die monatliche…\nAS4 · PI 55209\n\nCreate transaction\nCreate process data\n\n2. Antwort\nAS4 · PI 55210 · E_0078\nE_0078 — MaBiS-ZP AAÜZ Aktivierung prüfen\n\nUpdate transaction\nUpdate process data\n\n4. Weiterleitung der Aktivierung\nAS4 · PI 55211\n\nUpdate transaction\nUpdate process data\n"} titel="BIKO" /> ## Process steps ### Activation of a MABIS-ZP for the monthly AAÜZ
**Check identifiers** - [55209](/en/schnittstellen/202604/pruefi/UTILMD/PI_55209) — Activation ZP monthly AAÜZ · AS4
**Flow**
  1. Message from **NB (ANB)** · AS4
  2. **Write endpoint** - Transaction created — `ERSTELLEN_PROZESSDATEN` Creates a new transaction in the backend with the data of the incoming message.
### Response
**Check identifiers** - [55210](/en/schnittstellen/202604/pruefi/UTILMD/PI_55210) — Response to activation ZP · AS4
**Flow**
  1. Message to **NB (ANB)** · AS4
    **Response per decision tree** - `55210` → [E_0078](/en/referenz/202604/ebd/E_0078) · BIKO · Check MaBiS-ZP AAÜZ activation
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
### Forwarding of the activation
**Check identifiers** - [55211](/en/schnittstellen/202604/pruefi/UTILMD/PI_55211) — Forwarding activation ZP · AS4
**Flow**
  1. Message to **BKV (of the anfNB)** · AS4
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
Decision trees of this process | EBD | Name | |---|---| | [E_0078](/referenz/202604/ebd/E_0078) | Check MaBiS-ZP AAÜZ activation |
## Process information Wording of the consolidated version, profile ch. 17.3.5.1.1, pp. 267–268.
  1. ### Preconditions The ANB has possible redispatch measures in the grid area for which it is not the requesting NB and for which no MaBiS-ZP for the AAÜZ is activated yet at the requesting NB.
  2. ### Results The BIKO can assign the AAÜZ to the MaBiS-ZP.
  3. ### Error case #### Result in the error case The BIKO and the BKV (of the anfNB) can assign the AAÜZ to a Ma-BiS-ZP. In the error case, the BKV (of the anfNB) can initiate the clearing process with the ANB.
  4. ### First message **NB (ANB)** sends “Activation 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.
  5. ### 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 ANB](/en/prozessdoku/202604/NB/MaBiS-aktivierung-eines-mabis-zp-fuer-die-monatliche-ausfallarbeitsueberfuehrungszeitreihe-aauez-zwischen-nb-und-bkv-anfnb) — connecting grid operator · market role NB - [View BKV-ANFNB](/en/prozessdoku/202604/BKV/MaBiS-aktivierung-eines-mabis-zp-fuer-die-monatliche-ausfallarbeitsueberfuehrungszeitreihe-aauez-zwischen-nb-und-bkv-anfnb) — balance responsible party of the requesting grid operator · market role BKV *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](#schritt-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. Applies to: [1](#schritt-1), [2](#schritt-2), [4](#schritt-4)