#  Executive Summary

This deliverable describes the research datasets that will be produced within
CHEOPS and if and how they will be made available. **Need for the
Deliverable**

It is in the interest of society that best use is made from datasets obtained
with the help of public funding. To this end, consideration of data format and
post-project storage and curation should be made at an early stage.
**Objectives of the Deliverable**

With the help of this deliverable it shall be ensured that as much research
data as possible is ‘FAIR’:

  * **F** indable 

  

  * **A** ccessible 

  

  * **I** nteroperable to specific quality standards 

  

  * **R** e-useable beyond the original purpose for which it was collected 

  

##  Outcomes

All WP leaders have defined and described the most important datasets
generated within their work package.

##  Next steps

The DMP is not a fixed document, but rather represents the current status of
reflection within the consortium about the data that will be produced and the
DMP will evolve during the lifespan of the project.

..

#  1 Introduction

In Horizon 2020, the EC is implementing a pilot action on open access to
research data. Participation in the pilot is voluntary, but participating
projects are required to develop a Data Management Plan (DMP), in which they
specify which data will be open. The CHEOPS consortium has chosen not to
participate in the pilot action, but nevertheless has promised to deliver a
DMP as part of WP6.

##  1.1 Objectives

The purpose of the DMP is to provide an analysis of the main elements of the
data management policy that will be used by the CHEOPS consortium with regard
to all the datasets that will be generated by the project. The DMP is not a
fixed document, but rather represents the current status of reflection within
the consortium about the data that will be produced and the DMP will evolve
during the lifespan of the project. According to the  _EC Guidelines on Data
Management in Horizon_ _2020_ 1  , scientific research data should be ‘FAIR’:

  * **_F_ indable ** : Are the data produced and/or used in the project discoverable with metadata, identifiable and locatable by means of a standard identification mechanism (e.g. persistent and unique identifiers such as Digital Object Identifiers)? 

  

  * **_A_ ccessible ** : Are the data and associated software produced and/or used in the project accessible and in what modalities, scope, licenses (e.g. licencing framework for research and education, embargo periods, commercial exploitation, etc.)? 

  

  * **_I_ nteroperable ** : Are the data produced and/or used in the project interoperable, that is allowing data exchange and re-use between researchers, institutions, organisations, countries, etc. (i.e. adhering to standards for formats, as much as possible compliant with available [open] software applications, and in particular facilitating re-combinations with different datasets from different origins)? 

  

  * **Re-usable** : Are the data produced and/or used in the project useable by third parties, in particular after the end of the project? 

  

According to the EC guidelines the DMP should describe how the FAIR principles
will be implemented. In addition, the DMP should also address the allocation
of resources to data management, data security, ethical aspects and any
additional procedures for data management that are made use of.

##  1.2 Structure

The DMP is organised as follows: After a section with general considerations
that are shared for all datasets (Section 2), the 5 datasets are described in
Sections 3 to 7 and all questions listed in the DMP template of the  _EC
Guidelines on Data Management in Horizon 2020_ 1  are addressed for each
dataset.

#  2 General considerations (applying to all datasets)

##  2.1 Data archiving and preservation

CHEOPS intends to deposit the data selected for sharing in one of the EU
supported open access data repositories such as OpenAIRE  _www.openaire.eu_ or
ZENODO  _https://zenodo.org_ .  The ultimate decision on the repository and
the modalities will be taken at the time the datasets are available.

##  2.2 Metadata

It is planned to make the metadata available through the same repository the
data will be stored in. The metadata will use standard format as much as
possible. ZENODO for instance stores all metadata internally in the MARC
(MAchine-Readable Cataloging) format and allows export into several standard
formats such as MARCXML, Dublin Core and DataCite Metadata Schema according to
OpenAire Guidelines.

The metadata will include among others:

  * The terms “European Union (EU)” and “Horizon 2020”, “perovskite”, “photovoltaics” and 

  

“solar cell”

  * The project acronym “CHEOPS” as well as the grant number “653296”  The publication date 

  

##  2.3 Making data findable

Typically, the organisations hosting a data repository (e.g. ZENODO) are
assigning a unique Digital Object Identifier.

The CHEOPS project website will be kept online for at least 3 years after the
end of the project and will contain references to the datasets in the open
access repositories.

##  2.4 Licensing and re-use of data

It is the intention of the CHEOPS consortium to allow the widest possible re-
use of data. Creative Commons licensing is considered for some datasets, but
currently no definitive decision has been taken. Apart from the restrictions
of the Creative Commons license chosen (if this is the case) no other
restrictions for re-use of data will apply.

##  2.5 Time of making datasets available

As a general rule, datasets will not be released before the publication date
of the scientific paper in which the data are reported the first time. It is
the intention of the CHEOPS consortium to make the datasets publicly available
as early as possible after the publication date, but potential restrictions or
embargo periods of the scientific journal will have to be respected. CHEOPS WP
leaders will jointly review the status of actual upload of the datasets at the
occasion of the 6-monthly meetings of the Executive Board and the Annual
Meetings.

