enprove energy consumption prediction with building usage … · 2017-04-20 · with the technical...

FP7-ICT-2009-4-248061

EnPROVE

Energy consumption prediction with building usage measurements for software-based decision support

Instrument: Small or medium-scale focused research project

Thematic Priority: Theme 3 – Information and Communication Technologies

D6.2 GUIDELINES FOR DEPLOYMENT AND INTEGRATION OF ENPROVE

Due date of deliverable: 30.04.2012

Actual submission date: 17.05.2012

Start date of project: 01.02.2010 Duration: 36 months

Organisation name of lead contractor for this deliverable: UNINOVA

Dissemination level: PU

Revision 1

EnPROVE D6.2 Guidelines for Deployment and Integration of EnPROVE

of 18

Executive Summary

The objective of EnPROVE is to support retrofitting of buildings, particularly, by introducing control technologies in the lighting and HVAC systems that enable decreasing the building’s energy consumption.

The EnPROVE platform comprehends two systems: the Building Performance and Usage Auditing that includes a wireless sensor network deployed in the building to be renovated; and the Energy Prediction and Decision Support System that suggest possible renovation scenarios and predicts the corresponding energy consumption, enabling the investor to select the best renovation scenario considering tangible (e.g. return on investment) and intangible (e.g. comfort level) criteria. The prototypes of these components have been developed in the scope of work packages WP5 Implementation and WP6 Integration and Performance Evaluation.

The objective of the current deliverable D6.2 Guidelines for Deployment and Integration of EnPROVE is to explain how to install and start using the EnPROVE platform. The document starts by setting the context of EnPROVE, helping to decide is this is the right solution to use.

This deliverable is addressed at two audiences:

The companies/persons that want to use EnPROVE, e.g. building owners, facility managers. Such users need to understand if EnPROVE provides the appropriate support for them, and what it entails. The approach includes auditing a building, which requires the installation of sensors, and owners should be fully aware of this and also of the time frames involved. In addition, these users need a manual to quickly take the most out of the software solutions developed.

The information and communication technology experts responsible for the installation and maintenance of software. The EnPROVE platform comprehends two systems hosted on web servers and databases that need to be installed and configured. It is necessary to have the necessary skills to install and properly maintain the system, enabling its adequate operation. The current manual provides step-by-step instructions of what to install. The companies that want to use EnPROVE should give this manual to their information technology departments or to any external subcontractor.


of 18

Abbreviations

BAU Building Performance and Usage Auditing

D Deliverable

e.g. exempli gratia = for example

EC European Commission

EnPROVE Energy consumption prediction with building usage measurements for software-based decision support

EPDSS Energy Prediction and Decision Support System

etc. et cetera

i.e. id est = that is to say

ICT Information and Communications Technologies

M Month

MS Milestone

RTD Research and Technological Development

STREP Small or medium-scale focused research project

w.r.t. With respect to

WP Work package

WSN Wireless Sensor Network


of 18

Contents

1 Introduction .............................................................................................................................. 5

2 Installing the EnPROVE Platform ............................................................................................. 7

2.1 BAU-WSN ......................................................................................................................... 7

2.1.1 Set up the WSN ......................................................................................................... 7

2.1.2 Set up the BAU server ............................................................................................. 11

2.2 EPDSS ........................................................................................................................... 12

3 When and How to Use EnPROVE ......................................................................................... 13

3.1 How does EnPROVE work? ............................................................................................ 13

3.2 The auditing process....................................................................................................... 14

4 User Manuals ......................................................................................................................... 16

5 Conclusions ........................................................................................................................... 17

6 Appendix A: Printed Manual ................................................................................................... 18


of 18

1 Introduction

The objective of EnPROVE is to support an investor in selecting the most appropriate scenario to retrofit a building, improving energy efficiency. The concept of the EnPROVE platform is based on analysing the real use of the building and proposing sets of control technologies that could be installed in the building, predicting the energy consumption.

The EnPROVE platform consists of two major systems (see Figure 1):

The Building Performance and Usage Auditing (BAU) includes a wireless sensor network (WSN) deployed in the building to be renovated, connected to local gateways that transmit data to the remote building performance and usage server, which processes this.

The Energy Prediction and Decision Support System (EPDSS) responsible for interacting with the technical consultant to extrapolate the data collected from the building and predict energy consumption for several possible technical solutions, and enable the investor in selecting the best renovation scenario considering tangible (e.g. return on investment) and intangible (e.g. comfort level) criteria.

Figure 1: EnPROVE platform overview.

The current document aims at presenting step-by-step guidelines for the deployment and integration of the several EnPROVE components. This means that someone with information and communication technologies skills could use this deliverable as guide to install and start using the EnPROVE system.

