4 December 2024
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
3 December 2024 - insurance signals
Review of SAE ADAS descriptors and capabilities, compare to insurance signals
Ensure VSS captures both warning (singular or levels) and intervention within same or adjacent signals (review required of VSS)
Insurance interest in video should be shaped and shared with VSS EG as COVESA intends to address need for video and other data streams
27 November 2024
20 November 2024
19 November 2024 - Insurance Signals
13 November 2024
16 October 2024
15 October 2024 - Insurance breakouts
Otonomo, Samsara, Caruso, Wejo, High-Mobility
2 October 2024
1 October 2024 - Insurance breakout call
Ted to prepare the PR
11 September 2024
4 September 2024
28 August 2024
21 August 2024
31 July 2024
24 July 2024
17 July 2024
10 July 2024
3 July 2024
26 June 2024
19 June 2024
12 June 2024
29 May 2024
22 May 2024
15 May 2024
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)
Reaction to previously presented conventions, introduced
How to handle alternate sampling conventions
Tooling & .csv converter topic
- no comments or offers for support so we continue here between geotab and etas
FMS-update
- Carlton explained again the background of why J1939 is a good std to abstract into our guidelines using the VSS data model
- potentially missusing overlays or need another DEG discusion required
- explained about the wishes from the fMS standards group that SAE J1939 causes them issues/cost due to being so closely copupled to CAN and HW
> (melissa request) Create an overview of what data is actually relavent for each additional field we are proposing for VSS overlay
> do we define our own DSL (data sampling Language) for measuring the data or do we want to change VSS
-currently DEG (data expert group) is discussing this topic and thinking that they need to have a way to managed this for specific vehicles
J1939 questions
- Some OEMs even considering replacing CAN with IP in the future
how do we get VSS to become protocol agnostic
- Melissa asked if we want to do something with the data >
- How do we do "plug and play" HW > can the CV BoF be a place that we also focus on this aspect of CV upfitting etc
- Suppliers & Tiers will need to focus on the lower level abstraction (ford opinion)
Cummins focus:
- Cummins to support for the FMS topic > we really need to focus on the fleet beenfits aspect
UNECE1516 direction = Operations: Warranties status & SW updates for all makes/models/components could be highly beneficial
- Should there be some sort of standard defiend in the control layer for updates etc in COVESA