D1.1 gives a clear introduction to the MEDIATOR concept and a comprehensive overview of the state-of-the-art knowledge on vehicle automation. It serves as a foundation for the project, it gives focus to our further research (in WP1) and is a starting point for the development of the mediator system (WP2).
Aims and scope
This report aims to define what we need to know to assess the fitness of the human driver and the automation, what we already know based on the available literature, and what are the research gaps that need to be bridged in order to develop the Mediator system. Information and approaches of existing Mediator-like systems in road and in other transport domains were also considered. In a more or less iterative process the review of needed and available knowledge helped to further elaborate a set of feasible functional requirements for three use cases. The results form the basis for the concrete design and work plan
for the technical development of the various components of the Mediator system and their interaction. The results also form the basis for the definition of a series of targeted experiments to fill the most prominent research gaps in the area of human fitness, automation fitness, and HMI, in order to make the best possible decision for a transfer of control, and define the best means of communication to the driver.
This deliverable discusses the assessment of human fitness, the assessment of the fitness of the automation, the HMI requirements, the decision making logic, and the functional requirements in relation to the identified use cases.
Conclusion and next steps
The main goal of the Mediator system is to determine who is fittest to drive (human or automation) and consequently define preferred actions to be sent to the HMI or automation in order to ensure safety and comfort of the human driver. To this end, four components of the system were defined: human state, automation state, HMI and decision logic.
This deliverable describes the state-of-the-art knowledge and corresponding knowledge and development gaps related to these four components as well as a description of the high level (non) functional requirements and relevant use cases for the MEDIATOR project. The identified knowledge and development gaps will be further investigated in the next steps in the project. More detailed requirements will be defined as well as a clear structure for the integration of all components into one Mediator system. Detailed use cases will be defined to test the Mediator system throughout the project and help with the prioritization of investigations into the identified knowledge gaps.
