NB (69)
E_0472 — Check whether the disconnection order was successful
Check whether the disconnection order was successful
| Attribute | Value |
|---|---|
| Designation | Check whether the disconnection order was successful |
| Market role | NB |
| Regulatory determination / chapter | GPKE |
| Section | 6.12.4: AD: Interruption of grid connection use (disconnect) on the instruction of LF |
| Check identifiers | Response: 21039 |
| EBD version | 4.3 |
| As at | — |
Decision tree
| Step | Check | Result | Code | Note |
|---|---|---|---|---|
| 1 | Was a disconnection not possible for legal reasons (e. g. if an injunction was in place)? | yes | A01 | Cluster: failed Market location was not disconnected because a legal reason was identified on site. |
| — | — | no | → Step 2 | — |
| 2 | Was the connection user encountered? Note: There were no indications that the connection user was present. | no | A08 | Cluster: failed The connection user was not encountered. There was no indication that they were present. |
| — | — | yes | → Step 3 | — |
| 3 | Was a disconnection not possible for the reason "active refusal of access"? Note: "Active refusal of access" means that the connection user was encountered and prevented access, e.g. by threats, physical attacks or by blocking access to the isolating point. | yes | A02 | Cluster: failed Market location was not disconnected because access was actively refused. |
| — | — | no | → Step 4 | — |
| 4 | Was a disconnection not possible for the reason "passive refusal of access"? Note: "Passive refusal of access" means that the presence of the connection user was established but the connection user denies being present. (e.g. the connection user was seen in the flat but does not open the door). | yes | A03 | Cluster: failed Market location was not disconnected because access was passively refused. |
| — | — | no | → Step 5 | — |
| 5 | Was a disconnection not possible due to an impediment? | yes | A04 | Cluster: failed Market location was not disconnected because a preventing reason existed. Note: The preventing reason must be stated in the free text. |
| — | — | no | → Step 6 | — |
| 6 | Was a disconnection not possible for a factual reason? Factual reasons include, for example: market location cannot be identified on site, access to the market location not possible, customer change established at the market location, supplier switch established at the market location and allocation start of the LFN lies before the earliest possible disconnection date of the LFA. | yes | A05 | Cluster: failed Market location was not disconnected because an actual reason existed. Note: The actual reason must be stated in the free text. |
| — | — | no | → Step 7 | — |
| 7 | Was a disconnection not possible for a technical reason (e. g. a further market location would have been affected by the disconnection)? | yes | A06 | Cluster: failed Market location was not disconnected because a technical reason existed. Note: The technical reason must be stated in the free text. |
| — | — | no | A07 | Cluster: successful Market location has been disconnected. |
Result codes
| Result code | Cluster | Meaning |
|---|---|---|
A01 | failed | The market location was not disconnected because a legal reason was identified on site. |
A08 | failed | The connection user was not encountered. There were no signs that they were present. |
A02 | failed | The market location was not disconnected because an active refusal of access existed. |
A03 | failed | The market location was not disconnected because a passive refusal of access existed. |
A04 | failed | The market location was not disconnected because an impediment existed. Note: the impediment must be communicated in the free text. |
A05 | failed | The market location was not disconnected because an actual reason existed. Note: the actual reason must be communicated in the free text. |
A06 | failed | The market location was not disconnected because a technical reason existed. Note: the technical reason must be communicated in the free text. |
A07 | successful | The market location was disconnected. |
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.
Consistent with the generated process
All 8 result codes of the decision tree are contained in the generated process E_0472.bpmn.