Deactivation of a MaBiS metering point for the balancing group aggregated time series from the NB to the BIKO and the BKV — NB view
The NB deactivates the activated MaBiS-ZP for a BK-SZR (category A) and sends the corresponding information to the BIKO, which the BIKO accepts or rejects. Once received, the BIKO forwards the deactivation of a MaBiS-ZP for a BK-SZR (category A) to the BKV, provided it has accepted the deactivation. The BKV can inform the NB about a deactivation it considers faulty. In the event of an error message from the BKV, the NB and the BKV clarify where the error lies and – if necessary – ensure that the error is corrected.
Process flow from the perspective of the NB
Process steps
Deactivation of a MaBiS-ZP for the BK-SZR (category A)
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 BIKOZ33Check identifiers
- 55064 — Response · AS4
Flow
Message from BIKO · AS4
Response per decision tree
55064→ E_0018 · 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
4 Forwarding of the deactivation of the MaBiS-ZP for the BK-SZR (category A)
BIKO BKV
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55063 — Deactivation of ZP · AS4
Decision trees of this process
| EBD | Name |
|---|---|
| E_0018 | Check MaBiS-ZP deactivation |
Process information
Wording of the consolidated version, profile ch. 10.5.1, pp. 126–127.
Preconditions
- The NB ends the assignment of the last market location with NB aggregation responsibility, and for whose assigned combination of BK, ZRT and BG a MaBiS-ZP for the BK-SZR (category A) is activated, and this MaBiS-ZP is activated at the BIKO.
Further requirements
After the point in time of deactivation, the MaBiS-ZP can no longer be used until it is activated again for the BK-SZR (category A).
First message
The party involved on this page is itself the sender of: „Deactivation of a MaBiS-ZP for the BK-SZR (category A)“ to BIKO (step 1).
Objective
- The NB has deactivated the MaBiS-ZP for the BK-SZR (category A) at the BIKO.
- The BIKO has forwarded the deactivation of the MaBiS-ZP for the BK-SZR (category A) 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.
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.
Applies to: 2
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.