#  INTRODUCTION

EC Horizon 2020 project DIVERSITY (Grant Agreement No. 636692) consortium
decided to take part in the Pilot on Open Research Data in Horizon 2020 on
voluntary basis by expressing this will on project proposal. This is the
associated Data Management Plan (DMP) in the form of a deliverable.

This document should be considered in combination with Section 3 of the Grant
Agreement “RIGHTS AND OBLIGATIONS RELATED TO BACKGROUND AND RESULTS” that
concerns intellectual property, ownership, exploitation and dissemination of
the results and access right to results of the project. This DMP is intended
as a first draft, keeping in mind what is stated in the _**Guidelines on data
management in Horizon 2020:** “The DMP is not a fixed document, but evolves
during the lifespan of the project _ ”. Eventual further developments will be
structured as additional deliverables if issues arise that have not been
foreseen.

Hereafter are listed the datasets that have been considered relevant to the
project to date, together with a description of their possible evolution. Each
dataset is examined following the template given by the _**Guidelines for Data
Management in Horizon 2020.** _

#  SCIENTIFIC PUBLICATIONS  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

_Description and origin:_ Text and images. Scientific articles produced under
DIVERSITY and based on data collected during the project and on the
experiences with project business partners and business cases.

_To whom it would be useful:_ to researchers and companies interested in
carrying on program on PSS and lean engineering.

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

**Format**

</td>  
<td>

PDF, txt

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

**Standards and metadata**

</td>  
<td>

Standard: ISO 19005-1 PDF/A because these documents are thought for long term
archiving.

Basic metadata included:

  * Title 

  

  * Author 

  

  * Subject 

  

  * Keywords 

  

  * Created 

  

  * Modified 

  

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

**Data sharing**

</td>  
<td>

Open access via project website  www.diversity-project.eu,  a copy of
publication may be made available on zenodo.org and on publisher website.

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

**Archiving and preservation**

</td>  
<td>

For long term preservation of text data type both pdf and txt version of the
file will be stored. This way as pdf might not be readable, information will
still be obtainable by the txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  GENERIC ONTOLOGY  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

_Description:_ DIVERSITY General Ontology describes the components that build
DIVERSITY prototype and the relations among them. It describes also a general
scheme widely applicable with no possible limitation given by a specific
context.

This dataset will be produced as soon as a draft version of the ontology will
be defined. It will evolve during the project and will reach a final version
at the end of DIVERSITY.

_To whom it would be useful:_ to researchers and companies interested in
carrying on program on PSS and lean engineering.

_Indications on the existence of similar data:_

Example of ontology stored in zenodo with open access
https://zenodo.org/record/16493#.VaePafntmko

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

**Format**

</td>  
<td>

RDF/XML, OWL/XML

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

**Standards and metadata**

</td>  
<td>

XML Schema and OWL as defined by W3C.

Basic metadata included:

  * Title 

  

  * Author 

  

  * Subject 

  

  * Keywords 

  

  * Created 

  

  * Modified 

  

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

**Data sharing**

</td>  
<td>

Open access via project website www.diversity-project.eu

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

**Archiving and preservation**

</td>  
<td>

For long term preservation of text data type both pdf and txt version of the
file will be stored. This way as pdf might not be readable, information will
still be obtainable by the txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  SPECIFIC ONTOLOGY  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Description: DIVERSITY Specific Ontology, describes the components that built
DIVERSITY prototype and the relations among them. Each file will describe an
ontology related to a specific business case. The ontology will be developed
in cooperation with industrial DIVERSITY’s partners.

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

**Format**

</td>  
<td>

RDF/XML, OWL/XML

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

**Standards and metadata**

</td>  
<td>

XML Schema and OWL as defined by W3C.

Basic metadata included:

  * Title 

  

  * Author 

  

  * Subject 

  

  * Keywords 

  

  * Created 

  

  * Modified 

  

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

**Data sharing**

</td>  
<td>

Private dataset. It features data related to each specific business case
company’s confidential information

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

**Archiving and preservation**

</td>  
<td>

For long term preservation of text data type both pdf and txt version of the
file will be stored. This way as pdf might not be readable, information will
still be obtainable by the txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  GENERAL REQUIREMENTS  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Description: Text and images. Lists of requirements that are guiding the
development of the full prototype.

Set of lists underlying deliverable D1.2. The requirements descripted are “top
level” type and are extracted from the more detailed requirements associated
to each business case.

This list can be useful to software developers and researchers interested in
applications useful for PSS development and management.

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

**Format**

</td>  
<td>

PDF, txt

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

**Standards and metadata**

</td>  
<td>

Standard: ISO 19005-1 PDF/A because these documents are thought for long term
archiving.

Basic metadata included:

  * Title 

  

  * Author 

  

  * Subject 

  

  * Keywords 

  

  * Created 

  

  * Modified 

  

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

**Data sharing**

</td>  
<td>

Open access via project website  www.diversity-project.eu,  a copy of
publication may be made available on zenodo.org

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

