Intelligent & Digital Roadway Infrastructure for Vehicles Integrated with Next-Gen Technologies

In September 2025, Work Package 6 (WP6) advanced the part of iDriving that turns “great tech” into validated, usable, real-world impact: the evaluation methodology, the preparation of pilot trials, and the user training approach that will help stakeholders make the most of the platform. WP6 is structured around these three pillars—evaluation methodology, pilot trial implementation, and user training programmes—and is progressing according to plan.

A multi-level evaluation framework: tools, platform, and impact

A key WP6 achievement up to September has been the consolidation of an evaluation framework that looks at iDriving from three complementary angles: technical evaluation of the tools, technical evaluation of the platform, and evaluation of expected impacts. This multi-level structure is designed to ensure iDriving is assessed not only as a set of components, but as an integrated system with measurable effects.

To make evaluation consistent across pilots, WP6 partners agreed on core performance categories for platform and tool assessment – latency, reliability, accuracy, and efficiency – and began converting data sources into KPI definitions that can be applied across all Pilot Use Cases.

KPIs refined during the 2nd Plenary Meeting in Paris

During the 2nd Plenary Meeting in Paris (22–23 September 2025), WP6 ran focused internal work to review and converge on KPI definitions for technical evaluation, ensuring they match both operational needs and the evolving system architecture.

For platform validation specifically, WP6 developed an initial set of KPIs addressing key aspects such as availability, latency, service reliability, and processing, and formalised how these KPIs will be tested (test purpose, expected results, procedures, verification criteria, and logging formats) to ensure consistent data collection across trials.

First pilot trials prepared: Graz and Nevers (Use Case 1)

In parallel with methodology work, WP6 progressed preparations for the first two pilot trials, both linked to Use Case 1 (improving compliance with traffic regulations and enhancing road user safety):

Up to September 2025, planning for both trials was already underway, and a first successful rehearsal had been executed in Nevers, helping the consortium test readiness and integration steps ahead of the planned on-site deployments.

On the Nevers side, trial preparation included identifying and preparing camera locations, installing traffic sensors for baseline and real-time inputs, commissioning required hardware, and collecting historical data (e.g., vehicle counts and traffic signal operations) from the local authority to support calibration and evaluation.

WP6 also supported early baseline work for evaluation in Graz by collecting relevant data sources to underpin KPI definition and “before/after” comparisons (including traffic flow data, signal data, and records related to accidents and traffic violations).

Training approach: embedded guidance plus practical resources

WP6 also progressed the user training concept so that training strengthens pilots rather than slowing them down. As of September 2025, training materials aligned with the first version of the iDriving application were being prepared for upcoming user sessions.

A key decision is that user training will be integrated into the applications themselves, providing embedded guidance either at first use or on demand. In parallel, WP6 is preparing additional resources -such as user manuals and short instructional video clips – to ensure consistent, accessible support for different user groups. Training and engagement are designed to take place alongside the pilots, on-site, directly supporting platform validation and user readiness.

Looking ahead from September 2025

As of September 2025, WP6 reported no major deviations and confirmed that the first pilot trials were scheduled for February 2026 (M20) for both Graz and Nevers, with additional trials planned later in the project lifecycle.