Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: final workshop plan

...

  1. In-vehicle
    • VSS Data Storage and Sync
    • CVII Tech Stack in-vehicle arch diagram => in-vehicle data architecture
    • Data filtering
      • Real-time vs historical
      • Change set vs sample
      • Ted: If we do should consider including curvelogging and connection to EV charging
    • Autosar, Vehicle API
  2. Cloud
    • CCS Architecture => Covesa Cloud Architecture
    • Ingest (Kafka etc.)
  3. V2C
  4. Data EG: Data Architecture / Infrastructure
    1. In-vehicle Data Storage and Sync PoC (BMW discussion - earlier discussion with MongoDB: https://www.w3.org/2022/01/25-auto-minutes)
  5. VISSv2 client from UMA
    1. Has security track connection also.


Session timetable planning (Data Expert Group Working Internal planning page for COVESA AMM October 2022):

  1. Steve: Very brief recap of the project scope
  2. BMW/MongoDB: Presentation by BMW and MongoDB combining return of experience and input
  3. All: technical workshop agreeing the next collaboration work for the in-scope touch points within In-vehicle, Vehicle2Cloud and Cloud
    1. What are the gaps? What do people want to work on?
    2. In the case of in-vehicle interest has been shown in VSS Data Storage and Sync. Work on moving that towards a plan.