Ensuring safety over the complete vehicle lifecycle

Vehicles are rapidly evolving into software-defined, sensor-rich systems capable of highly automated driving. But once these vehicles are deployed on public roads, a fundamental question remains unresolved: who is responsible for monitoring their safety over time - and how?

The challenge

Modern vehicles continuously sense, plan, and act through complex combinations of software, sensors, and algorithms. Over their lifetime, they are exposed to wear and tear, software updates (including over-the-air updates), regulatory changes, and shifting usage conditions.

Despite these dynamics, frameworks for assessing the in-use safety of Advanced Driver Assistance Systems (ADAS) and Automated Driving Systems (ADS) remain underdeveloped. Existing approaches are largely conceptual and not yet operational.

This creates a clear gap: safety assessment is still mostly static, while vehicle systems are anything but.

Addressing this requires a shift towards continuous, data-driven monitoring and reporting. This direction is already reflected in emerging regulatory developments, such as UNECE proposals on new assessment methods and global technical regulations for automated driving systems.

What WP4 is building

Within the CERTAIN project, Work Package 4 (WP4) is translating this shift into practice.

WP4 develops a methodology for continuous safety validation, enabling the monitoring and reporting of safety performance throughout the entire lifecycle of CCAM systems.

At its core is the development of an In-Service Monitoring and Reporting (ISMR) system. This system is designed to continuously track system performance after deployment and support ongoing safety assurance under real-world conditions.

Building on a solid foundation

The work in WP4 builds on earlier project activities. In particular, WP1 (Task 1.1) identified and validated end-user needs across stakeholder groups, including OEMs and type approval authorities. These insights were translated into Functional System Requirements (FSR), which define what an effective ISMR system must deliver.

WP4 also builds on previous EU-funded projects such as HEADSTART, V4SAFETY, SUNRISE, SYNERGIES, and SET Level, ensuring alignment with the current state of the art.

From periodic inspection to continuous assessment

Today, vehicle safety in the EU relies heavily on Periodic Technical Inspections (PTI). While these inspections are mandatory, they are not designed to assess the functional performance of increasingly complex ADAS and ADS technologies.

The ISMR framework - developed in WP4 - addresses this limitation. It outlines a future approach in which safety assessment moves beyond periodic checks towards a continuously informed process based on real-world operational data.

What’s next

The foundations are now in place, and the first results are emerging. WP4 is currently preparing its first milestone: a draft report defining ISMR functional requirements and specifications, alongside a proposed governance framework and initial concepts for future PTI integration.

More updates will follow as the work progresses.