**Archiving and preservation**

</td>  
<td>

For long term preservation of text data type both pdf and txt version of the
file will be stored. This way as pdf might not be readable, information will
still be obtainable by the txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  SPECIFIC REQUIREMENTS  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Text and images. Lists of requirements derived from business cases as a direct
description of the needs of each industrial partners. These requirements will
lead to the development of the specific ontologies at paragraph 4.

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

**Format**

</td>  
<td>

PDF, txt

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

**Standards and metadata**

</td>  
<td>

Standard: ISO 19005-1 PDF/A because these documents are thought for long term
archiving.

Basic metadata included:

  * Title 

  

  * Author 

  

  * Subject 

  

  * Keywords 

  

  * Created 

  

  * Modified 

  

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

**Data sharing**

</td>  
<td>

No Open access and no public distribution due to confidential information
concerning industrial partners.

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

**Archiving and preservation**

</td>  
<td>

For long term preservation of text data type both pdf and txt version of the
file will be stored. This way as pdf might not be readable, information will
still be obtainable by the txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  BUSINESS CASES DESCRIPTIONS  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Description and origin: Text and images. A set of documents which describe the
introduction of DIVERSITY tools and software into companies environments.

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

**Format**

</td>  
<td>

PDF, .txt, .ppt

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

**Standards and metadata**

</td>  
<td>

Standard: ISO 19005-1 PDF/A because these documents are thought for long term
archiving.

Basic metadata included:

  * Title 

  

  * Author 

  

  * Subject 

  

  * Keywords 

  

  * Created 

  

  * Modified 

  

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

**Data sharing**

</td>  
<td>

No Open access due to the presence of confidential information on industrial
partners.

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

**Archiving and preservation**

</td>  
<td>

For long term preservation of text data type both pdf and txt version of the
file will be stored. This way as pdf might not be readable, information will
still be obtainable by the txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  GENERIC LEAN RULES  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Description and origin: Text and images. These rules are currently being
developed by DIVERSITY as stated in D1.3 System Concept and they “will
facilitate the transformation of PSS design considerations in terms of
customer requirements and technical constraints into usable design
guidelines.”

Set of rules that will make reusable the knowledge acquired in a process of
PSS development. These rules occur at two different levels: Content Design
level and Development process level.

This dataset can be useful for industries and organizations that aim at the
introduction of a lean environment for PSS development.

These dataset does not contain confidential information on industrial
partners.

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

**Format**

</td>  
<td>

PDF, .txt

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

**Standards and metadata**

</td>  
<td>

Standard: ISO 19005-1 PDF/A because these documents are thought for long term
archiving.

Basic metadata included:

  * Title 

  

  * Author 

  

  * Subject 

  

  * Keywords 

  

  * Created 

  

  * Modified 

  

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

**Data sharing**

</td>  
<td>

Open access via project website www.diversity-project.eu

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

**Archiving and preservation**

</td>  
<td>

For long term preservation of text data type both pdf and txt version of the
file will be stored. This way as pdf might not be readable, information will
still be obtainable by the txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  DEMO VIDEO OF PROTOTYPES (ONE FOR EACH COMPANY)  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Description and origin: Demo videos associated to each full prototype (Lean
Design and Visualization tool, PSS engineering environment, Context Sensitive
tool for search Stakeholders feedback analysis and KPI) and its test case
within an industrial partners.

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

**Format**

</td>  
<td>

The format is to be defined but will probably be Audio-Video Interleave (AVI)
container and MPEG-4 codec, or any similar format.

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

**Standards and metadata**

</td>  
<td>

Standard: standard associated to MPEG-4, ISO/IEC 14496-14:2003

Metadata to be defined but basic information about Product name, Author,
Copyright, Version, Language will definitely be included.

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

**Data sharing**

</td>  
<td>

Open access via project website  www.diversity-project.eu  where a link for
direct download will be provided. The demo version will be presented and
disseminated during various scientific events at the end of the project.

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

**Archiving and preservation**

</td>  
<td>

Measures for long term archiving will be taken once the dataset will be
defined.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  SOFTWARE: FULL PROTOTYPE  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Executable application and installation package of the full prototypes (Lean
Design and Visualization tool, PSS engineering environment, Context Sensitive
tool for search Stakeholders feedback analysis and KPI).

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

**Format**

</td>  
<td>

The format is to be defined.

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

**Standards and metadata**

</td>  
<td>

Although standards and metadata may vary depending on the language of the
development, basic metadata included will be:

Product name, Author, Copyright, Version, Language

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

**Data sharing**

</td>  
<td>

Open access via project website  www.diversity-project.eu.

A copy may be made available on zenodo.org

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

**Archiving and preservation**

</td>  
<td>

The first version will be archived on institutional servers at UNIBG and other
safe location of the consortium. Measures for long time preservation will be
taken when the format will be clearly defined.

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

#  SOURCE CODE  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Source code package associated to the full prototype. It will contain all the
files needed to generate the full prototype.

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

