**Executive Summary**

According to the "Guidelines on Data Management in Horizon 2020"  1  , the
Data Management Plan has the aim to produce data so that researchers may
benefit by their use directly, and / or to apply their methods based on data
generated by Research in Horizon 2020. The AEOLIX Data Management Plan governs
all data generated and collected during the project, the standards that will
be used, how the research data will be preserved and what parts of the
datasets will be shared for verification or reuse. The documentation of this
plan is part of work package 4 (WP4) Collaborative data exchange certification
framework.

The data relevant in the AEOLIX project can be roughly divided into three
categories:

  1. Data retrieved from project participants, LL actors and other stakeholders by non-technical means, e.g. by participation in surveys, through interviews etc. 

  

  2. Data used in the technical implementation of the AEOLIX platform, e.g. position data of vehicles or cargo, scheduling data (ETA), custom or billing information. 

  

  3. Project internal administration data such as meeting agendas and minutes, cost statement, internal reports. 

  

  

The category 1 data will be mainly used in the WP 2 (Lessons learned,
strategic needs and requirements) which is focused on experiences and future
needs of potential AEOLIX users and WP6 (AEOLIX evaluation framework) which
concentrates on the results achieved in the LL operations.

Category 2 data is used in the application of the AEOLIX platform at the
different living labs and is of relevance to WP3 (AEOLIX IT Ecosystem) dealing
with the development of the AEOLIX system and WP5 (Verification with Living
Labs) which aims at the implementation of AEOLIX in real-word situations, i.e.
the Living Labs (LL).. The handling of category 2 data is considered highly
complex and is can only be partly described in the present document. The
details will be presented in the following deliverables of WP4:

  * D4.1: Best practices for AEOLIX collaborative data sharing 

  

  * D4.2: AEOLIX high level architecture guideline for collaborative data exchange 

  

  * D4.3: Guidelines for an AEOLIX framework for legal, trusted, interoperable and high quality data exchange 

  

Category 3 data is AEOLIX consortium internal and may have different levels of
confidentiality. The agenda of AEOLIX general assemblies may for example be
available to the public whereas cost statements of individual partners will
not be disclosed outside the consortium.

The format of the plan follows the Horizon 2020 template.

  * To comply with the Horizon 2020 Open Data Access Guidelines 

  

  * To embed the AEOLIX project in the EU policy on data management which is increasingly geared towards providing open access to data that is gathered with funds from the EU. 

  

  * To ensure that all possible data will be accessible to other researchers, helping to streamline the research process from start to finish. 

  

**1\. Introduction**

#####  1.1 Purpose of Document

The purpose of the present document is the provision of a Data Management Plan
(DMP). The AEOLIX Data Management Plan (DMP) is defined within the context of
the Grant Agreement. The full text of this Deliverable is addressing the “Open
Access to Research Data” Objective. The document describes the level of
confidentiality of different data sets, defines data governance and privacy
principles, and the strategy towards contributing to the Open Data Research
Pilot. It has been prepared by taking into account the template of the
“Guidelines on Data Management in Horizon 2020”. In addition, to that the
project has dedicated a specific Work Package called ‘’Data governance’’ with
the aim to address all issues related with data within the project. The
intention of the AEOLIX project is to publish no confidential results under
Open Access, regarding all scientific publications produced along the project
lifecycle. Although it is preferable to publish in online publications free of
charge, when it is not possible it will be up to the partner who will cover
the associated costs. The AEOLIX Open Access strategy relates to the EU “Open”
paradigm for publishing project results, which foresees two possible ways of
accessing the published results: Gold Open Access, which grants immediate
access through a publisher, and Green Open Access. The consortium will decide
which data will be part of an open data scheme to become available for the
Open Access Data initiative. Various mechanisms to protect identities and
sensitive information will be enforced as a part of the data management
actions. The DMP is Deliverable D4.6 due on month 6 of the project. After that
due date the DMP will remain a living document throughout the project's
lifetime. The present first version may evolve during the project according to
the progress of project activities.

###  1.2 Procedures to update the Data Management Plan

The strategy for updating the present document has not been fully developed at
this early stage of the AEOLIX project. However, certain factors have been
identified that may trigger the publication of new versions of the DMP, such
as

  * Change of the scope of a Work Package (WP); 

  

  * Addition/Deletion of deliverables from WPs; 

  

  * Input from Living Labs (LL) operation; 

  

  * Inputs from work on deliverables D4.1, D4.2 and/or D4.3. 

  

#####  1.3 Intended audience

