You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 67
Next »
Quick introduction:
All Resources:
It is still possible to add to the pre-workshop survey - to provide your opinion (because it is important!) fill it in here.
The question "Why automotive suppliers and data-focused companies need a Common Vehicle Interface Initiative" was addressed in this Mobex/ Automotive World Webinar.
The services aspects of CVII, Vehicle Service Catalog, and resulting Service Oriented Architectures were presented in another Mobex/Automotive World webinar. You can view the recorded webinar!
CVII future-looking presentation including Software-defined Vehicles and "Vehicle Cloud Computing" was presented at Focus - Software Defined Vehicle.
There is a recording available on request (send email).
VISS v2 protocol development (=web protocol for VSS data)
GENIVI Cloud & Connected Services – reference architecture for Vehicle-to-cloud, (using standard data model) – see project home page for information
Android Automotive SIG - Vehicle HAL topic is related since it also investigates the integration of Android with a full vehicle data model (VSS) → see project home page for information.
Backlog/Topics (in addition to active projects above)
User Identification – this is not the first/primary scope of CVII (establish data & services standards) but is an important part of authorizing data access, etc., so likely becoming an important side-topic project.
Introduction
In May of 2020, a number of companies initiated a conversation about the Common Vehicle Interface Initiative (CVII) in a panel discussion held at the GENIVI Virtual Tech Summit, which has led to W3C and GENIVI spearheading a coordination initiative in the automotive and web industries.
The core of the initiative gathers around this question: “Is it time to finally define the industry-wide standard vehicle data model?"
The initiative proposes some technologies but is not there primarily to add just another choice to the mix. It is there primarily to drive conversations between all conflicting projects towards alignment and compatibility – ultimately yielding a single consistent model for data and services.
The idea of inviting many industry development organizations to a wide initiative was based on seeing a number of industry trends, specific requests from some companies for a similar activity, and a natural extension of collaboration already in place between different industry organizations like GENIVI, W3C, Sensoris, AUTOSAR, and others.
After completing some initial activities (virtual panels, presentations, OEM-only-roundtable meetings, and other outreach), the initiative can now be considered started. The work is already underway and gradually being organized from an outreach discussion to become a proper project or collection of projects under the initiative.
1. OEM Panel during the GENIVI Virtual Event (27th October 1510 Central Europe Time / 10:00 am US Eastern Time) entitled "Why does the industry need a Common Vehicle Interface?"
Representatives from Ford, Renault, and Volvo Cars give compelling support for the initiative to build a common vehicle interface. Slides and recordings
A presentation of the CVII will be done in parallel during the plenary part of W3C TPAC and TPAC participants are invited to join the following workshop that takes place during the COVESA AMM. W3C members are encouraged to register for that event through their representatives. Since this is the plenary session for W3C, it has the opportunity to spread the word about this automotive-specific work to a variety of protocol experts in many other fields. If the participants are not already aware of the upcoming workshop, they will be invited to hop over to the Workshop when it starts.
3. CVII Work Definition Workshop (27th October, Europe/US time zone)
Following the introductory panel, there will be significant workshops in which we expect different stakeholders who are already active to lead discussions on various sub-topics that include
A very short introduction (most participants will already be active in the project, therefore we ask that new participants read the introductory material
in-vehicle standard interfaces vs. vehicle-to-cloud boundary
How to progress a common model and a common catalog as separate but synergistic parts.
Discussing the definition of the Technology Stack (common software solutions to process the common model)
Outreach and organization of this initiative across the industry, including multiple consortia.
4. Panel and workshop #2 (29th October, Asia/Europe time zone)
Re-broadcast of the panel presentation: Presenting industry reactions from car manufacturers under the title "Why does the industry need a Common Vehicle Interface?"
A slightly extended presentation to give an introduction to CVII.
Workshops focused on deep-dive discussion of alignment of standards across already existing initiatives, including for example SENSORiS, JASPAR, and more.
The invitation to the activities hosted in the GENIVI AMM extends to any industry participant who would like to join
5. Follow-up W3C+GENIVI+industry seminar/workshop to organize project (November, planning)
The agenda will be influenced by the outcome of the AMM workshops.