#  Chapter 1 Introduction

The H2020 programme is implementing a pilot action on open access to research
data.

SUPERCLOUD as a participating project to this pilot action is required to
develop a Data

Management Plan (DMP). This DMP has been identified in the description of
action as

SUPERCLOUD deliverable D6.2. This document is drafted according to the
“guidelines on Data Management in H2020” (version 16 dated December 2013).

This is intended as a living document. It will be periodically revised to
reflect changes in the data that may be made available by the project, and to
provide additional information on the datasets as this information is
developed during the specifications of the experimental phases.

All partners have contributed to the document, particularly through the use of
a project wide questionnaire.

Since each partner will generate and manipulate data, the document is
organized with one section per partner. Each section is structured following
the 4-points structure described thereafter:

  1. Dataset description contains a textual description of the dataset. It aims at explaining, in a short paragraph, what the dataset contains and what the goal is. 

  

  2. Standards and metadata focuses on explaining the internals of the dataset, namely how a user can find syntactical and semantic information. 

  

  3. Data sharing addresses the issues related to data access, namely if the dataset is going to be indexed, and how and to whom it will be made accessible. 

  

  4. Archiving and presentation covers the aspects related to data availability, during and beyond the project, as well as the actions taken and planned to support availability. 

  

  

#  Chapter 2 Methodology

In order to compile the data management plan, a questionnaire was first
elaborated covering the main questions that need to be answered in the
template provided by the European Commission.

In a second phase, each project partner responded to the questionnaire,
filling it with as much detail as possible at this stage of the project.
Completed questionnaires were stored for analysis and traceability in the
project’s SVN repository.

In a third phase, the Data Management Plan was created as a synthesis of the
questionnaire results, attempting to take advantage of commonalities between
responses in order to provide a simple view of data management procedures
within the consortium.

Further revisions of the document will be based on updates to partner
questionnaires. Therefore, the DMP will be updated at least by the mid-term
and final review to be able to fine-tune it to the data generated and the uses
identified by the consortium.

In addition, a confidential index of datasets will be created and maintained
in the project when the datasets are created. Since the DMP itself is a public
document, information about the datasets, that may need to remain internal to
the project, will be provided to the EU and the reviewers.

The SUPERCLOUD project will consider open licenses and open availability for
the datasets. The reasons for not offering open access will be documented in
the partner questionnaires and in the appendix describing the datasets.

#  Chapter 3 Dataset TEC-Evaluation

##  3.1 Dataset description

For the purposes of evaluation and validation, in particular of the SUPERCLOUD
Architecture, Technikon will generate realistic mock-up data resembling
health-care records. The data will be generated applying realistic
distributions and dependencies. The current objective is to generate the
dataset independently of any pre-existing real dataset, although pre-existing
datasets such as census data will be analyzed.

The dataset will be owned and maintained by Technikon.

##  3.2 Standards and metadata

The dataset will contain data, using the common Comma-Separated Values (CSV)
format (used for example in the database community). This has been specified
in RFC 4180 [1].

Technikon will be responsible for maintaining the metadata associated with the
dataset.

##  3.3 Data sharing

The data will not be discoverable (no indexing). However, it will be
accessible, intelligible, and interoperable to RFC4180.

For the time being, no license is required. Hence, no restrictions on sharing
are foreseen to apply.

##  3.4 Archiving and presentation

The dataset will be disseminated to the consortium through the internal shared
SVN repository. It will be presented in SUPERCLOUD deliverables. When ready,
it may be disseminated to third parties through the SUPERCLOUD website.

The dataset is planned to remain available for three (3) years after the
project. Costs for the availability of the data after the end of the project
will be covered by internal funding.

#  Chapter 4 Dataset Orange-Measurements

##  4.1 Dataset description

Data will result from experiments of measurements aiming to validate one or
several components of the SUPERCLOUD security management infrastructure.

