OpenBIM

IFC Viewer Architectures: Where Should Model Processing Live?

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.

IFC Viewer for Microsoft Teams: Model Collaboration Without Leaving Your Project Environment

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.