Explanations use OCPI 2.2.1. Physical and billing-system events are authored examples.
CDR bills each period at its own rate
Advanced
5 min
CDR bills each period at its own rate
The driver charges from 16:40 to 17:30 local time. The Location's time_zone is Europe/Amsterdam, so the tariff's 17:00 is 16:00 UTC on this February day. The CPO starts a new charging period at 17:00, when the 0.55 element becomes active, and bills 11.3 kWh at 0.35 and 19.7 kWh at 0.55.
Sandbox run · OCPI 2.2.1
Run this exchange in the sandbox
CPO
EMSP
"A *Charge Detail Record* is the description of a concluded charging session. The CDR is the only billing-relevant object. CDRs are sent from the CPO to the eMSP after the charging session has ended. Although there is no requirement to send CDRs in (semi-) realtime, it is seen as good practice to send them as soon as possible. But if there is an agreement between parties to send them, for example, once a month, that is also allowed by OCPI."OCPI 2.2.1 CDRs module · #mod_cdrs_cdrs_module"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."OCPI 2.2.1 CDRs module · #mod_cdrs_cdr_object"A `TariffRestrictions` object describes if and when a Tariff Element becomes active or inactive during a Charging Session. These restrictions are not to be interpreted as making the Tariff Element applicable or not applicable for the entire Charging Session. When more than one restriction is set, they are to be treated as a logical AND. So a Tariff Element is active if and only if all of the properties in its `TariffRestrictions` match."OCPI 2.2.1 specification · #mod_tariffs_tariffrestrictions_class"|start_time |string(5) |? |Start time of day in local time, the time zone is defined in the `time_zone` field of the Location, for example 13:30, valid from this time of the day."OCPI 2.2.1 specification · #mod_tariffs_tariffrestrictions_class
Message FlowStep 3 of 4