##  2.6 Data security

Regular backup schemes are usually in place for the data repositories and
CHEOPS does not have to take care of this.

There is no sensitive data such as personal or health data collected or
processed in CHEOPS and therefore no specific requirements apply.

##  2.7 Ethical aspects

No ethical aspects need to be considered for the datasets concerned. This has
been confirmed by the comment of the EC Project Officer in the request for
revision of this deliverable.

##  2.8 Updates of the Data Management Plan

The DMP is not a fixed document, but rather represents the current status of
reflection within the consortium about the data that will be produced and the
DMP will evolve during the lifespan of the project. The next updated version
of the DMP will be produced in Month 18. A further update is scheduled for
Month 30, to allow sufficient time in the final 6 months of the project to
implement the plan and store the research data in the repository.

#  3 Dataset on perovskite single junction PV devices (from WP1) 3.1 Data
summary  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**State the purpose of the data collection / generation**

</td>  
<td>

In the framework of WP1, data will be produced on typical structures (for 2
polarities) of the used perovskite single junction devices with typical
structure composition and thicknesses of the individual layers. Information
(non-confidential) on process conditions of the different layers will also be
documented. Eventually, information on the achieved device performances will
also be measured, along with descriptions of the procedure that has been used
to measure the data.

The purpose of the data generation is to allow comparison between perovskite
PV devices with different structures to ultimately identify the best
combination of processing techniques and materials.

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

**Explain the relation to the objectives of the project**

</td>  
<td>

The data is produced as part of the process to reach the project’s technical
objective 1 (TO1 in the DoA) of upscaling the perovskite PV technology.

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

**Specify the types and formats of data generated / collected**

</td>  
<td>

The data on device structure and process conditions of the different layers
will be descriptive, while the measured device performances will each consist
of a combination of:

  1. Name of the parameter measured 

  

  2. Numeric value measured 

  

  3. Physical unit 

  

  

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

**Specify the origin of the data**

</td>  
<td>

The data will be documented or measured by the CHEOPS partners in WP1.

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

**State the expected size of the data (if known)**

</td>  
<td>

Not known yet.

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

**Outline the data utility: To whom it will be useful**

</td>  
<td>

These data could be useful for people working in the field of perovskite based
PV and in general to the PV community.

Similar data already exist in several published works from different groups.
Our dataset could be compared to this already existing information.

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

##  3.2 FAIR Data

###  3.2.1 Making data findable, including provisions for metadata  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Outline the discoverability of data (metadata provision)**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**Outline the identifiability of data and refer to standard identification
mechanisms. Do you make use of persistent unique identifiers such as Digital
Object Identifiers?**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**Outline naming conventions used**

</td>  
<td>

To be defined at a later stage.

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

**Outline the approach towards search keyword**

</td>  
<td>

_See general considerations and list of default keywords in Section 2.2
above._

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

**Outline the approach for clear versioning**

</td>  
<td>

To be defined at a later stage.

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

**Specify standards for metadata creation (if any). If there are no standards
in your discipline describe what type of metadata will be created and how.**

</td>  
<td>

This kind of datasets can typically be found in scientific publications but
there exist no standards for these publications. Very recently, in October
2015, the “Nature Materials” journal has made and attempt at harmonisation by
developing a checklist for photovoltaic research:
_http://www.nature.com/nmat/journal/v14/n11/full/nmat4473.html_

CHEOPS will consider this checklist and monitor its further development, as it
might help to create a metadata set by allowing proper comparison between the
different published results.

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

###  3.2.2 Making data openly accessible  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify which data will be made openly available. If some data is kept
closed provide rationale for doing so**

</td>  
<td>

In the framework of CHEOPS, the information on device performances, stability,
measurement protocols and device structures will be shared

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

**Specify how the data will be made available**

</td>  
<td>

Currently data are shared via scientific communication, either in the form of
scientific papers or at conferences via oral or visual presentations. While
the peer-reviewed publications will be made available as open access, it is
the intention to also provide the underlying data itself by storing it in an
open repository ( _see Section 2.1 above_ ).

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

**Specify what methods or software tools are needed to access the data. Is
documentation about the software needed to access the data included? Is it
possible to include the relevant software (e.g. in open source code)?**

</th>  
<th>

No special software is needed to access the data.

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

**Specify where the data and associated metadata, documentation and code are
deposited.**

</td>  
<td>

_See general considerations outlined in Section 2.1 above._

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

**Specify how access will be provided in case there are any restrictions**

</td>  
<td>

The data that will be made available will be available without restrictions

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

###  3.2.3 Making data interoperable  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Assess the interoperability of your data. Specify what data and metadata
vocabularies, standards or methodologies you will follow to facilitate
interoperability.**

</td>  
<td>

