Richard Romano
Please Note
3 records found
1
Conceptualising user comfort in automated driving
Findings from an expert group workshop
The driving style of an automated vehicle (AV) needs to be comfortable to encourage the broad acceptance and use of this newly emerging transport mode. However, current research provides limited knowledge about what influences comfort, how this concept is described, and how it is measured. This knowledge is especially lacking when comfort is linked to the AV's driving styles. This paper presents results from an online workshop with nine experts, all with hands-on experience of AVs and a long track record of research in this context. Using online tools, experts were invited to introduce concepts they considered relevant to comfort/discomfort in currently available modes of transport which offer a ride (taxi/bus/train) to users and compare these to the concepts used to define comfort and discomfort in AVs. Results showed that a wide range of terms were used to describe user comfort and discomfort for both modes. Although all terms used for existing vehicles were found to apply to AVs, additional terms were proposed for determining comfort/discomfort of AVs. For example, to enhance comfort in AVs, designers should consider good communication channels, as well as ensuring that the AV's capabilities match users’ expectations. Results also revealed that more terms were used, overall, to define discomfort, and that a comfortable ride in AVs is not just about mitigating discomfort. New concepts specific to AVs were also revealed when considering what increases their discomfort, such as whether riders’ safety and privacy are affected, or if they feel in control. Experts’ input from the workshop was used to enhance and expand a simple conceptual framework, explaining how AV driving styles, as well as other, non-driving-related factors, affect user comfort. It is hoped that this framework provides a more comprehensive list of the concepts affecting user comfort, also allowing more accurate measurement of the concept. As well as allowing for a more accurate comparison between empirical studies measuring comfort in AVs, this study will facilitate the design of more comfortable and acceptable automated driving for future vehicles.
In the original article, author affiliation published with error. The correct affiliations are: Davide Maggi—Institute for Transport Studies, Leeds, UK. Richard Romano—Institute for Transport Studies, Leeds, UK. Oliver Carsten—Institute for Transport Studies, Leeds, UK. Joost C. F. De Winter—Faculty of Mechanical, Maritime and Materials Engineering, Delft University of Technology, Delft, The Netherlands. The original article has been corrected.
When terminology hinders research
The colloquialisms of transitions of control in automated driving
During the last 20 years, technological advancement and economic interests have motivated research on automated driving and its impact on drivers’ behaviour, especially after transitions of control. Indeed, once the Automated Driving System (ADS) reaches its operational limits, it is forced to request human intervention. However, the fast accumulation and massive quantity of produced studies and the gaps left behind by standards have led to an imprecise and colloquial use of terms which, as technology and research interest evolve, creates confusion. The goal of this survey is to compare how different taxonomies describe transitions of control, address the current use of widely adopted terms in the field of transitions of control and explain how their use should be standardized to enhance future research. The first outcome of this analysis is a schematic representation of the correspondence among the elements of the reviewed taxonomies. Then, the definitions of “takeover” and “handover” are clarified as two parallel processes occurring in every transition of control. A second set of qualifiers, which are necessary to unequivocally define a transition of control and identify the agent requesting the transition and the agent receiving the request (ADS or the driver), is provided. The “initiator” is defined as the agent requesting the transition to take place, and the “receiver” is defined as the agent receiving that request.