Common Data Environment (CDE)
CDE platforms for BIM collaboration: shared repositories, approval workflows, and ISO 19650 compliance.
Definition & Context
A Common Data Environment (CDE) is the single, agreed source of information for a project — a managed repository where all model files, documents, and data are stored, versioned, and shared under ISO 19650 status codes (WIP → Shared → Published → Archived).
CDE platforms include Autodesk Construction Cloud / BIM 360, Trimble Connect, Bentley ProjectWise, Viewpoint, and Asite. A compliant CDE enforces access control, an audit trail, revision history, and a formal approval workflow between states.
Why It Matters
The CDE is where coordinated, current information lives — eliminating the ‘which version is right?’ problem that plagues email-based exchange and underpinning every ISO 19650 workflow.
A CDE is defined by its process, not just its storage: what makes it “common” is the shared status/approval workflow (WIP → Shared → Published → Archived) with access control and an audit trail, so any party can trust that Published information is approved and current. The platform (ACC, Trimble Connect, ProjectWise, Asite) matters less than agreeing the naming convention, container structure, and who authorises each state transition.
Best Practices
- Enforce the status-code workflow with gated approvals between WIP, Shared, and Published.
- Maintain a strict, agreed file-naming convention for every information container.
- Keep a full audit trail and never delete superseded revisions — archive them.
- Control access by role so parties only edit what they own.
Common Pitfalls
- A shared folder masquerading as a CDE with no status control or audit trail.
- Files exchanged by email outside the CDE, breaking the single source of truth.
- Inconsistent naming that makes containers unsearchable.
- No formal approval gate between Shared and Published states.
Core Commands & Practical System Operations
Executing Common Data Environment (CDE) effectively relies on specialized CAD/BIM command workflows and system variable configurations: BIM & CAD tools: WALL, FLOOR, ROOF, FAMILY, XREF, IFCEXPORT. Setup: Coordinate shared project base points, configure Level/Grid datum.
Standard Engineering Workflow for Common Data Environment (CDE)
1. Spatial Programming & Shared Georeferencing
Establish project base points, survey coordinates, building storeys, and column grid systems coordinated across architectural, structural, and MEP consultants.
2. LOD 200 - 300 Parametric Component Assembly
Model multi-layer architectural assemblies (curtain walls, structural framing, floor slabs, MEP risers) using intelligent parametric family components.
3. Interdisciplinary Clash Detection & Coordination
Federate discipline models in Navisworks or Solibri. Run automated hard/soft clash tests and track issues using BCF (BIM Collaboration Format) workflows.
4. 2D Construction Documentation & Quantity Schedules
Extract live plans, building sections, elevations, and automated component schedules (doors, windows, concrete volume) linked directly to the central model.
Common Failure Scenarios & Troubleshooting
| Failure / Geometric Issue | Root Cause & Mitigation Strategy |
|---|---|
| Architectural and Structural models do not align when linked | Shared coordinates were not acquired. Ensure both teams use 'Acquire Coordinates' from a designated master site model. |
| Wall joints and multi-layer materials do not clean up cleanly | Layer core priorities are misconfigured. Ensure structural cores have Priority 1, substrate Priority 2, insulation Priority 3, and finishes Priority 4/5. |
| IFC export drops custom attributes and scheduling properties | Map property sets using custom IFC export translation tables before exporting to external coordination software. |
Industry Standards & Compliance Codes
- ISO 19650-1/-2 (Organization of information about construction works - BIM)
- buildingSMART openBIM & IFC 4x3
- AIA Document E202 (Building Information Modeling Protocol)
- National CAD Standard (NCS)
Sources & Further Reading
Related Concepts
- ISO 19650 — defines the CDE and its status codes
- BIM Execution Plan (BEP) — sets CDE naming and workflow rules
- openBIM & buildingSMART Standards — open formats exchanged via the CDE
- Clash Detection — coordination on models pulled from the CDE
- National BIM Standards — jurisdiction-specific CDE mandates