Large programmes are delivered by many organisations, and each one brings its own CDE. CDE Sync™ connects those platforms so information flows between partners automatically, and the Utopiaverse™ turns the combined data into one record the client and delivery partners can search and analyse.
Why big projects end up with many CDEs
A metro, motorway or energy programme might involve a client authority, several design consultants, main contractors in joint venture and dozens of subcontractors. Each has invested in its own platform and processes. The client may require submissions in Aconex or ProjectWise, the designers work in Autodesk Forma, and the contractor runs Procore or SharePoint. Forcing everyone onto one platform is expensive, slow to negotiate and often fails when a new partner joins mid-delivery.
What breaks between platforms
The cost appears at every boundary. Deliverables are downloaded from one system and uploaded to another. Metadata is re-keyed to match a different schema. Status changes in one platform do not reach the other. Over time the copies drift, and teams make decisions using superseded information.
How CDE Sync™ connects the programme
CDE Sync™ links each partner's platform to the others through rules agreed at the start of the work. It can push design deliverables from a consultant's Forma hub into the client's submission platform, pull subcontractor information into the main contractor's federated environment, and keep shared folders aligned in both directions. Metadata is translated between schemas as files move, so ISO 19650 fields stay correct on both sides, and every transfer is logged.
Each partner keeps its own platform and its own permissions. CDE Sync™ only moves what the agreed rules allow, using service accounts on each side, and never stores files on Utopia Digital's systems.
Adding partners as the programme grows
Programmes change shape over time. New packages are let, partners join and leave, and joint ventures form and close. Adding a partner to a connected programme means connecting one more platform and mapping its folders and fields, which takes days and avoids writing a fresh set of manual transfer procedures.
Seeing across the programme with the Utopiaverse™
Connecting platforms solves the flow of information during delivery. The next question is insight: which packages are behind, where open issues cluster, and how one project compares with another. Answering those questions needs the data in one place and in a consistent form.
The Utopiaverse™ provides that. Data from connected platforms lands in the client's or contractor's own Azure, translated into one schema aligned to ISO 19650. AI Insights then lets people browse folder and version history across every package and platform and ask questions in plain language, with answers that cite their source files. Because the record sits in your own tenancy, it stays with you after the programme closes and is ready to support operations and future work.