Antitrust statement

Meeting Minutes

11 February 2025

• • Co-Chairing: welcome Mouham (Bosch), others interested? 
  • AMM CV track - including tying to EU Data Act project, AOSP data workstream
    • Business Track (main stage)
      • Insurance and fleet presentations or panel?
      • Big picture/ecosystem
    • Technical track (breakout rooms)
      • Insurance and fleet data campaign presentation and solicit input/discussion
      •  
  • Insurance campaign YAML produced, needs polishing
    • VHAL
  • 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
    • Min/max, 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
    • mathematical expressions in VSPEC YAML
    • https://github.com/COVESA/vss-tools/issues/436
  • 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)

...