Antitrust statement

Meeting Minutes

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
  • 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

...