Deliverable D8.8

EXECUTIVE SUMMARY

TRI-HP EU project is aiming to develop trigeneration integrated solutions that
combine heating, cooling and elec-tricity generation, based on heat pumps
running with natural refrigerants and using multiple renewable energysources.

During TRI-HP project, research data will be generated, collected and even
reused. These data will be made avail-able to the general public through
publication with open access, which is a mandate for H2020 projects. In
addition,TRI-HP participates in the Open Research Data Pilot (ORDP), which is
a program that aims to make data accessi-ble and available for anybody. It
applies primarily to the data needed to validate the results presented in
scientificpublications, but other data can also be provided by the
beneficiaries on a voluntary basis, as stated in their DataManagement Plans
(DMPs).

Having a DMP is mandatory for projects participating in ORDP. The purpose of
DMP is to facilitate good data  handling during and after the end of a
project, indicating which data to collect/process/generate, the method-ologies
and standards followed, which data will be shared/made open access, and how
data will be curated andpreserved.

In TRI-HP project, the following tasks/activities will generate data that need
to be handled:

•  •  ••••••••••••• Task 2.3. Barriers, hindrances and incentives towards the
social acceptance of TRI-HP systems.  Task 3.3. Laboratory testing at sample
scale (icephobic coatings).  Task 3.4. Laboratory testing of immersed coaxial
tubes with circulating water (icephobic coatings).Task 4.2. Testing and
optimizing of supercoolers.Task 4.4. Testing and optimizing a tri-partite gas
cooler.Task 4.6. Testing and optimizing a dual-source heat exchanger.Task 4.7.
Simplified TRNSYS modelling and validation (heat exchangers).Task 5.3.
Assembly of the prototypes and first experimental campaign.Task 5.4. Heat pump
upgrading and second experimental campaign.Task 5.6. TRNSYS modelling and
validation (heat pumps).Task 6.2. Experimental validation of the efficiency-
self-diagnosis system.Task 6.5. Preliminary validation of the advanced
management system in a simulation environment.Task 7.4. Whole system test and
optimization.Task 7.6. Model calibration and yearly simulation assessment.Task
7.7. Simulation scale-up, cost assessment and extrapolations to EU-28.

It has been decided that these data will be uploaded to the repository
currently used in the project, SWITCHdrive,to allow the access and
collaboration of the project partners. Data and metadata will be added and
preparedfollowing the guidelines indicated in this document.

In addition to this, the Norwegian Centre for Research Data (NSD) repository
will be used to comply with H2020  ORDP, making research data underlying
publications available. If additional public data not directly related to pub-
lications are uploaded to this repository, this will be indicated in future
updates of this DMP. Datasets will be givena persistent identifier DOI, with
relevant metadata and closely linked to 814888 grant number and TRI-HP
projectacronym. Data are licensed after signature of the "Archiving Agreement"
with NSD, in which the project partnerswill specify the access and reuse of
the datasets. Data security arrangements are defined for the SWITCHdriveand
NSD repositories. Ethical aspects affecting data sharing have been considered.

**DMP** Data Management Plan

**DOI** Digital Object Identifier

**ICT** Information and Communications Technology **IPR** Intellectual
Property Right

**NSD** Norwegian Centre for Research Data **ORDP** Open Research Data Pilot

##  1 INTRODUCTION

###  1.1 DATA MANAGEMENT PLAN

During TRI-HP project, research data will be generated, collected and even
reused. These data will be made avail-  able to the general public through
publication with open access, which is a mandate for H2020 projects. In
addition,TRI-HP participates in the ORDP, which is a program that aims to make
data accessible and available for anybody.It applies primarily to the data
needed to validate the results presented in scientific publications. Other
data canbe provided by the beneficiaries on a voluntary basis, as stated in
their DMPs.

Having a DMP is mandatory for projects participating in ORDP. The purpose of
DMP is to facilitate good data  handling during and after the end of a
project, indicating which data to collect/process/generate, the method-ologies
and standards followed, which data will be shared/made open access, and how
data will be curated andpreserved.

