Skip to main content
To KTH's start page To KTH's start page


We make driving as safe as flying.

Project Description

AutoDrive  is a European project focusing on the development of connected, electric and highly automated vehicles with special focus on safety. AutoDrive started in June 2017 and will last for 3 years. It has 60 partners, each of which is a company, a research institute or a university within Europe. Involved companies include Automotive OEMs, suppliers and also consultant companies.

All 60 partners

With diverse background of all the partners, AutoDrive aims to find synergies among different aspects of autonomous driving. From the development perspective, it covers the whole development lifecycle from requirement analysis to validation and Test. From the product perspective, it includes most of the automotive functional components for automated driving such as perception, communication, decision, control and the electrical powertrain. From the technical perspective, it considers software, hardware, system architecture and safety.

This huge project is managed in a matrix way as shown in the figure below. The horizontal axis refers to the six technical work packages (WPs). The vertical axis refers to the 10 supply chains (SCs).

Graphic of all WP. The WP where KTH is involved are described in text on this page.

WPs are divided according to the development V cycle of the automotive domain as shown below. Each WP contains multiple tasks. The outcome of each task is a deliverable report.

Each SC represents a technical enabler of highly automated vehicle. The relationship among the SCs is illustrated in the figure below. Each SC connects corresponding tasks in different WPs. The outcome of each SC is one or more demonstrators. Therefore, each partner needs to work for both deliverable reports and demonstrators.

KTH in AutoDrive

Within AutoDrive, KTH is mainly involved in WP1, 2, 5 and SC2, 3. The following table presents the tasks that KTH is involved in within the AutoDrive matrix structure. The date in parentheses denotes the end date of the task. Among these tasks, KTH is leading T2.10, which is marked in italics in the table below.

  SC2 HAD SAE Level 4 SC3 Cooperative active safety


(Req. & Spec.)
T1.4 Requirements for future automated vehicle in urban scenarios (March 2018)

T1.6 Specification of critical scenarios for cooperative active safety (End 2017)

T1.7 Specification of the active safety system (Feb. 2018)

WP2 (Sys. Lvl. Design) T2.8 Design of architecture for automated vehicle in urban scenarios (Feb. 2019) T2.10 Functional safety concept for active safety (Sep. 2018)
WP5 (Sys. Int.) T5.8 Demonstrator integration and verification (End T5.7 Integration of collaborative active safety system components (Feb. 2020)


KTH also needs to contribute to two demonstrators

For SC2, KTH, with other partners, needs to work for an electric bus from IRIZAR to enable it with automated driving.

IRIZAR bus in grey scale.
Research concept vehicle (RCV) from ITRL, KTH.
And for SC3, KTH needs add a safe stop maneuver to the research concept vehicle (RCV) from ITRL, KTH.


Belongs to: Engineering Design
Last changed: May 19, 2021
6 DOF Haptic devices
A New 6-DOF Haptic Device
Auto2: Automation for autonomous terrain mobility
Combined Model-based Analysis (MBAT)
Complete Vehicle Energy-saving (CONVENIENT)
CPS Integrated Information Engineering (CPS IIE)
CREST: Coarse Grain Reconfigurable Embedded Systems Technologies
Developing Mechatronics Education in Uzbekistan
Dynamic Simulation for Robot Grasping and Manipulation
Efficient Safety for Products (ESPRESSO)
IDIOM - Integrated Design and Optimization of Mechatronic Products
Internet of DevOps (IoD)
FUSE: FUnctional Safety and Evolvable architectures for autonomy
Integrated Design of Mechatronic Systems
Log traceability and forest automation
oCPS Graduate Course: Communication Systems for CPS
oCPS: Platform-aware Model-driven Optimization of Cyber-Physical Systems
oCPS Travel and Accommodation info