Insurance relevant Parameters

[StefanSellschopp]

09072024_Covesa_Allianz_UseCasesADAS_Risk_LiabilityData_Table_V8.xlsx

the first tab describes relevant data points (AggregationDataPoints), (the tabs on the right describes specific situations and can be ignored) the first ones include the VSS parameters I could find in VSS4.2 - any additions? the lower ones are missing from my perspectives - any thoughts?

[SebastianSchildt]

The attached xls has more, but for convencience and a quick glance:

[SebastianSchildt]

So there is acceleration in Vehicle:

Acceleration:
  type: branch
  description: Spatial acceleration. Axis definitions according to ISO 8855.

Acceleration.Longitudinal:
  datatype: float
  type: sensor
  unit: m/s^2
  description: Vehicle acceleration in X (longitudinal acceleration).

Acceleration.Lateral:
  datatype: float
  type: sensor
  unit: m/s^2
  description: Vehicle acceleration in Y (lateral acceleration).

Acceleration.Vertical:
  datatype: float
  type: sensor
  unit: m/s^2
  description: Vehicle acceleration in Z (vertical acceleration).

Same for gyroscope:

#
# Spatial Rotation
#
AngularVelocity:
  type: branch
  description: Spatial rotation. Axis definitions according to ISO 8855.

AngularVelocity.Roll:
  datatype: float
  type: sensor
  unit: degrees/s
  description: Vehicle rotation rate along X (longitudinal).

AngularVelocity.Pitch:
  datatype: float
  type: sensor
  unit: degrees/s
  description: Vehicle rotation rate along Y (lateral).

AngularVelocity.Yaw:
  datatype: float
  type: sensor
  unit: degrees/s
  description: Vehicle rotation rate along Z (vertical).

Basically insurance side there would needed to be the added "non-functional requirement" for a system to provide this in the desired frequency and range

Dashcam data: In VSS we would not "model" video data (as a datatype/stream), but certeinly the existence of a dashcam and a "location" to the ringbuffer may be modelled, see i.e. https://covesa.github.io/vehicle_signal_specification/rule_set/data_entry/data_types/#data-streams

Pedestrian Protection:Does this mean some form of pedestrian protection has been deployed, like an airbag? (or this kind of "reactive armor" kind of hoods?), or does this mean existence of some system?

descent/ascent: What is meant here? Whether the vehicle is on a slope?

[SebastianSchildt]

And Outside AirTemperature is

Vehicle.Exterior

AirTemperature:
  datatype: float
  type: sensor
  unit: celsius
  description: Air temperature outside the vehicle.

[tguild]

@StefanSellschopp for easier iterating the spreadsheet, I converted to a Google Sheet as discussed. I've made you, @SebastianSchildt and myself initial editors, expand as appropriate.

https://docs.google.com/spreadsheets/d/1gnaP8dUER4uOlgC9htJssW9rRdg0D_FA/edit?gid=1736927769#gid=1736927769

[StefanSellschopp]

pedestrian protection means the sensor and upward movement of the hood, in case of a pedestrian accident. ascent/decent: is a vehicle moving upwards or downwards

[erikbosch]

MoM:

• Prioritize this topic for next meeting.
• Please review

[StefanSellschopp]

I would suggest to add crash related parameters in one PR vehicle.body.rollover datatype: boolean type: sensor (?) description: vehicle detects roll-over event - TRUE trigger

vehicle.body.pedestrianDetection datatype: boolean type: sensor (?) description: vehicle detects an impact with a pedestrian, the hood is pushed upwards - TRUE trigger

[erikbosch]

@StefanSellschopp - as discussed in the meeting I added a small tutorial for creating a Pull Request at https://github.com/COVESA/vehicle_signal_specification/wiki/Creating-a-VSS-Pull-Request.

I used your signals above as example, visible in (my fork internal) PR https://github.com/erikbosch/vehicle_signal_specification/pull/16. Feel free to experiment with creating a PR yourself.

When the PR is created I see two things that may need to be discussed

• Where to put the new signals. Not obvious as I see it.
• Define detailed semantics, like when shall they be true, when shall they be reset to false.

[StefanSellschopp]

Internal

Thanks, I will give it a try…

From: Erik Jaegervall (Jägervall) @.> Sent: Wednesday, August 7, 2024 9:48 AM To: COVESA/vehicle_signal_specification @.> Cc: Sellschopp, Stefan (Allianz Partners) @.>; Mention @.> Subject: [EXT] Re: [COVESA/vehicle_signal_specification] Insurance relevant Parameters (Issue #754)

@StefanSellschopphttps://github.com/StefanSellschopp - as discussed in the meeting I added a small tutorial for creating a Pull Request at https://github.com/COVESA/vehicle_signal_specification/wiki/Creating-a-VSS-Pull-Request.

I used your signals above as example, visible in (my fork internal) PR erikbosch#16https://github.com/erikbosch/vehicle_signal_specification/pull/16. Feel free to experiment with creating a PR yourself.

When the PR is created I see two things that may need to be discussed

• Where to put the new signals. Not obvious as I see it.
• Define detailed semantics, like when shall they be true, when shall they be reset to false.

— Reply to this email directly, view it on GitHubhttps://github.com/COVESA/vehicle_signal_specification/issues/754#issuecomment-2272838438, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BJYGIWAKLPIR6YVQMJYA43TZQHGMPAVCNFSM6AAAAABKTDQZQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZSHAZTQNBTHA. You are receiving this because you were mentioned.Message ID: @.**@.>>

[StefanSellschopp]

@erikbosch i did try to do a fork. Then tried to copy your changes. my file ending does not say .vspec - how do I create this? also I was not able to create a "folder" to include another vspec file on CrashNearCrash. I manually copied the header lines and then added some parameters. I think we should move the CrashManagement parameters here as well. Also added slope in the "chassis" file not sure if this correct.

[StefanSellschopp]

@SebastianSchildt : any ideas on how to proceed on this? what do i need to change? eg. https://github.com/StefanSellschopp/vehicle_signal_specification/blob/master/spec/Crash_NearCrash

[tguild]

@StefanSellschopp I can go over with you in a call with a shared screen if you want - we can also discuss this specific proposed set of signals in one of our regular breakout calls with MOTER

[StefanSellschopp]

we can discuss in our regular calls, no problem. Perhaps you have a suggestion?