DH-1221 Load control request for calendar control
Event description
The load control service provider submits a request for calendar‑based 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. For each calendar day, 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. The request must always include seven calendar days, from Monday to Sunday.
The time periods specified in the calendar request use Finnish local time, taking daylight saving time into account, without a time‑zone indicator. This approach ensures that the same request can continue to be applied across daylight‑saving transitions without the need to send new calendar‑based load control requests. The load control service provider must take this into consideration and therefore must not send control periods that begin or end between 03:00 and 04:00 during the change between summer time and winter time.
See additional information about load control requests for calendar control here.
Parties
Load control service provider
Datahub
DSO
Time limits
Submitting a load control request |
|---|
There is no time limit for submitting a calendar‑based load control request. The calendar-based control defined in the request will take effect no later than the beginning of the day following the programming of the meter. |
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
A calendar‑based load control request cannot be cancelled. If necessary, a new corrected request must be submitted after the previous calendar‑based load control request has been confirmed.
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
The accounting point is found in Datahub and is valid on the reporting date. | 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 |
|
The calendar‑based load control request must include the control periods for each day of the week. | EC.LCR.103 |
|
Each individual day’s control schedule may contain a maximum of 7 control periods. | schema validation |
|
Each individual day’s control periods must cover the full 24‑hour day. | EC.LCR.104 |
|
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. | ||