Termination of the assignment of a grid load time series to a grid time series — ÜNB view
Process flow from the perspective of the ÜNB
Process steps
1 Termination of the assignment of the metering point of the NGZ to the NZR
NB (responsible NB of the NGZ) NB (neighbouring NB)
This step runs between other market partners and is not relevant for this view.
Check identifiers
- 55236 — Termination assignment ZP of the NGZ to the NZR · AS4
Information about the termination of the assignment of the metering point of the NGZ to the NZR
ÜNB NB (responsible NB of the NGZ)Check identifiers
- 55236 — Termination assignment ZP of the NGZ to the NZR · AS4
Flow
Message from NB (responsible NB of the NGZ) · AS4
Write endpoint
- Transaction created —
ERSTELLEN_PROZESSDATEN
Creates a new transaction in the backend with the data of the incoming message.
- Transaction created —
Decision trees of the other parties involved
| EBD | Name |
|---|---|
| E_0103 | Check termination of the assignment |
Process information
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 source provides no use case profile for this process — objective, precondition and result are not recorded there.
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.
Step sequence reconstructed
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.
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.
Applies to: 4