Page 1 of 1

Side impact: near side vs. far side

Posted: Tue Aug 20, 2024 6:28 pm
by tdeland
I'm working on rolling out ISO codes to our lab and am looking for input on how to transition our existing conventions. Currently, our side impact team uses channel identifiers like near side and far side. The benefit being the channels stay the same whether the impact is to the left or right side of the car. However, TS13499 clearly outlines locations using the position character which are at odds with our existing convention (e.g. 11SILB... would be near side for a LH hit but far side for a RH hit).

I think the most "appropriate" way is to reference the impacted side of the vehicle from the metadata then use that to determine whether a channel is near- or far-side based on the position code. Another is to treat the channels for every side test as though it were a LH impact (i.e. 1 = front near side, 3 = front far side, 4 = rear near side, etc.).

I welcome any feedback or suggestions from the group on how they've handled this issue. Many thanks in advance!

-Trevor

Re: Side impact: near side vs. far side

Posted: Tue Aug 20, 2024 9:00 pm
by DiVe
Dear Trevor,

we do it the same way in our analysis software.
We combine the impact side information of the test object with the "seating position" (vehicle zone):
Impact side LE -> SP 1 and 4 (and 7,...) are Near side; SP 3 and 6 (and 9,...) are Far Side
Impact Side RI -> SP 3 and 6 (and 9,...) are Near Side; SP 1 and 4 (and 7,...) are Far Side

Internally we use the following identifier to formulate specific references or variable names:
FarSide-NearSide.png
FarSide-NearSide.png (84.69 KiB) Viewed 54 times
We have a similar approach for frontal impact to have identifier that are independent from the
left hand/right hand steering.

Kind regards,
Dirk