The EnPROVE system is used by actors with three main roles:

Investor (e.g. building owner or building operator) as the primary EPDSS user provides the key project/building data and investment constraints. Expected result is the final advice (where to invest) together with the financial and technical arguments (mostly economically driven).

EPDSS DBBAU DB

WSN DB

WSNGateway

WSNGateway

EnPROVE Platform

Building Performance & Usage Server

EPDSSServer

Processed Data

WSN DB

Raw Data

WSN DB

Raw Data

Raw Data

Remote siteBuilding on-site

Raw Data

WirelessSensor

Network


of 18

Technical consultant does the project specific configuration, creates the auditing request and controls the EPDSS in terms of steering the decision-support towards the final recommendations (assessing variants/proposals provided by the system for technical feasibility).

Building auditing contractor is responsible for the auditing work flow, including selection, deployment and management of the WSN and participates in defining auditing zones with the technical consultant using the EPDSS.

In addition to these three roles as EnPROVE users, it is necessary to consider the role of EnPROVE tool installation and maintenance. These users will mainly be ICT consultants, hired by building owners, with the responsibility to install and set-up the complete EnPROVE platform, making it ready to be used.

The current document is organised as follows:

Chapter 2 Installing the EnPROVE Platform is addressed to the ICT consultant who will deploy and configure the EnPROVE software solution and make it ready to be used. This chapter describes hardware and software requirements, along with all necessary steps to deploy the wireless sensor network, install and configure the BAU and the EPDSS.

Chapter 3 When and How to Use EnPROVE is directed at the actors with responsibility of selecting EnPROVE to support a renovation process in a building. This process is usually led by the investor (commonly the building owner), but may require the technical inputs from other actors. This chapter indicates the building types suitable to be supported by EnPROVE, as well as renovation levels supported and operational time frames.

Chapter 4 User Manuals comprehends the handbook to operate the software tools and is also available as online help with the software. This chapter is targeted to the software users, i.e. investor, technical consultant and auditing contractor.


of 18

2 Installing the EnPROVE Platform

As previously described, the EnPROVE Platform comprehends two systems: BAU-WSN and EPDSS. These systems can be deployed in the same or different machines, according to the specific use of the platform. The several components of the EnPROVE platform are distributed as represented in Figure 2.

Figure 2: EnPROVE Platform server deployment.

If the platform is only to be used in one building, than the on-site and remote locations could actually be the same. If the objective is to have the platform support several buildings, than the distribution becomes essential. However, there are several ways of implementing it. For example, the BAU DB and EPDSS DB servers could be the same machine.

This chapter supports an ICT consultant in installing and configuring the EnPROVE platform.

2.1 BAU-WSN

The BAU-WSN is actually a group of two independent systems: the Wireless Sensor Network, which is locally deployed in the building being analysed, and the Building Performance and Usage Auditing, which is a server that can be installed in the building being audited or on another chosen location.

2.1.1 Set up the WSN

The wireless sensor network is a set of sensors and a gateway to collect the sensorial data.

A. Requirements

The first step is to identify hardware and software requirements for a WSN deployment, which include the following:

A PC installed with Ubuntu operating system;

TinyOS software;

SE1000 driver; and

Java 6 and JDBC driver for MySQL.

In order to be able to use TinyOS to program the sensor node, a PC installed with Ubuntu operating system and Java 6 are required. Once this first step is completed, following the procedures below to install the TinyOS operating system and the additional SE1000 driver.

REMOTE LOCATION 2REMOTE LOCATION 1BUILDING ON-SITE

WSN GatewayBuilding with WSN BAU

EPDSS DB

EPDSS

WSN DB BAU DB


of 18

Install TinyOS 2.1.1 and SE1000 driver

o Remove any old TinyOS repository from /etc/apt/sources.list and add the following:

deb http://tinyos.stanford.edu/tinyos/dists/ubuntu lucid main

o Update the repository cache by running

sudo apt-get update

o Run the following to install the latest release of TinyOS and all the supported tools

sudo apt-get install tinyos-2.1.1

o Add the following line to the ~/.bashrc or ~/.profile file in the home directory to set up the environment for TinyOS development at login

source /opt/tinyos-2.1.1/tinyos.sh

Install SE1000 driver

o In order to program the SE1000 sensor nodes, which are deployed for occupancy detection, SE1000 driver is additionally required. This step is completed by extracting the file SE1000.zip into /opt/tinyos-2.1.1/tos/sensorboards.

Install Java 6 and JDBC driver for MySQL

o Download and install Java 6 for Ubuntu from http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u32-downloads-1594644.html

