PERFORMERWP2

INTRODUCTION

13th of September 2013

CSTB Sophia Antipolis, France

| PAGE 2PERFORMER Kick-Off meeting

WP2 ‘HOLISTIC ASSESSMENT FRAMEWORK FOR BUILDING ENERGY PERFORMANCES’ – OVERVIEW

• Objectives:• To build a consistent and comprehensive framework, which augments

the PERFORMER solution with ICT-enabled smartness and automation

• Facts & figures• RTD work-package – mainly focused on ICT• Duration: M1 – M30• Involving UPL, CSTB, CEA, CU, BRE, EC, GDF, SG, SIGMA, CCC

(Leader CEA)• Total WP effort = 93 p.m (15% of project’s total effort)

• Activities• Specifying and prototyping a comprehensive and adaptable (i.e. scalable) ICT

infrastructure (sensors, communication software, interfaces, and devices) for building energy, comfort and usage data collection.

• Assessing, selecting and implementing the most relevant combinations of artificial intelligence and building digital modelling approaches for real-time energy monitoring, awareness and management.

• Providing smart visualization and decision support during operation phase.

| PAGE 3DELFT, 17-18 SEP 2013

Task 2.1: Base technology selection (CU)

Task 2.2: Building intrinsic and actual performances energy assessment ICT infrastructure (ECG)

Task 2.3: Energy performance modelling environment (CEA)

Task 2.4: Energy performances management (CSTB)

D2.1: Performer Base Technologies Report (M6, 9 p.m)

D2.2: Intrinsic Performances Assessment Framework (M24, 24 p.m)

D2.3: Energy Performance Modelling Environment (M24, 27 p.m)

D2.4: Actual Performance Monitoring and Management Framework (M30, 33 p.m)

WP2 ‘HOLISTIC ASSESSMENT FRAMEWORK FOR BUILDING ENERGY PERFORMANCES’ – STRUCTURE

PERFORMER Kick-Off meeting

MS4: Delivery of Intrinsic and in-use performance monitoring and management framework (M30)

WP1: Global framework and methodologies

Methodological supportD1.1: PERFORMER framework (M12)D1.2: Methodologies for the Assessment of Intrinsic Energy Performance of Building Envelopes (M15)D1.3: Cost Optimised Energy Performance Measurement Plan Methodology (M15)D1.4: Specification for Energy Management, Fault Detection and Diagnostic Tools (M15)Pilot informationD3.1: Pilot Building Characteristics and Related Energy Data (M9)D3.3: Pilot Information Model (M12)D3.4: Consideration of Measurement Challenges (M12)Demonstration requirementsD4.1: Pilot Version Sharing and Awareness Raising Report (M6)

WP3: Pilot Data Gathering

WP4: Demonstrators

WP2: ICT framework

WP4: Demonstrators

WP5: Replication and Assessment

WP6: Dissemination and

exploitation

WP1: Global framework and methodologies

SoA (D2.1) and ICT-related requirements and limitations

Technology Research results

ICT infrastructure and tools (D2.2, D2.3, D2.4)

WP2 ‘HOLISTIC ASSESSMENT FRAMEWORK FOR BUILDING ENERGY PERFORMANCES’ – DEPENDENCIES

| PAGE 5

ACTIVITY PLAN M1-M6 WP2 ‘HOLISTIC ASSESSMENT FRAMEWORK FOR BUILDING ENERGY PERFORMANCES’

Activity Expected outcome Partners involved Deadline

1. Review of WP2 partners’ background

Summary of technological background available to WP2

All WP2 partners 10/2013

2. Clarification of technological contributions

Summary of contributions – tools architecture overview – detailed structure of D2.1

All WP2 partners 11/2013

3. Technology review (-> D2.1) State of the art contributions

TRF, RNS, AOC, APH

01/2014

4. D2.1 consolidation D2.1 for internal review CU, CEA, CSTB, GDF

02/2014

5. Development planning refinement

M6-24 detailed development planning

Task leaders: CU, EC, CEA, CSTB

02/2014

Objectives in M1-M6 SoA – technologies selection - clarification of contributions

Active tasks T2.1 ‘Base technology selection’ mainly – CU ; All tasks to start during the first 6 months.

Planned effort 10-12 person-months (out of total 93 person-months for this WP)

Remark/anticipated issue

-

PERFORMER Kick-Off meeting

WP2 - COMMENTS

Work organization

List of participants + one main contact point for each partners

One conf call every two weeks

F2Fmeetings when necessary

Having a WP2 workshop at M3 about the architecture?

Need business models

Initially planned at M48 – early internal delivery?

The planning is tight

Two ICT deliverables at M24

There is a risk of “drift” to M28-M30

Need for an early awareness of end-users functional requirements

From WP3-4-5

Impact on technology choice (e.g. MAS vs expert systems)

THANK YOU

Any questions?