#  INTRODUCTION

The main objective of this deliverable is to provide the data management
policy with regard to the data sources that the ENTROPY project collects,
processes, generates and makes available. This deliverable is a ‘living
document’ which will be further developed within the course of the project so
as to define the research data that will be collected and specify how these
data collections will be processed and managed in accordance with relevant
standards and methodologies. Finally, it will also incorporate the decisions
for data sharing and archiving.

####  Document Composition

This document is composed of the following six (6) chapters, each one covering
a specific area as specified by the EC guidelines in its Data Management Plan
template:

  * Chapter 1: Introduction 

  

  * Chapter 2: Initial naming of the datasets 

  

  * Chapter 3: Description of the minimum datasets to be collected for each pilot 

  

  * Chapter 4: Standards and metadata 

  

  * Chapter 5: Data access and sharing mechanisms ▪ Chapter 6: Archiving and preservation of the data 

  

#  DATASETS: REFERENCE AND NAME

ENTROPY project is still identifying a set of heterogeneous data sources
through a series of interviews with project end-users. Following an iterative
process, data sources are being established, encapsulating that way the
project end-user requirements. A refinement process will continuously take
place throughout the lifetime of the project, as new data sources are becoming
available to the consortium.

ENTROPY project is driven by three different pilots in three different sites:

  1. Pilot A: Navacchio Technology Park (NTP) 

  

  2. Pilot B: University of Murcia Campus (UMU) 

  

  3. Pilot C: Technopole in Sierre (HES-SO) 

  

  

The teams working under these pilots have formed users’ interaction scenarios
with the system, which include data for overall assessment and behavioural
analysis, providing a minimum set of data.

The data sets required by each pilot differ to each other, since the pilots
have different types of data sources. However, similar naming methodology will
be followed. The partners will receive one or more files (.xls/.csv)
containing data. The name of the file should follow a specific structure, such
as: PL_DS_FT_ND_V_D.

  * PL: PiLot, the name of the pilot, the first letters (three max) of the pilot’s responsible partner (UM for UMU, NT for NTP, HE for HES-SO) 

  

  * DS: DataSet, the set of data related to the pilot. It may take the value “ALL”, if the file contains all the sets of data. 

  

  * FT: FormaT, the format of the file of the data 

  

  * ND: The name of the original document 

  

  * V: The version of the document 

  

  * D: The date of receiving the document or the date of creating this document (dd-mm-yyyy). 

  

The respective folders used may follow similar structure: PL_FT_ND_D

  * PL: PiLot, the first letters (three max) of the pilot’s responsible partner (UMU, NTP, HESSO) 

  

  * FT: FormaT, the format of the file of the data 

  

  * ND: The name of the original document 

  

  * D: The reception or creation date of the document. 

  

Additionally, some of the pilots could expose their datasets by means of
public web services to make the data access easier and more reliable.

#  DATASET DESCRIPTION

For each of these target groups, several parameters have been identified by
each pilot. The data to be received by external sources will fill in these
parameters. The pilots have identified some identical parameters, however some
differ. For Pilot 1 and Pilot 2, there are five basic types of parameters,
which are also shared by Pilot 3:

  * Demographics: Data concerning the demographics of the users 

  

  * Building Data: Data describing the buildings’ characteristics 

  

  * Psychographics: Data concerning the personality of the users 

  

  * Room Sensor Data: Data concerning the sensors’ technical characteristics and measurements per room 

  

  * Building Sensor Data: Data concerning energy consumption in the building 

  

**Table 1** Variables corresponding to the common parameter types of all the
three pilots  
  
<table>  
<tr>  
<th>

**Parameter**

</th>  
<th>

**Type**

</th>  
<th>

**Unit**

</th>  
<th>

**Mandatory**

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

DEMOGRAPHICS

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

User ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N(NO)

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

Age

</td>  
<td>

Numeric

</td>  
<td>

Years

</td>  
<td>

N

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

Gender

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Ethnicity

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Function (ex. Manager, professor, student etc.)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Educational level

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Studies

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Hours at university/campus

</td>  
<td>

Numeric

