Organisation

 nIoVe's project management has two main principles:

  1. The project organisation and management structure ensure that the stated objectives can be achieved with minimum deviations respecting timeline, the scope of the nIoVe solution efforts, and budget.
  2. Any changes or deviations and potential risks in the project structure will be managed with special care from the start of the project and supported by continuous (re)planning for the evolution and diffusion of the project results during and after the project lifecycle. 

The figure below illustrates the key organisation and roles in the management of the project.

Picture4

The day-to-day activities of the nIoVe project will be monitored by the following key members:


The Project Coordinator (PC) will be Dr. Dimitrios Tzovaras of CERTH
The Technical and Innovation Manager (STM) will be of Dr. Shahid Raza of RISE
The Pilot Manager (PEM) will be Ms. Marc Châtelain of TPG
The Exploitation Manager (EP) will be Mr. Antonio Jara of HOPU
The Dissemination & Communication Manager (DCM) will be Mrs Thalia Kouri of SEEMS
The Interoperability, Standards and Ethics Manager (ISEM) will be Mr. Paolo Balboni of ICTLC
The Quality Assurance Manager (QAM) will be Dr. Sebastian Steinhorst of TUM

  • Work Package 1: Project Management & Ethics

The core objectives of this WP are: (1) To coordinate the technological and scientific orientation of the project, to ensure the delivery of the project on time and within the budget and that the project maintains its relevance towards the objectives, (2) To guarantee high-quality standards at all levels and to guarantee the accomplishment of the objectives, (3) To manage resources monitor the overall project performance and manage risks, ethics, and contingencies, (4) To establish appropriate relationships and communication channels with the funding actors as well as between consortium partners.

Start Date: M1 End Date: M40 Leader: CERTH 

  • Work Package 2: IoV Cybersecurity Challenges & Solution Architecture

This work package will take advantage from the analysis of the cybersecurity State-of-the-Art, as well as the requirements of the stakeholders in formulate the technical specifications of the nIoVe solution, to define the models used and finally to propose a technical and functional description of the overall system architecture.

Start Date: M1 End Date: M29 Leader: RISE 

  • Work Package 3: Secure Cyber-Threat Data Collection & Pre-processing across the CAVs Ecosystem

This work package aims to provide nIoVe decentralized information gathering from CAVs and connected infrastructure for complementing the implementation of WP4. Thus it will i) design and implement the data collection infrastructure, collecting data from all layers of the IoV ecosystem, ii) develop tools to monitor the behavior of the network and critical parts of it, or even specific IoT devices, iii) To provide trusted and secured infrastructure using blockchain technology.

Start Date: M3 End Date: M35 Leader: TUM 

  • Work Package 4: Machine Learning (ML)-Driven Threat Analysis & Situational Awareness Platform

Deep/Machine Learning is forming the development focus of this work package. The recent development of optimization techniques that can exploit deep structures will be taken into advantage in pervasive and successful application of Deep/Machine learning across the threat analysis arena. The tasks of the WP4 will collaborate with each other in order to complete the cycle of state-of-the-art analysis of risks in the IoV ecosystem, develop vulnerability assessment tools, detect cyberattacks and monitor network activities to finally help in decision making.

Start Date: M3 End Date: M35 Leader: UniGe 

  • Work Package 5: Multi-layered Cyber Response & Incident Recovery Mechanisms

This work package aims to the i) Development of an Attack Attribution and forensic readiness tools, to be used for reporting for new threats and risk to the IoV ecosystem, ii) Design of mechanisms for the assessment of CAVs and IoV ecosystem infrastructure vulnerability, iv) Development of a response and recovery Toolkits, for providing real-time response to attacks and recovery actions will be possible to take place.

Start Date: M9 End Date: M35 Leader: ATHINA 

  • Work Package 6: Integration of nIoVe Solutions & Interoperability

