#  Executive Summary

This deliverable outlines the first version of the EU calculator Data
Management Plan. The DMP as outlines only deals with process data (not
personal data gather during the EU calculator workshops). Accordingly, this
document provides:

  6. the characterization of the main types of data expected to be collected and produced during the time frame of the project, 

  

  7. the list of licences detailing data re-use policies and intellectual property rights to be adopted, 

  

  8. the list of repositories and strategies to make the data accessible after the termination of the project, 

  

  9. the first version of the metadata standards to be adopted by the EU calculator both for collected and produced data. 

  

  10. The first outline of model documentation guidelines. 

  

  

#  Introduction

##  Importance of the plan and objectives

The appropriate management of data is an essential, often forgotten,
undertaking of responsible research. At the start of a new research project,
it is important to lay down the basic principles relating to data and data
management. The creation of a shared Data Management Plan (DMP) at the
beginning of the project meets the requirement of informing the involved
partners on important procedures and processes regarding data collection,
processing, storing and distribution. Furthermore, the DMP is pivotal in
guaranteeing that the data collected and processed can be easily and properly
shared within the consortium and distributed beyond the project lifetime. A
data management plan helps achieve optimal handling, organizing, documenting
and enhancing of research data. It is particularly important for facilitating
data sharing, ensuring the sustainability and accessibility of data in the
long-term, and allowing data to be reused for future research.

For maximum effectiveness, the DMP must start when research is being designed
and needs to consider both how data and information will be managed during the
research and how they will be shared afterwards. This involves thinking
critically of how research data can be shared, what might limit or prohibit
data sharing, and whether any steps can be taken to remove such limitations.
In the context of the European Calculator project, plans regarding the usage
of data and model documentation started during its preparation phase. The time
and thoughts devoted to the data management issues were preliminary and hence
it is now time to undertake a more concerted effort in elaborating the MP for
the European Calculator project. The DMP for a research project in the H2020
program should elaborate on the following aspects (without any particular
order of importance).

  * Handling of research data during and after the end of the project 

  

  * What data will be collected, processed and/ or generated 

  

  * Which methodology and standards will be applied 

  

  * Whether data will be shared/made open access and how data will be curated and preserved (including after the end of the project) 

  

These aspects are a mandatory requirement in the Programme Guidelines on FAIR
Data Management in Horizon 2020  1  . The guidelines from the European
Commission on the requirements for the DMP focus on the issues of data
documentation, standards applied and data re-use.

During the lifetime of the European Calculator project the DMP will be updated
in D11.7 (Month 35). The DMP described in the sections below is to be taken as
a first iteration document to synchronize the knowledge of partners on their
datarelated responsibilities and to outline the major guiding principles of
the EU calculator project in regard to its data policy. I addition, future
iterations will also explore potential synergies of the EU calculator DMP with
those being developed by INNOPATHS and REINVENT.

##  FAIR data principles

The open data policy of the European Union favours the implementation of the
G8 Open Data Charter  2  and the FAIR Guiding Principles  3  for scientific
data. The latter highlights core principles as enumerated below:

**To be Findable:**

  * Data are assigned a globally unique and persistent identifier 

  

  * Data are described with rich metadata 

  

  * Metadata clearly and explicitly include the identifier of the data it describes  Data are registered or indexed in a searchable resource 

  

**To be Accessible:**

  * Data are retrievable by their identifier using a standardized communications protocol 

  

  * The protocol is open, free, and universally implementable 

  

  * The protocol allows for an authentication and authorization procedure, where necessary 

  

  * Metadata are accessible, even when the data are no longer available 

  

**To be Interoperable:**

  * Data use a formal, accessible, shared, and broadly applicable language for knowledge representation. 

  

  * Data use vocabularies that follow FAIR principles 

  

  * Data include qualified references to other data 

  

**To be Reusable:**

  * Data are richly described with a plurality of accurate and relevant attributes 

  

  * Data are released with a clear and accessible data usage license 

  

  * Data are associated with detailed provenance 

  

  * Data meet domain-relevant community standards 

  

The EU calculator project will adhere to these principles during the
elaboration and fulfilment of its DMP.

#  Data origin and type

The European calculator project will make use of a number of heterogeneous
data sources that can be broadly classified as external and internal to the
project. By external it is meant that datasets are acquired from institutions
external to the European calculator consortium. By internal it is meant that
the data is owned by the partners or generated within the European Calculator
activities. As a rule, external open-datasets that are regularly updated will
be favoured although one cannot discard the possibility of the project
requiring particular external datasets subject to licensing.

