Bring the whole project into one view.
Load multiple models into a shared project view. Review the relationship between disciplines and keep the wider project in context.
Engineering projects arrive as separate files from separate teams. Reviewing them one at a time hides exactly the thing you need to see: how they fit together.
The xeoVision framework combines model-viewing workflows with xeokit SDK visualization. Bring architecture, structure and building-services models into one browser view while retaining each model’s object tree and properties. Select an object to inspect its information in the wider project context. Try a combined view in the browser-based BIM viewer.
Selected xeokit Data Engine processors prepare engineering source files for viewing. Supported web-ready models can use the SDK’s loaders directly. Review the format and processor matrix for the files your teams exchange, then filter the combined view around a discipline or review question. The components behind both steps are described separately. Model alignment and useful properties depend on the project data you supply.
How it works
- 01 Bring relevant models together in a single view.
- 02 Navigate the combined project and inspect its objects.
- 03 Use the same context when reviewing with your team.
Can you view IFC and Revit models together?
Yes. Files prepared by different xeokit Data Engine processors can be loaded into the same view, so an IFC model and a Revit RVT model can be reviewed side by side. Check a representative file from each source before agreeing the workflow, because what each model contributes depends on how it was authored and which processor prepared it.
Does federating models merge them into one model?
No. Each model keeps its own object tree and properties inside the combined view. Federation is a viewing arrangement rather than a conversion step, so nothing is flattened into a single merged file and the source data stays as it was supplied.
How are the models aligned with each other?
Models are positioned using the coordinates they already carry. Files authored against a shared project origin line up; files that were not have to be corrected in the authoring tools or handled as part of the integration work. A common origin is not inferred for you.
