#  1\. INTRODUCTION

This deliverable constitutes the final Data Management Plan Implementation of
the ENTROPY project. The main objective of this deliverable is to provide the
overall update relevant to the data management policy with regards to the data
sources that the ENTROPY project collects, processes, generates and makes
available. It takes into account the new data, changes in the consortium
policies as derived from the innovation potential of the project and it
follows the Horizon 2020 FAIR DMP approach.

Overall, ENTROPY follows the FAIR approach followed in H2020 as it presents
research data that are findable, accessible, interoperable and re-usable as
depicted in the following chapters.

In Chapter 1 Data Summary, the ENTROPY datasets are presented alongside with
the overall purpose for collection, alignment with the objectives, origin of
data and expected size of them. Chapter 2 outlines the FAIR data approach and
measures taken pertinent to data. In this chapter the detailed description of
the datasets made open is conducted alongside with the means to access them.
Chapter 3 describes the resources allocation and Chapter 4 the provisions
taken during and past the project lifecycle pertinent to data security.
Chapter 5 relates to any issues relevant to the open data and Chapter 6
presents all the relevant information pertinent to the forms utilized in the
project in an Appendix format.

#  2\. DATA SUMMARY

This section describes the basic data collected and generated throughout the
lifetime of the ENTROPY Project in relevance to the platform, the apps
developed and the pilots. Following the evolution of the ENTROPY project, the
data collected and generated are reflective of the three pilots where ENTROPY
was deployed and evaluated: (1) PILOT A: Navacchio Technology Park (POLO), (2)
PILOT B: University of Murcia Campus (UMU) and (3) PILOT C: Technopole in
Sierre (HES-SO). The data sets collected and generated by each pilot differ to
each other, since the pilots differ in terms of sensing devices, context and
users, however some data are applicable. For each of these three target
groups/deployments, several parameters have been identified by each pilot and
the data received by external sources will fill in these parameters.

The overall purpose of data collection / generation in ENTROPY was to enable
the identification of Energy Consumption, Building setup and Participant
actions relevant to Energy Efficiency and the potential to reduce their
overall energy consumption relevant to current conditions in the place of
application. The consortium took the necessary measures to ensure that the
necessary amount and type of data was collected in order to meet the
technological and scientific objectives of ENTROPY.

The aforementioned necessary data collected and then processed adhere to User
Demographics, Building Data, Sensing Data, Environmental data and Energy data
and the types and formats of the data are presented in detail, in the
following sections globally, alongside with the data in the Personal App
(PersoApp) and the Treasure Hunt Serious game (TH). Additionally, data related
to energy performance characteristics of the considered areas and subareas, as
well as open data regarding environmental conditions in the past, were re-used
to assist in setting the baselines and calibrating the system. Following the
presentation of the data collected / generated in the lifecycle of the ENTROPY
project, a table of the datasets that will be made available is presented
alongside with the relevant information in the following sections.

##  2.1 Datasets

###  2.1.1 Users Data / Building Data / Sensing Data

The following tables present the data collected / processed in the main
ENTROPY platform during the course of the ENTROPY project. Part of such data
is only collected for creation of the behavioral profiles of the end users and
is anonymized upon completion of relevant questionnaires.  
  
<table>  
<tr>  
<th>

**Parameter**

</th>  
<th>

**Type**

</th>  
<th>

**Unit**

</th>  
<th>

**Mandatory**

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

**USERS DEMOGRAPHICS**

</td>  
<td>

</td>  
<td>

</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>

