# Activation of a MaBiS metering point for the grid time series — NBV view The responsible NB activates a Ma-BiS-ZP at the neighbouring NB in order to be able to assign the NZR between two BG to it. If the neighbouring NB consents to the activation, or if the manual error clarification with the neighbouring NB is successful after the latter has rejected the activation, the responsible NB also activates this MaBiS-ZP at the BIKO. ## Process flow from the perspective of the NB (NBV) \nSystem diagram: Aktivierung eines MaBiS-Zählpunkts für die Netzzeitreihe — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB (verantwort…\n\nMarket partner\n\n\n\n1. Aktivierung eines\nMaBiS-ZP für die NZR\n\nNB (benachbarter NB)\n\nAS4\n55062\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort\n\n\nNB (benachbarter NB)\n\nAS4\n55064\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Aktivierung eines\nMaBiS-ZP für die NZR\n\n\nBIKO\n\nAS4\n55062\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Antwort\n\n\nBIKO\n\nAS4\n55064\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Aktivierung eines MaBiS-Zählpunkts für die Netzzeitreihe — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB (verantwort…\n\n\nNB (benachbarter NB)\n\n\nBIKO\n\n\n1. Aktivierung eines MaBiS-ZP für die NZR\nAS4 · PI 55062\n\nUpdate transaction\nUpdate process data\n\n2. Antwort\nAS4 · PI 55064 · E_0020\nE_0020 — MaBiS-ZP Aktivierung prüfen\n\nUpdate transaction\nUpdate process data\n\n4. Aktivierung eines MaBiS-ZP für die NZR\nAS4 · PI 55062\n\nUpdate transaction\nUpdate process data\n\n5. Antwort\nAS4 · PI 55064 · E_0024\nE_0024 — MaBiS-ZP Aktivierung prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="NBV" /> ## Process steps ### Activation of a MaBiS-ZP for the NZR
**Check identifiers** - [55062](/en/schnittstellen/202610/pruefi/UTILMD/PI_55062) — Activation of ZP · AS4
**Flow**
  1. Message to **NB (neighbouring NB)** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response
**Check identifiers** - [55064](/en/schnittstellen/202610/pruefi/UTILMD/PI_55064) — Response · AS4
**Flow**
  1. Message from **NB (neighbouring NB)** · AS4
    **Response per decision tree** - `55064` → [E_0020](/en/referenz/202610/ebd/E_0020) · NB · Check MaBiS-ZP activation
  2. **APERAK checks** - `55064` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
### Activation of a MaBiS-ZP for the NZR
**Check identifiers** - [55062](/en/schnittstellen/202610/pruefi/UTILMD/PI_55062) — Activation of ZP · AS4
**Flow**
  1. Message to **BIKO** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response
**Check identifiers** - [55064](/en/schnittstellen/202610/pruefi/UTILMD/PI_55064) — Response · AS4
**Flow**
  1. Message from **BIKO** · AS4
    **Response per decision tree** - `55064` → [E_0024](/en/referenz/202610/ebd/E_0024) · BIKO · Check MaBiS-ZP activation
  2. **APERAK checks** - `55064` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_0020](/referenz/202610/ebd/E_0020) | Check MaBiS-ZP activation | | [E_0024](/referenz/202610/ebd/E_0024) | Check MaBiS-ZP activation |
## Process information Wording of the consolidated version, profile ch. 5.2.1, pp. 43–44.
  1. ### Preconditions - With regard to the two adjoining BGs, the two neighbouring NB have agreed in advance of a grid time series formation which of the two NB assumes the tasks of the “responsible NB” in the overall process “Exchange processes for the NZR”. - The two BG are set up and known for the affected time period. - The metering-based delimitation of the two adjacent BG is ensured for the affected time period.
  2. ### Results The BIKO and the neighboring NB can assign the NZR to the MaBiS-ZP.
  3. ### First message The party involved on this page sends this itself: “Activation of a MaBiS-ZP for the NZR” to **NB (neighboring NB)** (step 1).
  4. ### Objective The responsible NB has activated the MaBiS-ZP for the corresponding NZR at the neighbouring NB and at the BIKO.
## 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 NBB](/en/prozessdoku/202610/NB--NBB/MaBiS-aktivierung-eines-mabis-zaehlpunkts-fuer-die-netzzeitreihe) — neighbouring grid operator · market role NB - [View BIKO](/en/prozessdoku/202610/BIKO/MaBiS-aktivierung-eines-mabis-zaehlpunkts-fuer-die-netzzeitreihe) — BIKO *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](#schritt-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](#schritt-2), [5](#schritt-5) 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. Applies to: [1](#schritt-1), [2](#schritt-2), [4](#schritt-4), [5](#schritt-5)