Determination and reconciliation of the billing-relevant curtailed energy – forecast model — NB view
Process flow from the perspective of the NB
Process steps
Determined curtailed energy
NB BTRCheck identifiers
- 13022 — Redispatch 2.0 individual time series curtailed energy · RD
Flow
Message to BTR · RD
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
Confirmation of curtailed energy
NB BTRZ33Check identifiers
- 21038 — View BTR · RD
Flow
Message from BTR · RD
Response per decision tree
21038→ E_0900 · BTR · Check of the curtailed energy
APERAK checks
21038→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
Rejection and transmission counterproposal
NB BTRZ33Check identifiers
Flow
Message from BTR · RD
APERAK checks
21038→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
Acceptance of counterproposal
NB BTRCheck identifiers
- 21037 — View NB · RD
Flow
Message to BTR · RD
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
Rejection counterproposal
NB BTRCheck identifiers
- 21037 — View NB · RD
Flow
Message to BTR · RD
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
Decision trees of this process
| EBD | Name |
|---|---|
| E_0900 | Check of the curtailed energy |
Process information
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.
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 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.