ICT
PLATFORM
FOR
HOLISTIC
ENERGY
EFFICIENCY
SIMULATION
AND
LIFECYCLE
MANAGEMENT
OF
PUBLIC
USE
FACILITIES
Deliverable
D6.2:
Web
service
and
interface
client
for
interoperable
energy
management
support
Responsible Authors: Tuomas Laine, Francisco Forns‐Samso, Eino Kukkonen Co‐Authors: Marie‐Christine Geißler Due date: 31.5.2012 Issue date: 31.5.2012 Nature: Prototype
Start
date
of
project:
01.09.2010
Duration:
36
months
Organisation
name
of
lead
contractor
for
this
deliverable:
Insinööritoimisto
Olof
Granlund
Oy
History
Version Description Lead Author Date
0.1 First Draft Granlund Oy 17.04.12
0.2 Second Draft Granlund Oy 15.05.12
0.3 Edited pre‐final version TUD‐CIB 24.05.12
1.0 Final Version Granlund Oy 31.05.12
Copyright
This
report
is
©
HESMOS
Consortium
2011.
Its
duplication
is
restricted
to
the
personal
use
within
the
consortium,
the
funding
agency
and
the
project
reviewers.
Its
duplication
is
allowed
in
its
integral
form
only
for
anyone's
personal
use
for
the
purposes
of
research
or
education.
Citation
Laine
T.,
Forns
‐
Samso
F.,
Kukkonen
E.,
Geißler
M.,
(2012):
HESMOS
Deliverable
D6.2:
Web
service
and
interface
client
for
interoperable
energy
management
support,
©
HESMOS
Consortium,
Brussels.
Acknowledgements
The
work
presented
in
this
document
has
been
conducted
in
the
context
of
the
seventh
framework
programme
of
the
European
community
project
HESMOS
(n°
26088).
HESMOS
is
a
36
month
project
that
started
in
September
2010
and
is
funded
by
the
European
Commission
as
well
as
by
the
industrial
partners.
Their
support
is
gratefully
appreciated.
The
partners
in
the
project
are
Technische
Universität
Dresden
(Germany),
NEMETSCHEK
Slovensko,
S.R.O.
(Slovakia),
Insinooritoimisto
Olof
Granlund
OY
(Finland),
Royal
BAM
Group
NV
(The
Netherlands),
Obermeyer
Planen
+
Beraten
(Germany)
and
AEC3
LTD.
This
report
owes
to
a
collaborative
effort
of
the
above
organizations.
Project of SEVENTH FRAMEWORK PROGRAMME OF THE EUROPEAN COMMUNITY Dissemination Level
PU Public X
PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services)
Executive
summary
The objective of WP6 is to provide energy‐related tools and web services for the intelligent lifecycle
management of public use facilities that are capable to resolve operating problems, improve
comfort, optimize energy use, identify retrofits and provide related cost estimates.
Deliverable D6.2 presents the development of the web service and data interface client for energy
related management as planned in Task 6.2. Web services are utilized to integrate measured sensor
data collected by building automation systems (BAS) with the tools of the Facilities Management
module of the Integrated Virtual Energy Laboratory of HESMOS (IVEL). The performed work complies
with the tasks specified in the HESMOS Description of Work.
This deliverable report is a supplementary document that contains the data transfer specification to
the developed software, which is the actual product of WP6.
We present two use case scenarios that integrate sensor data with FM tools.
The first use case supports requirements management of energy related thermal conditions.
The second case supports monitoring of energy related system performance. The deliverable report is structured in four parts:
The first part provides a description of the two use case scenarios of utilizing web services to transfer
BAS data to requirements management of thermal conditions and monitoring of energy related
system performance.
The second part introduces the advantages of utilizing web services as the method to transfer data
and describes the data transfer procedure into the energy requirements management and
monitoring of energy performance management metrics.
The third part presents the involment of a third party by testing the developed data interface before
the FM GUI is ready, a separate practical example was used with existing BEQ visualization tool
prototype developed in an earlier EU project BuildingEQ.
The fourth part concludes with the tasks accomplished in this deliverable and the importance of
integrating BAS data with FM tools for energy efficiency management.
The following partners contributed task 6.2 work in accordance with their knowledge and expertise:
OG: OG contributed its large experience in the development of integrated energy analysis and
facilities management software. For the task 6.2, by new development and prototype
implementation of the energy requirements management system and the energy
performance management system metrics.
BAM: BAM contributed its extensive experience in the operation of lifecycle optimized Public
Table
of
contents
1. USE CASE SCENARIOS FOR ENERGY RELATED FACILITIES MANAGEMENT ... 5
1.1 USE CASE 1 ... 6
1.2 USE CASE 2 ... 6
2. DEVELOPED WEB SERVICES FOR ENERGY RELATED MANAGEMENT ... 9
2.1 WEB SERVICE FOR ROOMEX ... 9
2.2 WEB SERVICE FOR RYHTI METRICS ...10
3. PRACTICAL EXAMPLE: ITÄKESKUS SHOPPING CENTER ... 14
4. CONCLUSIONS ... 16
REFERENCES ... 17
APPENDIX ... 18
APPENDIX I: ACRONYMS AND ABBREVIATIONS ...18
1.
Use
Case
Scenarios
for
Energy
Related
Facilities
Management
In the scope of HESMOS task 6.2 web services are utilized to integrate sensor data collected by
building automation systems (BAS) with the tools of the Facilities Management module on the
HESMOS Integrated Virtual Energy Laboratory (IVEL). In order to cover applications for new and
existing buildings that utilize BAS systems, two use case scenarios were developed that integrate
sensor data with FM tools.
The first use case supports requirements management of energy related thermal conditions. The
typical users include tenants, end‐users and facility managers.
The second case supports monitoring of energy related system performance. The typical users
include building owners and facility managers.
Figure 1 shows the two use cases described above for sensor data integration with the FM IVEL Web
module.
Figure 1: Description of data transfer of the two use case scenarios
1.1
Use
Case
1
Use case 1 supports requirements management of energy related thermal conditions. The
information delivered will be related to spatial thermal conditions such as temperature and CO2
content. The requirements management system ROOMEX already provides as‐required and as‐
analyzed thermal comparisons for the design phase as shown in Figure 2. In HESMOS, the new web based application of the ROOMEX software for requirements management is developed to support
the whole building life cycle. As a web application it offers an easy access for the FM disciplines.
Measured sensor data for specific times will be provided for as‐required against as‐measured
comparisons regarding spatial thermal conditions in a building. The provided web service interfaces
support best higher level, web‐based BAS systems that are typical in new buildings.
Figure 2: Comparison of as‐required and as‐simulated thermal conditions during design phase
1.2
Use
Case
2
Use case 2 supports monitoring of energy related system performance. It focuses on existing buil‐
dings that typically utilize different lower level building automation systems. Measured sensor data
obtained from BAS will be transferred into energy related performance management RYHTI Metrics.
BAS data will be transformed into performance metrics by comparing actual measurements with
values represent good performance of the building and can be derived from building standards and
guidelines or according to the equipment manufacturer’s information.
Figure 3: Methods of transforming automation data into performance metrics (Ihasalo, 2012)
The purpose of energy performance metric is to obtain actual measured data to improve energy
performance of the heating, ventilation and air conditioning system (HVAC). This aims to reduce
energy consumption and improve indoor environmental conditions by continuously tracking and
monitoring issues related to HVAC equipment. Contrary to the practice of tracking energy use
measures, energy performance metrics concentrate on the factors that affect energy use in facilities.
Usually, energy savers in buildings are gained by correction of operational and control deficiencies
related to HVAC systems such as adjusting setpoints and changing time schedules or parameter
settings (Mills, 2004). The measured factors are air handling units (AHU), time schedule efficiency
and heat recovery efficiency. The energy performance metric is calculated as an average of these two
sub‐measures. By measuring these factors users will have more comprehensive detailed information
than common energy use displays. The reason for choosing a different approach for energy
performance is to use the information available in building automation systems. Commonly, energy
meters are not always connected to building automation systems.
AHU time schedule efficiency
The importance of AHU time schedule efficiency sub‐measure is to control that air handling units are
operated only when needed. Many times air handling units are changed to meet special needs in the
building and if the schedules are forgotten in this setting and never changed back to original settings
then problems may occur.
To prevent such situations the sub‐measure compares the actual AHU time schedule to a so‐called
optimal time schedule. Optimal time schedule for each AHU is determined together with the users
and operators of the building. The AHU time schedule efficiency sub‐measure has two target values,
starting time and ending time. The sub‐measure is calculated by counting the time during which the
actual time schedule exceeds the optimal time schedule and dividing this by the total measurement
time.
Heat Recovery Efficiency
Heat recovery efficiency has a significant impact on the energy use of buildings in cold climates. The
purpose here is to track that the heat recovery efficiency unit achieves the thermal efficiency
according to the equipment manufactures specification. Thermal inefficiencies are commonly due to
manufacturing failures, poor installation and use during operation. Heat recovery efficiency will be
calculated according to the efficiency ratio used in the calculations for supply‐air temperature which
is defined in the European Standard EN 308 (CEN 1997) as: ߟ௧ ൌ௧మమି௧మభ
௧భభି௧మభ (2.1)
where:
t21 = supply air inlet
t22 = supply air outlet
t11 = exhaust air inlet.
The submeasure is calculated by dividing the actual heat recovery efficiency (2.1) by the target
efficiency and multiplying by 100.
2.
Developed
Web
Services
for
Energy
Related
Management
In HESMOS, web services are utilized as the method to transfer measured sensor data collected from
the BAS systems into energy‐related requirements management and energy‐related system
performance management. This method enables more flexible integration of BAS data with energy
related management systems. The purpose of using web services is that it allows working with
services independent of the platforms and programming languages in which they are written (Bai et
al., 2011). The key component of web services is the internet protocol XML providing a universal
format for structured documents and data on the web. It represents content in a textual format that
is platform and language neutral. XML can separate the user interfaces from structured data making
possible to integrate the data which comes from different sources (Tom, 2004). However, many
buildings use different levels of BAS systems. In many cases the information is not transferred in XML
format but it can be delivered in other formats such as xls, csv or txt. For that reason an XML
converter will be developed in HESMOS to translate the information into an XML‐file format. An
example of that file format is shown in Figure 4.
Figure 4: XML‐File with temperature data
The measured data is placed in the section named <CONDITIONFILE>. The basic idea is to send data
values for selected data points (<LogPoint>) in a time tag section named <LogResult>. The time
tag is defined with special fields for each time concept (year/month/day/hour/minute/second). The
type‐attribute contains information about the type of data and the unit for the data. In addition to
temperature measurements other XML sections contain information about room humidity, CO2
levels and concrete core temperatures.
2.1
Web
Service
for
ROOMEX
In this use case scenario, a user will log in to the IVEL Connector providing a username and password.
The IVEL connector is the portal application where web services can be chosen and connected to each
other. The Intelligent Access Services (IAS) of the IVEL get the information from the IVEL connector and
the user can access other applications such as the building automation systems. Sensor data can be
accessed through the IAS by a specified filter, for instance, room temperature for a specific period of
time can be selected via the interface. The basic connections are shown in Figure 5.
<?xml version="1.0" encoding="UTF‐8"?> <!DOCTYPE RMTransfer SYSTEM "RMTransfer.dtd"> <CONDITIONFILE HostID="localhost" OverwriteSenderHostID="no"> <LogPoint LogPointID="GW1.A03_G4_412TE16_K02_005_M"> <LogResult year="2009" month="8" day="1" hour="0" minute="0" second="0" type="TEMPERATURE_C">22,70</LogResult> <LogResult year="2009" month="8" day="1" hour="1" minute="0" second="0" type="TEMPERATURE_C">22,80</LogResult> </LogPoint> </CONDITIONFILE>
The user can request data of actual measured values and times from ROOMEX through web services,
whereby both ROOMEX and RYHTI assume the use of BIM/IFC in the current version IFC2x3 as basis
(cf. ISO/PAS 16739). For that purpose a list of IfcSpace “names” or GUIDs and Attribute Keys
(temperatures, humidity, CO2 levels, etc) of the measurements values that are requested for specific
starting and ending time (StartDateTime and EndDateTime) has to be provided. The web service
response will deliver the measured values of the IfcSpace “names” or GUIDs and Attribute Keys
within the time interval requested. The requested values will not be stored in the ROOMEX database.
In addition to actual measured data, average, minimum and maximum values can be requested
through the IAS to make comparisons with designed values stored in the ROOMEX database. The
specific list of requirements is shown in Appendix II.
Figure 5: Description of data transfer between BAS and ROOMEX
2.2
Web
Service
for
RYHTI
Metrics
Figure 6 shows a common data transfer procedure for measured sensor data of a BAS system into
monitoring of the energy related system performance management. The procedure starts by
obtaining measurements of different parameters such as temperature, humidity, CO2 levels etc. from
technical systems in various location points in a building. Afterwards, the sensor data is stored into
the BAS server and later transferred for validation. In many cases, data is exported with file
extensions such as xls, csv or txt. After the data is processed and validated it is stored in a central
database. The results are later reproduced by the performance management system for monitoring
and reporting purposes.
Figure 6: Common data transfer procedure
To warrant this functionality, an XML‐converter has been developed to convert the measured data
exported in file formats other than XML. In addition, three different BAS data transfer mechanism
have been developed utilizing web services. They take into account the wide range variations in BAS
systems. Figure 7 illustrates the first concept specification and the different components of the data
transfer mechanism.
The procedure starts with configuring the BAS systems with regard to the schedule for saving sensor
measured data to defined folders in the BAS server. In this case, Method 1, the BAS server is directly
connected to the BAS systems. However, this is not the most typical case. The XML‐Converter runs a
scheduled service and reads many file formats, later it converts and transfers the information in XML
format into the webservice input folder. An example of the “Data Transfer XML” is presented and
described in Figure 4. The data collector client requests the measured information stored according
to the defined schedule through the web service. The Data Collector web service receives the
request from the data collector client program, reads the information in XML format and sends the
information back to the Data Collector Client. Data Collector Client saves the information (raw data)
to the database in the IVEL FM Server.
Method 2 (Figure 8) is developed for cases that the BAS system works with its own computer.
Therefore, it is necessary to use an external server that can allow, for instance, the installation of the
XML converter. The procedure is almost identical to the one described in the first method on how
the data is requested and answered.
Method 3 (Figure 9) is designed for BAS systems that are outdated and are not configured to transfer
information through a web service. The data collector client requests the information as usual, but in
this case the BAS system is directly connected through the internet with the data collector client.
Figure 9: Method 3 for BAS data transfer concept specification
3.
Practical
Example:
Itäkeskus
Shopping
Center
The task 6.2 was developing data interfaces for the FM IVEL, whereas the FM GUI development will
happen later in the task 6.4. To be able to test the developed data interfaces before the FM GUI is
ready, a separate practical example was used with an existing BEQ visualization tool prototype
developed in an earlier EU project BuildingEQ (Building EQ, 2010).
BuildingEQ was a project in the Intelligent Energy Europe Programme of the European Commission
(2007‐2010). Its goal was to strengthen the implementation of EPBD (Energy Performance of
Buildings Directive) by linking the certification process with commissioning and optimization of
building performance. The project developed methodologies and tools that could be used for
commissioning and optimization along with comprehensive type of reporting that facilitate how to
analyze and interpret information concerning the performance of the building.
The Itäkeskus shopping center is the largest in Nordic countries with a total area of 120, 300 m2. The
project was constructed in 1984, but it has been through major additions to the area of the complex
in 1992 and 2001. From 2002 the shopping center has invested periodically in the use of technology
and monitoring tools with successful results improving the overall performance of the building. With
updating and renovation of building management systems (BMS) major improvements have been
measured in many parameters, essentially in energy efficiency and indoor conditions. Figure 10
shows a layout of the 800 locations points that measure actual conditions in the shopping center.
The gap has been the large amount of measured information that has been sent manually.
Figure 10: Layout example of sensor locations points in the Itäkeskus Shopping Center
In task 6.2 the developed web services were installed to automate BAS data transfer and the testing
was done by using the BEQ visualization tool as a preliminary GUI. BAS data is transformed in csv
figure 11. It contains information about the sensor location ID, date, time and temperature. As
shown in this figure, sensor measurements can contain missing or faulty data. That data needs to be
filtered out and processed in order to give accurate measurements for later reporting and analysis.
Figure 11: Example of temperature data from BAS in csv format
An example of the testing of the developed web services by using the BEQ vitalization tool is shown
in Figure 12. While Itäkeskus was used for early testing of the developed data interfaces, it also made
possible to involve third party participation to HESMOS for enhanced exploitation purposes.
4.
Conclusions
In this deliverable report we presented the developed web services and data interface clients for
energy related facilities management. We described the advantages of utilizing web services as the
method to integrate data from different sources and present two different use case scenarios, where
building automation system data will be integrated into the energy related requirements manage‐
ment and the energy related system performance management. It is important to consider that the
report is complementary to the software development, which is the actual deliverable of task 6.2.
The development of the two use case scenerios was based on the different usage areas as well as
different user groups. Also, they together support both modern/new buildings with web‐based BAS
systems and existing buildings with typically lower levels of BAS systems.
This development is very important considering that the current use of BAS systems in not fully
exploited to the maximum potential, because the raw data is not integrated or reported in efficient
way. Having the integration of BAS and FM tools of the IVEL we will enable the use of information for
energy efficiency management.
In addition, the testing of the data transfer procedure in the Itäkeskus Shopping Center created early
proof of concept as well as important third party involvement already during the progress of the
References
Bai, J., Hao, Y., & Miao, G. (2011). Integrating Building Automation Systems based on Web Services.
Journal of Software, 6(11). doi:10.4304/jsw.6.11.2209‐2216
Building EQ ‐ intelligize your energy management: homepage:: (2010). Retrieved May 21, 2012, from
http://www.buildingeq‐online.net/
CEN. (1997). EN 308:1997. Heat exchangers. Test procedures for establishing performance of air to
air and flue gases heat recovery devices. European Committee for Standardization, Brussels.
Ihasalo, H. (2012). Transforming building automation data into building performance metrics –
design, implementation and evaluation of use of a performance monitoring and management
system. Unpublished Doctoral Dissertation. Aalto University, Espoo, Finland.
ISO/PAS 16739 (2005): Industry Foundation Classes, Release 2x, Platform Specification (IFC2x
Platform). © International Organization for Standardization, Geneva, Switzerland.
Mills E. (2004): Inter‐comparison of North American residential energy analysis tools. Energy and
Buildings 36(9), pp. 865‐880, http://dx.doi.org/10.1016/j.enbuild.2003.11.005.
Tom, S. (2004). Web Services & BACnet. BACnet Today | A Supplement to the ASHRAE Journal.
Appendix
Appendix
I:
Acronyms
and
abbreviations
AHU Air Handling Unit
BAS Building Automation System BIM Building Information Modelling BMS Building Management System
eeBIM Energy Enhanced Building Information Modelling
GUID Global Unique Identifier
IAS Intelligent Access Services IFC Industry Foundation Classes
IVEL Integrated Virtual Energy Laboratory XML eXtensible Markup Language
Appendix
II:
Requirements
for
BAS
Web
Service
Interface
To specify the objects for the request: ‐ List of spaces
‐ Space GUID or Space name for each listed space To specify time period:
‐ Date and time for the start ‐ Data and time for the end To specify the kind of monitored data:
Choose from temperature, humidity, CO2 levels and concrete core temperatures.
For each data type, choose:
‐ Hourly: List of hourly average values of sensor in the space
‐ Maximum: Maximum value through the requested time period during occupancy hours ‐ Minimum: Minimum value through the requested time period during occupancy hours.
