Driver Workload Guidelines applied to MirrorLink™ Mobile Applications Dr. Matthias Henning HMI...
Preview:
Citation preview
- Slide 1
- Driver Workload Guidelines applied to MirrorLink Mobile
Applications Dr. Matthias Henning HMI Specialist, Carmeq -
Volkswagen Group Driver Distraction Task Group, CCC
- Slide 2
- Overview 1.Driver Distraction Guidelines 2.DD Guidelines and
MirrorLink 3.MirrorLink Developer Requirements
- Slide 3
- Phone Applications in the Car Phone applications are not
designed for use in cars!
- Slide 4
- Phone World vs. Car World Driver Distraction Guidelines Car
ModePhone Mode
- Slide 5
- Driver Distraction Guidelines The early days
- Slide 6
- Driver Distraction Certification Existing Regional Guidelines
Workshop Driver Distraction Guidelines, V01.0 6
- Slide 7
- DD Guidelines and MirrorLink
- Slide 8
- 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 DD Guidelines and MirrorLink
Challenges
- Slide 9
- Drive-Certified Application Requirements Compilation of
Regional Guidelines EU Apply ESoP
- Slide 10
- Drive-Certified Application Requirements Compilation of
Regional Guidelines EU & NA Combine AAM and ESoP
- Slide 11
- Drive-Certified Application Requirements Compilation of
Regional Guidelines Global Global Guidelines
- Slide 12
- Head Unit 1.Installation Principles Head unit installation
2.Information Presentation Principles e.g., workload, font size,
contrast 3.Principles on Interactions with Displays/Controls e.g.,
chunkibility, pace of interaction 4.System Behavior Principles
e.g., no video, lock of functions 5.Principles on Information About
the System documentation Divided/Shared Responsibility Example AAM
Guidelines Smartphone Application
- Slide 13
- MirrorLink Developer Requirements
- Slide 14
- 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 Cookbook
for Developers to pass Drive-Cert Testing 14
- Slide 15
- Guiding Principals Nothing that demands the drivers 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 Minimizing Driver
Distraction
- Slide 16
- 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
- Slide 17
- 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 MirrorLink Developer Requirements Measuring Driver
Distraction
- Slide 18
- 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 Conclusion DD
Guidelines and MirrorLink
- Slide 19
- THANK YOU