###  1.2 STRUCTURE OF THE DOCUMENT

The document is structured as follows:

•  •  •••• Section 2 states the data summary and the procedures to upload data
to the different repositories.  Section 3 describes the main principles for
FAIR data management in TRI-HP and how it will comply with  the H2020 Open
Access Mandate.  Section 4 describes the allocation of resources to make this
open access to publications and data possible.Section 5 gives a detailed
description of data security arrangements.Section 6 deals with ethical
aspects, if any, connected to data management in TRI-HP project.Section 7
deals with other aspects that do not fit the previous sections.

###  1.3 UPDATES OF THE DATA MANAGEMENT PLAN

Projects evolve while they progress and, thus, it is not realistic to have a
fully detailed DMP with all the answers andinformation clear in the first
version, which in TRI-HP project is due in month 7. A DMP is seen as a living
document,in which information is refined in subsequent updates as the project
progresses. The following updates to the DMPare foreseen in TRI-HP project’s
Grant Agreement (814888 project number):

•• D8.9. Data Management Plan DMP (update M24). Due by M24 (February 28,
2021).D8.10. Data Management Plan DMP (update M48). Due by M48 (February 28,
2023).

##  2 DATA SUMMARY 2.1 GENERAL ASPECTS

The objective of TRI-HP Project is to develop trigeneration integrated
solutions that combine heating, cooling and  electricity generation, based on
heat pumps running with natural refrigerants and using multiple renewable
energy  sources. In order to fulfill this ambitious objective, the different
partners in the consortium will work solving smallerchallenges. Work in all
these different aspects/topics will comprise experimental and/or simulation
campaigns. has been chosen.The results from these activities will be either
confidential, for internal use in the project, or public and published  with
open access to the general public. As part of the ORDP, in TRI-HP we will make
data linked to the publications  available (to validate the results from the
publication). Additional data not linked directly to publications will
beincluded only if the partners involved in the specific task consider it
convenient. For this purpose, NSD1 repository

TRI-HP consortium foresees various types of data: results of experimental
campaigns and simulations at com-  ponent and system level,
images/pictures/video from tests, answers from interviews, etc. The formats of
thesedata will be also diverse.

A particular case is that of the heat pump models developed within WP 5 and
the results obtained with them, which  are confidential. However, the partners
involved in this modelling, TECNALIA and NTNU, will use an approach basedon
the use of Gitlab and Sourcetree to handle and develop them safely and
collaboratively.

###  2.2 DATA SUSCEPTIBLE TO OPEN ACCESS MANDATE

The data used in TRI-HP project will be new data and no re-use of data is
planned. The origin of these data will  be different tasks, as indicated in
Table 2.1. This table includes a short description of the data expected, kind
ofdata and probable formats (using as much as possible the preferred file
formats according to the NSD and shownin Table 2.2), which deliverables are
associated with the task and if they are linked to any publication. It is
earlyto define the size of the datasets, so this topic will be included in a
future update. This list is preliminary and willbe completed and changed with
the progress of the project.

The data resulting from the activities in TRI-HP project will be useful for
the following groups:

•••• Researchers: other researchers will have the possibility to use data for
other studies, comparisons, valida-tions, etc.Manufacturers: heat pump
manufacturers, even competitors, will benefit from TRI-HP’s results and
conclu-sions, being a benchmark for their systems and assisting them with
strategic decisions concerning theirbusiness, products, etc.European
regulators: some of the results from TRI-HP could be useful for European
regulators in order tomake decisions concerning which technologies to support,
new project calls to launch, etc.Final users: even if it is unlikely that the
data from this project could be relevant for the average final user,some users
could understand the benefits of installing heat pumps systems, if the outcome
of the projectis inline with their goals.

~~1NSD - Norwegian Centre for Research Data is a natio~~ to research data, and
to improve opportunities for empirical research through a wide range of
information and support services. NSD’score value is that research data is a
collective good that should be shared. For more informationnal archive and
center for research data, that aims to ensure open and easy access  www.nsd.no

