Versions Compared

Old Version 64

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

16 October 2024



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
    • Video 
    • OEM outreach: candidates and contacts (Daimler NA, Stellantis NA, Asian in EU, Volvo car EU)
      • additionally bring to AOSP data and EU Data Act groups in COVESA 
    • Roland Berger whitepaper on COVESA and connected vehicle data (pending)

22 January 2025

Review Data Exchange Platform and related pages


21 January 2025 - insurance


Review of sampling in insurance data campaign, brief explanation of curve logging, incorporating SAE ADAS signals into data campaign


15 January 2025

    • CES highlights - AI, AV, Automation 
    • CV blog
    • Change of chairing - addition of Kai or Achim and potential continuation from Thomas? Check in with Paul re Ford
    • Review work topics/level set
      • EU Data Act project in DEG coordination
      • Similar strong interest in data exchange platform proposal
        • update next week and prototype planned for next AMM
          • will need assistance on legal aspects
      • Video - black box
        • Privacy concerns
          • internal (DMS, assessments not clips)
          • anonymization
          • varying capabilities
          • applicability to aftermarket - same legal requirements
      •  ACEA FMS to formalise further (draft MOU being circulated) and next meeting 6 Feb 
        • CVIS breakout on hold until HD OEM appear - Thomas shares update on Volvo Group effort and possible interest/collaboration
        • Upfitting on pause, awaiting Ford engagement 
      • SAE ICT coordination - also hoping to get assistance on J1939 licensing/fair use clarification
    • COVESA AMM in Berlin, ear;y May
      • possible hydrogen truck being in showcase, interest in CV and surfacing data. internal architecture is extensively VSS - including hydrogen specific signals

14 January 2025 - insurance signals

    • Review work topics
      • publish insurance and fleet data campaigns - Ted, started staging in December, no progress over holidays
      • video data - produce a presentation or paper to VSS group on what insurance/fleet would like to see for video data, expand on notes - draft Stefan, input/review Ted and others
      • AOSP data - attend, ensure use cases covered for:
        • VSS/VHAL
          • data collection - prioritise signals and fidelity from data campaigns
        • consent capture - inform operator owner has granted permission for data collection - immutable
          • web based so people can change prefs from phone or laptop
        • driver coaching - necessitates need for in-vehicle data and processing
        • hours of service (HOS - US/Canada regulation for HD trucks), similar in EU but dedicated hardware at present
      • Promotion, outreach and lobbying
        • TSP and Insurance companies - review earlier list and assign, plan to do so in a few weeks as draft campaigns are available for review
          • Schedule and informative workshop during regular call time 
        • ACEA members pushing EU commission towards VSS for Data Act - would be helpful for data consumers to weigh in - Ted to reach out to Nils Lagerqvist *Volvo cars
      • EU data act - besides lobbying
        • Swen's data exchange platform
        • Propose our data campaigns as priority - benefits for OEM who want to control/limit data flows
    • CES presentation by MOTER


18 December 2024

    • EU Data Act DEG project proposal - shared goal of using VSS from OEM cloud to  interested/approved first and third parties
    • CV blog input
    • Insurance and fleet campaign representations in YAML - quick tour, will be staged in github
    • Video continued - intent to wrap up notes and provide as input (paper or presentation) to VSS group
    • Miro continued (depending on attendees)
    • Happy Holidays, next meetings 14 January 2025 (insurance) 15 January (CV)


17 December 2024 - insurance signals

    • Insurance campaign representation in YAML
    • EU Data Act DEG project proposal 
    • short call


11 December 2024

    • Scope of FMS collaboration - TBD, awaiting proposed liaison agreement from ACEA in Q1 2025 (4 or 5 February)
      • Thomas and Ted drafted this high level work statement upon request: The FMS to VSS mapping solves the problem of hardware coupling found in J1939 implementations. This J-standard is typically used as a backbone for many Northbound Telematics use-cases with Heavy commercial vehicles. This mapping will enable an abstraction layer for the new FMS on-board API.
      • Invitees for ACEA discussion: Kai Hudalla (Bosch), Steve Crumb, Paul Boyes, Ted Guild, Wally Stegall additional Bosch: Micha, Achim, Mouham 
      • Licensing (COVESA MPL2) needs to be clear in MoU/liaison agreement - still awaiting response from SAE - nudged last week
      • Also FMS API part of existing CV charter
    • CV blog pending, will share on slack channel for input
    • Add week of 6 January as off week due to CES
    • Miro board exercise
    • Data exchange use cases input - not for this week, early next year. Discussions advancing with Eclipse, MS, others. Will reach out to AWS Fleetwise - Thomas to introduce Swen
    • Video conversation continued and next steps

10 December 2024 - insurance signals

    • Continue review of ADAS spreasheet, Obstacle Detection and Adaptive Cruise Control merged and now part of VSS
    • Ted and Thomas to work on YAML overlay of latest development version of VSS and insurance signals spreadsheet, also fleet data campaign
    • MOTER to focus on VHAL mapping later this year
    • Short call

