Skip to end of metadata
Go to start of metadata

How would a similar, common approach for defining vehicle services in a standard way simplify system development and deployment?

Ulf Björkengren, Principal Connectivity Strategist at GEOTAB and Paul Boyes, Community Director at COVESA share their perspectives on how a common approach for defining vehicle services will simplify system development and deployment. 





Ulf Björkengren, Principal Connectivity Strategist, GEOTAB

Paul Boyes, Community Director, COVESA

Open source software development today has a strong track record of producing high-quality code. However, this first requires an established common design. Preferably, this design should be developed in a similar open paradigm, and given approval from the relevant industry as a formal or de-facto standard.

The shared efforts in this scenario lead to a simplified development effort from participating members, compared to doing it solely, and the interoperability that standards provide also leads to a simplified "plug-in" deployment. 

In the world of connected vehicles, everyone wants access to vehicle data and functions from both outside and inside the vehicle. The only way to do this in a sane efficient way is to standardize vehicle interfaces and data. The time is right for multiple automakers to make this a reality. If I were an OEM, given the recent announcement by Apple, it would be a priority to me to work with other OEMs to tell the big tech companies, “This is how you interface with our vehicle.” Currently, it is often the other way around. This would be a win all around for consumers, OEMs, and tech companies.



For more information about COVESA, visit our website and blog.

  • No labels