CDE — common data environment
A CDE is often confused with a folder in the cloud. The difference is single but fundamental: in a CDE, every document has a status and a version, not just a file name. As long as the binding version is recognized by a suffix in the file name ("_final_v3_ost"), the environment is not common — it is merely commonly accessible.
The minimum feature set
When a CDE does not solve the problem
A CDE brings order to documents. It does not bring order to operational data — quantities, acceptance statuses, assignment to work fronts. Deploying a CDE where the real problem is a missing register of quantities and statuses ends with a tidy archive sitting next to a still-unknown state of the works.
Related: approval workflow.
Sources
The substantive basis of this text. Items marked as own practice do not come from a document — they are delivery experience that cannot be verified with a publisher.
- DocumentCentralny Port Komunikacyjny sp. z o.o.OPW (CPK requirements document, in Polish) — BIM definitions and „Wymagania Wymiany Informacji (EIR)” as the specification of exchange information requirements for the asset (pp. 5, 8)
- Own practiceThe distinction between a CDE and a shared drive comes from implementation practice — the abbreviation “CDE” does not appear in the analyzed tender corpus
Where we write about this
Where information gets lost in construction document flow
Seven points where information on an infrastructure contract disappears or loses credibility — and what can be done about them without deploying a system.
Excel or a custom application — where the break-even point lies
When a spreadsheet stops being enough in a construction process and how to tell. Decision criteria, hidden spreadsheet costs, and when a custom application pays off.