A Event Data Recorder (EDR) is used for accident analysis purpose (UNECE R160 (LDV) and R169 (HDV). For Automated Lane Keeping Systems (ALKS) additionally a Data Storage Systems for Automated Driving (DSSAD) is defined to record data on mainly who’s in charge of performing the (Dynamic Driving Task) DDT at which time (the ADF or the human driver) (UNECE R157).
Only relevant data should be saved. Data must be stored for a certain period of time. Data retention and storage requirements for EDR and DSSAD are subject to national legislation.
Main Question
Is it clearly defined what kind of data needs to be stored how long for EDR and DSSAD purpose?
Sub-Questions
- Is it clearly defined for the target ADF which internal and external vehicle signals—along with their resolution, format, and recording frequency—must be captured, as required by the EDR and DSSAD regulations?
- Are data retention and storage requirements fullfield?
- Is it necessary, for any reason, to make sure that data/information is also stored outside the vehicle?
- Are there mechanisms included in the design that collect safety-relevant data, which will be needed for documentation purposes (e.g. required by law or for certification) and for field monitoring?
References
- UN Regulation No. 157 – Automated Lane Keeping Systems (ALKS). Available at: https://unece.org/transport/documents/2021/03/standards/un-regulation-no-157-automated-lane-keeping-systems-alks (Accessed: 12 February 2024)
- UN Regulation No. 160 – Event Data Recorder (EDR). Available at: https://unece.org/transport/documents/2021/10/standards/un-regulation-no-160-event-data-recorder-edr (Accessed: 09 December 2025)
- UN Regulation No. 169. Available at: https://unece.org/transport/documents/2024/10/standards/un-regulation-no-169 (Accessed: 09 December 2025)