</td>  
<td>

hours

</td>  
<td>

N

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

Kids at home (yes/no)

</td>  
<td>

Boolean

</td>  
<td>

\-

</td>  
<td>

N

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

Working hours

</td>  
<td>

Numeric

</td>  
<td>

hours

</td>  
<td>

N

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

Reported health issues

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

BUILDING DATA

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

Date

</td>  
<td>

String

</td>  
<td>

dd-mm-yyyy HH:mm:ss

</td>  
<td>

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

Building ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y(YES)

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

Construction year

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

Building type

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Building size

</td>  
<td>

Numeric

</td>  
<td>

m (meters)

</td>  
<td>

Y

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

Windows percentage

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

Building regulations

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Consumption baseline

</td>  
<td>

Numeric

</td>  
<td>

kWh

</td>  
<td>

Y

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

Sensor ID (link with sensor data)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Total number of sensors

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

Internal temperature

</td>  
<td>

Numeric

</td>  
<td>

°C

</td>  
<td>

Y

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

Internal humidity level

</td>  
<td>

Numeric

</td>  
<td>

%

</td>  
<td>

Y

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

Occupants per room/building

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

N

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

PSYCHOGRAPHICS

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

Personality test

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Curtailment behaviour

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

“Hassle factor”

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Comfort level

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

The impact of incentives (Questionnaire)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Interest in energy renewable sources

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Intrinsic interest in efficiency (Questionnaire)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

ROOM SENSOR DATA

</td>  
<td>

</td>  
<td>

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

**HVAC**

</td>  
<td>

</td>  
<td>

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

Sensor ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Location

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Automated system (Yes/No)

</td>  
<td>

Boolean

</td>  
<td>

\-

</td>  
<td>

Y

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

State (ON/FF)

</td>  
<td>

Boolean

</td>  
<td>

\-

</td>  
<td>

Y

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

Operation mode (heating/cooling)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Fan speed

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Nominal power

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Energy efficiency label

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Energy ( Electricity, Gas, Fuel oil)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**Energy Meter**

</td>  
<td>

</td>  
<td>

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

Date (timestamp)

</td>  
<td>

Date

</td>  
<td>

dd-mm-yyyy HH:mm:ss

</td>  
<td>

Y

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

Meter ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Energy consumption

</td>  
<td>

Numeric

</td>  
<td>

KWh

</td>  
<td>

Y

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

Energy from renewable sources

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Type of energy source

</td>  
<td>

String

</td>  
<td>

</td>  
<td>

Y

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

Building/Room ID (link with building/room data)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**Indoor Lighting System Management/Luminosity Sensors**

</td>  
<td>

</td>  
<td>

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

Sensor ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Location

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Automated system (Yes/No)

</td>  
<td>

Boolean

</td>  
<td>

\-

</td>  
<td>

Y

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

Light status (ON/OFF)

</td>  
<td>

Boolean

</td>  
<td>

\-

</td>  
<td>

Y

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

Light regulation (0-100%)

</td>  
<td>

Numeric

</td>  
<td>

%

</td>  
<td>

Y

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

Hours of lighting per day

</td>  
<td>

Numeric

</td>  
<td>

Hours

</td>  
<td>

Y

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

Type of lighting (ex. CFL, LED etc.)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Number of lights on

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

Luminous flux

</td>  
<td>

Numeric

</td>  
<td>

lm(lumen)

</td>  
<td>

Y

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

Nominal power

</td>  
<td>

Numeric

</td>  
<td>

W

</td>  
<td>

Y

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

</td>  
<td>

</td>  
<td>

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

**Humidity Sensors**

</th>  
<th>

</th>  
<th>

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

Sensor ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Location

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Humidity level (internal)

</td>  
<td>

Numeric

</td>  
<td>

%

</td>  
<td>

Y

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

**Presence sensor**

</td>  
<td>

</td>  
<td>

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

Sensor ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Location

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Number of attendees

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

N

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

User ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

N

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

Enter timestamp

</td>  
<td>

Date

</td>  
<td>

\-

</td>  
<td>

N

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

Exit timestamp

</td>  
<td>

