DH-1200 Use case examples

Participants

• Load control service provider (LCS)

• DSO

• Datahub

Initial state

• The load control service provider (LCS)

  • has entered into an agreement with the customer regarding the control of the customer’s loads.

  • has received information from Datahub that the customer has granted a load control authorization (DH‑825) and that the authorization has entered into force.

• Datahub

  • has sent the DSO a notification of the new authorization at the accounting point (DH‑1111‑1).

  • has sent the DSO a notification that market‑based load control has started at the accounting point (DH‑1211‑1).

• The DSO

  • has received the above notifications from Datahub and processed them as necessary.

Steps

1. The load control service provider sends a calendar-based load control request (DH-1221-1) to Datahub.

2. Datahub accepts the request and returns a positive acknowledgement to the service provider.

3. Datahub forwards the load control request (DH-1221-2) to the DSO’s message queue.

4. The DSO retrieves the load control request from Datahub’s message queue.

5. The DSO programs the meter at the customer’s accounting point according to the calendar specified in the request.

6. The DSO sends a positive load control confirmation (DH-1231-1) to Datahub.

7. Datahub accepts the confirmation and returns a positive acknowledgement to the DSO.

8. Datahub forwards the confirmation (DH-1231-2) to the service provider’s message queue.

9. The service provider retrieves the confirmation from its message queue and matches it to the original request in its own system.

End state

A base calendar suitable for the customer’s service has been programmed at the accounting point. The accounting point is ready to receive scheduled load control requests, if agreed between the load control service provider and the customer.

Participants

• Old load control service provider (OLCS)

• New load control service provider (NLCS)

• DSO

• Datahub

Initial state

• The new load control service provider has entered into a new agreement with the customer regarding the control of the customer’s loads.

• The old load control service provider is currently providing load control service to the customer.

Steps

1. The customer terminates the existing load control authorization granted to the OLCS through the Authorization Service.

2. Datahub notifies the OLCS (DH-825) and the DSO (DH-1111-1) of the change in authorization.

3. The customer grants a load control authorization to the NLCS through the Authorization Service.

4. Datahub notifies the NLCS (DH-825) and the DSO (DH-1111-1) of the authorization change.

5. (If the change in authorization takes effect in the future,) the OLCS continues to provide load control service for the customer until the authorization end date.

6. Once the authorization change takes effect, the NLCS begins providing the service by initiating the base calendar setup (see example use case UC 1).

End state

The load control service provider at the accounting point has been changed, and the new service provider is ready to perform load control at the accounting point.

Participants

• Old load control service provider (OLCS)

• New load control service provider (NLCS)

• DSO

• Datahub

Initial state

• The old load control service provider is providing load control service to the customer.

• The agreement between the customer and the OLCS ends earlier than the agreement between the customer and the NLCS begins.

Steps

1. The customer terminates the existing load control authorization granted to the OLCS through the Authorization Service.

2. Datahub notifies the OLCS (DH-825) and the DSO (DH-1111-1) of the change in authorization.

3. (If the authorization change takes effect in the future,) the OLCS continues to provide load control service for the customer until the authorization end date.

4. At the moment the authorization ends, Datahub notifies the DSO that market-based load control at the accounting point has ended (DH-1211-2).

5. The DSO programs the meter with the time division schedule of the grid agreement or another base calendar agreed with the end customer.

6. The customer grants a load control authorization to the NLCS through the Authorization Service.

7. Datahub notifies the NLCS (DH-825) and the DSO (DH-1111-1) of the authorization change.

8. At the moment the new authorization takes effect, Datahub notifies the DSO that market-based load control at the accounting point has started (DH-1211-1).

9. After the authorization takes effect, the NLCS begins providing the service by initiating the base calendar setup (see example use case UC 1).

End state

The load control service provider at the accounting point has been changed, and the new service provider is ready to perform load control at the accounting point.

Participants

• Load control service provider (LCS)

• DSO

• Datahub

Initial state

• The DSO has identified that the end customer’s meter is faulty and must be replaced. The replacement has been carried out, but the DSO has not programmed the meter with the most recently sent base calendar of the load control service provider. In this case, once the service provider is informed, it must submit a new calendar‑based load control request.

• The load control service provider is performing the load control service agreed with the customer.

Note: This use case example is relevant only if the DSO does not restore the service provider’s previously sent base calendar to the meter.

Steps

1. The DSO informs the LCS that the end customer’s meter has been replaced and that the DSO has not programmed the meter with the LCS’s most recently sent base calendar. There is no defined information exchange process for this notification via Datahub; the communication must be handled directly between the parties as soon as possible.

2. The LCS receives the information that the meter has been replaced.

3. The LCS submits a new calendar‑based load control request, as described in example use case UC 1.

4. After receiving the confirmation for step 3, the LCS resubmits any scheduled control request for the following day.

5. Communication between Datahub, the DSO and the LCS continues as in steps 2–9 of example use case UC 1.

End state

After the meter replacement, the accounting point is in the same state regarding load control as it was before the replacement.

Participants

• Load control service provider (LCS)

• DSO

• Datahub

Initial state

• The load control service provider is performing the load control service agreed with the customer.

• The end customer’s load control authorization in Datahub will end in the future, and no subsequent load control authorization exists at the accounting point. The ending may occur, for example, because the end customer has not authorized a new service provider to control the loads, or the end customer is moving out of the accounting point and a potential new customer has not authorized anyone to control the loads.

• Datahub has notified the LCS and the DSO of the upcoming end of the authorization.

Steps

1. After the authorization validity ends, Datahub notifies the DSO that market‑based load control at the accounting point has ended (DH‑1211‑2).

2. The DSO receives the notification of the end of load control.

3. The DSO programs the meter with the time‑division schedule of the grid agreement or another base calendar agreed with the end customer.

End state

• The market‑based load control service at the accounting point has ended, and the DSO has programmed a new base calendar into the meter.

• The end customer has the possibility to use the DSO’s load control service, if such a service is offered.