BIKO (46)
E_0012 — Check MaBiS-ZP deactivation
Check MaBiS-ZP deactivation
| Attribute | Value |
|---|---|
| Designation | Check MaBiS-ZP deactivation |
| Market role | BIKO |
| Regulatory determination / chapter | MaBiS |
| Section | 7.37.1: AD: Deactivation of a MaBiS metering point for the balancing group aggregated time series from ÜNB to BIKO and BKV |
| Check identifiers | Response: 55064 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Does the deactivation take place after expiry of the clearing deadline for the KBKA? | yes | A01 | Cluster: Rejection Deadline exceeded |
| — | — | no | → Step 2 | — |
| 2 | Does the deactivation take effect as of the first day of the month, 00:00? | no | A02 | Cluster: Rejection Selected point in time not permitted |
| — | — | yes | → Step 3 | — |
| 3 | Is the balancing area valid in the control area of the BIKO at the point in time of the deactivation? | no | A03 | Cluster: Rejection Balancing area not valid |
| — | — | yes | → Step 4 | — |
| 4 | Is the MaBiS-ZP already deactivated at the point in time of the deactivation? | yes | A04 | Cluster: Rejection MaBiS-ZP already deactivated |
| — | — | no | → Step 5 | — |
| 5 | Do time series after the point in time of the deactivation already exist for the MaBiS-ZP? | yes | A05 | Cluster: Rejection Deactivation, time series present |
| — | — | no | A06 | Cluster: Consent Deactivation carried out |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | Rejection | Deadline exceeded |
A02 | Rejection | Selected point in time not permitted |
A03 | Rejection | Balancing area not valid |
A04 | Rejection | MaBiS-ZP already deactivated |
A05 | Rejection | Deactivation, time series present |
A06 | Consent | Deactivation carried out |
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.