#  1 ROLES AND RESPONSIBILITIES

Roles and responsibilities for maintaining and updating the Data Management
Plan (DMP) are linked to roles within VirtuWind. In case new personnel is
assigned to a relevant role, responsibilities with respect to the DMP are also
taken over. For details on the management roles and structure of VirtuWind see
Description of Action (DoA), Section 3.

The Data Management Plan is maintained by the Project Coordination Committee
(PCC). Reviews of the DMP are a regular agenda item of PCC meetings,
conference calls, and work package (WP) results will be checked with respect
to relevant information for the DMP. WP leads are responsible that results of
tasks within their work package are aligned with the definitions in the DMP.
WP leads are also responsible that the table in Section 3 of this DMP is
updated as soon as data according to the definition in Section 2 is created
within their WP (for details on the update procedure see Section 6.2). Updates
of the tables in Section 3 of the DMP are communicated from the Technical
Management Committee (TMC) to the PCC together with the minutes of the monthly
TMC calls (see also section on update procedures).

In order to ensure that this DMP is implemented and followed, reviews (by PCC
and/or TMC) of all kinds of project related documents (e.g., reports,
deliverables, publications) will include also a check for used data and the
proper documentation and use in-line with this DMP.

In case the contact person for data is leaving the project, the affiliation of
the original contact person will take over the responsibility and will assign
a new contact person.

#  2 EXPECTED DATA

VirtuWind is a three year project and will produce a number of technical
results relevant for SDN-based industrial networks. This includes data created
in lab experiments and real world tests of industrial networks (specifically
control networks of wind parks). Some data created and used in VirtuWind is
related to critical infrastructures and will not be publically accessible.
More details and reasoning will be given in the detailed description of the
specific data sets in Section 3.

Expected data will be created as:

  * raw data sets of network status data from lab experiments and real world data 

  

  * data derived from raw data, including related data processing algorithms 

  

  * technical and scientific publications (processed data) 

  

  * reports and deliverables (processed data) 

  

#  3 DATA FORMATS AND METADATA

##  3.1 Data Formats

Detailed descriptions of the expected information of each cell are given at
the end of this section.  
  
<table>  
<tr>  
<th>

**Data set reference**

</th>  
<th>

**Data set name**

</th>  
<th>

**Data Set Description**

</th>  
<th>

**Standards and metadata**

</th>  
<th>

**Data sharing**

</th>  
<th>

**Archiving and preservation (including storage and backup)**

</th>  
<th>

**Contact Person/ source of data**

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

VirtuWind01

</td>  
<td>

Test Data

</td>  
<td>

Test Data

</td>  
<td>

NA

</td>  
<td>

confidential

</td>  
<td>

\-

</td>  
<td>

PI, pi@virtuwind.eu

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

Test

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Table 1: Data Formats Note:**

**This table is linked to file “VirtuWind DMP.xlsx” -**

**_https://overseer1.erlm.siemens.de/repository/Document/downloadWithName/VirtuWind%20DMP.xlsx?reqCode=downloadWithName
&id=8 _ ** **_033083_ . **

**Insert text into the Excel file and update this linked table to make changes
visible!**

5

The following table gives a detailed description of the fields used in the
data formats table of Section 3.1.  
  
<table>  
<tr>  
<th>

Data set reference and name

</th>  
<th>

Identifier for the data set to be produced

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

Data set description

</td>  
<td>

Origin (in case it is collected), scale and to whom it could be useful, and
whether it underpins a scientific publication. Information on the existence
(or not) of similar data and the possibilities for integration and reuse.

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

Standards and metadata

</td>  
<td>

Reference to existing suitable standards of the discipline. If these do not
exist, an outline on how and what metadata will be created

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

Data sharing

</td>  
<td>

Gives dissemination level, where data is available (link), access procedures,
embargo periods (if any), outlines of technical mechanisms for dissemination
and necessary software and other tools for enabling re-use, and definition of
whether access will be widely open or restricted to specific groups.

Identification of the repository where data will be stored, if already
existing and identified, indicating in particular the type of repository
(institutional, standard repository for the discipline, etc.).

