Periodic Reporting for period 1 - BuildON (Affordable and digital solutions to Build the next generatiON of smart EU buildings)
Reporting period: 2023-05-01 to 2024-10-31
In a world increasingly focused on energy transition, the 2021 EPBD recast emphasised the pivotal role of buildings in achieving an integrated, renewable energy-based EU system. The urgency to digitalise and decarbonise, especially in light of the REPowerEU Plan, has never been clearer. In this context, the EU-funded BuildON project aims to create a scalable, and replicable solution for intelligent building services. This transformative Smart Transformer Toolbox at TRL8, will enhance energy performance across diverse building types and smart readiness levels. Users will be empowered with user-friendly tools to support this transformation to continuously Monitor, Assess, Predict and Optimise (MAPO services) building performance, and make better informed-decision on smart technologies. Through a Universal Building API, BuildON simplifies the intricacies of communication between heterogeneous systems, enabling real-time monitoring and control of energy devices while digital twins complement this vision by representing buildings and their systems, and offering advanced simulation and control capabilities. Thanks to this unified approach to interact with buildings, the overall goal is to accelerate the smart transformation of existing and new buildings.
A brief summary of the progress performed in RP1 is presented below.
The first activities in BuildON have focused on understanding pilot’s needs, the starting point and the main expected goals, in order to better define actions to be performed (WP2). Within this definition phase, user stories, scenarios and functional and non-functional requirements have been defined (D2.1) taking into consideration the different needs of the demonstrators, the relevant stakeholders and personas involved, the user stories elicitation and the particular characterization of the users’ journey. To complement this user-centric approach, a user engagement roadmap has been particularised per pilot (D2.2). This roadmap is intended to capture services and tools to be co-designed, who will be involved within this process, how and the timing for this involvement.
The technical activities have run in parallel, starting also with the design and definition stages (WP3, D3.1 for architecture design), to align and support the designed application scenarios ensuring highly replicable solutions while minimising the need for customisation efforts. The next step is dedicated to orchestrating the interactions between the key components of the Start Transformer Toolbox Solution.
As the effectiveness of the project relies on a successful demonstration campaign, preparation activities in pilots are crucial (WP6). They have been carried out from an early stage, and an evaluation framework to assess the impact of the MAPO solutions has been formulated, incorporating energy consumption and flexibility, environmental, economic, social, IEQ and smart readiness aspects. To complement this, a baseline calculation has been performed (D6.1).
In terms of technical activities, the main components of the IoT edge-cloud architecture have reached their first functional implementation (WP3, D3.2) and a suite of tools aimed at facilitating smartness enhancement and fostering improved interaction between individuals and intelligent assets have released a first version (WP2, D2.3). Finally, the specifications on the BuildON Energy Management System and the interaction requirements have been defined (D4.1 WP4), and a top-down methodology based on archetypes has been established to deliver adaptable automation and control services as part of this orchestration (D5.1 WP5). MAPO services conceptualisation and specification activities have been carried out, while a first validation of their functionalities has taken place as pathway for the first technical release (D4.1). Strategies for effective deployment of services have been also investigated, considering potential conflicts and synergies between them.
In parallel, first steps have been taken to consolidate a sound communication and dissemination strategy (WP8, D8.1) including several activities and collaboration with projects and other initiatives. Finally, a first characterization of the exploitable results of the project has been covered, to continue working on the best data-driven business models for the adoption of smart solutions (WP7, D8.1).
To conclude, in addition, other management activities have also been undertaken: firstly, a Project Management Plan has been consolidated, detailing the activities to perform and the guidelines to be followed (D1.1 and D1.5). Furthermore, a Data Management Plan (D1.2) and Ethics requirements (D1.3) have been detailed to ensure the proper handling of information. Finally, and Advisory Board has been created to support project outreach and for exploitation purposes, mainly (D1.4).
The first activities in BuildON have focused on understanding pilot’s needs, the starting point and the main expected goals, in order to better define actions to be performed (WP2). Within this definition phase, user stories, scenarios and functional and non-functional requirements have been defined (D2.1) taking into consideration the different needs of the demonstrators, the relevant stakeholders and personas involved, the user stories elicitation and the particular characterization of the users’ journey. To complement this user-centric approach, a user engagement roadmap has been particularised per pilot (D2.2). This roadmap is intended to capture services and tools to be co-designed, who will be involved within this process, how and the timing for this involvement.
The technical activities have run in parallel, starting also with the design and definition stages (WP3, D3.1 for architecture design), to align and support the designed application scenarios ensuring highly replicable solutions while minimising the need for customisation efforts. The next step is dedicated to orchestrating the interactions between the key components of the Start Transformer Toolbox Solution.
As the effectiveness of the project relies on a successful demonstration campaign, preparation activities in pilots are crucial (WP6). They have been carried out from an early stage, and an evaluation framework to assess the impact of the MAPO solutions has been formulated, incorporating energy consumption and flexibility, environmental, economic, social, IEQ and smart readiness aspects. To complement this, a baseline calculation has been performed (D6.1).
In terms of technical activities, the main components of the IoT edge-cloud architecture have reached their first functional implementation (WP3, D3.2) and a suite of tools aimed at facilitating smartness enhancement and fostering improved interaction between individuals and intelligent assets have released a first version (WP2, D2.3). Finally, the specifications on the BuildON Energy Management System and the interaction requirements have been defined (D4.1 WP4), and a top-down methodology based on archetypes has been established to deliver adaptable automation and control services as part of this orchestration (D5.1 WP5). MAPO services conceptualisation and specification activities have been carried out, while a first validation of their functionalities has taken place as pathway for the first technical release (D4.1). Strategies for effective deployment of services have been also investigated, considering potential conflicts and synergies between them.
In parallel, first steps have been taken to consolidate a sound communication and dissemination strategy (WP8, D8.1) including several activities and collaboration with projects and other initiatives. Finally, a first characterization of the exploitable results of the project has been covered, to continue working on the best data-driven business models for the adoption of smart solutions (WP7, D8.1).
To conclude, in addition, other management activities have also been undertaken: firstly, a Project Management Plan has been consolidated, detailing the activities to perform and the guidelines to be followed (D1.1 and D1.5). Furthermore, a Data Management Plan (D1.2) and Ethics requirements (D1.3) have been detailed to ensure the proper handling of information. Finally, and Advisory Board has been created to support project outreach and for exploitation purposes, mainly (D1.4).
BuildON will offer innovative, affordable, user-friendly and accessible products and services to continuously monitor and improve energy performance of buildings. The steps followed during the first reporting period are the cornerstone to obtain the key exploitable results (KERs) of the project. The first identification and characterisation of the KERs has been covered during this period.
In terms of progress beyond the state of the art and impacts, the BuildON solution is composed of several subcomponents, to be delivered and implemented in pilots gradually, up to M33. Details of the main achievements so far can be consulted in Part B, while the connection between WPs, Scientific and Technical Objectives (STO) or Non-Technical Objectives (NTO), ambition and Expected Outcomes (EO) is shown below:
• WP2: STO1; ambition 1, 2, 4; EO1, EO2, EO3, EO4
• WP3: STO2; ambition 3, 5; EO1, EO2, EO3, EO4
• WP4: STO3, STO4, ambition 5, 6, 7; EO1, EO2, EO3, EO4
• WP5: STO3, STO5, ambition 5, 6, 8; EO1, EO2, EO3, EO4
• WP6: STO6; EO2, EO3, EO4
• WP7: NTO1, ambition 9; EO1, EO2, EO3, EO4
• WP8: NTO2; EO1, EO3, EO4
In terms of progress beyond the state of the art and impacts, the BuildON solution is composed of several subcomponents, to be delivered and implemented in pilots gradually, up to M33. Details of the main achievements so far can be consulted in Part B, while the connection between WPs, Scientific and Technical Objectives (STO) or Non-Technical Objectives (NTO), ambition and Expected Outcomes (EO) is shown below:
• WP2: STO1; ambition 1, 2, 4; EO1, EO2, EO3, EO4
• WP3: STO2; ambition 3, 5; EO1, EO2, EO3, EO4
• WP4: STO3, STO4, ambition 5, 6, 7; EO1, EO2, EO3, EO4
• WP5: STO3, STO5, ambition 5, 6, 8; EO1, EO2, EO3, EO4
• WP6: STO6; EO2, EO3, EO4
• WP7: NTO1, ambition 9; EO1, EO2, EO3, EO4
• WP8: NTO2; EO1, EO3, EO4