BIM to BEM for Building Energy Analysis: A Review of Interoperability Strategies
The main objective of this review is to summarize and thoroughly investigate the most popular and promising BIM (building information modeling) and BEM (building energy modeling) interoperability strategies employed in the last years (2004–2023), highlighting pros and cons of each strategy and tryin...
Gespeichert in:
Veröffentlicht in: | Energies (Basel) 2023-12, Vol.16 (23), p.7845 |
---|---|
Hauptverfasser: | , , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | The main objective of this review is to summarize and thoroughly investigate the most popular and promising BIM (building information modeling) and BEM (building energy modeling) interoperability strategies employed in the last years (2004–2023), highlighting pros and cons of each strategy and trying to understand the reason for the still limited BIM–BEM interaction. This review summarizes the main countries, areas, modeling tools, and interoperability strategies, with the advantages and disadvantages of each one. The methodology is based on the PRISMA protocol, and two databases were used for the research: Scopus and Google Scholar. A total of 532 publications were selected and 100 papers were deemed useful for the purposes of this review. The main findings led to the identification of four different interoperability strategies between BIM and BEM tools: (1) real-time connection; (2) standardized exchange formats and middleware corrective tools; (3) adherence to model view definitions; (4) proprietary tool-chain. These strategies were found to be characterized by different degrees of complexity, time required for information exchange, proprietary or opensource software, ability to reduce information loss, and detailed energy results. The results of this study showed that, to date, there is no better interoperability strategy, and that further efforts are needed so that interoperability between the two tools can become commonplace. |
---|---|
ISSN: | 1996-1073 1996-1073 |
DOI: | 10.3390/en16237845 |