Considering the needs of older adults when developing Human-Machine Interfaces for Connected Autonomous Vehicles (CAVs)

Transcription

1 Considering the needs of older adults when developing Human-Machine Interfaces for Connected Autonomous Vehicles (CAVs) Keir Haines, Designability Road Safety Trust - Funded Projects Seminar Thursday 17 th May 2018

2 ? CAV? Connected Autonomous Vehicle??

3 Car to CAV network connected self-driving sensors autonomous vehicle

4 ? HMI Human Machine Interface???

5 Dashboard to HMI

6 What is Flourish? Developing services and capabilities that support the safe, secure and user focused deployment of connected and autonomous vehicles. User Approach ensures that all elements of CAV deployment from the user to the vehicle and city level, are considered. Develop end-to-end CAV solutions that are accepted by users. Vehicle City

7 What is Flourish? Developing services and capabilities that support the safe, secure and user focused deployment of connected and autonomous vehicles. Approach ensures that all elements of CAV deployment from the user to the vehicle and city level, are considered. Develop end-to-end CAV solutions that are accepted by users. Vehicle User City

8 Impact and opportunity safety mobility quality of life independence participate

9 FLOURISH Consortium Partners 9

10

11 11

12 user engagement 12

13 user engagement interface design 13

14 user engagement interface design design evaluation 14

15 user engagement interface design design evaluation showcase 15

16 Assumptions? Ownership HMI has been developed to accommodate either Focus on In-vehicle HMI, not additional 3rd party services Case studies will acknowledge additional services (for example; booking, parking, mobility support) Vehicle type Pod as test vehicle, but HMI design could be applied to any vehicle Simulator testing allows; high speed, variable journey times, main roads Level of Autonomy Fully autonomous (5) Older people would benefit mostly from this level out autonomy when they no longer drive - likely to transition earlier

17 Older people as use case Has it been designed specifically for older people? How is this different from other HMIs? We know why people currently stop driving Age related impairments prevent continued independent mobility Change in: Vision, hearing, mobility, cognition HMI for all Not a bespoke solution for older people Needs of older people have informed design Accommodating and understanding their needs will inform a better experience for all Simple, intuitive, accessible, flexible

18 Design approach Working closely with end users to gather needs and desires Balance between understanding; What people are used to (expectations) and Sharing what is possible (technology) - a vision of the future User-centred needs capture - we listen and observe Design led development - we challenge and create Attitudes are different depending on technology acceptance System should accommodate the needs of all - flexibility Start with expectations and concerns of older people Level 5 seems crazy now! Trust in technology with increase with use Give people a vision and let them try it

19 Initial reactions It sounds very futuristic I don t drive" It won t happen in my lifetime They sound expensive What about safety and reliability?

20 Expectations Where am I? Have I got enough fuel? Is the vehicle OK?

21 User Engagement User needs capture stakeholder engagement, public engagement, surveys, participant workshops, design workshops with older people design that meets needs of 70+ year olds in terms of accommodation of impairments, technology use and the kind of journeys they make Basic HMI principles - trial 1 First use of CAV HMI for older people Features older people shared as most important Developing more features / interaction modes in further iterations

22 HMI principles Accessible/Usable Best practise user interface design (not always evident in automotive industry) Simple, intuitive, language/layout consistency, clear images/icons/fonts, high contrast Flexible/Adaptable Multi-modal (voice/touch) Ability to customise to individual use Functional Do the things you need it to do - for example; make changes Two way interaction - communicate status/what is happening Desirable Great user experience Technology people want to use Flourish developing best practise HMI principle for level 5 CAVs

23 HMI Iteration 1 - basic functionality

24 Journey Definition 24

25 Dashboard 25

26 dash.8 Fuel indicator: How much fuel will be consumed on current journey and overall fuel remaining Dummy data Pop up info when selected dash.9 dash.10 dash.11 Quick controls: Temperature Volume Music Temperature - dummy Volume - dummy Music - dummy Pop up controls when selected Journey closure (coming to the end of a journey) exit.1 exit.2 exit.3 exit.4 Arrival countdown: Displayed as destination or waypoint is approached Determined by journey selection - uses data from Simulator Pop up exit.5 exit.6 exit.7 Safe STOP: CAV finds next safest place to stop at (not Emergency stop) Not included in trial 1 STOP - Pop up interface when selected Journey closure 26

27 Screen 2 - profile, infotainment and future journey planning Ref. Feature description Simulator Trial 1 Notes My Profile two.1 About me: Home address Calendar: To help plan journeys based on where you are going Contacts: Addresses of friends for easy navigation Health profile: to inform HMI (visual impairment for example) Demo only not functional Used to gauge opinion on these features in trial 1 to be tested more fully in later trials two.1 Preferences: Text size Layout Brightness Contrast Demo only not functional Information and Entertainment Music Internet Television Dummy link to google search 27 link to BBC iplayer

28 Novel Features Ref. Feature description Simulator Trial 1 Notes Novel features Pod Spacing: Space between pod and vehicle in front can be modified within limits Speed adjustment: Ability to adjust pod speed within limits Demo - will have no effect on journey Demo - will have no effect on journey Not included in trial 1 Not included in trial 1 CAV brain Not included To be shared in WP3 engagements Augmented surroundings Not included To be shared in WP3 engagements Link to 3rd party services Not included To be shared in WP3 engagements CAV social network Not included To be shared in WP3 engagements 28 Emergency response Not included To be shared in WP3

29 Simulator testing Trial 1

30 Trial 1 feedback Despite basic functionality: HMI rated at least 7 out of 10 for all participants in terms of overall usability [n=30] The opportunity to plan future journeys was popular with participants Participants are not so keen to share personal data with the vehicle Participants expect to have the option to dictate journey aspirations to the HMI via voice Successful first technical trial paving way for future trials

31 HMI Iteration 2 features Developing more features / interaction modes Modifying journeys ability to change destination and add and remove stops Notifications and updates route, vehicle, network, CAV actions - what do users think? Voice interaction ability to interact with the HMI via voice; voice recognition, journey set up, voice updates, querying HMI/CAV, basic controls Settings and preferences customise HMI to you; which notifications? voice or not? basic design changes (e.g. colour) Adaptability early stage design testing during iteration 2; customise visual layout, what information you want, choose features will take input from HSM testing

32 HMI Iteration 2 + voice dashboard

33 HMI Iteration 2 + choice

34 HMI Iteration 2 + notification and updates

35 HMI Iteration 2 + modification (add stop) + settings and preferences (determined by trial 2 scenarios) + adaptability - share ideas with participants in trial 2 - input from HSM testing

36 What next?

37 Simulator trial 2 May 2018

38 Real world trials June

39 Pod trial 1 HMI 39

40 HMI Iteration 3. + Showcase (6 September 2018, Bristol) + Projects outcomes (2019)

41 Expected outputs from project Best practise HMI design Fully working system - simulator based +development toolkit Flourish showcase with older adults as use case Mainstream HMI solution - accommodate most users Pod based HMI Version for use in Lutz pod and similar future models Simple interface to enable independent user control Support further research and testing of fully autonomous systems Other outputs Public engagement report on use of CAVs and the needs of users with specific impairments Requirements for CAV HMI s to meet the needs of all users, including those with age related impairments

42 Thank you :) Questions?

43 Thank you If you d like to find out more visit: Follow us on Copyright info except where stated otherwise. The Flourish logo and strapline are trademarks of the Flourish Consortium. 43