Antitrust statement

Meeting Minutes

17 July 2024

• • Insurance signals
    • Use cases, calculations and sampling guidelines
    • Allianz and Moter alignment
    • Existing efforts we should seek coordination with? eg OPIN
  • Expert Group launch/Workshop agenda

10 July 2024

• • Recap of last week
  • Stefan's issue and signals
    • Reviewing individually offline
    • Going to VSS call in coming weeks
  • Update on Curve logging in Eclipse SDV Fleet Blueprint demo - data PR merged and demo works
    • Discussion on necessity of time series and absence of a timestamp in VSS
    • Time more a function of API or data-broker - when is the data collected, broadcast, event based?
      • Important to clarify for data collection campaigns - which are we talking about?  
  • COVESA Board decision on Expert Group proposal expected later today, potentially a new co-chair from Ford
  • Expert Group kickoff/Workshop planning see main page 
  • Summer slowdown - plan on 7 and 14 August off

3 July 2024

• • Insurtech use case
  • Moter to propose initial set of signals for data collection campaign 

26 June 2024

• • Update on CV Expert Group proposal to COVESA Board
    • Scope, additional signaling in break out group, additional verticals (EV and Insurance)
    • OEMs interested, Ford willing to co-lead
      • Challenges and hesitation from OEM to enable
        • EU Data Access Act will require OEM to provide data to third parties at owner direction 
      • Need for consent management/opt-in, privacy 
      • Potential elation to AOSP group - UX for capturing consent, push notifications for insurance/fleet driver coaching, remote routing suggestions for fleet. Data collection more likely to take place in TCU or be done by OEM and made available to third parties in the cloud
    • Plan is to continue work as incubator group and work on marketing, materials to hold a kick-off workshop in early September before AMM
  • Insurance data campaign coming together and to be made available at future CV call
  • Diagrams for information architectures to support a more robust ecosystem will be on a subsequent call as well
    • We have previously explored consent and privacy in CV BoF, should incubate and ensure alignment before forming a separate Expert Group for it and other ecosystem topics

19 June 2024

• • data exchange environment proposal
  • COVESA Board reaction to Expert Group proposal
  • Firming up insurtech interest

12 June 2024

• • Expert Group proposal 

29 May 2024

• • Event definitions discussion in VSS
  • Charter draft advancing, will circulate soon for input
  • Workshop, other ideas on promoting Expert Group after Board approves
  • Commercial and Fleet Vehicle Expert Group (working name, still open to input. have some more marketing minds on Board) 

22 May 2024

• • Charter outreach - confirming participation intent for scoped items
    • (OEM, insurance) - suggestions
  • Input on group name given scope and previous confusion\
    • Fleet, Commercial and [Insurance] Expert Group
  • Volvo car playing with curve - Bosch's demo from AMM being redone and recorded
  • Insuretech alignment on VSS marketplace vertical (Fleet, EV and Insurance) (MOTER and possibly Allianz)
    • Reviewing FMDG for overlap, will work on insurance data sampling campaign (basic and advanced)
  • Commercial Vehicle Information Specifications (HIM and VSS overlay) - separate task force under Expert Group

15 May 2024

• • Scope discussion
  • https://github.com/COVESA/commercial-vehicles/issues
    
    • YAML overlay for a sampling campaign
    • attributes, tooling and sampling convetions
    • DTC need in VSS with OBDII branch deprecation

8 May 2024

• • AMM debrief
  • AOB
  • Charter Scope
    • Upgrade from BoF to Expert Group 
    • Common Data Sampling Campaigns
      • Fleet Management Data Guidelines (VSS marketplace)
      • EV Range Prediction (Ford, Geotab)
      • Insurance (MOTER)
      • Other?
      • Organize and align signals lists for specific campaigns
    • In-Vehicle API (VISS)
      • ACEA FMS (Bosch) 
      • ATA TMC RP1226 (Bosch, Morey)
    • Additional  / Hierarchical Information Models (Ulf HIM) 
      • DTC and fault codes
      • Control Unit firmwares' version numbers
      • Trailer (Great Dane, Volvo Group)
      • Tractor to trailer interface (wired, WLAN, other)
      • Upfitting (refrigeration, salt spreader, plow, sirens) - (Ford, Bosch)
      • HD truck/bus not adequately represented already in VSS
      • Driver Profile*? (limit scope, coord w/ AOSP, CVI, other)
        • IETF GNAP 

April 2024

• • Link to AMM CV track agenda/slides

19 February 2024

• • EV range prediction/correction factor campaign, see Github issue 12

12 February 2024