4 December 2024

    • Holiday schedule (no meetings weeks of 23, 30 December and 6 January for CVIS, insurance signals and CV)
    • Tracking deliverables
      • need for accompanying implementation documentation on parameters of campaign, guidelines in general
      • roadmap when available - define when possible
        • diagram in miro ecosystem/marketplace, aosp and other in-vehicle apis, campaigns 
    • End of year nudges (SAE ITC, HD OEM, EV bus OEM, Stellantis, Japanese OEM in two regions...)
    • Camera discussion - meta data, use cases and provide input to VSS group

      Camera count (#)

      Resolution, FPS rate of camera

      Lens of camera (important for later analysis on videos)
      f-stop, manufacturer, identifier (sn) - video used as evidence in legal disputes

      Last calibration date - need to be done upon repairs, sometimes not done so worth tracking
      \either in workshop or in-vehicle, remotely

      Error/status before and after crash event

      Selection of camera (internal, external front, back, left side, right side, surround view)

      **Stream versus buffer (clip)
      relates to consent/privacy - willingness to share with specific party in certain events
      stream - higher bandwidth and cloud storage costs

      review how video is being handled in Android Automotive

      interest in object detection/identification - in-vehicle analysis and send observations instead of video similar to DMS in VSS

      Definition of conditions for camera feed to be stored (trigger events to be configurable- e.g. accident critical event or specific situation e.g. “pedestrians close to the vehicle. Time to collision below threshold”)

      Configuration of duration of video buffer - of seconds before and after an event

      Configuration of post processed video (e.g. privacy mode – anonymization of license plates, faces, reduced resolution)

      Live feed transmission or store video locally for later retrieval

      Configuration of context data (e.g. sensor data, time stamp) to be stored with a video triggered by a trigger event 

    • ADAS 
    • Check-in on ecosystem use cases

3 December 2024 - insurance signals 

Review of SAE ADAS descriptors and capabilities, compare to insurance signals, MOTER add VHAL to insurance signals spreadsheet, Ted to complete "In data campaign spreadsheet" (column c of ADAS sheet) 


Ensure VSS captures both warning (singular or levels) and intervention within same or adjacent signals (review required of VSS)

Insurance interest in video should be shaped and shared with VSS EG as COVESA intends to address need for video and other data streams


27 November 2024

    • Ecosystem/marketplace - Swen - request for input in general and use cases in particular
    • SAE J1939 permission and SAE ITC collaboration
      • Question of where diagnostics should take place whether to map J1979 DTC to VSS or defer to ISO/ASAM SOVD
    • Sampling alternatives, client preferences and server (VISS) capabilities
    • Blocking issues for data campaign release: 7 alternative sampling, 9 naming convention, 4 representing calculations (defer for v1.x.x)

20 November 2024

    • CVIS - awaiting HD OEM
      • FMS to send Expert Group opinion on VISSv3 needs in December and next meet in January 
      • Intent to formalize relationship between ACEA and COVESA - MoU with scope of collaboration - action on Armin (FMS)
    • J1939 / VSS mapping
      • CSV format - full mapping with FMS J1939 but no direct references by Bosch, some gaps
      • Inquiry to Peter Winzell (Volvo cars) on his AI+heuristics mapping approach
      • SAE ITC meet and J1939 request
        • Intent to establish detailed collaboration between SAE ITC and COVESA CV EG before AMM (Berlin 12-15 May 2025)
        • ACEA unaware of licensing or other agreement w/ SAE to cite/use J1939
        • Inquiry to ATA TMC RP1230, can send to VDV, others?
        • Potentially don't need - fair use clause of copyright
    • Insurance update
      • HIM experiment/discussion
        • contrast with overlay for data campaigns
    • API support of protobuf - performance needs by ACEA/others
      • have to resolve in VSS and/or VISS calls - CV wants for FMS and RP1230 support in-vehicle (<10ms)
      • gRPC Kuksa to be open sourced

19 November 2024 - Insurance Signals

    • Adaptive Cruise Control and Lane Detection - advanced use cases based on driver interactions
    • SAE ADAS definition alignment

13 November 2024

    • FMS & J1939 
    • Track deliverables on main page of wiki
    • Consent update
        • ISO 20078 (Ext Veh and Neutral Server - blockchain based consent management) 
          • getting adoption in EU by OEMs and TSP (Caruso)
        • draft coming from Volvo Car, Wireless Car on EU Data Act based effort
        • marketplace charter coming from Endava
    • FMS Update 
      • Volvo Group and Daimler joint EU venture should rely on open standards (COVESA) and common middleware (Eclipse SDV)
      • COVESA/FMS collaboration formalizing further, discussion has been drawn out - request sharing slides in COVESA
        • HD OEM from ACEA to participate
        • Additional signaling as spelled out in CV charter, interest in Hierarchical Information Model (support additional data models - driver, trailer)
        • Some pieces already done
          • VISS API
          • J1939 to VSS mapping, rFMS covered, some gaps for FMS to be prioritized
      • in NA seeing similar with Cummins/Microsoft/ETAS led effort which also will work within SDV, COVESA and ATA TMC
    • Publishing pre-release data campaigns
      • Pending issues to clarify 1 licensing, 7 alternative sampling, 9 naming convention, 4 representing calculations 
      • CVIS tooling vs VSS Overlay - Ted and Ulf to experiment on representing data collection campaigns in November

16 October 2024

    • recap of 9 October call
    • Cancel next week's call, conflicts with ACEA FMS sync
    • Update on deliverables
      • review charter scope and activity
      • how to track - table on group page with status, stakeholder/driver
    • MS/Cummins Workshop debrief
      • SDV for trucks - increased awareness of COVESA in general and CV activity in particular
        • more southbound into the vehicle and SDV "core stack" proposal
      • Regular coordination - monthly cadence
      • Azure - DTDL/ontology for VSS and interest cloud ecosystem 
        • engage MS further, Stefan and Swen have interest/contacts
    • recap of 9 October call
    • Cancel next week's call, conflicts with ACEA FMS sync
    • Update on deliverables
      • review charter scope and activity
    • MS/Cummins Workshop debrief
    • Insurance to release basic data campaign by EOY
      • naming conventions for campaigns
      • promotion - blog, linkedin and outreach to group contacts
      • recruiting additional stakeholders
        • want others in fleet space, will do a pre-release of fleet campaign as well - hoping to 
      • increased interest in ADAS systems data from insurance sector - Stefan to share video of recent event

15 October 2024 - Insurance breakouts

...