Common Vehicle Interface Initiative OEM Roundtable 16 July

Common Vehicle Interface Initiative OEM Roundtable 16 July 2020

Agenda • • Introduction Round Background and Overview of CVII and related topics Statements from OEMs Open Dialog and Next Steps 2

Ongoing and future Industry Collaboration • GENIVI & W 3 C have a long history of producing industry-wide connectivity standards. • GENIVI has produced technologies compatible with AUTOSAR® Adaptive platform, and holds ongoing leadership-level discussion about future collaboration • GENIVI Cloud and Connected Services (CCS) project studies and coordinates with previous work in the area of data standards, including several government funded projects (Automat/CVIM, NEVADA from VDA) and industry-initiatives (Sensor. IS, ISO 27008 Extended Vehicle) • GENIVI & W 3 C is initiating the conversation about Common Vehicle Interface Initiative and recognizes that its execution needs to be widely connected. CVII needs an industry-wide conversation, which is the purpose of today’s dialog. Several consortia and standards bodies should be part of a shared movement. 3

What is the Common Vehicle Interface Initiative? Concrete deliverable view: Common Data Model and catalog Technical protocol and interface standards Common Service/ Interface Model and catalog 4

What is the Common Vehicle Interface Initiative? Common Data • An invitation to the automotive industry to discuss Model fundamental issues that will accelerate development and business value • An extension of the existing movement of Protocols and Common Service Interfacing Model “A common data model”, where Vehicle Signal Specification (VSS) is a driving example • A technology collaboration to define associated protocols (e. g. W 3 C VISS/Gen 2) and interfacing technologies to make use of the data/service model in real systems • A discussion on where standard interfaces are appropriate in the entire vehicle+cloud • A movement towards unification of fragmented ecosystems that inadequately address only part of this problem, and not in concert. • The initiative may include inside-vehicle: Standardized software components and welldefined interfaces between ECUs, and outside-vehicle: Remotely-accessible vehicle functions in the car-to-cloud infrastructure 5

Today’s automotive development trends • The software market place – interoperable components are as important as ever! • OEMs, Tier 1 s and platform providers need interoperability standards on data-model and APIs • Service Oriented Architecture trend enables agility and flexibility, does not eliminate integration work • Investment into shared infrastructure (Smart City, V 2 X) for connectivity functions -> requires standards • We see the “CVII” desire clearly (multiple companies, multiple conference talks on similar topic), but not coordinated yet • Non-automotive data and cloud-oriented companies (Amazon, Microsoft, start-ups) need interoperability standards for data and cloud solutions. • Business opportunities for vehicle data will reach its full potential by leveraging common and scalable data standards. • We believe as a conclusion that CVII is a necessary conversation in our industry! 6

Current status and next steps for CVII • GENIVI held a panel discussion at the Virtual GENIVI Tech Summit, May 2020 • VSS will now be complemented by Vehicle Service Catalog => VSC • Collaboration between GENIVI & W 3 C continues on protocol standards that serve VSS and VSC • We are inviting to industry-wide conversation with several consortia and standards bodies that should be part of a shared movement. • A potential next step is a broader workshop for awareness and definition, possibly including suppliers • First, OEM input is requested to adjust direction and focus 7

OEM supportive statements • Ford Motor Company • Jaguar Land Rover • BMW • followed by open dialog. 8

Thank you! Visit GENIVI: http: //www. genivi. org http: //projects. genivi. org Contact us: help@genivi. org

BACKUP SLIDES 10

Why is VSS (VSC) the appropriate “source format” • The selected format should be a plain-text, line-oriented format, like VSS: Any text editor – no special tooling for editing A line-oriented format reads like a normal logical hierarchical document would be written Is easy to read and write, also by non-programmers. ← MOST IMPORTANT FACTOR! A line-oriented format (YAML) promotes handling VSS like source code (version control in git repository, patches, change history, . . . ), unlike “syntax-oriented” (JSON, XML, …) which can be less convenient. Still has formal meaning, machine-processable input, and easy to write and extend tools. • VSS is plain-text as stated above, has several years of development, and includes: Easy, obvious hierarchical model Simple and recognizable data types Reasonable modelling power for signals/data (e. g. instantiation) • VSS is extensible using VSS-layers. Adds unique deployment information for different target environments. Adds your own (proprietary) signals and/or potentially local modification to common catalog when it is strictly required • VSS is only the source and model of our information → Proven conversion to other formats (including Graph. QL, JSON, XML, Franca IDL, ) • W 3 C develops official protocols for web-access to data with VSS as the primary data model 11

12