Date

</td>  
<td>

\-

</td>  
<td>

N

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

BUILDING SENSOR DATA

</td>  
<td>

</td>  
<td>

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

**Energy Meter**

</td>  
<td>

</td>  
<td>

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

Date (timestamp)

</td>  
<td>

String

</td>  
<td>

dd-mm-yyyy HH:mm:ss

</td>  
<td>

Y

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

Meter ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Energy consumption (KWh)

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

Electrical consumption (Active and reactive power)

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

Energy from renewable sources

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Type of energy source

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**Water Meter**

</td>  
<td>

</td>  
<td>

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

Meter ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Water meter type (Mass/Volumetric)

</td>  
<td>

Boolean

</td>  
<td>

</td>  
<td>

Y

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

Water consumption

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

**Environmental conditions monitoring (Weather station)**

</td>  
<td>

</td>  
<td>

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

Weather station ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Temperature (external)

</td>  
<td>

Numeric

</td>  
<td>

°C

</td>  
<td>

Y

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

Barometric pressure

</td>  
<td>

Numeric

</td>  
<td>

Hpa

</td>  
<td>

Y

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

Humidity (external)

</td>  
<td>

Numeric

</td>  
<td>

%

</td>  
<td>

Y

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

Wind speed

</td>  
<td>

Numeric

</td>  
<td>

m.s  -1

</td>  
<td>

Y

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

Wind direction

</td>  
<td>

Numeric

</td>  
<td>

°

</td>  
<td>

Y

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

Precipitation

</td>  
<td>

String

</td>  
<td>

Mm

</td>  
<td>

Y

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

Outside sun duration (luminosity)

</td>  
<td>

Numeric

</td>  
<td>

h/day (hours per day)

</td>  
<td>

Y

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

Outside radiation

</td>  
<td>

Numeric

</td>  
<td>

W/m  2  /day

</td>  
<td>

N

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

</td>  
<td>

</td>  
<td>

(daily radiation average)

</td>  
<td>

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

Further, Pilot 3 concerns three more types of parameters:

  * Environment: Data concerning environmental characteristics of the building 

  

  * Energy: Data describing the building’s characteristics per energy type used 

  

  * Price: Data concerning the price and its updates for gas and fuel oil, along with the consumption characteristics of the city 

  

**Table 2** Variables corresponding to three more parameter types of Pilot 3  
  
<table>  
<tr>  
<th>

**Parameter**

</th>  
<th>

**Type**

</th>  
<th>

**Unit**

</th>  
<th>

**Mandatory**

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

ENVIRONMENT

</td>  
<td>

</td>  
<td>

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

User ID

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Age

</td>  
<td>

Numeric

</td>  
<td>

Years

</td>  
<td>

Y

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

Number of people at work

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

Week-end work

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

Planning production

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Studied surface

</td>  
<td>

String

</td>  
<td>

m  2

</td>  
<td>

Y

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

Location

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Mountain mask/Building environment

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

ENERGY

</td>  
<td>

</td>  
<td>

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

**Heating System**

</td>  
<td>

</td>  
<td>

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

Technology

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Nominal power

</td>  
<td>

Numeric

</td>  
<td>

W

</td>  
<td>

Y

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

Output/energy efficiency

</td>  
<td>

Numeric

</td>  
<td>

%

</td>  
<td>

Y

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

Energy ( Electricity, Gas, Fuel oil)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Energy ( Electricity, Gas, Fuel oil)

</td>  
<td>

Numeric

</td>  
<td>

kWh

</td>  
<td>

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

Local energy control command

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**Devices system**

</td>  
<td>

</td>  
<td>

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

Clusters definition (Cold, Heating,…)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Nominal power

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

Hours at use per day (or per period)

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

Number

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

**Lighting System**

</td>  
<td>

</td>  
<td>

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

Type of lighting (ex. CFL, LED etc.)

</td>  
<td>

</td>  
<td>

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Nominal power

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

W

</td>  
<td>

Y

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

Luminous flux

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

lm

</td>  
<td>

Y

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

Number

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

Y

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

**Hot Water**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Technology

