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.


Day 1

15 February - 5 am - 9 am PT / 1400 - 1800 CET 

ICS File

Agenda


Time (minutes)ItemSession Leaders/PresentersNotes
30IntroductionsPaul Boyes, Erik Jaegervall, Adnan Bekan, Stephen Lawrence

Theme:

What problem are we trying to solve?

What are we producing in what time frame?


60

Data Centric Architecture Overview and Group Alignment

  • Motivations/goals
  • Key questions to be answered
  • Data domains
  • Data characterization


Erik Jaegervall, Adnan Bekan, Stephen Lawrence

Compare interface types

  • type of data
  • levels
  • pros/cons
  • environmental constraints (e.g. compute power) 
  • Consider existing/previous work
    • Existing protocols exposing VSS?
    • Vehicle Information Service Specification

Presentation Material:


60

Choose Specific Touch Points/ Scenarios to Drill Into

 For example:

  • Head Unit to Android in-vehicle hosted OS 
  • Zone ECU to Head Unit
  • ECU to Edge compute device in vehicle
  • Zone ECU to TCU

Collaboration Session (Miro Board

Erik Jaegervall, Adnan Bekan, Stephen Lawrence

Common ways of describing and exposing/exchanging data

Agree on specific examples to drill into

60

Drill Into Specific Context/Interface/Arch

Collaboration Session (Miro Board) -

Erik Jaegervall, Adnan Bekan, Stephen Lawrence
30Wrap-Up and Next StepsPaul Boyes, Erik Jaegervall, Adnan Bekan, Stephen LawrenceConcrete action items for next day


Day 2

16 February - 5 am - 9 am PT / 1400 - 1800 CET

ICS File


Time (minutes)ItemSession Leaders/PresentersNotes
30

Review Previous Day

Questions/Discussion

Paul Boyes, Erik Jaegervall, Adnan Bekan, Stephen Lawrence
150

Drill Into Specific Context/Interface/Arch - Continued 


Erik Jaegervall, Adnan Bekan, Stephen Lawrence
60

Roadmap

  • Specific Work Product Identified 
  • Work Product Completion On Timeline (as possible)
Erik Jaegervall, Adnan Bekan, Stephen LawrenceLet's do our best to identify work product over time using AMMs and CES as milestones
30

Wrap-Up and Next Steps

  • Action Items
  • AMM - Workshop
Paul Boyes, Erik Jaegervall, Adnan Bekan, Stephen Lawrence




Proposed Agenda Ideas

Below is a working table to collect proposal idea.  The actual agenda is above.


TopicWhyProposed ByPriority

Target roadmap for 2023

  • Milestones for Spring AMM
  • Milestones for Fall AMM
  • Milestones for CES 

Where do we wish to take the Data Expert Group and when?  We should have basic agreed upon direction for launching and maturing projects and initiatives with-in the 4 pillars of the Data Expert Group. 

We should use the AMMs and CES as the bounding milestone events/dates.


Data Security and Privacy Best PracticeThis has been called out as one of the Best Practice pillars topics.  What would be useful to the community here?  A white paper?  Aggregation of existing practices?  Regulation overview?
VSS How To and/or Implementation guidesHow do users implement VSS in-vehicle, out of vehicle, from vehicle to out of vehicle?  How do they facilitate interoperability?  How do you know and validate that your implementation will allow you to easily share data, integrate, interoperate with others?
How does VSS relate to other models/the world?VSS as a common way of describing vehicle data is useful and a good start.  It becomes very powerful when used to relate vehicles to other models?  In other words, how does VSS related to EV charging, Points of Interest, road infrastructure, ...
Complex Types


Data Architecture Pillar

Two themes:

  • The general data centric data architecture pattern
    • Motivations/goals
    • Key questions to be answered
    • Data domains
    • Data characterisation
  • More descriptive/prescriptive orientations of the pattern for specific use cases or touchpoints
    • e.g. Android touch-point:
      • Methods of signal abstraction via VHAL or VSS Data Server
      • App connection via cloud and in-vehicle

AMM Planning

What to present/discuss, who shall do it, ..

  • Possibly: the "Ulf evolution multiple tree proposal"

VSS general roadmapWhat needs attention?

How to get attractive documentation/guides

How can we achieve a nice "goto site" for all VSS questions


"Describe/identify a few scenarios; xxx, yyyy, zzzz, ....

"If you want to do xxxx, then the challenges are .... If you want inspiration you can look at this presentation..."


An idea at: https://github.com/erikbosch/doc_test/blob/master/architecture_overview.md

Possibly merge it with https://covesa.github.io/vehicle_signal_specification/






  • No labels