##  External data

###  Open sources

The European calculator project will connect to open data sources that are
regularly maintained and updated from European and Global institutions. For
example, it is foreseen to substantially rely on Eurostat and OECD data, both
as model baseline and as input for statistical relations to quantify some of
the model dynamics. External data repositories such the Database on Shared
Socioeconomic Pathways hosted at IIASA  4  and climate data from initiatives
like CORDEX  5  and the ODYSEE database  6  are also foreseen to be accessed
and data retrieved during the running time of the project. Databases from
existing and closed EU-funded projects such as Heat Road Maps  7  project will
also be scanned for their potential in supplying the European calculator
project with data. For example datasets from the TRACCS  8  project or the EU
Buildings Database  9  are also expected to be used during the project.

###  Paying sources

At the time of writing there is not yet a clear indication that datasets
falling into this category are required. This section will be updated in the
next iteration the ECDMP.

##  Internal data

In regard to internal datasets, these will refer mostly to the data generated
during the lifetime of the project and are foreseen to comprise mostly model
outputs and expert opinions gathered during the sectoral expert-consultation
workshops. Regarding the latter, there is in place a common procedure to
guarantee confidentiality of personal data (see Del. 12.1). The expert
consultation workshops will supply the team of the European Calculator with
opinions on the modelling approaches undertaken and evidence base support on
the choice of particular ambition levers.

To a lesser extent, datasets and model processes owned by the institutions
comprising the European Calculator project will also be used. For example,
published datasets like the BPIE Building observatory database or dietary
patterns and decarbonisation pathways will be used to inform on the
development of the model.

##  Data types

The following section describes the current data types forecast to be
generated during the project. Note that this is a preliminary judgement based
on the author’s understanding of the EU Calculator model. This section will be
updated periodically as part of the ECDMP life cycle.  
  
<table>  
<tr>  
<th>

**Identifier**

</th>  
<th>

**Label**

</th>  
<th>

**Description**

</th>  
<th>

**Type**

</th>  
<th>

**Main responsible**

</th>  
<th>

**Access**

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

**OTS**

</td>  
<td>

Observed time

series (historical data)

</td>  
<td>

Observations of climate, socio-

economic variables and emissions.

</td>  
<td>

Numeric

</td>  
<td>

WP leaders of the respective modules.

</td>  
<td>

Public

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

**FTS**

</td>  
<td>

Future time series

(generated data)

</td>  
<td>

Projections of climate, socio-

economic variables and emissions.

</td>  
<td>

Numeric

</td>  
<td>

WP leaders of the respective modules.

</td>  
<td>

Public

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

**LL**

</td>  
<td>

Levels of levers

</td>  
<td>

Levels of technology or lifestyle ambition.

</td>  
<td>

Numeric

</td>  
<td>

WP leaders of the respective modules.

</td>  
<td>

Public

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

**CP**

</td>  
<td>

Constant parameters

</td>  
<td>

Time-invariable parameters required for the model.

</td>  
<td>

Numeric

</td>  
<td>

WP leaders of the respective modules.

</td>  
<td>

Public

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

**MC**

</td>  
<td>

Model/module code

</td>  
<td>

Source code of modules and model.

</td>  
<td>

Code

</td>  
<td>

WP leaders of the respective modules & CLIMACT.

</td>  
<td>

Public

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

**MD**

</td>  
<td>

Model/module documentation

</td>  
<td>

Documentation of model/module code

</td>  
<td>

Text

</td>  
<td>

WP leaders of the respective modules & CLIMACT.

</td>  
<td>

Public

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

_Table 1 – Types of data considered in the European Calculator project._

#  Metadata standards and data formats

All the data used within the project will be available using non-proprietary
formats and documented accordingly via the use of extensive metadata
descriptions and EU-calculator naming conventions. The metadata descriptions
will contain the required elements to guarantee that data are easily
discovered. Table 2 enumerates and describes the foreseen metadata elements to
be used when documenting Observed Time Series (OTS), Future Time Series (FTS),
Level of Levers (LL) and Constant Parameter (CP) data in the EU calculator
project.  
  
<table>  
<tr>  
<th>

**Attribute name**

</th>  
<th>

**Description**

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

_**ID** _

</td>  
<td>

Unique identifier of the dataset.

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

_**Title** _

</td>  
<td>

Dataset title.

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

_**Summary** _

</td>  
<td>

