We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

In the GENIVI Technical Summit it came to discussion, how different vehicle datasets could be defined in order to provide OEM guidelines.

"To define datasets that can be provided for specific purposes/use-cases to have consistent coverage from OEMs (bundling of data per use-case)"

It should be kept in mind that different services have different data needs, and might need an expanded dataset in order to function. Still, sorting data points into different bundles makes the data use cases clearer compared to listing individual data points. Apart from these first data bundles, we should also consider different categories based on data sensitivity, privacy and regional laws.

Personalised vehicle data – read-only

Name: Pay-as-you-Drive (PAYD)
Purpose:Insurance services based on the vehicle mileage
Data pointDescriptionUpdate frequency
OdometerThe mileage in miles or meters24h
Name: Logbook
Purpose:Automated trip logging for business vehicles
Data pointDescriptionUpdate frequency
OdometerThe mileage in miles or metersTrip end
LatitudeVehicle latitudeTrip start/end
LongitudeVehicle longitudeTrip start/end
Name: Charging
Purpose:Services for electric vehicles
Data pointDescriptionUpdate frequency
State of ChargeThe state of charge percentageOn change
Estimated rangeEstimated electrical rangeOn change
Charging statePlugged in or chargingOn change
Name: Fleet
Purpose:Fleet owners, car rental companies
Data pointDescriptionUpdate frequency
OdometerThe mileage in miles or metersTrip end
LatitudeVehicle latitudeOn change
LongitudeVehicle longitudeOn change
Fuel levelFuel level percentage (State of Charge for EVs)On change
  • No labels

Privacy Policy | Cookie Policy