View Categories

HVI

The Human Vehicle Integration (HVI) category comprises all factors related to the interaction between the highly automated system(s) and the user. This ranges across a broad area covering user experience, usability, human factors and cognitive ergonomics. A clear and well-designed HVI is a key factor in gaining the user’s acceptance of the ADF and to ensure their safety. The impact of the HVI on user experience, usability and the underlying safety of the ADF are very important and should not be underestimated. In other words, the HVI factors must be designed, developed and implemented in such a way that it is easily and safely operated by the user of an ADF. Whereas the HVI is about the harmonious interaction between the user and the vehicle in a broader sense, the Human Machine Interface is more specifically about the hardware and software interface between them. The topics of this category are guidelines for HVI, mode awareness, driver monitoring, controllability and customer clinics, as well as tele-operators and driver training, including the variability of users.

The HVI category comprehends the following topics:

  • User's Clinics – It includes aspects of different nature, related to “what the users would need", such as variability (of subjects), customer's clinics, controllability, and so on. In fact, the interaction with the different levels of automated driving (only exception can be L5-SAE) requires the driver to take over the driving task in the event of system failures and malfunctions.
  • Human Machine Interaction with internal user (driver) – It consists in a systematic review of the design principles that promote trust in AD systems and underlines the fundamental importance to inform users about the situations and events that are about to happen or to be managed. A clear and well-designed Human Machine Interaction is a key factor in gaining the user’s acceptance and trust of the ADF.
  • Shaping Human Machine Interaction with other road users (via vehicle kinematics) – It addresses the correct understanding of the role shared between the internal user (i.e., the driver of the host vehicle) and the other road users, especially with reference to the correct usage of the ADF (in public and shared roads). The awareness of the current automated driving mode is crucial for the safe operation of the vehicle, which interacts with the other ones and with the vulnerable road users (VRUs) in general.
  • Human Machine Interaction with other road users: eHMI – It is in line with the previous topic, but this is specifically related to the external human-machine interface (eHMI) for the interaction. In fact, AVs should inform the environment in situations where it will slow down, stop, grant priority, or start driving again via an appropriate eHMI, regarding its future intention. This allows the other road traffic users to perceive, understand and adapt their behavior accordingly.
  • Driver State Monitoring (DSM) – It deals with the aspects of monitoring the cognitive status of the driver (e.g., distraction, drowsiness, fatigue, etc.) as well as which actions s/he is doing (with the possible extension to all the occupants of the vehicle). Thus, real-time monitoring of a driver’s cognitive status is a crucial topic for twofold reasons: i) from SAE-L3 and over, driver is allowed to perform non-driving-related tasks (NDRTs); ii) the knowledge of driver status (namely, if s/he is attentive or distracted) is fundamental before a take-over request (TOR) is issued.
  • Remote Control or Tele-Operation – It is about the design of teleoperation procedures to extend the ODD, remotely managing vehicle operation. When the AV encounters an event in which it requires support, it relays an event notification to the remote operator, which has to be efficient and ready to intervene properly. Therefore, the human-factor aspects of teleoperators should include how supervision is affected by distraction, fatigue and different mental models of system capability.
  • Take Over Request (TOR) – It has the goal of investigating all the aspects related to a request-to-intervene (RTI), in terms of the right time and right mode. AVs can make transportation safer, but at the same time they can have problems in dealing with complex situations (such as e.g., dense urban traffic, for perception difficulties). Especially in this context, where the ADFs reach the limits of their ODD, a TOR is necessary to ask the driver to get back control of the vehicle. When using AVs, the drivers are removed by their "traditional" role, leaving them the monitoring/supervision task. Since they are no longer required to actively monitor the driving environment, they are allowed to fully engage in non-related driving tasks (NDRTs). This situation can have a potential drawback: the high probability of error when the driver is asked to resume control of the vehicle.