15-minute data import

General information

Load profile data billing can be implemented using 15-minute consumption data. This enables extended tariff structures such as ZEV billing or multi-tariff systems. The data import tool can be used to import data from specific charging stations into the smart-me cloud.

Green diagram area: 15min Data import into the property account. 

The migration to the green diagram area can be carried out in the background for already installed charging stations and without any impact on the end customer (as the authentication is not changed on site). 

Attention: In this variant, the authentication works on site / with the charging stations directly. eCarUp has no influence on the activation.

Advantage: As it is a data import in the background, customers do not notice anything in the event of a migration.

Disadvantage: Since there is no authentication via eCarUp, the charging data of the customers is not recorded and cannot be viewed.

Red: 15min data import with activation via eCarUp App.

Here a separate account must be created for the activation of the charging stations via eCarUp. incl. the OCPP implementation via one of the following instructions depending on the charging station manufacturer used (Zaptec / easee)

Advantage: Customer can activate via the app or RFID card and sees his charging history.

Disadvantage: Two separate logins must be managed.

Data Quality

Note: Quality is defined by the third-party provider and cannot be changed or improved by smart-me or eCarUp.

Important: We recommend installing a smart-me meter at the e-mobility outlet for the following reasons:

• If no smart-me meter is installed, support will not be able to help you find discrepancies between smart-me billing and the electricity provider's bill. This always applies when measurements are taken by third-party providers.

• With smart-me billing, the total e-mobility consumption can be referenced.

• A separate billing unit for total consumption can be created and reported (use case: external administration).

Zaptec

The current data is retrieved from the Zaptec Cloud at 15-minute intervals.

https://api.zaptec.com/help/index.html#/Charger/get_api_chargers__id_

The Zaptec interface only provides live data when charging is active.

• If the station is offline, no live data or meter readings are provided.

• This also applies if the station is online but no one is charging.

If a charging station is not used for several weeks, it will never send updated meter readings to the API. Both auto-export and billing in smart-me Billing depend on the data from the measuring points. If a measuring point does not send any data, auto-export will not be performed and tariff calculation in Smart-Me Billing will be suspended. This means that invoicing cannot be carried out in a timely manner. 

To prevent invoicing from becoming impossible over several weeks/months, we proceed as follows: 

• We want to ensure that smart-me billing and auto-export can be carried out with a maximum backlog of three days and that the data in the 15-minute intervals is as accurate as possible.

• When the station is charging, we receive live data via the API endpoint chargers/{chargerId}, which we store at the time of the query.

• When the station is online, we store the last measurement value we received via the API endpoint chargers/{chargerId} for the time of the query. Even if this is several weeks old.

• If the station is offline, we store the value that the station sends us as an OCMF message via the API endpoint chargers/{chargerId}. We use the timestamp of the OCMF message, provided it is less than three days old. If it is older, we store the value via X-3days. This ensures that stations that are offline can also be billed promptly and do not unnecessarily block the entire system. 

If you have set up an alarm in smart-me, we recommend allowing for at least three days of offline time, as the alarm checks the last stored value and, in the event of offline status, even if only for ten minutes, this can be up to three days old.

Easee

15-minute readings are stored on the smart-me cloud for your easee charging stations. These are normally available with a delay of 1-3 hours.

In the event of internet or server failures, it may exceptionally take longer. As soon as the outage is resolved, the readings from the outage period are automatically transferred to the smart-me Cloud.

Configuration of easee charging station

smart-me configures easee charging stations with a measurement interval of 15 minutes. This affects all charging stations of your easee account configured for import. The configuration is done once per charging station, namely:

• when setting up the import: all charging stations already existing in the easee account

• charging stations newly installed in the easee later: within 3h.

Note: This configuration has no influence on the measurement and billing of charging transactions.

Attention:

If you (or an authorized person) change the measurement interval of an easee charging station, this will affect the measurement values available in the smart-me Cloud. In this case, the measurement interval will not be corrected by smart-me.

Further information can be found in the easee documentation:

• https://developer.easee.cloud/docs 

• https://developer.easee.cloud/docs/consumption-report-types#lifetime-energy 

Instructions for data import

1. Configure Zaptec settings of easee settings

2. Configure smart-me settings

Zaptec Configuration

easee Configuration

1. Create an account in the easee Cloud for each ZEV object, the registration is done via an e-mail (here in this example an alias e-mail address). The mobile phone number is a mandatory field and the same number can always be entered. 

2. E-mail must be confirmed

3.  Share the permissions for the corresponding installation in it.

4. Important: Please always enter as "owner or admin of the site".

smart-me Configuration

6. Login or click on accept. Create a Zaptec/Easee data import via "Add"

7. Click on the top right on your account name and choose account settings.