Your own common data environment.
Build a common data environment with the xeoVision framework. Bring project files, federated models and review teams into a shared workspace, then shape access, delivery workflows and integrations around your process and the environment you choose.
What is a common data environment?
A common data environment is the single agreed place where a project’s information lives — the files, the models, the revisions and the record of who approved what. The idea is standard practice in AEC delivery. The difficulty is rarely the concept; it is that most CDE products expect your process to match theirs.
Why build one rather than buy one?
Because the process is the differentiator. Organizations that run complex delivery have usually already worked out how their approvals, revisions and hand-offs should work, and the cost of changing that to suit a product is higher than the licence.
Starting from xeoVision gives you a working viewer, federation and file handling from day one, and leaves the workflow around them yours to define. You are not writing a BIM viewer; you are writing the part that is specific to your business.
What you get from the start
The model side is already solved: multiple models in one view, the object tree and properties from the source files, saved views for recurring reviews, and sharing that separates project visibility from source-file access. Those are the parts that take longest to build and matter least to your competitive position.
Where it runs
A CDE holds commercially sensitive material, so the hosting question usually arrives early. xeoVision runs as a managed service, on dedicated infrastructure, or inside your own environment, and the xeokit Data Engine can process files as a standalone binary within your network. Which of those is appropriate depends on your obligations, not on a licence tier.
