CORDIS - Risultati della ricerca dell’UE
CORDIS

Adapt-&-Play Holistic cOst-Effective and user-frieNdly Innovations with high replicability to upgrade smartness of eXisting buildings with legacy equipment

Periodic Reporting for period 1 - PHOENIX (Adapt-&-Play Holistic cOst-Effective and user-frieNdly Innovations with high replicability to upgrade smartness of eXisting buildings with legacy equipment)

Periodo di rendicontazione: 2020-09-01 al 2022-02-28

PHOENIX has the aim of investigating and test technologies and methodologies that will help on the upgrading of legacy equipment in buildings to increase and improve smart services for users and occupants. For this, PHOENIX will develop an ICT platform that will serve as a common arena to connect the different devices that one can find in a building.
PHOENIX aims at changing the role of buildings from un-organised energy consumers to active agents orchestrating and optimising their energy consumption, production and storage, with the goal of increasing energy performance, maximising occupants’ benefit, and facilitating grid operation. The project will design a portfolio of ICT solutions covering all aspects from hardware and software upgrades needed in legacy equipment and optimal deployment of sensors, to data analytics and services for both building users and energy utilities. PHOENIX will take advantage of artificial intelligence technologies, as well as edge/cloud computing methods, to provide the highest level of smartness to existing buildings. The tools that will result from the different work packages will offer the possibility of establishing a new framework that will enable the optimisation of the energy use and infrastructure exploitation, while at the same time facilitate the creation of new SMEs and Start-Up ideas to exploit new revenue streams and business opportunities.
The work of WP2 aims to provide background information about the situation of the market and regulation with respect to smartness of buildings at the same time that it will pulse the status of society. It is expected that the findings obtained from this work package will feed on the rest of the work packages particularly on those in which the hardware and software solutions are made “ready for market”.
With respect to WP3, D3.2 has been delivered. Most integrations of external data sources are fully operational and the remaining are in the last stage of tests/configuration (Entsoe, LTU FIWARE platform, UMU Scada, etc.). The integrations of devices from the different pilots have been finished and the final Raspberry Pi image is ready and working in the different IoT Gateways installed.
WP4 tsecurity components (e.g. Identity Manager, Authorization Manager, and Policy Enforcement Point) (Task 4.1) have been updated, and a set of authorization policies for the existing entities supporting different roles for users/services/device have been configured. Moreover, the security components, more precisely the actuation part (integration with the Z-Wave/WMP actuation agent), have been deployed and tested with the final version of the IoT gateway image (node-RED). In task T4.2 sensor data is being modelled based on FIWARE’s Smart Data Models. For the grid services, SAREF4ENER is being used. The newly created SRI model has been updated to reflect the changes in the SRI calculation.
Within WP5 the solutions to grid flexibility to demand adjustment and for self-generation and energy storage have been developed on an integrated manner. The fact that on both cases the demand has to be adapted in relationship with the congestion in the first case and with the battery storage and generation no the second, made possible to have a flexibility engine downstream of both services. Two components to prepare the input of this flexibility engine prepare the inputs so the engine works for one or the other.
In addition, the conceptualization of the Integration, Testing and Refinement has been performed so the testing framework can be defined in order to perform task 6.4.
During this reporting period, in T7.2 "Adaptation, Planning and Deployment of pilots" the energy upgrade on the five demo-sites was continued by installing smart devices and equipment in all demo-sites. The communication with the platform has been established in all demo-sites by the provision of initial data sets from devices to context broker. Moreover, the initial trials list that will validate the intended use cases per pilot were defined for all demo-sites and a tentative timeline was set.
For this reporting period all relevant to communication activities KPIs due by M18 were achieved on WP8. The project video was launched, as well as the poster, brochure and two newsletters describing the project’s activities. Efforts were also allocated in the establishment of synergies with one project community (SmartBuilt4EU) and one interest group (Smart Cities Network).
a) Hardware solutions for connection and smart control of legacy systems and appliances
Within the project, a set of the mechanisms of integration of legacy equipment within the PHOENIX platform have been developed.

b) Integration and interoperability for multi-systems data exchange
From the data analytics services side, basic but operational versions of user-centric and grid- related services are included in this developments with both using real data. For the framework of the SRI, the SRI data is then stored in the triplestore and linked to other available building information (the building model if available).

c) Data analytic and Artificial Intelligence toolbox for EEB domain and human-related data
Data analytics techniques play an important role in the engines for Energy Efficiency of Buildings and other energy related actions.

d) Smart services for the energy sector and building users
A whole ecosystem has been developed in PHOENIX in this aspect. The communication of the various stakeholders with the grid Demand Response requests is simulated with the help of USEF framework interacting with PHOENIX, serving as a support tool for the aggregator in terms of flexibility, providing information from active consumers/prosumers and their devices able to adjust their demand to alleviate grid congestion peaks.

e) Security, Privacy and Trust
The security components can be deployed using either Docker or Kubernetes technologies. In the PHOENIX Project, Docker has been selected preliminary as the technology. The containers can be launched both in the same environment as the rest of the PHOENIX components or out of it due to their distributed nature.

f) Business Models
Within project PHOENIX a great deal of development has been done in order to identify and define new business models based on the innovations of the project.
Project logo