Sources (7)
country_code · CiString(2) · cardinality 1: ISO-3166 alpha-2 country code of the CPO that _owns_ this Tariff.
party_id · CiString(3) · cardinality 1: ID of the CPO that 'owns' this Tariff (following the ISO-15118 standard).
id · CiString(36) · cardinality 1: Uniquely identifies the tariff within the CPO's platform (and suboperator platforms).
currency · string(3) · cardinality 1: ISO-4217 code of the currency of this tariff.
type · TariffType · cardinality ?: Defines the type of the tariff. This allows for distinction in case of given Charging Preferences. When omitted, this tariff is valid for all sessions.
tariff_alt_text · DisplayText · cardinality *: List of multi-language alternative tariff info texts.
tariff_alt_url · URL · cardinality ?: URL to a web page that contains an explanation of the tariff information in human readable form.
min_price · Price · cardinality ?: When this field is set, a Charging Session with this tariff will at least cost this amount. This is different from a `FLAT` fee (Start Tariff, Transaction Fee), as a `FLAT` fee is a fixed amount that has to be paid for any Charging Session. A minimum price indicates that when the cost of a Charging Session is lower than this amount, the cost of the Session will be equal to this amount. (Also see note below)
max_price · Price · cardinality ?: When this field is set, a Charging Session with this tariff will NOT cost more than this amount. (See note below)
elements · TariffElement · cardinality +: List of Tariff Elements.
start_date_time · DateTime · cardinality ?: The time when this tariff becomes active, in UTC, `time_zone` field of the Location can be used to convert to local time. Typically used for a new tariff that is already given with the location, before it becomes active. (See note below)
end_date_time · DateTime · cardinality ?: The time after which this tariff is no longer valid, in UTC, `time_zone` field if the Location can be used to convert to local time. Typically used when this tariff is going to be replaced with a different tariff in the near future. (See note below)
energy_mix · EnergyMix · cardinality ?: Details on the energy supplied with this tariff.
last_updated · DateTime · cardinality 1: Timestamp when this Tariff was last updated (or created).OCPI 2.2.1 specification · #mod_tariffs_tariff_objecttype · TariffDimensionType · cardinality 1: The dimension that is being priced
price · number · cardinality 1: Price per unit (excl. VAT) for this dimension.
vat · number · cardinality ?: Applicable VAT percentage for this tariff dimension. If omitted, no VAT is applicable. Not providing a VAT is different from 0% VAT, which would be a value of 0.0 here.
step_size · int · cardinality 1: Minimum amount to be billed. That is, the dimension will be billed in this `step_size` blocks. Consumed amounts are rounded up to the smallest multiple of `step_size` that is greater than the consumed amount. For example: if `type` is `TIME` and `step_size` has a value of `300`, then time will be billed in blocks of 5 minutes. If 6 minutes were consumed, 10 minutes (2 blocks of `step_size`) will be billed.OCPI 2.2.1 specification · #mod_tariffs_pricecomponent_classPARKING_TIME · : Time in this ChargingPeriod during which the vehicle is not requesting power. Defined in hours, default step_size multiplier is 1 second.OCPI 2.2.1 CDRs module · #mod_cdrs_cdrdimensiontype_enum"A CPO SHALL at least start (and add) a ChargingPeriod every moment/event that has relevance for the total costs of a CDR. During a charging session, different parameters change all the time, like the amount of energy used, or the time of day. These changes can result in another Price Component of the Tariff becoming active. When another Price Component becomes active, the CPO SHALL add a new Charging Period with at least all the relevant information for the change to the other Price Component. The CPO is allowed to add more _in-between_ Charging Periods to a CDR though."OCPI 2.2.1 CDRs module · #mod_cdrs_cdr_object"When calculating the cost of a charging session, `step_size` SHALL only be taken into account once per session for the TariffDimensionType `ENERGY` and once for `PARKING_TIME` and `TIME` combined."OCPI 2.2.1 CDRs module · #mod_cdrs_cdr_object"The `step_size` uses the total amount of a certain unit used during a session, not only the last ChargingPeriod. In other words, when the price of energy per kWh or the price of time per hour differs during a session,only the total amount of energy or time is used in calculations with `step_size`. + Example: Energy costs € 0.20 perkWh before 17:00 and € 0.27 per kWh after 17:00. Both Price Components have a `step_size` of 500 Wh. If a driver charges 4.3 kWh before 17:00 and 1.1 kWh after 17:00, a total of 5.4 kWh is charged. The `step_size` rounds this up to 5.5 kWh total. It does NOT round the energy used after 17:00 to 1.5 kWh."OCPI 2.2.1 CDRs module · #mod_cdrs_cdr_object"NOTE: Earlier versions of the OCPI 2.2.1 specification document mistakenly defined PARKING_TIME as "Time during this ChargingPeriod not charging". Under that definition, drivers would be exposed to penalizing loitering fees not only when they leave their vehicle in a charging session after it has been fully charged, but also when the EVSE is not offering energy to the vehicle while the vehicle is still requesting power. In practice, PARKING_TIME was already used according to the new definition."OCPI 2.2.1 CDRs module · #mod_cdrs_cdrdimensiontype_enum