This is the landing page for the Architecture and Infrastructure pillar of the Data Expert Group.

Introduction

The COVESA Logical Architecture shows the Data Expert Group scope as being the large ECUs and above.

From the perspective of a DIKW Pyramid hierarchy we have:

1. Data Layer - native (raw) vehicle board-net data carried on vehicle buses such as CAN, LIN, FlexRay, Some/IP and DDS.
2. Information Layer - data in the VSS data-model abstracted from the data layer, along with data from other domains such as personal data.
3. Knowledge Layer - insights and wisdom derived from the Information Layer.

The Architecture and Infrastructure pillar is currently concentrating on data-centric architectures, with an emphasis on the needs of the Information and Knowledge layers in-vehicle, mobile devices and the cloud. For example, in the Information Layer that means technologies (software) providing data services for serving, storing and synchronizing data in VSS and other data-models, with the goal of making their adoption quicker and easier. That can be achieved through collaboration on specifications, design patterns, non-differentiating technology and PoCs to prove they work.

Projects

Information on the current projects, such as the Central Data Service Playground, can be found in the project list.

Communication

To avoid multiple sources of information please refer to the Data Expert Group main page for details of the community calendar and communication channels.

Currently the group meets weekly on Wednesday afternoons at 5pm CET:

Stephen Lawrence is inviting you to a scheduled Zoom meeting. 

Topic: Data Expert Group: Architecture and Infrastructure 
Time: Nov 2, 2022 05:00 PM Amsterdam, Berlin, Rome, Stockholm, Vienna 
	Every week on Wed, until Oct 11, 2023, 50 occurrence(s) 
	Nov 2, 2022 05:00 PM 
Please download and import the following iCalendar (.ics) files to your calendar system. 
Weekly: https://us06web.zoom.us/meeting/tZwodemppjotGdWrdaqM4LJ0ECSXsmxy4sz-/ics?icsToken=98tyKuGgqzkqG9yUtxqGRpw-GYjoc-vxiH5ajadqjhvkEg0HTimmE8FxCqFyCMGE 

Join Zoom Meeting https://us06web.zoom.us/j/88520181731?pwd=dnplcTdvT0dVdHNXYzdiQ1RjbFdYUT09

Meeting ID: 885 2018 1731 
Passcode: @DATA1

In Slack we use the data expert group channel. Hope to see you there.

The current Data-Architecture pillar lead is Stephen Lawrence (Renesas).

Sub-pages

• Architecture and Infrastructure Meeting Minutes
• Data Architecture / Infrastructure Pillar projects
  • Central Data Service Playground
    • Early planning
      • Artifact JSON-RDF Converter
      • Playground design artifact outline
    • Playground Development Notes
      • Embedded Databases (IoTDB, Realm etc)
      • VISSR (WAII) VISS Data Server
• Data Architecture Pillar Proposals
  • Central Data Service playground proposal
    • Central Data Service Playground outline
  • Design Pattern / Data Architecture documentation proposal
  • Proposal for the elaboration of a Data Architecture framework including a Knowledge Layer.
  • VSS Database Schema Generator
  • VSS Data Modeling for NoSQL Document Databases
• Data Architecture Terminology (incl. logical components)
• Planning Pages
  • 2023 Autumn AMM (Data Architecture and Infrastructure)
  • 2023 Spring AMM (Data Architecture and Infrastructure) Workshop
  • 2024 Autumn AMM Planning (Data Architecture and Infrastructure)
  • 2024 Spring AMM Planning (Data Architecture and Infrastructure)

Related earlier work (Cloud and Connected Services, CVII Tech Stack)

The Genivi Cloud & Connected Services (CCS) project investigated the requirements of open data capture in-vehicle and its connection to back-end systems in the cloud. One of the deliverables was this well known cloud reference architecture diagram:

Source: CCS Reference Architecture - Work Breakdown Structure

CCS was followed by the Common Vehicle Interface Initiative (CVII) Tech Stack project which investigated the software required to transfer and process the standard VSS data model. For that a mutual understanding of terms and common components were required. The latter resulted in this in-vehicle architecture diagram, which is intended to show the likely in-vehicle components and how they interact, rather than specify a specific monolithic architecture:

These two diagrams, the CCS Cloud reference architecture and the CVII Tech Stack in-vehicle architecture will be foundational building blocks for discussion of evolved versions in the Data Architecture and Infrastructure team.