Cascade Deliverable 2.1

Deliverable D2.1

CASCADE Methodology for Energy Efficient Airports

Starting date: 01/10/2011

Duration in months: 36

Call (part) identifier: FP7-2011-NMP-ENV-ENERGY-ICT-EeB

Grant agreement no: 284920

Due date of deliverable: month 12

Actual submission date: 2012-09-30

Organization name of lead contractor for this deliverable: NUIG

Dissemination level: [PU]

Revision: [Final]

CASCADE Methodology for Energy Efficient Airports Deliverable 2.1

page 2 of 234


page 3 of 234

Authors

Author(s)

NUI Galway – Civil Engineering

Department - Ryan Institute –

IRUSE (NUIG)

Marcus M. Keane

Andrea Costa

Luis M. Blanes

Ciara Donnelly

Ignacio Torrens

ENERIT

Paul Monaghan

Mike Brogan

Mark Macafrey

Contributor(s)

Fraunhofer ISE (ISE)

Nicolas Rehault

Felix Ohr

PSE

Johannes Farian

Frank Luginsland

D’Appolonia S.p.A. (DAPP)

Andrea Pestarino

Federico Meneghello

Institute Mihajlo Pupin (IMP)

Sanja Vranes,

Nikola Tomasevic,

Marko Batic

SENSUS MI

Francesco Cara

Enrico Cara


page 4 of 234


page 5 of 234

Table of Content

1 INTRODUCTION 10

2 METHODOLOGY BACKGROUND 12

2.1 OVERVIEW OF EXISTING STANDARDS AND METHODS FOR ENERGY AUDIT. 13

2.1.1 ICT for sustainable homes 13

2.1.2 AuditAC 14

2.1.3 Harmonac AC 18

2.1.4 prEN 15240. Ventilation for buildings. Guidelines for inspection of air-conditioning systems. 20

2.1.5 ENAC (Italian Airport Authority) 23

2.1.6 IEA Annex 11 (1987) (IEA, 1987) 25

2.1.7 AS/NZS 3598:2000 31

2.1.8 RP-351 Energy Audit Input Procedures and Forms 34

2.1.9 ASHRAE Procedures for Commercial Building Energy Audits 34

2.1.10 ASME (American Society of Mechanical Engineers) 35

2.1.11 EINSTEIN Audit Methodology. 37

2.1.12 Short Term Monitoring 39

2.2 CASCADE ENERGY AUDIT 42

3 KEY PERFORMANCE INDICATORS 46

3.1 KPIS FOR BASELINING AND BENCHMARKING 47

3.2 KPIS FOR HVAC 49

3.2.1 Energy Efficiency KPIs 49

3.2.2 Service level KPIs 49

3.2.3 Energy Intensity (EI) and Energy Efficiency (η) for HVAC systems. 50

3.2.4 KPIs Hierarchy and Aggregation Level 51

3.3 STRUCTURING KPIS BY TIERS 52

3.4 CASCADE KPIS REPOSITORY 55

3.5 KPI SELECTION METHOD 68

3.5.1 Selection Method based in cost effectiveness 68

4 CASCADE PARTNER SOLUTION DESCRIPTIONS 71

4.1 ENERIT – ENERIT TOOL 73

4.1.1 Brief description 73

4.1.2 Detailed description 80


page 6 of 234

4.1.3 Application examples 101

4.2 FRAUNHOFER ISE – DATASTORAGE TOOL 103

4.2.1 Description 104

4.2.2 Data import and format 105

4.2.3 Database Structure 106

4.2.4 Dataprocessing Concept 107

4.2.5 Unified data point naming convention 107

4.2.6 Visualizing Data 110

4.3 FRAUNHOFER ISE - FAULT DETECTION AND DIAGNOSIS MODELS 113

4.3.1 Motivation 113

4.3.2 Sensor Fault Detection 114

4.3.3 Rule based Fault Detection and Diagnosis approach 115

4.3.4 Rule Based FDD Implementation 116

4.3.5 Model based Fault Detection and Diagnosis 120

4.4 SENSUS MI – DIAGNOSTIC TOOL 123

4.4.1 Data Exchange Carrier 123

4.4.2 Automated Fault Detection and Diagnostics 123

4.4.3 Data Collection 123

4.4.4 High frequency collection added value 124

4.4.5 Data Mapping & Normalization 124

4.4.6 Operational Guidelines (OG) 125

4.4.7 Energy Benchmarking 125

4.4.8 Detected faults within CASCADE 126

4.5 PSE - REMUS DATA LOGGER 128

4.5.1 Brief description 128

4.5.2 Detailed description 128

4.6 PUPIN – ONTOLOGY 132

4.6.1 Concept 133

4.6.2 Ontology Class Hierarchy 134

5 CASCADE INTEGRATED SOLUTION 136

5.1 AIRPORTS REQUIREMENTS AND CASCADE SOLUTION DEFINITION 137

5.2 CASCADE SOLUTION ARCHITECTURE 139

5.2.1 Challenges of Systems Integration 140


page 7 of 234

5.2.2 Use of Ontologies 141

5.2.3 Loose Coupling 142

5.2.4 CASCADE Architecture - The Big Picture 142

5.3 CASCADE SOLUTION USERS 148

5.3.1 CASCADE solution users at ADR FCO 149

5.3.2 CASCADE solution users at SEA MXP 150

5.4 CASCADE ENERGY ACTION SYSTEM (EAS) WORKFLOW 152

5.4.1 Improvement Opportunities/Suggestions 153

5.4.2 Pre-Populated Energy Audit Items (HVAC) 164

5.4.3 Fault detection diagnosis Alarms (FDD) 170

5.4.4 BMS Alarms 179

5.5 CASCADE ACTION MANAGEMENT AND TRACKING 183

5.5.1 Energy Action Reporting 186

5.5.2 Specific Charts for different users 188

6 CASCADE IMPLEMENTATION KIT 191

6.1 CASCADE IMPLEMENTATION TIMELINE 193

6.2 THE INITIATION PHASE 194

6.2.1 CASCADE Survey experience 194

6.2.2 CASCADE Energy Audit 197

6.2.3 CASCADE BMS / IT Assessment 197

6.2.4 CASCADE Organisational Factors Assessment. (OFA) 198

6.3 THE PLANNING PHASE 198

6.3.1 The CASCADE Project Charter 199

6.3.2 The CASCADE Project Management Plan 201

6.4 THE IMPLEMENTATION PHASE 201

6.4.1 Conduct Procurements 202

6.4.2 Execute Project Work 202

6.5 THE COMMISSIONING PHASE 203

6.5.1 Project Pilot Trial 204

6.5.2 Users Training 204

6.5.3 Implement Energy Action Plan 205

6.6 THE MONITORING AND CONTROLLING PHASE 205

6.6.1 Monitoring and Controlling CASCADE EXECUTION 206


page 8 of 234

6.6.2 Testing CASCADE performance. (Technical Implementation) 206

7 CONCLUSION 209

8 REFERENCES 211

ANNEX 1. CASCADE DETAILED AIRPORT SURVEY TEMPLATE 215


page 9 of 234

Abstract

The report describes the development of the CASCADE methodology and the preparation for its

exploitation phase. D2.1 initially gives some methodology background focusing on energy audits

and defining the CASCADE energy audit approach. Secondly CASCADE solution KPIs are

defined to assess the impact on energy, comfort and maintenance performance. The third

aspect is the description of CASCADE consortium available technologies with the objective of

identifying the best way to achieve integration of the CASCADE solution which is also described

in the deliverable. The description of the CASCADE solution is carried out using two viewpoints:

(1) end users roles and associated functionalities and (2) action management system and

workflow. The main aspect of the CASCADE solution is the integration of a data driven

automated Fault Detection and Diagnosis (FDD) application for energy systems/subsystems with

an Energy Action Management systems following ISO 50001 Standard. Lastly the structure of

the CASCADE implementation toolkit is described, this will be updated during the course of the

project according to lesson learned in the different implementation phases at pilot airports.


page 10 of 234

1 Introduction

The objective of WP2 is to develop the Framework and Methodology to implement CASCADE as

an approach across all 500 EU airports and like environments (because airports are very similar

to small cities or large manufacturing industrial plants). To this effect, targeted outreach will be

conducted in the appropriate WP (WP7). The methodology will be utilised to incorporate

automated FDD (WP4) and to coordinate the triggered action management plan according to the

ISO 50001 standard “Energy Management System” (WP5). This WP is built upon airports

facilities operation and technical characterization of the selected subset of key IT and energy

systems/subsystems (mainly HVAC given the situation at both pilots) defined in WP1. Because

of the need and potential for Fault Detection Diagnosis Methods and an approach for them to

adapt or overlay on top of different types of existing ICT infrastructures, this WP is deliberately

placed up front in the project with a “push” emphasis instead of a “catch” emphasis. Although it

looks different on the GANTT as such we feel it is important. The WP is also long in duration.

Although this is generally to be avoided we also feel it is essential that this WP push the initial

development of the project, learn from and evolve with the project, and then be exploited

towards the project end. Up to the submission of this deliverable (M12), the only phase entirely

completed is the initiating phase1 and lessons learned from this have been already included (and

have already shaped) the proposed methodology. It is expected to carry out the same process

for all the other phases of the project and to develop working templates for each of the

CASCADE implementation phases.

This report describes the development of the CASCADE methodology and the preparation for its

exploitation phase. The focus is on the results of concluded and on-going tasks. Section 2, after

presenting an extensive literature review on energy audit methodologies and approaches,

defines the CASCADE energy audit as part of the methodology background work. Section 3

defines the CASCADE Key Performance Indicators at different tiers and with the greatest value

for determining the energy performance and maintenance impact of the CASCADE solution on

airport operation. Section 3 gives a detailed description of partners technologies to support the

overall solution. Section 5 defines the CASCADE solution starting form end user (airport)

requirements defined in WP1 and then gives a detailed description of the CASCADE integrated

solution focusing on integration of heterogeneous technological components in a coherent way.

The main areas presented in Section 5 are CASCADE solution architecture, definition of the end

users roles, supported functionalities and action management system and workflow according to

ISO 50001. The part on the CASCADE architecture includes and documents work carried out

within Task 5.1 (Integrating FDD, ISO, and Energy Management Systems) which is still on-going.

Finally section 6 focuses on the construction of a methodology for the effective implementation

of CASCADE. Different processes of the CASCADE methodology are defined, as well as the

related inputs, outputs and tools/techniques for each one of them. This part of the methodology

will be revised during the solution implementation at the 2 pilots and will be incorporated in the

1 For project phases see Fig. 85 Overview of the CASCADE Implementation Toolkit in Section 6


page 11 of 234

replication plan final report. The current version of the methodology described in this chapter has

been already updated to capture lesson learned within the initiating phase the only one fully

completed by the end year one. Table 1 shows a more detailed overview that indicates the

between all the tasks within WP2 and the sections of D2.1.

Table 1 WP2 mapping between tasks, objectives and sections within D2.1

Task Objectives Sections in D2.1

Task 2.1

Methodology

Background

Seek and obtain access to Energy Audit definitions

Define CASCADE Energy audit

Section 2.1

Section 2.2

Task 2.2 Definition

of the relevant

performance

indicators

Formal definition of the performance metrics at

different tier Section 3

Task 2.3 Definition

of the energy

action system

Define the content of standard actions and how

actions will be targeted to different individuals

Define the outputs from the FDD system and the

inputs to the Action Management system

Define how the actions will be transported to the

user and how the follow up process is organised

Section 5.3

Section 5.4

Section 5.5

Task 2.4 Validation

Plan

Describe how the consortium aims to perform the

validation of the technical implementation of the

CASCADE solution

Refer to D2.2

Task 2.5

CASCADE

Methodology

Creates, capture, and prepare the exploitation of the

CASCADE methodology

Section 3,

Section 5.1,

Section 5.2 (this

one covers

aspects of Task

5.1), Section 6


page 12 of 234

2 Methodology Background

This section documents the work carried out within Task 2.1 which has focused on the

discussion of what constitutes an Energy Audit. An extensive literature review has been done

focusing on both EU funded projects/actives and available national and international standards

and studies. Energy Audits have become a commonly used instrument to assess the current

conditions of an existing facility and evaluate possible energy conservation measures previous

to commit any investment. Audits can be classified attending to different purposes, level of detail,

complexity and different scopes or interests.

An essential high level categorisation of an Energy Audit should look at three different aspects:

(1) Focus (2) Scope and (3) Detail, as shown in Fig 1.

Fig 1: Three pronouncements of an Energy Audit

The Focus: Audits can be targeting different interests. Some audits are aimed at retrofit

of the physical building, or specifically to energy or thermal systems with the aim of

evaluate retrofit options and the effectiveness of ECOs. Increasing energy costs, or

Stakeholders identification, enterprise goals and standards (both de jure or de facto).

Although an audit is an helpful tool, occasionally it may respond to simply mandatory

requirement or even with an interest on marketing and public visibility.

The Scope or Boundaries: According with the intentions of the Audit and the

stakeholders expectations (see OFA assessment on Section 6: CASCADE

Implementation Kit), the Energy Audit will establish the relevant Airport Areas and

Energy/HVAC systems subject to the inspection. Large buildings and facilities would

need a selection of representative samples of systems to analyse.

The Level of Detail: Normally audits are systematized in levels or phases corresponding

with the level of detail they involve. An initial low level detail audit may involve only rough

analysis of utility bills and energy contracts, estimates about the ECOs cost and

estimated savings, while some other would involve complex financial calculations, or the

use of specialized modelling tools.

Necessary DATA acquisition to perform an Energy Audit, also remains an open question as

there are many types of data and ways to collect information, from measured data (sensors) to

site inspection, the analysis of historical documents regarding energy consumption (e.g.:

collection of bills), or even a detailed monitoring of HVAC system in real operation using portable

battery powered sensors and dataloggers (Short term monitoring).


page 13 of 234

Section 2.1 gives an introduction to the most common energy audits methodology coming from

available literature including a number of standards and international protocols. Section 2.2 aims

at define the CASCADE energy audit approach which has an important role in the CASCADE

implementation methodology (Section 6).

2.1 Overview of existing Standards and Methods for Energy Audit.

This section will describe a sample of twelve standards with the intention of depicting a general

overview of different instruments used around the world. Only some of the tools are standard de

jure 2 , as the one used in Australia and New Zealand (AS/NZS 3598:2000). The rest are

commonly regarded as methods, handbooks or inspection tools but it is difficult to agree in which

are the most commonly used instruments, or de facto3 standards.

Standards vary also in their focus: from very simple and generic energy audits to others targeted

at quantifying specific issues attaining HVAC as degradation or faulty operation, or aimed for

studying retrofitting options for thermal recovery.

2.1.1 ICT for sustainable homes

The “ICT for Sustainable Homes” conference took place in Nice, 2011. A talk given by Enrico

Sabbitini, en titled” Form Energy audits to ICT implementation: A methodology applied to sports

facilities” opened up the discussion on “What is an Energy Audit?”. A tentative definition of

Energy Audit was referred as:

“An energy audit quantifies trends of current energy use, equivalent greenhouse gas

emissions and related costs and recommends energy efficiency improvements.”

(Sabbatini, 2011)

He also stated that the content of an energy audit is also open to interpretation. Within the

presentation by Sabbitini, he defined a 3 level audit, consisting of a Simple, Basic and Advanced

Audit (See Fig. 1 below).

Level 1 – Simple Audit

A simple audit is a remote investigation of the facility. Investigation is made using past energy

invoices, facility survey information, equipment inventories, and usual occupation of the facility.

Level 2 – Basic Audit

The basic audit involves a facility visit and expert evaluation of the facility. Energy consuming

devices are identified, counted, and inspected. Through this survey it is possible to better

characterise energy flows and potential saving measures. The expert conducting the audit also

has a better probability of identifying energy faults.

Level 3 – Advanced Audit

2 De Jure refers to “mandatory”

3 De facto refers to “common practice”


page 14 of 234

The advanced audit involves the use of measuring equipment for particular areas of concern.

Measuring flow rates of an HVAC system, the energy provided by renewables, or the

consumption of a particular device are examples. In some facilities, such data is already

available. In others, such data is not available.

Fig. 1: Workshop: ICT for Sustainable Homes. Nice 2011.

The outcomes and goals of the auditing were defined and are as follows:

The development of a long term relationship with the client;

Characterisation of all energy sources utilised at the facility;

Identification of the type of energy contract in place with the energy suppliers;

Identification of the functional areas present at the facility in question;

A characterisation of the energy flows at the facility;

Recommendations for energy efficiency improvements, and;

Recommendations for next steps (One of the most important outcomes).

Energy monitoring is the basis for effective and target oriented energy management, providing

useful information about energy usage profiles, seasonal changes and possible defects.

The spectrum of tools and services available on the market for implementing a successful

energy management system, extends from simple automated meter reading processing to load

profiling, analysis reporting and visualization.

2.1.2 AuditAC

The AuditAC is the project Acronym for “Field Benchmarking and market Development for Audit

Methods in Air Conditioning” (WSA, 2010). The core aims of this European project (2005-2007)

was to provide tools and information that would enable air-conditioning system inspectors,

auditors and owners across Europe to confidently identify energy saving Opportunities that will

save them money and reduce energy consumption within their Air-Conditioning systems.


page 15 of 234

Under new legislation, governments are obliged to adopt inspection schemes for air condition

systems over a certain cooling output. AuditAC investigated and promoted auditing procedures

as a fundamental way of achieving real savings, in both CO2 and energy, in air conditioning

systems.

Preliminary audit is a first step of the audit procedure where the auditor has a first approach with

the plant. This procedure is very important for the comprehension of the design of the plant and

its use. The auditor will be able, at the end of the procedure, to identify preliminary energy

saving opportunities. Some easy energy saving actions can be made operational immediately

after the preliminary audit, whereas other potential actions may require normally a more detailed

analysis, in order to assess their effectiveness and their economic performance. The actions

requiring a deeper analysis of the system are best performed during the subsequent detailed

audit.

The pre-audit audit structure

In a preliminary audit procedure one detects the errors in the AC systems through data

gathering, visual detection and with measurements. Preliminary audit involves an interview of

the site operating staff, a review of facility utility bills and other operating data, and a walk-

through of the facility (to become familiar with the building operation and to identify obvious

areas of energy waste or inefficiency). Typically, only major problem areas will be discovered

during this type of audit. This level of detail, while not sufficient to take all improvement decisions,

is adequate to prioritize energy efficiency projects and determine the need for a more detailed

audit.

Preliminary audit activities should include the following sequential steps:

1. Identify the air-conditioning system type(s) in use in the building;

2. Evaluate the conditions of use and the operational state of the system;

3. Find out and describe the possible impact of improvements to this system, and;

4. Write up a preliminary audit report.

The preliminary audit is less expensive than the detailed one, but is nonetheless an important

study that can identify very useful savings potential and a list of low-cost savings opportunities,

through improvements in operational and maintenance practices. The preliminary audit

information will be used to underpin the more detailed audit, if the energy saving potentials

appears to warrant further auditing activity. The first step of the preliminary audit process should

be the collection of information.

The information may be collected on the structural and mechanical components that affect

building energy use and the operational characteristics of the facility. Much of this information

can be collected prior to the site visit. Evaluating energy use and systems before going on-site

helps identify potential savings and makes best use of time spent on-site.

The preliminary audit consists of three distinct steps: (1)Preliminary data collection and

evaluation;(2)Site visit and (3)Analysis and reporting.


page 16 of 234

Step1: Preliminary Data Collection and Evaluation

A pre-site review of building systems and their operation should generate a list of specific

questions and issues to be discussed during the actual visit to the facility. This preparation will

help ensure the most effective use of on-site time and minimize disruptions to building personnel.

A thorough pre-site review will also reduce the time required to complete the on-site portion of

the audit.

The first task is to collect and review two years’ worth of utility energy data for electricity. The air-

conditioning system consumption data should be provided if the system energy is measured

separately. This information is used to analyse operational characteristics, calculate some

energy benchmarks for comparison to averages, estimate savings potential, set an energy

reduction target, and establish a baseline to monitor the effectiveness of implemented measures.

The building manager should provide occupancy schedules, operation and maintenance

practices, and plans that may have an impact on energy consumption. This kind of information

can help identify times when building systems such as lighting, recirculating pumps or outside air

ventilation can be turned off and temperatures set back. The building manager should ideally

also provide documentation for all the above information. If the data are not available, or they

don't correspond to reality, then the first action should be to help to collect the data.

Analysing Energy Data

If the A/C system energy consumption is available separately, then a Cooling Energy Index (CEI)

could be calculated to compare energy consumption to similar building types or to track

consumption from year to year in the same building. The CEI consist of calculated ratios based

on the annual consumption and the area (gross or conditioned square meters) of the building.

CEI is a good indicator of the relative potential for energy savings. A comparatively low CEI

indicates less potential for large energy savings. By tracking the CEI using a rolling 12-month

block, building performance can be evaluated based on increasing or decreasing energy use

trends. This method requires a minimum of two years of energy consumption data to establish

the trend line and values including weather correction.

Looking at Loads for cooling

Cooling loads include occupants, lighting, office equipment, appliances, solar gains and specific

processes. High loads are in general easy to detect and the energy management efforts should

be focused in these areas. High loads may reveal opportunities to reduce consumption by

making improvements to the air conditioning equipment, temperature controls, the building

envelope, or to other systems which are affected by operation. After utility use has been

allocated, the auditor should prepare a list of the major energy-using systems in the building and

estimate the time when each system is in operation throughout the year. The list will help identify

how each system uses energy and potential savings. Building systems can then be targeted for

more detailed data collection. One of the easiest ways to evaluate energy data is to. Either

graphing two or more years of monthly data on one graph or graphing only the annual totals for

several years can help.

Building Profile


page 17 of 234

Obtaining mechanical, architectural, and electrical drawings and specifications for the original

building as well as for any additions or remodelling work that may have been done is the first

step to creating a building profile. Any past energy audits or studies should be reviewed. The

auditor can use this information to develop a building profile narrative that includes age,

occupancy, description, and existing conditions of architectural, mechanical, and electrical

systems. The profile should note the major energy-consuming equipment or systems and

identify systems and components that are inherently inefficient. A site sketch of the building(s)

surveyed should also be made. The sketch should show the relative location and outline of each

building; the name of each building; year of construction of each building and additions;

dimensions of each building and additions; location and identification numbers of utility meters;

central plant; and orientation of the complex.

While completing the pre-site visit review, the auditor should note areas of particular interest and

write down any questions about the lighting systems and controls, HVAC zone controls, or

setback operation. Other questions may regard equipment maintenance practices. At this point

the auditor should discuss preliminary observations with the building manager or operator. The

building manager or operator should be asked about their interest in particular conservation

projects or planned changes to the building or its systems. The audit should be scheduled when

key systems are in operation and when the building operator can take part.

Step2: The Site Visit

The site visit will be spent inspecting actual systems and answering specific questions from the

preliminary review. The amount of time required will vary depending on the completeness of the

preliminary information collected, the complexity of the building and systems, and the need for

testing equipment.

Having several copies of a simple floor plan of the building will be useful for notes during the site

visit. A separate copy should be made for noting information on locations of HVAC equipment

and controls, heating zones, light levels, and other energy-related systems. If architectural

drawings are not available, emergency fire exit plans are usually posted on each floor; these

plans are a good alternative for a basic floor plan.

Prior to touring the facility, the auditor and building manager should review the auditor's energy

consumption profiles.

Step3: Analysis and Reporting

Post-site work is a necessary and important step to ensure the preliminary audit will be useful.

The auditor needs to evaluate the information gathered during the site visit, research possible

Energy Conservation Opportunities (ECO’s), organize the audit into a comprehensive report,

and make recommendations on improvements. The report from the preliminary audit, with

possible ECO’s, should be used as the basic input for subsequent more detailed audits.


page 18 of 234

Fig. 2: Overview of the AudiTAC energy audit process

The CEN draft standard prEN15240 (European Commission, 2006) was an important part of this

effort. This standard gives details for inspection of air conditioning systems, and of the

associated air distribution and exhaust systems. It comprises a "normative" (mandatory)

standard plus several "informative" annexes that describe recommended procedures, checklists

etc. (See prEN 15240. Ventilation for Buildings Guidelines for Inspection of Air-Conditioning

systems below)

2.1.3 Harmonac AC

HarmonAC (HarmonAC, 2009), is a project supported by the Intelligent Energy Europe Initiative.

Its main target is to structure a methodology for a regular inspection of air-conditioning systems

over 12 Kw cooling capacity to respond to the EPBD requirements.

The purpose of an Air Conditioning inspection is to determine the energy efficiency of the AC

system in the context of the overall building and of its specific components, the structure and

equipment. Its aim is to generate energy improvement options for the AC system inspected, to

estimate the costs of energy improvements and propose the likely Energy Savings from the

ECO’s identified.

There are two basic phases to an inspection;

1. A pre-inspection phase, that ideally does not require a site visit, where the Inspector

gathers data about the buildings and system to be studied, and;

2. An in-depth detailed inspection, either of the entire building and system or only selected

parts of the building.

The main elements of HARMONAC A/C Inspection Methodologies are:

1. Data collection about the actual building. Identify the installed HVAC system, along

with its current and designed use, and its current building occupancy. This includes

analysis of this data to help identify possible areas of concern or just to reassure the

Inspector that the system operation is normal and reasonable.

2. Physical Inspection - The determination of existing faults or possible improvements to

the Air Conditioning system.


page 19 of 234

3. Inventory - Prior to considering any possible improvements of the air conditioning

system, it is necessary to produce an inventory of the thermal equipment in place and to

collect information about it. Some building owners or facility managers have a well-

documented description of their plants. In other cases, a detailed tour in the building can

produce the necessary information about the installation in order to determine the type of

equipment in place. The existence of certain components implies a certain functioning of

the installation.

4. Different phases - Two or more phases of Inspection may be needed or preferred, e.g. a

first phase might be the collection of the information and evaluation of the collected data,

a second phase the site visit (walk-through), and a third phase the formal analysis and

reporting of these 2 phases. The choice of how to undertake an inspection in practice is

dependent on the system and building to be inspected, and the information available for

the pre-inspection phase.

Phase 1: Information Collection and Evaluation

The aim of this phase is to:

1. Establish a connection and talk briefly with the building operating personnel, owner,

occupants etc. about the HVAC system, comfort, problems etc.;

2. Study the plans and specifications and become familiar with the building, systems,

capacities, equipment, etc.;

3. Examine the overall building energy consumption history AND AC system energy

components consumption history if available. If not, get a complete building energy

consumption history on gas, oil, and electrical use from utility companies and fuel

suppliers. Compare the consumption per unit area per year with other similar buildings

and determine degree of variance, and;

4. Get a detailed list of all maintenance, cleaning, adjustment, repairs and system balancing

undertaken to this point.

Phase 2: Walkthrough inspection procedure

Field Surveys

Make an initial walkthrough inspection to become familiar with the building, systems, equipment,

maintenance, operation status and so forth. Take spot test measurements if needed. If the

walkthrough inspection is sufficient, calculate energy savings from ECO’s for the various energy

improvements, estimate retrofit costs and calculate paybacks.

Make a thorough inspection of building systems and equipment and become familiar with them.

Check out operations, maintenance, malfunctions, comfort and problems. Check and record

equipment specification plates and model numbers.

Conduct in-depth interviews if needed with the HVAC system manager and some spot

information could be provided by occupants in specific thermal zones (e.g. some persons who


page 20 of 234

work in the north side of the building and others in the south side). Review maintenance,

scheduling, performance, comfort and problems of building, equipment and systems.

Make sure to record actual hours of operation of systems and equipment, and the hours of

occupancy of the personnel.

Energy Data

Study and analyse the history of the buildings electrical and fuel energy consumption. Compare

with building consumption indices of similar buildings.

Determine actual existing seasonal and peak energy consumption, along with the efficiencies of

specific systems and equipment based on tests and other data.

Calculate the peak and seasonal heating and cooling loads actually required for the current

conditions of the building. Compare with the design and existing capacities.

Field Tests

Perform measurements of actual flows, temperatures, pressures, etc. in the HVAC equipment

where possible.

Evaluation of Energy Improvements

List all problems with buildings, systems and equipment. Generate energy improvements and

develop those with most potential. Calculate the potential energy savings from ECO’s in

percentage of total consumption and in terms of kWh in a typical season. Depending on the

energy contract, cost estimation should be provided. Estimate costs of retrofitting, payback time

and return of investment.

Phase 3: Report and Analysis

The final report should summarise all the main findings from the Inspection and be clear as to

the ECOs identified to minimise the obstacles to their implementation.

To summarise, three distinct steps are suggested as being required for a FULL Inspection:

1. Preliminary data collection and evaluation

2. Physical survey - site visit

3. Analysis and reporting

This report will then lead the way for a decision to be made on a full scale Energy Audit being

carried out.

2.1.4 prEN 15240. Ventilation for buildings. Guidelines for inspection of air-

conditioning systems.

This European standard describes a methodology for:

“The inspection of air conditioning systems in buildings for space cooling and/or heating from an energy consumption standpoint.”


page 21 of 234

(European Commission, 2006) It is not intended that a full audit of the air conditioning system is carried out, but a correct assessment of its functioning and main impacts of energy consumption, and as a result determine any recommendations on improving the system or possibilities of using an alternative solution. This European standard provides guidelines for these inspections. Inspection Methodology

The following method of inspection is outline within the standard:

1. Pre-Inspection and document collection:

Documents: All design criteria, system characteristics and operational regimes shall be

determined.

Building and system survey: All available original documentation relating to the building and

the installed systems shall be collected and assessed.

Advice in case of outdated, incomplete or missing documentation: Any documentation that

indicates any modifications or alterations to the building, the systems or the use since the

original documents is gathered and assessed.

2. Methodology

The Inspector has to check visually as far as possible to ensure that the equipment described is

present and according to system specification.

The following inspections are carried out:

2.1. Inspection of the refrigeration equipment;

2.2. Inspect for effectiveness of outdoor heat rejection;

2.3. Inspection of the effectiveness of heat exchange to the refrigeration system (indoor units

of split and distributed systems);

2.4. Inspect cooled air, and independent ventilation air, delivery systems in treated spaces;

2.5. Inspect cooled air, and independent ventilation air, delivery systems at air handling units

and associated ductwork;

2.6. Inspect cooled air, and independent ventilation air, delivery systems at outdoor air inlets;

2.7. Inspect building system controls and control parameters, and;

2.8. Energy Consumption metering.

It is advised, that if metering has been installed to monitor air condition systems, Regular checks

on the meter readings can also help in assessing the operation of the system. If no such

metering is in place, it would be advised to install appropriate on the Significant energy

consuming air conditioning plant, and then to record consumption on a regular basis.

3. Reporting


page 22 of 234

The following information is gathered and put in a report which is then given to building

owners/managers for decision purposes:

Details of the property inspected, and the inspector;

List of the documents provided;

Details of the systems inspected;

Details of the results of the inspection: measurements or calculations;

Comments will be made:

On the efficiency of the installation and any suggestions made for improvement;

On any faults identified during the inspection and suggested actions On the

adequacy of equipment maintenance and any suggestions made for improvement;

On the adequacy of installed controls and control settings and any suggestions made

for improvement;

On the size of the installed system in relation to the cooling load and any suggestions

for improvement, AND;

Concerning alternative solutions.

A summary of all the findings and recommendations of the inspection are also included,

including advice on Energy Saving Opportunities and possible retrofits etc.

1. Advice on Alternative solutions and improvements

Significant opportunities are highlighted, for example, improvements / Renovations /

Replacement of specific systems. More details may be provided on Cooling load reduction and

alternative cooling techniques etc.

2. Frequency of Inspection

The frequency is defined at national level, the default number is every 3 YEARS.

This can be more or less frequent, depending on:

Type of building;

Energy impact of the system;

Type of equipment;

Quality of maintenance, and;

Result of the previous inspection.

Detailed cost effectiveness studies are outside the scope of this assessment, but a number of

opportunities may be considered worthwhile recommending for further study by outsourced

specialists. These would generally include alterations that could be made at relatively low cost,

particularly those that might be considered when older equipment is due for replacement.


page 23 of 234

2.1.5 ENAC (Italian Airport Authority)

This method has been recently proposed by ENAC (Italian Aviation Authority) as a base for a

retrofit program of Italian airports (ENAC, 2012). The aims of the Audit are:

The definition of Energy Conservation Measures in accordance with Italian regulations.

The issuing of the Energy Certification

First Level audit:

1. Documentation gathering

Drawing, constructive arrangements/details, technical documentation, thermal systems etc., Bills

3+ years,(electricity gas gasoil bills)

2. Site Visit

Gather schedules and usage of different facilities, trends and patterns etc. Register problems

that they already have, regarding thermal systems and energy systems…may be related.

Photographical reports and verification of all documentations from the previous stage.

3. Data Analysis

Thermal and electrical data analysis is carried out.

Thermal

It is mandatory to use normalised annual data and calculation for average consumption.

(See ). They provide you with a fixed formula and within this formula you have factors

which are provided in accompanying tables as reference. The results of this calculation

should be compared to established data (See Fig. 3 below).

