Versions Compared

Old Version 93

changes.mady.by.user Ted Guild

Saved on

compared with

New Version Current

changes.mady.by.user Ted Guild

Saved on

Key

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

Antitrust statement

Meeting Minutes

29 January 2025



24 June 2025


Stefan Werder (Bosch) joined for Sensoris perspective and previous VSS comparison analysis

Moving from protobuf to ISO https://tisa.org/

https://www.sae.org/binaries/content/assets/cm/content/miscellaneous/adas-nomenclature.pdf

https://docs.google.com/spreadsheets/d/1L4cUQZB0rAUvNC2iFL-GYNIUqAohWnvZ/edit?gid=1214249666#gid=1214249666


17 June 2025


Insurance signals continued


10 June 2025

(short call, low attendance)

Insurance signals continued, initial reception on VSS call to Issue 830

Sensoris https://sensoris.org/presentations/


3 June 2025

Insurance signals - second and third priority, object detection/GIS categorization

Summer Schedule: play by ear


27 May 2025

    • ADAS/AV/automotive AI standards work taking place anywhere?  perhaps with an insurance focus
      • InsureVision will be joining COVESA and interested in onboard/edge AI
      • GraphQL project - facilitates AI processing VSS and related/linked data
      • ADAS - object detection - AI and camera - conversation with Blackberry Ivy (Jasmin Mulaosmanovic, Robert Dugal)
        • Driving Monitoring System (DMS) already in VSS has AI derived analysis of driver
      • Would OEM harmonize/standardize AI on vehicle edge? there would be demand but understand hesistation and how AI might have tighter integration with underlying vehicle
      • Example being improved range prediction, allow for competing logic or normalized/consistent logic
    • Toyota Connect moving forward on VSS
    • Waiting on ACEA FMS trailer signals
    • Next steps
      • Outreach, prototype or production adoption of VSS/FMD 
        • MongoDB FMD demo - will invite here or have separate call
        • Bosch's Eclipse SDV Blueprint - potentially with Volvo Group
      • Return to second and third priority insurance signals from list, bringing to VSS missing data points
        • Paul to introduce Ted to Sensoris on object detection/observations/signage - potentially bridge to VSS
        • Ted to reach out to Open Geospatial Consortium (OGC) - any standardization of GIS being exposed in-vehicle
        • ITS, TISA - traffic jams, dangerous intersections, other conditions
      • Sync with Chitanya (Ford) on sampling metadata

20 May 2025

    • ACORD - uptake with insurance?
    • BMW now supporting VSS in cloud offering
      • Report from colleague on their earlier offering and what is missing from Fleet Management Data (FMD) perspective
      • Will try to approach from our business contacts, BMW research doesn't think they can help
    • AMM debrief
      • CV track
        • Bosch's Trucks on a leash demo using FMD, open source in Eclipse SDV
        • MongoDB demo using FMD
        • Florian led AOSP hackathon in their workshop, Remotive had an impressive demo
          • Another AOSP app to access camera, was successful. Used sensor data as events to trigger camera - g-force from accelerometer 
      • EU Data Act
        • Trying to get coordination with Mobility Data Space (EU) 
        • German insurance association preferred proprietary option to COVESA open source
        • Data quality concerns and meta data discussions (including eg use cases and sampling rate) - impacts usefulness of data
          • learned an important distinction - may only apply to raw data that supports services not all data OEM collects
      • Data Ecosystem - working session and demo
      • Discussion with a HD OEM, Bosch on PoC of ACEA FMS + trailer - especially upfitted (refrigeration)
      • Vehicle Data Model / VSS Debate
        • CVIS approach
        • TST discussion, requirements


6 May 2025


AMM Agenda review of adjacent topics to increase coverage, understanding of their work and promoting our activity