This deliverable is aimed to the AEOLIX Consortium as a reference document
with the objective of covering all aspects of data management for all WPs.
However, it may be of special importance to the LL within the project
consortium as they may need to exchange data with the partners active in the
development of the AEOLIX architecture in WP3. This is a public document which
can be downloaded by external stakeholders which might be interested in
cooperate with AEOLIX consortium.

**2\. Literature Review of Data Management**

###  2.1 Definition

The Data Management Plan will describe the data management life cycle for the
data to be collected, processed and/or generated by the AEOLIX project, during
the project lifetime itself, and once it is completed. This will help to
better manage the data, meet funder requirements, and help others use these
data when they are shared, ensuring that these data are well managed in the
present, and prepared for preservation in the future.

###  2.2 Personal Data

Personal Data refers to any information relating to an identified or
identifiable natural person, meaning by identifiable person the one who can be
identified, directly or indirectly, in particular by reference to an
identification number or to one or more factors specific to his physical,
physiological, mental, economic, cultural or social identity. Data is
considered personal when someone is able to connect information to a specific
person, even when the person or entity that is holding the personal data
cannot make the connection directly (e.g. name, address, e-mail), but has or
may have access to information allowing such identification (e.g. through
telephone numbers, credit card numbers, license plate numbers, etc.).

####  2.2.1 Personal Data Protection

The fundamental right to the protection of personal data is explicitly
recognised in Article 8 of the Charter of Fundamental Rights of the European
Union, and in Article16 of the Treaty on the functioning of the European
Union, according to which _everybody has the right to the protection of
personal data concerning them_ . Such data must be processed fairly for
specified purposes and on the basis of the consent of the person concerned or
some other legitimate basis laid down by law.

####  2.2.2 Personal Data Processing and movement

The European Parliament and Council Directive 95/46/EC _on the protection of
individuals with regard to the processing of personal data and on the free
movement of such data_ establishes on its Article 6 that Personal Data must be
processed fairly and lawfully, and collected for specified, explicit and
legitimate purposes and not further processed in a way incompatible with those
purposes. These data must be also adequate, relevant and not excessive in
relation to the purposes for which they are collected and/or further
processed, and also accurate (and, where necessary, kept up to date) keeping
them in a form which permits identification of data subjects for no longer
than is necessary for the purposes for which the data were collected or for
which they are further processed.

The Article 7 continues to determine the rules for processing data, allowing
this only if the data subject has unambiguously given his consent, meaning by
this (as per Article 2) “ _any freely given specific and informed indication
of his wishes by which the data subject signifies his agreement to personal
data relating to him being processed”._ Another circumstance required for
processing personal data is that it is necessary:

  * for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract; 

  

  * for the compliance with a legal obligation to which the controller is subject; 

  

  * in order to protect the vital interests of the data subject; 

  

  * for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller or in a third party to whom the data are disclosed; 

  

  * for the purposes of the legitimate interests pursued by the controller or by the third party or parties to whom the data are disclosed, except where such interests are overridden by the interests for fundamental rights and freedoms of the data subject which require protection. 

  

####  2.2.3 Information given to the data subject

According to the Article 10 of the Directive, the subject must be informed by
the controller of the data or his representative about from whom data relating
to him are collected, specifically about:

  * the identity of the controller and of his representative, if any; 

  

  * the purposes of the processing for which the data are intended; 

  

  * any further information such as the recipients or categories of recipients of the data, whether replies to the questions are obligatory or voluntary, as well as the possible consequences of failure to reply, the existence of the right of access to and the right to rectify the data concerning him in so far as such further information is necessary, having regard to the specific circumstances in which the data are collected, to guarantee fair processing in respect of the data subject. 

  

Article 11 establishes that the same information will be given to the data
subject where the data have not been obtained from him, at the time of
undertaking the recording of personal data or if a disclosure to a third party
is envisaged , no later than the time when the data are first disclosed,
except for the cases where, in particular for processing for statistical
purposes or for the purposes of historical or scientific research, the
provision of such information proves impossible or would involve a
disproportionate effort or if recording or disclosure is expressly laid down
by law.

##  3\. AEOLIX data

#####  3.1 Data summary

The data relevant in the AEOLIX project can be roughly divided into three
categories:

  1. Data retrieved from project participants, LL actors and other stakeholders by non-technical means, e.g. by participation in surveys, through interviews etc. 

  

  2. Data used in the technical implementation of the AEOLIX platform (supply chain data coming from the living labs, other open data- e.g. statistics, GPS, metadata from standards or information exchanges) 

  

  3. Project internal administration data such as meeting agendas and minutes, cost statement, internal reports. 

  

  