Fig. 3: Grading system for Energy Consumption within institutional buildings proposed by ENAC

Tender for Italian Airport Retrofits

Electrical

It is mandatory to use normalised annual data and calculation for average consumption.

They provide you with a fixed Electrical IENEL formula and similar to thermal equation,

this formula has factors which are provided in accompanying tables as reference. The

results of this calculation should be compared to established data.


page 24 of 234

An interesting thing to note within these calculations is that the normalisation factor used

is volume as conventionally sq. Meters is used.

4. Results

The results are aimed to highlight the critical points to which give the most attention for the

detailed audit, i.e. the areas which provide the greatest number of Energy Conservation

Opportunities.

Second Level audit:

The second level audit gives a structure for a more detailed audit. The scope of this audit should

be defined previously giving flexibility to the stakeholders to decide among a range of detailed

investigations those who fit better and should give more effective results.

The Second level audit is broken down as follows:

1. Detailed data acquisition:

a. Verification of measurements and elaboration of detailed as built drawings and

technical specs. on site by using a collection of 21 templates covering both

building efficiency and facilities.

b. Depending on requirements (here the Audit is not specific), there may be a

number of investigations among those being the following:

Indoor Air Quality data monitoring

Energy consumption monitoring

Thermal bridges evaluation using Infrared Camera

U value characterisation using standardised tests procedures

Thermal Modelling

2. Analysis of the detailed data

3. Issuing of the energy certification and supporting documentation

4. Definition of the Energy Saving Actions

a. Retrofits

Thermal facilities

Thermal envelope

Distribution network (thermal energy)


page 25 of 234

Fig. 4: Overview of the proposed audit by ENAC

2.1.6 IEA Annex 11 (1987) (IEA, 1987)

This comprehensive handbook is the result of the International Energy Agency effort to develop

a recast energy audit method containing inputs from industry, university and government bodies

from different countries and building a collective body of knowledge. IEA Annex 11 defines an

energy audit as:

“A series of actions, aiming at breaking down into component parts and quantifying the

energy used in a building, analysing the applicability, cost and value of measures to

reduce energy consumption, and recommending what measures to take”

(IEA, 1987)

This Annex consists of 2 separate volumes, Volume I and Volume II. Volume I explains and

defines the steps of the Auditing process, with the supporting documentation templates being

provided in Volume II.

Volume I:

“Energy Auditing” is taken to entail a series of actions aimed at the evaluation of the energy

saving potential of a building and the identification and evaluation of Energy Conservation

Opportunities (ECOs).

The approach to energy auditing used in the sourcebook seeks to minimise the cost of auditing

and maximise its effect. This is done through a Staged Audit Process, where the early stages

are wide in scope and low in detail and the later stages being more detailed but less of a scope.

These audit stages are:

1. Building Rating for an audit;

2. Disaggregation of energy consumption;


page 26 of 234

3. ECO Identification;

4. ECO Evaluation, AND;

5. Post Implementation Performance Analysis (PIPA).

Fig. 5: Overview of the audit process within IEA Annex 11. The "Staged Audit Process"

2.1.6.1 Building rating for an audit

The first step is to identify buildings with a good potential for energy conservation, i.e. buildings

with extraordinarily high energy consumption or buildings with design, material, equipment or

usage that can be easily and cost effectively retrofitted. Rough estimates of energy saving


page 27 of 234

potential can also be carried out. This initial step is not intended to address specific Energy

Conservation Opportunities (ECOs).

2.1.6.2 Disaggregation

Disaggregation is the splitting up of the total building energy consumption into its component

parts. There are a number of reasons as to why this is done, i.e., to focus on specific energy

flows and identify areas for retrofit and conservation.

Focusing the attention can help limit subsequent auditing to the areas where the most

productive retrofits could be carried out. This step will directly assist in the identification of ECOs.

2.1.6.3 ECO Identification and ECO Evaluation

A simple data collection allows for identifying applicable Energy Conservation Opportunities

(ECO), which is then followed by the detailed data collection needed for the evaluation of Energy

Conservation Opportunities. The intent is to ensure that every possible ECO is given sufficient

attention so that it can be implemented, considered for a more detailed evaluation, or discarded

as being inappropriate.

A continuous process should then be implemented where ECOs are identified and followed by

ECO evaluation to gradually increase level of detail. As this process continues, overall ECO

implementation plans must interact carefully with the ECO and retrofit sequencing.

The initial stages which relate to the identification of ECO’s do not require measurements,

although final stages of evaluation may require significant onsite measurements or analysis due

to higher levels of detail.

2.1.6.4 Post Implementation Performance Analysis

Following the implementation of the ECO’s, there are two basic checks that need to be done;

1. Problem Identification

2. Retrofit Evaluation

Problem Identification:

Through the monitoring and analysis of energy consumption data, deviations from expected or

past performance data can be identified. To eliminate energy losses, this monitoring should take

place weekly so that problem can be detected as they develop.

Retrofit Evaluation:

There a number of different ways in which a building manager/owner can evaluate a retrofit:

- By comparing pre and post energy consumption;

- By comparing actual energy consumption with that of similar non-retrofitted buildings, or;

- By experimental or testing procedures.


page 28 of 234

Volume II:

An extensive collection of necessary audit templates are provided in Volume II categorised

under the following 4 headings:

1. Audit Procedures;

2. Measurement Techniques;

3. Analysis Techniques, and;

4. Reference Values (RV).

Audit Procedures

The format of the Audit Procedures contained in this Appendix is described by means of the

example below (see Figs: 1 and 2) which refers to quantifying the air filtration rate in a building.

A set of ECO’s are directly linked as seen in the template, i.e. under “Referenced From”.

Fig 2: A sample of a IEA Annex 11 "Audit Procedure" Template (Part 1-Identification and

description). Soucer: (IEA, 1987)


page 29 of 234

Fig. 6: A sample of a IEA Annex 11 "Audit Procedure" Template (Part 2: Cost, Ease of Use,

Accuracy, References, Recommended applications, Alternative Procedures and Diagram) Source:

(IEA, 1987)

The first part of the form is for classifying the procedure of measuring. The second part of the

form can be used in the decision process. “Cost”, “Ease of use”, “Accuracy”, “Recommended


page 30 of 234

application” and “Alternative Procedure” provide the building Owner/Manager with the necessary

information which can be taken into account during the decision process. If they then decide that

they want to go ahead with this audit, the method of procedure is provided in the first part.

Measurement Techniques

The purpose of carrying out a measurement is to know whether a building is operating to the

intended design and to identify and quantify abnormalities in building functions. Measurements

may serve more than one purpose and may be classified according to the objective of the

measurement or the objects measured, for example:

Objectives:

- Building rating;

- Preliminary audit;

- Disaggregation audit;

- ECO identification;

- Post Implementation Performance Analysis;

Objects:

- Environment;

- Envelope;

- HVAC installations or energy systems;

- Comfort level of the users.

One should clearly define or identify:

1. The method to measure;

2. The kind of Instruments;

3. The choice of the place to measure;

4. The duration of measurement;

5. The way to carry out the measurement, and;

6. The cost of measurements.

The format used for presenting Analysis Techniques (AT) is identical to that described for Audit

Procedures (AP) (See Fig. 6: A sample of a IEA Annex 11 "Audit Procedure" ).

Analysis Techniques

A number of Analysis Techniques (AT), including algorithms presented in a common format are

presented in this Volume. All Analysis Techniques here are either required for the evaluation of


page 31 of 234

an Energy Conservation Opportunity, for performing an Audit Procedure, or can be applied for

other reasons during an audit.

The Analysis techniques are arranged in groups and individually numbered following the

standard category system used throughout this Source Book.

The format used for presenting Measurement Techniques (AT) is identical to that described for

Audit Procedures (AP).

Reference Values (RV)

A fundamental part of any audit step is the comparison of measured values with desired values

of the same indicators. This appendix is intended to be a collection of the most frequently used

reference, legal and target values against which values obtained from building audits may be

compared.

Such values may refer to the whole building (e.g. energy indicators) or to component

performance. It must be remembered, however, that often the Reference Values (RV) are

country dependent. Frequently, the average performances and the desired targets vary with

technological level, climate, occupants' habits and behaviour, etc. Even values, which should be

invariant such as fuel, heat, content or material conductivities, are found to vary from country to

country.

The Reference Values are presented in standard forms which are identical to those seen in Fig.

6. The application areas, the audit step, the audit procedures and the specific ECOs, where the

Reference Values are used, are highlighted.

2.1.7 AS/NZS 3598:2000

This standard is being carried out in Australia and New Zealand energy authorities, and it is

targeted to the commercial and industrial sector. It refers to the standard as to be of better use

while employed in the context of an “Energy Management Program” complying with ISO 9000

series standards. Within the AS/NZS 3598:2000 Energy Auditing Standard, an Energy Audit or

Survey is defined as:

“Investigations of energy use in a defined area or site. They enable an identification of

energy use and costs, from which energy cost and consumption control measures can be

implemented and reviewed” (Standards Australia, 2000)

The standard sets out minimum requirements for commissioning and conducting energy audits

which identify cost effective opportunities to improve efficiency and effectiveness in the use of

energy. Like many of these standards, there are 3 different levels of audit:

1. Level 1(Gather data);

2. Level 2 (Gather data), and;

3. Level 3 (Gather previous reports)


page 32 of 234

Fig. 7: Overview of AS/NZS 3598:2000 Energy Audit workflow

The energy user may decide on a single level of audit, or may start with Level 1 audit and use

the results to decide whether to progress to one of the other levels. The content of, and time

spent on, an audit will vary depending on the size of the site and the annual cost of energy use.

Reports from all audit levels will state the identified savings, with the accuracy of the cost and

savings figures being stated also.

Level I Audit (Overview)

The overall energy consumption is evaluated and then analysed to determine whether energy

use is reasonable or excessive. Energy Benchmarks are defined so energy measures can be

tracked and evaluated also. All information gathered by the auditor must be sufficient to enable

the overall efficiency of the site to be determined.


page 33 of 234

(Accuracy of figures: ±40%)

Should be carried out once a year as part of the review of an energy management program

Level 2 Audit (Preliminary assessment of costs and savings)

Within this audit, sources of energy to the site are identified along with the amount of energy

supplied and what the energy is used for. Energy saving opportunities are identified and

statements of costs and potential savings are provided.

(Accuracy of figures: ±20%)

Should be carried out every 3 to 5 years

Level 3 Audit

Level 3 audits provide a more detailed analysis of energy usage along with the savings that can

be made and the cost of achieving these savings. Significant energy users may be highlighted,

with the main focus being on this specified area, or it may cover the whole site. Some areas of

the audits may require specialist attention in order to get the most accurate audit results with

specialists being employed for these areas. Extra local metering may be installed also. This

audit often forms the justification for substantial investment by the building owner. Detailed

economic analysis with an appropriate level of accuracy is required.

(Accuracy of figures: ±10% for costs and ±10% for benefits)

Should be carried out every 3 to 5 years

Fig. 8: 3 Levels of Energy Audits according with AS/NZS 3598:2000

Higher level audits should be carried out every 3-5 years or whenever there is::

1. Proposed and recent significant change in site use or process;

2. Site development or refurbishment;

3. Proposed and recent revision of working practices;

4. Substantial changes in energy price or its availability;

5. A significant increase in the energy performance indicator for the site; or

6. Introduction of a new technology.


page 34 of 234

2.1.8 RP-351 Energy Audit Input Procedures and Forms

The “RP -351-Energy Audit Input Procedures and Forms” was a research project conducted

almost 30 years ago by the American Society of Heating, Refrigerating and Air conditioning

Engineers (ASHRAE). All existing energy audit procedures were catalogued, reviewed and

assessed and recommendations for future use based on the findings of the research were

offered.

One finding from this research project, highlighted:

“If energy use is only measured at the total building level, without assessment of the

quality of services provided through the expenditure of that energy, it is difficult to

accurately assess the degree to which any specific technology can or cannot play a role

and, when technologies are aggregated, for determining which ones to prioritise.

Facilitating an assessment of energy use and delivered building attributes to further a

more refined measurement and expression of energy use and delivered building services

should then effectively serve to prioritize the need for new technology, as well as the

application of current technology in the right places to achieve the most benefit.”

(ASHRAE, 1983)

2.1.9 ASHRAE Procedures for Commercial Building Energy Audits

The American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE)

define an energy audit as:

“The study of a buildings energy consuming systems. It provides a building owner/Energy

Manager/Facilities Manager, a useful insight into how energy is being used and where it

is being wasted.” (ASHRAE, 2011)

ASHRAE have provided standards for energy companies to use when conducting an energy

audit. Three different levels of energy audit have been established with Level I being the least

detailed, and Level III being the most detailed. By knowing what each level entails, a building

owner can determine which type of audit will be the most cost effective.

Level I Audit (Simple walk-through)

A Level I Audit is a simple building walk-through. It is the most beneficial type of energy audit

that will result in only a high-level analysis of energy use. Energy conservation measures (ECMs)

will be identified, but no cost analysis will be performed.

Level II Audit (Energy Survey & Analysis)

A Level II Audit looks at all base building systems (electricity, heating and air conditioning,

telephone, water supply, drainage, gas) and examines how they use energy. It begins with a

study of past energy bills and is followed by investigation of current performance. The energy


page 35 of 234

audit report will include a breakdown of energy consumption and will outline the low- to no-cost

measures that can be implemented to reduce energy use.

Level III Audit (Detailed Analysis of Capital-Intensive Modifications)

A Level III Audit is the most detailed audit. It will provide a granular analysis of energy inputs and

outputs in a building. In addition to base building systems, the building envelope will be

examined to ensure efficient use of heating and cooling resources. As part of a Level III Audit,

data logging equipment will be used to record temperature, humidity, and the hours of operation

for the major building systems and equipment. Energy Conservation Measures (ECMs) will be

identified and accompanied by an investment-grade cost analysis. Cost savings for ECMs will be

determined using computer simulation. The ECMs will be assessed singularly and collectively to

investigate the interactive effects of the measures and their dynamic effect on the building

conditions using hourly weather data for a full calendar year.

The chart below summarizes each level:

Fig 3: The three levels of ASHRAE Energy Audit

2.1.10 ASME (American Society of Mechanical Engineers)

This Standard is intended for energy managers, facility managers, plant engineers, maintenance

managers, plant managers, environmental health and safety managers, plus others across a

broad range of industries.

This Standard sets the requirements for conducting and reporting the results of:

1. Process heating energy assessment;

Leve

l 1

Rapid assessment of building energy systems

Building energy benchmark

High-level definition of energy system optimisation opportunities

Outline applicable incentive programs

Leve

l 2

Detailed building survey of systems and operations

Breakdown of energy source and end use

Identification of EEMs for each energy system

Range of savings and costs for the EEMs

Spotlight on Operational Discrepancies

Identification of EEMs requiring more thorough data collection and analysis (ASHRAE Level-3)

Leve

l 3

Longer term data collection and analysis

Whole-building computer simulation calibrated with field data

Accurate modeling of EEMs and power/energy response

Bid-level construction cost estimating

Investment-grade, decision-making support


page 36 of 234

2. Pumping System Assessment that considers the entire system, from energy inputs to the

work performed as the result of these inputs;

3. Steam Systems;

4. Compressed Air Systems energy assessment (that considers the entire system, from

energy inputs to the work performed as the result of these inputs.

Following subsections will describe in more detail each sub-standard.

2.1.10.1 ASME–EA–1–2009 (Process Heating Systems)

This Standard covers process heating systems that are defined as a group (or a set, or

combination) of heating equipment used for heating materials in the production of goods in an

industrial plant. These systems, commonly referred to using terms such as furnaces, ovens, and

heaters, use heat sources such as fuels, electricity, steam or other fluids to supply the required

heat. Source: (ASME, 2009)

2.1.10.2 ASME–EA–2–2009 (Pumping Systems)

This Standard covers pumping systems, which are defined as one or more pumps and those

interacting or interrelating elements that together accomplish the desired work of moving a fluid.

A pumping system thus generally includes pump(s), driver, drives, distribution piping, valves,

sealing systems, controls, instrumentation, and end use equipment such as heat exchangers, for

example. This standard addresses open and closed loop pumping systems typically used in

industry, and is also applicable to other applications. Source: (ASME, 2009)

2.1.10.3 ASME–EA–3–2009 (Steam Systems)

This Standard covers steam systems that are defined as a system containing steam generator(s)

or other steam source(s), a steam distribution network and end-use equipment. Cogeneration

and power generation components may also be elements of the system (gas turbines,

backpressure steam turbines, condensing steam turbines).

An assessment may also include additional information, such as recommendations for improving

resource utilization, reducing per unit production cost, and improving environmental performance

related to the assessed system(s). Source: (ASME, 2009)

2.1.10.4 ASME–EA–4–2010 (Compressed Air Systems)

This Standard covers compressed air systems, which are defined as a group of subsystems

comprised of integrated sets of components, including air compressors, treatment equipment,

controls, piping, pneumatic tools, pneumatically powered machinery, and process applications

utilizing compressed air. The objective is consistent, reliable, and efficient delivery of energy to

manufacturing equipment and processes.

An assessment complying with this standard need not address each individual system

component or specific sub-system within an industrial facility with equal weight; however, it

should be sufficiently comprehensive to identify the major energy efficiency opportunities for


page 37 of 234

improving the overall energy performance of the system. This Standard is designed to be

applied primarily at industrial facilities, but many of the concepts can be used in other facilities

such as those in the institutional, commercial, and water and wastewater facilities. Source:

(ASME, 2010)

2.1.11 EINSTEIN Audit Methodology.

The EINSTEIN audit methodology and tool-kit has been developed in the Framework of the

European projects “EINSTEIN4 (expert-system for an intelligent supply of thermal energy in

industry)” and “EINSTEIN-II 5 (expert-system for an intelligent supply of thermal energy in

industry and other large scale applications)” with the financial support of the European

Commission.

The EINSTEIN thermal Audit focuses on large scale consumers with high thermal energy (heat

and cold) demand in a low and medium temperature ranges up to 400°C. Typical areas of

application are:

Manufacturing Industry: Food, Chemical, Textiles (etc.);

District heating and cooling networks;

Tertiary sector buildings or building complexes;

SWRO Desalination Plants.

The EINSTEIN approach for Energy Audit attempt to solve some of the problems encountered in

the above-mentioned industries by providing a tool-kit with the following advantages:

Use of standardised models for data acquisition and proposal of ECOs, with a

systematised characterisation of typical thermal industrial processes;

“Quick and Dirty” estimation tools. This method overcomes the lack of information,

unavailable data and shorten the time duration of the energy audit by simplified

calculations;

Semi-automatisation of the auditing procedure and proposal generation by the use of

databases and the EINSTEIN software tool. The main aim here is to allow non-

specialised personnel evaluate ECOs for complex systems in a simplified way;

4 EINSTEIN (Contract N°: EIE/07/210/S12.466708, Project Coordinator: Christoph Brunner,

Joanneum Research - Institute for Sustainable Techniques and Systems, Austria), 2007-2009.

5 EINSTEIN-II (Contract Nº: IEE/09/702/SI2.558239 .Project Coordinator: Hans Schweiger,

energyXperts.NET, Spain), 2010 – 2012.


page 38 of 234

Web-based data submission and short questionnaire using a block based expert

systems software tool.

The EINSTEIN Energy Audit process is described in Fig 4, it is made up of 10 steps grouped in

four phases: (1)Pre-audit, (2)Audit, (3)Evaluation of alternatives, and (4)Proposal. The emphasis

of this tool is on thermal processes, which are methodically described by the EINSTEIN

foundation definitions. These standardised approach gives an straightforward procedure for

thermal analysis of complex systems. Some of the techniques used for thermal analysis are:

Energy flows convention tool

Standardised process models

Standardised demand profiles

Pinch-analysis and heat integration

Another important feature of EINSTEIN is the use of remote data acquisition (using telephone

surveys, online web-software tools), in the pre-audit stages. The Audit stage, involves a site

survey focused on thermal systems, specially targeted to the design of waste-heat recovery and

the adoption of alternative energy sources, with a strong prominence of process-integration

methodologies for energy improvements.


page 39 of 234

Fig 4: Overview of the EINSTEIN Energy Audit workflow. Source: (energyXperts , 2012)

Another important feature of EINSTEIN is the use of remote data acquisition (using telephone

surveys, online web-software tools), in the pre-audit stages. The Audit stage, involves a site

survey focused on thermal systems, specially targeted to the design of waste-heat recovery and

the adoption of alternative energy sources, with a strong prominence of process-integration

methodologies for energy improvements. In this way, energy auditing becomes very much an

automatized process, supported with free accessible and user friendly array of tools.

2.1.12 Short Term Monitoring

Energy Audits targeting HVAC systems can be carried out using short-term monitoring

techniques. This is the application of specialized software and hardware tools to systematically

gather and analyse data typically over a two week period to evaluate the performance of building

energy systems, such as HVAC, controls, and lighting. Diagnostics based on short-term

monitoring can clarify how the systems in a building actually perform. The data analysis results

using these techniques allow you to make decisions with the confidence of knowing how

systems are actually performing. Diagnostics based on short-term monitoring can reveal and

unravel problems created over time that would be very difficult to identify in a typical service call.

The premise is that by looking at graphs that represent key relationships of how the system

operates over time, operating efficiencies can be clearly identified.

Fig. 9 Short Term Monitoring Equipment. Source: (Field Diagnostics Services, Inc., 2012)

Short-term monitoring using typically carried out using battery-powered data loggers as a

portable data acquisition device and specialized software. These system, as the one shown in

Fig. 1, is four-channel logger that records:

Temperature

Relative Humidity

Current/Power


page 40 of 234

Pressure

Air Flow

Standard Output Signal (customizable)

Lighting parameters (optional)

One of the key features of portable dataloggers is that the battery supply energy to the sensors

needed to operate. It only requires a 120 volt outlet to plug a transformer into to create 12 volts

DC to power a humidity sensor or flow sensor. By drawing directly from the battery in the data

logger it makes the installation. The battery is designed to run long enough to collect the data

needed for short-term monitoring in HVAC systems

The short-term monitoring process is divided into three steps: (1)project planning,

(2)measurement of system data, and (3)data analysis.

1. Planning

The objective of the planning step is to establish the data streams that need to be collected

by the data acquisition equipment. The person responsible for the diagnostic activity

conducts all the tasks necessary to determine what measurements should be made and

prepares the monitoring equipment. The activities in this process include:

Stating the goals and objectives of the monitoring and diagnostic processes, including

any reports provided;

Obtaining copies of mechanical plans and specifications, including control drawings and

sequences of operation;

Site visit to the facilities with the O&M personnel to gather information about the building

and its systems;

Interviewing O&M staff to discuss obvious or chronic problems, operating and occupancy

schedules, operation of the EMS, and any other relevant information it can be provided

Determine the methodology used to analyse the data;

Develop a list of data requirements based on the plans and building tour and determine

where all the measurements will be made in the building;

Assemble the data loggers and sensors;

Program the data loggers.

2. Measurement of System Data

The objective of the measurement step is to collect the data needed for the analysis. The

HVAC system audited should be operated in a normal manner during the monitoring period.

The activities in this process include:

Install data acquisition equipment in the building (central plants, systems, and zones);


page 41 of 234

Verify the correct operation of all equipment;

Operate the building in a normal manner.

3. Data Analysis

The objective of the data analysis step is to understand the operation of the systems.

Systems working properly and ones operating inefficiently will be identified in this process.

The activities in this process include:

Download the data from the loggers to the computer;

Use software-based automated analysis tools or spreadsheet to create the graphs

needed to detect problems;

Calculate the energy and cost savings that can be achieved through repairs,

modifications, and equipment replacements.


page 42 of 234

2.2 CASCADE Energy Audit

This section defines the CASCADE energy audit approach which has an important role in the

CASCADE implementation methodology (Section 6). The definition of the CASCADE energy

audit scope is a result of iterative process that has compared different available audit

approaches on one hand and, on the other hand, has supported the definition of the CASCADE

solution, integrating stakeholder’s requirements and technologies provider’s solutions.

Table 2 gives and overview of the CASCADE energy audit in relation to the methodologies and

approaches discussed in section 2.1. From the table it is possible to identify the 3 main

objectives of the CASCADE methodology. It appears clear form this table that the final goal of

the CASCADE energy audit is not a detailed energy audit that identifies a list of energy

conservation measures, but it is an approach that supports the gathering of information needed

to for the CASCDE solution that is FDD centred. In the table it is possible to identify which are

the actions to be carried out within the CASADE energy audit and which of the objectives are

they useful for. The main objectives of the CASCADE energy audit are the following:

Objective 1 – Understanding Airport Energy Flows identifying SEUs

Airports are large environments. In many facilities and especially in small and medium

size airports only very few and aggregate information on the actual energy consumption

is available (fuel bills, technical data of boilers, etc.). Therefore consumption of individual

processes and sub-processes has either to be estimated or determined by costly and

time-consuming measurements. To get a better understanding of airport energy flows, a

reliable, quick and cost/time-effective tool is required, so that better decision making is

completed at initial stages of the project. Energy Flows using Sankey diagrams or

EINSTEIN (energyXperts , 2012) diagram conventions are useful starting point for

CASCADE Energy Audit. Often this task in already carried out by the airport energy

management office, in this case this becomes an item for interaction with the stakeholder

for CASCADE solution scope definition. A study of airport energy flows, like the one in

Fig. 10 and Fig. 11 for MXP and FCO airports, outline the Significant Energy Users

(SEUs) and support the definition of target area and system for CASCADE

implementation. This process follows the ISO 50001 4.4.3 Energy review approach. If

improvements opportunities are identified they are also collected for ISO 50001 approach

supported by the CASCADE solution.

Objective 2 – Detailed study of HVAC systems to sensor evaluation and installation and

support modelling activities

Targeted areas and systems/equipment identified required a more detailed focus.

Specific DATA about component level equipment is not used in common practice Energy

Audits, which are more focused at a high level energy conservation measures. We need

this for installation of additional sensors and also for modelling of HVAC systems and

components for model based FDD. If model based FDD requires building details such as

construction and materials, these are gathered in this phase.


page 43 of 234

Objective 3 – Validation plan compliance (data for baselining)

Airport Energy audit key target is the creations of the initial data set to establish the

baseline for measurement and verification of energy savings, according with the

validation plan described in D2.2 and ISO 50001 (section 4.4.4 Energy baseline).

Others aspect of an airport facility that can impact on CASCADE implementation are covered

within other processes according with the CASCADE Implementation Kit. Standards, strategic

goals or the characterisation of the Operations and Maintenance Processes are studied in the

OFA assessment (Organisational Factors Assessment). Furthermore particular requirements of

CASCADE IT implementation will need a specific assessment on IT and BMS facilities on

Airports covered by the CASCADE BMS/IT assessment (see Section 6.2.3). Like for the other

process the final energy audit template will be part of the replication plan deliverable.

Fig. 10 Malpensa airport Energy flows 2010


page 44 of 234

Fig. 11 Fiumicino airport energy flows 2010


page 45 of 234

Table 2 CASCADE Energy audit comparison


page 46 of 234

3 Key Performance Indicators

This section documents the work done in Task 2.2 that aimed at giving a formal definition of the

performance metrics taking into account baselining, benchmarking and a tier structure. Tier

structure was focused on capturing the best way for determining the energy performance of

various airports public zones and systems/subsystems needed to monitor and evaluate their

specified operation described in D1.1. Standardization works for the measurement and the

characterization of these systems with a focus on HVAC systems has been achieved as a result

of the present task. The tiers approach defined here (especially tier 4 - see tiers definition in

Section 3.3) has be have been taken into consideration in the definition of the minimal data set

(WP3) and have been inputted into the analysis and FDD algorithms to detect normal or faulty

behaviour described in WPs 4.3 and 4.4.

After presenting the approach and a list of possible KPIs, section 3.5 describes how KPIs

selection method that depends on specific requirements on a case by case basis and how this

process is embedded in the overall CASCADE implementation methodology (6).

KPIs are measurements used to provide information about the actual operation of a process, an

organisation or, as in our case, energy consumption, CO2 emissions and the behaviour of

mechanical devices. KPIs must be carefully chosen and constructed, they must reflect a clear

picture of what is important for a system, what are the areas of activity to monitor and the effect

of policies, actions and corrective measures.

KPIs are tools for measurement of success. Performance-based metrics are becoming a

common instrument in public and private organisations used to analyse and monitor

performance, and finally to drive informed decisions. KPIs for an Airport can be used in many

areas (e.g.: Safety, Security, Finance, Operational Performance, Customer Satisfaction,

Sustainability, etc.), and can be one-dimensional (e.g.: CO2 emissions), or rations of two or more

parameters (e.g.: CO2 emissions per passenger). For that reason, their construction, and the

subsequent understanding of the parameters involved are of vital importance to those who

select them. Wrong choice of indicators, errors due to not normalising metrics, unclear

definitions of boundaries of measurement, hierarchy levels not clearly defined, or simply the

definition of too many KPIs are common drawbacks when employing performance measurement

techniques.

Standardised performance metrics are important because allow to measure and present them in

a way that they can be used for comparison with previous performance or other

buildings/systems performance. Deru and Torcellini gives the following definition for

performance metrics:

“A metric is a standard definition of any measurable quantity, and a

performance metric is a standard definition of a measurable quantity that

indicates some aspect of performance. Many other terms are used with a

similar meaning, such as performance indicator, performance index, and

benchmarking. Performance metrics need certain characteristics to be

valuable and practical. A performance metric should:


page 47 of 234

Be measurable using standard parameters or easy to be determined from other measurements.

Have a clear definition, including boundaries of the measurements.

Indicate progress toward a performance goal.

Answer specific questions about the performance.”

(Deru and Torcellini, 2005)

KPIs selection are closely linked with measurement and verification protocol IPMVP, which is an

explicit tool adopted in the CASCADE Validation plan (Task 2.4). In particular, Options A and D6

for determining energy savings will be implemented during the Monitoring and Controlling

activities (see Section 4.4.6).

To understand KPIs meaning, some concepts must first be established:

Difference between absolute data and normalised data;

Definition of boundaries: specifying a meaningful subdivision of zones and energy

systems within the zone or providing service to it; Timeframe of measurements:

regarding time range quality of measured data, whether the data is absolute,

cumulative, seasonal, instantaneous etc.

Strategic targets to measure performance against (set by the organisation, based on

standards, regulations, protocols, etc.);

Thresholds and allowances to define optimal operation;

Correction for short term data acquisition: Time extrapolation and Weather correction.

(According with ISO 15603:2008) (ISO, 2008)

Measurements needed to construct the KPI and necessary equipment. Cost-benefit

analysis is needed in case extra sensors or associated cost are required.

Section 3.3 will establish the physical boundaries subdivision in Tiers. In Section 3.1 the

utilisation of KPIs as a benchmarking tool will be introduced. Section 3.2 will focus on KPIs

specifically directed to measure HVAC systems performance. Eventually, an inventory of

indicators will be identified with the intention building a repository of KPIs and related information

in Section 3.4 and finally in Section 3.5 a selection method using cost-benefit analysis will be

described.

3.1 KPIs for BASELINING and BENCHMARKING

Baselining is the process of determining a KPI value "as is", in other words, before any Energy

Action have taken place. Baseline value are crucial as a point of reference and will serve to

determine whether or not Energy Conservation Measures (ECOs) implemented were successful

and by how much. To determine baseline values it is imperative to calculate values for the

relative index dating back to at least one year, so that dynamic factors such as weather and

6 IPMVP defines four options to determine energy savings (A,B,C and D), being Option (A): Retrofit

Isolation: Key Parameter Measurement and Option (D): Calibrated Simulation


page 48 of 234

demand are accounted for. Should such data be unavailable it is imperative to model

building/system performance in order to derive close estimations.

Benchmarking may be external or internal. An external benchmark refers to available

information about a reference building of comparable use, size, assets and position. For

instance, an Airport global energy consumption KPI (kWh/m²) can be tested against a

benchmark describing average energy usage (kWh/m²) of Airports of comparable size in the

same climate zone with comparable operation and traffic rates. An internal benchmark, helpful

when, as often happens, external benchmarks are not available, may involve selecting from an

Airport facility those actions or systems/subsystems/components scoring the highest and setting

them as a standard. Benchmarks in general may assist greatly in managing performance targets

for KPIs describing energy / operations.

In general, to make comparisons of annual energy use between buildings is possible but the

following prerequisites must be fulfilled:

The energy data is monitored/calculated in a similar way;

In most climates heat energy data must be adjusted to a standard “normal” year for

the location of each building;

In climates where cooling energy is “climate-driven” cooling must also be adjusted to

a standard year for the location of each building;

If the buildings have very different time of use (use pattern), say normal office hours

and around-the-clock use, all energies must be adjusted to a standardized use

pattern;

The physical factor, e.g. a floor area or conditioned air volume, must also be defined

in a similar way between the buildings.

Specifically about airports, there are a number of different factors which surely impact on airport

energy consumption and could subsequently result in further interesting studies, for which more

data would be needed. These include factors such as:

Airport size (area and volume of conditioned spaces, area of externally exposed

building envelope);

Type of construction of the building envelope;

Location-Climate. Heating and cooling degree days (HDD and CDD), and other

weather parameters like solar radiation, humidity levels, etc.;

Operating conditions, like opening hours and schedules, passengers and freight

traffic;

HVAC systems and controls.

The CASCADE approach in terms of both baselining and benchmarking is defined in the

Validation plan (D2.2)


page 49 of 234

3.2 KPIs for HVAC

Given the situation of the pilots in which the main systems to apply the CASCADE solution are

HVAC systems this section gives a bit more of theoretical background on how HVAC KPIs can

be structured.

3.2.1 Energy Efficiency KPIs

Energy efficiency Key Performance Indicators are generally regarded as ratios between energy

inputs and outputs. Energy is consistently measured in the same units. The concept of efficiency,

or η is a non-dimensional quotient widely used in the engineering field

3.2.2 Service level KPIs

Service level KPIs introduce a number of difficulties, here the concept of performance or

Intensity is defined as the ratio between energy input against the output unit of service.

Definition of service provided becomes difficult and non-standardised. Service level KPIs can

provide useful information about a system performance and can be constructed upon any useful

system metric. Service Level KPIs are normally used as meaningful indicators to measure

feedback about effectiveness of corrective actions, e.g. using KWh/passenger, the effects of set

point optimisations can be effectively tracked down, particularly when peak loads occur.

Particularly for HVAC related processes, levels of service can be difficult to assess, due to

discretional interpretation and must be agreed upon during the initial phase of the project, and

aligned with stakeholders interests. Service level for CASCADE implementation (in future

replications) will be explored to measure (during the project pilot implementation and

demonstration) performance in the following areas:

Indoor Air Quality (IAQ): Predicted Mean Vote (PMV), Percentage of Persons

Dissatisfied, CO2 can be used to asses and benchmark energy used in HVAC to provide

required levels of service. Faults can bring IAQ levels out of acceptance thresholds and

time dimension can be introduced to assess incidence of undesirable conditions

(frequency, number of occurrences, duration of inappropriate conditions etc…);

Airport specific KPIs: Data related to number of passengers (PAX), traffic units (tu) or

number of flights can be used to determine energy intensity of different parts within an

airports. Interrelations between buildings, energy systems and their operations,

combined with occupancy data can provide useful information. For instance, two different

zones can lead to different energy consumption levels and provide the same level of

service (same flights/passengers), same equipment may be operated ineffectively, or

some zones in the airport may be under-or over utilised.


page 50 of 234

3.2.3 Energy Intensity (EI) and Energy Efficiency (η) for HVAC systems.

Applying these previous concepts (Energy Efficiency and Energy Intensity) to HVAC systems at

a global level leads us to the following formulations for annual normalised global HVAC KPIs:

For HVAC Energy Intensity7:

and for HVAC efficiency (annually):

The concept of energy demand has been introduced recently in literature regarding KPIs for

HVAC systems (Perez-Lombard et al., 2012). Here the concept of IDEAL demand is introduced,

being defined as the amount of thermal energy that a virtual device or “ideal system” should

theoretically add to or extract from the space in order to maintain certain comfort conditions

during a given time period. Ideal demand is also referred to as “space energy need“(EN 13790)

or “room energy demand” (EN 15243). It may be calculated from a thermal balance equation but

may not be measured on-site. Ideal demand depends on many factors as weather, occupancy,

building envelope, and required comfort conditions8.

Both indicators have significant drawbacks: while Energy Intensity is calculated from two real

and measurable magnitudes, Efficiency needs the calculations of ideal demands thus entangling

assumptions and simulation. Efficiency therefore is a difficult indicator to communicate to

stakeholders as long as standardised methods for calculating HVAC ideal demand are not

common practice. Energy Intensity can easily sustain uncertain assumptions. For instance, it is

simplistic to assume that the delivered service is being provided at a 100% of effectiveness.

Such supposition would hide episodes where defective systems are in operation, thermal loads

cannot be met by HVAC systems due to undersizing, or setpoints are not finely tuned.9 There is

no an standard solution for this problem, so a robust definition for “service” should be solved on

a case by case basis.

7 m3 may be more also interesting for airports since they are big spaces with variable height.

8HVAC Real Demand: real demand on the HVAC system that considers heat transfer within actual

facilities responsible of providing useful heating or cooling to conditioned spaces. The latter deals with the

performance of real HVAC systems and may be calculated via simulation or measured on-site.

9 One way of solving this problem would be the application of a correction factor created by first

subtracting the time where satisfactory conditions are not met (e.g.: faulty operations of systems) and

second, extrapolating this to a full year period.


page 51 of 234

3.2.4 KPIs Hierarchy and Aggregation Level

HVAC systems efficiency indicators can be broadly categorised in two categories global level

(HVAC) and component level (EQUIPMENT). Global HVAC energy consumption can be easily

calculated by summing up energy used by all lower level components (EQUIPMENT). In

between these two broad types, there is room for further additional level subdivision. Classically

this subdivision partition is being done in three parts: (1) Cooling, (2) Heating and (3)

Ventilation/Extraction. This division makes it difficult to quantify and allocate energy consumed to

service provided whenever a system is consuming energy by simultaneously providing heating

and cooling. Cooling/Heating situations are usual in Airports facilities (e.g.: Dual Duct Air

Handling Units in Malpensa Airport and Variable Air Volume air distribution boxes).

Fig 5 Aggregation Levels of HVAC systems. (Source: L. Perez-Lombard et al. 2012)

CASCADE will explore ways of solving these issue introducing a new level (SUBSYSTEM), as

shown in Fig 5, comprising: (1) Heat Generation (2) Cool Generation (3) Air Transport, and (4)

Water Transport. With this subdivision, energy consumption of each subsystem can also be

subdivided in two, heating and cooling.

This approach makes it possible to use better aggregation levels in relation to heating, cooling

and ventilation duties. That means that calculations for total cooling, heating, and total HVAC

energy consumption can be done using the following expression:


page 52 of 234

Segregating heating and cooling energy consumption can be carried out proportionally to

instantaneous heating and cooling loads, but further research is necessary for simultaneous

heating and cooling generation devices into a system or to assess energy used for air transport

(Fans) when it is used by the same HVAC system providing heating and cooling. CASCADE will

explore the construction of HVAC KPIs using available data from BMS and advance Dataloggers

and reflect the result of this study in the final CASCADE methodology definition in the replication

plan.

3.3 STRUCTURING KPIs by TIERS

One useful way of categorise KPIs is to arrange them into a tiers structure. Tiers are domains of

interest that affect a specific set of stakeholders and reflect a hierarchical structure. Some of the

KPIs can be built by simply summing up a group of lower level indicators. It is also a helpful

instrument to assign responsibilities, track the impact of faults detected, and evaluate the

effectiveness of correction actions or energy conservation measures. Tiers structure can be

used to structure knowledge and further investigations with the airports and the software

specialists will be carried out in the next steps of the CASCADE project to integrate it in the

ontology. CASCADE proposition is to use 4 KPIs Tiers levels, described as follows:

Tier 1: Global KPIs.

KPIs at Tier 1 provide a high level view of airport. Tier 1 measurements typically involve no

additional investment, as can be constructed using existing data extracted from utility bills,

physical measurements etc. Tier 1. Timeframes are usually monthly, seasonally and annual

for measurements and indicators. This activity is already carried out by the airport energy

management and reported at management level to support high level decision making, to

meet high level target values required by sustainability programmes, and/or to communicate

relevant performance data to stakeholders or the public.

Tier 2: Service KPIs

These indicators provides a detailed breakdown of the global KPIs into different types of

services provided (heating. cooling, energy generation) or a useful subdivision of the airport

in zones depending on the connection in the energy network. Tier 2 indicators provide a

more segmented breakdown to the Energy Management Office (EMO) and Management

staff. Tier 2 KPIs can be summarised as follows:

By sector:

Global KPIs can be subdivided conveniently by areas in the same facility

(zones within a terminal, different buildings within a complex etc.)

whenever this division provides a consistent indicator for benchmarking

and comparison purposes.

By service:


page 53 of 234

Energy Generation;

Ventilation efficiency;

Heating efficiency;

Cooling efficiency.

Tier 3: System/Subsystem KPIs

Tier 3 indicators target basically the energy efficiency of complex systems (made up of

different pieces or equipment) and the additional subdivision of subsystems described in

Section 3.2. Some of the KPIs in this Tier can be constructed by simply adding up the

relevant indicators from Tier 4, others may follow a recommended method, e.g.: Air Handling

Units and the EUROVENT 6/8 Methodology (EUROVENT , 2005). They provide detailed

information on specific subsystems or zones. Operations and maintenance dedicated

personnel are the stakeholders more related to this set of indicators. Seen below, is a list of

systems that CASCADE will explore under the System/Subsystems Tier:

AHUs;

Site Energy Generation: Renewables, CHP;

Cooling Production:

Compression Chillers;

Absorption Chillers.

Heating Production:

Boilers;

Combined Heat and Power (CHP).

Air Transport;

Water Transport.

Tier 4: Component Level KPIs

Tier 4 focuses on the lower level metrics in the HVAC spectrum. They provide detailed

information closely related to the measurements to support FDD algorithms developed in

WP4. At this level, decision making process described in Section 3.5 should be taken into

account to build the minimal data set required for FDD algorithm and CASCADE

implementation (this process has been followed within WP3). Monitoring of KPIs at a

component level is of interest to the O&M personnel. Again, below is a list of equipment

components CASCADE will consider:

Air filters;

Fans;

Pumps;

Cooling Coils;

Heating Coils;

Humidifiers;

Heat Recovery devices (Heat exchanger, Thermal wheels, etc.);


page 54 of 234

Air control devices (Terminal Variable Air Volume boxes).

After describing the 4 Tiers system organisation for HVAC, three additional types of KPIs will now be

introduced: Indoor Air Quality (IAQ) KPIs, Operations and Maintenance (O&M) KPIs and Airport Specific

KPIs. These can be considered also fitting into some of the 4 tiers structure, this can be seen in Fig 6.

Tier 1/Tier 2: Indoor Air Quality KPIs

KPIs in this category include those indicators intended to evaluate healthiness of the indoor

environment and the comfort of building energy users. Outcomes from FP7 research project

PERFECTION10 (Perfection Consortium, 2010) will be used as a base point to construct IAQ

KPIs for CASCADE.

Tier 1/Tier 3/Tier 4: Operations and Maintenance KPIs

Operations and Maintenance practices are useful for maintaining service level satifaction

and building/system proper effectiveness and efficiency. O&M KPIs must be constructed and

selected in accordance with business strategic goals (Top-down approach), but also in a way

that shows a clear connection with those persons or groups that may influence their

outcomes (Bottom-up approach). This approach makes it more effective to assign task

responsibility and accountability, as KPIs measures can be directly influenced by specific

personnel. Efficiency of O&M operations can be assessed from several points of view, being

the more significant the following:

Reliability of equipment;

Quality and speed of O&M;

O&M activities costs;

Effectiveness of maintenance cycles (calendar based could be improved with

performance based cycles).

It is important to point the special link existing between O&M and economic performance.

Several KPIs commonly used in industry refer to the economic value of components,

Estimated Replacement Value ERV11 ), or overhead costs. Therefore a connection with

