Deactivation of a MaBiS metering point for the grid time series — NBV 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 NB (NBV)
Process steps
Deactivation of a MaBiS-ZP for the NZR
NB (responsible NB) NB (neighbouring NB)Check identifiers
- 55063 — Deactivation of ZP · AS4
Flow
Message to NB (neighbouring NB) · 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 (responsible NB) NB (neighbouring NB)Z33Check identifiers
- 55064 — Response · AS4
Flow
Message from NB (neighbouring NB) · AS4
Response per decision tree
55064→ E_0010 · NB · Check MaBiS-ZP deactivation
APERAK checks
55064→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
Deactivation of a MaBiS-ZP for the NZR
NB (responsible NB) BIKOCheck identifiers
- 55063 — Deactivation of ZP · 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 (responsible NB) BIKOZ33Check identifiers
- 55064 — Response · AS4
Flow
Message from BIKO · AS4
Response per decision tree
55064→ E_0009 · BIKO · Check MaBiS-ZP deactivation
APERAK checks
55064→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
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
The party involved on this page is itself the sender of: „Deactivation of a MaBiS-ZP for the NZR“ to NB (adjacent NB) (step 1).
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.
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.
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.