NB (69)
E_0902 — Check plausibility of curtailed energy including the schedule share
Check plausibility of curtailed energy including the schedule share
| Attribute | Value |
|---|---|
| Designation | Check plausibility of curtailed energy including the schedule share |
| Market role | NB |
| Regulatory determination / chapter | Redispatch 2.0 |
| Section | 15.2.1: AD: Determination and reconciliation of the billing-relevant curtailed energy – planned value model |
| Check identifiers | Response: 21037 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Do the energy quantities of the outage energy time series or of the schedule share time series match the expected energy quantities? | yes | A01 | Cluster: Consent Consent |
| — | — | no | → Step 2 | — |
| 2 | Can a counterproposal be created? | yes | A02 | Cluster: Rejection Energy quantities incorrect / not plausible transmission of counterproposal Note: The identified problem must be described / named in the response. |
| — | — | no | A03 | Cluster: Rejection Energy quantities incorrect / not plausible incl. correction request Note: The identified problem must be described / named in the response. |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | Consent | Consent |
A02 | Rejection | Energy quantities incorrect / not plausible, transmission of counterproposal Note: The identified problem must be described / named in the response. |
A03 | Rejection | Energy quantities incorrect / not plausible incl. correction request Note: The identified problem must be described / named in the response. |
Notes on this page
Role of the numbers: »response« are the check identifiers that list this tree in the ebd_code column of the check identifier table (knowledge-collection · FV 202610); »checked« is the difference set to it from the return path of the process steps.
Not checked against a process
No consistency check was carried out for this decision tree — no generated BPMN found. Whether the MACO APP implements this tree completely is therefore not evidenced here.