The category 1 data will be mainly used in the WP 2 (Lessons learned,
strategic needs and requirements) and WP6 (AEOLIX evaluation framework). WP2
is focused on experiences and future needs of potential AEOLIX users and will
gather its data by a set of measures:

  1. Web based survey to establish the state-of-the-art and the problem awareness (lessons learned); 

  

  2. Analysis of information obtained in other WPs; 

  

  3. Individual interviews based on a defined questionnaire; 

  

  4. Delphi analysis in physical meetings. 

  

  

Delphi is used in complex situations and its aim is to reach the correct
response through consensus. Whereas in the original technique question rounds
are administered in writing, the WP2 of the AEOLIX projects has focused on
physical meetings where the selected experts have been invited to express
their opinions about the proposed issues, answering several questions and
deciding together a consensus about those.

WP6 concentrates on the results achieved in the LL operations. As the
methodology on how to obtain the results is part of the work of WP6 (Cost-
Benefit Analysis evaluation tool, Multi-Criteria Analysis and Analytic
Hierarchy Process), the exact nature of the resulting data cannot be described
at the time of the writing of the present data management plan.

Category 2 data is used in the application of the AEOLIX platform at the
different living labs and is of relevance to WP3 and WP5. This data will carry
a big variety of information (supply chain data, geographic positions,
schedules, legal data, price information, etc.) of different levels of
confidentiality. Furthermore, the data will be present in many different
formats that will be processed by the AEOLIX connectivity engine. The concept
of the AEOLIX platform does not imply the long term storage of the data under
processing; however, short term storage of real-time data may not be
completely avoidable.

However, the handling of this data is highly complex and is not completely in
the scope of the present document. However, some considerations are made in
clause 3.2 of DMP. Further details will be presented in the following
deliverables of WP4:

  1. D4.1: Best practices for AEOLIX collaborative data sharing 

  

  2. D4.2: AEOLIX high level architecture guideline for collaborative data exchange 

  

  3. D4.3: Guidelines for an AEOLIX framework for legal, trusted, interoperable and high quality data exchange 

  

  

Category 3 data is AEOLIX consortium internal and may have different levels of
confidentiality. The agenda of AEOLIX general assemblies may for example be
available to the public whereas cost statements of individual partners will
not be disclosed outside the consortium.

#####  3.2 Accessibility of data

The raw category 1 data (e.g. results from the web survey, qualitative KPIs
from LL evaluations) will be kept in restricted storage areas as they are
considered private and/or confidential.

However, the aggregated results derived from the different data gathering
methods will be made available through publicly available AEOLIX project
deliverables, mainly of WP2 and WP6. They will be available through the AEOLIX
website

Category 2 data is mostly owned data that the data owners do only want to
disclose to partners with which they have a business relation. The nature of
the data exchanges between AEOLIX partners,

e.g. in the context of a LL, may be manifold and aspects such as
confidentiality or data security are usually covered by mutual agreements
between the partners that exchange and process data.

Consequently, category 2 data is not publicly available to any party outside
of the AEOLIX consortium and even within the consortium strict rules for data
access have to be established (see D4.3). This is of special importance as
data from many partners will run through the AEOLIX platform, where it may be
manipulated (e.g. data conversion) and exchanged between different data
handling/displaying entities. The concept of the AEOLIX platform does not
imply the long term storage of the data under processing; however, short term
storage of real-time data may not be completely avoidable.

During the operation of the AEOLIX project, partners of the consortium will
have access to the web based project management tool project place. This tool
allows the exchange and sharing of any kind of information. Within the AEOLIX
context, it will be mainly used to exchange and archive category 3 data.

#####  3.3 Interoperability of data

Data interoperability only applies to category 2 data and is at the heart of
the AEOLIX project. The whole AEOLIX concept aims at achieving data
interoperability between all players in the technical area of logistics. The
AEOLIX Platform represents a critical way forward of supply chain
interoperability through decentralized information sharing. AEOLIX is
established via cloud services where data, application, on-premises and cloud-
based processes and services from multiple actors can be connected - enhancing
collaboration and interoperability, potentially across the entire freight
transportation system. Data governance in AEOLIX will ensure the proper Data
Management of important and sensitive data including information for
customers, product designs, to be appropriately managed, anonymized, encrypted
and sanitized, managing risks which should arise upon their access by third
parties. The details of achieving data interoperability will be presented in
the deliverables of WP3.

#####  3.4 Reusability of data