_See last point under Section 3.2.1 above._

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

**Specify whether you will be using standard vocabulary for all data types
present in your data set, to allow interdisciplinary interoperability? If not,
will you provide mapping to more commonly used ontologies?**

</td>  
<td>

No standard vocabulary currently available.

_Please also see the comments made under Section 3.2.1 above_ .

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

###  3.2.4 Increase data re-use (through clarifying licenses)  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify how the data will be licensed to permit the widest re-use possible**

</td>  
<td>

_See general considerations under Section 2.4 above._

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

**Specify when the data will be made available for re-use. If applicable,
specify why and for what period a data**

</td>  
<td>

_See general considerations under Section 2.5 above._

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

**embargo is needed.**

</td>  
<td>

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

**Specify whether the data produced and/or used in the project is useable by
third parties, in particular after the end of the project? If the reuse of
some data is restricted, explain why.**

</td>  
<td>

_See general considerations under Section 2.4 above._

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

**Describe the data quality assurance process**

</td>  
<td>

For use within CHEOPS, a standardised sample size and geometry as well as
standard operating procedures (SOP) for sample shipment and sample measurement
has been agreed upon. Following these SOPs will be mandatory for all
measurements carried out during the project. The SOPs were made available to
the CHEOPS consortium in deliverable D6.3, the “Quality and Best Practice
Manual” and will be made publicly available.

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

**Specify the length of time for which the data will remain re-useable.**

</td>  
<td>

The data made available will remain re-useable for an unrestricted duration.

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

##  3.3 Allocation of resources  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Estimate the costs for making your data FAIR. Describe how you intend to
cover these costs**

</td>  
<td>

The small amount of staff costs required for inserting the data into the
repository will be covered from the CHEOPS project budget.

The hosting of the data in the repository is typically free (e.g. ZENODO).

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

**Clearly identify responsibilities for data management in your project**

</td>  
<td>

General decisions (e.g. on licences or repositories) will be taken by the
Executive Board. For actual implementation of data management in each WP, the
WP leaders are responsible.

For this dataset, WP1 leader CSEM is in charge.

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

**Describe costs and potential value of long term preservation**

</td>  
<td>

There will be no long-term costs for CHEOPS partners for maintaining the data
repository.

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

##  3.4 Data security  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Address data recovery as well as secure storage and transfer of sensitive
data**

</td>  
<td>

_See general considerations in Section 2.6._

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

##  3.5 Ethical aspects  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**To be covered in the context of the ethics review, ethics section of DoA and
ethics deliverables. Include references and related technical aspects if not
covered by the former**

</td>  
<td>

Not applicable. _See also general consideration in Section 2.7_

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

##  3.6 Other  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Refer to other national / funder / sectorial / departmental procedures for**

**data management that you are using (if any)**

</td>  
<td>

Not applicable.

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

#  4 Dataset on stability testing and encapsulation methods of Perovskite PV
devices (from WP2) 4.1 Data summary  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**State the purpose of the data collection / generation**

</td>  
<td>

The purpose of the data collection is to test the efficacy of the different
encapsulation methods used by the CHEOPS consortium members. Analysis on
encapsulation layers will be carried on via calcium tests. Additionally,
calcium tests will also asses the quality of transportation devices used
during the exchange of samples among partners. The information produced is not
confidential.

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

**Explain the relation to the objectives of the project**

</td>  
<td>

The data is produced as part of the process to reach the project’s technical
objective 1 (TO1 in the DoA) of upscaling the perovskite PV technology.

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

**Specify the types and formats of data generated / collected**

</td>  
<td>

The measured data from the calcium test will each consist of a combination of:

  1. Description of the encapsulation process used 

  

  2. Name of the CHEOPS partner providing the sample 

  

  3. Date of the measurement 

  

  4. Humidity 

  

  5. Temperature 

  

  6. Transmission of light over time 

  

  

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

**Specify the origin of the data**

</td>  
<td>

The data will be documented or measured by Fraunhofer from samples delivered
by partners in WP2.

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

**State the expected size of the data (if known)**

</td>  
<td>

A few KB per sample.

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

**Outline the data utility: To whom it will be useful**

</td>  
<td>

These data could be useful for people working in the field of perovskite based
PV and in general to the PV community.

Similar data already exist in several published works from different groups.
Our dataset could be compared to this already existing information.

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

##  4.2 FAIR Data

###  4.2.1 Making data findable, including provisions for metadata  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Outline the discoverability of data (metadata provision)**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**Outline the identifiability of data and refer to standard identification
mechanisms.**

**Do you make use of persistent unique identifiers such as Digital Object
Identifiers?**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**Outline naming conventions used**

</td>  
<td>

_To be defined at a later stage._

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

**Outline the approach towards search keyword**

</td>  
<td>

_See general considerations and list of default keywords in Section_

