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.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

NOTE: POSTPONED - No F2F in July

Agenda July 25th (Virtual)


Please add items to agenda

  • Two goals
    1. Aspect of common catalog
    2. Tooling for translation

Use them as base for the discussion

September Session


Full workshop at AMM

AMM is Oct 10-12th, possibly on Monday 9th


General Discussions Below

Open Issues:

  • 4 Hour Online Workshop:  July 21? 24? 25?
  • 4 Hour Online Workshop:  Sept?
  • F2F at AMM 
  • Number of days/date?  1 or 2?  18th or 19th?  18th allows for some to participate 1/2 day.  Due to conflict with Board meeting, they will not be able to attend on the 19th.
  • Need a place/room.  Ford has some but requires a Ford employee to be present.  Currently no Ford employees are available to attend in person.
  • Who can attend in person?  Do we have enough people?

Workshop Purpose

  • Achieve consensus and alignment at a high level on the purpose/why of the following Interface Pillar projects. 
  • Drill into interface definition, translation and exchange and emerge with a focused collaborative plan for execution with near term wins

Overview

There are 4 projects/initiatives in the DEG Interface Pillar that have emerged over the years with varying level or agreement by members.  Common agreed service and interfaces specifications that align around a common data model have become increasingly important to the connected vehicle ecosystem, as such, they have become central to COVESA.  These common interfaces and data model are critical to enabling the future.  It is time to come to agreement and align this pillar and projects in the industry.

Projects

IFEX - general interface description and transformation technology

Vehicle Services Catalog - service/API descriptions for vehicles in a standard catalog

Vehicle API - expose vehicle data as defined and described by COVESA's Vehicle Signal Specification to a  variety of agreed upon touch-points in and out of the vehicle 

W3C VISS - service for accessing vehicle information, signals from sensors on control units within a vehicle's network.

VSS - vehicle data model.

Architecture

Data Centric Architecture 

Data Expert Group Architecture Diagram

Topics

The above projects fall into these four topics:

  • Service Capabilities - what does the service do?  For example, adjust seat, adjust hvac, play media, monitor driver, etc...
    • VSC 
  • Service Catalog - a list of service capabilities
    • VSC
  • Interface definition, translation and exchange
    • IFEX
  • Data servers (pub/sub, get/set service and data model they serve) 
    • VISS
    • Vehicle API


High Level Proposed Agenda Items: (Please Comment/Propose Items)

9-10am - Overview of Interface Pillar and Purpose of Current Projects

10-12am - Drill into the requirements of interface definition, translation, and exchange

12-2pm - Execution planning for interface definition, translation, and exchange

2-5pm - Drill into requirements of Service Capabilities and Catalog

Location:

(TBD)

Cologne, Germany


  • No labels