2.2. Data susceptible to Open Access Mandate

**Table 2.1:** Research data to be generated in TRI-HP project.

**Task Delivarable Short name/description Kind of data and formats
Publication? Comments**  
  
<table>  
<tr>  
<td>

Task 2.3

</td>  
<td>

D2.2

</td>  
<td>

Surveys on barriers towards TRI-HP systems

</td>  
<td>

Statistical (.xls)

</td>  
<td>

Yes

</td>  
<td>

No personal data will be handled.

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

Task 3.3/3.4

</td>  
<td>

D3.5

</td>  
<td>

Test results of icephobic coatings

</td>  
<td>

Test data (.xls, .csv)Images (–)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 4.2

</td>  
<td>

D4.6

</td>  
<td>

Test results of supercoolers

</td>  
<td>

Test data (.xls, .csv)Images (–)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 4.4

</td>  
<td>

D4.3

</td>  
<td>

Test results of tri-partite gas cooler

</td>  
<td>

Test data (.xls, .csv)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 4.6

</td>  
<td>

D4.4

</td>  
<td>

Test results dual-source heat exchanger

</td>  
<td>

Test data (.xls, .csv)Images (–)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 4.7

</td>  
<td>

D4.7

</td>  
<td>

Validation TRNSYS heat exchanger models

</td>  
<td>

Test data (.xls, .csv)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 5.3

</td>  
<td>

D5.5

</td>  
<td>

Test results heat pump prototypes

</td>  
<td>

Test data (.xls, .csv)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 5.4

</td>  
<td>

D5.6

</td>  
<td>

Test results heat pump prototypes refined

</td>  
<td>

Test data (.xls, .csv)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 5.6

</td>  
<td>

D5.8

</td>  
<td>

Validation TRNSYS heat-pump models

</td>  
<td>

Test data (.xls, .csv)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 6.2

</td>  
<td>

D6.3

</td>  
<td>

Validation self-diagnosis efficiency system

</td>  
<td>

Data (.xls, .csv)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 6.5

</td>  
<td>

D6.5

</td>  
<td>

Validation AEM system through simulations

</td>  
<td>

Data (.xls, .csv)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 7.4

</td>  
<td>

D7.4

</td>  
<td>

System test results R290 systems

</td>  
<td>

Test data (.xls, .csv)

</td>  
<td>

Partially via D7.9

</td>  
<td>

–

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

Task 7.4

</td>  
<td>

D7.8

</td>  
<td>

System test results R744 system

</td>  
<td>

Test data (.xls, .csv)

</td>  
<td>

Partially via D7.9

</td>  
<td>

–

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

Task 7.6

</td>  
<td>

D7.9

</td>  
<td>

Energy performance/cost competitiveness of systems

</td>  
<td>

Data (.xls, .csv)

</td>  
<td>

Yes

</td>  
<td>

–

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

Task 7.7

</td>  
<td>

D7.10

</td>  
<td>

Benefits TRI-HP systems in Europe

</td>  
<td>

Data (.xls, .csv)

</td>  
<td>

Yes

</td>  
<td>

–

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

2.2. Data susceptible to Open Access Mandate

**Table 2.2:** Type of data and preferred file formats by NSD. Formats most
likely to be used are bolded.  
  
<table>  
<tr>  
<td>

Textual documents

</td>  
<td>

**• •  ** ••OpenDocument-text (.odt)Rich text format (.rtf) **PDF/A (.pdf) MS
Word (.doc, .docx)  **

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

Plain text

</td>  
<td>

•Unicode-text (.txt)

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

Spreadsheets

</td>  
<td>

•  **•••** •  PDF/A (.pdf)  OpenDocument-spreadsheet (.ods) **Comma- and
semicolon-separated values (.csv)Tab-separated values (.txt)Excel file format
(.xls, .xlsx)**

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

Database

</td>  
<td>

