Task Force Data Analysis held an online meeting on 7 July 2026. The group discussed database analysis, including insufficient data for higher performance and acceleration, and agreed that more data are needed. When new data are generated, operation conditions should focus on higher performances covering the ASEP range, higher accelerations up to and exceeding 5 m/s, pass-by runs with gear shifting, and low speed measurements in the UN R117 AVAS control range. The group reviewed proposals to the TF-Editing based on draft UN R51.04 and agreed some changes, with review results to be uploaded as Rev.1. A question regarding the phrase “but no more than 2.0 m/s” in paragraph 3.1.2.1.4.3 regarding vehicles with only one gear ratio was noted as issue #23 pending further review.

This document proposes guidance on reporting cyber security issues affecting autonomous driving systems safety. The proposal modifies the description of reportable cyber security incidents to replace “Safety-relevant ECU compromised” with “Any cybersecurity threat identified to safety relevant ECU, or” and deletes “ADS control channel manipulated.” The text also clarifies that reporting must align with UN R155 where this Regulation is applied, replacing the reference to “CSMS procedure where R155 is applied.”

Proposal for guidance on reporting average feature engagement time in para. 4. The average engagement time is a statistical measure of how long an ADS feature stays engaged per activation (e.g., cumulative time / number of activations). The average is expected to be computed in an aggregated manner, i.e., over the whole fleet of vehicles having the same ADS feature.

Proposal to amend the guidance on reporting safety-relevant communication issues by deleting “Such an occurrence could be reported in case of” and replacing it with “Examples of communication issues could include”, deleting “The remote interaction is unavailable” and replacing it with “Interruption of remote interaction,”, replacing “Information” with “Communication”, adding “the” before “safety threshold”, and adding “(if indicated in the safety case)” after “safety threshold”, and replacing the period after “unavailable” with “, or”.

Proposal to add animals and children to examples of safety-relevant objects in para. 6.1.2.8. The revision inserts “Animals and children (in or adjacent to the roadway, under the vehicle carriage, etc)” into the illustrative and non-exhaustive list of safety-relevant objects. The proposal removes ambiguity for manufacturers developing safety cases and ensures consistent treatment across ADS requirements, making explicit that animals and children are safety-relevant objects even though they cannot be expected to respond predictably based on vehicle signals, traffic rules, or common conventions.

Proposal to add animals and other road users as examples of entities an ADS may encounter in driving situations and test scenarios. The revised text adds “animals, or other road users” to the illustrative example in para. 2.33 and para. 2.34, and replaces “pedestrians” with “these entities” in the corresponding sentence about scenario design. This ensures scenario design used to demonstrate ADS competency explicitly accounts for animal encounters alongside pedestrians and other road users.

EV Guard Oy manufactures battery guards for hybrid and electric vehicles using 3 mm marine aluminum and 8 mm recycled PET composite to protect battery packs, liquid-cooling systems, and electrical connectors. The guards distribute impact force, reduce temperature fluctuations, improve energy efficiency, and are 100% recyclable. The company supplies guards to authorized repair shops. No valid regulation currently applies to aftermarket battery shields; UN R100 does not cover this product, representing a structural gap in regulation.

Proposal to delete “the examples given below is not the only possible approach,” add clarification that examples are non-comprehensive and represent one possible approach for documenting claims, arguments and evidence, modify example descriptions to point to regulation requirements 5/7.3.3.2 (a) and (b), and incorporate examples from ADS-20-09 by removing the placeholder “Examples to be provided.”