Function / Role (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>

Hours at university/campus / Working hours

</td>  
<td>

Numeric

</td>  
<td>

hours

</td>  
<td>

N

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

Energy Awareness Level

</td>  
<td>

Numeric

</td>  
<td>

\-

</td>  
<td>

N

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

**BUILDING DATA**

</td>  
<td>

</td>  
<td>

</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>

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>

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>

**SENSING DATA**

</td>  
<td>

</td>  
<td>

</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> </table>  
<table>  
<tr>  
<th>

Energy consumption

</th>  
<th>

Numeric

</th>  
<th>

KWh

</th>  
<th>

Y

</th> </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>

**Humidity 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>

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>  
<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 (daily radiation average)

</td>  
<td>

N

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

###  2.1.2 ENTROPY Personal App Data

The following tables present the data collected / processed relevant to the
Personal App during the course of the ENTROPY project.  
  
<table>  
<tr>  
<th>

**Parameter**

</th>  
<th>

**Data**

</th>  
<th>

**Type**

</th>  
<th>

**Unit**

</th>  
<th>

**Mandatory**

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

PERSONAL APP DATA

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Authentication token form user sign in**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

username

</td>  
<td>

The user name of the participant

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

password

</td>  
<td>

The password of the participant

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**Consumption profile data of all the registered buildings**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

energyConsuptionPerSqMeter

</td>  
<td>

Energy consumption per sqr meter

</td>  
<td>

Integer

</td>  
<td>

kWh

</td>  
<td>

Y

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

buildingSpace

</td>  
<td>

Building surface in sqr meters

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

energyConsumptionPerOccupa nt

</td>  
<td>

kWh per occupant in building room

</td>  
<td>

Integer

</td>  
<td>

kWh

</td>  
<td>

Y

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

**Consumption profile data of a building**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

energyConsuptionPerSqMeter

</td>  
<td>

Energy consumption per sqr meter

</td>  
<td>

Integer

</td>  
<td>

kWh

</td>  
<td>

Y

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

buildingSpace

</td>  
<td>

Building surface in sqr meters

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

EnergyConsumptionComparis onWeekly

</td>  
<td>

Energy consumption

</td>  
<td>

Integer

</td>  
<td>

kWh

</td>  
<td>

Y

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

**Building subAreas**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

returnobject

</td>  
<td>

Number of areas in buildings

</td>  
<td>

Array

</td>  
<td>

\-

</td>  
<td>

Y

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

**All building space areas**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

returnobject

</td>  
<td>

Number of areas in buildings

</td>  
<td>

Array

</td>  
<td>

\-

</td>  
<td>

Y

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

**Observation Values from a Sensor**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

sensor_data_stream_id

</td>  
<td>

The unique URL id of a Sensor Data Stream

</td>  
<td>

URL

</td>  
<td>

\-

</td>  
<td>

Y

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

dateFrom

</td>  
<td>

Timestamp

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

dateTo

</td>  
<td>

Timestamp

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**All Recommendations per end user**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Username

</td>  
<td>

User name

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

recommendationType

</td>  
<td>

Type of Recommendation

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

status

</td>  
<td>

Recommendation status

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

App_name

</td>  
<td>

App name

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**Positive or Negative Feedback from a Recommendation**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

id

</td>  
<td>

ID of recommendation

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

App_name

</td>  
<td>

App name

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

feedback

</td>  
<td>

Positive or Negative

</td>  
<td>

Boolean

</td>  
<td>

\-

</td>  
<td>

Y

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

points

</td>  
<td>

User points earned

</td>  
<td>

Integer

</td>  
<td>

\-

</td>  
<td>

Y

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

Status

</td>  
<td>

Recommendation status

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Custom_attributes

</td>  
<td>

Attributes

</td>  
<td>

JSONObject

</td>  
<td>

\-

</td>  
<td>

Y

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

**SensorDataStreams per building for a list of attributes**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Temperature

</td>  
<td>

Room temperature

</td>  
<td>

String

</td>  
<td>

celsius, lux,

</td>  
<td>

Y

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

CO2

</td>  
<td>

Room C02

</td>  
<td>

String

</td>  
<td>

ppm,w/h

</td>  
<td>

Y

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

**User profile per app**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

playerCharacter

</td>  
<td>

Pic of the player

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

totalScore

</td>  
<td>

Score of the player in total

</td>  
<td>

Integer

</td>  
<td>

\-

</td>  
<td>

Y

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

Ranking

</td>  
<td>

Player ranking in leader board

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Badges

</td>  
<td>

Player badges in leader board

</td>  
<td>

Object

</td>  
<td>

\-

</td>  
<td>

Y

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

**A new Action**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

App_name

</td>  
<td>

Name of the app based on Pilot location

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Building_name

</td>  
<td>

Building name where the action took place

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

validatable

</td>  
<td>

Is action validatable?

</td>  
<td>

Boolean

</td>  
<td>

\-

</td>  
<td>

Y

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

Score

</td>  
<td>

Points to gain for this action

</td>  
<td>

Integer

</td>  
<td>

\-

</td>  
<td>

Y

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

badge

</td>  
<td>

Name of the badge for this action

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

###  2.1.3 ENTROPY Serious Games Data

The following tables present the data collected / processed relevant to the
Treasure Hunt during the course of the ENTROPY project.  
  
<table>  
<tr>  
<th>

**Parameter**

</th>  
<th>

**Data**

</th>  
<th>

**Type**

</th>  
<th>

**Unit**

</th>  
<th>

**Mandatory**

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

SERIOUS GAME DATA

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Authentication token form user sign in**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

username

</td>  
<td>

The user name of the participant

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

password

</td>  
<td>

The password of the participant

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**Observation Values from a Sensor**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

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

Sensor_data_stream_id

</td>  
<td>

The unique URL id of a Sensor Data Stream

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

dateFrom

</td>  
<td>

Start date

</td>  
<td>

String

</td>  
<td>

date

</td>  
<td>

Y

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

dateTo

</td>  
<td>

End date

</td>  
<td>

String

</td>  
<td>

date

</td>  
<td>

Y

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

**All Recommendations per end user**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

username

</td>  
<td>

The user name of the participant

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

status

</td>  
<td>

Status of recommendation

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

app_name

</td>  
<td>

Application name

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

recommendationType

</td>  
<td>

Type of recommendation (e.g. task)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**User Profile per Application**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

app_name

</td>  
<td>

Name of the game

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

playerCharacter

</td>  
<td>

Character of the player

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

lastscore

</td>  
<td>

The last score of the player

</td>  
<td>

Integer

</td>  
<td>

\-

</td>  
<td>

Y

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

lastRanking

</td>  
<td>

The last rank of the player

</td>  
<td>

Integer

</td>  
<td>

\-

</td>  
<td>

Y

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

buildingSpace

</td>  
<td>

The building where the game is played

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

custom_attributes

</td>  
<td>

The list of badges

</td>  
<td>

Array of Strings

</td>  
<td>

\-

</td>  
<td>

Y

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

**Positive or Negative Feedback from a Recommendation**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Id

</td>  
<td>

ID of recommendation

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

app_name

</td>  
<td>

Name of the game

(e.g. TH POLO, TH UMU, TH HESSO)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Feedback

</td>  
<td>

The feedback from the recommendation "POSITIVE" or "NEGATIVE"

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

Points

</td>  
<td>

Number of points won for the completed task/action

</td>  
<td>

Integer

</td>  
<td>

\-

</td>  
<td>

Y

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

**A new Action**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

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

app_name

</td>  
<td>

The name of the app based on the Pilot location

(e.g. TH POLO, TH UMU, TH HESSO)

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

building_name

</td>  
<td>

The building name where the action took place

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

validatable

</td>  
<td>

Is action possible to validate

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

score

</td>  
<td>

The points to gain for this action

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

badge

</td>  
<td>

The name of the badge that can be won for this action

</td>  
<td>

String

</td>  
<td>

\-

</td>  
<td>

Y

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

**SensorDataStreams per building for a list of attributes**

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

Temperature

</td>  
<td>

</td>  
<td>

Integer

</td>  
<td>

Celsius

</td>  
<td>

Y

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

Luminosity

</td>  
<td>

</td>  
<td>

Integer

</td>  
<td>

Lux

</td>  
<td>

Y

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

CO2

</td>  
<td>

</td>  
<td>

Integer

</td>  
<td>

ppm

</td>  
<td>

Y

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

active power

</td>  
<td>

</td>  
<td>

Float

</td>  
<td>

w/h

</td>  
<td>

Y

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

##  2.2 The ENTROPY datasets

The previous tables presented the basic data collected and processed in the
course of the ENTROPY Project. Out of the aforementioned collected data,
different datasets are produced as presented in the following table.  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**Data Type**

</th>  
<th>

**Origin**

</th>  
<th>

**WP**

</th>  
<th>

**Format**

</th>  
<th>

**Overall size**

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

1

</td>  
<td>

POLO Sensor Observation Data

</td>  
<td>

Primary Data, Pilots

</td>  
<td>

5

</td>  
<td>

.jsonld

</td>  
<td>

> 5GB

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

2

</td>  
<td>

POLO Recommendation Data

</td>  
<td>

Primary Data, Pilots

</td>  
<td>

5

</td>  
<td>

.jsonld

</td>  
<td>

> 50 MB

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

3

</td>  
<td>

UMU-Pleiades Sensor Observation Data

</td>  
<td>

Primary Data, Pilots

</td>  
<td>

5

</td>  
<td>

.jsonld

</td>  
<td>

> 8 GB

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

4

</td>  
<td>

UMU-Pleiades Recommendation

Data

</td>  
<td>

Primary Data, Pilots

</td>  
<td>

5

</td>  
<td>

.jsonld

</td>  
<td>

> 100 MB

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

5

</td>  
<td>

UMU-Lanave Sensor Observation

Data

</td>  
<td>

Primary Data, Pilots

</td>  
<td>

5

</td>  
<td>

.jsonld

</td>  
<td>

> 1 GB

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

6

</th>  
<th>

UMU-Lanave Recommendation Data

</th>  
<th>

Primary Data, Pilots

</th>  
<th>

5

</th>  
<th>

.jsonld

</th>  
<th>

> 10 MB
</th> </tr>  
<tr>  
<td>

7

</td>  
<td>

HESSO Sensor Observation Data

</td>  
<td>

Primary Data, Pilots

</td>  
<td>

5

</td>  
<td>

.jsonld

</td>  
<td>

> 5 GB
</td> </tr>  
<tr>  
<td>

8

</td>  
<td>

HESSO Recommendation Data

</td>  
<td>

Primary Data, Pilots

</td>  
<td>

5

</td>  
<td>

.jsonld

</td>  
<td>

> 20 MB
</td> </tr>  
<tr>  
<td>

9

</td>  
<td>

Serious Game Analytics Data

</td>  
<td>

Primary Data, Pilots

</td>  
<td>

5

</td>  
<td>

.jsonld

</td>  
<td>

400 kB

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

10

</td>  
<td>

Perso app data

</td>  
<td>

Primary Data, Pilots

</td>  
<td>

5

</td>  
<td>

.jsonld

</td>  
<td>

1 MB

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

11

</td>  
<td>

Campaign Users Interaction Data (data per campaign)

</td>  
<td>

Primary Data

</td>  
<td>

5

</td>  
<td>

Raw Data in

MongoDb

</td>  
<td>

> 50MB
</td> </tr> </table>

The following table describes the data sets and the purpose of the data
collection or data generation in relation with the objectives of the project
in detail. Additionally, it shows the data utility for clarifying to whom the
data might be useful.  
  
<table>  
<tr>  
<th>

**#**

</th>  
<th>

**Data Type**

</th>  
<th>

**Description and Purpose**

</th>  
<th>

**Utility**

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

1

</td>  
<td>

POLO Sensor

Observation Data

</td>  
<td>

**Description:** The POLO Sensor Observation Data contains the data from all
sensors distributed in the different rooms used for the campaigns

**Purpose:** The POLO Sensor Observation Data are used as input for the
recommendation engine, producing recommendations when the defined rule
conditions are accomplished. Also is used to inform participants about the
current status of variables like indoor and outdoor temperature, CO2 levels,
humidity, etc. And last but not least, all gathered data from sensors are used
to evaluate if campaigns have influenced in energy consumption and comfort.

</td>  
<td>

The POLO Sensor

Observation Data can be used by other researchers working in the field of
energy savings in building.

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

2

</td>  
<td>

POLO

Recommendation

Data

</td>  
<td>

**Description:** The POLO Recommendation Data contains the data from the
recommendation engine, templates and rules definition and all the statistics
about them, i.e., how many times a rule has been triggered in a determined
campaign and the responsiveness of the participant.

**Purpose:** The POLO Recommendation Data are used to analyse the result of
campaigns, the participants behaviour during campaigns and evaluate their
responsiveness.

</td>  
<td>

The POLO Recommendation Data can be used by other researchers working in the
field of behavioural change.

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

3

</th>  
<th>

UMU-Pleiades

Sensor

Observation Data

</th>  
<th>

**Description:** The UMU Sensor Observation Data contains the data from all
sensors distributed in the different rooms used for the campaigns

**Purpose:** The UMU Sensor Observation Data are used as input for the
recommendation engine, producing recommendations when the defined rule
conditions are accomplished. Also is used to inform participants about the
current status of variables like indoor and outdoor temperature, CO2 levels,
humidity, etc. And last but not least, all gathered data from sensors are used
to evaluate if campaigns have influenced in energy consumption and comfort.

</th>  
<th>

The UMU Sensor Observation Data can be used by other researchers working in
the field of energy savings in building.

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

4

</td>  
<td>

UMU-Pleiades

Recommendation

Data

</td>  
<td>

**Description:** The UMU Recommendation Data contains the data from the
recommendation engine, templates and rules definition and all the statistics
about them, i.e., how many times a rule has been triggered in a determined
campaign and the responsiveness of the participant.

**Purpose:** The UMU Recommendation Data are used to analyse the result of
campaigns, the participants behaviour during campaigns and evaluate their
responsiveness.

</td>  
<td>

The UMU Recommendation Data can be used by other researchers working in the
field of behavioural change.

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

5

</td>  
<td>

UMU-LaNave

Sensor

Observation Data

</td>  
<td>

**Description:** The LaNave Sensor Observation Data contains the data from all
sensors distributed in the different rooms used for the campaigns

**Purpose:** The LaNave Sensor Observation Data are used as input for the
recommendation engine, producing recommendations when the defined rule
conditions are accomplished. Also is used to inform participants about the
current status of variables like indoor and outdoor temperature, CO2 levels,
humidity, etc. And last but not least, all gathered data from sensors are used
to evaluate if campaigns have influenced in energy consumption and comfort.

</td>  
<td>

The LaNave Sensor

Observation Data can be used by other researchers working in the field of
energy savings in building.

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

6

</td>  
<td>

UMU-LaNave

Recommendation

Data

</td>  
<td>

**Description:** The LaNave Recommendation Data contains the data from the
recommendation engine, templates and rules definition and all the statistics
about them, i.e., how many times a rule has been triggered in a determined
campaign and the responsiveness of the participant.

**Purpose:** The LaNave Recommendation Data are used to analyse the result of
campaigns, the participants’ behaviour during campaigns and evaluate their
responsiveness.

</td>  
<td>

The LaNave Recommendation Data can be used by other researchers working in the
field of behavioural change.

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

7

</td>  
<td>

HESSO Sensor Observation Data

</td>  
<td>

**Description:** The HESSO Sensor Observation Data contains the measurement
data collected from various sensor streams

**Purpose:** The HESSO Sensor Observation Data are used to calculate energy
baselines as well as to decide when recommendations would be fired and how
they would be validated.

</td>  
<td>

The HESSO Sensor

Observation Data can be used by other researchers working in the field of
Energy in order to test their data analytics algorithms and conduct

literature review

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

8

</td>  
<td>

HESSO

Recommendation

Data

</td>  
<td>

**Description:** The HESSO Recommendation Data contains the data of
recommendation templates created by campaign managers

**Purpose:** The HESSO Recommendation Data are used to intervene users’ energy
consumption behaviour to achieve energy savings.

</td>  
<td>

The HESSO Recommendation Data can be used by other researchers working in the
field of Energy in order to have basis for what kind of data should be
represented in terms of behavioural interventions for energy efficiency.

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

9

</td>  
<td>

Serious Game Analytics Data

</td>  
<td>

**Description:** The serious game analytics data contains relevant data for
player interaction with the game elements (e.g. number of logins, number of
actions read, number of actions completes, time spent doing an action etc.).
More details are given in D5.4.

**Purpose:** The Serious Game Analytics Data was used for KPI calculation, as
a basis for game modifications in order to improve KPIs

</td>  
<td>

The Serious Game Analytics data can be used by the game designers to provide
indication how different elements of the game are used, interacted with and
how different gamification elements are used, and whether they provide
motivation to the players. Also the level of difficulty of the questions is
estimated based on total number of correctly answered questions.

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

10

</td>  
<td>

Personal App data.

</td>  
<td>

**Description:** The Personal App data contains all appropriate data sets and
streams required for a player to engage and interact with the mobile app. It
uses credential data, sensor streams and also educational content interaction
data (click streams, quizzes taken, tips read, user actions, content
interaction results, user views, dashboard views, educational results, points
taken and leader-board, QR location scan, etc)

**Purpose:** The purpose is to use the data sets in order to measure various
digital interaction KPIs, user engagement and user knowledge through the

Entropy platform applied on pilot sites

</td>  
<td>

The Perso App data sets and the relevant KPIs that were created (engagement,
knowledge) can be used from researchers and digital marketers in order to
evaluate, analyse and optimize various digital marketing techniques, to
research new ways of customer engagement and

KPIs to measure it, to evaluate digital content and to generate new ways of
customer

interactions, over mobile apps

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

11

</td>  
<td>

Campaign Users

Interaction Data

(data per campaign)

</td>  
<td>

**Description:** The set of campaign users interaction data regard the data
collected per campaign with regards to the interaction of end users with the
applications, in terms of responsiveness to recommendations and evolution

</td>  
<td>

Such data may be used by other researchers mainly for realisation of extended
behavioural analysis and comparison with similar interventions in other

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

</th>  
<th>

</th>  
<th>

of their application profiles.

**Purpose:** Used to evaluate the behavioural change of end users and adapt
accordingly the provided recommendations.

</th>  
<th>

buildings. Such data may be provided upon full anonymization.

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

#  3\. ENTROPY FAIR DATA

##  3.1 Making data findable, including provisions for metadata

The ENTROPY project is related to different pillars, e.g., green energy,
environment, etc. This section presents the open datasets and the provisions
for making the data findable and presents the metadata form adopted in the
ENTROPY project (APPENDIX 1) filled in relation to the datasets. As a general
rule, the sensor observations are aggregated four times a day. The
recommendations will be opened after the user identifiers are going to be
anonymized and all profile information is left out.

###  3.1.1 Dataset: POLO Sensor Measurements  
  
<table>  
<tr>  
<th>

**Polo Tecnologico di Navacchio.ttl**

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

Document version

</td>  
<td>

v1

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

Document format

</td>  
<td>

.jsonld

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

Description

</td>  
<td>

This dataset contains sensor measurements from POLO building of Navacchio
Technology Park Pilot

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

Date

</td>  
<td>

2018-11-27

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

Keywords

</td>  
<td>

sensor, energy, infrastructure

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

Subject

</td>  
<td>

This data is sourced from several sensors with different properties

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

**Creator (NTP)**

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

Sector of the provider

</td>  
<td>

University

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

Permissions

</td>  
<td>

CC-BY-SA 4.0

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

**Name of the Partner (NTP)**

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

Responsible person

</td>  
<td>

Giulia Gori (Campaign Manager)

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

Pilot

</td>  
<td>

NTP – POLO

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

Scenario of data usage

</td>  
<td>

Data collected through several sensor data streams

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

**Description of the Data Source**

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

File format

</td>  
<td>

JSON-LD (.jsonld)

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

File name/path

</td>  
<td>

POLO-sensor.jsonld

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

Storage location

</td>  
<td>

https://  _entropy-opendata.inf.um.es_

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

Data type

</td>  
<td>

JSON-LD, .jsonld

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

Standard

</td>  
<td>

RDF

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

Data size

</td>  
<td>

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

Time references of data

</td>  
<td>

2018/02/28

</td>  
<td>

2018/11/16

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

Availability

</td>  
<td>

2018/02/28

</td>  
<td>

2018/11/16

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

Data collection frequency

</td>  
<td>

Aggregated to 4 times a day

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

Data quality

</td>  
<td>

Complete, available, right collection frequency

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

**Observation Values**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

isObservedBy

</td>  
<td>

Observed by Sensor

</td>  
<td>

OCBSensor

</td>  
<td>

Yes

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

isProducedBy

</td>  
<td>

Produced by Sensor Data Stream

</td>  
<td>

SensorDataStream

</td>  
<td>

Yes

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

inDateTime

</td>  
<td>

Observation Date

</td>  
<td>

Date

</td>  
<td>

Yes

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

hasValue

</td>  
<td>

Observation Value

</td>  
<td>

Double

</td>  
<td>

Yes

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

isUsedFor

</td>  
<td>

Property the Observation Value used for

</td>  
<td>

URI

</td>  
<td>

Yes

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

isMeasuredIn

</td>  
<td>

Unit of measure

</td>  
<td>

UnitOfMeasure

</td>  
<td>

Yes

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

hasSampleFrequency

</td>  
<td>

Sampling Frequency

</td>  
<td>

String

</td>  
<td>

Yes

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

**OCBSensor:**

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

Variables

</td>  
<td>

Name

</td>  
<td>

Type

</td>  
<td>

Mandatory

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

@id

</td>  
<td>

Sensor URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

deviceCategory

</td>  
<td>

Sensor Type

</td>  
<td>

URI

</td>  
<td>

Yes

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

attributes

</td>  
<td>

List of sensor attributes

</td>  
<td>

List<String>

</td>  
<td>

Yes

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

isLocatedIn

</td>  
<td>

Building Space URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

**SensorDataStream:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

comesFrom

</td>  
<td>

Sensor

</td>  
<td>

OCBSensor

</td>  
<td>

Yes

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

hasMonitoringType

</td>  
<td>

Monitoring Type

</td>  
<td>

String

</td>  
<td>

Yes

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

###  3.1.2 Dataset: POLO Recommendation Data  
  
<table>  
<tr>  
<th>

**Polo Tecnologico di Navacchio.ttl**

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

Document version

</td>  
<td>

v1

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

Document format

</td>  
<td>

.jsonld

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

Description

</td>  
<td>

This dataset contains recommendation sent to users from POLO building of
Navacchio Technology Park Pilot

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

Date

</td>  
<td>

2018-11-27

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

Keywords

</td>  
<td>

sensor, energy, infrastructure

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

Subject

</td>  
<td>

This data is generated by campaign managers and sent to users by rule firings

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

**Creator (NTP)**

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

Sector of the provider

</td>  
<td>

University

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

Permissions

</td>  
<td>

CC-BY-SA 4.0

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

**Name of the Partner (NTP)**

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

Responsible person

</td>  
<td>

Giulia Gori (Campaign Manager)

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

Pilot

</td>  
<td>

NTP – POLO

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

Scenario of data usage

</td>  
<td>

Data created based on rule firings based on collected sensor data

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

**Description of the Data Source**

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

File format

</td>  
<td>

JSON-LD (.jsonld)

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

File name/path

</td>  
<td>

POLO-recommendation.jsonld

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

Storage location

</td>  
<td>

https://  _entropy-opendata.inf.um.es_

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

Data type

</td>  
<td>

JSON-LD, .jsonld

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

Standard

</td>  
<td>

RDF

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

Data size

</td>  
<td>

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

Time references of data

</td>  
<td>

2018/02/28

</td>  
<td>

2018/11/16

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

Availability

</td>  
<td>

2018/02/28

</td>  
<td>

2018/11/16

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

Data collection frequency

</td>  
<td>

Per rule firing, per campaign

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

Data quality

</td>  
<td>

Complete, available, right collection frequency

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

**Observation Values:**

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

**Recommendation:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

recommendationRule

</td>  
<td>

Rule URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

Feedback

</td>  
<td>

User’s feedback,positive or negative or null

</td>  
<td>

String

</td>  
<td>

Yes

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

inDateTime

</td>  
<td>

Recommendation sending time

</td>  
<td>

Datetime

</td>  
<td>

Yes

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

triggeringAttributes

</td>  
<td>

List of attributes that is involved with the rule

</td>  
<td>

List<String>

</td>  
<td>

No

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

**RecommendationRule:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation Rule URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

conditionRule

</td>  
<td>

Rule triggering condition

</td>  
<td>

String

</td>  
<td>

Yes

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

userRule

</td>  
<td>

User selection rule

</td>  
<td>

String

</td>  
<td>

Yes

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

areaRule

</td>  
<td>

The condition that selects the area

</td>  
<td>

String

</td>  
<td>

Yes

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

isValidatedBy

</td>  
<td>

Action that validates the recommendation

</td>  
<td>

URI

</td>  
<td>

No

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

recommendationTemplat

</td>  
<td>

The template the rule is

</td>  
<td>

URI

</td>  
<td>

Yes

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

e

</td>  
<td>

based on

</td>  
<td>

</td>  
<td>

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

**RecommendationTemplate:**

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation Template URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

Name

</td>  
<td>

Name of the recommendation template

</td>  
<td>

String

</td>  
<td>

Yes

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

Description

</td>  
<td>

Descriptive Content of the Recommendation

</td>  
<td>

String

</td>  
<td>

Yes

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

difficultyLevel

</td>  
<td>

Level of difficulty, Low Medium or High

</td>  
<td>

String

</td>  
<td>

Yes

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

@type

</td>  
<td>

Type of recommendation from the behavioural ontology

</td>  
<td>

URI

</td>  
<td>

Yes

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

showOnCompletion

</td>  
<td>

The message shown after completion

</td>  
<td>

String

</td>  
<td>

Yes

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

**ActionValidation:**

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

duration

</td>  
<td>

Maximum duration before validation in seconds

</td>  
<td>

Integer

</td>  
<td>

Yes

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

conditionRules

</td>  
<td>

The condition that validates if the recommended activity has been carried

</td>  
<td>

String

</td>  
<td>

Yes

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

###  3.1.3 Dataset: UMU-Pleiades Sensor Measurements  
  
<table>  
<tr>  
<th>

**UmuPleiadesFinalSensorMeasurements.ttl**

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

Document version

</td>  
<td>

v1

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

Document format

</td>  
<td>

.jsonld

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

Description

</td>  
<td>

This dataset contains sensor measurements from Pleiades building of UMU Pilot

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

Date

</td>  
<td>

2018-11-27

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

Keywords

</td>  
<td>

sensor, energy, infrastructure

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

Subject

</td>  
<td>

This data is sourced from several sensors with different properties

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

**Creator (UMU)**

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

Sector of the provider

</td>  
<td>

University

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

Permissions

</td>  
<td>

CC-BY-SA 4.0

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

**Name of the Partner (UMU)**

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

Responsible person

</td>  
<td>

Pedro J. Fernandez (Campaign manager of UMU and La Nave)

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

Pilot

</td>  
<td>

UMU – Pleiades

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

Scenario of data usage

</td>  
<td>

Data collected through several sensor data streams

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

**Description of the Data Source**

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

File format

</td>  
<td>

JSON-LD (.jsonld)

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

File name/path

</td>  
<td>

Pleiades-sensor.jsonld

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

Storage location

</td>  
<td>

https://  _entropy-opendata.inf.um.es_

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

Data type

</td>  
<td>

JSON-LD, .jsonld

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

Standard

</td>  
<td>

RDF

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

Data size

</td>  
<td>

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

Time references of data

</td>  
<td>

2017/04/12

</td>  
<td>

2018/11/27

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

Availability

</td>  
<td>

2017/04/12

</td>  
<td>

2018/11/27

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

Data collection frequency

</td>  
<td>

Aggregated to 4 times a day

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

Data quality

</td>  
<td>

Complete, available, right collection frequency

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

**ObservationValue:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

isObservedBy

</td>  
<td>

Observed by Sensor

</td>  
<td>

OCBSensor

</td>  
<td>

Yes

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

isProducedBy

</td>  
<td>

Produced by Sensor Data Stream

</td>  
<td>

SensorDataStream

</td>  
<td>

Yes

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

inDateTime

</td>  
<td>

Observation Date

</td>  
<td>

Date

</td>  
<td>

Yes

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

hasValue

</td>  
<td>

Observation Value

</td>  
<td>

Double

</td>  
<td>

Yes

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

isUsedFor

</td>  
<td>

Property the Observation Value used for

</td>  
<td>

URI

</td>  
<td>

Yes

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

isMeasuredIn

</td>  
<td>

Unit of measure

</td>  
<td>

UnitOfMeasure

</td>  
<td>

Yes

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

hasSampleFrequency

</td>  
<td>

Sampling Frequency

</td>  
<td>

String

</td>  
<td>

Yes

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

**OCBSensor:**

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

Variables

</td>  
<td>

Name

</td>  
<td>

Type

</td>  
<td>

Mandatory

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

@id

</td>  
<td>

Sensor URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

deviceCategory

</td>  
<td>

Sensor Type

</td>  
<td>

URI

</td>  
<td>

Yes

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

attributes

</td>  
<td>

List of sensor attributes

</td>  
<td>

List<String>

</td>  
<td>

Yes

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

isLocatedIn

</td>  
<td>

Building Space URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

**SensorDataStream:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

comesFrom

</td>  
<td>

Sensor

</td>  
<td>

OCBSensor

</td>  
<td>

Yes

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

hasMonitoringType

</td>  
<td>

Monitoring Type

</td>  
<td>

String

</td>  
<td>

Yes

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

###  3.1.4 Dataset: UMU-Pleiades Recommendation Data  
  
<table>  
<tr>  
<th>

**UmuPleiadesFinalRecommendations.ttl**

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

Document version

</td>  
<td>

v1

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

Document format

</td>  
<td>

.jsonld

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

Description

</td>  
<td>

This dataset contains recommendation sent to users from Pleiades building of
UMU Pilot

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

Date

</td>  
<td>

2018-11-27

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

Keywords

</td>  
<td>

sensor, energy, infrastructure

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

Subject

</td>  
<td>

This data is generated by campaign managers and sent to users by rule firings

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

**Creator (UMU)**

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

Sector of the provider

</td>  
<td>

University

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

Permissions

</td>  
<td>

CC-BY-SA 4.0

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

**Name of the Partner (UMU)**

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

Responsible person

</td>  
<td>

Pedro J. Fernandez (Campaign manager)

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

Pilot

</td>  
<td>

UMU – Pleiades

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

Scenario of data usage

</td>  
<td>

Data created based on rule firings based on collected sensor data

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

**Description of the Data Source**

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

File format

</td>  
<td>

JSON-LD (.jsonld)

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

File name/path

</td>  
<td>

Pleiades-recommendation.jsonld

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

Storage location

</td>  
<td>

https://  _entropy-opendata.inf.um.es_

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

Data type

</td>  
<td>

JSON-LD, .jsonld

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

Standard

</td>  
<td>

RDF

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

Data size

</td>  
<td>

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

Time references of data

</td>  
<td>

2017/04/12

</td>  
<td>

2018/11/27

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

Availability

</td>  
<td>

2017/04/12

</td>  
<td>

2018/11/27

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

Data collection frequency

</td>  
<td>

Per rule firing, per campaign

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

Data quality

</td>  
<td>

Complete, available, right collection frequency

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

**Observation Values:**

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

**Recommendation:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

recommendationRule

</td>  
<td>

Rule URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

Feedback

</td>  
<td>

User’s

feedback,positive or negative or null

</td>  
<td>

String

</td>  
<td>

Yes

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

inDateTime

</td>  
<td>

Recommendation sending time

</td>  
<td>

Datetime

</td>  
<td>

Yes

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

triggeringAttributes

</td>  
<td>

List of attributes that is involved with the rule

</td>  
<td>

List<String>

</td>  
<td>

No

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

**RecommendationRule:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation Rule URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

conditionRule

</td>  
<td>

Rule triggering condition

</td>  
<td>

String

</td>  
<td>

Yes

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

userRule

</td>  
<td>

User selection rule

</td>  
<td>

String

</td>  
<td>

Yes

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

areaRule

</td>  
<td>

The condition that selects the area

</td>  
<td>

String

</td>  
<td>

Yes

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

isValidatedBy

</td>  
<td>

Action that validates the recommendation

</td>  
<td>

URI

</td>  
<td>

No

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

recommendationTemp

late

</td>  
<td>

The template the rule is based on

</td>  
<td>

URI

</td>  
<td>

Yes

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

**RecommendationTemplate:**

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation Template URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

Name

</td>  
<td>

Name of the recommendation template

</td>  
<td>

String

</td>  
<td>

Yes

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

Description

</td>  
<td>

Descriptive Content of the Recommendation

</td>  
<td>

String

</td>  
<td>

Yes

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

difficultyLevel

</td>  
<td>

Level of difficulty,

Low Medium or High

</td>  
<td>

String

</td>  
<td>

Yes

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

@type

</td>  
<td>

Type of recommendation from the behavioural ontology

</td>  
<td>

URI

</td>  
<td>

Yes

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

showOnCompletion

</td>  
<td>

The message shown after completion

</td>  
<td>

String

</td>  
<td>

Yes

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

**ActionValidation:**

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

duration

</td>  
<td>

Maximum duration before validation in seconds

</td>  
<td>

Integer

</td>  
<td>

Yes

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

conditionRules

</td>  
<td>

The condition that validates if the recommended activity has been carried

</td>  
<td>

String

</td>  
<td>

Yes

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

###  3.1.5 Dataset: HESSO Sensor Measurement  
  
<table>  
<tr>  
<th>

**HessoFinalSensorMeasurements.ttl**

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

Document version

</td>  
<td>

v1

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

Document format

</td>  
<td>

.jsonld

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

Description

</td>  
<td>

This dataset contains sensor measurements from HES-SO building of Technopole
Sierre Pilot

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

Date

</td>  
<td>

2018-11-27

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

Keywords

</td>  
<td>

sensor, energy, infrastructure

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

Subject

</td>  
<td>

This data is sourced from several sensors with different properties

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

**Creator (HES-SO)**

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

Sector of the provider

</td>  
<td>

University

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

Permissions

</td>  
<td>

CC-BY-SA 4.0

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

**Name of the Partner (HES-SO)**

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

Responsible person

</td>  
<td>

Vincent Schülé (Campaign Manager)

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

Pilot

</td>  
<td>

UMU – La Nave

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

Scenario of data usage

</td>  
<td>

Data collected through several sensor data streams

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

**Description of the Data Source**

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

File format

</td>  
<td>

JSON-LD (.jsonld)

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

File name/path

</td>  
<td>

Hesso-sensor.jsonld

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

Storage location

</td>  
<td>

https://  _entropy-opendata.inf.um.es_

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

Data type

</td>  
<td>

JSON-LD, .jsonld

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

Standard

</td>  
<td>

RDF

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

Data size

</td>  
<td>

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

Time references of data

</td>  
<td>

2017/04/12

</td>  
<td>

2018/11/27

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

Availability

</td>  
<td>

2017/04/12

</td>  
<td>

2018/11/27

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

Data collection frequency

</td>  
<td>

Aggregated to 4 times a day

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

Data quality

</td>  
<td>

Complete, available, right collection frequency

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

**ObservationValue:**

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

**ObservationValue:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

isObservedBy

</td>  
<td>

Observed by Sensor

</td>  
<td>

OCBSensor

</td>  
<td>

Yes

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

isProducedBy

</td>  
<td>

Produced by Sensor Data Stream

</td>  
<td>

SensorDataStream

</td>  
<td>

Yes

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

inDateTime

</td>  
<td>

Observation Date

</td>  
<td>

Date

</td>  
<td>

Yes

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

hasValue

</td>  
<td>

Observation Value

</td>  
<td>

Double

</td>  
<td>

Yes

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

isUsedFor

</td>  
<td>

Property the Observation Value used for

</td>  
<td>

URI

</td>  
<td>

Yes

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

isMeasuredIn

</td>  
<td>

Unit of measure

</td>  
<td>

UnitOfMeasure

</td>  
<td>

Yes

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

hasSampleFrequency

</td>  
<td>

Sampling Frequency

</td>  
<td>

String

</td>  
<td>

Yes

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

**OCBSensor:**

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

Variables

</td>  
<td>

Name

</td>  
<td>

Type

</td>  
<td>

Mandatory

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

@id

</td>  
<td>

Sensor URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

deviceCategory

</td>  
<td>

Sensor Type

</td>  
<td>

URI

</td>  
<td>

Yes

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

attributes

</td>  
<td>

List of sensor attributes

</td>  
<td>

List<String>

</td>  
<td>

Yes

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

isLocatedIn

</td>  
<td>

Building Space URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

**SensorDataStream:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

comesFrom

</td>  
<td>

Sensor

</td>  
<td>

OCBSensor

</td>  
<td>

Yes

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

hasMonitoringType

</td>  
<td>

Monitoring Type

</td>  
<td>

String

</td>  
<td>

Yes

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

###  3.1.6 HESSO Recommendation Data  
  
<table>  
<tr>  
<th>

**HESSOFinalRecommendations.ttl**

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

Document version

</td>  
<td>

v1

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

Document format

</td>  
<td>

.jsonld

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

Description

</td>  
<td>

This dataset contains recommendation sent to users from HES-SO building of
Technopole Sierre Pilot

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

Date

</td>  
<td>

2018-11-27

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

Keywords

</td>  
<td>

sensor, energy, infrastructure

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

Subject

</td>  
<td>

This data is generated by campaign managers and sent to users by rule firings

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

**Creator (UMU)**

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

Sector of the provider

</td>  
<td>

University

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

Permissions

</td>  
<td>

CC-BY-SA 4.0

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

**Name of the Partner (UMU)**

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

Responsible person

</td>  
<td>

Vincent Schülé (Campaign Manager)

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

Pilot

</td>  
<td>

HESSO

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

Scenario of data usage

</td>  
<td>

Data created based on rule firings based on collected sensor data

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

**Description of the Data Source**

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

File format

</td>  
<td>

JSON-LD (.jsonld)

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

File name/path

</td>  
<td>

Hesso-recommendation.jsonld

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

Storage location

</td>  
<td>

https://  _entropy-opendata.inf.um.es_

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

Data type

</td>  
<td>

JSON-LD, .jsonld

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

Standard

</td>  
<td>

RDF

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

Data size

</td>  
<td>

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

Time references of data

</td>  
<td>

2017/04/12

</td>  
<td>

2018/11/27

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

Availability

</td>  
<td>

2017/04/12

</td>  
<td>

2018/11/27

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

Data collection frequency

</td>  
<td>

Per rule firing, per campaign

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

Data quality

</td>  
<td>

Complete, available, right collection frequency

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

**Observation Values**

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

**Recommendation:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

recommendationRule

</td>  
<td>

Rule URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

Feedback

</td>  
<td>

User’s feedback,positive or negative or null

</td>  
<td>

String

</td>  
<td>

Yes

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

inDateTime

</td>  
<td>

Recommendation sending time

</td>  
<td>

Datetime

</td>  
<td>

Yes

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

triggeringAttributes

</td>  
<td>

List of attributes that is involved with the rule

</td>  
<td>

List<String>

</td>  
<td>

No

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

**RecommendationRule:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation Rule URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

conditionRule

</td>  
<td>

Rule triggering condition

</td>  
<td>

String

</td>  
<td>

Yes

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

userRule

</td>  
<td>

User selection rule

</td>  
<td>

String

</td>  
<td>

Yes

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

areaRule

</td>  
<td>

The condition that selects the area

</td>  
<td>

String

</td>  
<td>

Yes

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

isValidatedBy

</td>  
<td>

Action that validates the recommendation

</td>  
<td>

URI

</td>  
<td>

No

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

recommendationTemplat e

</th>  
<th>

The template the rule is based on

</th>  
<th>

URI

</th>  
<th>

Yes

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

**RecommendationTemplate:**

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation Template URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

Name

</td>  
<td>

Name of the recommendation template

</td>  
<td>

String

</td>  
<td>

Yes

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

Description

</td>  
<td>

Descriptive Content of the Recommendation

</td>  
<td>

String

</td>  
<td>

Yes

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

difficultyLevel

</td>  
<td>

Level of difficulty, Low Medium or High

</td>  
<td>

String

</td>  
<td>

Yes

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

@type

</td>  
<td>

Type of recommendation from the behavioural ontology

</td>  
<td>

URI

</td>  
<td>

Yes

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

showOnCompletion

</td>  
<td>

The message shown after completion

</td>  
<td>

String

</td>  
<td>

Yes

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

**ActionValidation:**

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

duration

</td>  
<td>

Maximum duration before validation in seconds

</td>  
<td>

Integer

</td>  
<td>

Yes

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

conditionRules

</td>  
<td>

The condition that validates if the recommended activity has been carried

</td>  
<td>

String

</td>  
<td>

Yes

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

###  3.1.7 Dataset: Lanave Sensor Measurements  
  
<table>  
<tr>  
<th>

**LanaveFinalSensorMeasurements.ttl**

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

Document version

</td>  
<td>

v1

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

Document format

</td>  
<td>

.jsonld

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

Description

</td>  
<td>

This dataset contains sensor measurements from Lanave building of UMU Pilot

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

Date

</td>  
<td>

2018-11-27

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

Keywords

</td>  
<td>

sensor, energy, infrastructure

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

Subject

</td>  
<td>

This data is sourced from several sensors with different properties

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

**Creator (UMU)**

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

Sector of the provider

</td>  
<td>

University

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

Permissions

</td>  
<td>

CC-BY-SA 4.0

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

**Name of the Partner (UMU)**

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

Responsible person

</td>  
<td>

Pedro J. Fernandez (Campaign manager)

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

Pilot

</td>  
<td>

UMU – La Nave

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

Scenario of data usage

</td>  
<td>

Data collected through several sensor data streams

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

**Description of the Data Source**

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

File format

</td>  
<td>

JSON-LD (.jsonld)

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

File name/path

</td>  
<td>

Lanave-sensor.jsonld

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

Storage location

</td>  
<td>

https://  _entropy-opendata.inf.um.es_

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

Data type

</td>  
<td>

JSON-LD, .jsonld

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

Standard

</td>  
<td>

RDF

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

Data size

</td>  
<td>

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

Time references of data

</td>  
<td>

2018/10/08

</td>  
<td>

2018/11/27

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

Availability

</td>  
<td>

2018/10/08

</td>  
<td>

2018/11/27

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

Data collection frequency

</td>  
<td>

Aggregated to 4 times a day

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

Data quality

</td>  
<td>

Complete, available, right collection frequency

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

**ObservationValues:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

isObservedBy

</td>  
<td>

Observed by Sensor

</td>  
<td>

OCBSensor

</td>  
<td>

Yes

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

isProducedBy

</td>  
<td>

Produced by Sensor Data Stream

</td>  
<td>

SensorDataStream

</td>  
<td>

Yes

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

inDateTime

</td>  
<td>

Observation Date

</td>  
<td>

Date

</td>  
<td>

Yes

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

hasValue

</td>  
<td>

Observation Value

</td>  
<td>

Double

</td>  
<td>

Yes

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

isUsedFor

</td>  
<td>

Property the Observation Value used for

</td>  
<td>

URI

</td>  
<td>

Yes

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

isMeasuredIn

</td>  
<td>

Unit of measure

</td>  
<td>

UnitOfMeasure

</td>  
<td>

Yes

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

hasSampleFrequency

</td>  
<td>

Sampling Frequency

</td>  
<td>

String

</td>  
<td>

Yes

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

**OCBSensor:**

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

Variables

</td>  
<td>

Name

</td>  
<td>

Type

</td>  
<td>

Mandatory

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

@id

</td>  
<td>

Sensor URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

deviceCategory

</td>  
<td>

Sensor Type

</td>  
<td>

URI

</td>  
<td>

Yes

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

attributes

</td>  
<td>

List of sensor attributes

</td>  
<td>

List<String>

</td>  
<td>

Yes

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

isLocatedIn

</td>  
<td>

Building Space URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

**SensorDataStream:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

comesFrom

</td>  
<td>

Sensor

</td>  
<td>

OCBSensor

</td>  
<td>

Yes

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

hasMonitoringType

</td>  
<td>

Monitoring Type

</td>  
<td>

String

</td>  
<td>

Yes

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

###  3.1.8 Dataset: Lanave Recommendation Data  
  
<table>  
<tr>  
<th>

**LanaveFinalRecommendations.ttl**

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

Document version

</td>  
<td>

v1

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

Document format

</td>  
<td>

.jsonld

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

Description

</td>  
<td>

This dataset contains recommendation sent to users from Lanave building of UMU
Pilot

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

Date

</td>  
<td>

2018-11-27

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

Keywords

</td>  
<td>

sensor, energy, infrastructure

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

Subject

</td>  
<td>

This data is generated by campaign managers and sent to users by rule firings

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

**Creator (UMU)**

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

Sector of the provider

</td>  
<td>

University

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

Permissions

</td>  
<td>

CC-BY-SA 4.0

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

**Name of the Partner (UMU)**

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

Responsible person

</td>  
<td>

Pedro J. Fernandez (Campaign manager)

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

Pilot

</td>  
<td>

UMU – La Nave

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

Scenario of data usage

</td>  
<td>

Data created based on rule firings based on collected sensor data

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

**Description of the Data Source**

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

File format

</td>  
<td>

JSON-LD (.jsonld)

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

File name/path

</td>  
<td>

Lanave-recommendation.jsonld

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

Storage location

</td>  
<td>

https://  _entropy-opendata.inf.um.es_

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

Data type

</td>  
<td>

JSON-LD, .jsonld

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

Standard

</td>  
<td>

RDF

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

Data size

</td>  
<td>

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

Time references of data

</td>  
<td>

2018/10/08

</td>  
<td>

2018/11/27

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

Availability

</td>  
<td>

2018/10/08

</td>  
<td>

2018/11/27

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

Data collection frequency

</td>  
<td>

Per rule firing, per campaign

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

Data quality

</td>  
<td>

Complete, available, right collection frequency

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

**Observation Values**

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

**Recommendation:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

recommendationRule

</td>  
<td>

Rule URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

Feedback

</td>  
<td>

User’s feedback,positive or negative or null

</td>  
<td>

String

</td>  
<td>

Yes

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

inDateTime

</td>  
<td>

Recommendation sending time

</td>  
<td>

Datetime

</td>  
<td>

Yes

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

triggeringAttributes

</td>  
<td>

List of attributes that is involved with the rule

</td>  
<td>

List<String>

</td>  
<td>

No

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

**RecommendationRule:**

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation Rule URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

conditionRule

</td>  
<td>

Rule triggering condition

</td>  
<td>

String

</td>  
<td>

Yes

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

userRule

</td>  
<td>

User selection rule

</td>  
<td>

String

</td>  
<td>

Yes

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

areaRule

</td>  
<td>

The condition that selects the area

</td>  
<td>

String

</td>  
<td>

Yes

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

isValidatedBy

</td>  
<td>

Action that validates the recommendation

</td>  
<td>

URI

</td>  
<td>

No

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

recommendationTemplat e

</th>  
<th>

The template the rule is based on

</th>  
<th>

URI

</th>  
<th>

Yes

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

**RecommendationTemplate:**

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

@id

</td>  
<td>

Recommendation Template URI

</td>  
<td>

URI

</td>  
<td>

Yes

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

Name

</td>  
<td>

Name of the recommendation template

</td>  
<td>

String

</td>  
<td>

Yes

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

Description

</td>  
<td>

Descriptive Content of the Recommendation

</td>  
<td>

String

</td>  
<td>

Yes

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

difficultyLevel

</td>  
<td>

Level of difficulty, Low Medium or High

</td>  
<td>

String

</td>  
<td>

Yes

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

@type

</td>  
<td>

Type of recommendation from the behavioural ontology

</td>  
<td>

URI

</td>  
<td>

Yes

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

showOnCompletion

</td>  
<td>

The message shown after completion

</td>  
<td>

String

</td>  
<td>

Yes

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

**ActionValidation:**

</td>  
<td>

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

**Variables**

</td>  
<td>

**Name**

</td>  
<td>

**Type**

</td>  
<td>

**Mandatory**

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

duration

</td>  
<td>

Maximum duration before validation in seconds

</td>  
<td>

Integer

</td>  
<td>

Yes

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

conditionRules

</td>  
<td>

The condition that validates if the recommended activity has been carried

</td>  
<td>

String

</td>  
<td>

Yes

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

###  3.1.9 Datasets : Perso App Dataset and Serious Game Dataset

The data utilized within the context of the both the PersoApp, as well as the
TH Serious Game will not be open to the public due to GDPR compliance with
personal user interactive data. In general, the TH Serious Game and the
PersoApp collected data, which are based on user interaction with the gamified
apps, enable data analytics and assessment of KPIs to have an insight on how
to improve the apps and increase the user interaction, in terms of promoting
energy efficient behaviour.

##  3.2 Making data openly accessible

The following table presents which datasets that are produced and used in the
ENTROPY project will be made openly available. It also explains why several
datasets cannot be shared.  
  
<table>  
<tr>  
<th>

#

</th>  
<th>

Dataset

</th>  
<th>

Data Openly

Available (Y/N)

</th>  
<th>

Justification

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

1

</td>  
<td>

POLO Sensor Observation Data

</td>  
<td>

Y

</td>  
<td>

N/A

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

2

</td>  
<td>

POLO Recommendation Data

</td>  
<td>

Y

</td>  
<td>

N/A

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

3

</td>  
<td>

UMU-Pleiades Sensor Observation Data

</td>  
<td>

Y

</td>  
<td>

N/A

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

4

</td>  
<td>

UMU-Pleidaes Recommendation Data

</td>  
<td>

Y

</td>  
<td>

N/A

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

5

</td>  
<td>

UMU-LaNave Sensor Observation Data

</td>  
<td>

Y

</td>  
<td>

N/A

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

6

</td>  
<td>

UMU-LaNave Recommendation Data

</td>  
<td>

Y

</td>  
<td>

N/A

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

7

</td>  
<td>

HESSO Sensor Observation Data

</td>  
<td>

Y

</td>  
<td>

N/A

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

8

</td>  
<td>

HESSO Recommendation Data

</td>  
<td>

Y

</td>  
<td>

N/A

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

9

</td>  
<td>

Perso App Data

</td>  
<td>

N

</td>  
<td>

The Perso App data will not be open to the public due to

GDPR compliance, on

personal user interactive data

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

10

</th>  
<th>

TH serious game data

</th>  
<th>

N

</th>  
<th>

The Serious Game data will not be open to the public due to GDPR compliance,
on

personal user interactive data

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

During the course of the ENTROPY project, all original raw data files and
respective processing programs were versioned over time and maintained in a
date-stamped file structure. Access to the datasets was given only after
request and during the design phases of the project to the responsible person.
These datasets were automatically backed up on a nightly and monthly basis.
Respectively, the data generated by the system during the pilots of the
project were stored to the database of ENTROPY platform, whose DB schema
reflected the aforementioned pilot parameters. Back-ups of the DB were
performed and stored on a monthly-basis. Also, the datasets were automatically
backed up on a nightly and monthly basis.

The ENTROPY 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. Through this research ENTROPY identified appropriate
platform solutions that can allow the sustainable archiving of all the ENTROPY
datasets after the life span of the project. The ENTROPY project Open Data are
hosted at  _https://entropy-opendata.inf.um.es_ on a CKAN installation in
JSON-LD format. The data will be available in a repository as different
datasets plus a dataset for the metadata.

##  3.3 Making data interoperable

From the beginning of the project, the ENTROPY platform aimed to make data
interoperable. For this reason, we developed two ontologies, mainly reusing
existing and well known ontologies. The detailed documentation of these
ontologies are available and can be found in the ENTROPY project website.
Additionally, the metadata regarding the datasets will be published annotated
with the DCAT Vocabulary  1  .

##  3.4 Increase data re-use (through clarifying licenses)

The Open Data of ENTROPY are licensed under CC-BY-SA 4.0 (
_https://creativecommons.org/licenses/by-sa/4.0/_ )  and the data is aimed to
be reusable for as long as the  entropy-opendata.inf.um.es  is alive.

##  4\. ALLOCATION OF RESOURCES

The ENTROPY consortium utilizes a CKAN repository installation at  _entropy-
opendata.inf.um.es_ ,  a content manager system dedicated to store and provide
open data in a unified way. The datasets declared as open in previous sections
will be available online for some years, ensuring that other researchers have
the chance of working with this useful data. Additionally, the reports and
deliverables are published in the ENTROPY website. The handling of the CKAN
repository on behalf of the ENTROPY project, as well as all data management
issues related to the project, fall in the responsibility of project
coordinator. As for the publications, the ENTROPY consortium has extensively
published in scientific journals that allow open access with the costs related
to open access will claimed as part of the Horizon 2020 grant.

##  5\. DATA SECURITY AND ETHICAL ASPECTS

In terms of Data Security, in the course of the ENTROPY project, measures were
undertaken to account for a detailed Data Protection through the developed and
followed Data Protection Procedures, which also take under consideration all
ethical aspects of the ENTROPY related data as presented below.

###  5.1 Data Protection Procedures of ENTROPY

In order to be compliant with the European Union’s Directive 95/46/EC on the
protection of individuals with regard to the processing of personal data and
on the free movement of such data, this chapter defines the policy to protect
and pseudonymise the personal data collected from the participants taking part
in the different pilot cases in the ENTROPY project. Short description of the
overall data management processes is also provided, focusing on the end users
personal data.

####  5.1.1 Data Management and Protection Workflow

In order to achieve a robust data protection plan in the context of ENTROPY, a
workflow comprising of a set of steps has been designed, as depicted in Figure
1. This data-handling workflow covers all the generation of data from the
initial recruitment of the participants to the final operation of the ENTROPY
platform in the pilots. During the lifetime of the ENTROPY project, this
process was followed for initial recruitment of participants prior to the
implementation of the platform and for recruitment of participants based on
the usage of the ENTROPY platform. Figure 1 shows the general workflow of this
procedure that is common for both cases (the only difference regards the
completion of online questionnaires via the ENTROPY platform or not).

The first step regards the registration process, where an end user was able to
create an account via the ENTROPY platform and agree with the overall platform
usage terms and conditions. Following, the end user had to fill in an online
questionnaire with a set of questions that aimed to build its personal
profile. Upon the completion of the questionnaire, an analysis took place
categorizing the end user in specific profile categories. Upon the completion
of the analysis, personal profile data was encrypted and stored in the ENTROPY
repository, while the rest data was pseudonymised and stored also in the
ENTROPY repository for further analysis purposes. Encrypted user profile data
were made available and may be updated through secure communication channels
via the ENTROPY mobile and web applications. Further data stored and made
available in the repository – that did not include any personal data- regard
the data collected from the set of activated sensor data streams, as well as
crowd sensing data collected from the end users. In the following sections,
detailed description of the aforementioned steps is provided.

It should be noted that an instantiation of the ENTROPY platform regards the
realization of one pilot case. Thus, in case of ENTROPY pilot cases, three
instantiations of the ENTROPY platform were realized in independent virtual
machines, one for each pilot case (UMU, HESSO, and POLO). No access to data
coming from other cases was made available in any of the pilot cases.
Furthermore, the collected personal data was used exclusively within the
ENTROPY project and not made available for any other source outside the
project as it was pointed out in the Ethical Requirement document.

Figure 1. ENTROPY data management and protection workflow

#####  5.1.1.1 Participants registration and questionnaire completion (based
on ENTROPY Ethics)

As an initial step, the target users who were invited to participate in the
ENTROPY project carried out a registration process. This process involved the
creation of an account and the completion of a personal questionnaire to
collect certain relevant personal data. Creation of a new account was realized
via the ENTROPY platform, while activation of the account was provided by the
platform administrator. An activation e-mail was sent to the e-mail denoted by
the end user in order to validate that he/she requested the creation of an
account. Upon validation by the end user, he/she was able to login to the
platform.

Following, the next step regards the agreement with the terms and conditions
of usage of the platform and the completion of the online questionnaire (the
consent form and the questionnaires are available in the Annexes). At the
first phase -and given that the implementation of the platform was in
progress- the questionnaire were filled in based on the infrastructure of each
pilot case. However, given the release of the platform, the completion of the
questionnaires and the collection of the provided data from the end users was
eventually realised within the ENTROPY platform. Actually, this step regarded
the first step upon the registration of a new user. The questionnaire is
composed by 6 parts, as it is designed by the ENTROPY consortium. The
completion of all the parts is mandatory. An indicative screenshot of the
questionnaire -as it is integrated in the ENTROPY platform- is shown in Figure
2.

It should be noted that all the personal private profile data is collected in
this step of the overall data collection and management process, while no
previous dataset exists with regards to such data. Data collection for this
step is realized at the initiation of a campaign for a fixed and predefined
time period, specified by the campaign administrators.

Figure 2. Screenshot from the online questionnaire.

It should be also noted that, in the first round, prior to the implementation
of the platform, the questionnaires were created and shared among the
participants by means of the pilots’ infrastructure. Indicatively, in the case
of UMU, a web-based platform for questionnaire generation and management of
the University of Murcia (UMU)  2  was used. This tool was only accessible by
using a proper UMU email account.

Among other features, this platform allows the easy creation of web-based
questionnaires. In that sense, we created five types of questionnaires. Each
one included an explicit link to the ENTROPY consent form in its first
introductory page so that all the participants could easily read it. The links
to all of these questionnaires are listed next:

  * https://encuestas.um.es/entropy_spa_emp.cc 

  

  * https://encuestas.um.es/entropy_spa_stud.cc 

  

  * https://encuestas.um.es/entropy_ita_emp.cc 

  

  * https://encuestas.um.es/entropy_fr_emp.cc 

  

  * https://encuestas.um.es/entropy_de_emp.cc 

  

Next, an email with the listed links was distributed among the project's
partners by using the regular email list of the project. Each partner was
responsible for distributing the appropriate links among their target staff.

The data collected through this step are denoted in the database collections
entitled “User”, “UserProfile” and “QuestionnaireResult”, as they are detailed
in the following sections in this chapter.

####  5.1.2 Data Analysis, De-association and Encryption of sensitive
information

Upon the completion of the questionnaire, an automated analysis is taking
place classifying the user into specific behavioural types. Such a statistical
analysis is defined by the ENTROPY partner Athens University of Economics and
Business (AUEB) and is implemented in the ENTROPY platform. The results of the
analysis, along with part of the personal information (e.g. gender,
educational level) provided in the questionnaire were encrypted and stored in
the ENTROPY repository in the database collections “User” and “UserProfile”.
Thus, all sensitive personal data is only known by the end user that provided
them and cannot be revealed to other parties. All data interaction for such
data is realised upon encrypted data. The rest information is pseudonymised
fully disjointed by the end user that provided them- and stored also in the
ENTROPY repository, aiming at supporting any statistical analysis that may be
considered helpful in the future.

At this point, the end user profile is successfully initialized. The end user
has data such as:

  * name, 

  

  * educational level, 

  

  * gender, 

  

  * personality profile axis (Extraversion, Agreeableness , Conscientiousness , Emotional Stability , Openness to Experiences), 

  

  * work engagement (as result of the Vigor , Dedication ,Absorption) 

  

  * energy conservation behaviours, 

  

  * game interaction type (Philanthropist, Socialiser, Free Spirit, Achiever, Disruptor, Player). 

  

All the string-represented data is encrypted through the usage of a popular
and widely adopted symmetric encryption algorithm, namely the Advanced
Encryption Standard (AES). Some of the features of AES include:

  * Symmetric key symmetric block cipher, 

  

  * 128-bit data, 128/192/256-bit keys, 

  

  * Stronger and faster than Triple-DES, 

  

  * Provide full specification and design details. 

  

AES is widely adopted and supported in both hardware and software. Up to our
knowledge, no practical cryptanalytic attacks against AES has been discovered.
Additionally, AES has built-in flexibility of key length, which allows a
degree of ‘future-proofing’ against progress in the ability to perform
exhaustive key searches. The password required by the algorithm to encrypt the
data is provided by the project coordinator.

After their encryption process, the end user data was made available in the
ENTROPY repository and could be used for analysis and personalized
recommendation purposes. Based on the usage of such services, the end user
profile may be updated, however such an update in the data is totally obscured
from the end users as well as the administrators of the platform.

It should be noticed that the covered and encrypted part of the data will not
be distributed to any project or third-party participants. This part of the
data will be only stored and retained at the pilot sites (UMU, HESSO, and
POLO) or at UBITECH’s infrastructure dedicated to the ENTROPY project.

In case that an end user desired to opt-out from the pilot, a relevant process
was defined and supported. Through the platform the end-user was able to
declare that we wants to opt-out and then was able to select whether he
desires his data to be removed or not from the ENTROPY repository. In the
first case, a removal process took place deleting all the end-user related
data, while in the latter case no action was required.

The data collected through this step are denoted in the database collections
entitled “User”, “UserProfile” and “QuestionnaireResult”, as they are detailed
in the relevant section of the chapter.

####  5.1.3 Data management and update from ENTROPY services and applications

Once the initial profile data has been created, the set of services provided
through the ENTROPY platform as well as the developed third party mobile
applications, have access to them. As already mentioned, all the sensitive
personal data was encrypted, thus access to the encrypted data was provided
and no further data exposure was realized.

The third party applications have partial access only to the demographic data
of the authenticated end user. Partial access to an end-user personal data is
considered 100% secure since it only needs to put once its username and
password and after that just make use of the token-based authentication
mechanisms supported by the ENTROPY platform. The general concept behind a
token-based authentication system is to allow users to enter their username
and password in order to obtain a token which allows them to fetch a specific
resource - without using their username and password. Once their token has
been obtained, the user can offer the token - which offers access to a
specific resource for a time period - to the remote site. All communication
between the third party personalized applications and serious games and the
ENROPY platform was done through a secure SSL channel which allows all
sensitive information to be transmitted encrypted and secure.

In case of an update in the profile of an end-user (e.g. energy awareness
level, engagement indicator on games) based on his interaction with the
ENTROPY services and applications, the relevant information in the ENTROPY
repository may be updated, respecting the applied authorization, encryption
and secure communication mechanisms. In case of the collection of crowdsensing
data on behalf of the end users (e.g. indication of presence, reporting of
problems, answers to raised questions), such data was also stored in the
ENTROPY repository and made available to the relevant applications. Collection
of such data was based on the terms and conditions agreed with the end users
prior to the first execution of the application.

The data collected through this step are denoted in the database collections
entitled “User”, “UserProfile”, “AppProfile”, “Action”, “Action Validation”
and “Recommendation”, as they are detailed in the relevant section in the
chapter.

####  5.1.4 Building and Sensor Infrastructure Data Management

In addition for the data collected from users feedback via mobile
applications, information about the set of buildings considered in each pilot,
as well as the set of sensors registered per building space was provided. Such
information was provided in the platform by the campaign administrator. For
each building, the set of building spaces was declared, while information
regarding the surface, the capacity and the working hours of each building
space was provided. Furthermore, the sensor data streams that were activated
during the operation of the pilot were declared. The templates of these excel
sheets are depicted in Figure 3 and Figure 4.

Figure 3. Building Space Information

Figure 4. Sensor Data Stream Information

Regarding the association of the presence or engagement of end users with
specific building spaces, such information was collected only with their
consent. Each end user may declare the building spaces that he has activities
in order to get meaningful recommendations for these spaces. Furthermore,
during his interaction with the third-party applications, he may also declared
his presence in specific spaces (e.g. for earning points upon the realization
of an action).

In addition to that, the infrastructure sensors deployed in the building could
be associated with presence and certain activities of the users. However, the
ENTROPY consortium did not use this type of information, except if the user
declared such an action on its own (e.g. as part of a serious game action).
Here we describe the information that may be indirectly inferred given the set
of sensors deployed in the three use cases:

  * As for HVACs , when such devices are manually switched on or off it would be possible to infer that a person, probably the person associated with the HVAC's building space, is located in this space. This applies mostly to cases where a very limited number of persons has access to this space. If this space can be easily linked to a certain activity like activity in a kitchen or a personal office, then it would be possible to also infer the potential activity undertaken by the user. In similar manner, the manual configuration of the regulated temperature also indicates the presence of a person in the HVAC's area of influence. 

  

  * Concerning CO2, luminosity, temperature and humidity sensors, their readings indicating remarkable fluctuations might also indicate the presence of one or more people in their associate building spaces. 

  

  * Regarding presence sensors, their readings can be used to know when a person moves around a building space. Using this information along with other external data like time or the category of the building space then it would be also possible to infer the activity of the user and his approximate location. 

  

  * The sensors installed in doors and windows reporting when they are closed or opened can be also used to infer the presence or not of people within a building space or room. Similarly, the correlation of this data with other sources of information like the current time of the day and the category of the space (e.g. kitchen, research laboratory or personal office) might also give rise to a coarse-grained perception of the current activity performed within the space premises. 

  

In that sense, the consent form also reported the possibility of inferring the
aforementioned information but pointing out that it would not be used in the
context of the project.

The data collected through this step are denoted in the most of the database
collections, as they are detailed in the relevant section of the chapter.

####  5.1.5 ENTROPY data structure

In this section, short description of the main collections of the ENTROPY
database structure is provided, aiming at providing information on the main
data stored per database collection. It should be noted that the provided
information final, since minor adaptations may take place based on the
continuous feedback provided by the mobile applications developers. All the
sensitive personal data is encrypted, while access to any type of data is
provided to authenticated users over secure connections.  
  
<table>  
<tr>  
<th>

**Collection**

</th>  
<th>

</th>  
<th>

**Fields**

</th>  
<th>

**Encrypted**

</th>  
<th>

**Hosted by**

</th>  
<th>

**Lifetime**

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

User

</td>  
<td>

• • • • •

•

</td>  
<td>

first name last name e-mail

educational level

gender role

</td>  
<td>

</td>  
<td>

UMU or

UBITECH

</td>  
<td>

Project lifetime (or until

a user decides to optout)

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

User

</td>  
<td>

• •

•

</td>  
<td>

id interests

energy awareness level

</td>  
<td>

</td>  
<td>

UMU or

UBITECH

</td>  
<td>

Project lifetime (or until a user decides to optout)

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

UserProfile

</td>  
<td>

• •

•

</td>  
<td>

id user id

behavioural indicators

</td>  
<td>

</td>  
<td>

UMU or

UBITECH

</td>  
<td>

Project lifetime (or until

a user decides to optout)

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

BuildingSpace

</td>  
<td>

• • • • • • •

•

</td>  
<td>

id

name type surface capacity building objects working hours coordinates

</td>  
<td>

</td>  
<td>

UMU, POLO,

HESSO or

UBITECH

</td>  
<td>

From pilots deployment until project's end

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

Recommendati on

</td>  
<td>

• • • • • •

•

</td>  
<td>

id user id description triggering attributes

datetime feedback category

</td>  
<td>

</td>  
<td>

UMU, POLO,

HESSO or

UBITECH

</td>  
<td>

From pilots deployment until project's end

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

AppProfile

</td>  
<td>

• • • • • • • •

•

</td>  
<td>

id

name

user id player character total score monthly score last ranking last score
update last building space

</td>  
<td>

</td>  
<td>

UMU, POLO,

HESSO or

UBITECH

</td>  
<td>

From pilots deployment until project's end

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

SensorStream

</td>  
<td>

• • • • •

•

</td>  
<td>

id attribute sensor id frequency type state

</td>  
<td>

</td>  
<td>

UMU, POLO,

HESSO or

UBITECH

</td>  
<td>

From pilots deployment until project's end

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

ObservationVa lue

</td>  
<td>

• • • • • •

•

</td>  
<td>

id value rate of change datetime sensor stream id unit of measure prediction

</td>  
<td>

</td>  
<td>

UMU, POLO,

HESSO or

UBITECH

</td>  
<td>

From pilots deployment until project's end

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

Action

</td>  
<td>

• • • • • • • • • •

•

</td>  
<td>

id

username app profile recommendation building space sensor stream datetime
validated awarded score badge

</td>  
<td>

</td>  
<td>

UMU, POLO,

HESSO or

UBITECH

</td>  
<td>

From pilots deployment until project's end

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

Sensor

</td>  
<td>

• • •

•

</td>  
<td>

id state attributes location

</td>  
<td>

</td>  
<td>

UMU, POLO,

HESSO or

UBITECH

</td>  
<td>

From pilots deployment until project's end

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

###  5.2 Data Protection of Datasets made open

The consortium chose to utilize the CKAN data repository, which ensures the
data protection of the ENTROPY datasets made open.

**6\. OTHER ISSUES**

The ENTROPY project does not have any other issues to declare.

#  APPENDIXES

##  APPENDIX 1: Dataset Metadata Template  
  
<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>

</td>  
<td>

</td>  
<td>

</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>

##  APPENDIX 2: Ethics related material (e.g. consent form, Terms and
Conditions)

