BIM AND REALITY VISUALIZATION
BIM viewers connected to information
A selection that has to work both ways
The first prototype grew out of an interface decision: placing the model inside Power BI, alongside the tables and visuals that needed to refer to it. The custom visual received report data and loaded an IFC model from a locally served resource. This allowed it to connect geometry with report rows without asking the reader to open Revit. The link depended on a recognizable key. I used IFC GlobalId identifiers to connect elements with records. When someone selected an object in the scene, the visual communicated that selection to the report; when the data was filtered in Power BI, the model could highlight or isolate the corresponding elements. The challenge was no longer just displaying geometry: it also involved deciding what should happen when an identifier was duplicated, missing, or referred to an entity without a visible mesh. One specific rule dealt with openings in the model. If a row described an opening and retained the identifier of its host element, the selection could visually lead to that wall or another related object. It showed how information relationships affect what is useful to highlight on screen.
Another representation for another question
The second exploration was developed to visualize a facility from a perspective closer to operations and maintenance. A single web application brought together a BIM model converted to Fragments and a photographic reconstruction using Gaussian Splatting. The model's geometry provided structure and identity; the visual capture showed the appearance of the site and its surroundings. To prepare the reconstruction, I worked with drone photographs, processing in COLMAP, and subsequent stages of transformation, orientation, and generation of versions suitable for viewing. Getting both resources to appear in the same scene did not automatically solve their spatial correspondence. The model and reconstruction could start from different coordinates and orientations, so their alignment needed to be adjusted and studied.
From prototype to useful information access
The two experiences raised different challenges. In Power BI, the work focused on turning object identities into interactions with analytical information. In the web viewer, it focused on preparing different types of representation to navigate a facility and recognize its components. The web demonstration worked in a local environment and made it possible to explore how the representations could be viewed together. Evolving it toward asset information access involves adding data prepared for operational questions, with shared identifiers and access criteria. The purpose is not to add geometry for its own sake, but to help someone find in the model the information they need about a place.