JOIN/SIGN UP

Join COVESA

Already a Member?
     ▷Sign Up for Member Newsletter

     ▷Request Wiki Account (Needed for Write Access)

GET INVOLVED

COVESA Getting Started

COVESA Community Calendar - Weekly Meeting Schedule

COVESA Communication Channels (Slack, Mailing Lists)

COVESA Github Repository

Project Launch Process

COVESA Briefing/Overview Deck

COLLABORATIVE PROJECTS

Data Expert Group
▶︎ Data Models and Ontologies
     ▷ Vehicle Signal Specification (VSS)
     ▷ Vehicle Signal Specification Ontology (VSSo) - W3C Collaboration
▶︎ Architecture and Infrastructure
     ▷ Data Architecture Terminology (including Logical Components)
▶︎ Interface Definition
     ▷ Vehicle API
     ▷ Vehicle Service Catalog (VSC)
     ▷ Vehicle Information Service Specification (VISS) - W3C Collaboration
▶︎ Best Practices
     ▷ Governance
     ▷ Privacy and Identity
     ▷ Data Model Definition
     ▷ API First
 
Data Expert Group Workshop 2023Q428 at Spring AMM
Data Expert Group Workshop 2023Q1

Electric Vehicle Charging Expert Group
▶︎ EV Charging Event Data Aggregation Project
▶︎ EV Optimization - Increase Travel Range for Fixed Battery
▶︎ Private Cross OEM Joint Compute for EV Charging

Android™ Automotive SIG
▶︎ Automotive AOSP App Framework Standardization

Security Team

Simulation and Tooling
▶︎ digital.auto

Vehicle Experience and Content - Entertainment BoF
▶︎ In-vehicle Payment SIG

Commercial Vehicle BoF

HISTORICAL

Common Vehicle Interface Initiative

Cloud & Connected Services Project

SDV Telemetry Project - On Hold

Events

Industry Events

Industry Events 2023

COVESA Events

April 2023 All Member Meeting

October 2022 All Member Meeting

April 2022 All Member Meeting

October 2021 All Member Meeting

May 2021 All Member Meeting

October 2020 All Member Meeting

May 2020 Virtual Technical Summit

November 2019 Technical Summit

May 2019 All Member Meeting

Contact Us

Blog

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

COVESA Roundtable: What is the adoption potential for a single method of defining vehicle data in the collection, exchange and usage of that vehicle data?

Ulf Bjorkengren, Senior Connectivity Strategist at Geotab, and Paul Boyes, Community Director at COVESA, offer their perspectives on the adoption potential for a single method of defining vehicle data.


Ulf Bjorkengren, Senior Connectivity Strategist, Geotab

Paul Boyes, Community Director, COVESA

To answer this question, one could look back to when the mobile phone industry transformed from the manufacturer proprietary solutions to the more open solutions such as Android and iOS. This led to an explosion of new apps providing completely new levels of innovative services. A similar development is very likely when OEMs now adopt VSS as a common data model, together with adoption of standardized solutions for transporting this data from vehicle to the cloud such as W3C VISSv2. This gives vehicle data providers the opportunity to leverage the interoperability potential to accelerate the innovation of services through the upscaling of development resources that a vibrant 3rd party app ecosystem makes possible.

The adoption potential of agreed upon methods of defining, cataloging, and communicating vehicle data is almost guaranteed. As a matter of fact, it is required to realize the promise of the mobility revolution. When a vehicle needs to communicate with a vehicle from another manufacturer, devices, infrastructure, anything… a shared understanding of what is being communicated is imperative. It also facilitates scale of a broader ecosystem in the development of compelling features and digital services. Will it be a single shared method, model or catalog? Maybe… More importantly, a collaborative ecosystem is required and COVESA VSS and CVII are excellent starts. Open always wins.


If you are interested in contributing to the COVESA roundtable or have topic suggestions, please email marketing@covesa.global.