One such component could be the UPSC (User-to-Provider Security Continuum)
component developed in WP2. Other components are foreseen as well in compute,
data, and network security management infrastructures. The data falls into two
main categories:

  * Infrastructure data constitutes the primary source of information for the system. It provides all necessary indicators and metrics that allow managing optimal trade-offs between customer-controlled and provider-controlled security properties. A typical implementation of such 'infrastructure data' in the SUPERCLOUD project would include the following elements: 

    * Security management data: Events associated with intentional security breaches, including vulnerabilities, risks, infection alerts, unauthorized access, and intrusions. 

  

    * Reliability management data: Events associated with accidental faults and failures (both at the system and network layers), as well as the improper use of resources. 

  

    * Quality of service (QoS) indicators: Memory and CPU usage, network jitter and latency, disk space, and other optional performance metrics. 

  

  

  * User data could constitute a secondary source of information to the previous components. In SUPERCLOUD, we consider two types of user data: o Raw text data. 

    * Multimedia content, including both photos and video images. 

  

  

Several data formats can be foreseen such as Comma-Separated Values (CSV) or
simulated network traffic PCAP files. In any case, we do not expect the volume
of data to fall in the bigdata category.

The main source of infrastructure data will be the monitoring tools and
measurement tools on execution of the components developed during the project.
User data will be randomly created where necessary. This data will be
exclusively fictitious data that does not relate in any case to “real-life”
user instances. Therefore, there should not be any link to pre-existing data
in both cases.

The dataset will be owned and maintained by Orange.

##  4.2 Standards and metadata

Several data formats can be foreseen such as Comma-Separated Values (CSV) [1]
or simulated network traffic PCAP files. In any case, we do not expect the
volume of data to fall in the big-data category.

The main source of infrastructure data for the UPSC system will be the
monitoring tools (both at system and network layers) that will be implemented
in the demonstrators specifically developed as a proof-of-concepts for the
SUPERCLOUD technology. No real users or customers will used be during the
entire lifetime of the project.

User data will be randomly created where necessary. To illustrate the
technologies that will be developed during the SUPERCLOUD project, random user
data could be created according to a specific format. This data will be
exclusively fictitious mock-up data that does not relate in any case to “real-
life” user instances. No corresponding human participants will be involved
during the SUPERCLOUD project.

Target users are researchers for publication and validation purposes.

##  4.3 Data sharing

Information on sharing and availability will be decided and provided in a
later revision of the document, as licensing is under discussion. However, no
restrictions are currently foreseen.

Textual data will be interoperable with RFC 4180 and related formats. Network
data will be interoperable with PCAP format and similar formats.

##  4.4 Archiving and presentation

The dataset will be disseminated to the consortium through the internal shared
SVN repository. It will be presented in SUPERCLOUD deliverables. When ready,
it may be disseminated to third parties through the SUPERCLOUD website.

Costs for the availability of the data after the end of the project will be
covered by internal funding.

#  Chapter 5 Dataset IBM-Measurements

##  5.1 Dataset description

IBM expects to produce a dataset containing the results of experiments of
measurement and testing of multi-cloud systems within the SUPERCLOUD
infrastructure.

The results will include statistics regarding performance (latency and
throughput) under a set of SUPERCLOUD deployments/configurations associated to
different security requirements.

The dataset will be owned and maintained by IBM.

##  5.2 Standards and metadata

Several data formats can be foreseen including Comma-Separated Values (CSV)
files [1]. The volume of data is expected not to fall in the big-data
category.

Textual data will be interoperable with RFC 4180 and related formats.

Target users are researchers for publication and validation purposes.

##  5.3 Data sharing

IBM expects that part of the data will be made available. Information on
sharing and availability will be decided and provided in a later revision of
the document, as licensing is under discussion.

##  5.4 Archiving and presentation

The dataset will be disseminated to the consortium through the internal shared
SVN repository. It will be presented in SUPERCLOUD deliverables. When decided,
it may be disseminated to third parties through the SUPERCLOUD website.

Costs for the availability of the data after the end of the project will be
covered by internal funding.

#  Chapter 6 FFCUL-Measurements

##  6.1 Dataset description