**_Forms and information to be provided to user_ **

#####  Title of project

ENTROPY: Design of an innovative energy-aware it ecosystem for motivating
behavioural changes towards the adoption of energy efficient lifestyles.

#####  Purpose of the project and its academic rationale

ENTROPY is a multidisciplinary project that aims to design and deploy an
innovative IT ecosystem targeting at improving energy efficiency through
consumers understanding, engagement and behavioural changes. The ENTROPY
consortium combines multidisciplinary competences and resources from the
academia, industry and research community focusing on the energy efficiency,
micro-generation, sensors and smart metering networking, behavioural change
and gamification domain.

We are going to monitor a series of sensors that are installed in each one of
the three pilots included in the project. The sensors will collect data from,
among others, temperature, humidity, CO2 levels, condition of air conditioners
and electrical consumption. The system will use this information to detect
energy-inefficient situations and notify a subset of the occupants.

We will collect information from the users of the pilots through questions and
surveys. On the one hand we will measure its factors relevant to energy use
such as habits, knowledge and attitudes. On the other hand we will measure
various factors related to player profiles. These measurements will be used to
offer users an experience as personalized as possible, thus increasing the
impact on their habits and attitudes.

We will deploy among the pilots participants a series of personalized
applications and serious games that will serve as a link between the users and
the system. We will develop a system of recommendations that will inform users
of possible tasks, news, or other information that can offer a positive change
in the behavior of users.