Abstract related to the title attribute.

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

_**Variable** _

</td>  
<td>

Short variable name.

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

_**Unit** _

</td>  
<td>

Unit of the variable.

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

_**Activity** _

</td>  
<td>

Name of the project.

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

_**Tags** _

</td>  
<td>

List of keywords commonly used to describe the subject.

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

_**Frequency** _

</td>  
<td>

Time frequency of the variable.

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

_**Period and reference** _

</td>  
<td>

Time period for which the variable was calculated and respective reference
year.

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

_**Institution** _

</td>  
<td>

URL of the home page of the institution compiling or producing the data.

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

_**Contact** _

</td>  
<td>

Email contact of the main responsible for the data as compiled or produced for
the EU calculator project.

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

_**Contributors and role** _

</td>  
<td>

Any name of person contributing for the data compiled or produced for the EU
calculator project, as well as the respective role.

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

_**Methods summary** _

</td>  
<td>

Brief description of the methodology used to compile/calculate the data.

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

_**Data filling** _

</td>  
<td>

Description of the approach to fill in missing country data.

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

_**Source data** _

</td>  
<td>

Any relevant sources used to compile or produce the data.

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

_**Quality control** _

</td>  
<td>

Description of the quality control process before data publication.

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

_**Comment** _

</td>  
<td>

Miscellaneous information about the data/methods used to derive the dataset.

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

_**References** _

</td>  
<td>

Any additional references.

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

_**Date created** _

</td>  
<td>

Date of data creation (YYYY-MM-DD).

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

_**Data type** _

</td>  
<td>

Type of data

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

_**Workpackage and task** _

</td>  
<td>

Project WP and task from which the data originates.

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

_**Version status** _

</td>  
<td>

Version of the data and its status for usage.

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

_Table 2 – Metadata elements for OTS, PTS, LL and CP data._

Datasets on the Levels of Levers (LL), Observed/Future Time Series (OTS/FTS)
and Constant parameters (CP) will be made publically available following the
CSV or XLS tabular data standard. OTS refers to historical data collected from
sources. The difficulty is to find data for every country and to fill the
gaps. This data is used as input of for the EU calculator model. In this
respect it should be noticed that 1) only credible sources could be used that
have primary/secondary access to the data, i.e. owning/overseeing the system
producing/recording the data or legally obliged to collect data (statistical
offices) and, 2) if possible, use the data from EU level/international bodies
that gather the data from member state level organizations by law, such as
Eurostat, the IEA or the World Bank.

Data coded as FTS are generated by the model. This is the "matrix of
possibilities" that will be used by the Web application; hence, this data is
an output of the model and INPUT of the Web application. LL data are created
by each WP in cooperation with the stakeholders. The LL data refers to
scenarios built for each lever and are therefore inputs of the model. Finally,
CP data refers to constants (physical, geographic, etc...; for example country
entity, mass to kcal conversion) that are required and input for the model.
The documentation of this data obeys to a template whose first version is
described in section 8.

Module Documentation (MD) data will be made available in PDF format. As for
the Model Code (MC) this will be made available in the KNIME and Python
formats.

  * KNIME is an open source data analytics platform 

  

