Model federation
Discipline, vendor, and fabricator models combined into one federated Navisworks model the whole project navigates.
We federate the models your disciplines and vendors publish, restructure them around CWAs and work packages, and process every engineering revision, so planning and reporting read one current model.
Discipline, vendor, and fabricator models combined into one federated Navisworks model the whole project navigates.
The Navisworks selection tree rebuilt around CWAs, disciplines, and packages.
The federated model split along CWA boundaries, so packages, progress, and constraints line up with the model objects they cover.
Intake
Collect discipline, vendor, and fabricator models and agree formats, cadence, and ownership for each source.
Federate and restructure
Combine the files in Navisworks and rebuild the selection tree around CWAs, disciplines, and packages.
Split and verify
Cut the federated model along CWA boundaries and check attributes against the Data Requirements.
Maintain
Process engineering revisions weekly and push the updated model through to UDiTH and Power BI.
On an industrial project the 3D model arrives from many authors. Engineering issues discipline models from Smart 3D or Aveva tools, vendors and fabricators send their own files, and each one is structured for the office that produced it. Construction reads the same geometry another way, by CWA, by package, by what one crew will install next. An advanced work packaging program treats the model as a construction deliverable, attribute-complete and organized around the build, and holds it to that standard for the life of the project.
We build and maintain that model. We federate discipline and vendor files in Navisworks, rebuild the selection tree around CWAs, disciplines, and packages, and split the federated model along CWA boundaries, so a workface planning team selects a package and gets the exact objects a crew will install. We verify attributes against the project's Data Requirements, and when a package assignment is missing or a tag disagrees with the engineering lists, the exception is reported and worked to closure. When engineering issues a revision, we process it on the weekly cycle, geometry and attribution together, so the model loaded to the AWP software stays current and attribute-complete.
Prepared models flow into the tools your team already runs: planners navigate the plant in UDiTH (Universal Digital Twin Hub), Power BI reports color the model by EWP, material, and fabrication status, and the Project Portal carries the same 3D and 4D views to every stakeholder. Our team has federated, restructured, and maintained models on live capital projects, and everything we stand up runs on your infrastructure and stays with you when the engagement ends. The BIM resource hub covers the discipline itself, from federation to attribute governance; this page describes the work we deliver when we run it for you.
Navisworks Add-insFree add-ins that build work packages against the Navisworks model and move model data into Power BI.
3D for Power BIA Power BI custom visual that puts the prepared model inside project reports, colored by the status fields your dataset carries.
UDiTH PBI ConnectorA free connector that selects, fits, highlights, and colors UDiTH model objects from Power BI report pages.Bring the model files your project has today. We scope federation, restructuring, and the weekly revision cycle against them.