Esta es la versión HTML de un fichero adjunto a una solicitud de acceso a la información 'Breton's cabinet industry meetings'.



Ref. Ares(2023)5193231 - 26/07/2023

 
 
A level playing field must be preserved between mobility providers to ensure the market for 
autonomous and connected cars remains competitive. In line with this, car rental companies, as 
trustworthy third-party service providers, should have the same level of data access as a vehicle 
manufacturer’s subsidiary performing a comparable service
.  
Manufacturers are in a privileged position to develop competing services, e.g. fleet-management 
solutions, based on data collected from their own subsidiaries and potentially from third-party 
service providers using their vehicles or other solutions. Without intervention, this will: facilitate 
vertical monopolies in the entire after-sales market, including mobility solutions; lead to 
monopolistic pricing of the data and gatekeeper issues; and diminish opportunities and 
innovation along the entire supply chain. 
We therefore call for access to in-vehicle data under fair, reasonable and non-discriminatory 
conditions.
 This ensures that all stakeholders in the emerging digital car ecosystem are 
considered by providing equal access to in-vehicle generated data and safeguarding the privacy 
and freedom of choice for consumers. Such access enables us to monitor and analyse the data 
generated by our own vehicles and follow through with important operational services, such as 
fleet maintenance or vehicle repair, as well as provide cost-efficient and market sensitive added 
value services for our customers. 
In addition to that, we recommend that the Data Act implements a “B2B fairness test” to avoid 
unilaterally imposed unfair conditions for access to and use of data.   
(2)  Direct and real-time access to data supporting our innovative services must be 
available in all scenarios 
The optimal solution for our required data points (highlighted in annex below) is direct and real-
time access while the vehicle is in use as well as stationary. 
Additionally, we require access to 
historic data which is also critical, as not all of our business is conducted in real time (e.g. claims 
management following damage).   
For all the use cases and data points highlighted, this information could be provided through an 
external vehicle server to guarantee interoperability and an even distribution of the cost across the 
mobility sector.  
(3)  One common “data language” and data access technology for all types of vehicles 
Mobility providers will be faced with extra costs if required to adapt their solutions to the 
products and systems of each manufacturer or aftermarket provider.
 Currently, there are no 
common standards around in-vehicle data relating to measures, API’s, reading frequency, 
methodology or accuracy. As a result, different cars speak a different “data language” and the cost 
of “translation” falls on the mobility providers.  
This issue is likely to be exacerbated by the advancement of electric vehicles (EVs) and other 
alternatively powered vehicles such as fuel cell electric vehicles (FCEVs), as these vehicles rely on 
different technologies and have different data points compared to internal combustion engine 
vehicles (ICEs). The data access technology (e.g. data access protocols and interfaces) should 
therefore be standardised so as to prevent additional obstacles to the uptake of alternative 
fuels vehicles.
  

 

 
 
Day-to-day use cases in a rental car scenario 
Car rental companies are innovating each and every day to improve both customer experience 
and enhance the performance and safety of shared vehicles. Access to in-vehicle data is therefore 
essential to our ability to carry out these activities in the future.  
We illustrate below some of the data points we require access to and their use in a rental scenario. 
Please find a more comprehensive list of data points provided in the annex.  
General use cases (in- and off-rental) 
x  GPS position: This data point allows rental companies to track stolen or missing vehicles. 
In case of full automation of the rental service, near real-time location data is also necessary 
to verify that the vehicle has been returned to the agreed location. This also allows us to 
identify the location of the vehicle when it is off-rental on the car rental lot to support 
automated inventories/car counts and to pin-point the location of the car on our customer 
rental app. 
x  Telemetry: All maintenance and vehicle health parameters including fluid levels (oil, ad 
blue, coolant, hydraulic), tyre pressure, warning messages, Diagnostic Trouble Codes (DTCs) 
and time/mileage to next vehicle service are required to support better fleet management 
and cost efficiencies to fleet operators. 
x  Command and control capability: This would include lock/unlock, mobilise/immobilise, 
honk horn, open boot, flashlights. For example, this would enable us to unlock a vehicle 
should a customer have lost access.  
 In-rental use cases 
x  Services for drivers: Car rental companies seek to offer and provide in-vehicle Wi-Fi, 
parking and refuelling services. This might also enable us to give the customer the 
possibility to easily erase personal data stored in the infotainment system such as phone 
logs, address books, etc. 
 
