Limitation of Power Consumption Event

Important

LPC-events (ResourceLPC and LocationLPC) is only sent to specific partners on an invite-only basis, and the structure of this event is subject to change. If you have not been sent here by Spark, please do not implement or base any decisions on this event.

When the need arises in the grid for limitation of power consumption, the Energy Coordination API will create a LPC event.

How it works

The LPC event can be used as a tool by the DSO to reduce power consumption in the grid for a short duration. Typical cases might be because of grid maintenance or unforeseen incidents that causes extra load on the grid. The event might be sent out 2 days ahead in time or just in time. E.g. if you receive an event where the first timestamp is the current hour, it means you should activate LPC immediately.

There will be a limit to how often we can ask for LPC and how many consecutive hours are issued. While currently undecided, you should not expect to have to limit power consumption for many hours at a time.

Step 1: Add your resources

To receive LPC events, you must first add your resources to the Energy Coordination API. Read more about adding resources here.

MeterPointId Required

To receive LPC events you must register meterPointId on your locations and/or resources. For other types of events, like PriceCurve we have some leeway in how we identify the location which can depend on coordinates instead, but for LPC events this is required.

Step 2: Receive events

Subscribe to either ResourceLPCRequested or LocationLPCRequested notification types to receive LPC events. The notifications will contain a payload with either ResourceLPC or LocationLPC payloadType.

One event will be sent per resource that we want to target. For “behind-the-meter” locations, you will receive one event per meterPointId registered on the location.

Step 3: Reacting to the event

These events are mandatory to react to, and you must cap the energy usage of the resource or location to the specified value in the event.

It is important to note that maxPowerInKiloWatts describes an upper limit to the power usage at any point in time, meaning, if maxPowerInKiloWatts is set to 1 kW for 1 hour, you should not be at 2 kW for half an hour and 0 kW for the remaining half hour.

When you receive a LPC event, you must first send a report which acknowledges the event at the earliest convenience. And later after the event has ended, you must send an energy usage report to the Energy Coordination API. These reports must be posted to the /reports endpoint.

Reporting LPC Acknowledgement Learn how to report acknowledgement on LPC events

Report Resource Energy Usage Learn how to report resource energy usage on LPC events

If you registered “behind-the-meter” locations, see here for information on how to report energy usage.

Event format

The event is available as a JSON object with the following properties:

• id: The id of the event that the report corresponds to.
• createdAt: The UTC-timestamp for when the event happened
• payload: The payload of the event

LpcRequested payload format

The LPC event will be sent as either a ResourceLPCRequested or LocationLPCRequested notification, depending on wether you have registered individual resources or “behind-the-meter” locations.

ResourceLPC-payload has the following properties:

• targets: An array of targeted locations for this event. Each of the targets have the following properties:
  • resourceId: The id of the resource that is targeted.
  • locationId: The id of the location the resource belongs to. In case of vehicles, we will send multiple events for all available locations.
  • meterPointId: The targeted meter point id.
  • resolution: The resolution of the each data point. Currently only hourly (01:00:00) is supported.
  • points: An array of maximum power datapoints. Each point has the following properties:
    • maxPowerInKiloWatts: The maximum power in kW. This is maximum amount of power that the location is allowed to consume at any point in time during the hour.
    • timestamp: The start time of the maximum power datapoint. The timestamp is in UTC, and we use the format yyyy-MM-ddTHH:mm:ss.fffZ. The length can be surmised from the resolution property. At the moment it is always an hour.
• payloadType: The type of the payload. For this payload it is always set to LpcRequested to identify that this is a LPC event.

LocationLPC-payload has the following properties:

• targets: An array of targeted locations for this event. Each of the targets have the following properties:
  • locationId: The id of the location that is targeted.
  • meterPointId: The targeted meter point id.
  • resolution: The resolution of the each data point. Currently only hourly (01:00:00) is supported.
  • points: An array of maximum power datapoints. Each point has the following properties:
    • maxPowerInKiloWatts: The maximum power in kW. This is maximum amount of power that the location is allowed to consume at any point in time during the hour.
    • timestamp: The start time of the maximum power datapoint. The timestamp is in UTC, and we use the format yyyy-MM-ddTHH:mm:ss.fffZ. The length can be surmised from the resolution property. At the moment it is always an hour.
• payloadType: The type of the payload. For this payload it is always set to LpcRequested to identify that this is a LPC event.

Example event

This is an example payload of a typical ResourceLPC-event:

resource-limitation-of-power-consumption-event.json

{
  "id": "ed7a8a7a-010f-4fad-a2e0-33dab82dccf2",
  "createdAt": "2024-09-10T07:17:07.9100677+00:00",
  "payload": {
    "targets": [
      {
        "resourceId": "7asd90c1-jk18-489b-g21d-b4g90k93230a",
        "locationId": "7751a1c1-e318-4f71-b4f4-5b6e93efb149",
        "meterPointId": "7070575000XXXXXXXX",
        "resolution": "01:00:00",
        "points": [
          {
            "maxPowerInKiloWatts": 0,
            "timestamp": "2024-09-12T11:00:00+00:00"
          },
          {
            "maxPowerInKiloWatts": 0,
            "timestamp": "2024-09-12T12:00:00+00:00"
          }
        ]
      }
    ],
    "payloadType": "ResourceLPC"
  }
}