Designing the f-HMI for Automated Vehicles Case Study
•
0 likes•19 views
Cognitive Ergonomics in Complex Systems: Designing the f-HMI for Automated Vehicles
Recommended
Recommended
More Related Content
Similar to Designing the f-HMI for Automated Vehicles Case Study
Similar to Designing the f-HMI for Automated Vehicles Case Study (20)
More from RojinMoghadam
More from RojinMoghadam (20)
Recently uploaded
Recently uploaded (20)
Designing the f-HMI for Automated Vehicles Case Study
- 1. f-HMI for Automated vehicles Cognitive Ergonomics Assignment 4: Designing the f-HMI for Automated vehicles Alexandra Maria Bartas - 5165369 Rojin Ghorbani Moghadam - 5088135 Jeroen Lieveloo - 4567382 Parastou Raeis Ghanavati - 5242568 Group 7
- 7. Renaming the modes Manual Mode = SAE level 0 Cooperative mode = SAE level 2 Autonomous mode = SAE level 3
- 8. Journey Map (Scenario 1)
- 10. Journey Map (Scenario 2)
- 11. HMI concept
- 17. Car surrounding and context (Manual, Cooperative) Speedometer, fuel meter, detected objects around the car to help the driver be more aware of the surrounding. OR 2nd custom panel (Autonomous) Usable for apps such as zoom calls, presentation slides, music players, etc. Control panel (Manual) Options to control the car OR Action log (Cooperative, Autonomous) Displays the current action and past actions the car has taken and why. This informs the use why it took that action. Driving mode Shows what Automation mode the car is currently on Transition change notification area Displays when a transition is available or required and how long before it is available if it is an expected transition. GPS (Manual) To help the driver navigate. OR Custom panel (Cooperative, Autonomous) Usable for apps such as zoom calls, presentation slides, music players, etc. Central Console
- 21. Braking for pedestrians Turn Left Speed Up Exited Roundabout Entered Roundabout Scenario: Teleconference (refining prioritization: color code)
- 22. Scenario: Construction work ahead
- 24. Scenario: Driving past construction
- 25. Scenario: Back to teleconference
- 32. Scenario: Autonomous mode available
- 33. Scenario: Listening to music
- 34. Scenario: Listening to music
- 36. Thank You
Editor's Notes
- This transitional journey map represents the first round of the scenario. The thickness of the lines represents the mental workload of the user\automated systems.
- This transitional journey map represents the second round of the scenario. The thickness of the lines represents the mental workload of the user\automated systems.
- Looking from the user’s point of view, these transitions arise feelings and emotions that we decided to intuitively demonstrate.
- In the image you can see the different levels of autonomy as described in the SAE standard. We renamed the different levels of autonomy to make them more meaningful to the driver. We chose the name manual, because the driver is driving fully manually in SAE level 0. Cooperative mode reflects working together with the car and assisting it if needed. SAE level 3 is the most autonomy that the car can offer and is therefore called Autonomous mode.
- Since the transition map focused more on the journey of the car, we made a journey map for the user (Florance), where we go through each action of the scenario and map out what are her thoughts, wants and feeling throughout. Underneath we placed opportunities for the UI. Q: how did the feeling map influence the design of your UI? A: We tried to look at the pain points and think how to reduce the lowest slopes. For example, we thought that by letting the user know at the beginning of the journey if there are any points in time they would have to take over the manual control (that they could have not known before e.g. construction site). That is why you can see at the beginning stage an opportunity is to show a visual of the road ahead or an auditory feedback of any obstacles in the way. (note add the user wandering why the car is doing something and looking for answers Adding later that the user is aware at all tims what mode the are in)
- Maybe show with a speaker icon when there is auditory feedback or tactile feedback? Q: When there is an important notification, why not put it on the HUD? A: We want to keep the view of the road open for the driver to take in the situation. As for highlighting objects/ things using the HUD: The car doesn’t know what to do, and relying on highlighting when the car does not understand the situation enough could highlight the wrong thing and misguide the drivers attention.
- In this scenario Florance is surprised again that she has to take over manual control when she approaches the arena. She was hoping to relax before going back to her office. An opportunity here is to let her know from the beginning (based on updated data) that she will have to take manual control at a specific time. At the same time when she is in the situation the car can inform her of what is going on or why she has to have manual control. Instead of trying to figure it out herself and getting more frustrated the interface can give text notifications of what is going on.
- The rear view mirror indicates upcoming events and non priority events, while the central console displays more detailed information and allows control of the car functionality. For instance here the car is in cooperative mode and it is indicated with a car symbol that it is currently overtaking another car.
- The car is in cooperation mode but due to construction nearby the driver is notified by the indicators in the rear-view mirror that he/she will need to take control of the car shortly.
- The driver is prompted to take control on the central console. The driver can do this by simply grabbing the steering wheel. The driver can also take control during any mode, even if the car did not request it.
- The car changes to manual mode and the driver can see the nearby construction on the GPS.
- The car is in autonomous mode and the user can use the central console for personal use. The driver can see that the car doesn't expect that the driver ill need to take control in the nearby future because it is not indicated in the rear view mirror.
- Here the information that is required constantly is available on the left, closest to the driver. This information are indicators like speed, fuel and nearby objects to the car. The information in the center is not necessary to drive the vehicle, but does make the job easier. Such as the GPS and the possible availability of cooperation and manual mode. Lastly the information on the most left sides are not (often) required for driving, or only relevant when the car is driving itself. Such as the driving mode. When the user is driving/ has its hands on the steering wheel, this mode will always be manual. And if the option is available to change than that is shown in the center. If the user is not driving, they can take their eyes off the road so it is easy to look at the right side of the central console at that point.
- Florence's car is parked on the street in front of her house. Although on the edge of the city, she lives on a busy road. She needs to go to the meeting venue next to the city. She starts driving manually.
- 1 km later, Cooperative mode (SAE level 2) is available. So, she starts Cooperative mode driving by letting go of the steering wheel
- Florence receives the call for her teleconference meeting which she can attend because she is not driving anymore. However, she will need to be prepared to take the wheel on short notice if needed. Q: Why did you list the actions the car took? A: For 2 reasons: 1. To let the user know why the car took the actions it did. For instance, it is nice to know that it abruptly stopped because there was a child running across the road. This is to hopefully make these events understandable instead of irritating. Another example from the journey map when Florence was passing by the Arena the car can inform her of what is going on or why she has to have manual control. Instead of trying to figure it out herself and getting more frustrated the interface can give text notifications of what is going on. 2. If the driver wants to take control then the user should know what the car was ding at the moment the user took over. For instance, if the car is at a standstill in the middle of an open road, it is good to know that the car is stopping for a red light, so when the user sees that there is no red light, the user knows it can take over and start driving. Q: Do you think the list of taken actions is legible? Seeing as it is the furthest away from the driver? A: It should still be legible because it is still quite close to the driver. Nonetheless, it is not that urgent to read and is only there when the user is not driving so it does not matter if they need to take a second to read it. The text gradually fades away so there is no overload of information. The important information could be prioritised with color coding and text size.
- Based on the discussions after presenting our idea, we implemented the color coding system for prioritizing notifications on the right side of the screen.
- Few minutes into the call, she approaches a construction site. The Cooperative mode (SAE level 2) cannot drive through a construction site independently, so Florence has to take over. Florence’s call is put on hold and she receives a takeover request 5 seconds away from the construction site.
- Florence drives past the construction manually while assisted by the GPS and using the car overview to spot closeby objects.
- After passing the construction, Florence is asked if she wants to re-engage Cooperative mode (SAE level 2) and continue the teleconference call.
- Florence continues her call while the car drives in cooperative mode. Q: what if the user wants to drive again instead? A: At any point, the user can take the wheel and the car will give control back to the user.
- The teleconference call ends and after moving out of a complex city, she can start driving in autonomous mode (SAE level 3). Florence acknowledges this by tapping the touch screen and it switches to autonomous mode.
- Florence starts reviewing the presentation on the central console while listening to music. Q: why do you keep the list of taken actions, now that the user is not required to pay attention anymore? A: It is to give the user understanding of why the car took actions, not as a requirement to stay informed, but for them to read for their own interest if they want to understand why the cad did what it did. Also, still to re-evaluate if they want to take control if they feel that the car is doing something wrong.
- While reading the presentation, the systems inform Florence that she will have to takeover in 5 minutes. (Expected transition) If the car can predict when a switch to manual mode will need to be made, than the time the user has left before that will be indicated in the center under the mode change notification area.
- After few minutes, she receives a takeover request to continue driving manually.
- After few kilometers, she is informed that she has reached her final destination. Her company is on the right side of the road—the vehicle parks on the street parking right in front of the entrance of the company.
- After few kilometers, she is informed that she has reached her final destination. Her company is on the right side of the road—the vehicle parks on the street parking right in front of the entrance of the company.
- After 2 km, SAE level 3 is available, and she engages it.
- Florence is driving in SAE level 3. She is so tired that she is a bit relaxed, listening to music.
- She approaches a football stadium area. Usually, the vehicle can pass this area using SAE level 3. However, because many people are running across the street without a traffic light, she receives a takeover request to continue driving manually during this area.
- She is informed that she has reached her final destination. Her office is on the right side of the road—the vehicle parks on the street parking right in front of the entrance of the company.