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

This page is an aggregation of links to various Vehicle Signal Specifications resources.  It is intended to provide a quick reference access to everything VSS.  If you do not find what you are looking for or see things that are missing, please let us know.


The VSS page on this wiki is a good starting point that leads/points to all of the other locations.   

Calendar and Collaboration Channels (mailing lists and Slack)


GitHub is where almost all of the VSS project work is maintained.  The main page contains links to   

  • Documentation

    • A straight forward set of topics that give a good overview of VSS

  • Releases

    • Release links with lists of what has changed

  • Specification/Catalog

    • VSS specification refers to the standard catalog. It is maintained in yaml.  It is fully expected that not everyone will implement all data elements/signals and they will likely implement some number of proprietary elements/signals.  VSS is still a useful methodology/rule set for defining interoperable models.

  • Tools

    • Tools are maintained in a separate repository

  • GitHub Project wiki

    • VSS project team uses the VSS wiki for documenting a variety of things including releases.

  • Pull Requests 

    • All edits and updates are presented to the team through Pull Requests and are discussed in weekly meetings.

  • Issues

    • All issues are tracked through GitHub issues

Presentations and Decks

  • Introduction to Vehicle Signal Specification at COVESA AMM October 2022 (deck)
  • Introduction to Vehicle Signal Specification (presentation) at COVESA AMM April 2022 (deck)
  • VSS and VSS Ontology (presentation) at at COVESA AMM Spring 2022 (deck)

How and where VSS is used?

There are various implementations where VSS is used as data model for vehicle data.  Beside several closed-source implementations, here are the ones that are shared publicly:

OEM Adoption

  • BMW
    • Mapped proprietary descriptions of vehicle data to VSS, for millions of cars.
    • Employing GraphQL to create a backend single access layer for querying data coming from various storage and streaming systems. Demonstrated backend application based on this solution. While for data streaming use cases, other technologies that are supporting VSS might be in place.
  • Volvo
  • Ford 
    • EV Charging Event Data Aggregation project led by Ford is actively updating the VSS model for EV Charging 
    • Internally working with VSS as a starting point for a variety of data related and development projects
  • Mercedes 
    • Internally working with VSS as a starting point for a variety of data related and development projects

Joint Projects with W3C

Covesa has joint projects to develop and standardize certain technology through the W3C process.

  • No labels