••••Comma- and semicolon-separated values (.csv)Tab-separated values (.txt)MS
Access (.mdb, .accdb)ANSI SQL (.sql)

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

Tabular/statistical data

</td>  
<td>

••••PASW/SSPSS (.sav, .por)STATA (.dta)SAS (.sas)R (.R, .Rdata, ...)

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

Image

</td>  
<td>

**• •  ** • **•** Scaleable vector graphics (.svg) **JPEG (.jpg, .jpeg) TIFF
(.tif, .tiff)  PDF/A (.pdf) **

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

Video

</td>  
<td>

• **••** •MPEG-2 (.mpg, .mpeg)QuickTime (.mov) **MPEG-4 H264 (.mp4)Lossless
AVI (.avi)**

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

Audio

</td>  
<td>

••WAVE (.wav)MP3 AAC (.mp3)

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

Geospatial information

</td>  
<td>

•ESRI shapefiler (.shp and similar formats)

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

####  **Type of data Preferred file formats**  

2.3. Upload instructions

#####  2.3 UPLOAD INSTRUCTIONS 2.3.1 SWITCHdrive repository

been established for research data that shall be made available for the
general public and will be uploaded in the  NSD repository (see next sub-
section). In addition, project partners are encouraged to upload their
research data,including those not associated with publications and even
confidential within the consortium, to the correspondingWP-folders in order to
prevent any loss of valuable information/data.SWITCHdrive has been established
by the project coordinator (SPF-HSR) as repository to allow for safe sharingof
information and data among the partners in the project. A dedicated folder, _
ResearchData_OpenAccess  _ , has

######  2.3.2 NSD repository

It is important to plan archiving in advance, since research data that shall
be made accessible (e.g. linked to pub-  lications) latest on article
publication. Each partner is responsible for uploading the datasets
created/collectedby them.need to create an NSD profile, ask for access to the
project (contact Ángel Álvarez Pardiñas through e-mailfied cases, project
partners could transfer to NTNU the task of archiving their research data in
the repository. Inany case, these data shall be first available in the
SWITCHdrive.  angel.a.pardinas@ntnu.no  If needed, NTNU - leader of Task 8.4
on data management, will assist the partners.), and upload the data to the
repository. As an alternative and just in justiPartners-

To create an account in NSD.

2341\. Choose the log in option (Figure 2.1). Unless access with FEIDE
(exclusive for Norway) or eduGAIN is pos. Accesssible, use Login with Google
(create an account if needed).  https://minside.nsd.no/  . -

65\. If Google log in is selected, Write e-mail and password.. If the log in
information is correct, the user will access his/her profile, which should be
similar to that in. NTNU, as responsible of the DMP, has created a project
with the name "TRI-HP. Trigeneration systems. An e-mail will be sent to the
user inbox with a hyperlink to open the project and add it to the user’s
profile.Figure 2.2.based on heat pumps with natural refrigerants and multiple
renewable sources". Ask NTNU (  pardinas@ntnu.no  ) to share access to the
project.  angel.a.

NSD suggests the following steps to archive data.

1\. Prepare data

d) Language? English (and Norwegian).b) Are there any personal data? This will
not apply to TRI-HP project.g) Is the data quantitative? Variable names and
descriptions must be understandable, i.e. documentationa) Is it the final
version?  e) Is the dataset in one of the preferred data formats (Table 2.2)?
c) Relevant documentation/metadata is included? Clarifications on this issue
are included in sectionf) More than one file? Overview of files must be
enclosed with the description of the individual files, i.e.3.1.4.documentation
at dataset level (section 3.1.4).at variable level (section 3.1.4).

2.3. Upload instructions

**Figure2.1:**

LoginalternativestoNSD

.

**Figure 2.2:** User website in NSD.

h) Are there transcribed interviews? This will not apply to TRI-HP project.