Further information on the academic rational of the whole ENTROPY project can
be found at  **_http://www.entropy-project.eu/_ **

Note: This project it is realized in collaboration between the three pilots
where the data will be collected, although the personal data will be stored
and treated within the repository of University of Murcia where the
disassociation is done. This note is relevant for the participants in the
pilots of Italy and Switzerland.

####  _Brief description of the methods and measurements_

Methods:

In each of the three pilot buildings will be monitored a subset of sensors
that previously existed. It is currently being investigated on what is the
optimal number and type of sensors needed to maximize the effect on the
participants.

The measurements collected from the sensors will be a variation of the
following depending on the result of the study mentioned in the previous
paragraph:

  * temperature 

  

  * temperature_2m 

  

  * average_temperature 

  

  * regulated_indoor_temperature 

  

  * active_energy_consumption 

  

  * active_power 

  

  * power_factor 

  

  * current 

  

  * voltage 

  

  * luminocity 

  

  * humidity 

  

  * radiation 

  

  * dew_point 

  

  * total_cloud_area 

  

  * snow_hour 

  

  * precipation_hour 

  

  * rain rate 

  

  * rain total 

  

  * co2 

  

  * wind_direction_10m 

  

  * wind_speed_10m 

  

  * sunshine_duration 

  

  * weather_conditions 

  

  * pressure 

  

  * active_persons 

  

