Deactivation of a MaBiS metering point for the grid time series — BIKO view
The responsible NB deactivates at the neighbouring NB the activated MaBiS-ZP to which the NZR between two BG is assigned. If the neighbouring NB consents to the deactivation, or if the manual error clarification with the neighbouring NB is successful after the latter has rejected the deactivation, the responsible NB also deactivates this MaBiS-ZP at the BIKO.
Process flow from the perspective of the BIKO
Process steps
1 Deactivation of a MaBiS-ZP for the NZR
NB (responsible NB) NB (neighbouring NB)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55063 — Deactivation of ZP · AS4
Deactivation of a MaBiS-ZP for the NZR
BIKO NB (responsible NB)Check identifiers
- 55063 — Deactivation of ZP · AS4
Flow
Message from NB (responsible NB) · 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 (responsible NB)Check identifiers
- 55064 — Response · AS4
Flow
Message to NB (responsible NB) · AS4
Response per decision tree
55064→ E_0009 · BIKO · Check MaBiS-ZP deactivation
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_0009 | Check MaBiS-ZP deactivation |
| E_0010 | Check MaBiS-ZP deactivation |
Process information
Wording of the consolidated version, profile ch. 5.3.1, pp. 47–48.
Preconditions
- A NZR is no longer relevant due to a change of the grid topology.
- Metering-based delimitation of the neighbouring BG is ensured.
- The BIKO and the neighbouring NB have an activated MaBiS-ZP.
Further requirements
After the point in time of deactivation, the MaBiS-ZP can no longer be used until it is activated again for the NZR.
First message
NB (responsible NB) sends “Deactivation of a MaBiS-ZP for the NZR” (step 4). From here on, it is the turn of the party involved on this page.
Objective
The responsible NB has successfully deactivated the MaBiS-ZP to which the corresponding NZR is assigned 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 — neighbouring grid operator · market role NB
- View NBV — responsible grid operator · market role NB
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: 4
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.