You use AI across a joint venture's CDEs by giving each partner a governed copy of the joint venture record in its own Azure tenancy, kept current by sync, and running AI over that copy alongside the partner's other projects. CDE Sync™ keeps each partner's copy aligned with the joint venture platforms, and the Utopiaverse™ lets each partner see and question that record together with the rest of its portfolio.
Why joint ventures are complicated for AI
A typical joint venture runs on several platforms. The client mandates its CDE, such as Oracle Aconex or Asite. The joint venture sets up its own environment, perhaps InEight or Autodesk Forma. Each partner keeps working content in its own systems, and design consultants work in ProjectWise. The joint venture's AI tools, if any, only see the joint venture platform. Each partner's AI only sees its own systems.
Ownership adds a further layer. The joint venture agreement usually sets out who owns what, who may use it and what happens to the record when the joint venture closes. Any AI approach has to respect those terms. Our article on joint venture CDEs covers the record-keeping side.
The partner-copy model
The model that tends to work gives each partner a copy of the content it is entitled to, in its own tenancy.
The joint venture agrees which content each partner may hold, consistent with the agreement.
CDE Sync™ keeps each partner's copy current from the joint venture and client platforms.
Each partner indexes its copy for AI under its own security and residency policies.
At close, CDE Archive™ captures the final record into each partner's tenancy.
Each partner then controls its own AI, without depending on the other partners' systems or on the joint venture platform remaining active.
What partners use AI for
Commercial teams trace the history of claims, variations and notices across client and joint venture platforms.
Design managers find every RFI, review comment and drawing revision touching an interface.
Executives see the status of the joint venture alongside the partner's other projects.
Bid teams draw lessons and reference content from past joint ventures for new pursuits.
That last use depends on the record being available after the joint venture ends, which is why each partner's own copy matters.
Governance points to agree early
What each partner may copy, and for what purposes, including AI.
Which regions and tenancies may hold the copies.
How access is controlled inside each partner's organisation.
Retention periods during delivery and after close.
How personal information in correspondence is handled.
Putting these points into the joint venture's information management plan early avoids disputes later. Utopia Digital's security evidence, including SOC 2 Type II and Cyber Essentials, is in the Security Trust Portal, and residency options are on the global data region map.
Build your own AI or use AI Insights
Once a partner's copy sits in its tenancy, the partner can build its own AI over it with Azure AI services, including an MCP server that lets approved AI assistants search the index. Or it can use AI Insights, which runs natively on Azure in the partner's tenancy and answers questions across every connected CDE with cited sources.
Joint ventures and the Utopiaverse™
For each partner, the Utopiaverse™ brings the joint venture record together with every other project in its portfolio, across every CDE, in one connected record in its own Azure. AI Insights answers questions across all of it with RAG and OCR search and cited sources. The file viewer opens documents from the client platform, the joint venture platform and the partner's own systems in one place, and dashboards report on document control across the portfolio.
Executives gain visibility of joint venture projects alongside wholly owned work, and the partner keeps a searchable record long after the joint venture closes.
See the Utopiaverse™ in the monthly live demo, or talk to the team about your joint venture projects.