</td>  
<td>

</td>  
<td>

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Nominal power

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

W

</td>  
<td>

Y

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

Output/energy efficiency

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

%

</td>  
<td>

Y

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

Energy ( Electricity, Gas, Fuel oil)

</td>  
<td>

</td>  
<td>

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Energy ( Electricity, Gas, Fuel oil)

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

kWh

</td>  
<td>

N

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

**Ventilation**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Technology

</td>  
<td>

</td>  
<td>

</td>  
<td>

String

</td>  
<td>

</td>  
<td>

Y

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

Nominal power

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

Output/energy efficiency

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

</td>  
<td>

PRICE

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Gas**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Taxes percentage

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

Price evolution year 2015 - n

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

**Fuel oil**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Taxes percent

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

Price evolution year 2015 - n

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

**Electricity**

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Name of supplier

</td>  
<td>

</td>  
<td>

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Taxes percentage

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

Power peak value for price shifting

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

W

</td>  
<td>

Y

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

Power peak percent

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

Reactive power percentage

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

Mean power peak percentage

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

Price evolution year 2015 - n

</td>  
<td>

</td>  
<td>

</td>  
<td>

Numeric

</td>  
<td>

</td>  
<td>

Y

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

#  STANDARDS AND METADATA

ENTROPY project is related to different pillars, e.g., green energy,
environment, etc. Several existing standards, addressing interoperability,
adaptability and dynamicity issues of data on each of these specific fields.
This section presents the required standards, along with the methodologies and
technical documents that will be taken into account in order for the project
to produce aligned data structures and data services.

##  ISO/TR 16344:2012

ISO/TR 16344:2012 provides a coherent set of terms, definitions and symbols
for concepts and physical quantities related to the overall energy performance
of buildings and their components, including definitions of system boundaries,
to be used in all standards elaborated within ISO on energy performance of
buildings.

These terms and definitions are applicable to energy calculations in
accordance with the Technical Report and standards on the overall energy
performance of buildings and their components, to provide input to the
Technical Report or using output from the Technical Report. They are based on
existing terms and definitions from standards and other documents referenced
in the bibliography.

##  ISO 16346:2013

ISO 16346:2013 defines the general procedures to assess the energy performance
of buildings, including technical building systems, and defines the different
types of ratings, and the building boundaries. The purpose of ISO 16346:2013
is to (a) collate results from other international standards that calculate
energy use for specific services within a building, (b) account for energy
generated in the building, some of which may be exported for use elsewhere,
(c) present a summary of the overall energy use of the building in tabular
form, (d) provide energy ratings based on primary energy, carbon dioxide
emission, or other parameters defined by a national energy policy, and (e)
establish general principles for the calculation of primary energy factors and
carbon dioxide emission coefficients.

ISO 16346:2013 defines the energy services to be taken into account for
setting energy performance ratings for planned and existing buildings and
provides (1) a method to compute the standard calculated energy rating, a
standard energy use that does not depend on occupant behaviour, actual
weather, and other actual (environment or indoor) conditions, (2) a method to
assess the measured energy rating, based on the delivered and exported energy,
(3) a method to improve confidence in the building calculation model by
comparison with actual energy use, and (4) a method to assess the energy
effectiveness of possible improvements. ISO 16346:2013 is applicable to a part
of a building (e.g. flat), a whole building, or several buildings.

##  Methods to assess environmental impacts of ICT

**ETSI Working Group DTR/EE-00008** : This work defines the methods to assess
the environmental impact Assessment of ICTs including the Positive Impact by
using ICT Services. This work will define the methods to assess the
environmental impacts of ICT, which have two aspects. (a) Negative impact
caused by the energy consumptions or CO2 emissions of operators of ICT
equipment and sites including telecom network, users’ terminals and
datacentres for residential and business services. (b) Positive impact caused
by energy saving or CO2 emission saving by using ICT services. We propose the
method of how to quantify these impacts at national level.

##  Technical documents

**IETF** : IETF’s mission is to improve the Internet by producing high quality
technical documents that influence the way people design, use, and manage the
Internet.

##  Metadata

