How evolving ADAS/AD regulations are reshaping validation - and how aiMotive helps meet the challenge

News & insights

Check our latest stories on automated driving

Self-driving vehicle navigating an urban street as computer vision technology identifies pedestrians and nearby traffic in real time.

Written by Tibor Steve Simon / Posted at 9/10/26

How evolving ADAS/AD regulations are reshaping validation – and how aiMotive helps meet the challenge

Over the past few years, the regulatory landscape for advanced driver assistance systems (ADAS) and automated driving systems (ADS) has undergone substantial change. This evolution is not the result of a single new regulation but of a broader shift within the UN and EU frameworks, complemented by increasingly demanding consumer assessment programs.

Although these frameworks differ in legal status and scope, they are moving in the same direction: the process is increasingly expected to be supported by measurable, structured, and traceable evidence of how the system actually behaves.

UN regulations: an evolving framework 

At the UNECE level, several UN Regulations already provide binding type-approval requirements for ADAS and automated driving systems.

Let’s take a closer look at the four regulations most relevant to this series:

  • UN R171 — Driver Control Assistance Systems (DCAS): covers systems providing sustained lateral and longitudinal assistance while the driver remains responsible for supervision.  

  • UN R157 — Automated Lane Keeping Systems (ALKS): defines requirements for conditional automated systems designed to operate only under specific conditions. 

  • UN R152 — Advanced Emergency Braking Systems (AEBS): establishes type-approval requirements for automatic emergency braking functions.

  • UN Regulation on Automated Driving Systems (ADS): adopted by WP.29 ( World Forum for Harmonization of Vehicle Regulations) in June 2026, establishing a global UN regulatory framework for fully automated driving systems.  

 
The UN Global Technical Regulation on Automated Driving Systems (ADS GTR) was also adopted during the same WP.29 session. Instead of serving as a direct type-approval regulation, it provides a common international foundation for aligning ADS safety requirements and assessment methods. 
 
Together, these developments indicate that system requirements are increasingly evaluated through scenario-based and real-world testing, virtual simulation, and structured safety evidence.

EU regulation: a defined type-approval framework for ADS

In the European Union, Commission Implementing Regulation (EU) 2022/1426 sets out the process and technical standards for fully automated driving systems, helping ensure safety and consistency. The rules were recently updated by the Commission Implementing Regulation (EU) 2026/481, which introduces new provisions effective as of March 2026. 

The practical implication is equally important: manufacturers must demonstrate how their automated driving systems perform across their intended operating conditions, including foreseeable critical situations, and provide solid evidence to support the safety of their systems. 

Euro NCAP: setting a higher external benchmark

Euro NCAP is not legislation; however, its protocols significantly influence public expectations regarding vehicle and ADAS performance.

Its 2026 methodology clearly reflects the growing role of both real-world and virtual evidence. Speed Assistance Systems, for example, are assessed through extensive on-road testing using an independent multimodal sensing system to establish ground truth, while Euro NCAP has also introduced virtual-testing methodologies within its 2026 assessment framework.

This highlights two parallel trends: the growing importance of independent real-world reference data and the increasing role of validated simulation in external vehicle assessment.

The common thread: shifting toward evidence-based safety assurance

Although these frameworks differ, they share a similar approach and create similar validation challenges.

Following the required development process is no longer enough. Developers must also demonstrate how the system behaves under specific conditions and whether its performance meets the relevant expectations.

This demands the capability to measure parameters such as system reaction times, trajectories, distances, acceleration, lane positioning, and interactions with surrounding traffic, and to trace these results back to the underlying test conditions.

For automated driving systems, this extends further: relevant scenarios may also need to be reproduced, varied, and evaluated in simulation.  

From Challenge to Solution: How aiMotive Makes It Possible

Three connected capabilities drive aiMotive’s response to these challenges:

Rooftop Box - independent ground truth system

The Rooftop Box is an independent, multimodal measurement platform that records the surrounding environment and vehicle behavior, providing a reliable reference distinct from the system under test.

aiData  - turning recordings into structured evidence

aiData transforms recorded sensor data into structured, annotated data. Its metrics then convert these observations into quantitative evidence that supports analysis, reporting, and comparison across test runs or software versions.

aiSim - extending validation into the virtual world

aiSim extends the workflow into simulation, enabling repeatable scenario-based testing, systematic variation of conditions, sensor simulation, and scalable exploration of situations that may be too rare, unsafe, or impractical to cover exclusively on public roads.

Capabilities such as Neural Rendering further bridge the real and virtual domains by combining real-world visual realism with the controllability of simulation. As simulation takes on a greater role in validation, the ability to demonstrate the credibility, traceability and repeatability of virtual test results is becoming increasingly important.

Two validation domains, one evidence workflow

Real-world testing and simulation are most effective when they operate together. Rather than being treated as separate activities, they can serve as complementary elements of a single, integrated validation framework.


Instead of creating separate validation workflows for each regulation, OEMs can use a connected infrastructure across multiple ADAS and ADS frameworks. This enables them to collect independent real-world data, generate quantitative performance evidence, reproduce scenarios in simulation, expand test coverage, and support evidence-based safety and approval processes.

Different regulations. Shared validation challenges. One connected workflow for building evidence.

In the upcoming parts of this series, we will follow this chain step by step: from independent real-world measurement and annotation, through quantitative metrics and reporting, followed by scenario-based virtual testing, sensor validation, and Neural Rendering with aiSim.