Driver Workload Guidelines applied to MirrorLink™ Mobile Applications Dr. Matthias Henning HMI Specialist, Carmeq - Volkswagen Group Driver Distraction Task Group, CCC

Overview Driver Distraction Guidelines DD Guidelines and MirrorLink™ MirrorLink™ Developer Requirements

Phone Applications in the Car Phone applications are not designed for use in cars!

Phone World vs. Car World Phone Mode Car Mode Driver Distraction Guidelines

Driver Distraction Guidelines The early days …

Driver Distraction Certification Existing Regional Guidelines Workshop Driver Distraction Guidelines, V01.0

DD Guidelines and MirrorLink™

DD Guidelines and MirrorLink™ Challenges Different driver distraction guidelines for different regions Guidelines are designed for a complete system vs. MirrorLink™ ecosystem consists of different entities Technical Requirements vs. Driver Distraction Guidelines

Drive-Certified Application Requirements Compilation of Regional Guidelines – EU Apply ESoP

Drive-Certified Application Requirements Compilation of Regional Guidelines – EU & NA Combine AAM and ESoP

Drive-Certified Application Requirements Compilation of Regional Guidelines – Global Global Guidelines

Divided/Shared Responsibility Example AAM Guidelines Installation Principles Head unit installation Information Presentation Principles e.g., workload, font size, contrast Principles on Interactions with Displays/Controls e.g., chunkibility, pace of interaction System Behavior Principles e.g., no video, lock of functions Principles on Information About the System documentation Head Unit Smartphone Application

MirrorLink™ Developer Requirements

MirrorLink™ Developer Requirements “Cookbook” for Developers to pass Drive-Cert Testing Restricted Content Excerpt: “Video-based entertainment SHALL NOT be used. Notable examples are streaming applications, …” User Interface Accessibility and Responsiveness Excerpt: “The foreground and background of an application SHALL have a Brightness Difference equal to or greater than NN.” Driver Workload Excerpt: “One of the following criteria will be used to verify that an application does not exceed critical driver workload thresholds: Occlusion Method …” Golden Rules for minimizing driver workload Excerpt: “Limit visual and auditory list length”

MirrorLink™ Developer Requirements Minimizing Driver Distraction Guiding Principals Nothing that demands the driver’s attention Quickly comprehendible and accessible Restricted Content No video, incidental animations or flashing No automatic scrolling text Visual Accessibility Color contrast – brightness & color differences Text legibility (Minimum height, Font requirements) Manual Accessibility No two-handed operations Control sizing and spacing

MirrorLink™ Developer Requirements Measuring Driver Distraction Only NA and Japan Occlusion Testing Bench testing with a pool (~24) of users 50% male, 50% female 45-65 years of age 1 hour training Special goggles that switch from transparent (1.5 seconds) to opaque (1 second) Must be able to perform a task with a total open time of less than 15 seconds for 85% of testers

MirrorLink™ Developer Requirements Measuring Driver Distraction Only NA Additional Test Methods Pending Eye tracking simulation testing Driver performance simulation testing Only 1 method will be required – app developers will be able to choose their preferred method

Conclusion – DD Guidelines and MirrorLink™ The MirrorLink™ Developer Requirements: cover the most relevant criteria for the driver workload use a common format for all regions give additional hints for a good HMI are ready to be published  The developer requirements support developing of applications that can be used while driving

Thank You