The concepts of the reuse of data apply to category 2 data and will be
investigated throughout the operation of the LLs in WP5 (AEOLIX Verification
with Living Labs). Within WP8 (Collaborative business models and AEOLIX
exploitation) the principles for the exploitation of the AEOLIX platform will
be developed. This will include also aspects of data reusability. The
following aspects will be covered by WP8

  * How the data will be licenced to permit the widest reuse possible 

  

  * How the data produced and/or used in the project is useable by third parties, in particular 

  

after the end of the project

  * How long the data will remain re-usable 

  

#####  3.5 Allocation of resources to Data Management

The AEOLIX project has a whole WP dedicated to data management issues. WP4
(Collaborative data exchange certification framework) is considered
complementary to the technical approach for a collaborative architecture as
set up in WP3 (AEOLIX IT Ecosystem) and aims to establish a sustained flow of
information across modes, entities and countries enabled by interoperable
systems and standards, allowing the re-use of data and trustworthiness of the
data content. AEOLIX has assigned the WP leader PTV to provide a mechanism for
controlling changes related to the data, data processes, and the data
architecture of AEOLIX and act as data protection officer. WP4 addresses the
structural problems and barriers of data exchange and sharing and develop
solutions to overcome. The AEOLIX governance model is to address the different
levels of data exchange starting reaching from strategic over tactical to
operational issues. Key stakeholders in industry and administrations are
involved.

More specifically WP4 aims to:

  * Identify and assess key AEOLIX practices for collaborative data sharing (liaise with LL) 

  

  * Define an architecture for cross entity data exchange and sharing 

  

  * Develop a framework for trusted, interoperable and high quality data exchange including legal aspect 

  

  * Develop a certification framework to certify company, who want to join the AEOLIX platform 

  

In total a resource of 112 man months has been allocated to WP4. However, this
also includes the development of certification schemes and the organisation
and execution of two TESTFEST events.

#####  3.6 Data security

The AEOLIX consortium will use the web based projectplace to tool to store and
exchange category 3 data within the partnership. Access to projectplace is not
public and the ERTICO project management team will assign and manage the
access rights of the project partners to the tool. AEOLIX stakeholders should
stay in control on who has access to their data. Privacy and data security are
very important strategic requirements.

The Conceptual Security and Privacy Taxonomy will be applied. It contains four
main Big Data security & privacy principles:

  * Data confidentiality topic: safeguarding the confidentiality of personal data. 

  

  * Data provenance topic: safeguarding the integrity and validation of personal data. 

  

  * System health topic: safeguarding the availability personal data. 

  

  * Public policy, social, and cross-organizational topics: safeguarding the specific Big Data and privacy & data protection requirements. 

  

Project participants are already covered by a Consortium Agreement which
encompasses NonDisclosure clauses as well as their Contract with the EC which
itself includes clauses on the treatment of data. However, NDAs are
implemented to cover future users, as well as through the implementation of
security measures in their processing systems aimed at a level of protection,
according also to the principle of proportionality, which should be at least
the same as that provided to their own confidential information.

#####  4\. Data confidentiality

The data to be considered as confidential as not so much related to personal
data or information as these are protected under basic data protection
legislation, as analysed in the previous section. Here it is particularly
technical, commercial information that are placed within the scope of
protection. This information may have intellectual property rights protection
over it, but it may well be the case that it is unprotected raw data, that
however still possesses business value for the disclosing party. The preferred
means through which to protect confidential information exchanged during
execution of the AEOLIX project are (NDAs) and these are included in the
present Consortium Agreement which has been signed by all partners. However,
after the end of the research project, when results will be rolled-out to
organizations which are not partners in AEOLIX and therefore not covered by
the present Consortium Agreement, it is essential that comprehensive NDAs are
signed prior to any disclosure of information. Such agreements should be
drafted by the Project Coordinator and entered whenever deemed important
before confidential information exchanges.

Regarding confidentiality measures of the different AEOLIX categories:

  1. Data retrieved from project participants, LL actors and other stakeholders by non-technical 

  

  

means, e.g. by participation in surveys, through interviews etc.

Participants in interviews or other activities must be asked to sign a
relevant form, in order for their consent to be demonstrable in writing. The
form must be composed in accordance with legal requirements, i.e. among others
to describe how the information will be used, how the person concerned may
review or amend them. Such data are responses to interviews, or views from
DELPHI studies. More details can be found in Data per WP.

  2. Data used in the technical implementation of the AEOLIX platform 

  

  