_2.2 above._ Additional keywords specifically for this dataset will be
‘Calcium test’ and ‘transmission rate’

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

**Outline the approach for clear versioning**

</td>  
<td>

_To be defined at a later stage._

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

**Specify standards for metadata creation (if any). If there are no standards
in your discipline describe what type of metadata will be created and how.**

</td>  
<td>

Stability measurement standards have been developed for different types of
photovoltaics. In this project, we are following standards developed for
organic photovoltaics. This information can be found in Reese _et al._
_DOI:10.1016/j.solmat.2011.01.036_ where the protocol ISOS-D-3, standard used
by the consortium is described in great detail. On the other hand, calcium
test is a popular method to test the permeation of water vapour through a
membrane which is widely explained in the literature, e.g.  _DOI:
10.1016/S00406090(02)00584-9_ .  
</td> </tr> </table>

###  4.2.2 Making data openly accessible  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify which data will be made openly available. If some data is kept
closed provide rationale for doing so**

</td>  
<td>

In the framework of CHEOPS, the information on device performances, stability,
measurement protocols and device structures will be shared.

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

**Specify how the data will be made available**

</td>  
<td>

Currently data are shared via scientific communication, either in the form of
scientific papers or at conferences via oral or visual presentations. While
the peer-reviewed publications will be made available as open access, it is
the intention to also provide the underlying data itself by storing it in an
open repository ( _see Section 2.1 above_ )

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

**Specify what methods or software tools are needed to access the data. Is
documentation about the software needed to access the data included? Is it
possible to include the relevant software (e.g. in open source code)?**

</td>  
<td>

No special software is needed to access the data.

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

**Specify where the data and associated metadata, documentation and code are
deposited.**

</td>  
<td>

_See general considerations outlined in Section 2.1 above._

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

**Specify how access will be provided in case there are any restrictions**

</td>  
<td>

The data will be made available without restrictions.

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

###  4.2.3 Making data interoperable  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Assess the interoperability of your data. Specify what data and metadata
vocabularies, standards or methodologies you will follow to facilitate
interoperability.**

</td>  
<td>

_See last point under Section 4.2.1 above._

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

**Specify whether you will be using standard vocabulary for all data types
present in your data set, to allow interdisciplinary interoperability? If not,
will you provide mapping to more commonly used ontologies?**

</td>  
<td>

No standard vocabulary currently available. _Please also see the comments made
under Section 4.2.1 above._

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

###  4.2.4 Increase data re-use (through clarifying licenses)  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify how the data will be licensed to permit the widest re-use possible**

</td>  
<td>

At present, no licensing is envisaged.

_Also see general considerations under Section 2.4 above._

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

**Specify when the data will be made available for re-use. If applicable,
specify why and for what period a data**

</td>  
<td>

At present, no embargo period is envisaged.

_Also see general considerations under Section 2.5 above._

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

**embargo is needed.**

</td>  
<td>

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

**Specify whether the data produced and/or used in the project is useable by
third parties, in particular after the end of the project? If the reuse of
some data is restricted, explain why.**

</td>  
<td>

_See general considerations under Section 2.4 above._

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

**Describe the data quality assurance process**

</td>  
<td>

For use within CHEOPS, a standardised sample size and geometry as well as
standard operating procedures (SOP) for sample shipment and sample measurement
has been agreed upon. Following these SOPs will be mandatory for all
measurements carried out during the project. The SOPs were made available to
the CHEOPS consortium in deliverable D6.3, the “Quality and Best Practice
Manual” and will be made publicly available.

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

**Specify the length of time for which the data will remain re-useable.**

</td>  
<td>

The data made available will remain re-useable for an unrestricted duration.

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

##  4.3 Allocation of resources  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Estimate the costs for making your data FAIR. Describe how you intend to
cover these costs**

</td>  
<td>

The small amount of staff costs required for inserting the data into the
repository will be covered from the CHEOPS project budget.

The hosting of the data in the repository is typically free (e.g. ZENODO).

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

**Clearly identify responsibilities for data management in your project**

</td>  
<td>

General decisions (e.g. on licences or repositories) will be taken by the
Executive Board. For actual implementation of data management in each WP, the
WP leaders are responsible.

For this dataset, WP2 leader Fraunhofer is in charge.

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

**Describe costs and potential value of long term preservation**

</td>  
<td>

There will be no long-term costs for CHEOPS partners for maintaining the data
repository.

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

##  4.4 Data security  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Address data recovery as well as secure storage and transfer of sensitive
data**

</td>  
<td>

_See general considerations in Section 2.6._

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

##  4.5 Ethical aspects  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**To be covered in the context of the ethics review, ethics section of DoA and
ethics deliverables. Include references and related technical aspects if not
covered by the former**

</td>  
<td>

Not applicable. _See also general consideration in Section 2.7_

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

##  4.6 Other  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Refer to other national / funder / sectorial / departmental procedures for**

**data management that you are using (if any)**