o Download and extract the official JDBC driver for MySQL from http://dev.mysql.com/downloads/connector/j/

o Modify the file /opt/tiny-2.1.1/tinyos.sh with the followings to include the path of MySQL JDBC driver

export TOSROOT=/opt/tinyos-2.1.1

export TOSDIR=$TOSROOT/tos

export CLASSPATH=/PATH/mysql-connector-java-5.1.17-bin.jar:$CLASSPATH

export CLASSPATH=$TOSROOT/support/sdk/java/tinyos.jar:.:$CLASSPATH

export MAKERULES=$TOSROOT/support/make/Makerules

B. Programming sensor nodes

After completing the installation requirement on both hardware and software sides, it is possible to proceed to the next step which is to program and configure the wireless sensor nodes. These sensor nodes can be grouped into three categories, which include base station, TelosB node, and SE1000. The TelosB and SE1000 nodes are used for measuring luminous level and object movement respectively, while the base station node, which is attached through USB port on the PC, acts as the gateway bridging the communication between the physical sensor network and the PC. Sensor node programming includes four steps as described in the following text.

Install sensor nodes

o Programming Base station node

o 6LowPAN driver support

o Base station configuration

o Programming TelosB node

o Programming SE1000 node

This process is started by programming the Base station node and 6LowPAN driver support, followed by the TelosB and SE1000.

Programming Base station node

http://tinyos.stanford.edu/tinyos/dists/ubuntu















of 18

o Open the Terminal and go to the directory /opt/tinyos-2.1.1/apps/IPBaseStation, which is the application used to provide gateway functionality between sensor network and PC.

o Attach the base station node, which can be any TelosB sensor node, to the USB port.

o Type make telosb blip install,0 to install the application on the sensor node.

o Upon completion of sensor programming, detach the sensor node from the USB port.

6LowPAN driver support

o This step is required for building the router driver with 6LowPAN support. Open the Terminal window and go to the directory /opt/tinyos-2.1.1/ and type the following commands

$ ./bootstrap

$ ./configure

$ make

In case that the process fails to proceed, it might be necessary to install some extra packages required for make, such as autoconf or automake.

o Open the terminal and go to /opt/tinyos-2.1.1/support/sdk/c/blip directory. Type the following commands in the console

$ ./bootstrap.sh

$ ./configure

$ make

o If the previous two steps succeeded, the routing driver for the base station has been successfully built, the binary of which is in the directory /opt/tinyos-2.1.1/support/sdk/c/blip/driver/ip-driver

o Running the driver for base station by typing sudo driver/ip-driver /dev/ttyUSB0 telosb in that directory.

Base station configuration

The driver for base station with 6LowPAN support loads its configuration from a file when it starts. By default, the file is located at /opt/tinyos-

2.1.1/support/sdk/c/blip/serial_tun.conf. This file controls the IPv6 prefix used for the subnet, the address of the router on that subnet (both are taken from the 'addr' directive), as well as the 802.15.4 channel used. The channel set here must be the same as the channel used by base station. The default file is shown below.

# Before you can run the adaptation layer and router, you must

# configure the address your router will advertise to the subnet, and

# which network interface to proxy neighbor advertisements on.

# set the debug level of the output

# choices are DEBUG, INFO, WARN, ERROR, and FATAL

# log DEBUG

# set the address of the router's 802.15.4 interface. The interface

# ID must be a 16-bit short identifier.

addr fec0::64

# the router can proxy neighbor IPv6 neighbor discovery on another

# interface so that other machines on the subnet can discover hosts

# routing through this router. This specifies which interface to proxy

# the NDP on.

proxy lo


of 18

# which 802.15.4 channel to operate on. valid choices are 11-26.

channel 15

Programming TelosB node

o Extract the attached application file UDPSense into /opt/tinyos-2.1.1/apps/

o Attach one TelosB node into the USB port on the PC

o Open the Terminal window and type motelist in the console. The output indicates through which USB port the sensor is attached on the PC. The possible values are /dev/ttyUSB0, /dev/ttyUSB1, No devices found

o If the output is not No Device found, go to the directory of UDPSense and type the following command to program the node

make telosb blip install,$ID bsl,$port

where $ID1 should be between 1 and 30, and $port should be the output after running motelist

o Upon completion, detach the sensor node from the USB port of the PC

Programming SE1000 node

o Attach one SE1000 node into the USB port on the PC

o Open the Terminal window and type motelist in the console. The output indicates through which USB port the sensor is attached on the PC. The possible values are /dev/ttyUSB0, /dev/ttyUSB1, No devices found

o If the output is not No Device found, go to the directory of UDPSense and type the following command to program the node

make telosb blip install,$ID bsl,$port

