DH-1222 Load control request for scheduled control
Event description
The load control service provider submits a request for scheduled load control at the accounting point.
In the request, the service provider defines both the periods during which the meter’s load control relay is closed and the periods during which the relay is open. Up to six relay‑state changes may be defined within a 24‑hour period. The periods must always cover the entire full calendar day from midnight to midnight in Finnish time, taking into account daylight saving time. The periods must not overlap. Scheduled controls must be sent only for the relay for which a base calendar has previously been sent using a calendar‑based load control request. For the time period covered by the scheduled control request, the meter or metering system will not execute the calendar‑based control; the scheduled control overrides it.
The time periods specified in the scheduled request use timestamps with time‑zone information, as in other Datahub events. Note: This differs from the approach used in calendar‑based load control requests.
See additional information about load control requests for scheduled control here.
Parties
Load control service provider
Datahub
DSO
Time limits
Submitting a load control request |
|---|
A scheduled load control request must apply to the next full calendar day, starting at midnight and ending at the following midnight. |
Event processing in Datahub
Step | Description |
Processing of the load control request | No processing is performed in Datahub based on the content of the load control request. |
Information storage
Origin of information | Information stored |
Information reported by the party | The information contained in the load control request is not stored in Datahub. |
Return of information
Party | Description | Message |
|---|---|---|
Load control service provider | Notification of a forwarded or rejected request. |
Forwarding of information
Party | Description | Message |
|---|---|---|
DSO | An accepted load control request is forwarded to the DSO for execution. |
Event cancellation
The request cannot be cancelled. If necessary, a new corrected request must be submitted once the previous request for the same accounting point has been confirmed. The corrected request must be submitted using the request type “Scheduled control correction”.
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
The accounting point must be found in Datahub and be valid at the start of the first control period. | EC.MPT.115 |
|
The accounting point must have status “connected”. | EC.LCR.100 |
|
The load control service provider must have a valid load control authorization for the accounting point. | EC.LCR.101 |
|
If the message specifies relay 1 as the controlled relay, the accounting point’s load‑controllability information must be either “Relay 1 controllable” or “Relay 1 or relay 2 controllable”. | EC.LCR.102 |
|
If the message specifies relay 2 as the controlled relay, the accounting point’s load‑controllability information must be either “Relay 2 controllable” or “Relay 1 or relay 2 controllable”. | EC.LCR.102 |
|
A scheduled load control request must start from the beginning of the following calendar day. | EC.LCR.106 |
|
The scheduled control request must cover the entire following calendar day. | EC.LCR.107 |
|
The start and end times of the control periods must be provided with 15‑minute resolution. | EC.LCR.105 |
|
The reported party identification must match the sender of the control request. | EC.AGR.115 |
|
Please observe that the list is not complete. | ||