During your participation in ENTROPY, you will be asked for providing the
following types of information about yourself in active (through
questionnaires) or passive manner (through mobile applications and games):

  * Demographics 

  

  * Personality 

  

  * Engagement at work 

  

  * Energy-conservation behavior 

  

  * Video-gaming personal preferences 

  

  * Energy-related actions at work 

  

In addition to that, it might be possible to indirectly infer your presence
and associated activity in certain areas of your building by making use of
some infrastructure sensors deployed within yours workplace. Nevertheless, the
ENTROPY consortium commits to neither infer nor use such information at any
moment.

During the registration process, potential participants will be asked to fill
out a survey (included as annex II). In addition, throughout the duration of
the study, we will launch questions to users through personalized applications
and serious games. As a complement to this information we will monitor data
regarding the use of custom applications and serious games. All this
information will be used to compose energy and player profiles of the
participants and to facilitate the identification of pattern of behaviors.

From the data collected directly from the users it is intended to extrapolate
the following information:

  * Levels of awareness of energy saving. 

  

  * Levels of knowledge on energy saving. 

  

  * Player Profiles. 

  

  * Acceptance levels of the application or serious game. 

  

**It is understood by all members of the ENTROPY project that this initial
ethical approval application will cover only what is written here and any
additional work on this study will be subject to another ethical approval
application.**

