Periodic Reporting for period 2 - BIM2TWIN (BIM2TWIN: Optimal Construction Management & Production Control)
Période du rapport: 2021-11-01 au 2023-04-30
BIM2TWIN is a European-funded project aimed to build a Digital Building Twin (DBT) platform for construction management that implements lean principles to reduce operational waste of all kinds, shortening schedules, reducing costs, enhancing quality and safety and reducing carbon footprint. The key objective of the project is to develop a Digital Building Twin platform (DBT) able to provide situational awareness, with a comprehensive, holistic approach. This means that any stakeholder across the construction process is able to get a real-time representation of the status of everything happening on site and throughout the whole supply chain, thanks to a set of construction management applications.
The basic idea at the core of the BIM2TWIN project is to develop a platform able to represent the current status of products and processes through a Project Status Model (PSM). This model shall be populated by real-time monitored data from the site and the supply chain and should be able to manage and process all this data
in an automated way, across the entire lifespan of the project. The information managed by the platform will be interpreted and used by construction managers, thanks to a decision support dashboard for forward planning and real-time control.
The platform will therefore stand as a junction between the monitored data flow and the information made available to the different stakeholders through construction management applications.
In order to coherently manage all the collected data, the platform will rely on a robust system architecture, so that data can be processed to establish a PSM and turned into information for decision-making, providing a reliable tool for monitoring schedules, quantities, budget, quality, safety, and environmental impact.
As the name BIM2TWIN suggest, the Digital Building Twin representation – actually the Project Status Model (PSM) - will be semantically linked to Building Information Model (BIM), including schedule models, logistic models, task models and so on.
The project will implement an interoperable framework based on compatible linkeddata, building a common information backbone for digital twins. Moreover, the project will explore innovative approaches - compared to the state of the art – relying on a property-graph-based cloud data store that provides APIs (Application Programming Interfaces).
The basic idea at the core of the BIM2TWIN project is to develop a platform able to represent the current status of products and processes through a Project Status Model (PSM). This model shall be populated by real-time monitored data from the site and the supply chain and should be able to manage and process all this data
in an automated way, across the entire lifespan of the project. The information managed by the platform will be interpreted and used by construction managers, thanks to a decision support dashboard for forward planning and real-time control.
The platform will therefore stand as a junction between the monitored data flow and the information made available to the different stakeholders through construction management applications.
In order to coherently manage all the collected data, the platform will rely on a robust system architecture, so that data can be processed to establish a PSM and turned into information for decision-making, providing a reliable tool for monitoring schedules, quantities, budget, quality, safety, and environmental impact.
As the name BIM2TWIN suggest, the Digital Building Twin representation – actually the Project Status Model (PSM) - will be semantically linked to Building Information Model (BIM), including schedule models, logistic models, task models and so on.
The project will implement an interoperable framework based on compatible linkeddata, building a common information backbone for digital twins. Moreover, the project will explore innovative approaches - compared to the state of the art – relying on a property-graph-based cloud data store that provides APIs (Application Programming Interfaces).
This report covers the second reporting period from M13 to month M30 of the project.
The first 12 months were focusing mainly on the definition of the requirements and system design (MS1).
During the first period, the main focus was on WP1 for the definition of processes around our digital twin solution. This activity has led to an important dialogue among the WP1 and the so-called technical WPs (WP2 to WP7) to express and detail uses cases as well as KPIs necessary to follow up the on-site activity.
The end of the first reporting period corresponds to the end of WP1.
During the second reporting period covering 18 months, lots of activities have been carried out following the initial direction chosen in RP1.
The technical WPs have developed their software tools. These developments started mainly in silos in each WP with regular meetings to follow up the progresses. After MS2 (M18 - Internal Progress Review), several "cross -WPs" workshops have been organized in order to drive and facilitate the integration of the software developed in WP3 to WP7 with the Digital Building Twin Platform (DBTP) developed in WP2. The purpose of these workshops was to prepare the MS3 (M24 - First version of the platform). MS3 has been successfully reached, and we demonstrated that all solutions were connected to the platform and able to dialogue with it.
The next step was MS4 (M28 - First user requests for improvement), meetings with our pilots were planned in order to explain the developments made and demonstrate the first version of the tools. These demonstrations have taken place on our 3 pilot sites and have been prepared and organized by WP8 with the support of the technical WPs. The demonstration were accompanied by questionnaires in order to collect the feedback/expectations from our pilots. These feedbacks are currently addressed in the ongoing developments of the second version of the platform (MS5 - M33) that will be issued at the beginning of the third reporting period.
Now (from M28 to M33) the different work packages from WP2 to WP8 are working in strong collaboration to reach the MS5, in addition to the remarks collected from MS4, it is also important to show now the strong interactions and collaborations among the various services developed, and the key role played by the DBTP in the various exchanges.
The WP9 activity has become stronger, following the technical activity, several dissemination activities have been conducted (paper publication, conferences and exchange with the community and also with the sister projects).
Since the beginning of the project, 48 deliverables have been issued.
The first 12 months were focusing mainly on the definition of the requirements and system design (MS1).
During the first period, the main focus was on WP1 for the definition of processes around our digital twin solution. This activity has led to an important dialogue among the WP1 and the so-called technical WPs (WP2 to WP7) to express and detail uses cases as well as KPIs necessary to follow up the on-site activity.
The end of the first reporting period corresponds to the end of WP1.
During the second reporting period covering 18 months, lots of activities have been carried out following the initial direction chosen in RP1.
The technical WPs have developed their software tools. These developments started mainly in silos in each WP with regular meetings to follow up the progresses. After MS2 (M18 - Internal Progress Review), several "cross -WPs" workshops have been organized in order to drive and facilitate the integration of the software developed in WP3 to WP7 with the Digital Building Twin Platform (DBTP) developed in WP2. The purpose of these workshops was to prepare the MS3 (M24 - First version of the platform). MS3 has been successfully reached, and we demonstrated that all solutions were connected to the platform and able to dialogue with it.
The next step was MS4 (M28 - First user requests for improvement), meetings with our pilots were planned in order to explain the developments made and demonstrate the first version of the tools. These demonstrations have taken place on our 3 pilot sites and have been prepared and organized by WP8 with the support of the technical WPs. The demonstration were accompanied by questionnaires in order to collect the feedback/expectations from our pilots. These feedbacks are currently addressed in the ongoing developments of the second version of the platform (MS5 - M33) that will be issued at the beginning of the third reporting period.
Now (from M28 to M33) the different work packages from WP2 to WP8 are working in strong collaboration to reach the MS5, in addition to the remarks collected from MS4, it is also important to show now the strong interactions and collaborations among the various services developed, and the key role played by the DBTP in the various exchanges.
The WP9 activity has become stronger, following the technical activity, several dissemination activities have been conducted (paper publication, conferences and exchange with the community and also with the sister projects).
Since the beginning of the project, 48 deliverables have been issued.
The work performed during these 30 months are mainly technical development around:
- The platform by itself (activity carried out in WP2)
- The various services connected to the platform and developed by the WP3 to WP7
- The organization of demonstrations (WP8)
- The acquisition / treatment and exploitation of site data (WP2 to WP8)
- The platform by itself (activity carried out in WP2)
- The various services connected to the platform and developed by the WP3 to WP7
- The organization of demonstrations (WP8)
- The acquisition / treatment and exploitation of site data (WP2 to WP8)