This is a delivery-method resource, not project-specific design. Electrical protection, cable sizing, cooling capacity, fire strategy and structural loads require the appointed designers and the applicable codes. Technical review of this cluster by a named senior BIM/MEP lead is pending; do not treat it as sealed guidance.
Multi-discipline BIM coordination fails without a single source of truth. If the mechanical model on the architect's laptop is version 47 and the electrical team is coordinating against version 43 from an email attachment, clashes will be found and lost repeatedly. The common data environment solves this by establishing where information lives, in what state, and who can access it.
What a CDE actually is
ISO 19650-1 defines the common data environment as the agreed source of information for any given project or asset. It is not simply a shared drive or cloud folder. A CDE has structure: defined information states, a workflow for promoting information between states, access controls, and revision management.
The CDE may be a single platform or a federated environment across multiple systems, provided there is agreement on which system holds the single source of truth for each information type. For most projects, a single platform is simpler to govern.
Information states
ISO 19650 describes a state model for information containers (files). The typical states are:
CDE information states
| State | Description | Who can access | Typical content |
|---|---|---|---|
| Work in Progress (WIP) | Information being developed by the authoring team | Authoring team only | Draft models, working documents |
| Shared | Information shared for coordination, review or comment | Project team (read), authoring team (edit) | Models for clash detection, drawings for review |
| Published | Formally issued information, approved for its stated purpose | Project team and client (read) | Stage deliverables, approved-for-construction |
| Archived | Superseded or historical information retained for record | Restricted read access | Superseded versions, audit trail |
The state names and exact definitions can vary — some CDEs use Review as an intermediate state, others collapse Shared and Review. The principle is consistent: information moves from draft to shared to published to archived, with defined criteria for each transition.
Folder structure and naming
A CDE folder structure typically mirrors the state model and organises content by discipline, zone or package. There is no single correct structure — the BEP should define it. Common approaches:
- State-first: top-level folders for WIP, Shared, Published, Archived; sub-folders by discipline.
- Discipline-first: top-level folders by discipline; sub-folders for states.
- Zone-first: top-level folders by building or zone; sub-folders for discipline and state.
Naming conventions must be defined in the BEP. ISO 19650 and UK BIM Framework provide example structures — project code, originator, discipline, type, zone, level, sequence, description, status, revision. The exact fields depend on project needs.
Access control
Not everyone needs access to everything. The CDE should implement role-based access control:
- Authoring rights to own-discipline WIP folders.
- Read access to other disciplines' Shared folders for coordination.
- Publish rights restricted to defined roles (BIM manager, discipline lead).
- Client access to Published state only, unless otherwise agreed.
- External parties (subcontractors, vendors) access scoped to relevant packages.
For data-center projects with security-sensitive clients, ISO 19650-5 provides guidance on protecting sensitive information. Access logs, data classification and controlled export may be required.
Platform options
A CDE can be implemented on various platforms. Common choices:
CDE platform options
| Platform | Strengths | Considerations |
|---|---|---|
| Autodesk Construction Cloud (ACC) | Integrated with Revit, Model Coordination, issue tracking | Licensing cost, Autodesk ecosystem lock-in |
| Bentley ProjectWise | Strong for infrastructure, large file handling | Learning curve, cost for smaller projects |
| Trimble Connect | Multi-format, open platform | Less native Revit integration than ACC |
| Aconex (Oracle) | Document control, transmittal workflows | Model coordination less mature than ACC |
| SharePoint/Teams | Ubiquitous, low barrier | Needs configuration to enforce states; not a native CDE |
| Custom/client bespoke | Fits client IT policy | Integration effort, ongoing maintenance |
The platform matters less than the process. A well-governed SharePoint can outperform a poorly administered BIM 360. The BEP should specify the platform, the state model, the naming convention, and who administers it.
Data-center-specific considerations
- Model file size — dense MEP models can be large; ensure the platform handles uploads and federation.
- Security classification — clients may require on-premise hosting or specific data residency.
- Vendor access — prefabrication and equipment vendors need scoped access to upload models.
- Coordination cadence — weekly federation cycles need reliable state transitions.
- Issue tracking — integrate issue management with the CDE (BCF, ACC issues, linked registers).
FAQ
- Is SharePoint a valid CDE?
- It can be, if configured with defined states, version control, access permissions and naming enforcement. Out-of-the-box SharePoint is a file store, not a CDE. Configuration or third-party add-ons can bring it closer to CDE functionality.
- Who administers the CDE?
- Typically the BIM manager or a dedicated CDE administrator. The role includes setting up folder structure, managing access, enforcing naming, and promoting information between states.
- Can we have multiple CDEs on one project?
- ISO 19650 allows federated CDEs but emphasises a single source of truth for each information type. If multiple platforms are used, the BEP must specify which platform holds the authoritative version of each deliverable.
Sources
- 1. ISO, ISO 19650-1:2018 — Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Part 1: Concepts and principles (2018). https://www.iso.org/standard/68078.html. Accessed 2026-09-03.
- 2. ISO, ISO 19650-2:2018 — Information management using building information modelling — Part 2: Delivery phase of the assets (2018). https://www.iso.org/standard/68080.html. Accessed 2026-09-03.
- 3. BSI, ISO 19650 — Building Information Modelling (BIM) (2026). https://www.bsigroup.com/en-GB/products-and-services/standards/iso-19650-building-information-modelling-bim/. Accessed 2026-09-03.
- 4. UK BIM Framework, Information management according to BS EN ISO 19650 — Guidance Part 1: Concepts (2nd edition) (2019). https://ukbimframework.org/wp-content/uploads/2019/10/Information-Management-according-to-BS-EN-ISO-19650_-Guidance-Part-1_Concepts_2ndEdition.pdf. Accessed 2026-09-03.