DH-421 Request for supply disconnection
Event description
A supplier reports a request for supply disconnection to Datahub. The supplier requests the DSO to disconnect the supply if the customer fails to pay their bills to the supplier or commits another breach of agreement.
Parties
Supplier
Datahub
DSO
Balancing service provider
Time limits
Effective time of the update |
|---|
The request must be reported at least one week prior to the desired disconnection date. |
Event processing in Datahub
Step | Description |
Balance information update | From the day following the requested disconnection date, electricity use at the accounting point is calculated to the DSO’s balance (electricity use is once again calculated to the supplier’s balance after the connection notification DH-412). |
Closing previous connection and disconnection requests | If the same accounting point has an open connection or disconnection request from a supplier with a requested connection/disconnection date in the past, the past request is closed so that it no longer waits for the DSO’s response. |
Information storage
Origin of information | Information stored |
Information processed by Datahub | Balance information for the accounting point. |
Return of information
Party | Description | Message |
|---|---|---|
Supplier | Notification of successful or rejected disconnection notification. |
Forwarding of information
Party | Description | Message |
|---|---|---|
DSO | The disconnection request is forwarded to the accounting point’s DSO. | |
Balancing service provider | If the notification of disconnection changes a customer’s supplier information due to the updated agreement and the customer has issued an ‘Accounting point’s balance responsibility information’ authorization for the accounting point, the new balance responsibility information is forwarded to the balancing service provider. The authorization must be valid on the reporting date of the event and the validity of the changed data must overlap with the validity of the authorization. |
Composite processes
Party | Description | Composite process |
|---|---|---|
DSO | The disconnection request is forwarded to the accounting point’s DSO. |
Significant errors and consequences
Error | Consequence |
|---|---|
The disconnection request is reported for the wrong accounting point or the wrong day. | The DSO disconnects the customer’s delivery on the wrong grounds (consequences are equivalent to an unexpected electricity outage). |
Event cancellation
The cancellation must be made before the disconnection notification (DH-422) from the DSO, but no later than the day before the requested disconnection date. On the disconnection date, the process can be cancelled by submitting a connection request (DH-411).
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
The requested disconnection time is midnight. | EC.MPT.107 | '00:00:00' (local) = '22:00:00' (UTC). |
The accounting point is recorded in Datahub. | EC.MPT.115 |
|
The accounting point must not have the status ‘Removed from use’ or ‘Deleted’. | EC.MPT.120 |
|
The disconnection date must be at least one week in the future. | EC.MPT.125 |
|
No other disconnection processes may be under way at the accounting point. | EC.MPT.142 |
|
The status of the accounting point reported in the message must be ‘Disconnected’. | EC.MPT.143 |
|
The supplier must be party to a valid sales agreement for the accounting point when the request is made, as well as on the disconnection date. | EC.AGR.218 |
|
Please observe that the list is not complete. | ||