enterprise systems, e.g. IANMMAP (Inventory and Maintenance Management Application)

becomes of vital importance.

Tier 1/Tier 2: Airport Specific KPIs

Airport specific KPIs are those indicators constructed using data collected from Enterprise

Management Systems (see Section 5.2.4.1). Airport related information like number of

10 FP7 PERFECTION: Coordination Action For Performance Indicators For Health, Comfort And Safety

Of The Indoor Environment. Grant Agreement 212998

11 ERV: Estimated Replacement Value


page 55 of 234

passenger (PAX) or flights can be associated with energy related indicators, weather data,

etc. One of the CASCADE possibilities is to link energy consumption data with airport

operational usage, future investigations may be needed with the above described goals of:

- Building a more precise energy demand forecast based in real data acquisition;

- Comparing energy trends, thermal loads and systems efficiency against airport service

levels. Comparison may be between zones or systems within the same airport, between

different airports.

- Detecting abnormal trends by comparing with average or “normal” patterns;

- Assessing the impact of typical crisis-scenarios (energy shortage, heat waves, peak

demands, strikes, etc.) and provide airports with a modelling environment better manage

contingency planning.

Fig 6. KPIs 4 TIERS Structure

3.4 CASCADE KPIs REPOSITORY

The following section will serve as a collection of KPIs from which the adequate one can be

selected according with previously established targets and objectives. KPIs have been grouped

into categories so that different stakeholders may focus on specific areas of interests and

choose the indicators accordingly to their requirements.


page 56 of 234

Special emphasis in CASCADE project is on the airport specific metrics. Energy usage and

delivered service contrasted with occupancy data, flight-related building and service level

monitoring, as well as weather data are important for correlational studies research, forecasted

energy consumption.

Finally, every KPI will require a development of complete description. This will be developed in

the implementation phase (See Section 4.4.4) in a table-like format including:

Definition, parameters and formula of the KPI, naming convention;

Measurement points description and diagram;

Meters needed, positions and specifications;

Standards and key documentation;

CASCADE Ontology related information.

The collection of all tables will create a repository of information that would be a part of the

CASCADE implementation package as a reference manual. These tables are the initial

proposed set of performance indicators but are not thought to be comprehensive of all possible

systems and particular stakeholder requirements. The intention is not to expand this list but to

establish a process that selects CASCADE KPIs taking into consideration all stakeholders

requirements.

Table 3: TIER 1 - Global KPIs

KPI CODE Timeframe

TIER 1- Global KPIs

An

nu

al

Mo

nth

ly

Daily

Real Tim

e

Primary energy consumption Units: KWh or GWh Definition: Total energy consumption at a given facility, defined as the energy that has not been subjected to any conversion or transformation process. Energy Consumption should refer to building related uses, thus not including oil consumption for ground transportation, auxiliary power units, and/or other non building-related energy uses.

PEC refers to the total (consumed – exported energy) of all energy carriers.

Energy is affected by the primary conversion factors, (see references). Related Metrics: None Assessment Method: Energy data from electricity/gas/oil bills or metered consumption. Breakdown of PEC in different areas within a facility is also possible if necessary submetering is in place. References:

Standard EN 15603:2008

National Energy primary factors (if exist)

PEC x x x

CO2 emissions Scope 1

Units: tCO2 (Tonnes of Carbon Dioxide)/year

Definition: Scope 1 accounts for direct GHG emissions from sources that are

owned or controlled by the reporting company, mainly:

1. Production of electricity, heat, or steam.

(The following sources of emissions are not considered: Physical or chemical processing.

CO2S1 x x x


page 57 of 234

Transportation of materials, products, waste, and employees. Fugitive emissions)

Related Metrics: None

Assessment Method: Through application of emissions factors and activity factors. Emissions

will be calculated based on the purchased quantities of commercial fuels (such as natural gas

and heating oil) using published emissions factors. Cross-Sector calculations tools are

available from:

http://www.ghgprotocol.org/calculation-tools/all-tools

References:

World Resources Institute. 2004. “The Green House Gas Protocol: a corporate accounting and

reporting standard.” Available from WBCSD’s website: http://www.wbcsd.org

CO2 emissions Scope 2

Units: tCO2 (Tonnes of Carbon Dioxide)/year

Definition:

Scope 2 accounts for indirect emissions associated with the generation of

imported/purchased electricity, heat, or steam. Emissions attributable to the generation of

exported/sold electricity, heat, or steam should be reported separately under supporting

information and included in Scope 1. To increase data transparency, emissions data

associated with imported and exported electricity, heat, or steam should not be netted.


Assessment Method: Through application of emissions factors and activity factors. Emissions

will be calculated from metered electricity consumption using published emissions factors.

Cross-Sector calculations tools are available from:


References:

World Resources Institute. 2004. “The Green House Gas Protocol: a corporate accounting and

reporting standard.” Available from WBCSD’s website: http://www.wbcsd.org

CO2S2 x x x

Electricity consumption

Units: KWh (for monthly/daily data) or GWh (for annual data)

Definition: Electricity end-use consumption


Assessment Method: This value is available from billed or measured values.

References: None

EC x x x

Gas consumption

Units: GJ

Definition: Gas direct end use consumption


Assessment Method: This value is available from billed or measured values. Gas consumption

must be transformed using thermodynamic heat of combustion, commonly termed as High

Heating Value (HHV), and provided by the utility companies.

References: None

GC x x x


http://www.wbcsd.org/


http://www.wbcsd.org/


page 58 of 234

Normalisation Factors

per m2

Normalised primary energy consumption >>> PECM2 Units: KWh/m2 Definition: PEC per unit of gross surface area of conditioned buildings. Related Metrics: PEC

Normalised annual CO2 emissions Scope 1 >>> CO2S1M2 Units: tCO2/m2 (Tonnes of Carbon Dioxide/m2)

Definition: CO2 emissions scope 1 per unit of gross surface area of conditioned buildings. Related Metrics: CO2S1

Normalised annual CO2 emissions Scope 2 >>> CO2S2M2 Units: tCO2/m2 (Tonnes of Carbon Dioxide/m2)

Definition: CO2 emissions scope 2 per unit of gross surface area of conditioned buildings. Related Metrics: CO2S2

per m3

Normalised primary energy consumption >>> PECM3 Units: KWh/m3 Definition: PEC per unit of volume of conditioned buildings. Related Metrics: PEC

Normalised annual CO2 emissions Scope 1 >>> CO2S1M3

Units: tCO2/m3 (Tonnes of Carbon Dioxide/m3)

Definition: CO2 emissions scope 1 per unit of volume of conditioned buildings. Related Metrics: CO2S1

Normalised annual CO2 emissions Scope 2 >>> CO2S2M3

Units: tCO2/m3 (Tonnes of Carbon Dioxide/m3)

Definition: CO2 emissions scope 2 per unit of volume of conditioned buildings. Related Metrics: CO2S2

x x x

Table 4: TIER 2 - SERVICE KPIs

KPI CODE Timeframe

TIER 2 - SERVICE KPIs

An

nu

al

Mo

nth

ly

Daily

Real Tim

e

Delivered heating energy

Units: KWh or GWh

Definition: Heat energy should comprise the energy consumption of:

(1)Heat generator: boilers, heat pumps, furnaces, etc.;

(2)Water transport energy consumption for heating duty;

(3)Air transport energy consumption for heating duty;

Energy use of simultaneous heat and cool generation devices must be split proportionally

to the instantaneous cooling and heating loads

Fan energy use when no load on coils should be allocated the ventilation service;

Fan energy use when simultaneous heating and cooling loads occur requires partitioning

assumptions.

For 4 pipes systems, water transport energy consumption can be directly allocated for

heating and cooling;

For 2 pipes installations, time periods delivering hot and cold water must be metered;

DHE x x x


page 59 of 234

For heating pumps, split allocations can be made proportionally to the instantaneous

cooling and heating loads in the loop.

Related Metrics: No

Assessment Method:

1. Breakdown of HVAC equipment energy use according with service provided (heating,

cooling and ventilation/extraction);

2. Split of energy consumption (heating, cooling, ventilation) when necessary;

3. Aggregation of energy consumption for heating duty;

4. Choice of the reporting period (annual, monthly, daily);

References:

Perez Lombard et. al. 2012. Constructing HVAC energy efficiency indicators. Energy and

Buildings. n47. 2012. page 619–629 (Constructing HVAC performance indicators, 2011)

Delivered cooling energy

Units: KWh or GWh

Definition: Cooling energy comprise the energy consumption used by equipment for:

(1)Cool generation and heat rejection: chillers, direct expansion units, air condensers, cooling

towers, etc.

(2)Water transport energy consumption for cooling duty;

(3)Air transport energy consumption for cooling duty;

Energy use of simultaneous heat and cool generation devices must be split proportionally

to the instantaneous cooling and heating loads

Fan energy use when no load on coils should be allocated the ventilation service;

Fan energy use when simultaneous heating and cooling loads occur requires partitioning

assumptions.

For 4 pipes systems, water transport energy consumption can be directly allocated for

heating and cooling;

For 2 pipes installations, time periods delivering hot and cold water must be metered;

For heating pumps, split allocations can be made proportionally to the instantaneous

cooling and heating loads in the loop.

Related Metrics: No

Assessment Method:




3. Aggregation of energy consumption for cooling duty;


References: Perez Lombard et. al. 2012. Constructing HVAC energy efficiency indicators.

Energy and Buildings. n47. 2012. page 619–629 (Constructing HVAC performance indicators,

2011)

DCE x x x

Delivered ventilation / extraction energy

Units: KWh or GWh

Definition: Ventilation and extraction energy comprise the energy consumption used by

equipment for air transport only when ventilation and/or extraction modes are in operation.

Related Metrics: No

Assessment Method:




3. Aggregation of energy consumption for cooling duty;

DVE x x x


page 60 of 234


References: Perez Lombard et. al. 2012. Constructing HVAC energy efficiency indicators.

Energy and Buildings. n47. 2012. page 619–629 (Constructing HVAC performance indicators,

2011)

Normalisation Factors

per m2

Normalised annual delivered heating energy >>> DHEM2

Units: KWh/m2 Definition: Delivered heating energy per unit of gross surface area of conditioned buildings. Related Metrics: PEC

Normalised annual delivered cooling energy >>> DCEM2

Units: KWh/m2 Definition: PEC per unit of volume of conditioned buildings. Related Metrics: PEC

Normalised annual delivered ventilation/extraction energy >>> DVEM2


per m3

Normalised annual delivered heating energy >>> DHEM3


Normalised annual delivered cooling energy >>> DCEM3


Normalised annual delivered ventilation/extraction energy >>>DVEM3


x x x

Table 5: TIER 3 - System/Subsystem KPIs

KPI CODE Timeframe

TIER 3 - System/Subsystem KPIs

An

nu

al

Mo

nth

ly

Daily

Real Tim

e

Cogeneration Electrical Efficiency

Units: (%)

Definition: COGE refers to the ratio of electrical energy produced per unit of gas consumption.

The calculation formula is:

Related Metrics: No

Assessment Method:

Ecog-E (KWh) is the electrical energy produced and measured directly with electric meter

EGAS (kWh) is the energy provided to the CHP plan measured directly with gas/fuel meter

Reference: No

COGE x x x


page 61 of 234

Cogeneration Thermal Efficiency

Units: (%)

Definition: COGE refers to the ratio of heat produced per unit of gas consumption. The

calculation formula is:

Related Metrics: No

Assessment Method:

QCOG-H (kWh) is the heat energy produced measured directly with heat meter

EGAS (kWh) is the energy provided to engine through gas consumption, measured directly with

gas/fuel meter

Reference: No

COGT x x x

Solar Thermal Efficiency

Units: (%)

Definition: Solar thermal efficiency is calculated as the ratio of thermal energy produced by

the solar thermal plant to the demand for hot water. The calculation formula is:

Related Metrics: No

Assessment Method:

Qst (KWh) is the solar heat energy produced and measured directly with heat meter

DHW (KWh) is the hot water load measured directly with heat meter

Reference: No

STE x x

Photovoltaic System Efficiency

Units: (%)

Definition: PVE is the ratio of electricity produced and electricity demand. This metric

represents the adjustment of demand and production of electricity and how efficient the

demand profile and grid exchange is adjusted to meet PV output.


Related Metrics: No

Assessment Method:

Type 1: Systems which communicate with the inverters providing monitored data of all electrical values relating output from the PV facility and the inverter condition.

Epv = PV Electricity production (KW): direct metering with electrical meter;

Eload = Electricity load (KW): direct metering with electrical meter;

Electricity main supply: by difference as:

Electricity load – PV electricity production

Type 2: Systems without communication protocols to the inverters and provided with measured data of monitoring photovoltaic output.

Electricity main supply (KW) : direct metering with heat meter (E1);

Epv = PV electricity production (KW) : direct metering with electrical meter (E2);

PVE x


page 62 of 234

Eload = Electricity load: by difference as:

Electricity main supply + PV electricity production

Reference: No

AHU performance

Units: W/cfm [W/l-s-1]

Definition: AHU airflow efficiency is defined as the overall airflow efficiency of the make-up air

unit. Can be calculated as the total fan power required per unit of airflow. It provides an

overall measure of how efficiently air is moved through the AHU. The calculation formula is:

Where:

Related Metrics:

AHUpower (KWh) = Rated power of AHU (fans, dampers, and other electrical equipment).

Measured directly on site with electric heaters.

Airflow = Airflow passing through the AHU, can be calculated based on fan power and

manufacturer specifications.

References: LBNL. 2012. “Self Benchmarking for High-Tech Buildings”. [Online] available from

http://hightech.lbl.gov/benchmarking-guides/

AHUAE x

Chilled water loop temperature diferential

Units: degree centigrade (°C)

Definition: This metric is defined as the difference between the chilled water return and

supply temperatures. A reference value for the optimal temperature differential should be

stablished first based on design parameters. A low value of this indicator indicates energy

conservation measures as reducing chilled water flow, and/or increasing chilled water supply

temperature.


Where:

Tr = Chilled water return temperature;

Ts = Chilled water supply temperature.


Assesment Method: Temperatures can be measured directly from temperature sensors on-

site.

References: LBNL. 2012. “Self Benchmarking for High-Tech Buildings”. [Online] available from


CWLT

x

Hot Water loop efficiency

Units: degree centigrade (°C)

Definition: This metric is defined as the difference between the hot water suply and return

temperatures. A reference value for the optimal temperature differential should be stablished

first based on design parameters. A low value of this indicator indicates energy potential

energy conservation measures as decreasing hot water supply temperature.


Where:

Ts = Hot water supply temperature;

Tr = Hot water return temperature.

HWLT




page 63 of 234


Assesment Method: Temperatures can be measured directly from temperature sensors on-

site.

References: Pacific Northwest National Laboratory. 2012. Building Re-Tuning Training Guide:

Central Utility Plant Heating Control. [Online] available from:

http://www.pnl.gov/buildingretuning/documents/pnnl_sa_89222.pdf

Table 6: TIER 4 - Component KPIs

KPI CODE Timeframe

TIER 4 - Component KPIs

An

nu

al

Mo

nth

ly

Daily

Real Tim

e

Filters pressures drop

Units: (% of Maximum admissible)

Definition: Measure of the current pressure drop on a filtering device with relationship to

minimum and maximum admissible pressure drop for the specific filter.

Related Metrics: No

Assessment Method:

Current is taken from pressure sensors already installed in AHUs

ΔPmin and ΔPmax should be retrieved from the manufacturer specifications

References: No

FPD

Heat Recovery efficiency

Units: (%)

Definition: Temperature Transfer Efficiency The temperature transfer efficiency of an heat

recovery unit can be expressed as:

Related Metrics:

Assessment method:

t1 = Temperature outside air before the heat exchanger (°C), measured directly with a

meteorological station or temperature sensors.

t2 = Temperature outside air after the heat exchanger (°C), measured directly with

temperature sensors.

t3 = Temperature inside air before the heat exchanger (°C), measured directly with

temperature sensors.

References: None

HRE x x x x

Heating Coil Efficiency

Units: (%) Electrical energy to Thermal energy (KWh) for a period.

Definition: Ratio of energy consumption to thermal energy delivered by the cooling coil, as

shown by the formula:

Where:

HCE x x x

http://www.pnl.gov/buildingretuning/documents/pnnl_sa_89222.pdf


page 64 of 234

Ew = Energy consumtion of circulating pumps. Calculation should follow, assumptions and

methods of Section 5.4.1 of Eurovent 6/8.

Ea = The energy consumption of electric energy of the fan.

Qt = Calculation should follow assumptions and methods of Section 5.4.3 of Eurovent 6/8.

Related Metrics: No

References: : EUROVENT. 2005. Eurovent 6/8. Recommendations for calculations of energy

consumption for air handling units. Brussels : Eurovent Publications, 2005. (EUROVENT , 2005)

Cooling Coil Efficiency

Units: (%) Electrical energy to Thermal energy (KWh) for a period.

Definition: Ratio of energy consumption to thermal energy delivered by the cooling coil, as

shown by the formula:

Where:

Ew = Energy consumtion of circulating pumps. Calculation should follow, assumptions and

methods of Section 5.5.1 of Eurovent 6/8.

Ea = The energy consumption of electric energy of the fan.

Qt = Calculation should follow, assumptions and methods of Section 5.5.3 of Eurovent 6/8.

Related Metrics: No

References: : EUROVENT. 2005. Eurovent 6/8. Recommendations for calculations of energy


CCE x x x

Humidifiers efficiency

Units: (KWh/cfm)

Definition: Energy consumed by an humidifier in order to produce steam.

Related Metrics: Energy Consumed by the Humidifier (KWh) and Water consumption (volume)

need to be related with time values.

HE can also be measured for the cooling and heating sessions.

HE can also be assessed as a percentage of the nominal HE (%)

Assessment Method: Automatically constructed using CASCADE solution software.

References: EUROVENT. 2005. Eurovent 6/8. Recommendations for calculations of energy


HE x

Fans efficiency

Units: η

Definition: Total efficiency is measured by comparing the electric power consumption to the

mechanical power of the fan.

Related Metrics: According with (EU) No 327/2011

Assessment Method: Automatically constructed using CASCADE solution software.

References:

EC (2011). Commission Regulation (EU) No 327/2011 of 30 March 2011 implementing Directive 2009/125/EC of the European Parliament and of the Council with regard to Ecodesign requirements for fans driven by motors with an electric input power between 125 W and 500 kW. (EC, 2011)

EN 13779:2007. Ventilation for non-residential buildings. Performance requirements for ventilation and room-conditioning systems. European Committee for Standardization (CEN), 2007. (EC, 2007)

ASHRAE 90.1 – 2010: Fan Power Limitation (ASHRAE, 2010)

FE x

Air control device (VAV) efficiency VAVE x


page 65 of 234

Units: ( KW / m3 )

Definition: Power usage of ECM or PSC Motors versus flow rate. This depends on the static

pressure. Usually it is useful to compare with nominal performance curves from

manufacturer.

Related Metrics: No

Assessment Method:

Power usage of VAV control and flow rates must be estimated from operation times (retrieve

from the BMS control signals) and power specifications from manufacturer.

References: No

Table 7: Thermal Comfort and Indoor Air Quality (IAQ) KPIs

KPI CODE Timeframe

Thermal Comfort

Definition: Thermal Comfort is assessed using static methods of Predicted Mean Vote

(PMV) and Predicted Percentage of Dissatisfaction (PPD). Benchmark is set to 10% PPD

>>> HPPD10 using cumulative hours where conditions are not met as a measure of

undesirable conditions

HPPD10 should be broken down in zones within an airport >>> HPPD10zone n

Can also be measured as a yearly total cumulative or seasonally:

Hours not met >10% PPD yearly cumulative >>> HPPD10zone y

Hours not met >10% PPD cooling session >>> HPPD10zone c

Hours not met >10% PPD heating session >>> HPPD10zone h

Also a detected fault can be correlated with undesirable conditions when possible:

Hours not met >10% PPD fault >>> HPPD10zone f

Additional KPIs can be constructed by assigning occupancy data (EOCC)

Units: (hours)

Related metrics:

Environmental Variables for PMV: Air Temperature (Ta), Mean Radiant Temperature (Tr), Relative air velocity (v), Water vapour pressure in ambient air (Pa), can be measured on-site or estimated using a software simulation;

Physiological Variables: Skin Temperature (Tsk), Core or Internal Temperature (Tcr), Sweat Rate, Skin Wettedness (w), Thermal Conductance (K) between the core and skin, must be set on a case by case basis.

Assessment methods: Described in Perfection D1.5 Annex B: Assessment methods of

Health & Comfort Key Indoor Performance Indicators (KIPIs). (Perfection Consortium,

2010)

References:

Finnish Society of Indoor Quality and Climate (FISIAQ) 2008, Classification of Indoor Environment 2008, Target Values, Design Guidance, and Product Requirements, Finnish Society of Indoor Quality and Climate (FISIAQ), Helsinki, Finland. (FSIAQC, 2008)

ISO 7730-2005, 2005, Ergonomics of the thermal environment Analytical determination and interpretation of thermal comfort using calculation of the PMV and PPD indices and local thermal comfort criteria, International Standards Organization, Geneva. (ISO, 2005)

ASHRAE 55-2010R, 2010, Thermal Environmental Conditions for Human Occupancy, American Society of Heating, Refrigerating and Air-Conditioning Engineers, Atlanta, GA. (ASHRAE, 2010)

BS EN 15251-2007 2007, Indoor environmental input parameters for design and assessment of energy performance of buildings addressing indoor air quality,

HPPD10zone,n x x x


page 66 of 234

thermal environment, lighting and acoustics. (ISO, 2007)

Effective Ventilation

Units: (ppm CO2) / ( Estimated ppm CO2 )

Definition: The effective ventilation of a space is characterized by the carbon dioxide

concentration in a room. Carbon dioxide is considered an appropriate air quality

measurement also because of its potential to predict the amount of outdoor air

supplied to a space. Benchmarks should be established previously meeting regulations

or using the frameworks provided (see references).

EFFV must be broken down in specific zones within an airport >>> EFFVzone n

