Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Proposed Session Title

Description

Requested Duration (25 or 40 minutes)

Requested Day

(Wednesday or Thursday)

Speaker(s)

Comments

EXAMPLE:


Learning VSS:   A Deeper Dive

Taking the next steps with your understanding of VSS.  Learn from the pros as they walk through some how-tos.  Get your questions answered and learn how to get involved.

40Wednesday

What worked well last time?  What could be better?

CVI working group 

VSS extension for safety related data points :

  • How to model safety related features?
  • Which additional meta-data do we need?
40WednesdayHenkel Achim workshop or interactive presentation
Open1722 - Why, State and Future
  •  Project status
  • Linux Kernel driver
  • Upcoming extensions/updated IEEE 1722 standard
25Wednesday (well "before" showcase would be good)

So this would be sort of an extended "Project status" on the technical side. (We also will have a demo on the showcase)


If desired can additionally  also give a more generic talk WHY IEEE-1722 currently is the hype for E/E networks, what the uses are and what is going on with the "Remote Control Protocol" discussion. In that case I suggest putting that talk on the "earlier" day whereas the Project update as suggested here might move to the last day.


Alternatively combine both aspects in 40 min)

VSS-based offboard fleet-APIs

  • Open source based API-framework
  • Specification and implementation of VSS-based digital twin
  • Collaboration with Eclipse Meta-Modelling for data-semantics
30open

BOSCH Felix Loesch

Extension of the VSS tool-chain for cloud data-spaces  presented on AMM fall-meeting Novi 2024

Implementation of Virtual Sensors for predictive maintenance using VSS on automotive grade hardware 

  • Concrete example of the implementation of a Virtual Sensors Sensor using VSS and Kuksa on an S32G3 Hardware 
  • Agnostic implementation and flexibility in term terms of input and output signals in a Software Defined Vehicle context 
  • Provide through VS signal input. No more Hardware, now done Virtually 
  • Instead of physical hardware, virtual sensors provide vehicle signals.
  • New use cases can be enabled by adding VSS overlays corresponding to the new virtual sensor values (previously not available) on top of the standard VSS catalogue.Add new Signals with a Value on top of the existing catalog because before not measurable, enabling new usecases 
  • Extension of VSS to Predictive maintenance outputs, using the flexibility and openess openness of the VSS framework .
25Open (preferably Wednesday before Showcase)Join presentation with NXP and COMPREDICT to follow the ideation done at the AMM in Novi, Michigan, with concrete example and usecase for predictive maintenance leveraging NXP GoldBox and Virtual Sensor technology
Status update of the VISS and VISSR projectsPresentation of the latest release VISSv3.0, and of the VISSR support of the new specification.40OpenUlf Bjorkengren 
Status update of the Commercial Vehicle Information Specifications (CVIS) projectBesides the current project status a framework is presented that supports development of multiple trees sharing common objects as well as advanced configuration of a tree for deployment.40OpenUlf Bjorkengren 
An Automotive API and Data Model that caters to all types of vehicles.This proposal builds on results from the COVESA CVIS project where the HIM data model, that is an evolution of the VSS data model, is used to develop vehicle signal trees for trucks, trailers, busses, etc.40OpenUlf Bjorkengren