Activation of a MaBiS metering point for the delta time series carry-over from the ÜNB to BIKO and NB — NB view
The ÜNB activates a MaBiS-ZP of a DZÜ and sends the corresponding information to the BIKO, which is accepted or rejected by the BIKO. On receipt, the BIKO forwards the activation of a MaBiS-ZP for a DZÜ to the NB, provided the activation was correct. The NB can inform the ÜNB of an activation that it considers faulty. In the event of an error message from the NB, ÜNB and NB clarify where the error lies and – if necessary – arrange for the error to be corrected.
Process flow from the perspective of the NB
Process steps
1 Activation of a MaBiS-ZP for the DZÜ
ÜNB BIKO
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55062 — Activation of ZP · AS4
Forwarding of the activated MaBiS-ZP for the DZÜ
NB BIKOCheck identifiers
- 55062 — Activation of ZP · AS4
Flow
Message from BIKO · AS4
Write endpoint
- Transaction created — Create process data
POST /createProcessData
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created — Create process data
Decision trees of the other parties involved
| EBD | Name |
|---|---|
| E_0027 | Check MaBiS-ZP activation |
Process information
Wording of the consolidated version, profile ch. 12.2.1, pp. 163–164.
Preconditions
The BG in the RZ without an active MaBiS-ZP exists for the DZÜ.
Results
- The BIKO and the NB can assign the DZÜ to a MaBiS-ZP.
First message
BIKO sends “Forwarding of the activated MaBiS-ZP for the DZÜ” (step 4). From here on, it is the turn of the party involved on this page.
Objective
- The ÜNB has activated the MaBiS-ZP for the corresponding DZÜ at the BIKO.
- The BIKO has forwarded the MaBiS-ZP for the DZÜ to the NB, and the NB 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 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 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: 4