Skip to content

Take your BIM data beyond the viewer.

Extract project data for reporting and further processing. Use that information in Power BI, an AI agent or your own business-data workflow.

The geometry is only half of a BIM model. The other half is the object data — identifiers, classifications, property sets and base quantities — and that half is what your business systems actually want.

For supported IFC and Revit workflows, xeokit Data Engine extracts model information as JSON — see what comes out of an RVT file, or how the SDK and the Data Engine divide that work. Application foundations in the xeoVision framework make that information accessible alongside the model view. The available identifiers, properties and quantities depend on the source file and the processor used; check a representative file against your reporting requirements.

Map the extracted fields and object identifiers to the records used by Power BI, an asset system or an approved AI agent. That connection is scoped integration work Creoox or your partner can implement. It does not require moving your reporting system into the viewer, and it is not a preconfigured connector included with every deployment.

That distinction matters commercially: because the outputs are open, the reporting workflow you build is not dependent on continuing to use this viewer.

Choose where processing and project data run, and agree the mapping, refresh process and access requirements through our BIM integration services.

How it works

  1. 01 Extract the project information you need.
  2. 02 Prepare and map the data for your chosen tool.
  3. 03 Use it for reporting, analysis or automation.

What BIM data can you extract from IFC and Revit files?

Identifiers, classifications, property sets and base quantities, delivered as JSON by xeokit Data Engine. Which fields appear depends on the source file and the processor used, so check a representative model against your reporting requirements before committing to a data workflow.

Is there a ready-made Power BI connector?

No. The extraction produces open JSON outputs, and mapping those fields and object identifiers to Power BI, an asset system or an approved AI agent is scoped integration work that Creoox or your partner implements. It is not a preconfigured connector included with every deployment.

What happens to the reporting workflow if you stop using the viewer?

It keeps working. Because the extracted data is written to open outputs rather than held inside the viewer, the reporting you build on it does not depend on continuing to use this application.