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)
Process steps
Activation of a MaBiS-ZP for the NZR
NB (responsible NB) NB (neighbouring NB)Check identifiers
- 55062 — Activation 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_0020 · NB · Check MaBiS-ZP activation
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
Activation of a MaBiS-ZP for the NZR
NB (responsible NB) BIKOCheck identifiers
- 55062 — Activation 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_0024 · BIKO · Check MaBiS-ZP activation
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_0020 | Check MaBiS-ZP activation |
| E_0024 | Check MaBiS-ZP activation |
Process information
Wording of the consolidated version, profile ch. 5.2.1, pp. 43–44.
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.
Results
The BIKO and the neighboring NB can assign the NZR to the MaBiS-ZP.
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).
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.
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.