Each data file will be accompanied by unique specified metadata, in order to
allow their ease of access and re-usability. Below, we present the metadata
form we will adopt.

**Table 3** : Metadata form  
  
<table>  
<tr>  
<th>

**Parameter**

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

Document version

</td>  
<td>

The version of this document

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

Document format

</td>  
<td>

The format of this document

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

Description

</td>  
<td>

A description of the data included in the document

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

Date

</td>  
<td>

The date of the creation of the document (yyyy-mm-dd)

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

Keywords

</td>  
<td>

Some keywords describing the content

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

Subject

</td>  
<td>

Small description of the data source

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

**Creator (Name of the creator of the data source)**

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

Sector of the provider

</td>  
<td>

Information on the sector that this provider belongs to

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

Permissions

</td>  
<td>

The permission of this document are mandatory to be mentioned here

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

**Name of the Partner (The name of the partner that collected the data and is
responsible for)**

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

Responsible person

</td>  
<td>

The name of the person within the partner, who is responsible for the data

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

Pilot

</td>  
<td>

For which pilot the data will be used

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

Scenario of data usage

</td>  
<td>

How the data are going to be used in this scenario

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

**Description of the Data Source**

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

File format

</td>  
<td>

The format of the data source provided

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

File name/path

</td>  
<td>

The name of the file

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

Storage location

</td>  
<td>

In case a URI/URL exists for the data provider

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

Data type

</td>  
<td>

Data type and extension of the file; e.g. Excel Sheet, .xlsx; Standard if
possible

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

Standard

</td>  
<td>

Data standard, if existent

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

Data size

</td>  
<td>

Total data size, if possible

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

Time references of data

</td>  
<td>

Start date

</td>  
<td>

End date

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

Availability

</td>  
<td>

Start date

</td>  
<td>

End date

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

Data collection frequency

</td>  
<td>

The time frequency in which the data is collected; e.g. hourly, every 15
minutes, on demand, etc.

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

Data quality

</td>  
<td>

The quality of the data; is it complete, does it have the right collection
frequency, is it available, etc.

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

**Raw data sample**

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

Textual copy of data sample

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

**Number of Parameters included:**

</td>  
<td>

</td>  
<td>

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

**Parameter #1:**

</td>  
<td>

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

</td>  
<td>

…

</td>  
<td>

…

</td>  
<td>

…

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

**Parameter #2:**

</td>  
<td>

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

</td>  
<td>

**…**

</td>  
<td>

**…**

</td>  
<td>

**…**

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

The Energy-Infrastructure Monitoring Parameters’ Semantic Model and Citizens
Environment Friendly Behavioural Semantic Model form a semantic metadata in an
integrated manner. This document contains the initial versions of the both
models. More detailed information about the models will be presented in their
own deliverables.

Figure 1 represents the concepts and parameters - along with their
relationships- we will adopt for collecting information from the different
type of sensors from an energy efficiency perspective. The types of sensors
refer mainly to energy consumption, production and storage meters. This
semantic model is fully extensible, it’s evolution with the addition of new
concepts -or even the refinement of part of the existing concepts- will be an
evolving process.

**Figure 1** : ENTROPY Energy Efficiency Semantic Model

A building space (BuildingSpace) in ENTROPY Energy Model defines the physical
spaces of the building. A building space contains devices (DeviceInstance) or
building objects (BuildingObject). A building object is an object in the
building such as a room (Room) of a floor

(Floor) that can contain one or more devices. A Device instance
(DeviceInstance) implements a Device (Device), has a unique id and geolocation
coordinates (latitude, longitude) and is located in a Specific Building
Object. Each Device Instance (DeviceInstance) supports a set of measurements
(Measurement) that are also associated with a set of quantitative and
qualitative (Quality) characteristics (e.g. frequency, accuracy) and units of
measurements (e.g. KWh, bar, m,  o  C etc.) (UnitofMeasure). The values of the
monitored parameters are included in the Observation Values
(ObservationValue). Each observed value is also associated with a timestamp
(Timezone). A building space may be frequented by individuals (Agent) which
could be one person (Person) or group of people (Group).