**Format**

</td>  
<td>

Format to be defined. The extension of single files varies depending on the
development language chosen.

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

**Standards and metadata**

</td>  
<td>

Although standards and metadata may vary depending on the language of the
development basic metadata included will be:

  * Typology 

  

  * Version 

  

  * Copyright 

  

  * Dimension /volume 

  

  * Language 

  

  * Product Name 

  

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

**Data sharing**

</td>  
<td>

Open access via  www.diversity-project.eu,  a copy may be made available on
zenodo.org and on publisher website.

The consortium is currently evaluating the licensing policy considering the
following licenses: Creative Commons CC BY-NCND, GNU GPL or Mozilla Public
License.

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

**Archiving and preservation**

</td>  
<td>

The first version will be archived on institutional servers at UNIBG and other
safe locations of the consortium. Measures for long time preservation will be
taken when the format will be clearly defined. The project portal will be
active for 5 years following the end of the project.

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

#  PROTOTYPE USERS’ ROLES  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Text. Roles associated to a specific user behaviour in approaching software
prototypes. This datasets will be the basis for producing user manual.

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

**Format**

</td>  
<td>

PDF, .txt other formats to be defined.

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

**Standards and metadata**

</td>  
<td>

Standard: ISO 19005-1 PDF/A because these documents are thought for long term
archiving.

Basic metadata included:

  * Title; 

  

  * Author; 

  

  * Subject; 

  

  * Keywords; 

  

  * Created; 

  

  * Modified. 

  

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

**Data sharing**

</td>  
<td>

Open access via project website  www.diversity-project.eu,  sensitive
information will be cleaned out from the dataset.

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

**Archiving and preservation**

</td>  
<td>

For long term preservation of text data type both pdf and txt version of the
file will be stored. This way as pdf might not be readable, information will
still be obtainable by the txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  USERS' FEEDBACK ON TEST CASES  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Text. Feedbacks gathered during the application test phase through a
questionnaire. They will include a detailed description of each test case of
the full prototype and the associated profiling of the user that is
undertaking the test.

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

**Format**

</td>  
<td>

PDF, .txt

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

**Standards and metadata**

</td>  
<td>

Standard: ISO 19005-1 PDF/A because these documents are thought for long term
archiving.

Basic metadata included:

  * Title 

  

  * Author 

  

  * Subject 

  

  * Keywords 

  

  * Created 

  

  * Modified 

  

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

**Data sharing**

</td>  
<td>

Open access via project website  www.diversity-project.eu,  with sensitive
information cleaned out from the dataset.

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

**Archiving and preservation**

</td>  
<td>

For long term preservation of text data type both PDF and txt version of the
file will be stored. This way, as PDF might not be readable, information will
still be obtainable by the txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  MULTIMEDIA  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Promotional Demo videos created specifically for advertising purposes. These
videos (probably integrated with interactive features) will show the features
developed by DIVERSITY and the derived benefits to a PSS development. They are
thought to be shown around in fairs, conferences, etc.

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

**Format**

</td>  
<td>

Audio-Video Interleave (AVI) container and MPEG-4 codec.

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

**Standards and metadata**

</td>  
<td>

Standard: standard associated to MPEG-4, ISO/IEC 14496-14:2003

Basic Metadata:

  * Title 

  

  * Author 

  

  * Copyright 

  

  * More Info 

  

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

**Data sharing**

</td>  
<td>

Open access via project website  www.diversity-project.eu.

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

**Archiving and preservation**

</td>  
<td>

The AVI container has been chosen even if proprietary, but it is widely
diffused and well supported by open source and other tools. Codec MPEG-4 has
been chosen as a good compromise between compression for archiving and loss of
information.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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

#  SOCIAL NETWORK POSTS  
  
<table>  
<tr>  
<th>

**Data set description**

</th>  
<th>

Comment and issues posted on social networks both internal and external to
partners companies. Immediately after the distribution of the DIVERSITY
software, a series of questions regarding user experience will be asked on the
internal social networks. Users' posts will be collected and examined in order
to evaluate their satisfaction and issues observed.

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

**Format**

</td>  
<td>

The format will be probably JSON (JavaScript Object Notation) and an
associated .csv translation.

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

**Standards and metadata**

</td>  
<td>

Standard associated to json interchange format : ECMA-404 Metadata fields will
be defined later in this project.

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

**Data sharing**

</td>  
<td>

Partial data sharing due to privacy-related issues and the presence of
sensitive information. Posts will be made anonymous. This dataset will be
stored on project website repository  www.diversity-project.eu.

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

**Archiving and preservation**

</td>  
<td>

Even if JSON is yet good for long term preservation, as it is a text format
that is completely language independent .json file will be stored together
with a txt or csv version this way, if .json won’t be readable anymore
information will still be retrievable from the associated .csv/.txt.

Data will be stored on UNIBG server, kept in a secure and fireproof location.
Server administration assures daily and monthly backups of the data files. The
project portal will be active for 5 years following the end of the project.

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