</td>  
<td>

Not applicable.

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

#  5 Dataset on risk assessment and roadmap development (from WP3)

##  5.1 Data summary  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**State the purpose of the data collection / generation**

</td>  
<td>

In the framework of WP3, data will be generated to characterise potential
emissions of different chemicals brought by CHEOPS devices all along the life
cycle, from production to end-of-life. This will include the results of tests
made in standard conditions, but also during or after damage (incineration,
leakage after breakage). Results could be extended to exposure assessment
(workers, users, …). To our knowledge, those results are likely to be novel,
and as such would be published in scientific reviews.

Socio-economic analysis will also collect and generate data on the assessment
of potential impacts of a large scale development of CHEOPS devices. Those
impacts will be assessed qualitatively, quantitatively, or in monetary terms.
Those results will be published in peer-reviewed journals.

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

**Explain the relation to the objectives of the project**

</td>  
<td>

The data is produced as part of the process to reach the project’s main
objective of identifying and addressing risks to the perovskite PV technology.
In particular, it addresses Market Objective 3 (MO3 in the DoA).

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

**Specify the types and formats of data generated / collected**

</td>  
<td>

Concerning emissions characterisation, the format of data has not yet been
defined.

Concerning socio-economic analysis, results will follow the guidelines
produced by international organisations and agencies like  _OECD_ 2  and
_ECHA_ 3  .

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

**Specify the origin of the data**

</td>  
<td>

The data will mainly be documented or measured by the CHEOPS partners in WP3.
Data on emissions after damage will be obtained by INERIS.

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

**State the expected size of the data (if known)**

</td>  
<td>

Not known yet.

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

**Outline the data utility: To whom it will be useful**

</td>  
<td>

These data could be useful for people working in the field of perovskite based
PV, but also to public authorities and stakeholders of the solar energy
economy.

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

##  5.2 FAIR Data

###  5.2.1 Making data findable, including provisions for metadata  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Outline the discoverability of data (metadata provision)**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**Outline the identifiability of data and refer to standard identification
mechanisms.**

**Do you make use of persistent unique identifiers such as Digital Object
Identifiers?**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**Outline naming conventions used**

</td>  
<td>

To be defined at a later stage.

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

**Outline the approach towards search keyword**

</td>  
<td>

_See general considerations and list of default keywords in Section 2.2
above._

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

**Outline the approach for clear versioning**

</td>  
<td>

To be defined at a later stage.

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

**Specify standards for metadata creation (if any). If there are no standards
in your discipline describe what type of metadata will be created and how.**

</td>  
<td>

Concerning the socio-economic analysis, the results will follow the guidelines
produced by international organisations and agencies like  _OECD_ 3  and
_ECHA_ 5  .

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

###  5.2.2 Making data openly accessible  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify which data will be made openly available. If some data is kept
closed provide rationale for doing so**

</td>  
<td>

In the framework of CHEOPS, the information on device performances, stability,
measurement protocols and device structures will be shared.

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

**Specify how the data will be made available**

</td>  
<td>

Currently data are shared via scientific communication, either in the form of
scientific papers or at conferences via oral or visual presentations. While
the peer-reviewed publications will be made available as open access, it is
the intention to also provide the underlying data itself by storing it in an
open repository ( _see Section 2.1 above_ ).

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

**Specify what methods or software tools are needed to access the data. Is
documentation about the software needed to access the data included? Is it
possible to include the relevant software (e.g. in open source code)?**

</td>  
<td>

No software is needed to access the data.

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

**Specify where the data and associated metadata, documentation and code are
deposited.**

</td>  
<td>

_See general considerations outlined in Section 2.1 above._

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

**Specify how access will be provided in case there are any restrictions**

</td>  
<td>

The data that will be made available will be available without restrictions.

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

###  5.2.3 Making data interoperable  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Assess the interoperability of your data. Specify what data and metadata
vocabularies, standards or methodologies you will follow to facilitate
interoperability.**

</td>  
<td>

_See last point under Section 5.2.1 above._

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

**Specify whether you will be using standard vocabulary for all data types
present in your data set, to allow interdisciplinary interoperability? If not,
will you provide mapping to more commonly used ontologies?**

</td>  
<td>

_No standard vocabulary currently available. Please also see the comments made
under Section 5.2.1 above._

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

###  5.2.4 Increase data re-use (through clarifying licenses)  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify how the data will be licensed to permit the widest re-use possible**

</td>  
<td>

_See general considerations under Section 2.4 above._

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

**Specify when the data will be made available for re-use. If applicable,
specify why and for what period a data**

</td>  
<td>

_See general considerations under Section 2.5 above._

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

**embargo is needed.**

</td>  
<td>

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

**Specify whether the data produced and/or used in the project is useable by
third parties, in particular after the end of the project? If the reuse of
some data is restricted, explain why.**

</td>  
<td>

_See general considerations under Section 2.4 above._

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