( _https://www.knime.com/_ )  . It integrates various components for machine
learning and data mining and possess a graphical user interface to allow
assembly of nodes for data preprocessing (e.g., extraction, transformation,
etc), for modeling and data analysis and visualization.

  * Python is a high-level programming language for general-purpose programming. It is widely used in the scientific community given its scalability and philosophy emphasizing code readability. 

  

#  Policy of data re-use

##  Open source licence

The data produced in the European Calculator project will be stored as a
comprehensive database and therefore illegible for intellectual property
rights (IPR) and subjected to licencing. When it comes to intellectual
property rights and licences for data, the central notion is the database as
“a collection of independent works, data or other materials arranged in a
systematic or methodological way and individually accessible by electronic or
other means”  10  . The database notion is not restricted to a data collection
stored in traditional database management systems, it relates also to data
stored in a file and organized in a well-structured manner.

The data resulting from the European Calculator will be published under the

Creative Commons Attribution International License **CC-BY-4.0** (
_https://creativecommons.org/licenses/by/4.0/_ )  , and the Open Data Commons
Attribution Licence **ODC v1.0** ( _https://opendatacommons.org/licenses/by/_
)  . These licences are permissive and do not include a copyleft clause  11  .
They allow sharing (copy, redistribute and use the data) as long as the user
entity gives appropriate credit.

#  Data storage and preservation

##  Model data storage

Data used in the development of the EU calculator model will be stored online
using the Amazon S3 (  _https://aws.amazon.com/en/s3/_ )  solution. Inputs for
the model covering the data described in section Data origin and type3 and
documented according the standards described in section 4 will be stored in an
EU calculator dependency. The details on how to upload both the data and
metadata will be made available in the next iteration of the DMP.

##  Long-term storage plan

The data of the European Calculator project will be stored in a research data
repository like PANGAEA (  _www.pangaea.de_ )  . PANGAEA is a free publishing
repository for environmental data (although some small fees might apply in
case of data from big projects) with a Digital Object Identifier (DOI)
service. From this generic storage place for data, the EU calculator team will
reach out to other data repositories in order to increase the visibility and
secure long-term preservation of our outputs by exploring the following
possibilities:

  * Linking the data sets produced in the European calculator to OpenEI.org  ( _http://en.openei.org/wiki/Main_Page_ )  . The Open Energy Information (OpenEI.org) initiative is a free, open source knowledge-sharing platform created to facilitate access to data, models, tools, and information that accelerate the transition to clean energy systems through informed decisions. OpenEI strives to make energy-related data and information searchable, accessible, useful to both people and machines 

  

  * Linking the data sets produced in the European calculator to European’s Union Open Data Portal  ( _https://data.europa.eu/euodp/en/data/_ )  . The European Union Open Data Portal is the single point of access to a growing range of data from the institutions and other bodies of the European Union. The portal aims to promote their innovative use and unleash their economic potential. It also aims to help foster the transparency and the accountability of the institutions and other bodies of the European Union. The Open Data Portal is managed by the Publications Office of the European Union. 

  

  * Upload our datasets to the Open Energy Modelling Initiative  ( _www.openmod-initiative.org/_ )  . The Open Energy Modelling Initiative is more in line with the thematic focus of the European Calculator and hence 

  

the project outputs could gain more visibility for the community if announced
through this channel.

##  Model documentation

One of the most important criteria of the EU Calculator is the transparency of
the model. This can only be achieved by allowing anyone to understand the
model and to find the source of every data that we are using. The data we are
collecting are evolving quickly. It is important to keep track of the version
of every data we are using. Finally, every assumption/hypothesis that we are
taking are influencing the final result of the calculator, we need to track
them and to explain them with details.

  * For Observed Time Series data that we are collecting as input of the model, we need to document the place where we found them, the date, the owner, as well as the method we are using to fill the missing data. 

  

  * For Future Time Series built regarding expert opinion and stakeholder consultations, we need to document the critical hypothesis that we took to build our matrices of scenarios; 

  

  * For Levels of Levers data, it is crucial to track the assumption we made to define the lifestyle ambition or the levels of technology. 

  

  * For Model Code, everyone should be able to understand the code (Knime or Python) without having to know how to code. This is only possible by documenting the code with a deep Model Documentation (MD) inside the code itself. 

  

###  Model versioning

The EU Calculator is a large project with several complicated
modules/components where multiple developers are working together at the same
time. It is simply not feasible to keep track of every modification and to be
able to go back to an older version (in needed) without having something
called version control.

Multiple Version Control Systems (VCS) are on the market. We propose to use
the popular and open source GIT system in the EU Calculator project and to
host our code using the Bitbucket solution (  _https://bitbucket.org/product_
)  .

Git is a free and open source distributed version control system designed to
handle everything from small to very large projects with speed and efficiency.
It outclasses SCM tools like Subversion, CVS, Perforce, and ClearCase with
features like cheap local branching, convenient staging areas, and multiple
workflows. (  _https://git-scm.com/_ )  .

Git will allow us to keep track of the changes in the code but it is the task
of every developer to document his code and the version he is pushing to the
server. The code of the European Calculator can be found at the following
address (you need to be registered to access it):

_https://bitbucket.org/eucalcmodel/_

#  Responsibilities and duties

Each work-package leader institution is responsible for supervising the
creation, compilation and adequate documentation of data during the life time
of the project. This includes making the data available for the rest of the
team, as well as guaranteeing that the data compiled or generated adheres to
the metadata and format standards described in the ECDMP. PIK will support the
partners with doubts regarding the metadata standards. It also falls within
each work package the responsibility to keep the module documentation for the
EU calculator model up to gate and compliant with the template provided.
CLIMACT is responsible for supervising the model documentation, curating the
code and making it available in the predefined format.