• • HAL4SDV - EU projects
  • Eclipse SDV example towards SDV Alliance as a demonstrator
  • 3 potential projects worth open sourcing regardless of whether accepted in this program
    • Cloud2cloud - create a test server w/ VSS, CV guidelines on data points - cloud platform agnostic
    • in-vehicle edge
    • v2c serialization (see PR from Adnan, transmission
  • Endorsements now on the landing page, encourage participants to provide ones as well
  • Use case[s] for limited PoC
  • Group vitality, wide variation in attendees from week to week
  • A few OEMs have wandered in and out, one willing to pilot with Geotab but not part of COVESA and don't think they want to be out in the open
  • How to improve outreach?
  • Need to put the different aspects of CV activity on the table and see which people want to work on building out more
  • Schedule discussions with appropriate people from Stellantis, GM and Ford

5 February 2024

• • Endava introductions, engineering company
  • Endorsements for landing page
  • AMM PoC and Tech track
    • 3-5:30 on 17th and can spill over onto Thursday
      • include working session
    • mapping from RP1226, already done for rFMS. 
  • Use case for PoC
    • Looking for input from Wally on use case and availability of data from TMC fleet
  • Feedback on Business case to sell OEM

18 & 25 January 2024

• • RP1226, aligning other efforts

4 December, 2023

• • FMS - goals:
    • Agreement to use VSS in the cloud, leverage existing mapping for translation
    • Follow CV BoF recommendations - what signals are collected and how they are sampled
      • What is missing in current FMS? OEM only focus of FMS - lacks perspective of fleet customers' data needs
      • What are we missing in CV BoF recommendations? - likely takeaway - ongoing coordination on signals/sampling
    • EU regulator influence on data access - saw article @link? about passenger vehicle OEMs considering FMS
    • FMS has transport protocol but not focused on data being sent - unsure if passenger car OEM will coordinate on this level as much as EU HD OEM
    • ISO 21434 Neutral Server/Extended Vehicle - has a transport but not a common data model - any relation with FMS?
  • SDV Hackathon on Fleet Management
    • various things connected to LinkedIn, common hashtag #
    • work done in a private github repo - avoid legal issues
    •  6-7 challenges, Rust eco-system, effort to combine different container solutions** - at least 3 different ways to handle containers currently in SDV
      • Elektrobit container management
      • RedHat System D approach  
      • 4 teams chose fleet management challenge
        • created a dashboard, MQTT in the background to inject data into the system
        • group looking at profiles - more useful for rental vehicles (relate to ELD in NA?)
        • sourcing data for testing
        • group wanted to perform analytics and extended range of signals being collected by FMS forwarded - unsure what they added
        • Fleet Management Blueprint setup was straight forward, allowing developers to start using/adding onto it instead of wasting time
    • Configuration for sampling campaigns - Node Red was used for rapid prototyping
      • was too large a topic to solve in a short hackathon
      • emphasis was to understand FMS forwarder (Rust component of SDV Fleet Blueprint) and extend it

27 November, 2023

• • Preview landing page
    • VSS needs to be emphasized more up front
    • Requesting review, promotion and endorsements
  • Fleet Management Systems (FMS)
    • EU HD truck and bus telematics standards - OEM only group*
    • Uses J1939 (rFMS/J1939 mapped to VSS)
    • Technical deep dive set for 14 December, 2023 (2h), FMS leadership and reps from the 6 HD OEM
    • Commercial Fleets are a mix of different classes of vehicles, rest of which do not use J1939
    • Goal is to convince them on the importance of higher level abstraction
    • Prove VSS abstraction can be moved to vehicle edge
    • Questions raised by FMS:

      How would FMS Standard look like in a COVESA API? (AutoSAR collab update on Thursday, also Bosch CV Blueprint - Eclipse SDV)

      What are your plans to extend the COVESA VSS with commercial vehicle data? (HD specific branches can be added to VSS, much already there. VSS accepts contributions, want HD OEM SME to provide)

      What is the status of development of the COVESA vehicle API? (update from AutoSAR)

      Do you have a demo available? (yes, Bosch to present)

    • What to present/demo and which goals to emphasize?
      • Like FMS group to participate in CV to advance guidelines or at least some of their member companies
      • Tech demo ready
      • Higher level pitch based on what we've used - shorter version of AMM presentation (15 min max) ACTION ITEM: Ted to condense deck and share with Thomas by email, group on next call
        • Anchor on VSS, including mapping 
        • provide links for follow up, wiki with its slide decks and recordings, landing page and github
        • YAML of sampling campaign overlay
  • Revisit top issues introduced last week

20 November, 2023

...

13 November, 2023

• • Sampling conventions

...