EFFV can be yearly cumulative (hourly values * EFFV) >>> EFFVzone y

EFFV can be evaluated for the cooling session >>> EFFVzone c

EFFV can be evaluated for the heating session >>> EFFVzone h

Ineffective ventilation occurrences can be measured by slicing time when estimated

conditions are not met so >>> EFFVnotmet = EFFV>1

Related Metrics: Need to calculate estimated occupancy (EOCC)

Assessment Method: Described in Perfection D1.5 Annex B: Assessment methods of

Health & Comfort Key Indoor Performance Indicators (KIPIs)

References:

ASHRAE 55-2010R, 2010, Thermal Environmental Conditions for Human Occupancy, American Society of Heating, Refrigerating and Air-Conditioning Engineers, Atlanta, GA. (ASHRAE, 2010)

Schuh, C.K., 2000, Performance Indicators for Indoor Air Quality, Ph.D. thesis, University of Calgary (Schuh , 2000)

Finnish Society of Indoor Quality and Climate (FISIAQ) 2008, Classification of Indoor Environment 2008, Target Values, Design Guidance, and Product Requirements, Finnish Society of Indoor Quality and Climate (FISIAQ), Helsinki, Finland. (FSIAQC, 2008)

EFFVzone,n x x x

Table 8: Operations and Maintenance KPIs

KPI CODE Timeframe

Operations and Maintenance KPIs

An

nu

al

Mo

nth

ly

Daily

Real Tim

e

Fault frequency

Units: (times / year)

Definition:

Number of occurrence of faults in a specific system/component. FF can refer to a component

(TIER4) or a System (TIER3). Additional metrics can be constructed as ratios between FF and

ENF (Expected number of failures) during a considered period (one year). Benchmarking and

comparison between different zones using equivalent systems can be of special interest.

Temporal benchmarking is also possible to assess effectiveness of Energy Management and

O&M corrective actions and policies.

Related Metrics:

ENF can be estimated using ASHRAE tables (see References).

Assessment Methods:

Faults detected can be counted on using the CASCADE solution.

References:

The 2011 ASHRAE Handbook—HVAC Applications. Chapter 38. (ASHRAE, 2010)

FFsystem x


page 67 of 234

Fault duration

Units: (hours)

Definition: Fault duration until solution and reset to satisfactory conditions, measured in

hours is a measure of O&M effectiveness (personnel, contract types, coordination,

management styles, etc.).

FDUS can refer to a component (TIER4) or a System (TIER3). FDUS can be used to calculate

Average Response Time (ART). Benchmarking between different zones using similar

equipment, or between different periods (years) can be also considered.

Related Metrics: No

Assessment method:

CASCADE solution will provide all time related data. Automatic register of faults start and

finish are the basic measurements to consider.

References: No

FDUS x

Maintenance Costs

Units: (%ERV or ARV) where ERV stands for “Estimated Replacement Value” or ARV as “Asset

Replacement Value”

Definition: Annual cost of maintenance as a percentage of the total replacement value of an

asset. ARV is a non standardised value and highly variable. This metric is closely related with

internal cost policies and should be calculated in agreement with O&M cost model. Data

bases can be used to calculate estimated life duration of HVAC equipment as baseline for

financial calculations. TAMC can refer to a component (TIER4) or a System (TIER3).

Related Metrics: No

Assessment method: O&M cost performance should be calculated in accordance to

organisational policies.

References:

ASHRAE Owning and Operating Costs database. Available from:

http://xp20.ashrae.org/publicdatabase/

TAMC x

Table 9: Airport Specific KPIs

KPI CODE Timeframe

Airport Specific KPIs

An

nu

al

Mo

nth

ly

Daily

Real Tim

e

Energy consumption per PAX

Units: KWh/PAX

Definition: Ration of primary energy consumption to annual number of passengers. Number

of passengers is defined as “PAX = enplaned passengers plus deplaned passengers deplaned

plus direct-transit passengers”

Related Metrics: PEC >>> ECPAX = PEC / PAX

Assessment Method: Same as PEC.

References: None

ECPAX x x x

Energy consumption per Traffic Movement

Units: KWh/PAX

ECFL x x x

http://xp20.ashrae.org/publicdatabase/


page 68 of 234

Definition: Ration of primary energy consumption to annual number of flights. Number of

flights is defined as “Traffic Movement = landings and take-offs of aircraft”

Related Metrics: PEC >>> AECFL = PEC / Traffic Movements

Assessment Method: Same as PEC.

References: None

3.5 KPI SELECTION METHOD

Establishing a performance based methodology involves a significant effort at all levels within an

organisation. CASCADE’s philosophy is to make use of existing resources and data within an

airport environment without committing unnecessary funds. Moreover, the adoption of

standardised quality standard ISO 500014.5 - Section 4.4.5 (ISO, 2011) make it mandatory that

any organisation shall proceed thoroughly with a documented process addressing:

Identification of KPIs

Appropriateness of Election of KPIs

Methodology for determining and updating KPIs

Energy Baseline

This selection process will be covered in the future with the release of standards ISO 17588,

17570 and 17580(1) address selecting, establishing and maintaining energy performance

indicators (EnPI), their corresponding baselines and measurement & verification. This standards

will include the steps in selecting EnPIs, developing baselines, characteristics of significant

energy uses and appropriate reasons to change a baseline.

3.5.1 Selection Method based in cost effectiveness

New performance metrics may need extra investment in sensors and/or hardware. A procedure

to select the most valuable set of indicators should be established early on in the project. Thus,

a decision making process must account for cost-benefit analysis in order to optimize capital

investment and reinforce probabilities of project success guaranteeing that:

Careful selection of KPIs is done as up-front process during the planning phase;

Investment in new equipment, sensor or new hardware is based in feasibility analysis;

KPIs election process involve stakeholders, as they shape the way the enterprise

strategic vision aligns activities vertically in an organisation;

Avoid the commitment of unnecessary and costly investments (Due Diligence).


page 69 of 234

Fig 7. KPI Cost-Benefit Analysis

Fig 7 shows an overview of the decision making process proposed. First, from all KPIs

considered in the CASCADE KPIs repository a cost analysis of the necessary additional

measurements, hardware and sensors is made. More KPIs are added depending on

stakeholders requirements. Cost calculations are based in previous gathered information

regarding systems in place (e.g. pipe sizes) but also market value of sensors, meters, hardware,

network equipment and installation cost and procedures. Existing cost databases, vendors’

quotations are useful sources of information. Local conditions must be evaluated. Secondly an

estimation on energy savings is performed following the established procedure in the Energy

Audit process.

After cost and savings are calculated, a Cost-Benefit Analysis (CBA) is carried out using

common techniques of Internal Rate of Return (IRR), Payback Period, or Discounted Cash Flow

(the latter being the recommended technique). CBA inputs should carefully consider factors as

fiscal incentives, estimated benefits from improved O&M processes, or unstable energy markets

that can impact dramatically on economical valuations. Moreover, social and environmental

benefits can also be considered and taken into account as inputs. This issues will be analysed

with more detail in Work Package 7 (Replication Plan, Business Plan).

Finally, KPIs impact is analysed leading to the selection of the most appropriate combination

which proves also the most cost-effective. Decision making at this level should involve the


page 70 of 234

relevant stakeholders, as non-monetary impacts, or strategic decision may play an important

role in the selection process.


page 71 of 234

4 CASCADE Partner Solution Descriptions

This section gives an overview of all the partners solution that will be integrated in the final

CASCADE solution described in the next section (5).The different solutions provided by the

partners in the consortium are listed in Table 10.

Table 10 CASCADE partners solutions to be integrated

Provider Tool Key functionalities

Enerit tool

Support Energy Management Systems

according to ISO 50001

DataStorage tool

Data storage and handling, advanced

visualisation to support manual FDD,

automated FDD models

Diagnostic tool Automated FDD models

Remus data logger Advanced data logger

Ontology Airport specific ontology

Each technology provider partner was given a template to describe his own solution (in relation

to the use within the CASCADE project) according to a predefined list of aspects which included

a brief description, a detailed description and application example as follow:

Brief description

o Scope

o Who does use it?

o Who does implement it?

o Technologies involved

o Contribution to CASCADE solution

Detailed description

o INPUT – How is this information supplied (format, frequency...)?

o PROCESSES – How this solution processes and produces

Information/Outputs? .What are the techniques the solution uses?. What are the

underlying paradigms, theories and processes the solution operates?

o OUTPUT – How this information will be delivered (format, frequency...)?


page 72 of 234

Application example

The structure required to the partner solution description aimed at defining in the best way input

and output of each piece of technology to be integrated (Fig. 12). This in turn allowed a more

consistent integration approach described in section 5, which follow the philosophy showed in

Fig. 13.

Fig. 12: Partner solution overview

Fig. 13: CACADE Integration requirements


page 73 of 234

4.1 Enerit – Enerit tool

4.1.1 Brief description

Scope

The ISO 50001 energy management system (EnMS) standard enables organizations to

establish the systems and processes necessary to improve energy performance, including

energy efficiency, use, and consumption. Implementation of this standard is intended to lead to

reductions in greenhouse gas emissions and energy cost through systematic management of

energy. ISO 50001 is applicable to all types and sizes of organizations, irrespective of

geographical, cultural or social conditions. Successful implementation depends on commitment

from all levels of the organization, especially from top management. (Ref: ISO 50001) [12]

The requirements of the ISO 50001 standard requires that an organization develops and

implements an energy policy, establishes objectives, targets, and action plans which take into

account legal requirements and information related to significant energy use. This International

Standard is based on the ‘Plan Do Check Act’ (PDCA) continual improvement framework and

incorporates energy management into everyday organizational practices. Fig. 14 describes the

ISO 50001 PDCA Energy management system model. In the context of energy management,

the PDCA approach can be outlined as follows:

Plan: conduct the energy review and establish the baseline, energy performance indicators (EnPIs), objectives, targets and action plans necessary to deliver results that will improve energy performance in accordance with the organization's energy policy;

Do: implement the energy management action plans;

Check: monitor and measure processes and the key characteristics of operations that determine energy performance against the energy policy and objectives, and report the results;

Act: take actions to continually improve energy performance and the EnMS.

[12

]http://www.iso.org/iso/energy_management_system_standard, ISO 50001:2011 – “Energy

management systems – Requirements with guidance for use”

http://www.iso.org/iso/energy_management_system_standard


page 74 of 234

Fig. 14: ISO 50001 Energy management system model

“Management” vs. “Technical”

Fig. 15: EnMS Relations - Organisational-Technical-People

Fig. 15 illustrates three pillars of a successful EnMS, namely: technical, organisational and

people.

The “Technical” pillar deals with reducing energy consumption by understanding how energy is

used and how to control it, e.g. replacing old equipment with newer more energy efficient ones


page 75 of 234

or to replace fluorescent lighting with LED lighting. The “Technical” pillar is generally more

interesting to an energy manager!

The “Organisational” pillar deals with management commitment (e.g. top management providing

necessary resources for the EnMS to be successful) or dealing with energy planning in a

systematic manner (e.g. establishing an action plan based on relevant objectives and targets,

realised during an energy review).

The “People” pillar refers to nurturing and promoting an energy efficient culture by

communicating and promoting good energy saving practices effectively with all staff from top

management downwards.

It is evident from Fig. 15 that the balance for a successful EnMS involves both “Technical” and

“Management” (“Organisational” and “People”) aspects. In relation to the PDCA continual

improvement system model, sections of the ISO 50001 standard are also associated with

“Technical” and “Management” aspects. Fig. 16 further illustrates this concept. For example, in

the planning phase, the “Management” aspects include assessing and planning policy/goals and

targets. The “Technical” aspects of planning include carrying out an energy review, establishing

an energy baseline and defining relevant Energy Performance Indicators (EnPIs).

Gaining Commitment and defining management responsibility are non-technical concepts but

they are crucial for the success of an EnMS. Commitment is based on top management

responsibility and the creation of a strong energy policy.

Fig. 16: PDCA - Management vs. Technical comparison (numbers refer to the standard clauses) [13

]

Enerit ISO 50001 Software

[13

]http://www.sgs.com/~/media/Global/Documents/White%20Papers/sgs-energy-management-

whitepaper-en-11.ashx, Understanding the requirements of the energy management system certification,

SGS, July 2011.

http://www.sgs.com/~/media/Global/Documents/White%20Papers/sgs-energy-management-whitepaper-en-11.ashx

http://www.sgs.com/~/media/Global/Documents/White%20Papers/sgs-energy-management-whitepaper-en-11.ashx


page 76 of 234

Enerit ISO 50001 software is a stand-alone software for managing all aspects of an energy

management system (EnMS) based on ISO 50001. Enerit software is a management system

software and is currently the only software dedicated to managing all aspects of the ISO 50001

standard.

It is used by different sectors including, large industry, commercial buildings (e.g. banks),

Hospitals, Supermarkets, Hotels and schools. By implementing an EnMS real energy savings

can be achieved. Utilising the Enerit ISO 50001 software supports the implementation and

makes the EnMS more efficient, effective and transparent.

Enerit software is not a monitoring & targeting system (M&T) or a Building Management System

(BMS/BEMS). When these types of systems are integrated with Enerit ISO 50001 software an

organisation is presented with a holistic and comprehensive EnMS. The CASCADE project will

utilise the Enerit ISO 50001 software. The most significant aspect of the Enerit software that will

make the CASCADE project a success is the action management and tracking of actions

through to completion. The CASCADE Energy Action System (EAS) will be designed to aid

airport management in recording, assigning and prioritising actions related to:

Fault detection diagnosis (FDD),

Grouped BMS/SCADA alarms,

manually suggested energy saving actions, and

Provide a pre-populated checklist of energy savings actions related to HVAC systems.

These actions will be managed within the Enerit ISO 50001 software, from creation right through

to closure by the energy manager.

Enerit ISO 50001 software was designed to match the core principles of the ISO 50001 standard.

Fig. 17 illustrates the Enerit software modules and maps them to the previously discussed PDCA

diagram (Fig. 14). The software module titles are: Commitment, Planning, Implementation and

Checking. Under these titles there are various sub-titles referring to different functions and

document management areas. For example, the Energy Policy for an organisation is created

and stored in the Commitment tab of the Enerit ISO 50001 Software. The software functions

under Planning, allow a user to identify/review Significant Energy Uses, set/monitor objectives

and targets, identify/review improvement opportunities, and review/manage the Action Plan.

Under Checking a user is able to enter/review past and present energy use, create a Meeting

for management review or an Audit can be created to schedule an Internal Audit of the EnMS.


page 77 of 234

Fig. 17: Enerit ISO 50001 Software Mapping.

In summary, the Enerit tool is a highly focussed product that helps organisations to

systematically manage energy. It automates all aspects of ISO 50001 by providing functions for:

Registering of Improvement Opportunities

Energy Saving Suggestions

Energy Management Planning and Action

Energy Auditing

Reporting of Energy Action Status

Corporate Energy Portal

Reporting of Energy Performance Indicators (EnPIs)

Energy-related Documents – bills, drawings, audits, etc.

System Audits & Nonconformities

Management Review / Energy Management Meetings

Who does use it?

Enerit ISO 50001 software is used by:

Medium and large energy users who are adopting a systematic approach to energy

management and with the necessary skills in-house – particularly industrial companies or


page 78 of 234

owners of stocks of buildings. Typically those customers have energy costs in excess of

€1 million or $1 million a year.

Consultants introducing ISO 50001 energy management to their customers or who act as

outsourced (on-site and off-site) energy managers for customers who simply wish to

save energy.

Energy service companies (ESCos) which provide an outsourced energy management

service for their customers.

Who does implement it?

Industrial sector applications

Target customers in a wide range of industrial sectors, include:

Medical devices

Primary Metal , Fabricated Metal, Mining

Food and Beverages Manufacturing

Automotive

Chemicals and Allied Products Manufacturing

Rubber, Plastic and Leather Products Manufacturing

Paper Products Manufacturing, Publishing and Printing, Paper and Pulp

ISO 50001 energy management consulting

Technology Centre of Large Energy Users

Buildings sector applications

Enerit software is also used in energy management programmes for organisations with stocks of

buildings, e.g.:

Offices (banks)

Educational (universities and large schools)

Retail (Supermarket chains)

Airport terminals

Hotels

Technologies involved

