Antitrust statement

Meeting Minutes

15 April 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)
      • Bosch rFMS mapping in Eclipse SDV
    • 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

• • Data Marketplace POC demo (Swen) https://app.covesa.acc.am-isd.com/login (try it out and provide feedback)

15 April 2025

• • VSS meta data extensions
    • sampling: and other related metadata can be overloaded, different meaning depending on situtational understanding
      • On-board API reporting data broker broadcast capabilities, useful for third party apps running on-board (encryption: authentication: access_control:) and API
      • Prescriptive in how it wants data collected cf https://github.com/COVESA/commercial-vehicles/blob/main/tmp/convert-spreadsheet/insurance-output.yaml
      • Descriptive in how the data was collected
    • 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:
        • sampling_rate: "100 ms" (need more than just frequency, event, conditional and calculation. may have fallback preferences in collection request - issue 7)
        • retention_policy: "30 days"
        • data_privacy: "anonymized" (defined constants, aggregate, sensitive, consent - would need more details)
      • 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
      • usecase: OEM, COVESA_CV, 3RD_PARTY
      • importance:
      • category:
      • concept of time - issue 15
  • 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

...