where $ID should be between 30 and 60, and $port should be the output after running motelist

o Upon completion, detach the sensor node from the USB port of the PC.

C. Running Java application

Once all categories of sensor nodes are programmed and configured, they are ready for being deployed with battery or USB cable powered in the premise for data collection. Due to the multi-hop packet transmission and low power sensing functionality enabled by 6LowPAN protocol, these sensor nodes are capable of performing wide-range sensing tasks while preserving power consumption at lower levels. The data is collected at each sensing node and as a result, packets are delivered to the base station node. In order to constantly and persistently acquire data from these sensor nodes, a Java application has been created to extract this information and to put them into the database.

Running the Java application for data collection

o Create a database named test on the PC

o Open a Terminal windows and go to /opt/tinyos-2.1.1/apps/UDPSense/java/

o Running the Java application by typing the command bash run.sh

o Once the above steps successfully proceeded, data are persistently stored into the database of table sensor

1 By convention, Base station node is assigned UID with 0; TelosB node is assigned UID with value between

1 and 30; SE1000 node is assigned UID with value between 30 and 60.


of 18

2.1.2 Set up the BAU server

After setting up the WSN, it is necessary to configure the BAU server, which requires a database and a web server.

A. Database

The database used is MySQL server “Ver 14.14 Distrib 5.1.62”, but any version of MySQL server would do.

It is necessary to create two databases: “enprove_dev” (which will contain all the RAW data) and “enprovebaudb” (which will contain all the BAU data).

Afterwards the scripts: “dev.sql” and “bau.sql” should be run, which will create all the necessary tables.

There are two possible scripts that must be run in order to either transfer data in real time from the local database to the RAW database or process the data from RAW to BAU. The scripts must be run after setting up the whole WSN.

These scripts are written in Java 1.6, but are compatible with Java 1.7. In order to run the scripts without any problem, it is necessary to change the configuration file “dbInformations.txt” that contains all the credentials to the database and the correct tables in case any modification in the scheme or in the database names were made. Once the auditing period is complete, the script that will transfer the data from the RAW database to the BAU one should be run. This script must be run once and you have to specify the begin date and the end date inside the “dbInformations.txt” file, of the auditing period.

EnPROVE_DATA_LIVE.jar is the script to run to put the data live from the WSN.

EnPROVE_RAW_TO_BAU.jar is the script to run once the auditing period is over.

B. Web Server

The web server is Apache2 and is used to run the dashboard, which is the management console for the WSN. The dashboard is written in rails 3.2.1, and its installation requires the following steps.

In order to deploy a rails application into an Apache server, it is necessary to install Phusion Passenger, using the Passenger gem. To do so, run the following command:

gem install passenger

And

passengerinstallapache2module

This command checks all the dependencies needed and notifies any packages that need to be installed. Once all the dependencies are installed, it is necessary to add three lines (given by the installation tool) to the apache config file (/etc/apache2/apache2.conf). Afterwards, the Apache server should be normally restarted.

Before creating the virtual host, the rails project files should be placed into the /var/www directory. Instead of physically put them into this directory, it is possible to create a symbolic link as follow:

sudo ln s~/my_local_repository/my_link_name

Create a file in "/etc/apache2/sites-enabled", with any desired name. However, it is important to be consistent in the naming and it is recommended to put the same name as the ServerName. Below is an example of this file:

<VirtualHost *:80>

ServerName enprove.local

DocumentRoot /var/www/my_link_name/public

RackEnv development

<Directory /var/www/my_link_name/public>

AllowOverride all


of 18

Allow from all

Options MultiViews

</Directory>

</VirtualHost>

The following line should be added to the virtual host in the "/etc/hots" file:

127.0.0.1 enprove.local

Restart for the last time the apache server. Now the dashboard is locally available on http://enprove.local.

2.2 EPDSS

The EPDSS runs on a web server and is accessible from any device (desktop, laptop, tablet, smart phone) using a web browser. The EPDSS includes two components: the web application and the database.

In order to deploy the EPDSS, it is necessary to have a web and a database server. These two servers can be physically hosted in the same machine or not. In any case, the following pre-requisites have to be met on the sever machine(s):

MySQL database server (tested with version 5.5); and

Apache Tomcat web server (tested with version 6).

The installation is quite straightforward as described in the following steps:

1. Copy and unzip the EPDSS template database file “EPDSS.database.zip” to the server machine and in the just created subdirectory start the batch file “dataconf.bat” to load the EPDSS database schema.

2. Copy and unzip the contents of the EPDSS deployment package file “EPDSS.deploy.zip” to the Tomcat webapps directory (e.g. C:\Program Files\Apache Software Foundation\Tomcat 6.0\webapps).