Enerit software is a web based Cloud Service (using the Software as a Service (SaaS) model.

Some of the current underlying technologies are as follows:

Software Platform - Microsoft Windows Server 2003

Database Platform - IBM Lotus Domino 8.5.2

Web Server - IBM Lotus Domino 8.5.2 Web Server

Programming languages/Libraries/Methodologies:

o Lotus Notes Formula language

o Lotusscript

o Javascript

o HTML


page 79 of 234

o XML

o CSS

o Ajax

o JQuery

o C/C++ API

o Eclipse Framework

Automated Emails via Lotus Domino Server 8.5.2 SMTP/Mime Engine

Contribution to CASCADE solution

In the CASCADE project, fault detection and other feedback from control and monitoring

systems will pass information to the “Energy Management Planning and Action” module of the

Enerit ISO 50001 software. This will enable a problem detection, or diagnosis, to automatically

trigger an action for a person (ACTIONS with assigned RESPONSIBILITY). These actions would

then be communicated to the relevant person through "content-rich" action reports, dashboards,

and visualisation tools to ensure early correction of the reported problems.

Enerit will integrate FDD, the ISO 50001 standard and energy management software. To do this,

Enerit will adapt its energy management software suite to FDD and the airport environment as

an open space and then test and analyse the practical implementations of the developed

methodologies in the SEA and ADR airports.

Enerit’s software in the CASCADE solution will encourage organisations to think about and

adopt clear roles and responsibilities as related to energy management (e.g. the appointment of

energy managers, key players, energy champions, and committees). This will help planning,

communication, management, and provide a platform to review energy related documents. It

also provides a tool to assist audits, explain problems, or to take corrective measures when

targets or energy actions are not met.


page 80 of 234

4.1.2 Detailed description

4.1.2.1 INPUT – How is this information supplied (format, frequency...)?

Information is manually inputted into the system by the end-user.

There are a number of areas where information is inputted to the system, namely:

Significant Energy Uses

Improvement Opportunities

Energy Use

Audits

Nonconformities

Meetings

General energy documents

Fig. 18 describes the three main stages where data input is necessary:

1. The Setup,

2. Identifying SEUs, and

3. Every-Day use.


page 81 of 234

Fig. 18: Main stages where data input is necessary in Enerit ISO 50001 software.

The data for the Instance setup, administration configuration and SEU Identification is

inputted by the energy manager in the organisation or another competent person with

knowledge of the organisation’s energy use and management. The SEU creation form is

detailed in Section 4.1.2.1.1. The improvement opportunities can be created by members of

staff at any level in the organisation. The improvement opportunity creation form is detailed in

Section 4.1.2.1.2. The energy consumption data can be created by a competent user or can

be imported into the software automatically, once the building management system can export

to an FTP server. The Commitment, Planning, Implementation, Checking documents plus

other document types, such as: Audits, Nonconformities, Meetings and should be created by

the energy manager in the organisation or another competent person with knowledge of the

organisations energy use and management.


page 82 of 234

4.1.2.1.1 SEU data entry

Fig. 19: Significant Energy Use creation form.


page 83 of 234

Significant Energy Use Form (Fig. 19)

Title: Enter the title or description of the SEU. This field is mandatory.

Location/Sub-Location: Select from the list of pre-defined locations. The list of locations

is configured in the Administration section. This field is mandatory.

Owner: Click on the icon and select the person responsible for this SEU.

Category: Select a category for this SEU. This allows SEUs to be grouped for easy

searching later using the Category views. This list is configured in the Administration

section.

Sub-Category: Select from list (if available). The sub-categories are based on the

category selected above.

Details: Enter any additional information about the SEU.

Energy Drivers: Enter the reasons why it is a Significant Energy Use.

Annual Usage

Electricity (& Thermal): If you know the annual electrical energy usage and costs you

can enter it directly in the MWh and € box. The units and currency are configured in the

Administration section. For thermal, enter the name of the relevant energy sources.

Water: You can also identify significant water using equipment or processes and enter

the details.

Details: Enter any information and assumptions that you have used in determining the

Annual Usage data entered above.

Objectives & Targets

Objective: Enter a statement describing the targets that you have set in line with your

Energy Policy e.g. “Reduce consumption by 5% in 2012”

Target Electrical (& Target Thermal): Enter the actual quantity of energy savings that

you expect to achieve from this SEU.

Improvement Opportunities

New Improvement Opportunity: Click on this button to create an improvement

opportunity related to this SEU. The details of related improvement opportunities and

actions are summarised in the table. You can click on the title to open the improvement

opportunity.

4.1.2.1.2 Improvement Opportunity Data Entry


page 84 of 234

Fig. 20: Improvement Opportunity creation form.

Energy Saving Opportunity Form (Fig. 67)

Title: Enter a short description of the energy saving idea. This field is mandatory.

Location/Sub-Location: Select from the list of pre-defined locations. The list of locations

is configured in the Administration section. This field is mandatory.

Category: Select a category for this opportunity. This list is configured in the

Administration section.



Significant Energy Use: Select the related significant energy use for the list. This field

will be automatically populated if improvement opportunity is created from an SEU or

other source. You do not have to apply the opportunity to an SEU, but it is advisable.


page 85 of 234

Details: Enter any additional information about the energy saving idea.

Estimated Savings & Payback

Electricity (& Thermal) – “MWh”: Enter the estimated annual energy savings in the

“MWh” box (the energy units and currency are configurable in the Administration section.)

Electricity (& Thermal) – “€” & “kgCO2”: The estimated annual cost and emissions

savings are automatically calculated using the energy savings entered in the “MWh” box

(the unit cost and CO2 emission factor are configured in the Administration section – see

slides on Administration section later.)

Annual Co-Benefits: Enter, non-energy, cost savings achievable by carrying out the

action. Comments on co-benefits can also be recorded.

Capital Costs: Enter the costs to implement these savings.

Estimated Payback: The payback is automatically calculated based on a simple ROI

using the annual costs savings and the capital costs.

Complexity: This allows you to enter some information on the level of difficulty in

implementing this energy saving opportunity. Comments on Complexity can also be

recorded.

Submit (button): Click on this button when you have completed entering the details for

this improvement opportunity. The Energy Manager for the location selected will be

automatically notified by email.


page 86 of 234

4.1.2.2 PROCESSES

The Energy planning process is the key step in establishing an EnMS. Fig. 21 describes the

Energy Planning process and describes how the Enerit software maps to this process. Based on

the Planning inputs entered into the software such as consumption data and documents

relating to relevant variables effecting energy use the energy review can be carried out. The

Software supports the Energy Review process by allowing for entry of Significant Energy

Users and Improvement Opportunities. From there, Action Plans and Objectives & Targets

are automatically created based on the information entered during the creation of Improvement

Opportunities and Significant Energy Users.

Fig. 21: Energy Planning Process Mapped to Enerit ISO 50001 software.

In the CASCADE project, it will be possible to identify some faults that can be solved by software

in control systems. However, other problems will still need human intervention. It may be said:

“automatic control systems manage the machines”

“Enerit ISO 50001 software’s management system manages the people (through action

assignment)”

Systematic action management means that actions get completed in an organised way, no

action is left undone and corrective actions are also triggered, when necessary. The

Improvement Opportunity-Energy Saving Action workflow (Fig. 22) describes how an


page 87 of 234

improvement opportunity is captured and the actions carried out concisely and with minimum

time lag.

Fig. 22: Improvement Opportunity-Energy Saving Action Workflow.


page 88 of 234

Workflow detail:

An improvement opportunity can be created by relevant members of staff at level in the

organisation. The creator has the ability to save a DRAFT improvement opportunity form

and if perhaps they need to return to it at alter stage to input more detail.

Once an improvement opportunity has been submitted FOR REVIEW a notification email

is sent to the energy manager for the location.

Once the energy manager has reviewed the improvement opportunity, he can then

include it in the action plan (PLANNED), CLOSE it or place it in ON HOLD.

If the action is to be assigned to a relevant person, the energy manager must add detail

on; the validation method; the start date; end date and possible further notes for the

assignee.

Once ASSIGNED, the action is then included in the action plan the assignee receives a

notification email with a link to the action. The assignee has the ability to reject the action,

but must provide a reason for rejection to the energy manager.

The assignee also has the ability to request more time to complete the task, and this can

be reviewed by the energy manager.

If the assignee accepts the task, after completing it, they then detail what action they

carried out.

VALIDATION is then detailed by the assignee according to the instructions given by the

energy manager when the energy manager assigned the task. This may be after a period

of time or after a measurement comparison. The actual savings are detailed at this stage

also.

The action is then AWAITING CLOSURE by the energy manager then reviews the action

details and validation process undertaken.

If the energy manager is in agreement with the actions undertaken by the assignee, and

requires no further clarification, the energy manger CLOSES the action.


page 89 of 234

4.1.2.3 OUTPUT – How this information will be delivered (format, frequency...)?

The information is delivered through an online website Portal. The format is simple text based

forms, which include attachments. Results are also present in charts format. The frequency is

real-time i.e. once information is entered into the system then it can be seen through the Portal.

The software provides a clear and systematic view an organisations energy management

activities and the progress they are making.

The various portal views include:

My Tasks Commitment

• Energy Policy (Documents or links to other sources) • Energy Manual (Documents or links to other sources) • Roles and Responsibilities (Documents or links to other sources)

Planning (Views of inputted data)

• Significant Energy Uses • Improvement Opportunities • Action Plans • Objectives and targets

Implementation

• Procedures & Instructions (Documents or links to other sources) • Case Studies (Documents or links to other sources)

Checking

• Consumption data (Inputted data) • Standard • Audits (Inputted data) • Meetings (Inputted data) Corrective Actions (Inputted data) • Reports (Documents or links to other sources & Charts of inputted data)


page 90 of 234

4.1.2.3.1 My Tasks View:

My Tasks view lists all tasks that apply to the specific user of the system. Therefore an energy

manager would have tasks, such as, reviewing improvement opportunities, assigning actions,

reviewing and assigning actions related to Nonconformities, Fig. 23. An energy manager view

will generally include more tasks to complete than a responder licence user.


page 91 of 234

Fig. 23: 'My Tasks' view in Enerit ISO 50001 software.


page 92 of 234

4.1.2.3.2 Energy Planning Views:

The SEUs added to the system are located in the Significant Energy Uses section of the

Energy Planning module (Fig. 24). Similarly, the Improvement Opportunities and Action

Plans are documented depending on where they are in the workflow as illustrated in Fig. 25 and

Fig. 26, respectively. The Objectives & Targets for the SEUs and the improvement

opportunities associated with a particular SEU are described and presented in Fig. 27.

Fig. 24: ‘Significant Energy Use’ view in Enerit ISO 50001 software.


page 93 of 234

Fig. 25: 'Improvement Opportunities' view in Enerit ISO 50001 software.

The Action Plans highlights overdue actions with a red indicator. Closed actions are indicated

with a blue icon and actions yet to be assigned with a ‘?’ symbol.


page 94 of 234

Fig. 26: 'Action Plans' view in Enerit ISO 50001 software.


page 95 of 234

Fig. 27: 'Objectives & Targets' view in Enerit ISO 50001 software.


page 96 of 234

4.1.2.3.3 Consumption Data

Consumption data can be viewed in the software, as illustrated in Fig. 28.

Fig. 28: 'Consumption Data' view in Enerit ISO 50001 software.

4.1.2.3.4 Monitoring - Reports:

In parallel to the information recorded in the system, the reporting section of the software can

displays the information on SEUs, Improvement Opportunities, and importantly the people

associated with the tasks. The reports can be configured and categorised as the user requires.

Some reports are based on energy, which indicate the energy savings. Others are action

reports which indicate the management success and the action statuses.

Energy Reports

In the Energy Reports currently as the energy use data is inputted to the system the charts

display the information automatically update and display the new energy use data can be

displayed graphically. A typical electricity consumption report is shown, Fig. 29. The chart is

interactive and by clinking on a bar of the chart, the form where the information was inputted to

the system appears, Fig. 30.


page 97 of 234

Fig. 29: Interactive Report Chart of Electricity Costs.

Fig. 30: ‘Consumption data’ document linked to Electricity Consumption chart.

Action Reports

The actions reports Dashboard, Fig. 79, is configurable and includes a number of useful and

purposeful charts. The charts are interactive and are linked to the Actions and SEUs. Take the

example below, where if the dashboard is opened the ‘Energy Savings by Opportunity’ chart can

be made larger, Fig. 80.


page 98 of 234

Fig. 31: Reports 'Dashboard' view in Enerit ISO 50001 software.

Next by clicking on the ‘Refrigeration’ category which has 24 improvement opportunities the

chart detailing the sub-categories appears, Fig. 81.

Fig. 32: Interactive Report Chart of Energy saving Opportunities by Category.


page 99 of 234

Fig. 33: Interactive Report Chart of Energy saving Opportunities by Sub-Category (Drilled down).

By clicking on the ‘Chiller Sequencing’ sub-category the list of 3 improvement opportunities

applicable to that category are shown, Fig. 82.

Each of these are linked to the improvement opportunity document itself.

Fig. 34: Energy Saving Opportunities linked to the Category/Sub-Category in the interactive charts.


page 100 of 234

4.1.2.3.5 Document Views (Commitment, Planning, Implementation, Checking)

Under each area i.e. Commitment, Planning, Implementation, Checking, an organisation can

input relevant energy documents for document management and control, such as their:

Energy Policy

Energy Manual

Legal & Other Requirements

Procedures & Instructions

Case Studies

Also, when creating documents the user selects the area of the ISO 50001 standard that the

document being added applies to. The Standard section of the software then populates as the

documents are added, which can allow for a clear view of areas in the standard that have and

have not been addressed by the organisation, Fig. 35.

Fig. 35: 'Standard' view in Enerit ISO 50001 software.


page 101 of 234

Audits, Meetings and Nonconformities are created from within the Checking module. An

example of the nonconformities view is illustrated in Fig. 36. It is similar to the action plans view

and highlights overdue actions with a red indicator. Closed actions are indicated with blue and

actions yet to be assigned with a ‘?’ symbol.

Fig. 36: 'Nonconformities' view in Enerit ISO 50001 software.

4.1.3 Application examples

4.1.3.1 Pfizer Pharmaceuticals

Pfizer Pharmaceuticals used our software to get ISO 50001 certification in 3 months. They

eliminated administrative drudgery and saved 50% of the time needed for the organizational part

of ISO 50001. With the time saved, they were able to dedicate more time to energy saving

actions and use the highly dynamic nature of the software to drive actions to completion quickly.

Pfizer estimate that Enerit saves them 5% of energy cost year on year. With a €3 million/year

energy bill, this amounts to €150,000/year extra savings due to Enerit software. For

organizations new to the ISO 50001 approach, the first year’s savings would be 10-20%.

4.1.3.2 University College Cork (UCC)

University College Cork (UCC) in Ireland was the first university worldwide to achieve the ISO

50001 standard in energy management. It is also the first public sector body in Ireland to be

certified to the international standard. Enerit ISO 50001 software was used to implement UCC’s

energy management program and the University was certified to the standard in four months.

UCC decided to utilise Enerit ISO 50001 software, as it uniquely covers all aspects of the ISO

50001 standard including: significant energy uses, energy saving opportunities, energy actions

and planning, corrective actions and audit management.

The energy management consultant behind UCC’s successful certification to this international

standard was Liam McLaughlin of eNMS. Commenting on the success Liam said “UCC have

been successfully implementing energy saving measures and projects for decades and have


page 102 of 234

been winning awards for some of these projects since the early 1990’s. Given the long history of

excellence in the University, it is inspiring to see the improvements in performance that the use

of a systematic approach is bringing them”.

Maurice Ahern, energy manager for UCC, said he used Enerit ISO 50001 software because “its

integration into our existing energy management activities was very straightforward. We now

have a very clear and systematic view of our energy management activities and the progress we

are making”.


page 103 of 234

4.2 Fraunhofer ISE – DataStorage tool

DataStorage is a tool for handling and visualization of measured time series data. It has been

developed at Fraunhofer ISE since 2007 in the framework of energy building monitoring projects

which required an analysis tool capable of handling big amounts of data efficiently and with a

high flexibility. DataStorage provides following features:

Structured persistent data storage in a directory like manner.

Fast access to stored data by time slices.

Configurable data import from different sources csv, ascii, sql. PostGresql

Data export to ascii files and SQL

Filter collection for data processing and persistent storage of filter chains.

Meta data might be connected to data collections or single data series.

Data visualization: Collection of standard data visualization routines and persistent

storage of parameterized diagrams

Data visualization as time-series, scatter, carpet and bar plots

Online data visualization and export through a Java based web front end

Building specific benchmark (Model based analysis). In this module, a simplified model of

the building (zones + HVAC) is used for identification of faults and optimization potentials.

Models in this context are based on the regulations of the CEN standard.

Statistical analysis

Rule and model based Fault Detection and Diagnosis


page 104 of 234

Table 11 DataStorage structure

4.2.1 Description

4.2.1.1 Storage

The database content is stored using the HDF5-Fileformat in form files with the “.h5” suffix.

HDF5 is a data model, library, and file format for storing and managing data. It supports an

unlimited variety of data types, and is designed for flexible and efficient I/O and for high volume

and complex data. HDF5 is portable and is extensible, allowing applications to evolve in their

use of HDF5. The HDF5 Technology suite includes tools and applications for managing,

manipulating, viewing, and analyzing data in the HDF5 format. (The HDF Group, 2011)14.

The Datastorage Application Programming Interface (API) allows the user to cope with h5 files

through methods and functions.

14 http://www.hdfgroup.org/HDF5/

http://www.hdfgroup.org/HDF5/


page 105 of 234

4.2.2 Data import and format

4.2.2.1 Data import from SQL databases is also available.

There are several predefined data importing functions, for reading different data formats,

available for DataStorage. The most generic Importer is the CSV-Data-Importer for reading CSV

Data, which is widely used as a simple data exchange format.´

4.2.2.2 Data quality and temporal resolution

A maximal time resolution of 15 min is required to perform manual and automated FDD.

The quality and structure of data incoming from different sources play an important role for an

efficient import and processing by the Datastorage tool. Unfortunately, there are no existing

standard that defines how time series data have to be outputted by BAS/BMS or additional

sources like dataloggers.

In the context of CASCADE, following rules define the requirement regarding data quality and

structure of inputted data:

The recommended format for measured data is a simple ASCII-format (.csv). Ideally, a file

containing all data points should be generated minutely.

The formatting of the ASCII file (i.e. .csv) should be done as follows:

First Row: The header row is to contain data descriptions. (Data descriptions should not

be changed throughout the duration of the project!)

First Column: Equidistant Timestamps (Date and Time) in a uniform format (ex.

(dd.mm.yyyy HH:MM).

All other columns: The measured data is to be recorded here under the corresponding

header and timestamp.

Erroneous data (i.e. from lost signal) should be designated and recorded with a defined

error value (ex. -999).

Columns should be separated by a semicolon.

A period should be used for all decimal marks.

Temporal resolution should be a maximum of 15 minutes.

Temperature, pressure, flow-rate, and feedback signals should all be recorded with a

high temporal resolution and as an instantaneous value (i.e. no averaged value, no

convector factor.).

If for any reason the temporal resolution is greater than 15 minutes, the operation

feedback signal should be saved as an averaged value.

Variations of this format are for all intents and purposes possible; however, changes are

to be arranged in advance.


page 106 of 234

Fig. 37 Datastorage exemplary data file

4.2.3 Database Structure

The persistent data is structured in a tree like manner. The following basic types of tree nodes

build the database:

Projects: Project nodes are used to split up the data in user definable parts. As the name

suggests they are commonly used to distinguish data associated with a specific project.

Project nodes might be further divided into sub Projects to provide a finer structure.

Sensorgroups: Sensorgroups contain a collection of unprocessed data series (Sensors:

imported data). DataStorage distinguish two kinds of unprocessed data:

o Regular data: data with a fixed time steps.

o Event data: data with arbitrary time steps.

Filtergroups: Filtergroups are similar to Sensorgroups, but contain processed data (i.e.

Filters in the DataStorage terminology). Because Filters principally return regular data

there is only one category of Filtergroups.

Sensors: Sensors are members of a Sensorgroup. They contain unprocessed data and

provide access methods.

Filters: Persistent Filters are members of a Filtergroup and contain process (i.e. filtered)

data and access methods.

Plots: Persistent diagrams are stored in this kind of tree nodes.

Additionally it is possible to assign meta data to every node type.


page 107 of 234

Fig. 38 Datastorage Database Structure

4.2.4 Dataprocessing Concept

Within DataStorage it is possible to define data processing steps and store them along with the

data in the database. So called Filters are used for this purpose. Filters have one or more inputs

and one output. Valid inputs are either Sensors or (the output of) other Filters. Therefore it is

possible to concatenate filters to filter chains that accomplish some more complex processing

task. Once the filter chain has been build, it is possible to use the endpoint of the filter chain (or

if needed every intermediate Filter) to access processed data, in the very same way as

unprocessed data is accessed through Sensors. In order to make the processed data

persistently available, Filters are stored in a Filtergroup. After a Filter is stored to a Filtergroup,

newly available data at it inputs is automatically processed.

Fig. 39 Datastorage Example Dataprocessing Concept

4.2.5 Unified data point naming convention

In order to make the Datastorage tool easily applicable to many buildings and to have analysis

processes automated, a unified point naming convention is a necessary prerequisite. By this

convention the user is able to “tell” the tool which data points are available and the tool can

identify them automatically.


page 108 of 234

Furthermore the point naming convention assures that data points have unique names (which

the original names coming e.g. from the BAS might not have in some cases).

The standard point names are composed of predefined abbreviations for hierarchical categories.

The categories start at the building level and go down to the sensor. Table 1 shows the

categories.

Table 12 Datastorage categories for point naming convention

Nr Category Category

name

Remark

1 Building

User defined: Name of the building or abbreviation of name

2 Zone User defined, Name of Zone to which sensor corresponds (not the

location of the sensor!). e.g. name of the zone which is

served by the AHU that the sensor belongs to (e.g.

supply air temperature)

3 System From system

list

main system to which the sensor belongs. (e.g. heating

circuit, air handling unit (AHU), weather station, energy

supply,…)

4 Subsystem1 if appropriate: subsystem of system

(e.g. heating coil of an AHU or pump of a heating circuit)

5 Subsystem2 if appropriate: subsystem of subsystem 1

(e.g. pump of heating coil for an AHU)

6 Medium if appropriate: medium in which the sensor is placed

(e.g. hot water, chilled water, supply air, etc.)

7 Position

if appropriate: position of the sensor

(e.g. supply or return, primary or secondary loop)


page 109 of 234

8 Kind kind of the data point (either: measured value, set value,

operation signal, alarm)

9 Datapoint The (physical) quantity which is measured

(e.g. temperature, energy, status))

For every category a list of possible items and corresponding abbreviations were defined. A

complete list for the minimal data set is given in the Annex. If the point names are noted down,

the categories are separated by underscore „_“. Further (potentially user defined) specifications

can be appended after a dot „.“ if needed. If a category is not used (e.g. subsystem2) it stays

“empty”, i.e. it has no value.

Two examples are as follows (please refer to Annex for the abbreviations):

Example 1:

Measured supply air temperature of AHU 1 in Building A:

o Building: BuildingA

o Zone: -

o System: AHU.1

o Subsystem1: -

o Subsystem2: -

o Medium: SUPA

o Position: -

o Kind: MEA

o Datapoint: T

Full name: Building.A_ _AHU.1_ _ _SUPA_ _MEA_T

Example 2:

Status of (secondary) Pump of heating coil of AHU 1 in Building A:

o Building: BuildingA

o Zone: -

o System: AHU.1

o Subsystem1: HC

o Subsystem2: PU


page 110 of 234

o Medium: HW

o Position: SUP.SEC

o Kind: SIG

o Datapoint: STAT

Full name: Building.A_ _AHU.1_HC_PU_HW_SUP.SEC_SIG_STAT

Each data point stored in the h5 database as a sensor features meta data which are imported

sequentially after the sensor raw data. Algorithms using the unified data point names and the

hierarchical structure of the data points names have been developed for the automated

generation of standardized visualizations and automated fault detection and diagnosis.

4.2.6 Visualizing Data

4.2.6.1 Standard visualization

DataStorage provides several “plotting modules” for producing different kinds of parameterizable

Plots. The plots might be stored as part of the database.

Time series plot - Chronological sequence of measured values.

Scatter plots (XY plot) - Scatter plots show the dependency of two variables. Additional

information can be gained if the values are grouped. Potentially, several scatter plots can

be combined to scatter plot matrices to show the interdependency of more than 2

variables.

Carpet plots - Carpet plots are used to display long time series of a single variable in

form of a color map which often reveals pattern (like weekly operation patterns)

Box plots

The next figures show examples of different plot types that are implemented in Datastorage.

Fig. 40 Datastorage Time series plot The data is plotted as a line. It will only be used for analysis of

detailed time sequence of data points. The time resolution is 1 hour


page 111 of 234

Fig. 41 Datastorage Ideal carpet plot example (e.g., a fan running Monday to Friday from 8.00 to

18.00.), the time resolution is 1 hour

Fig. 42 Datastorage Carpet plot for real weather and consumption data. This plot shows a real

example. Naturally, the patterns are more blurred as in the ideal example.


page 112 of 234

Fig. 43 Datastorage Scatter plot of energy and water consumption versus outdoor air temperature,

grouped by workday and weekends. These plots help to identify weather dependent control

strategies. The time resolution for these plots is 1 day. Each dot represents a daily mean value.

The plots are also called signature or – for energy – energy signature.


page 113 of 234

Fig. 44 Datastorage Boxplots on daily basis Heat and Electricity consumption on different

weekdays. The boxplots shows the difference of consumption between workdays and weekends

and the distribution on each day

4.3 Fraunhofer ISE - Fault Detection and Diagnosis models

4.3.1 Motivation

Over the last forty years, the level of automation in non-residential buildings has risen

continuously. This is due to the increasing demand for more comfort and convenience and also

to the potential of Building Automation Systems to supervise and control various building

systems and to manage energy and security issues. Numerous scientific studies in the last

decade have indicated that building systems like i.e. air handling units (AHUs) or chillers very

often operate far from their energy optimum and that faults in the energy operation of these

systems often remain unknown over long periods because they do not cause comfort issues or

are simply not detected in time. All this despite an ongoing process in BAS development

integrating all active building systems, enabling a more user friendly utilization and connecting

and interoperating with various devices

These faults have many origins like wrong sensors signals, design faults (over-/undersizing),

deficient controls (simultaneous heating and cooling, wrong heating curves), insufficient

hydraulic balance or a lack of maintenance.

It is commonly admitted that energy savings in a range of 5 to 30% are possible in buildings by

simply optimizing the operation of existing systems. As buildings are responsible for about 40%

of the energy consumption in Europe, a very large energy saving potential remains to be

exploited just by enhancing the operation of buildings. Furthermore, this approach generally

requires only very low investment costs, so that short payback times can be achieved.


page 114 of 234

Nevertheless, barriers such as difficult and cost intensive access to building data due to closed

proprietary solutions, a lack of available tools allowing an automated FDD, a lack of

standardization in the data models or a lack of awareness and resources of building owners

could be identified, which hampers a large scale replication of this approach.

Since 2007, methods and tools have been investigated and developed at the Fraunhofer ISE in

the framework of German and European projects like MODBEN (www.modben.org), MODQS

(www.modqs.de) or BuildingEQ (http://www.buildingeq-online.net/) to support energy managers,

engineers and maintenance personnel in non-domestic buildings in their daily operation and to

help them reduce their energy consumption.

Within CASCADE, rule and model based FDD algorithms will be further developed, tested and

validated accordingly to the specificity of the targeted airport energy systems. Special efforts will

be set to better evaluate and enhance the sensitivity, robustness, ease of implementation of the

FDD methods and to minimize the costs their implementation. An interface between the FDD

algorithms and the supervisory ISO 50001 based Energy Management System will be

developed, that contains all information incoming from the FDD algorithms like location, time,

affected system, subsystem, fault description, fault diagnosis, fault priority, fault impact in terms

of energy, CO2 and costs.

4.3.2 Sensor Fault Detection

Sensor failures may cause faulty system operation and energy waste. Algorithms have been

developed at the Fraunhofer ISE which allows for the identification of malfunctioning sensors on

the basis of single sensor signals. Thus, minor expert knowledge about the inner workings of the

analyzed system is needed to identify sensor faults. In the FDD framework, incoming sensor

data is preprocessed to detect possible sensor faults before implementing FDD algorithms for

the whole targeted system.

There are different types of sensor faults which can be addressed including, but not limited to:

Total malfunction leading to a constant signal

Strong bias

Steps/jumps leading to an offset

Steady rise of the signal

Peaks/outliers with immediate recovery

To distinguish between normal and faulty data, a classifier common to pattern recognition is

utilized. Unique features of different sensor signals are extracted through dimension reducing

transformations (e.g. discrete Fourier transform). Data with known sensor faults are used for

training the classifier. The data for training and classification are gathered from the same time

span in their respective sets of data.

Currently, the following types of sensor faults can be detected:

Total malfunction leading to a constant signal

Steps/jumps leading to an offset

Peaks/outliers with immediate recovery

http://www.modqs.de/

http://www.buildingeq-online.net/


page 115 of 234

4.3.3 Rule based Fault Detection and Diagnosis approach

Fraunhofer ISE is currently developing and testing rule-based Fault Detection and Diagnosis

algorithms on energy systems like water loops, air handling units and chillers.

The rule based fault detection algorithms developed use a priori knowledge of a system to

derive a set of if-then-else rules and inference mechanism that searches through the rules to

draw conclusions. The basis for the fault detection methods is a set of expert rules capable of

automatically identifying the following features and faults on targeted systems:

time schedules

simultaneous cooling and heating

valve and damper faults

lack of setbacks

compliance of measured and set point values

abrupt changes of set point values and control signals to detect possible inappropriate operator intervention

energy generation efficiency equipment clockingIn the framework of CASCADE, rule-based algorithms will be further

developed for air handling units, water loops, compression and absorption chillers and cooling

towers.

4.3.3.1 Rule-based FDD framework

To implement automated FDD for a certain system, it is crucial that all needed input data for the

analysis can be retrieved automatically by the analysis routines. This is assured by the realized

implementation through the usage of a unified data point convention applied to the

measurement data. Furthermore, all system components under investigation (e.g. AHUs) are

mapped to a corresponding class realization in an object oriented manner. Through this, it is

possible for the different implemented components to automatically retrieve the measured data

as needed. In addition, the different classes can pass this data on to the different FDD routines

and choose the most appropriate order to do so. For example, basic routines can be used to

filter the input data and generate an initial preclassification, while more specialized routines are

subsequently used. Fig. 45 displays an exemplary class structure for the case of an

implemented class for air handling units. The AHU class utilizes the specialized FDD class

‘SensorFDD’ to perform a signal based analysis prior further analysis routines. Afterwards the

‘MollierFDD’ pre-classifier is used to check for the consistency of the system state given by the

measurement data. For the final analysis the input data is checked against different rules,

defined in ‘RulesFDD’ subclasses. This object oriented design allows for easy specialization and

extension of the FDD toolset developed at the Fraunhofer ISE.


page 116 of 234

Fig. 45: Exemplary class structure for the case of an implemented AHU unit. The specialized FDD

class ‘SensorFDD’ is utilized to perform a signal based analysis prior further analysis routines.

The ‘MollierFDD’ pre-classifier is used to check for the consistency of the system state given by

the measurement data. For the final analysis the input data is checked against different rules,

defined in ‘RulesFDD’ subclasses.

4.3.4 Rule Based FDD Implementation

4.3.4.1 Mollier Pre-Classifier for air handling units

General description

A pre-classifier based on the moist air enthalpy has been developed to allow a first overall fault

check at the plant level. This top down approach enables a first selection of rules before more

detailed fault detection routines are applied at a component level. Overall faults, e.g. the

simultaneous operation of the preheater and cooler or the simultaneous operation of humidifier

and dehumidifier, can be detected through this. Moreover, the control strategy of the whole plant

can be observed with respect to an energy optimized operation strategy, e.g. minimum fresh air

ratio when outdoor temperature is significant lower or higher than indoor comfort conditions.

The partition of the Mollier hx-diagram for a qualitative analysis of the AHU operation is done

depending on the type of humidification unit. Two main humidification types can be differentiated:

o AHUs with spray type humidifier (usual design) o AHUs with steam type humidifier (design for special application like pharmaceutical

industry or hospitals)


page 117 of 234

This assumption leads to the partitions of the Mollier hx-diagram as depicted in Figure 1 and

Figure 2. For an AHU design with a spray type humidifier, an adiabatic change of state along the

blue isenthalpic curves in the diagram is assumed ideally. Therefore the limits between zone 0, 1

and 3 correspond to these isenthalpic lines, see the following Figure 1.

Figure 1: Zoning of Mollier diagram for AHUs with spray type humidifier

For an AHU design with a steam type humidifier an isothermal change of state along the

horizontal black dashed curves in the diagram is assumed ideally. Therefore, the limits between

zone 0, 1 and 3 is corresponding to these isothermal lines, see following Figure 2.

isotherms

isenthalpic curves

curves with constant relat ive humidity

0

1

43

2

5

6

isotherms

isenthalpic curves

curves with constant relat ive humidity

4

2

5

6

0

1

3


page 118 of 234

Figure 2: Zoning of Mollier diagram for AHUs with steam type humidifier

With respect to the outdoor air psychometric conditions, a qualitative analysis of the operation of

the AHU components can be carried out. Thus, failure modes with an unauthorized operation of

components can be detected. The following operation modes were defined according to the

respective moist air diagram partition.

Spray type

Zone number Mode description

0 Heating and humidification

1 Humidification and adiabatic cooling

2 Only heating

3 Cooling and humidification

4 Only cooling

5 Cooling, dehumidification and post heating

6 Only fresh air circulation

Steam type

Zone number Mode description

0 Heating and humidification

1 Isothermal humidification


page 119 of 234

2 Only heating

3 Cooling and humidification

4 Only cooling

5 Cooling, dehumidification and post heating

6 Only fresh air circulation

First, the comfort area boundaries with maximal and minimal indoor air temperature and humidity values are defined in the Mollier hx-diagram (Figure 3, green lined area) according to the building operational guidelines and owner requirements. If missing, additional sensors measuring the outdoor air conditions have to be installed. Then, the outdoor air state can be located in the hx-diagram (Figure 3, red dot). In this case an AHU with a spray type humidifier is assumed. The outdoor air state is located in zone 0, compare Figure 1. The air has to be conditioned to reach a state within the comfort area. In this example the preheater, humidifier and heater are necessary for this, the state changes are marked with red arrows in following Figure 3.

Figure 3: Example for mollier diagram check.

If the check routines based on the moist air state detect an unauthorized operation of a component, , a fault mode will be displayed, otherwise, a preselection of the FDD rules is carried out according to the operation mode of the plant.


page 120 of 234

The rules used in the different subclasses of ‘RulesFDD’, which are used in the analysis, are

based on distinct thermodynamic laws and expert knowledge from air conditioning engineering.

The rule-based FDD approach for air handling units is based partly on the APAR rules

presented by J. Schein and S. Bushby (2005). The input data is sequentially checked against

the rules. If one of the rules is breached there has to be a failure in the system and the reason

for the discrepancy can be extracted from the rule system.

4.3.5 Model based Fault Detection and Diagnosis

Two main methods for the model-based Fault Detection and Diagnosis will be further developed,

tested and tuned in the framework of CASCADE:

A black box model approach using measurement data from targeted systems to identify a base pattern of a system. Training data are needed to tune the model parameters. Deviation between measured data and model prediction are detected and possible diagnosis for this deviation can be forwarded to the building operator.

A qualitative modeling approach using measurement and/or synthetic data from analytical models to describe relations between the observed quantities in qualitative terms.

4.3.5.1 Black-box model approach

Process history based algorithms known as black-box models will be adapted and tested in the

framework of CASCADE. The linear relationship contained in the signatures of typical

subsystems like chillers or water circuits will be applied to multiple linear regression models.

Supplied with enough information, such as the outdoor and indoor air temperature, water,

electricity and heat consumption, the model will estimate the unknown parameters necessary for

the identification of a system’s operating characteristics. Then, the model will be used to first

monitor a subsystem’s daily energy demand and detect unusual consumption. In a second step,

trials will be carried out to reduce the time resolution of the training data.

The multiple regression model is preceded by a clustering algorithm that uses features derived

from the system’s heat and electricity consumption to determine different day-types present in

the profile of the system’s consumption pattern.

4.3.5.2 Qualitative Model Based FDD with Stochastic Automata

Qualitative Models can be used for supervision and FDD of quantised systems. A quantised

system uses quantisers to transform numerical inputs into qualitative values or states. Thus, a

quantised system describes the qualitative behaviour of a dynamic system (Lichtenberg 1997).


page 121 of 234

Figure 1: Supervision of a quantised system, referring to Schröder (2003)

Quantisation means reduction of information. Therefore, the amount of information that is to be

processed by the supervisor is reduced to a minimum (Schröder 2003). The following Figure

shows the quantisation of a discrete-time and continuously-variable signal into a quantised

output. The quantised output is a qualitative value like “high” or “low”.

Figure 2: Signal quantisation, referring to Lichtenberg 1997 and Schröder (2003)

4.3.5.3 Development of qualitative model for FDD and implementation and test in

CASCADE

In CASCADE, qualitative models based on stochastic automata will be used to determine

system states or outputs of simple systems like a water loop that may occur in the future. This

prediction is based on the supervision of the current states, inputs and outputs of the considered

system. The stochastic automata determine the probability that a subsequent condition occurs

(transition probability).

The integration of stochastic automata for FDD in CASCADE will be done as follow:

1. A model of a selected dynamic process that describes the faultless behavior of the

system will be established in the modeling environment Dymola/Modelica

2. Then, a qualitative model based on a stochastic automata that describes the system

as rough as possible and as precise as necessary will be generated

3. The qualitative model will be used for determining the transition probabilities and

successor states of the faultless system.


page 122 of 234

4. A comparison between the occurring states of the real process and the expected

calculated states of the faultless system will be used to detect faults in the system.


page 123 of 234

4.4 Sensus MI – Diagnostic tool

Sensus MI (SMI) leads the market in providing fully scalable Facility Optimization solutions.

Backed by proven client successes, grants, industry awards, and a dedicated university

research laboratory, only Sensus MI offers an automated facility commissioning solution that

analyses billions of data points to transform static data into “dynamic decisioning”. By detecting,

prioritizing, and measuring fault impacts in real time, Sensus MI lowers energy costs and carbon

emissions, extends equipment life, boosts maintenance efficiency, & enhances comfort in

commercial buildings of any size.

4.4.1 Data Exchange Carrier

A centralized facility data collection and distribution platform for billions of continuously arriving

facility related data points that can be provided from an unlimited number of equipment, building

systems, weather stations, work order systems, and utilities. The SOA has been optimized to

manage multiple processes, threads, and connections to many databases in an automatically

scaling cloud based infrastructure based on data collection, analysis, and distribution need. All

data is normalized with standard label, engineering unit, and conversion criteria and then never

deleted. An underling OLAP multidimensional database allows quick queries and data

organization. All data from any machine or location combination is available for analysis in

graphing tools, web based viewing, CSV downloads, integration through provided web services,

RSS, or automatic FTP pushes.

4.4.2 Automated Fault Detection and Diagnostics

Automatically identifies energy, machine, and system faults before they escalate into large

financial, operational, or comfort problems. Advanced interactive browser based tools and

reporting that include problem descriptions, visualizations, severity levels, and the financial

impact are provided, so faults can be prioritized and acted upon allowing the centralized efficient

management of multiple locations and machines.

4.4.3 Data Collection

Data Collection involves the automated collection, normalization, & storage of data from

equipment & systems in a facility plus utilities, weather stations, & other external enterprise

applications with the data all residing in a centralized common platform allowing macro and

detailed valuable cross system and portfolio analysis.

Local Weather

Station Data

A weather station service feed is established allowing multiple possibilities to

be selected based on proximity to the location normally within a couple of

miles.

Temperature, Humidity, Wind speed & direction, Outside light levels are all

examples of collected data at one-minute intervals used in analysis.

Utility Data Energy data, demand response events, and pricing are all examples of data that can

be consumed from Utilities


page 124 of 234

Energy Star Integration with accepted benchmarking and carbon calculation systems

4.4.4 High frequency collection added value

Sensus MI has proved successful in setting up and collecting data at one-minute intervals,

normalizing, and then storing that data with no storage limitations. Only one-minute interval data

allows many problems to be accurately detected in a remote automated manner such as

equipment efficiencies, hunting, short run times, or cycling that are common in a quick serve

facility especially when humidity, ventilation needs, refrigeration, & appliances are considered.

FE

AT

UR

ES

All SMI stored data is available to view online, download as a CSV, as a web service, or automated FTP transfer and not deleted or purged ever from storage

The Sensus MI data collection platform is based on proven cloud computing technology that provides immediate scalability currently storing billions of data points

If data stops flowing then no automated or manual analysis can occur, so the Sensus MI storage monitor as seen below constantly monitors data collection and errors providing automated notifications if issues

4.4.5 Data Mapping & Normalization

Sensus MI has a ‘Mappings Manager’ wizard that contains a large library of equipment and

systems with standardized naming conventions that can be applied when connecting to a new

facility. Configurations can be saved and applied to future facilities and equipment allowing for

fast and congruent setup. It is important to efficiently ensure that all incoming data is

understood and standardized, so diagnostic formulas can automatically be applied and it is also

easy to analyse the data from one location to the next.

Mapping Manager Features

Set Engineering Unit such as C or F

All text data is converted to numbers 0/1, so it can be graphed and used in formulas. Examples are on /

off, active / inactive, true / false

The appropriate number of decimal places are set

Standard data full label names and abbreviations are applied

The proper time zone is recognize

Mathematical conversions to ensure common units among all stored data


page 125 of 234

4.4.6 Operational Guidelines (OG)

The web based OG system is meant to be the single source of truth for equipment or asset

information, energy, documents, drawings, set points, schedules, demand response, and even

control logic parameters. Data will be populated into the OG for the general location, lighting,

HVAC, and Refrigeration, which will then be utilized for future automated and manual analysis.

The Sensus MI approach to Energy Management is to provide tools, analysis, and interfaces

that quickly allow the identification of energy consumption or demand outliers and opportunities

for improvement, but then further expand the analysis into what actions can be performed to

realize savings with a focus on non-capital intensive solutions.

4.4.7 Energy Benchmarking

The Energy Benchmark tool shown below can be a single interface to identify energy saving

opportunities on a macro level for multiple facilities or subsystems and also compare time

periods to track improvement.

Normalization:

Data is can be normalized or filtered by size, weather, occupied schedules, energy rates, type of facility, & time of the year in order to work towards an apples to apples analysis.

Selection:

The most opportune facilities can be identified through the use of simple slider bars relating to energy efficiency and then energy cost;

The selected facilities characteristics are summarized, so simple what if analysis can be performed such as if those facilities saved 10% to be like the others then there would be ‘x’ amount of savings;


page 126 of 234

4.4.8 Detected faults within CASCADE

Fig. 46 Sensus MI diagnostic for CASCADE 1/2


page 127 of 234

Fig. 47 Sensus MI diagnostic for CASCADE 2/2


page 128 of 234

4.5 PSE - Remus data logger

4.5.1 Brief description

FDD techniques need significant amount of data. This usually involve handling the recording of

data provided by several points of measurement. These points of measurement are normally

located at very different places within an airport facility, thus presenting some challenges.

CASCADE project requires advanced data-logging features as follows:

1. Easy and fast integration of different sensor technologies

a. Direct connected

b. Data bus connected (wired or wireless)

2. Easy configuration tool

3. High availability of recorded data

4. Focus on distributed data acquisition

5. Integration in existing network for data transfer

6. Secure data transfer from the airport to the CASCADE partners

PSE AG and Fraunhofer ISE hve developed data acquisition hardware and software in several

projects. The development of the advanced data logger inclusive Software is based on the

experience made in the past. The software is based on the REMUS data acquisition software

which is already used at Fraunhofer ISE since several years.

4.5.2 Detailed description

4.5.2.1 Advanced data logger (hardware)

For the advanced data logger, different sensor technologies will be integrated. That guarantees

a high flexibility to configure the system to the local requirements. In respect of costs and data

availability a direct connected solution will be preferred. If this is not possible a data bus can be

used or the sensor can be connected via wireless technology. Furthermore by using embedded

systems available at low cost, it is possible to install an advanced data logger for a rather small

number of sensors to be monitored. The data loggers might be connected by an arbitrary

network layer providing TCP/IP (e.g. wireless lan or GSM/UMTS) and thus provide scalability to

the data acquisition network.

Direct connected sensors

If the distance between data logger a sensor is not too far, the sensor can be directly connected

to the data logger. This can be realized, when several sensor are installed at one system.


page 129 of 234

Fig. 48 Principle of direct connected sensors

Data bus connected sensors

If the spatial distribution is more sparse, a bus connected solution for the sensor connection will

be used. Therefore different bus systems will be available (depending on the configuration) on

the advanced data logger

Fig. 49 Principle of bus connected sensors

This can be done both ways, wired or wireless depending on the situation on side.

4.5.2.2 Data acquisition Software (Remus)

Remus is a data acquisition software, developed and used since several years within the

Fraunhofer ISE. It has proven to be reliable and provides high data availability with low

maintenance effort. It contains drivers for several data acquisition devices and data protocols

and is easily extendable with respect to new hardware drivers.

Within the project the interoperability and remote maintained of measurements conducted with

Remus will be improved by developing new efficient network data and maintance interfaces.

Each advance data logger running Remus is buffering the data in addition to propagate it to the

dataserver (or another datalogger), this improves the reliability of the data acquisition in presents

of unreliable network connections (e.g. wireless or UMTS connections). The data buffering

management will be improved by the new data and maintance interface:remote maintenance:

centralized integrated maintenance of all distributed data loggers will be made available by the

new remote maintenance interface.

Auto cleaning buffer space if needed and after acknowledged data transfer


page 130 of 234

Low latency: Using the opportunity to transfer (push) the data to the data server as soon

as a connection becomes available (important in presents of very unreliable connections)

Efficient compression for both, data transport and buffering of data

Fault detection: Along with the fault detections already implemented in Remus, the data

and maintance interface will be equipped with an additional system failure monitoring. For

instance a warning message could be issued, if the permanent storage of a data logger is

getting low or the operating system is reporting some errors.

A graphical user interface for maintenance and displaying the status of the distributed data

loggers will be developed. It will used the maintenance interface to provide simultaneous access

to all of the loggers in a network.

4.5.2.3 Integration of data points from existing BMS

In both cases a lot of data already recorded by the existing BMS systems. There are different

concepts in both airports. In Work package 4.1 SMI will develop an interface to collect the data

from the existing BckaMS. Therefore standard protocols as BACNet, SQL will be implemented.

To integrate this data to the CASCADE solution, an interface has to be defined between the

PSE data acquisition software and the software from SMI.

The data from BMS and the data from the additional installed data loggers have to be

synchronized.

4.5.2.4 Data transfer within the airport

The data which are recorded with the advanced data loggers will be transferred within the airport

to a central PC. There the data a collected and send to the consortium (see Chapter 6.2.4)

If possible the internal network is used to transfer the data within the airport. Therefore a VLAN

subnet will be configured by the local network administrator. Within this subnet, the data can be

transferred from the distributed advanced data logger to the central PC. In Chapter 6.3 you find

a graph who shows the distribution for the Malpensa and Fiumicino airport.

4.5.2.5 Data transfer between the airport and the CASCADE consortium

To transfer the data from the airports to the consortium, a VPN connection will be installed. The

VPN establishes a direct connection between the VLAN within the airports and Fraunhofer ISE.

The Fraunhofer ISE will provide the data to the consortium. This can be done in several ways:

- A web based service publishes the data as compressed ASCII Files.

- The data is pushed to some database / third-party-system (e.g. for documentation in

ENERIT software). The protocols may include ODBC, XML, JSON as possible others.


page 131 of 234

Table 13 Measures and ranges

Physical measure Range Accuracy Comment

Temperature 0 – 100 °C Tabsolute: +/- 1 °C

delta T: +/- 0.2 °C

For ambient sensors

(-20°C to 100°C)

Humidity 0 – 100 % r.h. +/- 2% Air humidity

Volume flow (air) 0.1 – 25 l/min +/- (2% m.V.** + 0.5%

F.S*)

Humidifier water

consumption

Volume flow (water) Depending on

measurement point +/- 2% (m.V.**)

Flow meter and

temperature sensor

Digital Input 0/1 e.g. Pump On/Off

Electric power 0 – 15 kW 0,4 % (m.V.**) Pump / Fan

Light meter 0 – 100 °C Tabsolute: +/- 1 °C

delta T: +/- 0.2 °C

For ambient sensors

(-20°C to 100°C)


page 132 of 234

4.6 Pupin – Ontology

The next step in evolution of facility management systems can be seen in the application of

emerging advanced Semantic Web technologies, which considers increased usage of open-

source and/or standardized concepts for data classification and interpretation. The advantage of

such technologies reflects in reducing the heterogeneity of system, higher flexibility of control

algorithms and in easier adoption of future technical systems/equipment. For providing more

intelligent, holistic, management systems, that harmonize this diversity, definition of

standardized and comprehensive facility data model which classifies and describes

information/data within the domain of interest is needed. One way of providing this metadata

layer is based on the concept of ontology modelling.

Ontology represents one of the advanced Semantic Web technologies and can be defined as a

formal way of representing the knowledge as a set of concepts within a domain of interest, while

also describing the corresponding relationships between those concepts. Furthermore, ontology

is utilized to describe a domain of interest by classifying and defining the related entities, but

also to reason upon the entities modelled within that domain. It defines entities, properties,

interactions, actors and basic concepts that compose the common vocabulary for all members of

the domain in which it is defined. Therefore, ontology as a concept for knowledge representation

found a broad perspective of application, such as: to share common understanding of the

structure of information among people or software agents, to enable reuse of domain knowledge,

to make domain assumptions explicit, to separate domain knowledge from the operational

knowledge, and to analyse domain knowledge. Additionally, by allowing reasoning and

inferencing capabilities, ontologies, as one of the techniques used to cope with the “big data”

paradigm, facilitate rapid exploitation of large quantity of information. Since “big data” represents

a collection of data sets so large and complex that it becomes difficult to process using on-hand

database management tools, it requires advanced technologies to efficiently process large

quantities of data. By attaching meaning to data and by providing logical relationship between

entities, ontologies provide a way to transform information into knowledge, so the data become

easier to retrieve, correlate and integrate.

This document contains the descriptions of the Core CASCADE Airport Ontology which provides

a generic model of the airport facility as a set of concepts and corresponding relationships

among them. The Ontology was based on the results of the technical characterization,

undertaken within the WP1, and the analysis of the different aspects of the involved devices and

modules.

By utilizing the concept of Ontology modelling the aim was to structure/classify the technical

characteristics of the airport facility, i.e. to model the semantics of the energy management

related systems installed at the airport. Furthermore, the Ontology approach has been selected

as the core technology to build the transversal middleware which would provide a homogeneous

and common platform for all diverse devices, sensors and systems involved into the CASCADE

solution.

Therefore, the main aspects of the CASCADE Airport Ontology are given as following:


page 133 of 234

modeling the domain of interest, i.e. defining the infrastructure of an airport facility

terminal building by classifying a range of installed systems relevant to the energy

consumption aspect and their belonging sensor/actuator devices;

providing means for technical characterization and semantic interpretation of signals

going to/from the installed system/equipment, that is: which incoming/outgoing signal

belongs to which device/system? what are their characteristics? relationships with other

devices/signals)

providing the topological profile of the airport facility and information about

geographical location of every installed device/signal (useful for analyzing spatial

correlation of data)

In addition, this approach provides consistent, yet flexible means for classification and

description of each device/signal that CASCADE framework might have to deal with.

Finally, in order to align the Core CASCADE Airport Ontology model with the contemporary

Ontology architectures, leading Ontology modelling standards, such as the Suggested Upper

Merged Ontology (SUMO), (IEEE, 2003) and the Common Information Model (CIM), as part of

IEC 61970 series of standards, were considered as a starting point. Furthermore, in order to

provide transparent communication within the CASCADE framework, the core Ontology model

was also aligned with the Fraunhofer’s proprietary unified data-point naming convention.

4.6.1 Concept

As mentioned above ontology is a formal description of the concepts and relationships that can

exist for an agent or a community of agents, usually inside a specific domain. It defines entities,

properties, interactions, actors and basic concepts that compose the common vocabulary for all

members of the domain in which it is defined. Ontologies are defined by classes, properties that

describe various features and attributes of classes and restrictions on these properties. Classes

describe concepts whereas subclasses represent concepts that are more specific. The

development of ontology usually includes:

to define the classes of the ontology,

to arrange the classes hierarchically,

to define the properties and their possible values.

Properties can be referred to an only class or subclass or can be used to relate different classes.

Some frequent uses of any ontology are:

to share common understanding of the structure of information among people or software

agents,

to enable reuse of domain knowledge,

to make domain assumptions explicit,

to separate domain knowledge from the operational knowledge,

to analyze domain knowledge.


page 134 of 234

One of the results of defining ontologies in a specific domain is the definition of a framework

where most of the disciplines, technologies, which will be involved in the domain, can adopt the

common vocabulary defined in the ontology. It can be the start point to several technologies,

applications and software that use the ontology as knowledge base to other objectives.

4.6.2 Ontology Class Hierarchy

In this section, the class hierarchy of the Core CASCADE Airport Ontology is presented in Fig.

50.


page 135 of 234

Fig. 50 CASCADE Core Ontology class hierarchy


page 136 of 234

5 CASCADE Integrated solution

This section deals with the integration in a coherent system of selected elements of the

heterogeneous components, described in section 3. The first mission is addressed in Section

5.1 by describing the proposed CASCADE solution architecture (this include also results from

the work in task 5.1), the paradigms used for the integration of different technologies and an

overview of the different elements, but within the CASCADE solution context. Section 5.3

identifies the main key stakeholders that will benefit from the CASCADE solution. The key

players are identified in both a general scenario (any possible airport) and also in a pilot specific

one at MXP and FCO. Section 5.4 characterises the running mechanism of CASCADE Energy

Action System (EAS) workflow, it does this by describing first how the action are triggered by

events (e.g. a fault automatically detected or a manual suggestion for an improvement

opportunity) and then how would travel through the different components of the system

illustrating how the solution will manipulate and transform the information following a logical

workflow. The same section shows how different stakeholders will approach and interact with

CASCADE in their day-to-day activity. Finally section 5.5 shows how actions are managed and

tracked in the along the whole process form the triggering event to the completion.

To illustrate this section approach, we use the fundamental division of system in two parts: form

and functionality.

Fig. 51 Form & Functionality paradigm

Form is commonly defined as the architecture or platform that conforms the stable

structure of the business over time, focusing in the inner essence of the system, in “what

the system is”, providing a robust structure that support the system/user conceptual

model along its lifecycle.

Functionality relates to the end user’s view of the services provided by the system, the

different processes, task and operations the system produces and how the tasks are

conceptualized, distributed and executed by the system: “what the system does” .

functionality

form

5.1 CASCADE Solution Definition5.2 CASCADE Solution Architecture

5.3 CASCADE Solution Users5.4 CASCADE Energy Action System5.5 CASCADE Action Management and Tracking


page 137 of 234

5.1 Airports requirements and CASCADE solution definition

WP2 CASCADE methodology starts form the airport requirements identified in WP1 and defines

2 things:

The integration of heterogeneous technological components in a coherent CASCADE

solution starting from end users requirements;

A methodology for the implementation of the CASCADE solution

the CASCADE solution functionalities addressing in detail the integration of the utilised

technologies. The main input form WP1 is the overview of gaps for improvements identified

within airports energy and maintenance management. These gaps were either suggested by the

airports management staff involved in CASCADE or by an iteration of between consortium

experts and airport staff during the documentation gathering process. During this process it was

possible to identify two different perspectives:

SEA and ADR staff (end users) wanted to:

o know more about CASCADE solution and available technologies within the

overall solution such as sub-metering and data-logging hardware and software,

FDD algorithms and ISO 50001 energy and action management;

o suggest needs to be addressed with the CASCADE solution to improve airport

operation staff activities;

The rest of the consortium (technology/methodology providers and integrators)

wanted to:

o know more about airport operation especially in relation to energy management

and maintenance;

o propose features of their technologies that could be adopted by airports in order

to improve operation activities.

The result of this work presented in WP1 identified the boundaries of the CASCADE solution

scope and functionalities which are described in this deliverable. This choice of the solution has

been a trade-off between:

Answering real airports needs in order to develop a useful solution that then can be

utilised by MXP and FCO airports and also replicated to other EU airports after the end

project;

Developing something within the scope, budget and timeframe of the project that means

not to overpromise and to consider the starting point of standalone technologies available

within the consortium and the resources allocated for further advancement in each

technology and also the integration effort for the overall CASCADE solution.

The above trade-off points are also showed in Fig. 52 where the different areas are identified

and the core CASCADE solution domain is in the centre.


page 138 of 234

Fig. 52 CASCADE solution trade-off between airport needs and consortium technologies

The CASCADE solution core/domain identification can be seen both as an opportunity and as a

threat for both airports and technologies providers/integrators as showed in Table 14.

Table 14: CASCADE solution threat and opportunities for both airports and consortium

THREAT OPPORTUNITY

SEA and ADR

(End users)

Solution not useful or not

answering real airports needs

A customised solution that

answer airport needs

Rest of the consortium

(Technology/methodology

providers and integrators)

Overpromise beyond the

project scope, budget and

timeframe, or do not

answer/support real airport

needs

Develop something very

useful for end users that can

also be replicated for airports

after the project

A key decision was taken during this iterative process that was to focus only on thermal systems

and do not consider FDD for lighting systems since there was no scope for large improvements

due to the lack of lighting automation in both airports (e.g. localised dimming or presence

detection).

The CASCADE solution will mainly focus on 5 aspects:

Performance monitoring of selected zones and systems;

Automated Fault Detection and Diagnosis based on measured performance data;


page 139 of 234

Assessment of service-level agreement with maintenance contractors on the selected

systems and subsystems and support of performance based maintenance;

Energy action management and tracking;

CO2 and energy savings accountancy in accordance with ISO50001 standard.

5.2 CASCADE Solution Architecture

This Section covers the description of the CASCADE solution architecture and the fundamental

paradigms underpinning the CASCADE scheme.

CASCADE proposition is strengthened by the adoption of a number of principles that will be

described later, such us: Service Oriented Architecture (SOA), Loosely Coupling and the use of

Ontologies. The three tiers arrangement (1-physical layer, 2-bussines logic layer and 3-service

layer) bear a resemblance to the Open System Interconnection Model (OSI - ISO/IEC 7498-1)

(ISO, 1994). This standard was established in the 80’s by the International Standard

Organisation (ISO) for network data communications and by the Institute of Electrical and

Electronic engineers (IEEE). The OSI model describes an architecture for network

communications distributed in seven layers, ranging from a bottom physical layer which relies

mostly in hardware to the top level application layer, which comprises mainly software

applications. With the development and growth of Internet-based applications the TCP/IP

protocol was adopted as the new paradigm. The TCP/IP can be described as consisting in a 4

layers pile and it is commonly accepted that the networking function could still be described in

relation with the OSI layers model, as it is shown in Fig. 53 .

Fig. 53 OSI Model Vs. TCP/IP Model


page 140 of 234

5.2.1 Challenges of Systems Integration

The following development of Information Technologies has rendered the lower layers of the

OSI model for all practical purposes now completely commoditized (Del Rio, 2009), letting the

upper layers of the model (Applications, Interfaces, User interaction, Services, etc.) as the arena

for the most recent advances. With regards to CASCADE Architecture, an approach based in

SOA (Service Oriented Architecture) will provide the most flexible solution to tackle the

intrinsic root problems of systems integration, as described by some authors (McGoveran, 2006),

a SOA approach will adapt better to:

Inherent Complexity: There is no process, system or business activity simple enough.

Constant competition promotes differentiation and change. CASCADE Architecture

should considere IT assets as “reusable” components;

Unforeseeable Requirements: It is almost impossible to predict all requirements for an

application or even other applications providing services to a system in the future.

Requirements will change adding, substracting or modifying existing status;

Perpetual Change: The current state of applications in an organisation is likely to change

over time. New technologies will impose new requirements, other will rest out of date or

unable to provide value. Moreover, organisations themselves can change internally and

can also be merged, reduced or split into parts.

SOA defines a set of rules regarding how to integrate widely disparate applications for a Web-

based environment and can integrate multiple implementation platforms. Rather than defining

specific APIs, SOA defines the interface in terms of protocols and functionality reflecting

Business Rules and Data Transformation Rules, as illustrated in Fig. 54.


page 141 of 234

Fig. 54 CASCADE Service Oriented Architecture

In fact, a SOA based bussines logic layer design will provide model and architectural

independence for the CASCADE partners, leveragin IT assets and securing long term added

value by the five service providers:

Fraunhofer ISE: Data Storage Tool

Fraunhofer ISE: FDD Engine

SENSUS MI: FDD Engine

ENERIT Ltd: Energy Management Tool

IMP: Airport Ontology

CASCADE Architecture embrace heterogeneity as a necessary condition for dynamic systems,

assuming that business, people and technologies will change and evolve, even though the

efforts on standardisation and the progressive commoditization on the lower layers of IT network

models.

5.2.2 Use of Ontologies

An Ontology is a formal representation of concepts within a domain and their relationships.

Ontologies are used as taxonomic models for the specification of conceptualised knowledge in

many fields. More concisely it is an IT artefact that establishes a formal definition of a domain of

interest regardless of latter evolutions or dependences on specific system language or protocols.


page 142 of 234

This way an ontology can be recognised by having the following attributes, according to White

(White, 2005):

It is a declarative, explicit representation or a domain;

It is machine readable;

It is consensual: many people have critiqued, revised and agreed upon the terms and

relationships contained in the ontology;

It can be used in multiple applications;

It is stable and long living.

The main benefit of using ontologies is the ability to separate and declare knowledge in a way

that can be inspected by humans and usable by computer programs, from system code. This

way, the CASCADE Airport Ontology will also add value to the project by providing a technology-

neutral terminology that will remain regardless of software evolution and mitigate risks of

dependency on ever changing applications.

5.2.3 Loose Coupling

Loose coupling refers to a system’s interconnection that reduces the common dependence of

knowledge of different parts of an architecture. The two main advantage of using a loosely

coupled architecture are:

It reduces the risk that a potential change made in one element would create

unexpectedly a change affecting other elements;

Limiting interconnections ease the identification of problems, bottlenecks and helps

identify and isolate the problem without affecting the rest of elements.

CASCADE uses flexible file formatting such as XML or JSON that dramatically enhances loosely

coupling between applications. This, in addition to the use of standardized Data communications

protocols such SOAP or REST will promote reusability and change.

5.2.4 CASCADE Architecture - The Big Picture

CASCADE will develop a distributed network architecture following a typical three-tiers

architecture as shown in Fig. 55. These layers are Physical Layer, Business Logic Layer and

Service Level or Application Layer.


page 143 of 234

Fig. 55 CASCADE Solution Architecture

5.2.4.1 Physical Layer

The Physical Layer (PL) concentrates the hardware and physical network used for gathering

data related to physical airport facilities, energy systems, environmental variables and data

related from enterprise wide applications. Data will be concentrate in a local server at the airport

facility and the sent via internet to the Fraunhofer Data storage tool server in Freiburg (Fig. 56).


page 144 of 234

Fig. 56 Physical layer - CASCADE Local Data Server

Weather Data

Weather Data is integrated in CASCADE as a crucial part to develop further analysis, energy

consumption forecast and optimize energy systems operation. Weather data can be retrieved

from:

Airport owned weather stations;

National Meteo Services as:

o Met Office DataPoint Beta (UK) (http://www.metoffice.gov.uk/datapoint)

Commercial applications as:

o Weather Underground API (http://www.wunderground.com/weather/api/)

o Weather XML Data Feed (http://www.weather.com/services/xmloap.html)

BMS & Dataloggers

Building Management Systems (BMS) or Building Automation Systems (BAS) are used to

facilitate systems control and building energy management. A Building Management System is a

computer-based control system installed in buildings that controls and monitors the building’s

mechanical and electrical systems. Though specific components may differ, these systems

normally include heating, ventilation and air conditioning (HVAC), lighting, power, security, and

fire protection systems. The main tasks of a BMS are:

Controlling electrical and mechanical components;

Monitoring environmental and technical variables in the controlled areas;

Optimising the operation of the facilities

Within the CASCADE solution it is expected to gather most of the systems data form the BMS,

however some of the data needed for feeding the FDD algorithms will not be available within

BMS, therefore additional metering hardware (sensors and meters) will need to be installed. For

this reason the PSE dataloggers with the advanced software REMUS will be employed (see 4.5).

http://www.metoffice.gov.uk/datapoint

http://www.wunderground.com/weather/api/

http://www.weather.com/services/xmloap.html


page 145 of 234

Enterprise Management Systems:

o BDV (Data Base Voli) and Flight Information Display System (FIDS). This system

is designed to provide airport management with automated control to distribute

and display critical information to the traveling public, airport tenants, and airport

operational staff. FIDS is directly connected to the Airport Operational Database

and Resource Management System;

o AIMS (Airport Information Management System). This module handles all aspects

of gate use, customer complaint tracking, passenger information displays and link

with other information systems and management services;

o ATBS (Air Traffic Billing System). This module deals with the financial

management of airport and airlines and the day to day air traffic control system;

o IANMMAP (Inventory and Maintenance Management Application). This

application (or others equivalent) is usually used in the Operations and

Maintenance department to manage the inventories and maintenance for capital

equipment and facilities.

5.2.4.2 Business Logic Layer

This layer coordinates the different parts of the CASCADE application. Command processing,

logical task decision and evaluation is performed remotely in a variety of application servers. The

Business Logic Layer (BLL) will comprise all IT artefacts, applications, rules and algorithms that

deal with the transformation of data from the physical layer to the final user interface. The BLL

designed initially will deliver a multi-provider “IT as a service” (ITaaS) platform serving the final

Application Layer. Internet is used as a network to exchange information, different partners will

act and interact within the CASCADE solution using own servers at remote locations.

Fig. 57 Fraunhofer DATA Storage Tool and FDD Engine


page 146 of 234

The Fraunhofer Datastorage tool, is responsible to receive measure data for the CASCADE local

data server, and supply:

FDD alarms to the Enerit tool for action management;

Advance visualisation of measured and handled data to the user, though the CASCADE

web interface;

Measured data to the Sensus MI tool for parallel FDD.

Fig. 58 SENSUS MI – FDD Engine

The Sensus MI diagnostic tool is responsible (like the Fraunhofer FDD engine built in the

Datastorage tool) to supply FDD alarms, according to his described functionalities (section 4.3).

The FDD algorithms run with measured data collected form the Datastorage tool server and

provides output to the Enerit tool.

Fig. 59 ENERIT Energy Management Tool

The Enerit tool, receives FDD alarms from the FDD providers (Fraunhofer FDD engine

embedded in the Datastorage tool and Sensus MI tool), then it transforms them in content rich

information by interrogating the airport ontology. The Enerit tool receives also input form the

users through the CASCADE web interface. The output of the tool is systems that supports

energy action management.


page 147 of 234

Fig. 60 Airport ONTOLOGY – IMP

5.2.4.3 Application Layer

The Application Layer provides access and services to the final user application. The main

function of the CASCADE Graphical User Interface (GUI) is to translate task and results into

information that users can understand and interact. The GUI is channelling software delivering

access to both ENERIT Management Tool and the Fraunhofer ISE Web Interface. ENERIT Tool

will provide the GUI for the support of effective energy action management (in accordance with

ISO 50001), and the Fraunhofer ISE Web Interface will provide access to advanced visualisation

to measured data and specific views of performance data relating to detected faults. The final

web interface enables effective energy action management for all stakeholders involved in the

energy O&M process.

Fig. 61 CASCADE Application WEB Interface


page 148 of 234

5.3 CASCADE Solution users

In this section we present first a generic description of the figures within the airports that have

been identified as end users of the CASCADE solution. These users will have all a customised

access to the CASCADE solution web interface with different rights and visualisation capabilities

(Fig. 62). A general description of main roles and activities of interest to the CASADE solution

within an airport organisation is given below.

A detailed description of the users in the 2 airports is also given. As part of the CACADE project

surveys were carried out in both pilot airports to identify the users of the CASCADE solution, a

description of users at FCO and MXP is given in section 5.3.1 and 5.3.2 respectively. The

practices described in these sections only relate to how each of the users currently operates at

the airports.

Section 5.4 (energy action system) describes how the key players in the airports will utilise the

CASCADE solution to support their activity, this is detailed with workflow examples.

Fig. 62 User access to CASCADE Solution

1. Energy Management Office (EMO)

The Energy Management Office monitors the energy consumption with monthly

reports identifying and validating (in broad terms) energy saving actions. Through

yearly energy reviews/audits, they can identify Significant Energy Users and

manually enter actions.

2. Operations and Maintenance (O&M)

The Operation and Maintenance (O&M) monitor the BMS, assign actions to

external maintenance company and supervise their work. They are also

responsible for dealing with comfort complaints. They keep track of important

actions. Their number one mission is to ensure efficient and correct operation of

all equipment and systems.

3. Technical Assistance Operations (TAO)

The Technical Assistance Operations (TAO) are responsible for making energy

efficiency investments and in managing contracts for new equipment (quotation,

design, installation, commissioning) and making long-term plans. They are also

responsible for signing off on extraordinary actions that are not included in the ext.

maintenance contracts (e.g. fan coils – the replacement of fan may include in the

maintenance contract, but the replacement of the coil may not be and it needs extra budget

CASCADE Web Interface


page 149 of 234

to be approved by the TAO office. The duties of this office are sometimes carried out directly

by the energy management office.

4. External Maintenance Company (Ext. M. Co.)

The External Maintenance Companies are outsourced companies that have a

contract with the airports that make them responsible for addressing all alarms

raised by the BMS along with HVAC scheduled and emergency maintenance

actions. As per contract agreement they need to provide a minimum level of service

on the systems they maintain. These companies have personnel based at the airport.

5.3.1 CASCADE solution users at ADR FCO

In ADR FCO there were 4 main users outlined:

1. SEA – Sistemi Energetici Aeroportuali – Energy manager office

2. TOM – Tecnici Operativi di Manutenzione - HVAC operation and maintenance office

3. TAL – Tecnici Assistente Lavori

4. Olicar – External Maintenance Company

1. Energy Management Office (EMO) >>> SEA – Sistemi Energetici Aeroportuali

The energy manager of the airport works in close collaboration with 2 engineers of

the Energy management office. Among their activities, they monitor the energy

consumption with monthly reports identifying and validating (in broad terms) energy

saving actions. They make the yearly energy plan, identifying SEUs and setting out O&T.

2. Operations and Maintenance (O&M) >>> TOM – Tecnici Operativi di Manutenzione

HVAC operation and maintenance office consists of 6 people under the supervision

of a team leader. They monitor the BMS, assign actions to Olicar and supervise their

work, communicating it to Olicar with phone calls and SAP. They keep track of

important actions on an excel spreadsheet:

– Daily report with closed actions

– A cumulative spreadsheet that gather all the actions still open in the long term

The actions that are manually sent to Olicar (though SAP – printout) are generated by

(approximate %):

– Complaints (though the SAP/ADR call enter) – 50%

– Alarms form the BMS – 25%

– Manual fault detection (looking at the BMS interface screens) – 25%

3. Technical Assistance Operations (TAO) >>> TAL - Tecnici Assistenza Lavori


page 150 of 234

They are responsible for supervising the HVAC operation and maintenance (TOM)

office, making long term plans (part of 5year plan) on HVAC equipment, managing

contracts for new equipment (quotation, design, installation, commissioning) and

they are also responsible for signing off on extraordinary actions that are not included in the

ext. maintenance contracts (e.g. fan coils – Replacement of fan is included in the

maintenance contract, but the replacement of the coil is not and needs extra budget).

4. External Maintenance Company (Ext. M. Co.) >>> Olicar

Olicar are an outsourced maintenance company based at the airport. They are

responsible for HVAC scheduled and emergency maintenance. Emergency

maintenance is triggered by:

– ADR-SAP call centre (3434) – e.g. for a comfort complaint

– TOM contact Olicar through SAP or by phone, for a:

• “Real” alarm on the BMS (“real” because a double check is made by TOM

before contacting Olicar)

• A degrading performance or something wrong manually detected by TOM

before the BMS detects it

5.3.2 CASCADE solution users at SEA MXP

In SEA MXP the Energy Management Office (EMO) takes care of the long term planning also

directly supervise the work of the operation and maintenance office (O&M). The O&M office is

also responsible for energy for signing off on extraordinary actions that are not included in the

ext. maintenance contracts. Therefore there is no need for the Technical Assistance Operations

(TAO). Therefore the 3 main users outlined are:

1. HVAC operation and maintenance office

2. Energy manager office

3. Gemmo – External Maintenance Company

1. Energy Management Office (EMO) >>> Energy Management office

The energy manager for SEA works in close collaboration with another engineer as

part of the energy management office. Among their activities, they monitor the

energy consumption with daily reports identifying and validating (in broad terms)

energy saving actions. They make the yearly energy plan, identifying SEUs and setting out

O&T. The EMO directly supervise the work of the operation and maintenance office.

2. Operations and Maintenance (O&M) >>> Impianti termomeccanici

HVAC operation and maintenance office form MXP Terminal 1 consists of 4

people under the supervision of a team leader. They supervise the BMS and the

maintenance actions carried out by Gemmo (External Maintenance Company). If


page 151 of 234

they see any additional fault they communicate it to Gemmo with: email, phone calls and

SAP. Every morning they check what the open actions on SAP are and also they check

when and how the most critical actions are carried out by Gemmo. They implement energy

savings schedules in close collaboration discussion with energy management office. for

signing off on extraordinary actions that are not included in the ext. maintenance contracts. A

support role in monitoring the BMS is given by the control room in which a full reading

access is given for the BMS. On the SEA side both the control room and the O&M office

monitor the BMS during the day, whereas at night the control room takes over and becomes

responsible for the management of emergency maintenance.

3. External Maintenance Company (Ext. M. Co.)

Gemmo are the outsourced maintenance company based at the airport. They are

responsible for HVAC scheduled and emergency maintenance, Gemmo operators

monitor the BMS 24/7 and are responsible for addressing all alarms raised by the

BMS. They are supervised by the HVAC operation and maintenance office (TOM)


page 152 of 234

5.4 CASCADE Energy Action System (EAS) workflow

The Energy Action System (EAS) for the CASCADE project is modelled on the ISO 50001

Action Management Approach. Improvement opportunities are recognised opportunities to

increase efficiency and save energy. Once recognised, the Enerit ISO 50001 software manages

these improvement opportunities through a workflow. The software allows a user to track actions

through the workflow, and also to view action report charts. In the CASCADE project, these

improvement opportunities come from a number of different sources (See Fig. 63):

1. Improvement Opportunities/Suggestions (Manual FDD); 2. Pre-populated list (through EnMS Audit/Energy Review); 3. Fault Detection Diagnosis alarms (JSON file received from ISE/SMI) and; 4. Grouped SCADA alarms (filtered/grouped SCADA/BMS Alarms from ISE/SMI)).

Fig. 63: Sources of Improvement Opportunities and Energy Saving Actions

It is through Enerit ISO 50001 software, that these actions will be managed from creation to

closure. Action plans will be available to check the progress of actions (at each step in the

workflow) along with all relevant information about the actions. ISE/SMI are responsible for

managing the signals from the Fault Detection Diagnosis (FDD) and for the filtering/grouping of

the SCADA/BMS alarms (Linking Actions Actors and Standard Task 5.2). Once these signals

are received by the Enerit Agent, the Enerit System builds content rich actions which are then

sent for REVIEW by Operations and Maintenance (O&M) (See Fig. 74 and/or Fig. 75).


page 153 of 234

Fig. 64: CASCADE FDD and Alarm sorting

Enerit’s expertise does not lie in the handling of small alarms, but are more about corrective and

preventative actions being triggered as a result of these alarms to guarantee closure of energy

saving actions. Therefore, if a particular alarm keeps occurring, then a corrective/preventative

action will be triggered. The following subsections give a detailed workflow description of each of

the four energy actions triggers.

5.4.1 Improvement Opportunities/Suggestions

Improvement opportunities are recognised ways of correcting/fixing inefficiencies, failures, leaks,

pressure drops, damaged components, etc. Hence, by acting to carry out improvement

opportunities, energy savings are achievable.

Improvement Opportunities/Suggestions can be recognised as a result of:

1. An energy management system audit;

2. An energy saving suggestion;

3. Reviewing the operation of a significant energy user;

4. Energy meetings.

For example, if an energy audit/review of HVAC systems is being carried out, improvement

opportunities are entered into the system using the Improvement Opportunities-Energy Saving

Action form (See Fig. 66).

Similarly, for example, if member of the energy team or member of external maintenance

company comes across a fault as part of daily Maintenance, the user can input improvement

opportunities into the Enerit system through the suggestion form seen in Fig. 68.


page 154 of 234

This feature could also be utilised to aid the Technical Assistance Operations (TAO) to record energy saving opportunities for their 5yr plan or long term planning.

Fig. 65 shows a schematic of the steps required to successfully implement an improvement

opportunity through to an action. The diagram describes the order in which actions are

successfully and efficiently created, reviewed, assigned, verified and closed.

(Note: Improvement opportunities can be referred to a number of ways:

Energy Saving Opportunity

Energy Conservation Measure

Energy Saving Action (this is more the resulting action from the opportunity itself))

Fig. 65: Steps required to successfully implement an improvement opportunity-energy saving

action

Fig. 66 illustrates the current Enerit ISO 50001 software improvement opportunity- energy saving

action workflow.

Create Review Plan Assign Check Verify Close


page 155 of 234

Improvement Opportunity-Energy Saving Action Workflow (Current Enerit Workflow)

Fig. 66: Enerit ISO 50001 Software Improvement Opportunity - Energy Saving Action Workflow


page 156 of 234

The following describes the workflow in words:

An improvement opportunity can be created by relevant members of the staff at any level in the organisation. For the CASCADE project, the creators (Ext. M. Co / TAO/ O&M/ EMO) have the ability to save a DRAFT improvement opportunity form, if perhaps they need to return to it at a later stage to input more detail.

Once an improvement opportunity has been submitted FOR REVIEW to the energy manager a notification email is sent to the energy manager for the location.

Once the energy manager has reviewed the improvement opportunity, he can then include it in the action plan (PLANNED), CLOSE it or place it in ON-HOLD.

Note: If PLANNED, the improvement opportunity then becomes an action.

If the action is to be assigned to a relevant person, the energy manager must add detail on; the validation method; the start date; end date and possible further notes for the assignee.

Once ASSIGNED, the action is then included in the action plan the assignee receives a notification email with a link to the action. The assignee has the ability to reject the action, but must provide a reason for rejection to the energy manager.

The assignee also has the ability to request more time to complete the task, and this can be reviewed by the energy manager.

If the assignee accepts the task, after completing it, they then detail what action they carried out.

Actual energy savings VALIDATION is then detailed by the assignee according to the instructions given by the energy manager when the energy manager assigned the task. This may be after a period of time or after a measurement comparison. The actual savings are detailed at this stage also.

The action is then AWAITING CLOSURE by the energy manager then reviews the action details and validation process undertaken.

If the energy manager is in agreement with the actions undertaken by the assignee, and requires no further clarification, the energy manger CLOSES the action.


page 157 of 234

Improvement Opportunity form:

Fig. 67: Improvement Opportunity creation form.

Improvement Opportunity Form (Fig. 67)


Location: Select from the list of pre-defined locations. The list of locations is configured

in the Administration section. This field is mandatory. This field will be automatically

populated if improvement opportunity is created from an SEU or other source (Sub-

Location will also be pre-populated and configured in the Administration section).

Category: Select a category for this opportunity. This list is configured in the

Administration section.




page 158 of 234

Significant Energy User: Select the related significant energy use for the list. This field

will be automatically populated if improvement opportunity is created from an SEU or

other source. You do not have to apply the opportunity to an SEU, but it is advisable.

Details: Enter any additional information about the energy saving idea.

Estimated Savings & Payback

Electrical (& Thermal) – “kWh”: Enter the estimated annual energy savings in the “kWh”

box (the energy units and currency are configurable in the Administration section.)

Electrical (& Thermal) – “€” & “kgCO2”: The annual estimated annual cost and

emissions savings are automatically calculated using the energy savings entered in the

“kWh” box (the unit cost and CO2 emission factor are configured in the Administration

section.)

Annual Co-Benefits: While the primary goal of the CASCADE project is creating a

systematic energy action system for airports with a goal of an increase in energy savings,

this in turn can bring other improvements such as increased staff awareness and

reduced maintenance costs. These additional improvements are termed co-benefits, and

may be considered when evaluating and comparing improvement opportunities and

energy saving actions.

Capital Costs: Enter the costs to implement these savings.

Estimated Payback: The payback is automatically calculated based on a simple ROI

using the annual costs savings and the capital costs.

Complexity: This allows you to enter some information on the level of difficulty in

implementing this energy saving opportunity.

Submit (button): Click on this button when you have completed entering the details for

this improvement opportunity. The Energy Manager for the location selected will be

automatically notified by email.

Suggestion form:

Fig. 68: Suggestion Form


page 159 of 234

The suggestion form can also be used to log faults which are occurring on the ground level, i.e.

faults which maintenance personnel come across on a one off basis, which are then logged in

the energy action system. Again all fields should be entered with as much information as

possible:


Details: All information detailing what kind of fault has occurred can be entered in this

section.

Name: Enter your name in this field

Email Address: Enter your Email address in this field.

Related Location: Select from the list of pre-defined locations. The list of locations is

configured in the Administration section. This field is mandatory. This field will be

automatically populated if improvement opportunity is created from an SEU or other

source.

5.4.1.1 Outputs

Energy Review/Audit:

- Action Title

- Reference No.

- Location/Sub -Location

- Category/Sub-Category of Action

- Significant Energy User (If necessary)

- Estimated Savings and Payback

- Complexity

Suggestions:

- Fault/Improvement opportunity title

- Details (All information relating to fault)

- Name of Suggestor

- Email Address of Suggestor

- Fault Location

5.4.1.2 Inputs to Action Management

All of the outputs from above will be inputted into the system as an improvement opportunity.

Quality is dependent on the competence and knowledge of the user (See Fig. 66)

Energy Review/Audit:

- Action Title

- Reference No.


- Category/Sub-Category of Action

- Significant Energy User (If necessary)

- Estimated Savings and Payback


page 160 of 234

- Complexity

Suggestions:

- Fault/Improvement opportunity title

- Details (All information relating to fault)

- Name of Suggestor

- Email Address of Suggestor

- Fault Location

5.4.1.3 Content of standard actions

The action is populated with the following information:

- Action Title

- Reference No.


- Category, Sub-Category of Action

- Significant energy user name (Name of SEU that the system belongs to)

- Action details (Outlining what needs to be carried out)

- Estimated Savings and Payback from Action

- Complexity of action (How difficult is it to carry out)

- Target Dates

- Verification Method for energy savings (Optional)

- Action Details (Outlining what has to be carries out)

- Action Details (Manually entered by assigned (Ext.M.Co or O&M) Actually carried out)


page 161 of 234

Example of action content:


page 162 of 234

Fig. 69: Improvement Opportunity - Energy Saving Action Form

5.4.1.4 Use Case

Two use case examples are described below.

1. Improvement opportunity Creation form;

2. Suggestion form.

Improvement Opportunity Creation form

An Energy Manager carries out an Energy Audit of a specific area within the terminal building.

Once the audit is complete, the Energy Managers Office input all resulting improvement

opportunities into the system using the Improvement opportunity creation form (Fig. 67). Once

they have been inputted by the Energy Manager, they are then sent to be reviewed by the

HVAC operation and Maintenance office. The energy saving actions are then assigned and

carried out by the External Maintenance Company.

This feature could also be utilised to aid the Technical Assistance Operations (TAO) in recording

energy efficiency or energy performance improvement opportunities identified as part of long

term planning, e.g. a 5yr plan.

Suggestion form


page 163 of 234

A member of staff has a comfort complaint in relation to their office being too hot/cold. The user

can log the complaint using the “Suggestion form” (Fig. 68). Similarly, this is then sent to be

reviewed by the HVAC operation and Maintenance office. The HVAC operation and

Maintenance office will then assign the action to the External Maintenance Company

(OLICAR/GEMMO) to carry out the action.

5.4.1.5 Targeted at different Users

As illustrated in Fig. 66, the following users are required to input to the Manual fault detection

action workflow:

- O&M - HVAC operation and maintenance office

The operations and maintenance department review all improvement opportunities that are

entered into the system. They are then responsible for reviewing and assigning improvement

opportunities. They are also responsible for closing actions after they have been verified.

- TAO -Technical Assistance Operations

The technical assistance operations (TAO) are involved only at the creation stage. They can

avail of this feature to log improvement opportunities which they think should be added to a 5

year plan (Long term planning).

- EMO - Energy manager office

The Energy Managers Office (EMO) is involved only at the creation stage. They can also avail of

this feature to log improvement opportunities which they think should be added to a 5 year plan

(Long term planning).

- Ext. M. Co. – Ext maintenance company

The External Maintenance Companies (OLICAR/GEMMO) are outsourced and based at the

airport. They are responsible for addressing all alarms raised by the BMS along with HVAC

scheduled and emergency maintenance actions.


page 164 of 234

5.4.2 Pre-Populated Energy Audit Items (HVAC)

Effective Operation and Maintenance is one of the most cost-effective methods for ensuring

reliability, safety, and energy efficiency. Inadequate maintenance of energy-using systems is a

major cause of energy waste. Energy losses from steam, water and air leaks, un- insulated

pipework, maladjusted or inoperable controls, and other losses from poor maintenance are quite

considerable. Good maintenance practices can generate substantial energy savings and should

be considered a resource. Moreover, improvements to facility maintenance programs can often

be accomplished immediately and at a relatively low cost.

Non-technical opportunities, for example, “Increase Staff awareness about energy consumption

of HVAC plant”, have proven themselves to be sometimes more effective for energy savings

within most sectors, in particular the vertical sectors. Such opportunities can be broadly defined

as Energy Management Best Practice, and tend to include “soft issues” such as behavioural

change arising from increased awareness, training, accountability and information systems.

The pre-populated EnMS Audit / Energy review is a feature which has been recently developed

by Enerit for other sectors, Including Schools and Hotels, and consists of lists of pre-populated

HVAC related energy saving opportunities and best practices which can be accessed and added

to action plans accordingly while carrying out an EnMS Audit/Energy review on-site. These lists

of best practices and energy saving actions will be HVAC specific, and will be pre-populated and

grouped under a number of headings, for example, Calibration/Maintenance, Management,

Controls, Design issues, heating and Cooling etc.

Depending on what area of the Airport is being Audited / Reviewed, or whether it is a member of

energy team (SEA) or someone in the Technical Assistance Operations (TAO), the lists of

Improvement opportunities from which they can choose from will be relevant to their area being

audited. For example, if someone from the Ext. M. Co is carrying out an energy review of the

Plant room, it would be possible for them to select options like “Improve insulation on Pipework”

or “Repair passing control valves”.


page 165 of 234

Fig. 70: Pre-Populated Action Workflow


page 166 of 234

5.4.2.1 Outputs from Energy Review/ Audit

The prepopulated list of improvement opportunities will give the user the option to choose the

most relevant energy saving action for a specific Sub-Location/Sub-Category. So when the user

selects an improvement opportunity from the list, the content rich action is automatically added

to the action plan.

- Action Title


Complete actions to improve HVAC systems in airports

- Action Title

- Action priority

- Reference Code (for search purposes)


- Device Name/Location (System Name)



- Estimated Savings from Action

- Verification Method for energy savings

- Action Details (Steps of what to do)

- Action Details (Manually entered by assigned (Ext.M.Co or O&M))

- Proposed Start and End Date


The action is populated with the following information:

- Action Title

- Action priority

- Reference Code (for search purposes)











page 167 of 234

Example of Pre-Populated Action content:

Action/Best Practice Title:

Insulate all Pipework

Priority:

High

____________________________________________________________________________

Reference (Code):

e.g. 0x0001

Category/Sub-Category:

HVAC, Calibration/Maintenance

Significant Energy User (SEU):

HVAC

Action Details:

Estimated Savings and Payback/Complexity (Estimated Savings Pre-populated):

PLANNED:

ASSIGNED:

Include in Action Plan:

Target Dates are set/Action details filled out:


page 168 of 234

Enter Action details:

For validation

Enter actual savings:

Awaiting Closure

Were actions carried out as originally expected? (O&M):

Close

5.4.2.4 Use Case

5.4.2.5 Member of Operation and Maintenance team want to carry out a scheduled

energy review of the terminal. A list of prepopulated/relevant improvement

opportunities and best practices will be available for the user to view, making it

easy for them to select the most appropriate ones.

Further to this, the lists of best practices will be specific to the user. This makes it easier for the

user to select different improvement opportunities which are appropriate to the different areas.

For example;

User is carrying out an energy review of the Plant room, and sees that the ductwork is not

insulated. He can see from the list of best practices under the heading “Calibration/Maintenance-

Plant room” that “All supply ducts must be insulated”. The user is then given a reason as to why

this is necessary, for example, “Ducts that leak heated air into unheated spaces can add

hundreds of euro a year to your heating and cooling bills. Insulating ducts in unconditioned

spaces is extremely cost-effective. If you are installing a new duct system, make sure it comes

with insulation”. If the user then wants to add this to the Action plan they select “Create action”

(See Fig. 71) and a prepopulated action is sent to be reviewed by the HVAC Operation and

Maintenance department and assigned to external maintenance company, before following the

workflow in Fig. 70.


page 169 of 234

Fig. 71: Example of pre-populated action form


As illustrated in Fig. 70, the following users are required to input to the pre-populated action

workflow:


The operations and maintenance department are responsible for reviewing all the energy saving

actions once they are in the system. They then assign to the external maintenance company or

if it is possible to carry out the action using the BMS, the O&M deal with it directly.


The technical assistance operations (TAO) give permission to carry out any extra-ordinary

actions based on cost (if action cannot be carried out as part of the maintenance contract).


Energy Managers office is also involved when extra-ordinary actions have to be considered.

They can also avail of this feature to log improvement opportunities which they think should be

added to a 5 year plan (Long term planning).


The External Maintenance Companies (OLICAR/GEMMO) are assigned all actions which cannot

be carried out using the BMS along with any HVAC scheduled and emergency maintenance

actions.


page 170 of 234

5.4.3 Fault detection diagnosis Alarms (FDD)

Fig. 73 below explains the process which occurs from when an FDD signal (JSON xml File) is

received by the Enerit agent, right through to when a Content Rich action is ASSIGNED.

Fig. 72: Enerit Agent

Fig. 73: Enerit Agent (In text)

Input •Outputs from the FDD (Datastorage) produce a JSON XML file from ISE/SMI FDD signals, which

will be transferred via ftp to a directory on Enerits server.

Stage 1

•Agent Reads JSON xml.

•The Enerit agent reads the XML files from the ftp target directory and will update every 1 / 2 hours (up for change).

Stage 2

•Queries Airport Ontology (area/location).

•Based on the faultInfo information(received through xml file), the agent then queries the airport Ontology .OWL file for a more complete set of information.

Stage 3

•Queries Action Database

•Once both the Fault Info and Device info has been received, the Agent will then query the action database (Enerit database) which provides rich content information on actions.

Stage 4

•"Content Rich Action" sent to Management system

•The Enerit Agent can then combine all this Action Information, Assignee information etc. to produce a “content rich” action.


page 171 of 234

Fig. 74: Workflow for FDD


page 172 of 234

Once the Content rich action is sent to Management system, it is sent straight for REVIEW by

O&M:

1. FDD signal is received in JSON file format from ISE/SMI.

2. Enerit Agent builds action using ontology and Enerit action database (As seen above).

3. Once an FDD action has been created, the Operation and Maintenance (O&M) Department are notified and actions are reviewed (FOR REVIEW).

4. Once O&M have reviewed the FDD action, they can then include it in the action plan (PLANNED), CLOSED it or place it in ON-HOLD.

5. O&M then check whether the action can be resolved using the BMS. - If yes;

Completion date is set. Once action is carried out, details are entered by O&M. Go to 10.

- If no; Action must be assigned to External Maintenance Company (Ext. M. Co.) O&M selects target completion date. Go to 6

6. If the Ext. M. Co. decide that it is not their duty to carry out the task, they can REJECT the task and the action is then sent back FOR REVIEW.

7. If the Ext. M. Co. decide to carry out the task, they also have the ability to request more time to complete the task, and this can be reviewed by the O&M.

8. Member of Ext. M. Co is sent directly to assess/review the action. 9. Ext. M. Co. check to see if the action can be carried out as part of the maintenance

contract. - If yes;

Action is carried out and detailed. - If no;

The energy management office (EMO) / Technical assistance office (TAO) must authorise the action to be carried out and agree the excess cost proposed by Ext. M. Co.

Once agreed, Action is carried out and detailed. 10. Enter actual energy savings (Use estimated savings from FDD or enter manually). If

manually entering energy savings, it may be after a period of time or after a measurement comparison (FOR VALIDATION).

11. The action is then AWAITING CLOSURE by the O&M, where they review the action details and validation process undertaken.

12. If the O&M is in agreement with the actions undertaken by themselves / the Ext. M. Co, and requires no further clarification, the O&M CLOSES the action.

5.4.3.1 Outputs from FDD

In the JSON file from ISE or SMI the following will be provided:

- Code (e.g. 0x0001)

- Fault title (Fault Description)

Key:O&M - HVAC operation and maintenance office TAO -Technical Assistance OperationsEMO - Energy manager officeExt. M. Co. – Ext maintenance company


page 173 of 234

- Action Title

- “Fault detection method based on”

- Action priority


- Location

- Cost (e.g. Low/No Cost)

- Trends/Plots and data from ISE datastorage and SMI



All of the outputs from the FDD above will be parsed by the Enerit Agent and then utilised to

build a content rich action.

The Ontology will provide:

- Name of Measurement Device

- Device Name (System Name)

- Component Name

- Location

The information in the Ontology will override the outputs from FDD if there is duplication (i.e. if

the “Location” is available from both sources).

Enerit Actions database will provide:

- Category, Sub-category of Action

- Action priority

- Action Title


- Technical data sheet for component/system (PDF files of O&M Manuals)





Similarly, the information in the Enerit database will override the outputs from FDD and Ontology

if there is duplication (i.e. if the “Action Title” is available from both sources).

Other inputs include the entry of action details and decisions made by O&M department, Ext. M.

Co., TAO and the EMO. See Fig. 74 for FDD workflow.

5.4.3.3 Contents of standard actions

However, the action will be populated with information on:

- Action Title

- Action priority



page 174 of 234

- Code (e.g. 0x0001)




- Component Name

- Trends and data from ISE/SMI datastorage









page 175 of 234

Example of action content:

Action Title:

Go and assess Device/System A for Simultaneous Heating and Cooling

Priority:

High

____________________________________________________________________________

Fault title/description:

Simultaneous heating and cooling

Reference (Code):

e.g. 0x0001

Device/Location:

In device/System A at location X near to ….

Category/Sub-Category:

HVAC, Calibration/Maintenance

Significant Energy User (SEU):

HVAC

Component name (??):

Cooling coil

Trends and data from ISE datastorage (Or Link to datastorage tool):

May not be provided with the action, but can be accessed through an accompanying link.

*Technical data sheet for component/system:

Same as Trends/Data from ISE, may not be provided with the action, but can be accessed through an

accompanying link.

Estimated Savings and Payback/Complexity:


page 176 of 234

If it is possible to carry out action using the BMS:

PLANNED:

ASSIGNED:

Can action be resolved using the BMS?:

Yes X No

Target Dates are set/Action details filled out:

For validation

(Use estimated savings from FDD or enters manually)

Use estimated Savings from FDD:

Yes x No


Awaiting Closure



page 177 of 234

Close

If it is not possible to carry out the action using the BMS:

PLANNED:

ASSIGNED:

Can action be resolved using the BMS?:

Yes No X

ASSIGNED:

Target Dates/Verification Method/Please follow the steps below to assess/correct the fault:

Rejected Wrong person Option: (Goes back to REVIEW stage) OR

Accept (Someone sent to carry out action):

Please Enter Details of Action Carried out (by either O&M or Ext. Maintenance Company):

For validation

(Use estimated savings from FDD or enters manually)

Note: Actual savings will default to estimated savings from FDD, but the user will have the option to manually

change the figures with entering manually.



page 178 of 234

Awaiting Closure


Close


As illustrated in Fig. 19, only the following users are required to input to the FDD action workflow:













actions.


page 179 of 234

5.4.4 BMS Alarms

The BMS/SCADA alarms workflow which can be seen In Fig. 75 below:

Fig. 75: BMS/SCADA Alarm Workflow


page 180 of 234

For the grouped BMS/Scada alarms action workflow, the steps are almost identical to the FDD

workflow as shown in Fig. 74. Alarms are grouped and processed by ISE/SMI, and picked up by

the Enerit energy Action system (EAS) and follow the same steps 1-12 as described above with

the exception of Step no. 10. For the FDD action, estimated energy savings are calculated by

the datastorage tool but are not available for grouped BMS alarms.

5.4.4.1 Outputs from BMS via Datastorage tool

The following list of outputs will be provided by the ISE/SMI data storage tool after the multiple

alarms are grouped and processed:

- Code (e.g. 0x0001)


- Action Title

- Action priority


- Location

- Cost (e.g. Low/No Cost)


All of the outputs from the data storage tool above will be parsed by the Enerit Agent and then

utilised to build a content rich action.

The Ontology will provide:

- Name of Measurement Device

- Device Name (System Name)

- Component Name

- Location

The information in the Ontology will override the outputs from the datastorage tool if there is

duplication.

Enerit Actions database will provide:

- Category, Sub-category of Action

- Action priority

- Action Title






Key:O&M - HVAC operation and maintenance office TAO -Technical Assistance OperationsEMO - Energy manager officeExt. M. Co. – Ext maintenance company


page 181 of 234


Similarly, the information in the Enerit database will override the outputs from the datastorage

tool and Ontology if there is duplication (i.e. if the “Action Title” is available from both sources).

Other inputs include the entry of action details and decisions made by O&M department, Ext. M.

Co., TAO and the EMO. See Fig. 75 for BMS/Scada alarm workflow.


However, the action will be populated with information on:

- Action Title

- Action priority


- Code (e.g. 0x0001)




- Component Name

- Trends and data from ISE/SMI datastorage








See “Example of action content:” for FDD actions.


As illustrated in Fig. 75, only the following users are required to input to the BMS/Scada alarm

workflow:










page 182 of 234


They can also avail of this feature to log improvement opportunities which they think should be

added to a 5 year plan (Long term planning).




actions.


page 183 of 234

5.5 CASCADE Action Management and Tracking

Enerit ISO 50001 software will manage all energy saving actions through its online portal,

making sure all actions are brought through the workflows and carried out correctly and within

the set target dates. Detailed examples of improvement opportunities are explained in detail in

the previous section (CASCADE Energy Action System (EAS)):

1. Improvement Opportunities/Suggestions (Manual FDD); 2. Pre-populated list (through EnMS Audit/Energy Review); 3. Fault Detection Diagnosis alarms (JSON file received from ISE/SMI) and; 4. Grouped SCADA alarms (filtered/grouped SCADA/BMS Alarms from ISE/SMI)).

Fig. 67 in the previous section illustrates the current Improvement Opportunity form in Enerit ISO

50001 software. Information can be recorded about the opportunity, such as, the improvement

title, an applicable location, a category for the opportunity, the significant energy user that it can

be associated with, details of the required action and estimated savings and payback.

Fig. 76 shows an action plan in the Enerit software. The Action Plan view in the Enerit ISO

50001 software gives details on the assigned person, the start and target date for the task

completion. The plan itself is comprised of all planned actions associated with different

categories, assigned people, locations, etc. The status of each action can be monitored and

overdue actions are highlighted with a red indicator. Actions on time are indicated with a green

icon, closed actions are indicated with a blue icon, and actions yet to be assigned with a ‘?’

symbol.


page 184 of 234

Fig. 76: 'Action Plans' view in Enerit ISO 50001 software.

All of these actions can be sorted in numerous ways. For example, by using the sorting functions,

actions can be sorted by assigned person (Fig. 77) i.e. this is an action which has been

assigned to “Celine Louchard”. It is also possible to sort by Significant Energy User, Category,

Location, All Open, All Closed depending on user preference.

Fig. 77: Actions sorted by Assigned Person

When sorting by Location, the user can view all actions within a certain area. As you can see in

Fig. 78 below, if you hover over the Icons on the right, the user can see what status the action is

currently at (i.e. “Install PIR s on lighting” is AWAITING CLOSURE.)

Fig. 78: Actions sorted by Location

By clicking on a particular action in the list (e.g. “Increase staff awareness about energy

consumption”) the particular action and all of its details can be viewed.

Corrective Actions

When particular BMS/Scada alarm related actions occur at a certain frequency over a certain

period of time, it may be necessary to trigger a corrective action to deal with the underlying

problem (e.g. a sensor that is not communicating with the BMS). As BMS/Scada occur they are


page 185 of 234

counted by data storage tool (ISE/SMI), if certain actions are to occur frequently for a given

system, a corrective action can be triggered through the Enerit Software.

Action Escalation Reminder

To ensure actions move efficiently through workflow, escalation of some actions may be

necessary. There will be 2 scenarios of escalation procedures, one for Fault Detection

Diagnosis/ BMS/Scada Alarms and another for the Manual FDD and the Pre-Populated

improvement opportunities.

Who has to be notified?

Escalation reporting Structure:

Start: Assignee (Action Owner)

1st Escalation: Assignee’s Manager (TAO)

Consecutive Escalation: Follow Organizational Structure in place – (Assignee, TAO ,EMO)

Below is an example of how the escalation process can be applied. This can be further

expanded to include Medium and Low priority actions also.

HIGH Priority Action

Escalation Cycle for BMS/SCADA Alarms, FDD. Max days to complete Task

Reminder Notification before escalation

1

st Esc.

Consecutive Esc

No. of days before escalation

Review = 6 2 1 &1

Plan = 6 2 1 &1

Assign = 20 10 1 &1

Validation (40 day time Lock)

8 3 2 & 1

Awaiting Closure = 8 3 2 & 1

For Clarification = 2 2 1 &1

Review / CLOSE = 5 4 2 & 1


page 186 of 234

5.5.1 Energy Action Reporting

The action reports Dashboard, Fig. 79, is configurable and includes a number of charts. The

charts are interactive and are linked to the Actions and SEUs. Take the example below, where if

the dashboard is opened the ‘Energy Savings Opportunities by category’ chart can be made

larger (Fig. 80).

Fig. 79: Reports 'Dashboard' view in Enerit ISO 50001 software.

Fig. 80: Interactive Report Chart of Energy saving Opportunities by Category.

Next by clicking on the ‘Refrigeration’ category which has 24 improvement opportunities the

chart detailing the sub-categories appears, Fig. 81.


page 187 of 234

Fig. 81: Interactive Report Chart of Energy saving Opportunities by Sub-Category (Drilled down).

By clicking on the ‘Chiller Sequencing’ sub-category the list of 3 improvement opportunities

applicable to that sub-category are shown, Fig. 82. Each of these is linked to an improvement

opportunity document.

Fig. 82: Energy Saving Opportunities linked to the Category/Sub-Category in the interactive charts.

During Task 5.3 “Reports to influence organizational and behavioural improvement” in WP5,

reports (such as those described in this section), graphs, dashboards, and visualisation tools will

be developed that communicate CASCADE results across the performance metrics identified in

WP1.


page 188 of 234

5.5.2 Specific Charts for different users

They key to a successful energy management system is to have good reporting, by providing the

users with the information they want to see in the most concise way possible. Within the Enerit

system, action reports will track the progress of individual locations/systems/assignees/SEU’s

across the entire HVAC system.

As part of the CASCADE project a number of charts will be developed in Task 5.3, which are

specific to the needs of different user types. (Operations and Maintenance, External

Maintenance Company, Energy Managers Office, Technical Assistant Operations)

1. Operation and Maintenance

a) Action Charts:

- Priority of Actions by Type

o OPEN

o CLOSED

- Number of actions per Category

o Number of OPEN actions per Category

o Number of CLOSED actions per Category

o Number of ON-HOLD actions per Category

o Number of REVIEW actions per Category

- Number of actions per Assignee

o Number of OPEN actions per assignee

o Number of CLOSED actions per assignee

b) Fault lists:

o Number of Faults per Category

o Number of Faults per Location

c) Energy, CO2, Cost (€) Charts

