BIKO (46)
E_0023 — Check balancing group aggregated time series (category B)
Check balancing group aggregated time series (category B)
| Attribute | Value |
|---|---|
| Designation | Check balancing group aggregated time series (category B) |
| Market role | BIKO |
| Regulatory determination / chapter | MaBiS |
| Section | 7.43.1: AD: Transmission of the balancing group aggregated time series from ÜNB to BIKO and BKV |
| Check identifiers | Response: 21002 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Is the time series received after expiry of the clearing deadline for the KBKA? | yes | A01 | Deadline exceeded |
| — | — | no | → Step 2 | — |
| 2 | Is the MaBiS-ZP active in the balancing month under consideration? | no | A02 | Selected time period not permitted |
| — | — | yes | → Step 3 | — |
| 3 | Is the deadline of 2 WT before the required dispatch of the time series after the activation met? | no | A03 | Deadline undershot |
| — | — | yes | → Step 4 | — |
| 4 | Does the version of the time series of MaBiS-ZP for this balancing month already exist? | yes | A04 | Time series already exists |
| — | — | no | → Step 5 | — |
| 5 | Has the BKV cancelled the subscription for aggregation level RZ for the BK of this MaBiS-ZP in this balancing month? | yes | → Step 7 | — |
| — | — | no | → Step 6 | — |
| 6 | Has the BKV already notified for this balancing month that the further checks must take place at BG level? | yes | → Step 7 | — |
| — | — | no | End | — |
| 7 | Is the version of the time series of the MaBiS-ZP higher than the highest version of the time series processed so far for this balancing month and this MaBiS-ZP? | no | A05 | Version not permitted |
| — | — | yes | End | — |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | — | Deadline exceeded |
A02 | — | Selected time period not permitted |
A03 | — | Deadline undershot |
A04 | — | Time series already exists |
A05 | — | Version not permitted |
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.