3. Go to the just created webapps subdirectory EnPROVE\client and execute the batchfile “clientconf.bat” to configure the webstart client .jnlp file.

4. Start the Apache Tomcat Server.

5. Publish the link to the EPDSS webstart client by an HTML page or by email.


of 18

3 When and How to Use EnPROVE

Although EnPROVE has been developed to support building retrofitting, some restrictions have to be considered. When is EnPROVE the right tool to support the renovation of a specific building?

The building is a non-residential one, particularly used for offices.

The renovation is supposed to be a non-disruptive process, i.e. the objective is to improve the energy efficiency of the building without modifying the building envelope.

If the previous two conditions are met, then EnPROVE might be the appropriate platform to support the retrofitting process. The previous chapter, 2 Installing the EnPROVE Platform, described how to install the software products developed. This chapter concentrates on the business and technical perspective of using EnPROVE.

3.1 How does EnPROVE work?

The objective of using the EnPROVE platform is, starting from the building description and objectives, to obtain a set of technical control solutions to be installed that will reduce the building’s energy consumption. The output of EnPROVE can be given to architects, engineers and contractors to implement the retrofitting scenario suggested. The complete process of analysing the building and suggesting the most suitable renovation scenario is entitled an assessment project in EnPROVE.

The EnPROVE platform operates on the following phases, involving specific actors, as described in Table 1.

Table 1: Assessment project phases.

No. Phase Steps Actors EnPROVE Component

1. Set-up assessment project

Define building to be renovated

Renovation constraints (e.g. budget, time period)

Assign team

Technical Consultant

Investor

EPDSS

2. Baseline definition Import building model

Describe building’s lighting and HVAC equipment

Define zones


Auditing Contractor

EPDSS

3. Auditing Select and deploy sensors

Collect and process sensor data

Auditing Contractor BAU-WSN

4. Extrapolation Define building schedule

Create yearly energy profile for the building

Technical Consultant EPDSS

5. Scenario Creation Define lighting and HVAC parameters

Create renovation scenarios

Predict energy consumption of each scenario

Technical Consultant EPDSS


of 18

No. Phase Steps Actors EnPROVE Component

6. Decision support Define decision criteria

Calculate discounted cash flows for each scenario

Order scenarios


Investor

EPDSS

3.2 The auditing process

The main assumption of EnPROVE is that knowing how the building is used allows a more precise prediction of energy consumption and therefore enables the suggestion of more suitable and realistic renovation scenarios. EnPROVE includes a Wireless Sensor Network (WSN) and a Building Performance and Usage Auditing (BAU) that permit this analysis of the building’s use.

The objective is to install a set of sensors in specific zones of the building and collect sufficient data to study how the infrastructure is used by its occupants, i.e. how the lights and HVAC are used, how long people are in the building, how windows and doors are used etc.

The ultimate goal of the auditing process is to allow a “picture” of the building’s energy profile, i.e. use and energy consumption. The starting point of the EnPROVE prediction and decision process is a yearly energy profile. The system is, nonetheless, capable of developing this profile by extrapolation without the need to have sensors installed and collecting data for a 12-month period.

EnPROVE has defined several types of areas in a building, namely:

Cellular office (1 person)

Cellular office (2-6 persons)

Open plan office

Conference room

Archives

Bathroom

Corridor

Entrance hall

Copying/Server room

It is necessary to first define the areas of the building that will be renovated, which can range from one single office to the complete building. For each room type to be renovated, a representative instance should be selected to be audited. This means that the auditing process only needs to cover one zone for each type.

The objective of the renovation can comprehend lighting only, HVAC only or both. This selection has an obvious influence in the information that needs to be gathered in the auditing process. Table 2 details the information needed according to the renovation scope.

Table 2: Audit data for renovation scope.

Renovation Scope Minimum Audit Data

Lighting Presence

Light actuation

Daylight

HVAC Presence

Temperature

Door/window opening

Actuation of terminal units (on/off)


of 18

The final concern of the auditing process is defining how long should the sensors be deployed in a building, gathering data. Ideally, data should be collected in two different time periods, covering two opposite seasons, e.g. summer and winter. The justification for this is related to the different operational modes of HVAC systems in these opposite seasons. However, this is not a strict requirement. If the audit process is realised in only one period, the EPDSS extrapolates the audit results and calculates the building’s energy consumption taking weather data into account.

Although there are no specific studies on the amount of data needed and its direct impact on the accuracy of predicted values, there is a recommendation of auditing the building for a period from 6 to 12 weeks.


of 18

4 User Manuals

The EnPROVE platform includes a manual enabling users to quickly get familiar with the software.

