Page History

...

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

• • Data Marketplace POC demo (Swen) https://app.covesa.acc.am-isd.com/login (try it out and provide feedback)

15 April 2025

• • VSS meta data extensions
    • sampling: and other related metadata can be overloaded, different meaning depending on situtational understanding
      • On-board API reporting data broker broadcast capabilities, useful for third party apps running on-board (encryption: authentication: access_control:) and API
      • Prescriptive in how it wants data collected cf https://github.com/COVESA/commercial-vehicles/blob/main/tmp/convert-spreadsheet/insurance-output.yaml
      • Descriptive in how the data was collected
    • 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:
        • sampling_rate: "100 ms" (need more than just frequency, event, conditional and calculation. may have fallback preferences in collection request - issue 7)
        • retention_policy: "30 days"
        • data_privacy: "anonymized" (defined constants, aggregate, sensitive, consent - would need more details)
      • 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

...