Cold storage

Without load shifting, energy usage is 96 kWh, resulting in a cost of $49. However, with load shifting, energy usage slightly increases to 98 kWh, but the cost decreases significantly to $34.

Design

To optimise the operation of a cold storage system by energy cost:

Once the customer completes the Connect flow, or if you imported their tariff:

Identify periods when the energy cost exceeds the daily average.
Proactively extend temperature ahead of high-cost periods and
Lower energy consumption during periods of higher cost until either the temperature reaches the maximum allowable tolerance or the cost decreases, whichever happens first.

To display energy cost:

Log consumed energy to the meter records API under the IMPORT tariff and IMPORT direction.
Report energy costs to the customer using cost calculate API and request energy cost for the IMPORT direction.

To display savings:

You must be able to simulate the typical energy usage profile of your system (not optimised by energy cost).

Log simulated consumed energy to the meter records API under the IMPORT tariff and EXPORT direction.
When you want to display energy saving:

Call cost calculate API and request energy cost for IMPORT and EXPORT directions.
Subtract IMPORT cost from EXPORT cost to get savings calculated here.

Implementation

Find high energy cost periods

To identify periods of high energy costs, call the slots-threshold API endpoint and request all periods over 24 hours when energy costs are at the top 25% (you may wish to adjust this based on your system’s capabilities). We recommend making this call periodically to create an operating schedule for the following 24 hours.

curl --request GET \
  --url 'https://api.flatpeak.com/slots/threshold/loc_65e42ce4d3b813479b252160 \
  ?start_time=2023-06-15T00%3A00%3A00Z \
  &end_time=2023-06-16T00%3A00%3A00Z \
  &direction=IMPORT \
  &segment=HIGH \
  &relative=25' \
  --header 'Authorization: Bearer <token>'

curl --request GET \
  --url 'https://api.flatpeak.com/slots/threshold/loc_65e42ce4d3b813479b252160 \
  ?start_time=2023-06-15T00%3A00%3A00Z \
  &end_time=2023-06-16T00%3A00%3A00Z \
  &direction=IMPORT \
  &segment=HIGH \
  &relative=25' \
  --header 'Authorization: Bearer <token>'

You can also identify periods of high energy costs by obtaining the full tariff rate and calculating pre-peak periods in your systems. For this, call the tariff-rates API endpoint and request the tariff for the next 24 hours. We recommend making this call periodically to create an operating schedule for the following 24 hours.

curl --request GET \
  --url 'https://api.flatpeak.com/tariffs/rates/loc_65e42ce4d3b813479b252160 \
  ?start_time=2023-06-15T00%3A00%3A00Z \
  &end_time=2023-06-16T00%3A00%3A00Z \
  &include_tariff=true
  &direction=IMPORT' \
  --header 'Authorization: Bearer <token>'

Use response data to identify periods when the cost of energy is higher than average.

Create cost-optimised schedule

Use the data obtained in the previous step to program your system to lower the temperature to the minimum allowed before the higher-cost period begins.

In the below example, the high energy cost period is between 08:00 and 09:20. You will program your system to start lowering the temperature at 07:45 to reach the minimum allowed temperature of -21 before the higher cost period begins.

{
    "start_time": "2023-06-15T08:00:00Z",
    "end_time": "2023-06-16T09:20:00Z",
    "tariff": {
      "rate": 14.998,
      "confidence": 1
    }
}

Meter energy use

To calculate the cost of energy used, submit meter readings from your system to one of the API endpoints:

If your system logs meter records as intervals, call the submit-interval-meter-records API. You can also use this endpoint to import historical records.

If your device is an EV charger, we recommend that you log records “tagged” by the charging session ID if you have it. Use the session_reference_id parameter in the request. This will make it easy to report the cost per charging session later.

Make sure that you use the units parameter correctly: W represents the speed of transfer over the accounting period; WH represents the amount of energy transferred over that period.

curl --request PUT \
  --url https://api.flatpeak.com/meters/interval \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '[
  {
    "location_id": "loc_641b90b758fb8e6293716e40",
    "device_id": "dev_65e6d8334c8d715963d99db3",
    "session_reference_id": "SESSION1234567890",
    "direction": "IMPORT",
    "tariff_rate": "IMPORT",
    "units": "W",
    "value": 8214,
    "confidence": 1,
    "start_time": "2023-06-16T01:00:00Z",
    "end_time": "2023-06-16T01:30:00Z"
  }
]'

The API response will indicate that the submitted records have been processed successfully. You can submit up to 10,000 records at a time for a device or location.

If your system logs meter records as intervals, call the submit-interval-meter-records API. You can also use this endpoint to import historical records.

Make sure that you use the units parameter correctly: W represents the speed of transfer over the accounting period; WH represents the amount of energy transferred over that period.

curl --request PUT \
  --url https://api.flatpeak.com/meters/interval \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '[
  {
    "location_id": "loc_641b90b758fb8e6293716e40",
    "device_id": "dev_65e6d8334c8d715963d99db3",
    "session_reference_id": "SESSION1234567890",
    "direction": "IMPORT",
    "tariff_rate": "IMPORT",
    "units": "W",
    "value": 8214,
    "confidence": 1,
    "start_time": "2023-06-16T01:00:00Z",
    "end_time": "2023-06-16T01:30:00Z"
  }
]'

The API response will indicate that the submitted records have been processed successfully. You can submit up to 10,000 records at a time for a device or location.

If your system logs meter records as cumulative values, call the submit-cumulative-meter-records API. This endpoint also supports importing historical records.

curl --request PUT \
  --url https://api.flatpeak.com/cumulative/epoch \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "location_id": "loc_641b90b758fb8e6293716e40",
  "device_id": "dev_65e6d8334c8d715963d99db3",
  "session_reference_id": "SESSION1234567890",
  "direction": "IMPORT",
  "tariff_rate": "IMPORT",
  "units": "WH",
  "data": [
    {
      "time": 1721991392,
      "value": 1553
    }
  ]
}'

The API response will indicate that the submitted records have been processed successfully. You can submit up to 10,000 records at a time.

If your system can distinguish between energy sourced from the grid versus from local generation, such as solar, set "tariff_rate": "LOCAL" when submitting the records. This will tell FlatPeak to account for this energy as “free” when calculating its cost.

Display energy costs

When you want to display the cost of energy the system uses, call calculate-energy-cost-by-time-interval API. Cost can be returned either unaggregated or pre-aggregated by day, month or year.

curl --request POST \
  --url 'https://api.flatpeak.com/costs/interval/dev_65e6d8334c8d715963d99db3 \
  ?aggregation=MONTH \
  &direction=IMPORT \
  &include_tariff=true' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "start_time": "2023-11-07T05:31:56Z",
  "end_time": "2023-12-07T05:31:56Z"
}'

Case studies

Data import & export

Service objects

Data sources

Design

To optimise the operation of a cold storage system by energy cost:

To display energy cost:

To display savings:

Implementation

Case studies

Data import & export

Service objects

Data sources

​Design

​To optimise the operation of a cold storage system by energy cost:

​To display energy cost:

​To display savings:

​Implementation

Design

To optimise the operation of a cold storage system by energy cost:

To display energy cost:

To display savings:

Implementation