The auditing contractor uses the Dashboard, a component of the BAU-WSN, to manage the wireless sensor network. The auditing contractor, technical consultant and investor use the EPDSS to identify the building, define zones, create and select renovation scenarios.

The user manual covers the functionality of the Dashboard and the EPDSS, and is available in two formats:

A printed manual that can be distributed to users or support training sessions. The manual is a stand-alone document, presented in 6 Appendix A: Printed Manual.

Online help available over a web browser, and linked to the software applications. The online help is available as NetHelp 2.0, which is a set of scripts and pages used to display and lay XML content out. Figure 3 displays the starting page of the dashboard manual.

Figure 3: Online help of the EnPROVE platform.


of 18

5 Conclusions

This deliverable comprehends the necessary guidelines to deploy and install the EnPROVE platform. These guidelines cover the deployment of the several platform components developed and previously reported as prototypes, namely:

D5.1 Wireless Sensor Network (M23),

D5.2 Energy Saving Prediction and Decision Support Tool (M23),

D5.3 Integration Components (M26), and

D6.1 BAU-WSN and EPDSS Integration Framework (M24).

The EnPROVE software components developed are currently (M27) deployed at a test site, in CLARITY’s building, in Ireland. The test site has a wireless sensor network installed, which has been collecting sensorial data, used to support building renovation. The dashboard is available, allowing auditing contractors to manage the wireless sensor network. The EPDSS is also being used to suggest renovation scenarios, which are also analysed and order using financial criteria. The two EnPROVE systems, i.e. the BAU-WSN and the EPDSS, communicate over web services to exchange data, namely audit request and audit results.

The detailed test results will be documented in D6.4 Overall System Performance (M29). This deliverable will describe the overall performance of the system based on the sensor test bed. This deliverable will report functioning details including scalability, reliability, system delay and usability.


of 18

6 Appendix A: Printed Manual

EnPROVE Manual 1

EnPROVE Manual

2 WSN Dashboard EnPROVE Manual

Contents

WSN Dashboard 3

What is the Dashboard?......................................................................................................................... 3 Login ........................................................................................................................................................ 3 The Main Window .................................................................................................................................. 3 My Account ............................................................................................................................................. 4 Site Details ............................................................................................................................................... 4 Zones........................................................................................................................................................ 5

Zone details ................................................................................................................................ 5 Edit Zone .................................................................................................................................... 6

Gateways ................................................................................................................................................. 6 Gateway Details ......................................................................................................................... 7 Edit Gateway .............................................................................................................................. 7

Devices ..................................................................................................................................................... 8 Device Details ............................................................................................................................ 8 Edit Device................................................................................................................................. 9 Re-assign Device........................................................................................................................ 9

WSN Management ............................................................................................................................... 10

EPDSS 12

What is the EPDSS? ............................................................................................................................. 12 Login ...................................................................................................................................................... 12 Project Information .............................................................................................................................. 12

Creating a New Assessment Project ........................................................................................ 12 Importing the Building Model ............................................................................................................. 13 Partitioning the Building into Zones ................................................................................................... 13 Requesting a Building Audit ............................................................................................................... 14 Yearly Building Usage.......................................................................................................................... 14 Defining the Building’s Baseline Scenario.......................................................................................... 16 Creating Renovation Scenarios ........................................................................................................... 18 Choosing a Renovation Scenario ......................................................................................................... 19

Glossary of Terms 22

EnPROVE Manual WSN Dashboard 3

WSN Dashboard

What is the Dashboard? The Wireless Sensor

Network (WSN)

comprehends the set of

sensors installed at the

building being analised.

The Dashboard is a web application that allows you to manage the Wireless

Sensor Network installed at the building being analysed.

With this tool you can see the sensors deployed, their specific location,

status, and the latest values collected.

In order to know how to access your dashboard, please contact your system

administrator.

Login You need to login to use the dashboard.

The username and password have been provided by your System

Administrator.

If you don’t remember your user credentials, click on Forget Password? You

will be prompted to insert your email address and you’ll receive an email to

reset your password.

The Main Window After logging in, a welcome screen is displayed.


The top right part of the screen displays two buttons, My Account allows

you to manage your account and Logout closes your dashboard session.

The bar below the EnPROVE logo has links to the welcome screen, Home,

and to the sites that you can access.

My Account When clicking the button My Account, you can see a screen that gives you

an overview of your account’s details, including your role and how many

sites you’re allowed to access.

Site Details A site is a building being

audited to enable studying

how the infrastructure is

used by its occupants.

Clicking on one of the sites displayed on the top bar, e.g. CLARITY, gives

you details about the respective building being audited.

The screen displays the name, description and address of the building. In

addition, you can also see how many auditing zones were defined for the