- Total Actual savings from energy saving actions by Sub-Category / (€, kWh, tCO2)

- Total Actual savings from energy saving actions by Location / (€, kWh, tCO2)

2. External maintenance Company (Ext. M. Co)

a) Action Charts:





page 189 of 234


o OPEN

o CLOSED

3. Energy Management office (EMO)

a) Action Charts:


o OPEN

o CLOSED


o OPEN

o CLOSED

o FOR REVIEW




b) Energy, CO2, Cost (€) Charts

- Total Estimated savings from improvement opportunities by Sub-Category / (€,kWh,

tCO2), (Per month if possible as ADR already track monthly energy savings)


- Total Actual savings from energy saving actions by Location / (€, kWh, tCO2)

23

34

45

64 22

34

24

44

22

Energy Saving Opportunites by Category Management

Ancillary Equipment

Heating and Cooling

Schedule Optimisation

Waste Heat Recovery

Energy service requirments:

Controls

Design Issues

Calibration / Maintenance

Energy Saving Opportunites by status

Open

Closed


page 190 of 234

4. Technical Assistance Operations (TAO)

a) Action Charts:


o OPEN

o CLOSED




o Number of ON-HOLD actions per Category

o Number of REVIEW actions per Category




- Number of Actions outside Maintenance Contract Per Category (to keep track of Extra-

Ord Actions, as it is their duty to sign them off)

