You build a federated common data environment (CDE) across subcontractors by connecting each party's own platform to a shared environment, with agreed rules for which information flows, in which direction and when. CDE Sync™ connects every subcontractor CDE to the principal's platform, translates metadata between schemas and logs every transfer, so the principal sees one federated record while each subcontractor keeps working in its own system.
What a federated CDE is
A federated CDE is a set of separate platforms that behave as one shared record for the project. Each organisation keeps its own CDE, permissions and processes, and agreed information is exchanged automatically between them. The principal contractor or client sees a complete, current picture without forcing every subcontractor onto a single platform.
The alternative, mandating one platform for everyone, often struggles in practice. Subcontractors have their own enterprise agreements, trained staff and internal processes, and asking them to duplicate their work in someone else's platform adds cost and resistance. Our article on supply chain CDE integration explores why.
Where federation is most valuable
Line-wide and corridor programmes are the clearest example. A principal contractor may need to pull models and documents from five or six subcontractor CDEs into one federated model for coordination, clash detection and reporting. Joint ventures and alliances have similar needs, where each partner keeps its own environment but the alliance needs a shared view. Large building projects with many trade contractors benefit too, because the principal can receive shop drawings and as-built information without retyping metadata.
How to build a federated CDE, step by step
Decide which platform holds the federated record, usually the principal's or the client's CDE.
List every subcontractor and the CDE each one uses, such as Autodesk Forma, Procore, 12d Synergy, Asite or SharePoint.
Agree the information each party must share, the folder structure in the federated record and the metadata standard, usually based on ISO 19650.
Write those rules into subcontracts or the project's information protocol so every party knows what is expected.
Request service accounts on each subcontractor platform and on the federated platform.
Connect each platform in the CDE Sync™ wizard, map metadata to the federated standard and set the schedule.
Onboard subcontractors one at a time, confirm each connection with a test, then monitor through the audit log.
Governance that keeps federation working
Technology is only half the work. A federated CDE needs a clear owner, usually the principal's information manager, who maintains the mapping, onboards new subcontractors and handles changes. It needs a published standard so subcontractors know how to name and describe their information. It also needs an agreed approach for the end of each subcontract, so the principal keeps the record when a subcontractor's platform access ends. Putting those pieces in place early means the federated record stays trustworthy as parties join and leave over the life of a long programme.
Starting small and growing
A federated CDE does not have to start with every subcontractor at once. Many principals begin with the two or three parties that generate the most information, such as the main design consultant and the largest trade packages, and add others as the pattern proves itself. Each new connection reuses the agreed standard and mapping, so onboarding gets quicker each time. Subcontractors also see the benefit early, because automated exchange removes the double handling they would otherwise carry. That goodwill makes later onboarding easier and helps the federated record become the place people trust.
Security across organisations
Federation crosses organisational boundaries, so control matters. Each party keeps its own permissions, and only the information your rules allow moves between organisations. CDE Sync™ streams files directly between platforms without storing them, encrypts data in transit and processes it in the Azure region you choose. Utopia Digital holds SOC 2 Type II and Cyber Essentials. See the Security Trust Portal.
Federated CDEs and the Utopiaverse™
A federated CDE is a natural part of the Utopiaverse™, the connected record Utopia Digital builds in your own Azure. CDE Sync™ federates live platforms, CDE Backup™ keeps an independent copy, CDE Migrate™ handles platform changes and CDE Archive™ captures the record when subcontracts close. AI Insights then searches across every subcontractor's information at once. See also joint venture CDEs and How Do I Connect My CDE Platforms?
See federation in the monthly live demo, or talk to the team about your supply chain.