building, how many gateways and devices are installed.


From this screen, you can manage the auditing process for the current site,

including the zones defined, gateways, and devices.

Zones A building being analysed

is divided into smaller

spaces, i.e. zones, where

the sensors are deployed.

This screen gives you an overview of all the auditing zones defined for the

current building.

You can view, edit or remove any of the zones by clicking the links on the

right column of the table displayed.

The auditing process has the objective of gathering information on how the

building is used to support the retrofitting process. Each zone corresponds to

a physical space in the building, which can be presented in the decription

field. Each zone has a type: lighting, HVAC or both. The type indicates if

the zone is collecting data relevant for lighting use, HVAC use or both.In

addition, the zone details indicate how many sensors are deployed in the

current zone.

Zone details


It is possible to edit the description and type of each zone. The editing

options of a zone are quite limited, because the zones are defined for both

EnPROVE systems, i.e. the BAU-WSN and the EPDSS. If you need to

modify the physical location or dimension of a zone, you should use the

Zone Editor in the EPDSS and then send an update request to the

Dashboard.

Gateways A gateway is a computer

installed at the building

being audited to collect

and store the data from the

sensors.

Each building being audited can have one or more gateways installed

locally. Each sensor is connected to one gateway, to which send its values.

The auditing contractor decides on the need of how many gateways should

be installed in the wireless sensor network.

Edit Zone


Using the links on the right column, you can view, edit or remove a

gateway. In addition, you can also define a new gateway for this site.

This details screen tells you how many devices are connected to this specific

gateway and where in the building it is located.

You can edit the description or location of a gateway, by selecting edit in

the gateway overview.

The description is a text field, particularly useful when several gateways are

defined.

The location is also a text field where you can describe the exact location of

the gateway. In addition, you should specify the location using a

correspondence to one of the zones defined for this site. This

correspondence is done in a combo box.

Gateway Details

Edit Gateway


Devices A device is a sensor

installed in the building to

collect information, usually

temperature, presence,

luminance, humidity, etc.

This screen provides an overview of all the devices deployed in the current

site. This set of sensors, plus the gateways, compose the wireless sensor

network.

You can view the details, edit, re-assign, activate or deactivate any of the

devices, using the respective links in the right column of the list provided.

You can check the details of any of the devices installed at the building. In

this screen, you can verify the description of the sensor, physical location,

gateway and communication protocol. In addition, you can also see how

often the sensor registers a new measure.

Device Details


You can modify some of the device’s details, using this screen. You can

change the description, physical location, communication protocol or event

periodicity of the sensor.

Re-assigning a sensor means allocating it to a new area in the building. You

can use the combo box to select one of the pre-defined zones where the

sensor is now located.

Edit Device

Re-assign Device


WSN Management This screen provides a graphical representation of the building floor plan

being audited and the physical deployment of all the sensors. You can

inspect the several types of devices installed.

When clicking in one of the icons representing a device, you’ll obtain a pop-

up message with the status of the device and the measures associated to it.

There are some devices that have more than one sensor, as they measure e.g.

luminance, temperature and humidity.


The name of each sensor is a link that opens a graphic displaying the history

of last values measured.

12 EPDSS EnPROVE Manual

EPDSS

What is the EPDSS? The Energy Prediction and Decision Support System is a software

application that will help an investor in selecting the best scenario to

renovate a specific building.

The complete process supported by the EPDSS is called an assessment

project, in which you can define the building, create possible renovation

scenarios and finally select the one to implement.

The EPDSS has two main users: technical consultant describes the building

and creates the possible renovation scenario, and the investor defines the

project’s constraints and priorities and makes the final decision.

Login To start using the EPDSS, you need to login using the credentials assigned

to you by the System Administrator. If you don’t have credentials, please

contact the person responsible for maintaining the software.

After logging in you can see the main window of the EPDSS, with several

tabs representing the process flow of an assessment project.

Project Information After logging in, you can see a list of assessment projects in which you are

involved. These projects have either been created by yourself or your name

has been indicated by a technical consultant or investor.

In the list of projects, you can choose to verify the details of an existing

project or create a new one. Creating a New Assessment Project

EnPROVE Manual EPDSS 13

To create a new project, you need to fill in some information regarding the

building’s address, initial budget for renovation, energy savings target

desired and timeline for the project.

Importing the Building Model After starting the project and defining the building to be renovated, you will

need a 3D model of the building being analysed. This model will be the

basis to define areas to be renovated. It is not one of EnPROVE’s objectives

to support the design of such a model. Instead, the building model should be

imported form an external software tool, such as AutoCAD or Revit.

Partitioning the Building into Zones A building being analysed

is divided into smaller