FFCUL expects to produce a dataset containing results of experiments of
measurement and testing of multi-cloud systems within the SUPERCLOUD
infrastructure.

The results will include statistics regarding performance (latency and
throughput) under a set of SUPERCLOUD deployments/configurations associated to
different security requirements.

The dataset will be owned and maintained by FFCUL.

##  6.2 Standards and metadata

Several data formats can be foreseen including Comma-Separated Values (CSV)
files [1]. The volume of data is expected not to fall in the big-data
category.

Textual data will be interoperable with RFC 4180 and related formats. Other
raw data formats may be included if necessary.

Target users are researchers for publication and validation purposes.

##  6.3 Data sharing

FFCUL expects that the data will be made available. However, terms are still
under discussion and will be indicated in a later release of the DMP.

##  6.4 Archiving and presentation

The dataset will be disseminated to the consortium through the internal shared
SVN repository. It will be presented in SUPERCLOUD deliverables. When decided,
it should be disseminated to third parties through the SUPERCLOUD website and
internal FFCUL channels.

Costs for the availability of the data after the end of the project will be
covered by internal funding.

#  Chapter 7 IMT-Measurements

##  7.1 Dataset description

IMT expects to produce a dataset containing measurement information extracted
from network experiments, e.g. bandwidth, latency, jitter, collected during
experiments related to the SUPERCLOUD project.

The measurements will be realized on the THD-Sec infrastructure at IMT,
running a local instance of the SuperCloud architecture.

The dataset will be owned and maintained by IMT.

##  7.2 Standards and metadata

The dataset will be constituted of Comma-Separated Values (CSV) files [1]. The
volume of data is expected not to fall in the big-data category.

Textual data will be interoperable with RFC 4180 and related formats.

Target users are researchers for publication and validation purposes.

##  7.3 Data sharing

IMT expects that the data will be made available. However, terms are still
under discussion and will be indicated in a later release of the DMP.

##  7.4 Archiving and presentation

The dataset will be disseminated to the consortium through the internal shared
SVN repository. It will be presented in SUPERCLOUD deliverables. It could be
disseminated to IMT partners through joint experimentations on the THD-Sec
platform.

Costs for sharing will be borne by the THD-Sec platform.

#  Chapter 8 TUDA-Measurements

##  8.1 Dataset description

TUDA will generate a dataset containing measurements that constitute the
performance evaluation of the SUPERCLOUD architecture.

The data will be plain measurement data (e.g., timings of operations) in a
simple format like comma separated values (CSV) [1]

The volume will be rather small compared given today’s storage devices. The
volume will not exceed the volume storable on costumer hardware.

The dataset will be owned and maintained by TUDA.

##  8.2 Standards and metadata

The data will be stored in plain text files or in data formats used by open
source software, e.g., sql data base created with MySQL

##  8.3 Data sharing

TUDA expects that the dataset will be shared upon request, for academic
research purposes. Sharing will only occur after the relevant publications
have been accepted.

##  8.4 Archiving and presentation

The dataset will be disseminated to the consortium through the internal shared
SVN repository. It will be presented in SUPERCLOUD deliverables.

The dataset will be hosted on pre-existing storage infrastructures at TUDA, at
no additional cost.

#  Chapter 9 Dataset PHC-Evaluation

##  9.1 Dataset description

In the SUPERCLOUD project Philips Healthcare focuses on the cloud
infrastructure (for compute, data management, and network) required for
medical applications. It will NOT focus on the actual clinical analytics and
algorithms while using the infrastructure, therefore, all data used in the
project will be mock data. By not using actual patient data in the project, by
definition, it cannot be tracked back to a real person avoiding privacy and
ethical issues.

Usability of the dataset will be limited to interoperability testing of the
SUPERCLOUD architecture and prototypes.

The mock data will be available after test-case definition is finalized
therefore it will be further specified after M22 of the project.

The dataset will be owned and maintained by PH HC.

##  9.2 Standards and metadata

The dataset will follow the DICOM - Digital imaging and communications in
medicine standard [2].DICOM includes metadata in its specification.