23\. Deposit data files, using the NSD website created for TRI-HP project,
which can be accessed as explained. Sign archiving agreement. The user
receives, within two to three working days, an e-mail confirming recepabove. A
form shall be filled out to capture the most important information about the
project and data.tion of the data and an archiving agreement. This agreement
defines access conditions for the data. Oncesigned and returned to NSD, they
start preparing the data and metadata. Confirmation is sent by NSD whenthe
data is available. -

###  3 FAIR DATA

TRI-HP project works according to the principles of FAIR data (Findable,
Accessible, Interoperable and Reusable).The project aims to maximize access to
the research data generated in the project so that it can be re-used.
Thisapplies to data intended to be public and used in publications. At the
same time, there are datasets that shouldbe kept confidential for commercial
and Intellectual Property Right (IPR) reasons. Details are given in Table 2.1
inSection 2.2.

####  3.1 MAKING DATA FINDABLE, INCLUDING PROVISIONS FOR METADATA

**3.1.1 TRI-HP and NSD repository**

TRI-HP will use the TRI-HP project website created in NSD repository as the
main tool to comply with the H2020Open Access Mandate and with TRI-HP’s
participation in ORDP program. All scientific articles/papers and
publicdatasets will be uploaded to this community in NSD, named according to a
convention, with Digital Object Identifier(DOI) and Metadata (see subsequent
subsections).

#####  3.1.2 Naming convention

Data related to publications or deliverables will be named using the following
naming conventions:

_H2020_AcronymProject_DeliverableNumber_DescriptiveTextDataset_UniqueDatasetNumber_Version_

_H2020_AcronymProject_PublicationNumber_DescriptiveTextDataset_UniqueDatasetNumber_Version_

**Example:** H2020_TRI-HP_D4.4_TriPartiteGasCooler_HXs1_1_v  1

**3.1.3 Digital Object Identifiers (DOI)**

DOI’s for all datasets will be reserved and assigned with the DOI
functionality provided by NSD. DOI versioning willbe used to assign unique
identifiers to updated versions of the data records.

#####  3.1.4 Metadata

the aim of the study, who is responsible for the project and the methods
applied. Second, atan overview of the different files and how they relate to
each other. Third, atunderstandable to outsiders.As recommended by NSD1,
metadata should be provided at three different levels. First, at **variable
levelproject level** , in order to make data **dataset level** , describing,
with

_Project level_ The metadata at project level shall include
(examples/explanations are given for some categories):

•••• Title: H2020–TRI-HP–Deliverable/Publication–Descriptivename.Institution:
institution responsible for the data.Responsible: person responsible within
the institution.Copyright.

_3\. FAIR data 3.2. Making data openly accessible_

••••••• Abstract: short description of the data collected, the purpose behind
these data, etc.Keywords: help to maximize the possibilities for re-use of the
data.Dates of collection: Start: YYYY-MM-DD. End: YYYY-MM-DD.Kind of data:
survey, tests (results, images), simulations, etc.Procedures.Access: who
should be given access, when is data made available, etc.Other comments.

_Dataset level_ The metadata at dataset level shall include:

• Name: shall follow the following structure.

••••• Format: .pdf, .xls, .csv, .jpg, etc.Size (optional).Date created: shall
correspond to the date in the name.Date modified (if any).Short description of
information in the file. _TRI-HP_TaskNumber_Date(YY-MM-
DD)_UniqueDatasetNumber_Version_

_Variable level_ This applies to structured and quantitative data. The names
given to the variables shall be as self-explaining as  possible, so that it is
possible to minimize the information that needs to be given so that outsiders
understand thedata. Ideally, the metadata at variable level for a certain
dataset could include:

••••• Variable group.Variable name.Description.Units: SI units are
preferred.Values: range of values.

####  3.2 MAKING DATA OPENLY ACCESSIBLE

The H2020 Open Access Mandate aims to make research data generated by H2020
projects accessible with as  few restrictions as possible, but also accepts
protecting sensitive data due to commercial or security reasons.

