Frame Federated BIM Reporting

• One dataset across every model
• Source and version stay traceable
• Faster coordination reporting

Frame was chosen because the coordination team needed to report across a federated view without flattening away the identity of its source models. Conventional exports made each discipline a separate reporting problem, while merged datasets often lost the information required to explain where an element or quantity came from. Frame connects directly to the ACC Model Coordination view, processes mixed Revit, IFC, and Navisworks sources, and provides a consistent schema for Power BI. The resulting report preserves provenance on every row and embeds the 3D model beside the data, supporting both portfolio-level summaries and detailed coordination reviews from the same connected dataset.

The team needed consistent columns across different authoring formats, reliable source-model attribution, and a way to report on models that were updated on independent schedules without losing version context.

Previously, each discipline model was exported and reported separately, then reconciled by hand in spreadsheets or dashboards. A fully merged export simplified totals but made it difficult to trace values back to the contributing file and version.

The federated reporting workflow provides a single analytical view across the coordination set while preserving the source and version of every element. Teams can compare disciplines, isolate a contributing model, review category totals, and move directly from a chart or table to the relevant geometry. Because Frame adds ACC models by reference, the process avoids another upload and maintains a clear relationship with the project’s coordination environment. This reduces manual reconciliation, improves confidence in cross-model totals, and gives BIM managers, coordinators, and project controls a shared reporting layer. The approach remains repeatable as the model set changes because provenance fields travel with the refreshed data.

The asset table uses the union of Revit, IFC, and Navisworks columns, while provenance fields retain source model, file type, child version, and seed version.