####  _Participants; recruitment methods, number, age, gender,
exclusion/inclusion criteria_

#####  Participants

Users of the three pilot buildings: Navacchio Technology Park (POLO),
University of Murcia Campus (UMU), Technopole in Sierre (HESSO).

#####  Recruitment

The majority of participants will be recruited via Advertisements, flyers,
information sheets, notices, Internet postings and/or media which will
encourage potential participants to register on the platform through a web
portal.

Other methods of recruitment may be used such as direct recruitment (i.e.
expositions, lectures with stakeholders), a referral system or a participant
pool. All methods listed above are not an exhaustive list of the methods that
will be used, and their usage is not obligatory for the consortium.

All recruitment materials and strategies has been/will be reviewed by the EAB
3  for approval.

No direct compensation to the participants is expected or planned during the
project. Based on the gamification mechanism developed for the platform, end-
users are expected to be rewarded with virtual points that may be redeemed on
services, as the software teams have decided and promoted at the time their
project launches. Nevertheless, the project may decide to promote the platform
through a series of lotteries and competitions on other platforms, the terms
of which will be announced when needed.

#####  Number, age, gender

The exact number, age and gender of the individuals within the households will
not be known until the point of recruitment.

**Inclusion/exclusion criteria** :

Participants must be students or university employees in the case of UMU and
HESSO. And employees and visitors in the technology park or residents in the
social housing infrastructure in POLO case.

####  _Consent and participant information arrangements, debriefing_

Specific attention will be given to the issue of _informed consent_ . For the
carrying out of the experiments, it will be ensured that all volunteers are
healthy adults legally capable of providing their informed consent. In order
to make an informed decision, all volunteers will be provided with
comprehensive information regarding the goals and duration of the project, the
progress, the planned tests and procedures to which they will take part, as
well as information on their rights – such as the right to withdraw their
consent at any time. Users will have access to the explanation **sheet of the
research project** **ENTROPY** provided within this document before entering
the service, and for the duration of its permanence in the same.

