Managing vast quantities of project data across multiple disciplines, contractors, and timelines is one of the defining challenges of large construction projects. Without a structured framework, information becomes fragmented, version conflicts multiply, and the cost of rework climbs. ISO 19650 addresses this directly by defining how information should be produced, shared, and managed throughout the lifecycle of a built asset — and at its core sits the Common Data Environment (CDE). This guide explains how to structure and implement a CDE under ISO 19650 for large, multi-disciplinary projects.
Understanding ISO 19650
ISO 19650 is an international standard for managing information using Building Information Modelling (BIM). Published by the International Organization for Standardization, it builds on the UK's established BIM Level 2 framework and extends it into a globally applicable structure. The standard is organised into five parts:
- Part 1: Concepts and principles — the vocabulary and overarching information management framework
- Part 2: Delivery phase of assets — how information is exchanged during design and construction
- Part 3: Operational phase — managing information after handover
- Part 5: Security-minded approach — protecting sensitive asset information
For large construction projects, Parts 1 and 2 are the operational foundation. They define the chain of information requirements — from the client's Asset Information Requirements (AIR) to the Employer's Information Requirements (EIR), through each appointed party's BIM Execution Plan (BEP) — creating a contractually enforceable information management structure.
The standard is mandatory on publicly funded projects in the UK, and increasingly referenced in infrastructure procurement across the EU, Middle East, and Australia. According to the UK BIM Framework, adoption has grown significantly since ISO 19650 replaced PAS 1192 in 2019, with most Tier 1 contractors now requiring ISO 19650 compliance from their supply chains.
What Is a Common Data Environment
A Common Data Environment is the single source of truth for all project information. Rather than relying on email chains, shared drives with inconsistent naming, or discipline-specific file servers, a CDE provides a governed platform where every team member — architect, structural engineer, MEP consultant, and contractor — accesses and contributes to the same controlled dataset.
Under ISO 19650, information within a CDE moves through four defined states:
- Work in Progress (WIP) — files being actively authored, not yet shared
- Shared — information released for review and comment by other disciplines
- Published — information formally approved and authorised for use
- Archived — superseded information retained for audit and record purposes
This lifecycle prevents a common failure mode on large projects: teams acting on outdated or unapproved information. A structural engineer who downloads a Revit model from a CDE knows it is the current published version — not a WIP file someone shared via email last Tuesday.
Selecting the Right CDE Platform
Not all CDE platforms are equal in their ISO 19650 support, integration capabilities, or suitability for different project scales. Here is how the major platforms compare:
| Platform | ISO 19650 Support | Key Strength | Best Fit |
|---|---|---|---|
| Autodesk Construction Cloud (ACC) | Full | Deep Revit/Navisworks integration, clash workflows | Multi-discipline design coordination |
| Bentley ProjectWise | Full | Large infrastructure, civil and rail projects | Highways, rail, utilities |
| Trimble Connect | Full | Open IFC support, mixed-tool environments | Contractors with diverse toolsets |
| Aconex (Oracle) | Full | Audit trail, legal document control | Mega-projects, contractual correspondence |
| Procore | Partial | On-site construction management | Field teams, subcontractor coordination |
For most building projects, Autodesk Construction Cloud is the most integrated choice if the design team works in Revit and Navisworks. For civil and infrastructure work, Bentley ProjectWise's handling of large point cloud and survey datasets makes it the preferred option. Trimble Connect suits environments where multiple BIM authoring tools are in use and IFC as the exchange format is a priority.
Steps for Implementing a CDE Under ISO 19650
Effective CDE implementation follows a structured sequence. Skipping steps — particularly around naming conventions and role assignment — is the most common cause of CDE adoption failures on large projects.
Step 1 — Define Information Requirements Before configuring any platform, document the Employer's Information Requirements. The EIR specifies what information is needed, in what format, at what Level of Development, and at which project milestones. This document drives every downstream configuration decision.
Step 2 — Establish the Folder Structure and Naming Convention ISO 19650 prescribes a specific file naming convention built from defined fields: project code, originator, volume/system, level/location, type, role, and number. A typical filename looks like:
PRJ-ARC-ZZ-00-DR-A-0001
Where PRJ is the project code, ARC is the originator (architect), ZZ is the volume, 00 is the level, DR is the document type (drawing), A is the role code, and 0001 is the sequential number. Establishing this convention before the first file is uploaded prevents the renaming chaos that plagues projects that adopt it retrospectively.
Step 3 — Configure Roles and Permission Levels Each CDE user is assigned a role that determines what they can upload, review, approve, or archive. Typical roles include: Author, Checker, Approver, and Coordinator. The approval workflow — who must sign off a model before it moves from Shared to Published — should mirror the contractual responsibility structure, not just the organisational chart.
Step 4 — Migrate Existing Data For projects transitioning mid-stream, existing drawings, models, and documents must be classified and migrated into the CDE under the new naming convention. This is time-consuming but non-negotiable — a CDE containing some ISO 19650-compliant files and some legacy files with inconsistent naming defeats its own purpose.
Step 5 — Train All Participants CDE adoption fails most often because of user behaviour, not technology. Training must cover not just how to upload and download files, but why the workflow exists — particularly the distinction between WIP and Shared states, and the consequences of bypassing the approval step.
Step 6 — Govern and Audit Continuously Assign a BIM Information Manager to review CDE usage monthly: are files being uploaded to the correct containers? Are naming conventions being followed? Are approvals happening within the agreed response times? Regular audits catch drift before it becomes embedded practice.
Benefits of CDEs for Large Projects
The business case for a properly structured CDE is well established across the industry.
Clash detection at the right time. When all discipline models are published to a shared CDE on a consistent schedule, federated models can be generated automatically for clash detection in Navisworks or Solibri. Clashes found in the model cost a fraction of what they cost to fix on site — McKinsey & Company estimates that rework accounts for 30% of construction costs on complex projects (McKinsey Global Institute, Reinventing Construction, 2017).
Reduced information requests. A significant proportion of RFIs on large projects stem from teams working from different versions of the same drawing. A CDE with a single Published container eliminates version ambiguity and measurably reduces RFI volumes — a finding consistently reported by contractors using Autodesk Construction Cloud and Aconex on major infrastructure programmes.
Audit trail for claims and disputes. Every upload, review comment, approval, and download in a CDE is time-stamped and attributed to a named user. This audit trail has significant contractual value when disputes arise over what information was available to whom and when.
Handover and facilities management. ISO 19650 Part 3 extends the CDE into the operational phase. Asset information — equipment schedules, maintenance records, O&M manuals — is structured within the same environment, enabling facilities management teams to query live asset data rather than hunting through handover boxes.
Overcoming Challenges in CDE Implementation
The most common barriers are cultural rather than technical.
Resistance to workflow change. Design teams accustomed to emailing files directly often resist the discipline of uploading to a WIP container and waiting for approval before sharing. The solution is clear governance — the BIM Execution Plan should explicitly state that files shared outside the CDE are not contractually valid — and visible leadership buy-in from project directors.
Naming convention discipline. A single team member uploading files with inconsistent names corrupts search results and automated clash workflows for everyone. Automated naming validation at upload — available in ACC and ProjectWise — reduces this significantly without relying on individual vigilance.
Initial setup cost and time. Configuring a CDE properly for a large project takes two to four weeks of specialist time. On a £50M+ project, this is a small fraction of the total cost and pays back rapidly through reduced rework and RFI management time. Phased implementation — starting with the architectural and structural disciplines before onboarding MEP and civils — reduces the initial complexity.
Frequently Asked Questions
Conclusion
Structuring a Common Data Environment under ISO 19650 is not a technology project — it is an information governance project that happens to use technology. The standard provides the framework; the platform provides the tooling; but the outcome depends on consistent discipline across every team that touches the model. When implemented properly, a CDE transforms a large construction project from a fragmented collection of siloed information into a single, auditable, version-controlled dataset that every discipline trusts.
At Adyantrix, our BIM consultants have implemented ISO 19650-compliant CDEs across large-scale architectural, structural, and infrastructure projects. Whether you are setting up a CDE from scratch, migrating from a legacy shared drive, or bringing a non-compliant supply chain into alignment, our team can design and manage the implementation end to end. Speak with our BIM consulting team to discuss your project's information requirements.
