NB (69)
E_0470 — Check disconnection order
Check disconnection order
| Attribute | Value |
|---|---|
| Designation | Check disconnection order |
| Market role | NB |
| Regulatory determination / chapter | GPKE |
| Section | 6.12.1: AD: Interruption of grid connection use (disconnect) on the instruction of LF |
| Check identifiers | checked: 17115 · response: 19116, 19117 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 10 | Is the market location already disconnected? | yes | A01 | Cluster: Rejection The market location is already disconnected. |
| — | — | no | → Step 20 | — |
| 20 | Does a disconnection order already exist for the market location within the period of 6 WT from the earliest possible disconnection date? | yes | A10 | Cluster: Rejection A disconnection order for the market location already exists. |
| — | — | no | → Step 30 | — |
| 30 | Is the LF ordering the disconnection assigned to the market location to be disconnected throughout the entire execution period of the disconnection order (= earliest possible disconnection date until earliest possible disconnection date + 6 WT)? | no | A11 | Cluster: Rejection A future confirmed start of supply towards another supplier already exists. The execution deadline of 6 WT from the earliest possible disconnection date affects the confirmed start of supply date towards the other supplier. |
| — | — | yes | → Step 40 | — |
| 40 | In the period of 6 WT from the earliest possible disconnection date, is the identical MSB assigned at all metering locations assigned to the market location as at the market location to be disconnected? | no | A02 | Cluster: Rejection At least one metering location has a different MSB assigned than the market location. Note: electricity-specific question |
| — | — | yes | → Step 50 | — |
| 50 | Is the market location to be disconnected at low voltage? | no | A03 | Cluster: Rejection The market location is not in the low voltage grid. Note: Electricity-specific question |
| — | — | yes | → Step 60 | — |
| 60 | Are further market locations affected by the disconnection for which this disconnection order must not take effect? Note: “Dormant market locations” are not to be taken into account when answering the question. | yes | → Step 65 | — |
| — | — | no | → Step 70 | — |
| 65 | Are the further market location(s) exclusively generating market location(s)? | no | A04 | Cluster: Rejection At least one further consuming market location is affected by the disconnection. Note: Electricity-specific question |
| — | — | yes | → Step 70 | — |
| 70 | Is there a confirmed start of supply towards the commissioning LF for the entire execution period? | yes | A12 | Cluster: Rejection A confirmed start of supply towards the ordering LF already exists within the execution period. |
| — | — | no | → Step 80 | — |
| 80 | Is there a reason preventing a disconnection at the market location? | yes | A05 | Cluster: Rejection There is a reason for prevention. Note: The identified problem must be described/named in the response. |
| — | — | no | → step 90 | — |
| 90 | Is the disconnection order date-bound? | yes | → Step 100 | — |
| — | — | no | → Step 110 | — |
| 100 | Is the transmitted disconnection date at least 12 WT after the receipt date of the message of the disconnection order? | no | A06 | Cluster: Rejection Deadline violation for a date-bound disconnection order. |
| — | — | yes | → Step 120 | — |
| 110 | Is the transmitted earliest possible disconnection date at least 6 WT after the receipt date of the message of the disconnection order? | no | A07 | Cluster: Rejection Deadline violation for a disconnection order that is not date-bound. |
| — | — | yes | → Step 120 | — |
| 120 | Has a previously unspecified error occurred? | yes | A99 | Cluster: Rejection Other Note: The identified problem must be described/named in the response. End of usability: 01.04.2027 00:00 |
| — | — | no | → Step 130 | — |
| 130 | Can the disconnection order be mapped as a flat rate via the electronic price sheet? | yes | A08 | Cluster: Consent Disconnection is mapped via the electronic price sheet. |
| — | — | no | A09 | Cluster: Consent The individual disconnection costs are exchanged in the message. |
Result codes
| Result code | Cluster | Meaning | Response check identifier |
|---|---|---|---|
A01 | Rejection | The market location is already disconnected. | 19117 |
A10 | Rejection | A disconnection order for the market location already exists. | 19117 |
A11 | Rejection | A future confirmed start of supply towards another supplier already exists. The execution period of 6 WT from the earliest possible disconnection date affects the confirmed start of supply date towards another supplier. | 19117 |
A02 | Rejection | At least one metering location has a different MSB assigned than the market location. Note: electricity-specific question | 19117 |
A03 | Rejection | The market location is not in the low voltage grid. Note: electricity-specific question | 19117 |
A04 | Rejection | At least one further consuming market location is affected by the disconnection. Note: electricity-specific question | 19117 |
A12 | Rejection | A confirmed start of supply towards the ordering LF already exists within the execution period. | 19117 |
A05 | Rejection | A reason for prevention exists. Note: The identified problem must be described/named in the response. | 19117 |
A06 | Rejection | Deadline violation for a date-bound disconnection order. | 19117 |
A07 | Rejection | Deadline violation for a disconnection order that is not date-bound. | 19117 |
A99 | Rejection | Other Note: The identified problem is to be described/named in the response. End of usability: 01.04.2027 00:00 | 19117 |
A08 | Consent | Disconnection is mapped via the electronic price sheet. | 19116 |
A09 | Consent | The individual disconnection costs are exchanged in the message. | 19116 |
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. The »response check identifier« column of the result codes assigns a cluster only because this tree carries exactly one checked message and exactly one response per pole; their pole comes from the use case title of the response.
Consistent with the generated process
All 13 result codes of the decision tree are contained in the generated process E_0470.bpmn.