The consent form will be presented to potential participants from the web
portal during the registration process on the platform. **The consent form is
provided in this document.** The consent will be won once the participant
clicks on accept after marking a clearly identifiable check box.

The platform developers will be responsible for ensuring the consent form is
completed before the access to the platform is granted. Also, the platform
will provide to the participants a mechanism to ask any question that they
could have.

Initially, subjects will be **contacted** , to inform them about the goal of
the project, provide relative material and privacy information. They will be
informed about the process that will be followed and they will be asked to
subscribe to the project contact list.

At the end of each pilot study, a debrief letter will be sent via e-mail to
each participant, appreciating that they have participated in the study and
reminding them of the possibility of withdrawing their study data. **The
debrief letter is provided in this document.**

**A clear but concise statement of the ethical considerations raised by the
project and how you intend to deal with them.**

The study will collect invasive and potentially sensitive data. For example
from sensors we will have access to electric consumption data, and from
serious games we will know participants' occupancy patterns.

As such the confidentiality and anonymity of the data is paramount, and a
secure data protection system will be put in place accordingly. **Data
storage**

The information will be stored on the servers of the pilot buildings making
use of the FIWARE platform. FIWARE uses MongoDB which offers rigorously tested
security mechanisms. Only encrypted login data will be stored on user's
devices.

#####  Identifiable data

Personal data of users, e.g. demographic data and survey results will be
entered immediately into a database from where each set of results will be
given an automatic number and the personal details omitted. During the pilot
stages, the correspondence with the users list will be saved into a local
database, which will be encrypted. The server, will be kept in a locked server
room with electronic access only to those analyzing the results of the ENTROPY
project from the consortium.

#####  Transparency of the being data collected

Before participants sign the first consent form they will be told the exact
nature of the data that is being collected in simple and clear language. This
will be in the ENTROPY Research information sheet.

#####  Third countries

The involvement of a non-EU partner (HESSO) deserves special attention.
Bearing in mind that the EU Data Protection Directive provides strong
limitations for the transfer of personal data beyond EU boundaries and only
legitimates such a transfer to “third countries” under well-defined conditions
(see esp. Art. 25, 26 of the Directive), **no such transfer will be planned
for in the initial phase** . Instead, the fundamental assumption will be a
model of three strictly separated “silos” with no personal data being
transferred from the Spanish and the Italian to the Swiss pilot and vice
versa. Independently from this strict separation, the ethical standards and
guidelines of Horizon 2020 will be rigorously applied to all project
activities, including those taking place outside of the EU (HESSO Confirmation
included).

#####  Estimated start and duration of the project

We will begin collecting information from potential participants on the pilots
from 02/2016 the end of the project in 08/2018.

The data collected at the end of the project will be completely anonymized to
be used in future research studies without creating traceability to the
participants.

**Include copies of any information sheets, consent forms, debrief sheets and
questionnaire measures you intend to use**

###  ENTROPY project: Research information sheet

  1. _Invitation:_

  

  

You are being invited to take part in the research project entitled ENTROPY.
If you decide to take part, you will be asked to provide behavioral and
lifestyle data which will be aggregated automatically from the applications to
be developed within the context of the project. Before you make this decision,
it is important for you to understand why the research is being done and what
it will involve.

This document describes the project in order to help you to make sure your
decision. Please read the information provided carefully and discuss it with
others if you wish. Please take time to decide whether or not you wish to take
part. You must not feel obliged to participate in this research project. If
you do decide to participate, you can withdraw your consent at any time
without any disadvantages. Also, if you decide not to volunteer for the
project, it will not affect your treatment in any way.

Thank you for reading this.

  2. _Purpose of the project:_

  

  

The vision of the ENTROPY project is to design and deploy an innovative IT
ecosystem for motivating endusers’ behavioural changes towards the adoption of
energy efficient lifestyles, building upon the evolvements in the Internet of
Things, Data Modeling and Analysis and Recommendation and Gamification eras.
Internet of Things technologies are exploited for the proper and energy
efficient interconnection of a heterogeneous set of sensor nodes (e.g. smart
energy meters, sensors interacting with microgeneration infrastructure,
sensors in smart phones), the collection of data based on Mobile Crowd Sensing
Mechanisms exploiting the power of the collection of data from a critical mass
of interested people and the application of proper communication networking
schemes with regards to data collection. Advanced Data Modeling and Analysis
techniques are applied for the modelling of the collected data –both from
sensor networks as well as directly from end users- and the extraction of
advanced knowledge by exploiting the power of Semantic Web techniques, Linked
Data and Data Analytics. Focus is given on the development of personalised
mobile applications and games targeted at providing energy related information
to end users, triggering interaction with relevant users in social networks
(e.g. users in a specific area within a city), increasing their awareness with
regards to ways to achieve energy consumption savings in their daily
activities and adopt energy efficient lifestyles based on a set of
recommendations and motives targeted to their culture. The engagement and
direct inclusion of end users within the diverse components of the provided IT
ecosystem is going to be strongly supported.

  3. _Why have you been chosen?_

  

  

You have been chosen because your data is of interest for the research
developed within the project.

  4. _Do you have to take part?_

  

  

Your participation in this study is entirely voluntary. If you decide to take
part you will be asked to sign a consent form. By signing the consent form,
you will confirm that you were properly informed about this project and that
all your questions have been answered. A copy of the consent form will be
given to you to keep. If you decide to take part, you are free to withdraw
your consent at any time and leave the study without giving any reason.

  5. _What will happen to you if you take part?_

  

  

If you have decided to take part, behavioral and lifestyle related information
will be collected automatically, stored in the ENTROPY platform and processed
in order to provide personalised recommendations with regards to energy
consumption savings in your daily activities and adoption of energy efficient
lifestyles.

  6. _How is your data protected?_

  

  

Access and use of the data, is only allowed to registered users of the
platform.

  7. _Costs_

  

  

There will not be any additional costs for you if you decide to participate in
the project.

ENTROPY project

Individual and legal commitment to abide to ENTROPY Privacy and personal data
protection rules and guidelines

_Details of the contracting collaborator:_

Organization name:

First name:

Family name:

Email address:

I hereby confirm that I have read and fully understood the “Data Protection
Procedure” of the ENTROPY project. I personally and formally commit to respect
and to make respect those rules and guidelines, as well as the European
directive(s) on personal data protection.

I also commit to:

  * Mitigate any identified risk that those rules may be breached; 

  

  * Ensure that access to any potentially stored personal data is reserved to those who have signed the present legal commitment; 

  

  * Inform my internal hierarchy and/or the personal data protection officer of ENTROPY in the case I would identify any breach in the privacy and personal data protection policy. 

  

I understand that any voluntary breach of those rules may be considered as a
grave fault.

Place:

Date:

Signature:

**ENTROPY project**

ENTROPY Terms of Use and Privacy Statement – Preliminary Document

To be included in Web pages and apps

_Note:_This is a preliminary document that will be finalised in collaboration
with the legal departments of the_ _partners and checked with the national
data protection agencies as soon as the first release of the project is_
_available._ _

_**1\. Terms of use** _

####  Basic Terms

  * _You must be 18 years or older to use this application._

  

  * _You may not post nude, partially nude, or sexually suggestive photos._

  

  * _You are responsible for any activity that occurs under your screen name._

  

  * _You are responsible for keeping your password secure._

  

  * _You must not abuse, harass, threaten, impersonate or intimidate other users._

  

  * _You may not use the service for any illegal or unauthorized purpose. International users agree to comply with all local laws regarding online conduct and acceptable content._

  

  * _You are solely responsible for your conduct and any data, text, information, screen names, graphics, photos, profiles, audio and video clips, links ("Content") that you submit, post, and display on the ENTROPY platform._

  

  * _You must not modify, adapt or hack ENTROPY or modify another website so as to falsely imply that it is associated with ENTROPY._

  

  * _You must not crawl, scrape, or otherwise cache any content from ENTROPY including but not limited to user profiles and photos._

  

  * _You must not create or submit unwanted email or comments to any ENTROPY members ("Spam")._

  

  * _You must not use web URLs in your name without prior written consent from ENTROPY._

  

  * _You must not transmit any worms or viruses or any code of a destructive nature._

  

  * _You must not, in the use of ENTROPY, violate any laws in your jurisdiction (including but not limited to copyright laws)._

  

  * _Violation of any of these agreements will result in the termination of your ENTROPY account. While ENTROPY prohibits such conduct and content on its site, you understand and agree that ENTROPY cannot be responsible for the Content posted on its web site and you nonetheless may be exposed to such materials and that you use the ENTROPY service at your own risk._

  

####  Proprietary Rights in Content on ENTROPY

  1. _ENTROPY does NOT claim ANY ownership rights in the text, files, images, photos, video, sounds, musical works, works of authorship, applications, or any other materials (collectively, "Content") that you post on or through the ENTROPY Platform. By displaying or publishing ("posting") any Content on or through the ENTROPY Platform, you hereby grant to ENTROPY a non-exclusive, fully paid and royalty-free, worldwide, limited license to use, modify, delete from, add to, publicly perform, publicly display, reproduce and translate such Content, including without limitation distributing part or all of the Site in any media formats through any media channels, except Content not shared publicly ("private") will not be distributed outside the ENTROPY Platform. This IP License ends when you delete your IP content or your account._

  

  2. _When you delete IP content, it is deleted in a manner similar to emptying the recycle bin on a computer. However, you understand that removed content may persist in backup copies for a reasonable period of time (but will not be available to others). All this content will be securely deleted at the end of the ENTROPY project, prior to notice from the consortium to all ENTROPY users for this operation, unless they explicitly grant permission to the consortium to retain this content in the ENTROPY platform, until the users delete it themselves in the future._

  

  3. _You represent and warrant that: (i) you own the Content posted by you on or through the ENTROPY platform or otherwise have the right to grant the license set forth in this section, (ii) the posting and use of your Content on or through the ENTROPY platform does not violate the privacy rights, publicity rights, copyrights, contract rights, intellectual property rights or any other rights of any person, and (iii) the posting of your Content on the Site does not result in a breach of contract between you and a third party. You agree to pay for all royalties, fees, and any other monies owing any person by reason of Content you post on or through the ENTROPY platform._

  

  4. _The ENTROPY platform contain Content of ENTROPY ("ENTROPY Content"). ENTROPY Content is protected by copyright, trademark, patent, trade secret and other laws, and ENTROPY owns and retains all rights in the ENTROPY Content and the ENTROPY platform. ENTROPY hereby grants you a limited, revocable, nonsublicensable license to reproduce and display the ENTROPY Content (excluding any software code) solely for your personal use in connection with viewing the Site and using the ENTROPY platform._

  

  5. _The ENTROPY platform contain Content of Users and other ENTROPY licensors. Except as provided within this Agreement, you may not copy, modify, translate, publish, broadcast, transmit, distribute, perform, display, or sell any Content appearing on or through the ENTROPY platform._

  

  6. _ENTROPY performs technical functions necessary to offer the ENTROPY platform, including but not limited to transcoding and/or reformatting Content to allow its use throughout the ENTROPY platform._

  

  7. _Although the Site and the ENTROPY platform are normally available, there will be occasions when the Site or the ENTROPY platform will be interrupted for scheduled maintenance or upgrades, for emergency repairs, or due to failure of telecommunications links and equipment that are beyond the control of ENTROPY. Also, although ENTROPY will normally only delete Content that violates this Agreement, ENTROPY reserves the right to delete any Content for any reason, without prior notice. Deleted content may be stored by ENTROPY in order to comply with certain legal obligations and is not retrievable without a valid court order. Consequently, ENTROPY encourages you to maintain your own backup of your Content. In other words, ENTROPY is not a backup service. ENTROPY will not be liable to you for any modification, suspension, or discontinuation of the ENTROPY platform, or the loss of any_

  

  

_Content._

  8. _Your profile is only visible under an avatar and cannot be linked with your real profile unless you make information public._

  

  9. _When you join a project (i.e. an application under development), your content and information is shared with the project owners, based on the profile data you have explicitly permitted to be public. ENTROPY requires projects to respect your privacy, and your agreement with that project will control how the project can use, store, and transfer that content and information and how IPRs are treated._

  

  10. _You are in a position to opt-out of any project (“leave” from a project) that makes use of your information, at any time and for any reason. This action will result in ceasing the IPR agreement between yourself and the project, while the data you have shared with this project will be deleted and no new data will be provided from your side._

  

  11. _You are allowed to re-join a project at any time, by accepting the agreement that is valid at the period of joining._

  

  12. _A project may at any time ban certain users due to violation of terms of use, prior to notifying the user and the ENTROPY consortium for the intended action._

  

  13. _A project may at any time request from users to share more data and/or modify the IPR agreement. In such a case, the user may a) decide either to accept these changes, b) reject them and continue his presence in the project without altering the agreement and data sharing permissions which he accepted at join (or during a previous request), or c) reject them and completely opt out of the project._

  

  14. _We always appreciate your feedback or other suggestions about ENTROPY, but you understand that we may use them without any obligation to compensate you for them (just as you have no obligation to offer them)._

  

  

_**2\. Privacy** _

####  Gathering of Personally-Identifying Information