**Describe the data quality assurance process**

</td>  
<td>

To be defined in detail at a later stage. But data production will follow the
most demanding standards of replicability required for scientific
publications.

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

**Specify the length of time for which the data will remain re-useable.**

</td>  
<td>

The data made available will remain re-useable for an unrestricted duration.

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

##  5.3 Allocation of resources  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Estimate the costs for making your data FAIR. Describe how you intend to
cover these costs**

</td>  
<td>

The small amount of staff costs required for inserting the data into the
repository will be covered from the CHEOPS project budget.

The hosting of the data in the repository is typically free (e.g. ZENODO).

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

**Clearly identify responsibilities for data management in your project**

</td>  
<td>

General decisions (e.g. on licences or repositories) will be taken by the
Executive Board. For actual implementation of data management in each WP, the
WP leaders are responsible.

For this dataset, WP3 leader INERIS is in charge.

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

**Describe costs and potential value of long term preservation**

</td>  
<td>

There will be no long-term costs for CHEOPS partners for maintaining the data
repository.

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

##  5.4 Data security  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Address data recovery as well as secure storage and transfer of sensitive
data**

</td>  
<td>

_See general considerations in Section 2.6._

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

##  5.5 Ethical aspects  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**To be covered in the context of the ethics review, ethics section of DoA and
ethics**

</td>  
<td>

Not applicable. _See also general consideration in Section 2.7_

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

**deliverables. Include references and related technical aspects if not
covered by the former**

##  5.6 Other  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Refer to other national / funder / sectorial / departmental procedures for**

**data management that you are using (if any)**

</td>  
<td>

Not applicable.

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

#  6 Dataset on life cycle analysis (from WP3) 6.1 Data summary  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**State the purpose of the data collection / generation**

</td>  
<td>

  1. Data collected for the manufacturing of the CHEOPS PV modules are the inputs and outputs of materials and energy for the factory and the transport of materials to and waste from the factory. 

  

  2. Calculated environmental impact results 

  

  

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

**Explain the relation to the objectives of the project**

</td>  
<td>

The data is produced as part of the process to reach the project’s main
objective of identifying and addressing risks to the perovskite PV technology.
In particular, it addresses Market Objective 3 (MO3 in the DoA).

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

**Specify the types and formats of data generated / collected**

</td>  
<td>

The Life Cycle analysis developed in the framework of WP3 will follow the ISO
standards 14040:2006. Since the ecoinvent 3 data set will be used for
background data the ecoinvent data structure will be used.

For the environmental impact assessment the ILCD method present in the Simapro
software will be used.

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

**Specify the origin of the data**

</td>  
<td>

The data will be collected and processed by the CHEOPS partner SMART in WP3.
Input data will be taken also from the ecoinvent 3 database.

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

**State the expected size of the data (if known)**

</td>  
<td>

Not known yet.

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

**Outline the data utility: To whom it will be useful**

</td>  
<td>

These data could be useful for people working in the field of perovskite based
PV, but also to public authorities and stakeholders of the solar energy
economy.

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

##  6.2 FAIR Data

###  6.2.1 Making data findable, including provisions for metadata  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Outline the discoverability of data (metadata provision)**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**Outline the identifiability of data and refer to standard identification
mechanisms.**

**Do you make use of persistent unique identifiers**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**such as Digital Object Identifiers?**

</td>  
<td>

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

**Outline naming conventions used**

</td>  
<td>

Ecoinvent 3 naming

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

**Outline the approach towards search keyword**

</td>  
<td>

_See general considerations and list of default keywords in Section 2.2
above._

Additional keywords specifically for this dataset will be ‘life cycle
assessment’

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

**Outline the approach for clear versioning**

</td>  
<td>

_To be defined at a later stage._

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

**Specify standards for metadata creation (if any). If there are no standards
in your discipline describe what type of metadata will be created and how.**

</td>  
<td>

The Life Cycle Analysis developed in the framework of WP3 will follow the ISO
standards 14040:2006. Since the ecoinvent 3 data set will be used for
background data the ecoinvent data structure will be used.

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

###  6.2.2 Making data openly accessible  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify which data will be made openly available. If some data is kept
closed provide rationale for doing so**

</td>  
<td>

The environmental impacts calculated with the ILCD impact assessment method.

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

**Specify how the data will be made available**

</td>  
<td>

Currently data are shared via scientific communication, either in the form of
scientific papers or at conferences via oral or visual presentations. While
the peer-reviewed publications will be made available as open access, it is
the intention to also provide the underlying data itself by storing it in an
open repository ( _see Section_

_2.1 above_ )

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

**Specify what methods or software tools are needed to access the data. Is
documentation about the software needed to access the data included? Is it
possible to include the relevant software (e.g. in open source code)?**

</td>  
<td>

No specific software is needed to access the data.

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

**Specify where the data and associated metadata, documentation and code are
deposited.**

