1. Use Case: Time-based pricing – Hubject

Scenario 1 - Time-based pricing: in this scenario, CPO XYZ wants to price charging sessions based on what time of the day or week these sessions occur.

The table below shows how CPO XYZ can capture his time-based price differentiation in the "PricingProductData" payload structure required for transferring tariff details to the HBS using the eRoamingDynamicPricing service.

Tariff Details (Time-based tariffs)

Tariff details converted to OICP PricingProductData format

Tariff Name	Pricing Details
Day Tariff	06.00-19.00h: 0.25 EUR/kWh
Night Tariff	19.01-05.59h: 0.30 EUR/kWh
Weekend Tariff	Saturdays & Sundays: 0.35EUR/kWh

{
"ActionType": "fullLoad",
"PricingProductData": {
 "OperatorID": "DE*XYZ",
 "OperatorName": "CPO XYZ",
 "ProviderID": "DE-ABC",
 "PricingDefaultPrice": 0.30,
 "PricingDefaultPriceCurrency": "EUR",
 "PricingDefaultReferenceUnit": "KILOWATT_HOUR",
 "PricingProductDataRecords": [
 {
 "ProductID": "DayTariff",
 "ProductPriceCurrency": "EUR",
 "ReferenceUnit": "KILOWATT_HOUR",
 "IsValid24hours": false,
 "MaximumProductChargingPower": 50,
 "PricePerReferenceUnit": 0.25,
 "ProductAvailabilityTimes": [
 {
 "Periods": [
 {
 "begin": "06:00",
 "end": "19:00"
 }
 ],
 "on": "Workdays"
 }
 ]
 },
 {
 "ProductID": "NightTariff",
 "ProductPriceCurrency": "EUR",
 "ReferenceUnit": "KILOWATT_HOUR",
 "IsValid24hours": false,
 "MaximumProductChargingPower": 50,
 "PricePerReferenceUnit": 0.30,
 "ProductAvailabilityTimes": [
 {
 "Periods": [
 {
 "begin": "19:01",
 "end": "05:59"
 }
 ],
 "on": "Workdays"
 }
 ]
 },
 {
 "ProductID": "WeekendTariff",
 "ProductPriceCurrency": "EUR",
 "ReferenceUnit": "KILOWATT_HOUR",
 "IsValid24hours": true,
 "MaximumProductChargingPower": 50,
 "PricePerReferenceUnit": 0.35,
 "ProductAvailabilityTimes": [
 {
 "Periods": [
 {
 "begin": "00:00",
 "end": "23:59"
 }
 ],
 
 "on": "Weekend"
 }
 ]
 }
 ]
 }
}

Related articles