_Certain visitors to ENTROPY websites choose to interact with ENTROPY in ways
that require ENTROPY to gather personally-identifying information. The amount
and type of information that ENTROPY gathers depends on the nature of the
interaction. For example, we ask visitors who sign up for an account on
http://Entropy.com to provide a username and email address. In each case,
ENTROPY collects such information only insofar as is necessary or appropriate
to fulfill the purpose of the visitor's interaction with ENTROPY. ENTROPY does
not disclose personally-identifying information other than as described below.
Visitors can always refuse to supply personally-identifying information, with
the caveat that it may prevent them from engaging in certain website-related
activities._

####  Aggregated Statistics

_ENTROPY may collect statistics about the behavior of visitors to its
websites. ENTROPY may display this information publicly or provide it to
others. However, ENTROPY does not disclose personally-identifying information
other than as described below._

####  Protection of Certain Personally-Identifying Information

_ENTROPY discloses potentially personally-identifying and personally-
identifying information only to those of its employees, contractors and
affiliated organizations that (i) need to know that information in order to
process it on ENTROPY's behalf or to provide services available at ENTROPY's
websites, and (ii) that have agreed not to disclose it to others. Some of
those employees, contractors and affiliated organizations may be located
outside of your home country; by using ENTROPY's websites, you consent to the
transfer of such information to them. ENTROPY will not rent or sell
potentially personally-identifying and personallyidentifying information to
anyone. Other than to its employees, contractors and affiliated organizations,
as described above, ENTROPY discloses potentially personally-identifying and
personally-identifying information only when required to do so by law, or when
ENTROPY believes in good faith that disclosure is reasonably necessary to
protect the property or rights of ENTROPY, third parties or the public at
large. If you are a registered user of an ENTROPY website and have supplied
your email address, ENTROPY may occasionally send you an email to tell you
about new features, solicit your feedback, or just keep you up to date with
what's going on with ENTROPY and our products. We primarily use our various
product blogs to communicate this type of information, so we expect to keep
this type of email to a minimum. If you send us a request (for example via a
support email or via one of our feedback mechanisms), we reserve the right to
publish it in order to help us clarify or respond to your request or to help
us support other users, without however disclosing any personal information
about you. ENTROPY takes all measures reasonably necessary to protect against
the unauthorized access, use, alteration or destruction of potentially
personally-identifying and personally-identifying information. ENTROPY may
process your personal data to increase accuracy on project recommendations.
The outcome of this process will not be available to any third-party entity._

####  Internet Protocol (IP) Address, WAN Data and Cookie processing

_No data of IP Addresses, WAN data and cookies will be processed by the
ENTROPY platform. Any such data unavoidably recognized for technical reasons
will be deleted as soon as possible._

####  Ads

_No Ads apply to the ENTROPY platform. Projects hosted on the platform may,
however, be promoted to potential contributors as “editors’ choice” or
“trending” without any fee during the project period._

####  Privacy Policy Changes

_Although most changes are likely to be minor, ENTROPY may change its Privacy
Policy from time to time, and in ENTROPY's sole discretion, after acceptance
by the consortium, the EAB and the responsible national agencies. ENTROPY will
inform users for any such change, asking for their acceptance, in order to
continue using of the platform. User’s that have not accepted the revised
policies will be put into a “frozen” state, meaning that their data will not
be shared anymore until they decide to accept or reject the new policies.
Rejecting them, would mean that user’s data will be treated using the previous
policy, while users will also be able to choose to delete their account and
remove their data from the platform._

####  Leaving the service

_Any time you decide to leave the service, you can delete your account and
remove all your related data from the platform. Nevertheless, your data will
be lost forever and cannot be retrieved by any means, while it may be
impossible to retrieve your previous username if you decide to return to the
platform._

##  De-brief [Sent as e-mail]

Dear [Participant],

Thank you for participating in the ENTROPY project, we really appreciate your
involvement. The data that has been collected over the past year is currently
being analysed to find better ways to generate behavioural changes towards the
adoption of energy efficient lifestyles.

_Reminder: your data is secure, confidential and anonymous. You are free to
withdraw from the study at any point and have your data destroyed. Please
contact us quoting your username within ENTROPY if you wish to do so._

.

**APPENDIX 3: Registration Questionnaire**

##  _A. Personality Test_

For each of the following statements, please state the degree of your
agreement, by selecting between 1 - (Strongly Disagree) to 7- (Strongly
Agree).  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

**Strongly disagree**

</th>  
<th>

**Disagree**

</th>  
<th>

**Somewhat disagree**

</th>  
<th>

**Neither agree nor disagree**

</th>  
<th>

**Somewhat agree**

</th>  
<th>

**Agree**

</th>  
<th>

**Strongly agree**

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

</td>  
<td>

</td>  
<td>

**1**

</td>  
<td>

**2**

</td>  
<td>

**3**

</td>  
<td>

**4**

</td>  
<td>

**5**

</td>  
<td>

**6**

</td>  
<td>

**7**

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

</td>  
<td>

**I See myself as:**

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

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

1

</td>  
<td>

Extraverted, enthusiastic.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

2

</td>  
<td>

Critical, quarrelsome.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

3

</td>  
<td>

Dependable, selfdisciplined.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

4

</td>  
<td>

Anxious, easily upset.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

5

</td>  
<td>

Open to new experiences, complex.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

6

</td>  
<td>

Reserved, quiet.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

7

</td>  
<td>

Sympathetic, warm.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

8

</td>  
<td>

Disorganized, careless.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

9

</td>  
<td>

Calm, emotionally stable.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

10

</td>  
<td>

Conventional, uncreative.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

##  _B. Engagement_

For each of the following statements, please state the degree of your
agreement, by selecting between 1 – (Never) to 7- (Always).  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

**Never**

</th>  
<th>

**Almost Never**

</th>  
<th>

**Rarely**

</th>  
<th>

**Sometimes**

</th>  
<th>

**Often**

</th>  
<th>

**Very Often**

</th>  
<th>

**Always**

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

**1**

</th>  
<th>

**2**

</th>  
<th>

**3**

</th>  
<th>

**4**

</th>  
<th>

**5**

</th>  
<th>

**6**

</th>  
<th>

**7**

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

</td>  
<td>

</td>  
<td>

**Never**

</td>  
<td>

**A few times a year or less**

</td>  
<td>

**Once a month or less**

</td>  
<td>

**A few times a month**

</td>  
<td>

**Once a week**

</td>  
<td>

**A few times a week**

</td>  
<td>

**Every day**

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

1

</td>  
<td>

At my work, I feel bursting with energy.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

2

</td>  
<td>

At my job, I feel strong and vigorous.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

3

</td>  
<td>

I am enthusiastic about my job.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

4

</td>  
<td>

My job inspires me.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

5

</td>  
<td>

When I get up in the morning, I feel like going to work.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

6

</td>  
<td>

I feel happy when I am working intensely.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

7

</td>  
<td>

I am proud of the work that I do.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

8

</td>  
<td>

I am immersed in my work.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

9

</td>  
<td>

I get carried away when I am working.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**_C. EMPLOYEE ENERGY-CONSERVATION BEHAVIOURS AT_ **

##  _WORK_

For each of the following statements regarding energy behaviours at work,
please state the degree of your agreement, by selecting between 1- (Strongly
Disagree) to 7- (Strongly Agree).  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

**Strongly disagree**

</th>  
<th>

**Disagree**

</th>  
<th>

**Somewhat disagree**

</th>  
<th>

**Neither agree nor disagree**

</th>  
<th>

**Somewhat agree**

</th>  
<th>

**Agree**

</th>  
<th>

**Strongly agree**

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

</td>  
<td>

**Question**

</td>  
<td>

**1**

</td>  
<td>

**2**

</td>  
<td>

**3**

</td>  
<td>

**4**

</td>  
<td>

**5**

</td>  
<td>

**6**

</td>  
<td>

**7**

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

**Self-reported behaviours**

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

1

</td>  
<td>

When I am finished using my computer for the day, I turn it off.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

2

</td>  
<td>

When I leave a room that is unoccupied, I turn off the lights.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

3

</td>  
<td>

When I leave a bathroom that is unoccupied, I turn off the lights.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

4

</td>  
<td>

When I am not using my computer, I turn off the monitor.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

5

</td>  
<td>

When I leave my work area, I turn off the Air Conditioner(s).

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

6

</td>  
<td>

When I leave my work area, I turn off the printer(s).

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

7

</td>  
<td>

I often leave the windows open while the Air Conditioner is on.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</th>  
<th>

**Behavioural intentions**

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

8

</td>  
<td>

I would help the organization I work for conserve energy.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

9

</td>  
<td>

I would change my daily routine to conserve energy.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

</td>  
<td>

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

##  _D. Game Interaction Design_

For each of the following statements, please state the degree of your
agreement selecting between 1 - (Strongly Disagree) to 7 - (Strongly Agree).  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

**Strongly**

**Disagree**

</th>  
<th>

</th>  
<th>

</th>  
<th>

**Strongly**

**Agree**

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

</td>  
<td>

**Question**

</td>  
<td>

**1**

</td>  
<td>

**2**

</td>  
<td>

**3**

</td>  
<td>

**4**

</td>  
<td>

**5**

</td>  
<td>

**6**

</td>  
<td>

**7**

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

1

</td>  
<td>

I like being part of a team

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

2

</td>  
<td>

It is important to me to follow my own path.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

3

</td>  
<td>

I enjoy group activities

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

4

</td>  
<td>

It is important to me to always carry out my tasks completely

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

5

</td>  
<td>

I like to question the status quo.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

6

</td>  
<td>

It is difficult for me to let go of a problem before I have found a solution

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

7

</td>  
<td>

I dislike following rules.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

8

</td>  
<td>

Interacting with others is important to me.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

9

</td>  
<td>

Rewards are a great way to motivate me

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

10

</td>  
<td>

It makes me happy if I am able to help others

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

11

</td>  
<td>

Return of investment is important to me.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

12

</td>  
<td>

I see myself as a rebel

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

13

</td>  
<td>

I like helping others to orient themselves in new situations.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

14

</td>  
<td>

The wellbeing of others is important to me.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

15

</td>  
<td>

I like mastering difficult tasks

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

16

</td>  
<td>

It is important to me to feel like I am part of a community.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

17

</td>  
<td>

Being independent is important to me.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

18

</td>  
<td>

I like to provoke

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

19

</td>  
<td>

I like overcoming obstacles.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

20

</td>  
<td>

If the reward is enough I will put in the effort.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

21

</td>  
<td>

I like sharing my knowledge

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

22

</td>  
<td>

I like to try new things.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

23

</td>  
<td>

I like competitions where a prize can be won.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

24

</td>  
<td>

I often let my curiosity guide me.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

25*

</td>  
<td>

I prefer setting my own goals.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

26*

</td>  
<td>

I like to take changing things into my own hands.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

27*

</td>  
<td>

I would like to enhance my skills by training.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

28*

</td>  
<td>

I like to play with others in a team.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

29*

</td>  
<td>

I like comparing my performance with others.

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

##  _E. GAME ELEMENT IMPORTANCE APPRAISAL_ _QUESTIONNAIRE_

The following table includes and explains the functionality of **game
elements** that a game may include. Please state **how important it is for
you, that each one is utilized in a game aimed at reducing energy consumption
at the workplace,** by selecting between 1- (Not Important) to 7- (Very
Important).  
  
<table>  
<tr>  
<th>

**Game Element Evaluation**

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

**Legend of game element terminology**

</td>  
<td>

**Not**

**Very Important Important**

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

**Term**

</td>  
<td>

**Definitio n**

</td>  
<td>

**Alternati ves**

</td>  
<td>

**1**

</td>  
<td>

**2**

</td>  
<td>

**3**

</td>  
<td>

**4**

</td>  
<td>

**5**

</td>  
<td>

**6**

</td>  
<td>

**7**

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

**Points**

</td>  
<td>

Numerica

l units indicating progress

</td>  
<td>

Experien

ce points; score

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Badges**

</td>  
<td>

Visual icons signifying

achievem

ents

</td>  
<td>

Trophies

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

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

**Leaderbo ards**

</td>  
<td>

Display of ranks

for

comparis on

</td>  
<td>

Rankings

,

scoreboar d

</td>  
<td>

</td>  
<td>

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

##  _F. Demographics_

###  _Role in the organisation_

In the following you can state your role in the organization

  * Administrative (1) 

  

  * Managerial (2) 

  

  * Technical (3) 

  

  * Security (4) 

  

  * Other (5) 

  

###  _Smartphone usage_

Do you use a smartphone?

  * Yes (1) 

  

  * No (2) 

  

If in “Do you use a smartphone?” Yes Is Selected

###  _Phone OS_

  * What is the Operating System of your mobile? 

  

  * iOS / Apple (1) 

  

  * Android (2) 

  

  * Other/Don't know (3) 

  

###  _Age_

  * 18-24 (1) 

  

  * 25-35 (2) 

  

  * 35-45 (3) 

  

  * 45-55 (4) 

  

  * 55-65 (5) 

  

  * >65 (6) 

  

###  _Gender_

Sex (M/F)

  * Male (1) 

  

  * Female (2) 

  

###  _Children (Y/N)_

Do you have children?

  * Yes (1) 

  

  * No (2) 

  

_Contact details:_

Please enter your e-mail address, so that we can send you notifications
regarding the upcoming game. (We will not be using this information for any
other reason and it shall be kept private)