</td>  
<td>

See general considerations outlined in Section 2.1 above.

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

**Specify how access will be provided in case there are any restrictions**

</td>  
<td>

The data that will be made available will be available without restrictions.

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

###  6.2.3 Making data interoperable  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Assess the interoperability of your data. Specify what data and metadata
vocabularies, standards or methodologies you will follow to facilitate
interoperability.**

</td>  
<td>

_See last point under Section 6.2.1 above._

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

**Specify whether you will be using standard vocabulary for all data types
present in your data set, to allow interdisciplinary interoperability? If not,
will you provide mapping to more commonly used ontologies?**

</td>  
<td>

No standard vocabulary currently available. Please also see the comments made
under _Section 6.2.1_ above.

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

###  6.2.4 Increase data re-use (through clarifying licenses)  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify how the data will be licensed to permit the widest re-use possible**

</td>  
<td>

No licensing. Free use.

_Also see general considerations under Section 2.4 above._

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

**Specify when the data will be made available for re-use. If applicable,
specify why and for what period a data embargo is needed.**

</td>  
<td>

_See general considerations under Section 2.5 above._

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

**Specify whether the data produced and/or used in the project is useable by
third parties, in particular after the end of the project? If the reuse of
some data is restricted, explain why.**

</td>  
<td>

_See general considerations under Section 2.4 above._

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

**Describe the data quality assurance process**

</td>  
<td>

Review by CHEOPS partners.

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

**Specify the length of time for which the data will remain re-useable.**

</td>  
<td>

The data made available will remain re-useable for an unrestricted duration.

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

##  6.3 Allocation of resources  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Estimate the costs for making your data FAIR. Describe how you intend to
cover these costs**

</td>  
<td>

The small amount of staff costs required for inserting the data into the
repository will be covered from the CHEOPS project budget.

The hosting of the data in the repository is typically free (e.g. ZENODO).

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

**Clearly identify responsibilities for data management in your project**

</td>  
<td>

General decisions (e.g. on licences or repositories) will be taken by the
Executive Board. For actual implementation of data management in each WP, the
WP leaders are responsible. For this dataset, SMART is in charge.

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

**Describe costs and potential value of long term preservation**

</td>  
<td>

There will be no long-term costs for CHEOPS partners for maintaining the data
repository.

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

##  6.4 Data security  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Address data recovery as well as secure storage and transfer of sensitive
data**

</td>  
<td>

_See general considerations in Section 2.6._

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

##  6.5 Ethical aspects  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**To be covered in the context of the ethics review, ethics section of DoA and
ethics deliverables. Include references and related technical aspects if not
covered by the former**

</td>  
<td>

_Not applicable. See also general consideration in Section 2.7_

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

##  6.6 Other  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Refer to other national / funder / sectorial / departmental procedures for**

**data management that you are using (if any)**

</td>  
<td>

_Not applicable._

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

#  7 Dataset on perovskite/silicon tandem cell development (from WP4)

##  7.1 Data summary  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**State the purpose of the data collection / generation**

</td>  
<td>

We generate data about device fabrication, material composition and device
performances. Data will be obtained for the individual cells as well as for
the tandem devices.

Similar data already exist in the form of publications from other groups. Our
dataset can be compared to existing results.

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

**Explain the relation to the objectives of the project**

</td>  
<td>

The data is produced as part of the process to reach the project’s technical
objective 2 (TO2 in the DoA) of manufacturing monolithic 2-terminal PK/c-Si
heterojunction tandem (demonstrator) cells.

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

**Specify the types and formats of data generated / collected**

</td>  
<td>

The data on device structure and process conditions of the different layers
will be descriptive, while the measured device performances will each consist
of a combination of:

  1. Name of the parameter measured 

  

  2. Numeric value measured 

  

  3. Physical unit 

  

  

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

**Specify the origin of the data**

</td>  
<td>

The data will be documented or measured by the CHEOPS partners in WP4.

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

**State the expected size of the data (if known)**

</td>  
<td>

Not known yet.

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

**Outline the data utility: To whom it will be useful**

</td>  
<td>

These data could be useful for other research groups working especially in the
field of perovskite-based photovoltaics, but also for other domains of
(academic and industrial) PV research and development.

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

##  7.2 FAIR Data

###  7.2.1 Making data findable, including provisions for metadata  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Outline the discoverability of data (metadata provision)**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**Outline the identifiability of data and refer to standard identification
mechanisms.**

**Do you make use of persistent unique identifiers such as Digital Object**

</td>  
<td>

_See general considerations in Sections 2.2 and 2.3 above._

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

**Identifiers?**

</td>  
<td>

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

**Outline naming conventions used**

</td>  
<td>

To be defined at a later stage.

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

**Outline the approach towards search keyword**

</td>  
<td>

_See general considerations and list of default keywords in Section 2.2
above._