All public datasets (and associated metadata and other documentation)
underlying publications will be uploadedto NSD repository and made open, free
of charge, latest when the publication is available. Other datasets with dis-
semination level "Public" will also be made open through the same repository.
Publications and related datasetswill be linked through persistent DOIs.
Datasets with dissemination level "Confidential" will not be shared. Infor-
mation on the public datasets was included in Table 2.1 in Section 2.2

It is expected that most of the data will be accessible using usual software
tools (.pdf readers, text editors, spread-sheet editors and others). In case
any special software is needed, it will be detailed in the corresponding Meta-
data.

  3. _FAIR data 3.3. Making data interoperable_

  

  

3.3 MAKING DATA INTEROPERABLE

Data within TRI-HP project are intended to be re-used by other researchers,
institutions, organizations, etc. Thus,the formats chosen for the datasets
shared are widely used and in most cases accessible using open
softwareapplications. Vocabulary will be kept as standardized as possible, and
further explanations will be given in caseuncommon terminology is used.

####  3.4 INCREASE DATA RE-USE (THROUGH CLARIFYING LICENSES)

TRI-HP project will enable third parties to access, mine, exploit, reproduce
and disseminate (free of charge forany user) all public datasets. The use for
the datasets is specified in the "Archiving Agreement" supplied by NSD,which
is signed by the owner of the dataset after their archive. The information
will be documented as "DepositRequirement", "Citation Requirement" and
"Restrictions" for further use. NSD offers the possibility to have somedata
not freely accessible, but these data can be order through a form, with an
access later and confidentialityagreement to be signed. However, this will not
be the case with the public data within TRI-HP.

#####  3.4.1 Availability of the TRI-HP research datasets

For data published in scientific journals, the underlying data will be made
available no later than by journal publi-  cation and linked to this
publication. Data associated with public deliverables will be shared once the
deliverablehas been approved by the European Commission. is to have data for
"unforeseeable future".Public data will remain archived and re-usable for at
least 5 to 10 years in the NSD repository2. NSD’s perspective

~~2Minimum stated in the Core Trust Seal requirements~~

#  4 ALLOCATION OF RESOURCES

TRI-HP uses standard tools and free of charge repository. The costs of data
management activities are limited toproject management costs and will be
covered by the project grant. TRI-HP publications in Open Access journalsor
with Open Access agreements will also be covered by the grant. The following
amounts have been allocated bythe different partners for this purpuse:

•

••••• ISOE: 2000NTNU: 3000UASKA: 3000IREC: 3000  SPF-HSR: 3000  TECNALIA:
3000€€€.. €. .  €.  €.

NTNU is responsible for TRI-HP’s data management, which is associated with
Task 8.4 from WP 8 - Disseminationand Exploitation. Task 8.4 is lead by NTNU.

###  5 DATA SECURITY

The aspects concerning security of the research data generated/used in TRI-HP
project are covered in this chap-ter. 5.1 ACTIVE PROJECT - UTILIZATION OF
SWITCHDRIVE REPOSITORY

At the beginning of TRI-HP project, a SWITCHdrive repository was established
by SPF-HSR to allow for safe sharing  of information and data among the
partners in the project. This repository will be active during the period in
whichthe project is active and beyond, namely until at least one year after
the project ends. Files from SWITCHdrivefolder that have been deleted are not
removed immediately, but moved to the folder "Deleted-files" from wherethey
can be easily restored, if needed. Deleted files are stored in this folder for
90 days and only after that theywill be permanently deleted. SWITCHdrive has a
backup system that can be used to restore the whole system incase of disaster,
but this cannot be claimed for individual restore requests. Thus, the HSR-SPF
network drive andin addition a back-up on an external drive will be used.

Some safety facts about SWITCHdrive are that:

••• all data are stored in SWITCH servers in Switzerland,there is full
compliance with Swiss data protection regulations,and there is no data and
metadata exchange with other Office companies.

A dedicated folder,  able for the general public and will be uploaded in the
NSD repository. In addition, project partners are encouragedto upload their
research data, including those not associated with publications and even
confidential for the con-sortium, to the corresponding WP-folders in order to
prevent any loss of valuable information/data.  _ResearchData_OpenAccess_ ,
has been established for research data that shall be made avail-