Off-rental use cases 
x  Fuel: Car rental companies need to accurately measure the level of fuel or level of charge 
for EVs both at the start and end of a rental. Based on accurate readings (ideally +/- 0.5 
litres) provided through data, customers can be billed more accurately for fuel used.  
x  Mileage: Accurate capture of fuel readings allows the rental start and end process to be 
digitised, opening up new business models to car rental companies. In terms of fleet 
management, there are benefits in being able to track mileage use through the rental to 
better manage that use on monthly or longer-term rentals. 
x  Accident/damage information: The ability to establish the events leading up to an 
accident are critical in being able to better manage claims. The data points required for this 
are GPS location, vehicle speed, acceleration and direction. 
Ensuring safety and security without compromising on competition 
Our customers’ safety and security is paramount. Cybersecurity and strict compliance with data 
protection laws are an intrinsic part of this and our preconditions to ensure the user’s trust in 
technology.  

 



 
 
Annex – Data Use Cases for Car Rentals  
●  Fuel used and damage detection – guarantees accuracy  for consumer protection and 
billing 
o  Which data points would be required? 
▪ 
Geo location 
▪ 
Speed / distance 
▪ 
Fuel level and consumption  
▪ 
Damages  
 
●  Accident logs – helps with claims management. 
o  Which data points would be required? 
▪ 
Event notifications 
▪ 
Geo location 
▪ 
Speed 
▪ 
Driver manoeuvres alerts - i.e. tailgating, aggressive driving, rapid 
acceleration, hard braking, speeding, unsafe phone use (if available). 
▪ 
Confirmed impacts and collusion data and videos if available 
▪ 
Time stamps on the above  
▪ 
Driving assistance system activation (e.g. ABS, lane keep assist, …) 
 
●  Security perspective – tracking stolen vehicles; or companies getting notified when 
vehicles are not used in compliance with rental conditions. 
o  Which data points would be required? 
▪ 
Geo location and geofencing events (suspicious areas entrance, border 
crossing) 
▪ 
Time stamps 
▪ 
In-vehicle generated safety alerts 
 
●  Services for drivers, offered as required or on an opt-in basis. Required ones include 
insurance purposes, either for concluding the contract or to help offer lower premiums 
to responsible drivers. Opt-in services can for example be evaluations of driver 
performance, remote diagnostics and servicing.  

o  Which data points would be required? 
▪ 
Dynamic data including real-time status information 
▪ 
Option for bi-directional communication 
▪ 
Driving events and data: harsh acceleration, braking, cornering, engine RPM, 
... 
 
●  Fleet management (e.g. tracking condition and upcoming maintenance – in general a 
rental company cannot anticipate how much a vehicle will be driven in any one week, 
or over one year). 

o  Which data points would be required? 
▪ 
Event notifications 
▪ 
Policy violations 

 

 
 
▪ 
Trip history (Start / end timestamps, location points, events …) 
▪ 
Maintenance information (dashboard alerts, next maintenance 
mileage/date, …) 
 
●  Fleet control: Improved operational management of the fleet in station (e.g. locate 
available vehicles, transfer monitoring, etc.) and fleet utilization (balanced mileage 
consumption, buyback limits control, track idle vehicles, etc.). 

o  Which data points would be required? 
▪ 
Geolocation and geofencing alerts 
▪ 
Time stamps  
▪ 
Vehicle conditions (maintenance alerts and data) 
 
●  Managing a fleet of increasing numbers of electric vehicles (EVs) – standardisation on 
access and availability of the data needs to be achieved as new 
technologies/manufactures do not follow same parameters.  

o  Which data points would be required? 
▪ 
Status of battery charge 
▪ 
Battery health 
▪ 
Miles per kilowatt hour and range achieved in a single journey (to measure 
efficiency)  
▪ 
Recharging information (amount of recharge; operator & billing information 
in some cases, depending on the billing system used) 
▪ 
Geolocation and by-directional communication (to ensure real time 
information can be given around availability and status of the closest 
charging stations) 
 
●  Added opt-in services for customers such as alerts to nearby points of interest. 
o  Which data points would be required (open list)? 
▪ 
Near real time geolocation and geofencing events   
 
●  Compliance requirements for the development of new services (i.e. Highly Automated 
Road Passenger Services). 
o  Which data points would be required (open list)? 
▪ 
Reporting accident 
▪ 
Vehicle supervision 
▪ 
Remote control of vehicle – installation of software critical updates 
▪ 
Untoward event reporting for collecting service/system statistics