Additional keywords specifically for this dataset will be ‘tandem’, ‘four-
terminal’, ‘monolithic’ and ‘two-terminal’.

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

**Outline the approach for clear versioning**

</td>  
<td>

To be defined at a later stage.

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

**Specify standards for metadata creation (if any). If there are no standards
in your discipline describe what type of metadata will be created and how.**

</td>  
<td>

This kind of datasets can typically be found in scientific publications but
there exist no standards for these publications. Very recently, in October
2015, the “Nature Materials” journal has made and attempt at harmonisation by
developing a checklist for photovoltaic research:
_http://www.nature.com/nmat/journal/v14/n11/full/nmat4473.html_

CHEOPS will consider this checklist and monitor its further development, as it
might help to create a metadata set by allowing proper comparison between the
different published results.

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

###  7.2.2 Making data openly accessible  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify which data will be made openly available. If some data is kept
closed provide rationale for doing so**

</td>  
<td>

In the framework of CHEOPS, the information on device performances, stability,
measurement protocols and device structures will be shared

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

**Specify how the data will be made available**

</td>  
<td>

Currently data are shared via scientific communication, either in the form of
scientific papers or at conferences via oral or visual presentations. While
the peer-reviewed publications will be made available as open access, it is
the intention to also provide the underlying data itself by storing it in an
open repository ( _see Section 2.1 above_ )

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

**Specify what methods or software tools are needed to access the data.**

</td>  
<td>

No special software is needed to access the data.

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

**Specify where the data and associated metadata, documentation and code are
deposited.**

</td>  
<td>

_See general considerations outlined in Section 2.1 above._

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

**Specify how access will be provided in case there are any restrictions**

</td>  
<td>

The data that will be made available will be available without restrictions.

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

###  7.2.3 Making data interoperable  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Assess the interoperability of your data. Specify what data and metadata
vocabularies, standards or methodologies you will follow to facilitate
interoperability.**

</td>  
<td>

_See last point under Section 7.2.1 above._

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

**Specify whether you will be using standard vocabulary for all data types
present in your data set, to allow interdisciplinary interoperability? If not,
will you provide mapping to more commonly used ontologies?**

</td>  
<td>

No standard vocabulary currently available. _Please also see the comments made
under Section 7.2.1 above._

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

###  7.2.4 Increase data re-use (through clarifying licenses)  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Specify how the data will be licensed to permit the widest re-use possible**

</td>  
<td>

Creative Common licenses such as CC-BY-NC or CC-BY-NC-SA could be an idea. We
will seek a consortium decision on this issue.

_Also see general considerations under Section 2.4 above._

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

**Specify when the data will be made available for re-use. If applicable,
specify why and for what period a data embargo is needed.**

</td>  
<td>

_See general considerations under Section 2.5 above._

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

**Specify whether the data produced and/or used in the project is useable by
third parties, in particular after the end of the project?**

</td>  
<td>

_See general considerations under Section 2.4 above._

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

**Describe the data quality assurance process**

</td>  
<td>

For use within CHEOPS, a standardised sample size and geometry as well as
standard operating procedures (SOP) for sample shipment and sample measurement
has been agreed upon. Following these SOPs will be mandatory for all
measurements carried out during the project. The SOPs were made available to
the CHEOPS consortium in deliverable D6.3, the “Quality and Best Practice
Manual” and will be made publicly available.

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

**Specify the length of time for which the data will remain re-useable.**

</td>  
<td>

The data made available will remain re-useable for an unrestricted duration.

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

##  7.3 Allocation of resources  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Estimate the costs for making your data FAIR. Describe how you intend to
cover these costs**

</td>  
<td>

The small amount of staff costs required for inserting the data into the
repository will be covered from the CHEOPS project budget.

The hosting of the data in the repository is typically free (e.g. ZENODO).

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

**Clearly identify responsibilities for data management in your project**

</td>  
<td>

General decisions (e.g. on licences or repositories) will be taken by the
Executive Board. For actual implementation of data management in each WP, the
WP leaders are responsible.

For this dataset, WP4 leader EPFL is in charge.

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

**Describe costs and potential value of long term preservation**

</td>  
<td>

There will be no long-term costs for CHEOPS partners for maintaining the data
repository.

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

##  7.4 Data security  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Address data recovery as well as secure storage and transfer of sensitive
data**

</td>  
<td>

_See general considerations in Section 2.6._

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

##  7.5 Ethical aspects  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**To be covered in the context of the ethics review, ethics section of DoA and
ethics deliverables. Include references and related technical aspects if not
covered by the former**

</td>  
<td>

_Not applicable. See also general consideration in Section 2.7_

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

##  7.6 Other  
  
<table>  
<tr>  
<th>

**DMP component**

</th>  
<th>

**Description**

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

**Refer to other national / funder / sectorial / departmental procedures for**

**data management that you are using (if any)**

</td>  
<td>

_Not applicable._

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