COVESA Getting Started

COVESA Community Calendar - Weekly Meeting Schedule

COVESA Communication Channels (Slack, Mailing Lists, Calendar)

COVESA Github Repository

Project Launch Process

Request Wiki Account


COVESA Briefing/Overview Deck


Data Expert Group
▶︎ Data Models and Ontologies
     ▷ Vehicle Signal Specification (VSS)
     ▷ Vehicle Signal Specification Ontology (VSSo) - W3C Collaboration
▶︎ Architecture and Infrastructure
▶︎ 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 2023Q1

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

Android™ Automotive SIG
▶︎ Android Automotive White Label App Store

Security Team

Simulation and Tooling

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


Common Vehicle Interface Initiative

Cloud & Connected Services Project

SDV Telemetry Project - On Hold


Industry Events

Industry Events 2023


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

Child pages
  • Tech Brief planning on CCS mapping to cloud providers

We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.

Skip to end of metadata
Go to start of metadata

Brainstorm (document structure, headings, content, principles, goals...)

Headings / Main Topics

  • DevOps
  • Microservices
  • Serverless
  • Containerisation

Principles for the document:

  • General explanation of each concept
  • Benefits of this in CCS context would be included

Topics likely to be covered:

  • Cloud-first approach
  • Agility, scalability, performance
  • Modern architecture characteristics (using microservices, containerisation etc.)
  • Advantages:  Higher performance, improved efficiency of underlying resources, cost savings, auto-scaling, load-balancing...
  • Proof of Concepts ← important principle, validate technical decisions.
    • Refer to the PoC (CCS)
  • Minimum Viable Product - MVP principle
  • Use infrastructure-as-code
  • Existing ecosystem / legacy systems integration, ...
  • References - sources for information / claims, and where to find more (joining the project etc.)

(question) Compare Cloud provider platform/software offers?

  • Initially was considered to be left out.  (keep it purely technical overview)
    ... but should be mention at minimum to reference what we know (that we know) about the different capabilities and offers.

(question) Reference Architecture?

  • reference CCS arch, advocacy for usefulness?
  • Different subsections of "whole system" such as cloud, vehicle, edge.

(question) CVII connection?

  • Effects of the existence of an agreed-upon data / services standard?


  • Introduction chapter should give "scope limit" for document.
  • Also, is there a problem statement, current state of practice - can we describe a solution
  • Are there other aspects of "OEMs doing things in a unique vs. similar way" that should be highlighted (not about data-model and the core of CVII goals, but other aspects)

References / earlier work

  • No labels