These supply chain data coming from the living labs are often commercial data
(shipper’s data like invoices, inventory data, GPS position data, delivery
information, data coming from services of the Living lab). This information
constitutes valuable commercial business information and if unauthorized
access was granted to them could cause serious damage to AEOLIX partners.
Therefore, as a general principle: This data will not be shared outside the
consortium and access within the consortium will be strictly limited to only
those parties agreed by the data owner. Other types of data are coming from
the evaluation and impact assessment evaluation results. Data in this category
require the agreement of all commercial parties related, to eliminate
sensitive information. More details can be found in Data per WP.

  3. Project internal administration data such as meeting agendas and minutes, cost statement, internal reports. 

  

  

These administrative data and project minutes are Confidential, only for
members of the Consortium (including the Commission services). More details
can be found in Data per WP.

##  5\. Detailed Data Management Aspects per WP

The data that is collected or generated in AEOLIX, contributes to different
purposes depending of the objective of the WP they relate to. The following
sub clauses provide an overview of the deliverables per WP giving also the
origin of the data in tables.

The tables will deliver the following information:

  * **Data set reference and name:** Pointer to the deliverable containing the data 

  

  * **Data set description:** Descriptions of the data that will be generated or collected 

  

  * **Data collection procedures:** Description how the data was collected or produced 

  

  * **Data privacy** : Description how data is kept confidential, if applicable 

  

  * **Data sharing/ confidentiality** : Description of how data will be shared, e.g. publicly available or consortium internal only 

  

###  5.1 Data in WP1

Table 1 – Data in WP1  
  
<table>  
<tr>  
<th>

**WP1**

</th>  
<th>

**Project Management**

</th> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Quality and Risk Management Plan

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

The AEOLIX Quality Plan will define all quality processes and procedures to be
applied throughout the project, including documents and Deliverable
Management.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Both Quality and Risk Management Plan will be developed under PRINCE2
Principles which are: Business justification, Roles and responsibilities,
Learn from experience, Manage by exceptions, Manage by stages, Tailor to suite
the environment, Focus on product.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

Confidential, only for members of the Consortium (including the Commission
services)

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Coordination Plan for a harmonised coordination of the LLs

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Each Living Lab develops a plan, agreed with the EC, with the aim to
demonstrate progress in the AEOLIX LLs

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Each LL will include a Gantt Chart (What the various activities are, When each
activity begins and ends, How long each activity is scheduled to last, Where
activities overlap with other activities, and by how much, The start and end
date of the whole project).

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

Confidential, only for members of the Consortium (including the Commission
services)

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Yearly Management and Progress reports.

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

The AEOLIX Yearly Management and Progress reports will inform the PO and
reviewers of the progress made by the Consortium.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Produced by the AEOLIX management team

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

Confidential, only for members of the Consortium (including the Commission
services)

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Final report.

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

The AEOLIX Final Report will summarise the work performed by the Consortium
members and the interaction with any external stakeholders

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Produced by the AEOLIX management team

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

Public

</td> </tr> </table>

###  5.2 Data in WP2

Table 2 – Data in WP2  
  
<table>  
<tr>  
<th>

**WP2**

</th>  
<th>

**Lessons learned, strategic needs and requirements**

</th> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Lessons learned

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

The result is a deliverable giving a clear vision of the technical and non-
technical elements that led previous solutions in the logistics field to
either success or to failure.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Analysis of the existing approaches, screening of projects, commercial
solutions and roadmaps within the domain of AEOLIX.

</td> </tr>  
<tr>  
<td>

**Data collection method**

</td>  
<td>

Web-based survey among stakeholders (from Europe and beyond) to identify
additional current and future needs and gaps in current provisions.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

The individual survey answers will be treated with confidentiality.

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D2.1

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

New and revised general needs and requirements

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

