Tariffs
The Tariffs module: how CPOs publish tariffs, the supported tariff structures and the Tariff object.
On this page
Technical considerations
Tariffs can be created and updated by CPOs through the MOBI.Hub. The HUB shall make the relevant tariff information available to connected EMSPs according to the configured interoperability relationships.
It is recommended that EMSPs retrieve tariff information regularly and should perform a (near) real-time request whenever one of its users is about to charge, whenever up-to-date tariff information is required. Note that within OCPI tariffs may be defined at the EVSE level.
The use of the Tariffs module is independent of the authorization model selected by the EMSP. Tariff information may therefore be exchanged whether the interoperability relationship operates through a Classic Hub or Centralized Authentication model.
Mobi.e will not perform any validation of the commercial correctness of the tariff structure beyond the validation required by the OCPI specification. It is the CPO's responsibility to ensure that the tariffs are correctly structured and accurately represent the applicable charging conditions. While it is constantly evolving, the HUB currently supports the following tariff structures:
- Pricing components:
- EUR/min, EUR/kWh, EUR/transaction
- Duration restrictions
- Time of day restrictions
- Most common tariffs today per charge:
- EUR/min
- EUR/kWh
- fixed EUR + EUR/min
- fixed EUR + EUR/min + EUR/kWh
- fixed EUR + EUR/kWh
- With duration restrictions (example, up to n elements):
- fixed EUR + x EUR/min, t<=z min
- fixed EUR + y EUR/min, t>z min
- With time restrictions (example, up to n elements):
- fixed EUR + x EUR/min, AAh-BBh
- fixed EUR + y EUR/kWh, BBh-AAh
Methods to be implemented
CPO (and MOBI.Hub) – Sender
| Method | Direction | Description of usage |
|---|---|---|
GET | Response | Getting current and/or historical tariffs (please check!) |
PUT | Request | Sending new or updated tariff |
DELETE | Request | Deleting a tariff |
EMSP (and MOBI.Hub) – Receiver
The following methods are to be implemented:
| Method | Direction | Description of usage |
|---|---|---|
GET | Request | Getting current and/or historical tariffs (please check!) |
PUT | Response | Receiving new or update tariff |
DELETE | Response | Acknowledging the deletion of a tariff |
Objects description
Tariffs
The following table describes the Tariffs object.
| Property | Mandatory | Value | Comments |
|---|---|---|---|
country_code | TRUE | PT | |
party_id | TRUE | ||
id | TRUE | Tariff ID (UUID format) | |
currency | TRUE | EUR | |
type | TRUE |
| Not sure whether ad_hoc_payment makes sense |
tariff_alt_text | FALSE | This field may be used by the CPO to communicate any relevant discounts. | |
min_price | TRUE | This field should be set to zero in most cases. | |
elements | TRUE | ||
start_date_time | FALSE | ||
stop_date_time | FALSE | ||
last_updated | TRUE |
The following TariffDimensionType values are allowed:
ENERGY,FLAT,TIME.PARKING TIME
The following TariffRestrictions properties can be used:
start_timeend_timestart_dateend_datemin_kwhmax_kwhmin_durationmax_durationday_of_week