##  9.3 Data sharing

The dataset will be disseminated to the consortium through the internal shared
SVN repository. It will be presented in SUPERCLOUD deliverables.

##  9.4 Archiving and presentation

Given the limited usability of the dataset, it will not be archived beyond the
project’s end.

#  Chapter 10 Dataset PEN-Measurements

##  10.1 Dataset description

PEN is at this time unsure of the generation of datasets. This will be updated
in a later revision of the document.

If generated, this data will probably be in the form of proof-of-concept
software applications, any generated input and output of these proof-of-
concepts, and performance statistics. It is quite possible there exists data
that PEN didn’t think is useful right now, but decide to include in the
project later.

The dataset will be owned and maintained by PEN.

##  10.2 Standards and metadata

Not applicable at this stage.

##  10.3 Data sharing

Dissemination of the dataset will be within the SUPERCLOUD consortium. Further
dissemination will be defined at a later stage.

##  10.4 Archiving and presentation

Not applicable at this stage.

#  Chapter 11 Dataset Maxdata-Demonstration

##  11.1 Dataset description

Maxdata will demonstrate a healthcare laboratory information system (LIS)
running on top of the SUPERCLOUD infrastructure. All data used in this use
case will be artificially generated data mimicking, in a representative way,
data records from Maxdata applications (e.g., results of random blood tests
with random results will be associated to virtual patients with fictional
names such as “Patient 1”, “Patient 2”, etc., and random birth dates).

The definition of the dataset will be further refined in a later version of
this document, after test-case definition is finalized therefore it will be
specified after M22 of the project.

The dataset will be owned and maintained by Maxdata.

##  11.2 Standards and metadata

The data will be made available using Comma-Separated Values (CSV) [1] files
given that the data size will be small (less than 100 Mbytes).

##  11.3 Data sharing

The dataset will be made available under the Open Database License (ODbL) [3].

The dataset will be made available after the project end.

##  11.4 Archiving and presentation

The dataset will be made available through the Maxdata (maxdata.pt) web site,
for at least three (3) years after the end of the project, at no additional
cost.

#  Chapter 12 Summary and Conclusion

The Data Management Plan of SUPERCLOUD describes the activity of the partners
related to datasets. It contains a summary of all the information available as
of July 1  st  , 2015. All partners intend to create data and make it
available within the consortium.

With respect to _dataset descriptions_ , most of the data manipulated by the
SUPERCLOUD project is related to measurements, result of test and validation
activities that will be conducted in experimental settings to validate the
SUPERCLOUD prototypes. Data collected will thus be related to measurements of
resource usage (use of compute, storage and/or network wherever applicable).
Supporting mock-up data will also be generated as a filler to feed into the
SUPERCLOUD prototypes, allowing meaningful experimentation. Given the target
experimentation on e-health applications, this mock-up data will mimic
e-health records and information.

With respect to _standards and metadata_ , the most prevalent form of data
format is CommaSeparated Values (CSV) [1], a textual description of data that
is extremely common and widely used in the database community. This format is
very easy to manipulate, is particularly adapted to sharing over SVN (as text
files are easily versioned) and is understood by a wide range of tools,
including all database engines, easing sharing and understanding. Other
formats mentioned include the software-based PCAP (packet capture) de-facto
standard and the DICOM [2] (Digital Imaging and Communication in Medecine)
standard, since SUPERCLOUD use cases are focusing on the e-health domain.

With respect to _sharing_ , several partners intend to share, at least in the
academic community, the datasets for further research and publication.
Academic research is the main objective of the data managed in the SUPERCLOUD
project.

With respect to _archiving and presentation_ , partners plan to use internal
resources and have them available at the time of writing. A few datasets will
be made available for 3 years after the end of the project.

Since it is very early in the project, this document only presents preliminary
proposals in terms of sharing, volume and archiving. The project is aware of
these aspects and will tackle them by updating the present document during the
development of the specifications of the experimentations. Therefore,
information in this document is subject to change.