Why submit metering records to FlatPeak

If you want FlatPeak to calculate the monetary and/or carbon cost of energy that is consumed or exported at your customer’s location or by your device, you need to first submit metering records (reads). Here is how it works:

​

Location-level metering

Suppose you can access property meter records at that location and want to calculate your customer’s energy cost.

You can write code that will continuously pull your customer’s tariff from FlatPeak and calculate consumption cost using meter records you receive from the customer’s property meter.

Simpler, you can submit metering records to FlatPeak and instantly receive its monetary and carbon cost. As a bonus, FlatPeak also provides cost in aggregated form (as daily, weekly, monthly, and yearly), making it easier to build reports.

​

Device-level metering

FlatPeak supports device-level metering for energy cost calculation. You can submit device meter records and get the monetary (and carbon) cost of energy using the tariff that applies to your customer at a location where the device operates at that time. This enables you to separately get the cost of energy for multiple devices operating at the same location (such as when you operate two car chargers at one address).

​

How to submit meter records

Depending on your use case, you can submit metering records in two ways:

• Single metering record (read) at the time with the cost of the energy immediately returned.
• Multiple records at once enabling you to query the energy cost per time interval, charging session id or aggregated by day, week, month or year.

​

Supported metering formats