Connect BIM to the systems your business runs on.
Connect model context to the records your business uses. The xeoVision framework combines xeokit Data Engine outputs with application foundations and integration services, so BIM properties can be mapped to ERP, project management and document systems through their APIs and your access policies.
Where BIM data usually stops
In most organizations the model and the commercial systems never meet. Quantities get retyped into a spreadsheet, asset tags get reconciled by hand, and the model stops being useful the moment the project moves from delivery into operation.
The blocker is rarely ambition. It is that the data is locked inside a viewer that was never designed to let it out.
Open outputs are the whole mechanism
The xeokit Data Engine writes object properties and metadata as JSON, and geometry as GLB and XKT. These are ordinary formats your own systems can read.
That turns “connect BIM to our ERP” from a request for a vendor feature into a normal data integration your team or your integrator can scope, build and own.
What a connection looks like in practice
A typical integration maps model object identifiers to the identifiers your business already uses — asset tags, cost codes, equipment numbers — and then keeps the two in step. Once that mapping exists, the model can act as a spatial index into records that live where they belong.
Common targets are ERP systems including SAP, project management and delivery tools, and document management or records systems.
Being precise about what this is
These are development possibilities, not preconfigured connectors shipping in the box. There is no built-in SAP integration and no automatic Power BI connector. What xeoVision provides is open, readable data and an application whose source is available as an add-on to a xeokit SDK licence, so the integration can be built properly against your systems and your access rules.
That is a slower promise than a logo on a connector page, and a considerably more reliable one.