27 April 2025

    • Insurance proposal
      • Input for German Insurance Association to counter a proprietary proposal, to go to EU Insurance Association and feedback to EU commission on EU Data Act
      • Allianz also presenting VSS based solution to undisclosed OEM
      • Ted to inform COVESA EU Data Act project call on both Insurance proposal and ACEA FMS collaboration 
    • ACEA FMS collaboration proceeding, gap analysis done, agreements on scoped work, MoU to be drafted and sent to COVESA Board
      • API/Protocol discussion - Ulf point on VISS/R
      • VSS extensions for truck - in ACEA with attendees from COVESA (Mouham Tanimou and Ted)
      • Other data models in CVIS - Upfitting, Driver, etc and can experiment/contrast overlay and HIM
      • Raise to CV, VSS or DEG as appropriate 
      • Action: Paul to make nominations as described above to ACEA
    • TST discussion of Vehicle Data Model and need for GraphQL PoC - initial VSS GraphQL schema created by BMW in vss-tools repo
      • modelling work to take place in GraphQL
      • relate to Data Marketplace POC from Swen/Endava presented last week
      • Cloud to cloud, big data and third parties in a marketplace could leverage GraphQL REST capabilities
      • IETF GNAP, W3C Verifiable Claims (a form of DID as required by EU Digital Identity Act, implementation nearing production in US state[s] for vehicle registration, insurer and driver data) and/or other?  ideally settle on broadly used information architecture

22 April 2025

15 April 2025

    • VSS meta data extensions
      • sampling: and other related metadata can be overloaded, different meaning depending on situtational understanding
      • Use of declared constants, some should be part of profile definitions
      • Privacy - Suggest bringing to EU Data Act project call
        • privacy_domain: [VehicleData, DriverData, LocationData, other?] use CONSTANTS, namespace or YAML declarations
        • data_collection:
        • network_serialization:
          • cycle_time: "10ms"
          • message_priority: "high" (timeliness of data can be highly important to third party, curve logging and other sampling conventions can help)
          • transmission_mode: "Periodotic"
      • Calculations and conditionals - issue 4
        • operational_conditions: "Normal operation, not during engine startup" - rewrite as a calculation based on other signals
        • dependencies: Vehicle.Powertrain.EngineCoolant.Level Vehicle.Powertrain.EngineCoolant.Pressure
        • minimum_send_interval: 
        • platform_system: motion_plus - this an on-board API and Supplier or OEM identifier? of interest to third party, example insurance using data in forensic evidence after an accident
      • Other we have in our collection campaign descriptions
    • CVIS AMM Slide review (Ulf)


8 April 2025

    • AMM working session planning
      • Overlays, profiles in general and data sampling in particular - present both campaigns but focus more on insurance details
      • Requested and regulator required data (different regions)* webinar reminder tomorrow
    • AMM presentation practice and feedback (Ian and/or Ulf)
    • Driver data - CVIS, US state DMV, regional regulations for HD truck operation, insurance, fleet ops
      • Request for input, regional requirements for HD, insurance, registry etc
      • Interest in driving time - for non-commercial (pass car) - fatigue and UBI 
      • In EU, governed by GDPR, not granular approval as in US/CA National Insurance Commissioners S* (NICS)
    • AOB

1 April 2025

    • ACEA signals list from EU Data Act project, intent to compare with ACEA FMS, Fleet Management Data Guidelines, Insurance Signals Guidelines (CV data campaigns), Battery Passport, other? Discussion of motivation, solicit assistance in identifying regulator or requested (eg CV) signals lists and contributing to github.
    • No progress on Profiles and proposed data sampling conventions
      • publish drafts of data campaigns for AMM? yes/no decision
    • Starting to liaise with ATA TMC SG12 on RP1230 - NA equiv of ACEA FMS
    • AOB / AMM draft presentations 

25 March 2025

    • Partial meeting, scant attendance
    • Interest in ACEA FMS less SAE J1939 as that has been a blocker

18 March 2025

    • ACEA FMS/COVESA collaboration
    • Allianz' AMM presentation
    • Monitoring progress on Profiles discussion in VSS w/ Ford & Bosch
      • hoping for conclusions before AMM for our fleet and insurance data campaigns - publish drafts if not?
    • AOB

11 March 2025

    • Coordination on 11 Feb issues list

4 March 2025

no meeting, infoshare

25 February 2025

