Coding for relative velocity, displacement (IIHS Rear 2025-12)
Posted: Fri Mar 13, 2026 12:48 pm
Dear all.
in the IIHS Rear impact protocol dated 2025-12 there will be new criteria introduced.
If these channels are visualized, stored or exchanged there will be a need for an ISO coding.
Also if the result values could then be stored in a CVC (Calculated Value Channel; see RED E).
There is a request and proposal from Björn for discussion in the next meeting (2026.03.):
Pelvis Displacement
PELV0000BRDSX
OCCUUPLOBRVER
two Main Locations involved. Like:
HEPE for Head-to-Pelvis
PESL or PESD for Pelvis-to-Sled
Still, this will not solve the resultant just from x,z for the coding.
Kind regards,
Dirk
in the IIHS Rear impact protocol dated 2025-12 there will be new criteria introduced.
- Pelvis Displacement (relative to sled) X
- Head-to-pelvis relative velocity (resultant from x,z)
If these channels are visualized, stored or exchanged there will be a need for an ISO coding.
Also if the result values could then be stored in a CVC (Calculated Value Channel; see RED E).
There is a request and proposal from Björn for discussion in the next meeting (2026.03.):
Pelvis Displacement
PELV0000BRDSX
- + build from existing code parts
- - relativ information is missing
OCCUUPLOBRVER
- + build from existing code parts
- - concrete measurements are not referenced
- - x,z resultant is not expressed in the code
two Main Locations involved. Like:
HEPE for Head-to-Pelvis
PESL or PESD for Pelvis-to-Sled
Still, this will not solve the resultant just from x,z for the coding.
Kind regards,
Dirk