b) Energy, CO2, Cost (€) Charts

- Total Estimated savings from improvement opportunities by Sub-Category / (€,kWh,

tCO2)



page 191 of 234

6 CASCADE Implementation Kit

The CASCADE Implementation Kit covers the fundamental processes of the whole system

development lifecycle. It’s been conceived as a formalized approach for the design,

implementation and delivery of CASCADE in any airport or other-like facility. Consequently, it will

learn from the experience of the two pilot implementation (Fiumicino and Malpensa airports) and

will evolve with the project. Within this deliverable the lesson learned apply to initiating phase

that has been verified and reshaped again after the survey experience (6.2.1). With the 3 years

progress of the project all the proposed phases will be updated according to the lesson learned

and documented in the replication plan. The ultimate and broader vision of the project is to

establish a comprehensive protocol serving the entire stakeholders interests and expectation. A

methodology for CASCADE implementation will serve fundamentally for:

Providing a framework for the replication and exploitation phase;

Improving the overall quality of the project, enhancing user experience;

Identifying and managing risks, increasing probabilities of success;

Defining means of measuring project performance.

Due to the multi-faceted nature of CASCADE, the proposed methodology is based on a

combination of current best practices and standards in the fields of Systems Analysis and

Development, Software Design Methodologies and Project Management. Computer Science is

constantly in evolution, CASCADE methodology will take sound principles and common used

practices that persist regardless of the plethora of IT paradigms and models that continuously

arise, allowing for further flexibility and keeping a basic core structure.

CASCADE Implementation Methodology is constructed around

processes and inspired in the Project Management Body of

Knowledge (PMBOK) under the standard ANSI/PMI 99-001-200 or

IEEE 1490-2011 (Project Management Institute, Inc., 2008).

Processes are defined as a set of operations performed towards

specific objectives. Processes are better characterised as shown in

Fig. 84, by their Inputs, Outputs, Tools and Techniques.

This methodology leverages the core components of a traditional

“waterfall”15 project approach, combined with iterative processes to

provide the benefits of a more “agile16” method. This combination

15 Waterfall refers to a sequential design process used in IT development in which every phase depends

highly in completion of the previous phase. Changes and evolution are difficult to integrate during the

project using this methodology.

16 Agile is a software development method that is based in incremental and iterative processes, embracing

change and delivering working software in evolving cycles.

Fig. 83 The PMBOK


page 192 of 234

enables the rapid design, development and deployment of highly scalable and flexible enterprise

solutions. During all phases of implementation, the CASCADE team works closely with the

airport team deliver clearly defined project objectives and solution requirements.

Fig. 84 Inputs / Outputs / Tools&Techniques for a process

Inputs refers to any specific item, product, document or external requirement that can (and in

most cases must), be used to trigger the execution of a particular process. Inputs can result from

external processes or work results or derive internally as output/results from other CASCADE

processes. Output refers specifically to any particular services, results, and or products that are

generated as a result of a particular project related process. Tools and techniques are

systematic, standardised, agreed upon and commonly used procedures aimed to produce the

desired result.

Processes are grouped according to phases. CASCADE Implementation Kit spread along four

phases, or processes group: Initiation, Planning, Implementation and Commissioning.

Before describing the different elements of the Implementation Kit, some assumptions should be

made clear:

A CASCADE Team exists, and operates to execute a specific implementation;

Airports or other like facilities provide access to information;

A system request is formally issued by the targeted facility;

Stakeholders are declared and defined in terms of impact in CASCADE.

Another group of processes, the Monitoring and Controlling phase, takes place during the

execution and commissioning phase, affecting and updating the planning phase. An

overview of the CASCADE Implementation Toolkit is shown in Fig. 85.


page 193 of 234

Fig. 85 Overview of the CASCADE Implementation Toolkit

6.1 CASCADE Implementation Timeline

CASCADE phases are typically completed sequentially, but can overlap in some project

situations. Project phases are divisions within a project where extra control is needed to

effectively manage the completion of a major deliverable. Generally a project phase is

concluded with a review of the deliverables to determine completeness and acceptance.

CASCADE will follow a classic four phases sequential structure as described in Fig. 86. The

Initiating, Planning, Implementation and Commissioning develop on a successive flow, while the

Monitoring and Controlling Phase involve iterative activities that take place during the Planning-

Implementation-Commissioning cycle. Monitoring and Controlling processes are of critical

importance during the project pilot phase, where continuous refining and adjusting actions occur

to finally deliver the final commission of the CASCADE implementation.


page 194 of 234

Fig. 86 CASCADE Lifecycle

6.2 The Initiation phase

This is an analytical stage of the project, in this phase, information is collected, filtered, analysed

and evaluated using different techniques. In CASCADE the purpose of this stage is to

understand the targeted Airport with regards to energy management (the As Is system), and

represent both the physical and organisational spheres. The motivation is to clearly specify what

is the potential for the implementation of CASCADE, how it can be achieved, and what are the

necessary resources to implement the new system (the To Be system).

6.2.1 CASCADE Survey experience

During the first months of the project as part of the data gathering process the CASCADE

consortium elaborated a detailed survey template. The main initial objectives of the survey were:

To identify energy management procedures and responsibilities in the airports organisations

(SEA and ADR);

To identify and describe Milan MXP and Rome FCO airports operation;

To document and characterise ICT and HVAC systems operating at Milan MXP and Rome

FCO.

The survey template, which is fully documented in ANNEX 1. CASCADE detailed airport

survey template , follows the structure of the energy management standard ISO 50001 and it is

divided according to its main headings in the following seven sections:

General Requirements

Management Responsibility

Energy Policy

Energy Planning

Implementation & Operation

Checking


page 195 of 234

Management Review

The completion of the survey required several meetings between NUI Galway staff (responsible

for this subtask) and the airports staff to support this large information gathering process. The

main outcomes of several iterations were multiple and can be summarised as follow:

The survey allowed identifying how the airports organisations are conducting the

energy management in relation to the ISO 50001 standard and also on how the

CASCADE solution could be used to support the standard implementation in a

systematic manner.

As a direct outcome of all the meetings required to fill the survey template, it was

possible to initiate iterative process between the partners in the consortium to both

identify airports requirements and to explain and present to the airports the

technological partners solutions

Airports management companies are large organisations and the information

gathering process was easier when a direct contact with the right person was made,

the difficulty was to identify the right person within the organisation that could

support in a specific information required. This is because the survey is very detailed

and covers many different aspects (e.g. from awareness campaign management to

security for data transfer to HVAC systems component, layout and technical

specification) It is likely to expect that employees of the airport staff will not be

familiar with all the topics covered by the survey.

Another important issue is that technical data is very often fragmented and

scattered over the different airport services and thus difficult to retrieve. CASCADE

will try to answer this issue by taking advantage of the ontology layer implementation

at airports in which all airport static technical data will be gathered enabling an

efficient, centralised and permanent fast access to data.

Airports management companies are under time and cost pressure and need simple

and targeted requests. The CASCADE project dedicated personal at airports needed

to be intensively supported during the survey phase to gather all information

requested in the survey template. Also, some question of the survey were related to

research works and were very specific and new for airports thus requiring additional

time and resources to be answered properly by the airports. From our experience at

both pilot airports, we learned that a methodical, iterative and continuous support is

necessary to ensure high qualitative survey process results.

Airports are strategic infrastructures in which security and information confidentiality

are essential. It impacts directly on the information collection processespecially on

the ease of access and the number of approvals required, the amount and the level

of detail of the documents. Even for on-site surveys a long process of identification

and criminal record check needs to be carried out each time when accessing the

airside of the airport, specific passes are required to visit the plant rooms, take

pictures and bring working tools.


page 196 of 234

As any building it was not easy to gather design technical documentation and as-built.

Considering that airports are infrastructures subject to continuous changes, with the

addition and therefore it is also not easy to gather up to date documentation.

Given these main points it is important to underline that this survey was a great experience and

a learning process for the whole consortium which resulted in a very detailed set of

documentation for both pilots and gave important inputs for the CASCADE solution definition.

That said, it is also important to remark that for replication purposes the survey has been split in

a subset of specific key documents that allows the documentation of specific details necessary

for project implementation. This are described as processes in Sections 6.2.2, 6.2.3 and 6.2.4.

Fig. 87 From WP1 to CASCADE Implementation Toolkit


page 197 of 234

6.2.2 CASCADE Energy Audit

The final CASCADE template for energy audit is the one reported in Chapter2.

6.2.3 CASCADE BMS / IT Assessment

This process is targeted specifically the state of BMS and IT facilities in the requesting

organisation. More details on this can be found in D3.1.


page 198 of 234

6.2.4 CASCADE Organisational Factors Assessment. (OFA)

This process refers to the analysis of what is commonly described as Enterprise Environmental

Factors17 (Project Management Institute, Inc., 2008). These are the factors that sorround or

influence CASCADE’s implementation, including but not limiting to:

Organisational Culture and Strategic Goals

Government or Industry Standards

Operations and Maintenance practices, contracts etc.

Marketplace conditions, political and economical climate (energy prices)

Commercial databases (suppliers, vendors, etc), local price index databases

Fig. 88 The Organisational Factors Assessment (OFA) Process

6.3 The Planning phase

The Planning Phase involves the creation of the CASCADE Project charter, which is the

foundational document of the CASCADE Implementation. This phase consist of those processes

performed to establish the total scope of the effort, define and refine the objectives and develop

17 Here the term “Environmental” have been substituted by “Organisational” to avoid confusion as in

Project Management it does not means “Natural Environment”


page 199 of 234

the course of actions required to attain those objectives. Where significant changes occur