18 February 2025

    • AMM Registration and CV, related track
      • Business: Data marketplace: Endava (big picture)
      • Business: Insurance: UBI and AI (MOTER)
      • Business: Big picture panel (insurance, AOSP, CV, data marketplace, EU Data act, in-vehicle API, ACEA FMS...)
      • AOSP and CV - pending (P3)
      • Business: unlikely, perhaps Technical track instead. ACEA FMS: want HD OEM recommendation. Achim invited Armin + FMS committee to AMM,  (Ford, DAF or Scania participants can make good candidates)
        • Alternate idea: Workshop would be useful if we can get FMS attendance and space from Paul for half a day (Tuesday afternoon)/could be a shorter tech track working session
      • Tech track (see below)
      • Tech: Eclipse SDV Fleet Blueprint: Trucks on a leash
      • Tech: Data marketplace showcase (Swen)
        • metadata needs
    • Video needs (further discussion to bring to VSS and/or AMM working session)
    • Issues for CV: still need to schedule w/ Erik 
    • Norwegian Traffic Agency project AOSP+FMD based

11 February 2025

    • Co-Chairing: welcome Mouham (Bosch), others interested? 
    • AMM CV track - including tying to EU Data Act project, AOSP data workstream* Bosch incorporating our use cases and going to select one or more for PoC
      • Business Track (main stage)
        • Insurance and fleet presentations or panel?
        • Big picture/ecosystem
        • Do not expect to be enough of substance on FMS for AMM - maybe high level intent from HD OEM
      • Technical track (breakout rooms)
        • Insurance and fleet data campaign presentation and solicit input/discussion
          • overview of in-vehicle API for FMS and RP1230
        • Insurance use cases in AOSP - VHAL assessment (Ian)
        • CVIS status update (Ulf)
        • Working session (EU, AOSP, CV, Data Marketplace, FMS other, MDS)
          • priorities
    • Insurance campaign YAML produced, needs polishing
      • VHAL signals from MOTER
        • accelerometer missing in VHAL but avail in Android (supported in phones)
        • no units of measurement analysis/comparison yet
        • GIS missing - speed and other signage (expect available in Google Maps - part of GAS of AA not AOSP) - bring up with Google
        • no DMS nor AV, less ADAS
        • no oil pressure, other scattered missing, no odo, travel distance
    • Insurance signals and tooling, need to come up with new workflow
      • nearby discussion in VSS call on more advanced representations than YAML
      • "Profiles" (vss-tools #436) - meta data in overlays
      • mathematical expressions in VSPEC YAML - maybe out of scope for v1 campaigns
      • Min/max API, alternate sampling representations
      • Would like dedicated call w/ Erik Jagervall & others to advance some of these discussions, we can be helpful in testing out 
    • FMS moving forward, getting started and informally (more lightweight) but slow

5 February 2025

    • Call schedule shift due to conflict with EU Data act project and collapsing insurance breakout call back into CV
    • AMM CV track
    • ACEA FMS meet tomorrow, formalizing arrangement with COVESA
    • Insurance signals and tooling, need to come up with new workflow (deferred)

29 January 2025

    • ACEA FMS, 6 Feb prep - MoU w/ COVESA and other legal topics of liaison. separate from pending response from SAE on J1939 licensing
    • VHAL mapping for insurance signals 
    • Tooling on generating YAML Overlay 
      • Suggestion from Achim: min/max rate on sampling/broadcast frequency when on vehicle edge (eg AOSP on IVI and/or TCU).
        • Clear difference depending on whether sampled, off-boarded and available in cloud versus supporting in-vehicle environment. We should have both defined separately
        • Limitations of the underlying sensor/ECU - we can have our desired range defined in VSS but the underlying system could expose actual available using the same meta-data attribute (wishlist vs actual). Variation in actual may be indicator of faulty component and maintenance need. AutoSAR always have a max - applied to filtered stream as CAN broadcast frequency might be even higher but the databroker feeding AutoSAR may have imposed limit. Want to be able to recognise difference and whether use case can be supported
        • Summary: desired in-vehicle and off-board need to be defined separately, also use the same metadata to reflect actual (collected for off-board or available in-vehicle) 
        • When/how data is sampled is a potential additional requirement for GDPR - eg GPS only collected and shared with E911 type services in event of an accident
    • Issues

    ...