In this WP the individual components of the nIoVe architecture will be integrated into a single a robust construct. Moreover, actions towards interoperability with existing cybersecurity solutions will be taken (e.g. by device manufacturers). A set of Application Programming Interfaces (APIs) will be developed to implement the wished communication between components and with
the workflow systems used by the vehicle manufacturers and other stakeholders. With respect to the existing state of the art, this WP will take advantage of the open standards to offer interoperability to the overall system. This will allow developers and technology adopters to access data generated or stored by the nIoVe ecosystem without compromising either the user’s privacy or the integrity of the data critical artefacts produce during their operation. Moreover, adaptive user interfaces will be developed to offer usable and highly personalized interfaces to all user categories, including passengers and citizens. This involves bringing together of the software subsystems into one unique and robust system ready for demonstration and for performing the pilot studies (WP7). Last, but not least, the Shared Threat Intelligence Repository will be developed in this WP.

Start Date: M13 End Date: M40 Leader: CERTH 

  • Work Package 7: IoV Cybersecurity Validation, Demonstration & Support

The core objectives of WP7 are: i) to install the nIoVe technologies in foreseen infrastructures, using real-world and innovative scenarios (i.e.in CAVs and IoV ecosystem’s infrastructure) in order to reduce the familiar cyber-attacks, to quickly detect advanced cyber-attacks and effectively respond and recovery to them. The secondary objectives are: a) Enhance security of the designed CAVs, by ensuring that security-by-design principles are applied, b) Provide guidelines for the design of the nIoVe cybersecurity framework, c) Define rules and policies for data governance and privacy protection, and d) Establish a cybersecurity certification process for vehicles and IoT devices.

Start Date: M16 End Date: M40 Leader: TPG 

  • Work Package 8: Dissemination, Exploitation & Standardization

This WP aims at (1) raising public awareness of project achievements among the key user groups and stakeholders in the connected-autonomous vehicles and IoV network, the scientific community and the general public; (2) facilitating sharing of knowledge inside the Consortium and establishing the projects’ communication & dissemination methodology; (3) developing a business plan for the project tangible outcomes including cost-benefit & cost effectiveness analysis for all project exploitable foreground; (4) identification of challenges and gaps in ongoing connected-autonomous vehicles standardization process and provision of targeted
mandates for improving current connected-autonomous vehicles-related standards.

Start Date: M1 End Date: M40 Leader: HOPU

  • D2.1 CAVs Cybersecurity threats digest and analysis
  • D2.2 Report Of Stakeholder Requirements Needs & Interests

 

  • D4.6 Hypothesis testing toolkit - v2
  • D4.7 Continuous Big Data Monitoring Tool - v2
  • D4.8 Visual Analytics Suite for Situational Awareness Engine - v2

 

  • D6.1 Integration Roadmap of the Cybersecurity Solution for the IoV
  • D6.2 System Integration & Final nIoVe Prototype
  • D6.3 Interoperability Coordination & Open Standards
  • D6.4 Adaptive Graphical user Interfaces
  • D6.5 Threat Intelligence Repository
  • D6.7 Interoperability Coordination & Open Standards - v2
  • D6.9 Threat Intelligence Repository - v2

 

  • D7.2 nIoVe Pilots Installations & Lessons Learned - v1
  • D7.4 CBA/CEA analysis of nIoVe solutions
  • D7.5 Security, Privacy & Data Protection Guidelines for nIoVe
  • D7.6 Definition of the Cybersecurity certification protocol and tools for CAVs

 

  • D8.1 Detailed dissemination and communication plan - v1
  • D8.2 Report on Dissemination Activities, Public Participation and Awareness
  • D8.3 nIoVe’s web site - v1
  • D8.4 CAVs Market analysis and nIoVe exploitation strategy - v1
  • D8.5 Business Models & Final plan for the use and exploitation of foreground
  • D8.6 Survey on existing CAVs security and privacy standards
  • D8.7 Contributions to the standardization bodies, consortiums and Alliances - v1
  • D8.8 nIoVe Final Dissemination, Exploitation and Standardization report
  • D8.9 Detailed dissemination and communication plan - v2
  • D8.10 Detailed dissemination and communication plan - v3
  • D8.11 Detailed dissemination and communication plan - v4
  • D8.12 nIoVe’s web site - v3
  • D8.13 nIoVe’s web site - v4
  • D8.15 Contributions to the standardization bodies, consortium and Alliances - v2