The requirements are divided into two groups:

  1. Functional requirements that define specific behaviour or functions with a focus on the utility 

  

  2. Non-functional requirements (that define the quality and general behaviour of the actors involved in the system operations 

  

  

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

The data is coming from the living labs in the project and much of the data
will be collected via deliverables D5.2 Connectivity Gap Analysis and D5.3
Logistics Business Needs and Data Identification Report.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D2.2

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

AEOLIX global needs and requirements

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Information to be collected:

  1. Trends in business needs as to demand and supply in logistics services 

  

  2. New types of processes envisaged and new kinds of ICT and information services needed 

  

  3. Trends in ICT technologies (including Secure, resilient and trusted communications and information storage and processing) 4. Trends in ITS technologies especially those focusing on the driver, the vehicles and the cargo. 

  

  

5 Current and future expected legislative and standards requirements

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Questionnaire as basis for individual interviews followed by a two round
Delphi analysis in physical meetings.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

The individual interview answers and the discussions during the Delphi
analysis will not be disclosed.

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D2.3

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

AEOLIX reference book

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Continuous upgraded information on AEOLIX requirements

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Establishment of a task force consisting of representatives from logistics
actors, software developers, authorities and academia from within the
consortium, that performs a continuous monitoring of the evolutions of the
demand and supply in the logistics market, of the ICT domain, of the
information sharing tools etc.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

The AEOLIX Reference Book will be continually communicated via a dedicated
space on the AEOLIX website and via direct meetings with representatives of
other WPs.

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

KPIs and evaluation criteria

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Indicators of local and global levels, e.g.

Network efficiency, Environmental impact, Economical sustainability, Traffic
network management, Driver specific metrics, Goods specific metrics

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Evaluation criteria and performance targets will be set in collaboration with
the LL leaders and will take into account use cases, LL setup, historical data
and projection and models of the expected impact of each of the applications
at each site.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D2.5 and will serve
as input to WP6.1 Evaluation framework WP 6.2 AEOLIX Living Labs business
impacts, WP6.4 Business Paradigm Shift Analysis and WP 7.4 Business Model
Scenarios.

</td> </tr> </table>

###  5.3 Data in WP3

Table 3 – Data in WP3  
  
<table>  
<tr>  
<th>

**WP3**

</th>  
<th>

**AEOLIX IT Ecosystem**

</th> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

AEOLIX Ecosystem technical architecture specification

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Definition of the AEOLIX IT architecture that enables the real-time data-
sharing platform, supporting the connectivity network and interoperability of
the different systems, applications and objects of the ecosystems through
AEOLIX IT platform services

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

_Definition of the AEOLIX Reference Architecture_ : Description of the
different ecosystem services and elements that will comprise the AEOLIX Cloud
Ecosystem, detailing the connectivity engine communication protocols that will
be used to interact among them, the collaborative ecosystem builder module and
detailing the services to support the functionalities.

</td> </tr> </table>  
<table>  
<tr>  
<th>

</th>  
<th>

_Definition of Platform services_ : Exchange of specific information among the
systems of the ecosystem and the security in those processes

_Definition of additional AEOLIX Platforms services_ : Management of the
ecosystem resources (reporting, statistical information, user administration,
support tickets, ecosystem status, admin newsletter, etc.)

</th> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

This data is publicly available as AEOLIX deliverable D3.1

</td> </tr>  
<tr>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Connectivity engine reference implementation

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Specification and provision of the Connectivity Infrastructure Services of the
AEOLIX Ecosystem based on development of data pipelines and cloud messaging
technology

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

The software source code will be non-public. IPR details are for further
study.

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

The textual description is publicly available as AEOLIX deliverable D3.2

</td> </tr>  
<tr>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

AEOLIX Intelligent Dashboard

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Definition and development of the AEOLIX dashboard as the component that
enables logistic stakeholders to create and configure the collaborative
environments composed by those stakeholders that are part of the logistic
network required for the transport of goods, and aiming to share information
between them.

AEOLIX provides an open AEOLIX API to provide access to main

AEOLIX IT Connectivity Services and a Software Development Toolkit (SDK) to
enable developers to join the ecosystem or creating the opportunity to develop
new pan-EU logistics applications based on the platform capabilities and
AEOLIX toolkit capabilities.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

The software source code will be non-public. IPR details are for further
study.

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

The textual description is publicly available as AEOLIX deliverable D3.3

</td> </tr>  
<tr>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Services and interoperability adapters

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Provision of the technical specification of the AEOLIX Data interoperability
services and security recommendations for a secure development of AEOLIX
ecosystem and services.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Control methods proposal, for the main security risks in the architecture.

Identification of the most suitable security solutions.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Logistics stakeholders use different standards and formats:

  * EDIFACT 

  

  * ODETTE 

  

  * GS1 Standards 

  

  * Common Framework 

  

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

This data is publicly available as AEOLIX deliverable D3.4

</td> </tr>  
<tr>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

AEOLIX API and SDK

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Provision of the procedure and necessary tools to allow developers, public and
private services to publish services and apps in the central functionalities
provided by AEOLIX for seamless integration into dashboards and intelligent
applications.

Development and implementation of standard interface mapping procedures.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

The software source code will be non-public. IPR details are for further
study.

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

The textual description is publicly available as AEOLIX deliverable D3.5

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

AEOLIX Toolkit

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

The toolkit provides a set of functional tools and component that can manage
the multitude of logistics information flows that will be accessible through
AEOLIX.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

The software source code will be non-public. IPR details are for further
study.

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

The textual description is publicly available as AEOLIX deliverable D3.6

</td> </tr> </table>

###  5.4 Data in WP4

Table 4 – Data in WP4  
  
<table>  
<tr>  
<th>

**WP4**

</th>  
<th>

**Collaborative data exchange certification framework**

</th> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Best practices for AEOLIX collaborative data sharing

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

AEOLIX Architecture for Collaborative Data Exchange; Complete overview of the
high level governance architecture related to the integration, securing,
management of data flows and organisation within AEOLIX.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Practices from different use cases, industry collaborations or PPP are the
basis for this task. Topics and approaches will be defined from the LL and
WP3.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D4.1

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

AEOLIX high level architecture guideline for collaborative data exchange

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Definition of generic data exchange and sharing architecture for AEOLIX
describing the processes related to the integration, securing, management and
measurement of data flows and organisation.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Based on the AEOLIX LL requirements, taking into account other research
initiatives (e.g. NEXTRUST).

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D4.2

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Guidelines for an AEOLIX framework for legal, trusted, interoperable and high
quality data exchange

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Guidelines for legal and organisational framework:

  1. Information ownership, data access levels and scope, data liability as treated within the EU member states. 

  

  2. Data re-use and sharing 

  

  3. Data quality and accuracy 

  

  4. Data interoperability 

  

  

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Extension of work from WP4.2

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D4.3, a high level
description of the data management within AEOLIX will be publicly available in
deliverable D4.6.

</td> </tr>  
<tr>  
<td>

**Archiving and preservation**

**(including storage and backup)**

</td>  
<td>

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Specification for certification framework for the AEOLIX platform

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Framework for certifying companies, who want to join the AEOLIX platform.
Objectives:

  1. Evaluation of compliancy of devices and services with the data governance model 

  

  2. Specification of the AEOLIX certification framework to check compliancy with the data governance model 

  

  

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

The data from the guidelines in D4.2 and D4.3 will be used as input to develop
the certification framework. Feedback will be included by performing a test
certification at the TESTFESTs.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D4.5, the results
from the TESTFEST events will be public in deliverable D4.5

</td> </tr> </table>

###  5.5 Data in WP5

Table 5 – Data in WP5  
  
<table>  
<tr>  
<th>

**WP5**

</th>  
<th>

**Verification with Living Labs**

</th> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Connectivity gap analysis

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Definition of the data flow and gaps as experienced by the logistics partners
and official agencies which collaborate to improve supply chain performance
across specified corridors

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Data Issue Analysis for each LL, describing the specific data gaps that
currently hamper effective operations.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data sharing**

</td>  
<td>

This data is publicly available as AEOLIX deliverable D5.2

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Logistics Business Needs and Data Identification

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Analysis of the business needs data needed and the sources of such data and
the format available and needed in each LL.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Identification of the specific sources of data needed and the

</td> </tr>  
<tr>  
<td>

</td>  
<td>

format in which it exists and it is provided.

Definition of procedures and mechanisms required for authorization of data
access and import, and the level of data analysis and manipulation needed by
users within the Intelligent Dashboard, and which data will be supplied by or
sent to partners’ existing in-house systems, and what Toolkit solutions may be
deployed.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data sharing/confidentiality**

</td>  
<td>

This data is publicly available as AEOLIX deliverable D5.3

</td> </tr> </table>

######  5.6 Data in WP6

Table 6 – Data in WP6  
  
<table>  
<tr>  
<th>

**WP6**

</th>  
<th>

**Collaborative data exchange certification framework**

</th> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

AEOLIX evaluation framework

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Framework for assessing the impacts of the AEOLIX project:

  1. Identification of the operational benefits 

  

  2. Mechanism depicting the market penetration 

  

  

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Cost-Benefit Analysis (CBA) evaluation tool, Multi-Criteria Analysis (MCA) and
Analytic Hierarchy Process (AHP). KPIs defined on based of those tools
complemented by the KPIs identified in WP2.5.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D6.1

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

AEOLIX impacts

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

AEOLIX Living Labs impact assessment, will present the results living lab
evaluation including socio-economic impacts of the AEOLIX project on society
and the environment. Continuous presentation of quick win impacts as
identified from the initial implementation of the LLs.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

As described in AEOLIX evaluation framework

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverables D6.2, D6.3 and
D6.4. D6.3 AEOLIX quick win impacts will be updated quarter-yearly as of
project month 15.

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Data set reference and name**

</td>  
<td>

Business Paradigm Shift analysis

</td> </tr>  
<tr>  
<td>

**Data set description**

</td>  
<td>

Business Paradigm Shift analysis describing the modification of the business
models required by the implementation of the AEOLIX ecosystem and the new
collaboration schemes among the stakeholders.

</td> </tr>  
<tr>  
<td>

**Data collection procedures**

</td>  
<td>

Based on the impacts of the Living Labs in comparison to a benchmark. Paradigm
shift analysis by a dynamic monitoring of the performance and the impacts of
the pilots.

</td> </tr>  
<tr>  
<td>

**Data privacy**

</td>  
<td>

Not applicable

</td> </tr>  
<tr>  
<td>

**Data Sharing/confidentiality**

</td>  
<td>

This data will be publicly available as AEOLIX deliverable D6.5

</td> </tr>  
<tr>  
<td>

**Archiving and preservation**

**(including storage and backup)**

</td>  
<td>

</td> </tr> </table>

######  5.7 Data in WP7

WP7 (Dissemination, Communication and Market Outreach) aims to maximise market
take-up of the AEOLIX project objectives, concepts and outputs as realised in
the AEOLIX Living labs, to all relevant logistic stakeholders and public
authorities both during and after the life of the AEOLIX project by raising
awareness about the AEOLIX project, its activities and its achievements. This
WP does not deal with data in itself. However, it may be necessary to define
the status of certain documents, e.g. slide sets of speakers at a conference.
The details of the related proceedings will be defined within WP7.

######  5.8 Data in WP8

WP8 (Collaborative business models and AEOLIX exploitation) addresses all
deployment/business aspects that are essential for ensuring sustainable after-
project life of the AEOLIX platform, piloted services and established Living
Labs. This WP does not deal with data in itself. However, certain data used in
the development of e.g. deliverable D8.6 (Cost benefit Analysis) may need
consideration in regards to data privacy. These data are related to costs and
benefits of the different systems. These data will need to be confidential
internal to the consortium for analysis but can be disseminated externally as
a overall evaluation of the project. The details of the related proceedings
will be defined within WP8.

**6\. Ethics**

The AEOLIX partners are to comply with the ethical principles as set out in
Article 34 of the Grant Agreement, which states that they must ensure that the
activities under the action have an exclusive focus on civil applications, and
must be carried out in compliance with:

 ethical principles (including the highest standards of research integrity —
as set out, for instance, in the European Code of Conduct for Research
Integrity and including, in particular, avoiding fabrication, falsification,
plagiarism or other research misconduct) and  applicable international, EU
and national law.

Partners will deploy all the efforts needed to ensure a high level of
transparency in data treatment and compliance with national and European
legislations. The ethics procedures in the involved countries will be analysed
and, if needed, partners will collect the necessary permissions in their
entity / country. The involved AEOLIX parties that will lead the design and
implementation of the overall system architecture and data feeding components,
has notified the National Authority for Protection of Personal Data (Garante
per la protezione dei dati personali, no: 2014-061000196946) in order to be
qualified, as required by the national law (Legislative Decree no. 196 of 30th
June 2003), to manage data about position and tracking of persons and objects
for research activities.

Deliverables D9.1 PODP – Requirement 1, describe the AEOLIX procedures for
research actions involving data collection. Each beneficiary must submit to
the coordinator in good time notifications for activities raising ethical
issues (e.g. personal data collection) and before the beginning of an activity
raising an ethical issue (e.g. prior to any personal data being collected),
the coordinator must submit to the Agency copy of:

  * The Ethics Committee opinion required under national law and 

  

  * Any notification or authorisation for activities raising ethical issues required under national law. 

  

This act should have had received favourable opinions from the relevant Ethics
Committee and, if applicable, the regulatory approvals of the competent
national or local authorities in the countries where the research is going to
be carried out.

**7\. Confidentiality**

All AEOLIX partners must keep any data, documents or other material
confidential during the implementation for the project and for four years
after the project period set out in Article 3 (36 months); as per Article 36
of the Grant Agreement (GA). Further detail on confidentiality can be found in
Article 36 of the GA. This confidential information will only be used to
implement the Agreement; consequently the partners may disclose confidential
information to their personnel or third parties involved in the action only if
they:  need to know to implement the Agreement, and;  are bound by an
obligation of confidentiality.

Nevertheless, the confidentiality obligations no longer apply if:

  * the disclosing party agrees to release the other party; 

  

  * the information was already known by the recipient or is given to him without obligation of confidentiality by a third party that was not bound by any obligation of confidentiality; 

  

  * the recipient proves that the information was developed without the use of confidential information; 

  

  * the information becomes generally and publicly available, without breaching any confidentiality obligation, or 

  

  * the disclosure of the information is required by EU or national law.