through the project lifecycle, this will trigger a need to revisit one or more of the planning

processes. This progressive detailing of the Planning phase can be defined as a “rolling wave

planning” to indicate that planning, documentation and execution of works are iterative and on-

going processes. Traditional Project Management processes have been gathered and grouped

into a single process called “Project Management Plan”, with the aim of not overextend this

section with specific PM-related information and keep the Implementation Kit closely linked to

CASCADE objectives.

During this phase, CASCADE team will work closely with the client to complete the scoping and

planning required to deliver a cohesive solution in the required timeframe. CASCADE will

confirm our understanding of the detailed requirements and draft designs for the functional,

technical, configuration, integration, data conversion, testing, training, and deployment

requirements. During this step, CASCADE will also produce and validate the timing, effort, and

cost estimates required to complete the project, prior to initiating full-scale development activities.

CASCADE will pay special attention to cost estimations regarding sensors and hardware

equipment as it represents a significant part of the budget. Cost-benefit analysis described in

Section 3.5.1: “Selection Methods based in cost effectiveness” is suggested as an approach to

be used in this phase, and also to comply with ISO 50001 requirement of KPI selection

methodology and quality assessment of KPI effectiveness. The planning phase concludes when

the client provides sign-off on the solution design documentation and Implementation Work Plan.

This activity is currently on-going in the project.

6.3.1 The CASCADE Project Charter

The project charter is a document that formally authorizes the CASCADE project and documents

initial requirements and identify high level stakeholders needs and expectations, establishing a

partnership between the performing organisation (CASCADE implementer) and the requesting

organisation (the Airport).


page 200 of 234

Fig. 89 The CASCADE Project Charter Process

The Input for this process will be the outcomes of the Initiation Phase, these are the CASCADE

Energy Audit, the CASCADE BMS/ICT Assessment and the CASCADE OFA (Organisational

Factors Assessment)

Expert Judgement18 and Negotiations will be the main tools to conduct this process.

The output will be the CASCADE Project Charter, that will define a minimum of high level

objectives leading to a Project Approval, and subsequently to the development of the Project

Management Plan.

18 Expert Judgment is a term that refers a specifically to a technique in which judgment is made based

upon a specific set of criteria and/or expertise that has been acquired in a specific knowledge area, or

product area, a particular discipline, an industry or any field of knowledge. (Project Management Institute,

Inc., 2008)


page 201 of 234

6.3.2 The CASCADE Project Management Plan

The Inputs for this process are the Outputs of the Initiation Phase + The Cascade Project

Charter.

The Project Management Plan is a common effort of the CASCADE team, and will require use of

Expert judgement and Negotiations.

The Outputs for the Project Management Plan These documents form the CASCADE contract

and This will eventually lead to a binding contractual agreement and the final Sign-Off of the

project.

6.4 The Implementation Phase

The Implementation phase comprise the processes performed to execute the work defined in

the Project Management Plan to satisfy project specification. Executing the work involves

coordination of people, resources internally or outsourced to external vendors or subcontractors.

During project execution, results may require planning updates and re-baselining the project,

involving changes to activity durations, changes in resource productivity or assessing the impact

of unexpected risks. The results of the analysis may conclude with changes in the Project

Management Plan (Planning Phase), and the development of appropriate responses. Change

requests should be integrated in the implementation phase with a formal procedure, or

“Integrated Change Control”.


page 202 of 234

6.4.1 Conduct Procurements

6.4.2 Execute Project Work

Physical Layer:

Network Layer: During this step, the CASCADE team will work to integrate the solution

with all other systems that define the client’s overall integrated solution. These could be

legacy systems or new systems that are part of the targeted solution.

Software development During this step, CASCADE team will configure specific business

modules to meet the client’s specific requirements. The resulting CASCADE

configuration will be deployed in multiple “build cycles” to provide a working model of the

configured solution, allowing for incremental progress and testing throughout the project.

This step will also include all work related to setting up development and integration

environments at the client’s location.


page 203 of 234

o Software Analysis

o Use-Case Modelling

o User Stories and Epics

o Develop Structural Model

o Develop Behavioural Model

o Software Design

6.5 The Commissioning Phase

This phase consist in a group of processes performed to finalize activities across all previous

phases to formally deliver the CASCADE implementation in operation to final users. In the

Commissioning phase CASCADE differentiate two separate situations:

A Pilot period: In this period, CASCADE will be delivered in the airport facility, Users will

be trained and an Energy Management Plan will be established. Results on the

implementation will lead to further refining / adaptation of the initial solution. Monitoring

and controlling activities will play a vital role in this stage, especially those related to

testing CASCADE performance.

A Final Commission: After the Pilot trial period expires, CASCADE will be

commissioned to the final user. A specific contractual framework will systematise

CASCADE stakeholders with the required rights and obligations and CASCADE will be

integrated as an going commissioning tool within the facility operation. A final CASCADE

results report will be

Deployment activities affect different project processes due to the simultaneous effect of the

Monitoring and Controlling activities and multiple testing processes: Integrated Testing, Data

Conversion Testing, Performance Testing, User Testing, and Production. Deployment activities

are iterative throughout the build cycles, and involve knowledge transfer to client / third party

resources.


page 204 of 234

6.5.1 Project Pilot Trial

6.5.2 Users Training

Training is delivered during the commissioning phase, initial Technical Training and Functional

Training sessions will be designed and tailored to meet specific stakeholder’s need. Training

activities have the following specific objectives

To familiarize members of the client project team with CASCADE terminology, tools, and

“out of the box” functionality.

Provide Energy Managers, O&M personnel with advanced Technical Training, especially

for those who will be participating in the Configuration, Integration and/or Data

Conversion activities.


page 205 of 234

6.5.3 Implement Energy Action Plan

This process focus on the implementation of ISO 50001 energy management plan. For doing

this, the cited standard provide a full pathway and CASCADE Energy Management Tool will

support standardised methodology.

6.6 The Monitoring and Controlling Phase

The Monitoring and Controlling Phase consists of those processes required to review, track and

regulate the progress and performance of project activities. another important objective is to

identify any area where changes to the project may be required, documenting the changes and

implementing them. Project performance is observed, measured regularly and consistently in

order to identify variances from the previously approved Project Management Plan. The

International Performance Measurement and Verification Protocol (IPMVP) will be adopted to

perform assessment of energy savings, thus the effectiveness of the CASCADE solution.

A continuous monitoring effort will provide an insight about the status of the project, coordinating

other processes and triggering preventive and corrective actions to bring the project into

compliance with the Project Management Plan.


page 206 of 234

6.6.1 Monitoring and Controlling CASCADE EXECUTION

This process involves tracking, reviewing and regulating the project progress to meet

performance objectives defined in the project management plan. Monitoring includes status

reporting, progress measurement and forecasting. Performance reports provide information on

the project’s performance with regard to scope, schedule, cost, resources, quality and risk.

6.6.2 Testing CASCADE performance. (Technical Implementation)

This connects with the Validation Plan, explained in detail in D2.2.

Functional Testing: This type of test is performed to prove effectiveness of functional

specifications and is a part of the development process. Test case specifications are

normally designed along the design process (Test driven development), and are aimed to


page 207 of 234

prove an intended system behaviour. These are commonly called “specification-based

test” or “black-box test”

Integration Testing and Architecture Performance: CASCADE will test the

performance of the solution One standardised approach for this is the ARM Applications

Response Measurement, an open standard for monitoring and diagnosing performance

of complex networks and enterprise systems architectures that base their design in

loosely coupled systems and Service Oriented Architecture.

Performance Tuning

Performance tuning is targeted at Databases Administration and Development part of the

CASCADE solution, especially for those based in SQL language. There are several tools

to measure health and performance of servers.

o Index analysis and Extremely Effective Index Created

o Server/Instance Level Configuration Check

o I/O distribution Analysis Performance

Testing USER Acceptance. (UAT)

This test is conducted to determine if stakeholders requirements, specifications or

contract requirements are met. This test are commonly used prior to accept transfer of

ownership (final commission of CASCADE after pilot stage is finished)

Testing FDD Quality Assurance: An effective evaluation method for FDD protocols

should be developed. For energy managers, evaluation of FDD will serve to select

servicing options with knowledge of the effectiveness that is expected. For FDD

developers to understand where FDD algorithms succeed or fail and establish thresholds

and criteria for assessment of success.

Post Project Review and LESSONS LEARNED (LL)

This type of report is produced near the completion of the project, and will summarise the

experience earned in the project. The ultimate purpose of documented LL is to provide

CASCADE with useful information that can increase effectiveness and efficiency and

building on the experience that has been gained by the pilot implementation.


page 208 of 234


page 209 of 234

7 Conclusion

In this report we have described the development of the CASCADE methodology and the

preparation for its exploitation phase. We have defined CASCADE energy audit as part of the

methodology background work which as conducted an extensive literature review on energy

audit methodologies and approaches (Section 2). We have defined the CASCADE Key

Performance Indicators at different tiers that allow assessing the impact of ECOs and the

CASCADE solution on energy, comfort and maintenance performance (Section 3). Starting from

end user requirements (D1.1) and technology solutions available within the consortium (Section

3) we have defined the CASCADE solution which focuses on 5 aspects (Section 5):

Performance monitoring of selected zones and systems;

Automated Fault Detection and Diagnosis based on measured performance data;

Assessment of service-level agreement with maintenance contractors on the selected

systems and subsystems and support of performance based maintenance;

Energy action management and tracking;

CO2 and energy savings accountancy in accordance with ISO50001 standard and

IPMVP Measurement and Verification Protocol.

Other aspects covered in Section 5 are the CASCADE solution architecture, definition of the end

users roles and action management system and workflow according to ISO 50001. The part on

the CASCADE architecture includes and documents work carried out within Task 5.1 (Integrating

FDD, ISO, and Energy Management Systems) which is still on-going.

Finally section 6 focuses on the construction of a methodology for the effective implementation

of CASCADE. Different processes of the CASCADE methodology have been defined, as well as

the related input, output and tools/techniques for each one of them. It is important to remark that

the work presented here is part of a WP which is on-going for the whole length of the project and

will be revised during the solution implementation at the 2 pilots and will be incorporated in the

replication plan final report. This review/update process will start form the basis defined within

this deliverable and will be completed with the lessons learned from the real implementation at

both Milan Malpensa airport Terminal 1 and Rome Fiumicino airport Terminal 1. The current

version of the methodology described in this deliverable has been already updated to capture

lesson learned within the initiating phase which is the only one fully completed.

The final result will be a detailed implementation toolkit, accompanied by appropriate templates

for cascade deployment which will support the Framework and Methodology to implement

CASCADE as an approach across all 500 EU airports and like environments. To this effect,

targeted outreach will be conducted in the appropriate WP (WP7).


page 210 of 234

Acknowledgement

The research leading to these results has received funding from the European Community's

Seventh Framework Programme (FP7/2007-2013) under grant agreement No. FP7-2011-NMP-

ENV-ENERGY-ICT-EeB 284920.

Furthermore, information on the supporting program and like projects can be found at the

homepage for the ICT Group for Sustainable Growth:ec.europa.eu/ictforsg


page 211 of 234

8 References

ASHRAE. 2010. ASHRAE 90.1 Standard. Energy Standard for Buildings Except Low-Rise

Residential Buildings. Atlanta. US : ASHRAE Publications, 2010.

—. 2010. ASHRAE Handbook for HVAC applications. Atlanta : ASHRAE Publications, 2010.

—. 2010. Ashrae Standard: 55.2010. Thermal Environmental Conditions for Human Occupancy.

Atlanta : ASHRAE Publications, 2010.

—. 2011. Procedures for Commercial Building Energy Audits, Second Edition. Atlanta, GA :

ASHRAE Bookstore, 2011.

—. 1983. RP-351-Energy Audit Input Procedures and Forms. Atlanta. GA : ASME, 1983.

ASME. 2010. Energy Assesment for Compressed Air Systems (ASME-EA-4-2010). New York :

ASME Publications, 2010.

—. 2009. Energy Assessment for Process Heating Systems (ASME EA-1-2009). New York :

ASME, 2009.

—. 2009. Energy Assessment for Pumping Systems (ASME EA-2-2009). New York : ASME

Publications, 2009.

—. 2009. Energy Assessment for Steam Systems (ASME EA-3-2009). New York : ASME

Publications, 2009.

Constructing HVAC performance indicators. Perez-Lombard, Luis, et al. 2011. 47, 2011,

Energy and Buildings, pp. 619-629.

Coplien, James O and Bjornvig, Gertrud. 2010. Lean Architecture for Agile Software

Dvelopment. Chichester, West Sussex, UK : John Wiley & Sons Ltd., 2010.

Del Rio, Israel. 2009. IT Transformation with SOA: "The Architecture Scope". [Online] 2009.

[Cited: 12 08 2012.] http://itransform.abstraction.com/labels/Strategy.html.

EC. 2011. COMMISSION REGULATION (EU) No 327/2011, of 30 March 2011 implementing

Directive 2009/125/EC of the European Parliament and of the Council with regard to ecodesign

requirements for fans driven by motors with an electric input power between 125 W and 500 kW.

Brussels : European Comission, 2011.

—. 2007. Ventilation for non-residential buildings - Performance requirements for ventilation and

room-conditioning systems. Brussels : European Comission, 2007.

ENAC. 2012. ENAC Ente Nazionale per L'Aviazione Civile. Diagnosi e certificazione n. 15

aeroporti nazionali nelle regioni individuate obiettivo convergenza. [Online] 2012. [Cited: 01 09

2012.] http://www.enac.gov.it/Canale_di_servizio/Bandi_di_gara/info2118083630.html.

energyXperts . 2012. Experts System for an Intelligent Supply of Thermal Energy in Industry

and other Large-Scale Applications. [Online] 2012. [Cited: 01 09 2012.] http://www.einstein-

energy.net/index.php.


page 212 of 234

European Commission. 2006. prEN 15240:2005 (E). Ventilation for buildings. Energy

Performance of Buildings. Guidelines for Inspection of air-conditioning systems. Brussels :

European Comission, 2006.

EUROVENT . 2005. Eurovent 6/8. Reccomendations for calculations of energy consumption for

air handling units. Brussels : Eurovent Publications, 2005.

Field Diagnostics Services, Inc. 2012. Field Diagnostics. [Online] 2012. [Cited: 01 09 2012.]

https://www.fielddiagnostics.com/.

FSIAQC. 2008. LVI 05-10440 - Classification of Indoor Environment 2008. Target Values,

Design Guidance, and Product Requirements. Espoo : Rakennustietosäätiö RTS 2010, 2008.

HarmonAC. 2009. HarmonAC. [Online] 2009. [Cited: 01 09 2012.] http://www.harmonac.info/.

IEA. 1987. Source Book for Energy Auditors. Stockholm : Swedish Council for Building

Research, 1987.

—. 1987. Source Book for Energy Auditors. Edited by M. D. Lyberg. Stockholm. Sweden :

Swedish council for Building Research, 1987.

IEC. 2009. IEC 61970: Energy Management System Application Program Interface - Part 301:

Part 301: Common information model (CIM) base. 2.0. s.l. : IEC, 2009.

IEEE. 2003. IEEE P1600.1 - Standard Upper Ontology Working Group (SUO WG) - Suggested

Upper Merged Ontology. [Online] 2003. [Cited: 01 September 2012.]

http://suo.ieee.org/SUO/SUMO/index.html.

ISO. 2007. BS EN 15251:2007. Indoor environmental parameters for design and assessment of

energy performance of buildings addressing indoor air quality, thermal environment, lighting and

acoustics. Geneve : ISO Publications, 2007.

—. 2011. ISO 50001 - Energy management systems. Requirements with guidance for use.

Geneve : International Standard Organisation, 2011.

—. 2005. ISO 7730:2005 Ergonomics of the thermal environment. Analytical determination and

interpretation of thermal comfort using calculation of the PMV and PPD indices and local thermal

comfort criteria. Geneve : ISO Publications, 2005.

—. 2008. ISO BS 15603:2008 Energy Performance of Buildings. Overall energy use and

definitions of enery ratings. London : ISO Publications, 2008.

—. 1994. ISO/IEC 7498-1. Information Technology - Open Systems Interconnection - Basic

Reference Model: The Basic Model. Geneve : International Standards Organisation, 1994.

McGoveran, David. 2006. Embracing SOA. The benefits of integration independende. Report N.

20060125. Alternative Technologies. [Online] 2006. [Cited: 01 09 2012.]

http://www.AlternativeTech.com.

Perfection Consortium. 2010. FP7 PERFECTION : COORDINATION ACTION FOR

PERFORMANCE INDICATORS FOR HEALTH, COMFORT AND SAFETY OF THE INDOOR


page 213 of 234

ENVIRONMENT – Grant Agreement 212998. [Online] 2010. [Cited: 01 09 2012.] http://www.ca-

perfection.eu/index.cfm?n01=general_info.

Project Management Institute, Inc. 2008. A Guide to the Project Management Body of

Knowledge (PMBOK GUIDE). 2008. Pennsylvania : Project Management Institute, Inc., 2008.

Sabbatini, Enrico. 2011. From energy audits to ICT implementation: a methodology applied to

sport facilities. [Online] October 2011. [Cited: 12 02 2012.] http://ict-sustainablehomes.org/wp-

content/plugins/alcyonis-event-agenda//files/Energy-Audit.pdf.

SCBIR. 2012. protégé - The Protégé Ontology Editor and Knowledge Adquisition System.

Stanford Center for Biomedical Information Research. [Online] 2012. [Cited: 01 09 2012.]

http://protege.stanford.edu/.

Schuh , A.C. 2000. Performance Indicators for Indoor Air Quality. PhD Thesis. Calgary :

Univiersity of Calgary, 2000.

Standards Australia. 2000. AS/NZ 3598:2000 australian/New Zealand Standard: Energy Audits.

Sydney : Standards Australia, 2000.

2011. The HDF Group. [Online] 11 15, 2011. [Cited: 03 06, 2012.]

http://www.hdfgroup.org/HDF5/.

White, Simon. 2005. Scientific Computing World: Better computational description of Sience.

[Online] 2005. [Cited: 21 09 2012.] http://www.scientific-

computing.com/features/feature.php?feature_id=37.

WSA. 2010. AuditAC. Welsh School of Architecture. CRIBE. Field Benchmarking and Market

Development for Audit Methods in Air Conditioning (AUDITAC). [Online] 2010. [Cited: 01 09

2012.] http://www.cardiff.ac.uk/archi/research/auditac/publications.html.


page 214 of 234

List of abbreviations

AEC Architecture, Engineering and Construction

AHU Air Handling Unit

API Application Programming Interface

ASHRAE American Society of Heating, Refrigeration Air-Conditioning Engineers

BAS Building Automation Systems

BER Building Energy Rating

BLC Building Life Cycle

BEM Building Energy Management

BES Building Energy Simulation


page 215 of 234

ANNEX 1. CASCADE detailed airport survey template

This annex presents the CASCADE detailed airport survey template that was utilised:

To identify energy management procedures and responsibilities in the airports

organisations (SEA and ADR);

To identify and describe Milan MXP and Rome FCO airports operation;

To document and characterise ICT and HVAC systems operating at Milan MXP and

Rome FCO.

The survey template below, follows the structure of the energy management standard ISO

50001 and it is divided according to its main headings in the following seven sections.

4.1 General Requirements

4.1

1. Have the Scope and boundaries required for compliance with ISO 50001 been defined? (See 4.1 of ISO 50001)

Answer

2. Did you already implement an ISO based Energy Management System (EN 16001, ISO 50001)?

Answer

3. Is there any kind of building energy rating certificate?

Answer

4.2 Management Responsibility

4.2.1 Top Management


page 216 of 234

1. Have top management demonstrated its commitment to support the EnMS (Energy Management System)? (See 4.2 of ISO)

Answer

2. Who is responsible for the different parts of the airport (Decision making structure, management structure, operational structure)? Is it possible to deliver an organogram (name, surname, phone, e-mail)?

Answer

3. Are there energy managers in place and who are they? If you deliver an organogram, please mark them.

Answer

4. Please name the IT-manager for data transfer issues, soft- and hardware installation? If you deliver an organogram, please mark them.

4.2.2 Management Representative

1. Has a management representative been appointed? (See 4.2.2 of ISO)

Answer

4.3 Energy Policy

4.3


page 217 of 234

1. Have top management defined an energy policy? (See 4.3 of ISO)

Answer

2. Did you defined targets for energy savings? One overall target (for the whole airport) or also small specific targets for the different energy subsystems (e.g. 20% for heating and cooling)?

Answer

3. Do you already have an idea of what you would like to improve with energy efficiency? Have you examples of problematic issue that facilities’ managers want to address with the project?

Answer

4. Are the energy saving intentions of the organization transparent and comprehensible for employees/public? Is there a way to motivate employees and customers to follow this energy

saving intentions (incentives etc.)?

Answer:

5. Is there a possibility for employees and customers to bring own ideas into the energy saving procedure (continuous improvement process CIP)?

Answer

6. Is there any lack of incentives to implement energy efficiency devices and encourage efficiency among customers that could be improved?

Answer

7. Within the analysed airport facilities, is there any energy efficient policies / energy conservation measure that has been put in place? Which one? Is it possible to measure and verify the associated energy impact?


page 218 of 234

Answer

4.4 Energy Planning

4.4.1 General

1. Has the organization carried out any energy planning? (See 4.4.1 of ISO)

Answer

2. What are the anticipated company development and planned investments for buildings, HVAC plants, lighting, …?

Answer

3. Is there a relationship between energy consumption and airport operation in terms

of scheduled flights, passenger traffic, …? Travellers – number of users, planes, gate schedules, weekends, special day types,…. Are these predictable patterns. Is there a formal way to monitor this parameter (e.g. check-in)?

Answer

4.4.2 Legal & Other Requirements

1. Are there any legal requirements to which the organization subscribes, in relation to energy use? (See 4.4.2 of ISO)

Answer

2. What are the rules surrounding co-generation?


page 219 of 234

Answer

3. What are the rules surrounding renewables (solar, wind, geothermal) ?

Answer

4. What are the regulations and approval from the public authority regarding energy questions?

Answer

5. How are the regulations different across different parts of the airport?

Answer

6. How do carbon credits / carbon offsetting work?

Answer

7. Available documentation related to carbon accreditation (including HVAC audit) - not only the general description (question 4.4.2.6) but the actual report that the airports submitted which includes deep analysis of HVAC.

Answer

8. For your electricity/heat/cold/water supply, which kind of contract do you have? Fixed pricing, variable pricing, contractual terms and conditions, peak limits?

Answer

4.4.3 Energy Review


page 220 of 234

4.4.3.1 Monitoring/BMS

1. For the energy review, has the organization analysed their energy use and consumption? Is past and present data available on energy consumption? (See 4.4.3 of ISO) What are the energy flows and energy costs in broad terms for the airport?

Answer

2. Can you generate energy flows in an hourly, daily, monthly or yearly average for the last 3 years (2008/2009/2010)?

Answer

3. Is there currently a system in place to record energy improvement opportunities? (See 4.4.3 of ISO)

Answer

4. Have energy audits been conducted? When? On which parts of your facilities?

Answer

5. Do you use manual raw data analysis? Which visualization techniques do you use?

Answer

6. How is the amount of released CO2 emissions related to the kWh produced (linear, exp, etc.), from the co-generation perspective?

Answer

7. Did you implement a BIM (Building Information Model)?


page 221 of 234

Answer

8. What is the Type/Model of the existing Building Automation System (BAS) /Building Management System (BMS)? When was it commissioned? What is the operating system (TinyOS, LiteOS, eCos, uC/OS etc., Linux, Windows)? What are kind of interfaces are used?

Answer

9. To what extent the currently installed sub-systems like HVAC´s, lighting are integrated to existing your BAS/BMS?

Answer

10. Do we have access to the low-level devices directly or through the centralized management system? Do you store your data in a database? If so, which kind of database is generated by your system? Has your system the capacity to generate ASCII data files?

Answer

11. Which kind of data transfer method by internet is allowed?

Answer

12. What kind of data can be generated by your BAS? What is the minimal time (giornaliero, mensile …ecc) resolution which can be generated?

Answer

13. Can you generate data point lists for each system/subsystem (AHU, water loops, …)?


page 222 of 234

Answer

14. Do you use a standard for the data point naming?

Answer

15. Which protocols are implemented in your BAS/BMS (Protocols (BACnet, Modbus, LonWorks, N2, IEC => 61970/61968 CIM, 61970 CIS, 61850-7, 60870-5)?

Answer

16. Do you think that it is possible to reduce the overall facility management costs by adopting some ICT solutions? Which ones?

Answer

17. Is possible to create awareness among customers in order to apply ICT system able to reduce the overall energy consumptions? (example Faro airport)

Answer

4.4.3.2 Technical Specification, Building

1. What is the date of construction of the building? What are the general features of the building structure? Can you give information on the physical characteristic of the building envelope?

Answer

2. Are 2D plans/ 3D models/schemas (paper/dxf/dwg,…) of the airport buildings and main technical plants available?

Answer


page 223 of 234

3. Are there technical documents for the facilities? Which one?

Answer

4. Is the detailed architecture of technical systems (HVAC, lightning, SCADA, etc.) available? ( ADR kick-off presentation, slide 17)

Answer

5. What are the Significant Energy Users (SEUs)? Give details of each? (See 4.4.3 of ISO) Do you know which are the major energy consuming buildings/zones/processes?

Answer

6. What kinds of heat generation systems are installed? What are their sizes in kW? Do you measure their efficiency? How? What are their operation schedules? Orari funzionamento

Answer

7. What kind of chilled water generation systems are installed? What are their sizes in kW? Do you measure their efficiency? How? What are their operation schedules?

Answer

8. Are there technical documents that describe the functions of your HVAC systems?

Answer


page 224 of 234

9. Have you technical specifications of your main air handling units? What are their sizes in m3/h?

Answer

10. Have you technical specifications of your main water loops? What are their water flows in m3/h?

Answer

11. What are the supply and return temperatures setpoints for hot and chilled water? Is there a winter/summer compensation strategy for the setpoint temperature?

Answer

12. Do you generate waste heat, waste gases and solids suitable for energy generation? Which ones?

Answer

13. Are there any renewable energy systems already installed? (Photovoltaic plants, Wind turbines, thermal solar collectors, bio-cogeneration plants etc.)

Answer

14. Do you sell energy generated by your renewable energy systems?

Answer


page 225 of 234

15. What are the requirements for backup power?

Answer

16. How does your Water Management System work? Which measures did you implement to reduce your water consumption?

Answer

4.4.3.3 Control & Feedback

1. What are the operational strategies of the HVAC systems? Are they seasonal?

Answer

2. What are the schedules of the main Air Handling Units (AHU)?

Answer

3. Is there a demand controlled ventilation according to occupancy (CO2 and integration with facility management tools e.g. occupancy schedules)?

Answer

4. Do you monitor inside air quality? Are there issues with kerosene vapours from the outside?

Answer

5. Do you apply time scheduling of "significant energy use" devices?

Answer


page 226 of 234

6. Do you use pumps with variable speed drive?

Answer

7. Do you use lux meters to control your artificial lighting?

Answer

8. Do you apply any peak shaving action plan related to both dynamical pricing and CO2 emissions?

Answer

9. Did you implement adaptive comfort strategies?

Answer

10. Do you receive any complaints from customers in terms of comfort conditions in the facility (too hot, too cold, too moist, too dry, air draughts, too bright, too dark , too loud…)? If so, are they associated to specific area of the building, type of activity or type of user?

Answer

11. Documentation of current manual procedures for ECM (reducing pressurization of AHUs, switching off lighting circuit during unoccupied periods in plant rooms)

Answer

4.4.3.4 Optimization & FDD


page 227 of 234

1. Did you optimize start-up/switch off time and operation schedules?

Answer

2. Did you optimize the pressurization and depressurization of different spaces according to different weather and people flows?

Answer

3. Did you optimize the free cooling?

Answer

4. Did you optimize the room setpoint and setback air temperatures?

Answer

5. Did you try to optimize the outside air flow rates?

Answer

6. Do you optimize dimming based on people flows and security requirements? How?

Answer

7. Do you use acoustic sensors to optimize your lighting strategies?

Answer

8. Does your system provide full-automated energy related data analysis on its facilities such as data logging, real-time energy consumption analysis, diagnostic etc.?

Answer


page 228 of 234

9. Did you already implement Fault Detection and Diagnostics Systems? Which kind? What are your experiences?

Answer

10. Did you detect impact of faults on energy consumption?

Answer

No

4.4.4 Energy Baseline

1. Has a suitable energy baseline been established? (See 4.4.4 of ISO)

Answer

2. For which period you have sensor readings stored in database? (IPMVP Definition of baseline (3.))

Answer

4.4.5 EnPIs

1. What are the energy performance indicators (EnPIs) currently in use? Are there any EnPIs in particular that would be helpful for the organization? (See 4.4.5 of ISO)

Answer

2. Do you measure your energy consumption per each typologies of facilities (terminal, mall, offices etc.) and systems that consume that energy (ventilation, heating, lighting, cooling, hot water, energy for equipment etc.) If not so, do you estimate these energy consumption and how?

Answer


page 229 of 234

3. How is energy consumption visualized and reviewed?

Answer

4. Do any energy decisions get based on real time or predicted information (usage, weather, pricing)?

Answer

4.4.6 Energy objectives, targets & Action Plans

1. What are the energy objectives and targets for your organization? What are the time frames? (See 4.4.6 of ISO)

Answer

2. Do you have an idea on the possible savings that the structure could achieve?

Answer

3. How many months could be a reasonable payback period?

Answer

4. Which existing systems do you need to optimize? Which faults/failures occurs the most frequently? Which faults are difficult to detect by the operating teams?

Answer


page 230 of 234

5. Is there a management system to update these documents accordingly to operation changes?

Answer

4.5 Implementation & Operation

4.5.1 General

1. What are the Competence, training and awareness systems in place at your facility? Who are the relevant persons related to the known SEUs? (See 4.5 of ISO)

Answer

4.5.2 Competence, training & awareness

1. What are the Competence, training and awareness systems in place at your facility? (See 4.5 of ISO)

Answer

2. Are there technical documents that describe the functions of your lighting systems? Is there a management system to update these documents accordingly to operation changes?

Answer

4.5.3 Communication

1. The organization shall decide whether to communicate externally about its energy policy, EnMS and energy performance, and shall document its decision. & How? (See 4.5.3 of ISO)

Answer


page 231 of 234

2. Have staff members a method by which to make comments or suggest improvements to the EnMS? (See 4.5.3 of ISO)

Answer

4.5.4 Documentation

1. Do the organization currently have documentation referring to the core elements of the EnMS? I.e. scope, energy policy, obj &targets, etc. (See 4.5.4.1 of ISO)

Answer

1. Does the organization currently have a document control system for the EnMS? (See 4.5.4.2 of ISO)

Answer

4.5.5 Operational control

1. Have the organization identified the operation and maintenance activities that are related to SEUs? (See 4.5.5 of ISO)

Answer

4.5.6 Design

1. Does the organization consider energy performance improvements in the design of new or modification of facilities, equipment & systems? (See 4.5.6 of ISO)

Answer

4.5.7 Procurement of energy services, products, equipment & energy

1. Have the organization created guidelines on the procurement of energy efficient equipment or services? (See 4.5.7 of ISO)

Answer


page 232 of 234

4.6 Checking

4.6.1 Monitoring, measurement & analysis

1. Have the organization identified the key characteristics of its operations that determine energy performance? (See 4.6.1 of ISO)

Answer

2. Has the organization an energy measurement plan in place? (See 4.6.1 of ISO)

Answer

3. Do you have sub or smart metering in place – or do you receive one bulk energy bill?

Answer

4. Do you already perform statistical analysis of gathered data and if you do, which procedures are used? (IPMVP Specification of analysis procedure (6.))

Answer

5. What are the time resolutions of each sensor readings? (IPMVP Meter specifications (8.))

Answer

4.6.2 Evaluation of compliance with other requirements & legal requirements

1. Is the organization aware of all legal requirements, in order to evaluate compliance on a regular basis? (See 4.6.2 of ISO)

Answer


page 233 of 234

4.6.3 Internal Audit of the EnMS

1. Has the organization a system in place for internal audits of their EnMS? See 4.6.3 of ISO)

Answer

2. At what time intervals are the organization willing to carry out internal audits of the EnMS? (See 4.6.3 of ISO)

Answer

4.6.4 Nonconformities, correction, corrective action and preventative action

1. How does the organization intend to deal with non-conformities? What are the incentives for SEUs to avoid non-conformities? (See 4.6.4 of ISO)

Answer

4.6.5 Control of records

1. How does the organization control records in relation conformities of its EnMS ? (See 4.6.5 of ISO)

Answer

4.7 Management Review

4.7.1 General

1. At what time intervals are the organization willing to carry out a management review? (See 4.7.1 of ISO)

Answer


page 234 of 234

4.7.2 Input to management review

1. Does the organization consider the relevant inputs to management review? (See 4.7.2 of ISO)

Answer

4.7.3 Output from management review

1. Are significant and meaningful actions created as a result of the management review? (See 4.7.3 of ISO)

Answer