Figure 2 shows the basic concepts and their relationships in the behavioural
model. This model will be utilized for representing extracted behavioural data
of users. It includes concepts representing demographic data, as well as
activity data and user’s context information. The ontology borrows concepts
from external ontologies and vocabularies when appropriate, in order to
increase reusability. For instance, initial model uses Agent, Person and
OnlineAccount concepts from the FOAF  1  vocabulary. As stated in deliverable
D1.1, reuse of other existing ontologies also will be considered in the later
versions of this model.

**Figure 2** : Initial concepts of the behavioural model

#  DATA ACCESS AND SHARING

Data access and sharing plan include several aspects that have to be
identified regarding the data resulted from the project. Bellow the issues
regarding the data access and sharing plan are presented in a more detailed
manner.

##  IPRs and Privacy Issues

Data access and sharing activities will be implemented in compliance with the
privacy and data collection rules and regulations, as they are applied
nationally and in the EU, as well as with the H2020 rules. Concerning the
results of the project, these will become publicly available based on the IPRs
as described in the Consortium Agreement.

Due to the nature of the data involved, some of the results that will be
generated by each project phase will be restricted to authorized users, while
other results will be publicly available. Data access and sharing activities
will be rigorously implemented in compliance with the privacy and data
collection rules and regulations, as they are applied nationally and in the
EU, as well as with the H2020 rules. One possibility would be to ask users to
pre-register for the purpose of using the system and will then need to
authenticate them against a user database. If successful, the users will have
roles associated with them. These roles will determine the level of access
that a user will be given and what they will be permitted to do.

##  Methods for Data Sharing

As the raw data included in the data sources, will be gathered from sensor
nodes and information management systems, those could be seen as highly
commercially-sensitive. Therefore, access to raw data can only take place
between the specific end users and the partners involved in the analysis of
the data. For the models to function correctly, the data will have to be
included into the ENTROPY repository. The results of the data analytics in the
orient phase are set to be anonymised and made available to the subsequent
layers of the framework, which will then allow the possibility for external
industry stakeholders to use the results of the project for their own
purposes. Publications will be released and disseminated through the project
dissemination and exploitation channels to make these parties aware of the
project as well as appropriate access to the data. Additionally, data that are
eligible for public distribution may be disseminated through:

  * Scientific papers 

  

  * Lectureships in case of Universities 

  

  * Dissemination via the appropriate channels of the project 

  

  * Interest groups created by the project’s partners 

  

Rather than the raw data used, there will be knowledge obtained by applying
analytics processes to low level information in order to extract behavioural
information about users. Such behavioural data that will be collected
throughout the project, or a fragment of it, will be published by following
the linked data principles  2  :

  * Use URIs to name (identify) things. 

  

  * Use HTTP URIs so that these things can be looked up (interpreted, "dereferenced"). 

  

  * Provide useful information about what a name identifies when it's looked up, using open standards such as RDF, SPARQL, etc. 

  

  * Refer to other things using their HTTP URI-based names when publishing data on the Web. 

  

Open access to the anonymized behavioural data will be provided by means of
periodic data dumps and read-only SPARQL endpoints.

#  ARCHIVING AND PRESERVATION

####  _Short Term_

All original raw data files and respective processing programs will be
versioned over time and maintained in a date-stamped file structure. Access to
the datasets will be given only after request and during the design phases of
the project to the responsible person. These datasets will be automatically
backed up on a nightly and monthly basis.

Respectively, the data generated by the system during the pilots of the
project will be stored to the database of ENTROPY platform, whose DB schema
will reflect the aforementioned pilot parameters. Back-ups of the DB will be
performed and stored on a monthly-basis. Also, the datasets will be
automatically backed up on a nightly and monthly basis.

####  _Long Term_

The project consortium is committed to make the high quality final data
generated by ENTROPY available for use by the research community, as well as
industry peers. We will identify appropriate platform solutions (e.g.
_https://joinup.ec.europa.eu/_ and  _http://ckan.org/_ )  that will allow the
sustainable archiving of all the ENTROPY datasets after the life span of the
project.