**In case the dataset cannot be shared, the reasons for this should be
mentioned here** (e.g. ethical, rules of personal data, intellectual property,
commercial, privacy-related, security-related).

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

Archiving and preservation (including storage and backup)

</td>  
<td>

In general, the procedure described in Section 5 will be applied. This cell
gives a data specific description of the procedures that will be put in place
for longterm preservation of the data (if required).

Indication of how long the data should be preserved, what is its approximated
end volume, what the associated costs are and how these are planned to be
covered (if required).

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

##  3.2 Metadata

VirtuWind plans to create and share data in relation to project deliverables
or publications. Deliverables and publications will give all relevant
information, including the meaning of data sets, the methods of data
acquisition/processing, as well as specific methods/algorithms for usage (if
required). Thus, deliverables and publication can be considered as main piece
of metadata for all data sets created within the project.

#  4 DATA SHARING AND ACCESS

Data and metadata, as well as project related documents (release version of
document – not raw format) with dissemination level “public” will be
accessible via the project website  _http://www.virtuwind.eu_ .  Registration
(free of charge) is required to get access. The dissemination level is
initially proposed by the corresponding author and will be approved by PCC
(details see Section 6.2).

As far as possible depending on the publishers’ policy pre-prints of the
publications will be made available open access via the project website, as
well as OpenAIRE. In case embargo periods (e.g., given by publishers) have to
be considered, open access will be given after the embargo period expires.
VirtuWind has also a budget item allocated for open access which will be used
to provide open access for publications of high importance/relevance. The
decision making procedure for such “selected” open access publication will is
given in the VirtuWind Dissemination Plan.

Software which is required for using published data is made available via the
project website  _http://www.virtuwind.eu_ according to the corresponding
license terms (e.g., open source licenses such as

EPL, …).

All modified GPL or similar copy left licensed code will be made publically
available in  _www.virtuwind.eu_ at project completion.

#  5 DATA ARCHIVING AND PRESERVATION

All project related documents (raw formats), deliverables, reports,
publications, data, and other artifacts will be stored in a repository
accessible during project duration for all partners. This repository is hosted
(with backup) by the Coordinator and the link is/was distributed at the first
consortium meeting. Access to the repository is given to registered persons
from project partners only. The folder structure of the repository is managed
by the coordinator and changes of the structure need to be coordinated with
the Coordinator. Corresponding partners will keep the above mentioned
repositories operational during the project life time. After project closure,
repositories will be maintained for at least one more year. After project
closure the administrating partner can change access policies (e.g.,
restricted access / access on demand) in order to keep maintenance costs at a
minimum.

  6. ANNEX: 

  

  

6.1 Important Links:

Current Version of the Data management plan (pdf):
_https://overseer1.erlm.siemens.de/repository/Document/downloadWithName/Deliverable%20D1.4.docx?req_
_Code=downloadWithName &id=8033085 _

Excel file for data formats and metadata (to be updated by WP leads and TMC):
_https://overseer1.erlm.siemens.de/repository/Document/downloadWithName/VirtuWind%20DMP.xlsx?reqCo_
_de=downloadWithName &id=8033083 _

##  6.2 Update procedure for Table 1

Trigger: data (see definition in Section 2) is produced within a task

  1. WP lead updates table with data format giving all required details for new data set including a proposal for the dissemination level. In case of questions, TMC/TM can assist. 

  

  2. WP lead informs TMC on update and TMC will create a new sub-version of the DMP (with updated table in Section 3). 

  

  3. TMC will inform PCC on the release of that new sub-version and PCC members can check the update on table 1 (incl. approval of dissemination level). In case PCC has objections, TM will be informed by PCC. TM then helps to clarify the open issues between PCC and WP lead. 

  

  

##  6.3 Update procedure of this deliverable (except Table 1)

Updates of this deliverable (not table 1 – for updating table 1 see section
above) can be triggered by TMC and/or PCC. All releases of this deliverable
are subject to PCC approval and will follow the decision making process
described in the Consortium Agreement.