...

Meeting Minutes

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

...