spaces, i.e. zones, where


After importing the building model from an external software application,

you can define the areas that should be targeted in this assessment project,

i.e. the physical areas that you want to retrofit. Although zones do not have

to be bound to physical separations, such as walls, they should correspond to

the different usage types of rooms. For example, a conference room and a

single-person office should constitute two separate zones.

In addition to defining the zones to be renovated, you also need to define the

zones to be audited. It is not necessary to audit all zones to be renovated. It

is however recommended to audit at least one zone for each usage type

available (e.g. one conference room, one single-person office, one open

space).


The definition of zones should be done by the technical consultant in

collaboration with the auditing contractor.

Requesting a Building Audit After dividing the building into zones, it is possible to proceed with auditing

the building to gather data on how the infrastructure is actually used. The

technical consultant defines a desired period for the auditing process and

places a formal request. The auditing request formulated in the EPDSS by

the technical consultant is sent to the BAU-WSN to be analysed and

implemented by the auditing contractor.

Yearly Building Usage The auditing results are used to create a yearly usage pattern of the building

being analysed. The auditing process covers usually a specific period of

around 6 to 12 weeks. The EPDSS extrapolates the audit data for a full year.

In order to do this, you need to define a usage schedule of the building.


The most significant part in defining the schedule is to identify periods, e.g.

weekends, when the building is not used at all.

You will be notified when the audit results are available, so that you can

start the extrapolation process.

If you have defined the building’s schedule, the extrapolation runs on its

own and lets you know when it is finalised.

Now, if you have stored usage patterns of the building covering a full year.

These patterns will be used to predict the energy consumption of the

building in the presence of different scenarios.


Defining the Building’s Baseline Scenario The purpose of auditing the usage of the building is to calculate a yearly

energy profile of the building.

If the objective is to analyse several renovation scenarios, a starting point

needs to be established. The baseline scenario details the energy

consumption of the building, per zone, before the desired renovation.

In this screen, you can see the building’s floor plan, with the defined zones.

By clicking in one of the zones on the left-side tree, the floor are becomes

highlighted in the plan and the respective information is displayed in the

bottom part of the screen.

You should go through all the zones in the building and define all the

lighting and HVAC equipment installed and any control technologies

already used.


For each zone you can define strategies used, such as set-points, and then

you can also define specific products used, for lighting and HVAC.

One you complete the definition of the baseline scenario, the EPDSS

calculates the monthly energy consumption per zone, based on usage

patterns given by the extrapolated audit results.


Creating Renovation Scenarios The EPDSS will suggest you possible renovation scenarios to be applied to

the zones you want to renovate. For that, you can define a limit of

suggestion, and you can breakdown your total budget between lighting and

HVAC renovation.

There is a comprehensive set of default values that relate possible control

strategies to zone types. This mapping can be modified using the next

screen. The objective is to define for example that common areas such as

coffee spaces should not use presence control.


The EPDSS uses this mapping to match strategies to your target renovation

zones. Scenarios are built and their respective energy consumption is

calculated to estimate the associated energy savings.

You can see a final list of scenarios suggested.

You can inspect the details of each scenario, getting a dialogue with the

scenario costs and savings. In addition, the details include a comparison of

energy consumption of the building as is, i.e. the baseline scenario, versus

the building with the suggested renovation scenario implemented.


Choosing a Renovation Scenario The EPDSS takes all the suggested renovation scenarios and performs a first

financial analysis, building detailed discounted cash flows for each scenario.

The scenarios can be compared using financial indicators, e.g. payback

period, net present value etc. These values can be used to set thresholds and

filter some of the suggestions made.


You should define the importance of the decision criteria, comprehending

tangible and intangible indicators. The scenarios are compared in pairs using

the criteria selected.

22 Glossary of Terms EnPROVE Manual

Glossary of Terms

The Wireless Sensor Network (WSN) comprehends the set of sensors

installed at the building being analised.

Building Performance and Usage Auditing (BAU) is a system that gathers

all the data from the wireless sensor network and processes it. The BAU is

responsible for exchanging data with the other EnPROVE components,

namely the EPDSS.

Energy Prediction and Decision Support System (EPDSS) supports the

investor in choosing the best retrofitting scenario for a specific building.

A computer installed at the building being audited to collect and store the

data from the sensors.

A sensor installed in the building to collect information, usually

temperature, presence, luminance, humidity, etc.

A building being audited to enable studying how the infrastructure is used

by its occupants.

A building being analysed is divided into smaller spaces, i.e. zones, where


WSN

BAU

EPDSS

Gateway

Device

Site

Zone

enprove energy consumption prediction with building usage … · 2017-04-20 · with the technical...

Documents