Embedding a BIM viewer into a web application is not only a rendering decision. It establishes a system boundary.
The choice affects where source models are processed, which credentials participate in the request path, whether intermediate representations are created, how model revisions propagate, and which components an engineering team must integrate and operate.
For IFC-centric applications, one question is especially useful:
Where should IFC model processing live?
Autodesk Platform Services (APS) and the Flinker IFC Viewer SDK represent two different approaches.
Construction projects track hundreds or thousands of individual work packages across multiple floors, trades, and delivery phases. The data that would let a site manager, BIM coordinator, or project controller answer “what has been installed on floor 1 this week?” typically lives in two disconnected places: the BIM model — which contains every element, its type, its storey, and its properties — and a separate spreadsheet or site diary, which has status updates but no reliable link back to model elements.
The Coordination Gap Between Models and Communication
Construction projects generate more structured digital information than any previous generation — and yet coordination failures remain among the industry’s most persistent cost drivers. According to an Autodesk and FMI study, 52% of rework is caused by poor project data and miscommunication, accounting for $31.3 billion in excess costs in the US construction market in 2018 alone. Across studies, rework is estimated to represent between 4% and 9% of total project cost, with the higher end reflecting indirect costs such as schedule compression, contractual disputes, and productivity loss on unaffected work packages.
BIM coordination depends on precision. A screenshot tells your colleague roughly where to look. A deep link takes them there — directly inside Teams, with the element already selected and its properties visible.
The Flinker IFC Viewer for Microsoft Teams now supports element-level deep links. Select any IFC element, copy the link, and paste it into any Teams chat or channel. The recipient clicks it, the viewer opens inside Teams, and they land on the exact element — no context switching, no ambiguity.
Review and coordinate models across Teams, SharePoint, Excel, and Power BI. Free to start, with project data kept on your device or in your Microsoft 365 tenant.
Implementation, rollout, and managed support for IFC Viewer on Power BI—enterprise-ready with clear SLAs, industry accelerators, add-ons, governance, and enablement.
