In the race for Connected and Automated Vehicles (CAVs) deployment the number of software-based functions will continue to increase. Given the additional complexity of the systems and the number of testing scenarios involved, neither a classical nor a modern certification approach will be able to fully assess the safety of the automated / autonomous driving systems with a limited number of performance tests and requirements.
The future approach will therefore be based on extended process and functional safety oriented audits (e.g. including safety of the intended functionality) and on the use of virtual testing tools (software / hardware / driver in the loop) as a foundation for vast scenario coverage. Edge case scenarios, Human Machine Interface and the ability to cope with traffic will be validated through a set of track and real world driving tests.
Each Automated Vehicles Technical Working Group meeting shall facilitate discussion to advance the best interests of the members of SMMT in any area that affects vehicle automation, specifically to:
Traditional regulations on steering and braking, including Automatic Emergency Braking Systems (AEBS) and generically Advanced Driver Assistance Systems (ADAS); More advanced functions (e.g. “hands-off”) such as Automated Lane Keeping Systems (ALKS) and Remote Controlled Parking / Manoeuvring (RCP/M); New certification concept for Automated / Autonomous Vehicles (Multi-Pillar Approach), including functional requirements (e.g. system safety, object and event detection/recognition, HMI, operational design domain, …) and validation methods for AVs (Simulations, Virtual Testing, Track and Real World Testing); Data Collection and Retention for the purpose of Automated / Autonomous Driving (i.e. Data Storage Systems for Automated Driving (DSSAD)); Road Traffic Safety, where relevant for Automated / Autonomous Driving (i.e. traffic laws allowing the driver to undertake secondary activities than “driving”