####  5.2 REPOSITORY \- DATA SECURITY AS SPECIFIED FOR NSD

TRI-HP project has chosen NSD’s repository. All scientific publications,
public deliverables, and public researchdatasets will be uploaded to NSD
repository and made accessible for everyone.

Some facts concerning information security and maintenance are explained in
NSD’s website. These facts aresummarised below.

• The purpose of NSD’s information security is to secure the data’s
confidentiality, integrity and accessibility.

  * Confidentiality: data are not accessible to unauthorised persons/systems. 

  

  * Integrity: data are not changed or destroyed by unauthorised means. **–** Accessibility: data resources are available for use when required. 

  

••• Access control: NSD keeps an updated overview of who has access to
relevant Information and Communi-  cations Technology (ICT) systems.
Training: all NSD employees/users sign the necessary declarations and are
given an introduction to NSD’ssecurity guidelines and the consequences of
breaching the guidelines before they are granted access to anactivated user ID
for NSD’s ICT systems.Declaration of secrecy: everyone with access to personal
data and/or IT systems that NSD is responsiblefor are required to sign the
company’s declaration of secrecy (new one every third year).

_5\. Data security 5.2. Repository - Data security as specified for NSD_

•••• Backups are made in accordance with the requirements of accessibility.
Storage media for the backupare labelled to facilitate finding and recovering
it. NSD keeps backup copies separate from the operatingequipment/computer room
in a locked and fireproof cabinet (external location). To avoid physical
wearand tear on tapes/disks/storage media, incremental backups are replaced at
expedient intervals. Backupcassettes are used for five weeks. After each
period, a complete backup copy is transferred to a secureexternal location.NSD
shall document and store all new datasets using Nesstar Publisherif not
possible in Nesstar. Every other year, NSD reviews the data collection to
check and, if relevant, updatethe file formats.Repository lifetime: the
minimum repository lifetime is 5 to 10 years, but NSD foresees repository for
the"unforeseeable future".CoreTrustSeal: NSD is certified as a credible and
reliable archive of research data and awarded CoreTrust-Seal. NSD meets
requirements connected to: 1 or in the most compatible format

**–––––––––** safe operations and continuous access to archived data in a
long-term perspective,disciplinary and ethical standards,sufficient funding
and expertise,information security,metadata to provide retrieval and
reuse,workflows from data submission to data dissemination,citation,licensing
andtechnical infrastructure.

~~1Nesstar publisher is an advanced data management~~ tool owned and developed
by NSD

#  6 ETHICAL ASPECTS

Currently, no ethical or legal issues that can have an impact on data sharing
have been identified. Ethical aspectsconnected to research data generated by
the project will be considered as the work proceeds.

Use and storage of e-mail addresses in TRI-HP’s SWITCHdrive repository:  An
e-mail address is by definition personal information and covered in GDPR
participants are stored in the SWITCHdrive repository. Only the project
participants invited have access. The e-mail address is a prerequisite to
access the project’s working area. By accepting the invitation to
SWITCHdrive,participants consent the use and storage of their e-mail
addresses. E-mail addresses will be deleted when accessto the project area is
no longer needed.  1\. The e-mail addresses of project

SPF-HSR and SWITCH (the organization handling the repository) comply with the
General Data Protection Regula-tion.

#  7 OTHER ISSUES

No other issues or aspects concerning data management are foreseen currently.

~~1The General Data Protection Regulation (EU) 2016/6~~ 79 (GDPR)

This project has received funding from the European Union’s Horizon 2020
research and innovation programme under grant agreement N. 814888\.  The sole
responsibility for the content of this paper lies with the authors.It does not
necessarily reflect the opinion of the European Commission (EC).The EC is not
responsible for any use that may be made of the informationit contains.

©TRI-HP PROJECT. All rights reserved.

Any duplication or use of objects such as diagrams in other electronic
orprinted publications is not permitted without the author’s agreement.