Common Data Environment (CDE)

A common data environment (CDE) is a shared information environment for the structured management and exchange of information in construction and BIM projects. Project data such as models, drawings, documents and other information is centrally organised, versioned and made available through defined review and approval processes.

The aim is to create a reliable information base that allows all project participants to work with the latest approved data at all times.

A CDE should not be equated with a particular software solution. It encompasses both the technical environment and the agreed information management processes, roles and rules.

‍

Why is a common data environment important?

• Consistent data source: Models, drawings and documents are managed in a structured way in one central location or within a shared information environment.
• Up-to-date information: Version control and status labels make it clear which data is being worked on, shared or approved.
• Controlled information exchange: Clear statuses, responsibilities and handovers ensure that project participants use the intended information at each stage.
• Fewer media discontinuities: Email attachments, local file storage and parallel data versions are reduced.
• Traceable processes: Changes, reviews and approvals can be documented, and responsibilities can be clearly assigned.

‍

How does a CDE work in practice?

A CDE organises project information through defined states and workflows. DIN EN ISO 19650 distinguishes between four key information areas.

‍

‍

1. Work in Progress

This area contains working information that is created and developed within a team or specialist discipline.

Examples:

• Architectural models in progress
• Specialist designs that have not yet been reviewed
• Internal drawing versions
• Preliminary calculations

The information has not yet been approved for general project coordination.

2. Shared

Following an internal review, information can be made available to other project participants.

This area is used, for example, for:

• Providing reviewed specialist information
• Cross-disciplinary information exchange
• Coordinating different design versions
• Reviewing and further coordinating information within the project

The information is approved for shared use within the project but is not necessarily considered final, published or contractually binding project information.

3. Published

Following defined review and approval processes, information is assigned an authoritative status.

This may include:

• Approved models
• Construction drawings
• Coordinated documentation
• Authoritative project information

Any subsequent changes are managed through controlled change and approval processes.

4. Archive

Information that is no longer active is archived in a traceable manner.

This ensures that previous versions, decisions and project stages remain available at a later date, for example for documentation, operation or future alterations.

‍

What information is managed in a CDE?

Depending on the project, a shared data environment may contain many different types of information:

• BIM models and IFC files
• CAD drawings and plans
• Point clouds and existing-building data
• Floor plans, sections and elevations
• Tender and contract documents
• Review and approval documents
• Minutes and reports
• Status, review and handover information
• As-built documentation
• Operational and handover data

Centralised storage alone is not enough. Information must be clearly structured, versioned and assigned to a defined status.

‍

Key functions of a CDE

• Version management: Changes to files and models are documented in a traceable way. This makes it possible to identify the current information status and the versions used previously.
• Roles and permissions: Not all project participants need the same access and editing rights. Roles and permissions control who can view, edit, review or approve information.
• Review and approval processes: Information does not automatically progress from a working version to authoritative project information. Defined workflows ensure that data is reviewed before approval.
• Information status and handovers: Defined statuses show whether information is still being worked on, has been shared, has been approved or has been archived.
• Traceability: Changes, approvals and responsibilities are documented. This makes it possible to determine when information was changed or approved and by whom.

‍

CDE and BIM

A common data environment is a key component of BIM information management.

• BIM describes the method used to create, exchange and use structured building information throughout design, construction and operation.
• The CDE provides the organisational and technical framework in which this information is managed, reviewed, approved and archived.
• A software platform alone does not therefore automatically constitute a complete CDE. Defined information statuses, responsibilities, review processes, approvals and archiving procedures are also essential.

A CDE is therefore more than a place to store BIM models. It describes the shared information environment and the rules used to manage project information throughout its entire lifecycle.

Depending on the project, the technical implementation may consist of a single CDE platform or several interconnected systems.

‍

CDE vs BIM collaboration platform and document management system (DMS)

CDEs, BIM collaboration platforms and document management systems can be closely connected from a technical perspective, but they fulfil different functions.

Document management system (DMS)

A document management system (DMS) primarily focuses on the structured management, versioning and archiving of documents. It is often used across an entire organisation and is not specifically designed for BIM processes.

A DMS can form part of the technical CDE environment, but it is not the same as a CDE.

BIM collaboration platform

A BIM collaboration platform is a cloud solution for operational, model-based collaboration. It provides the basis for coordinating discipline models, model-related communication and issue management.

A BIM collaboration platform is usually used as a standalone solution that complements the CDE. It is model-based, which means that communication always relates to specific elements, issues or processes within a BIM model. By comparison, the CDE covers all project documents and files.

Common data environment (CDE)

The CDE provides the overarching organisational and technical framework for information management within the project.

In simplified terms, the distinction can be summarised as follows:

• DMS → primarily manages documents
• BIM collaboration platform → supports operational collaboration on the BIM model
• CDE → organises and controls all project data, information and workflows

In practice, the systems used may overlap technically. What defines a CDE is therefore not a particular set of software functions, but the implementation of the agreed information processes.

‍

What makes a CDE a CDE?

Not every platform that provides models and documents automatically constitutes a complete CDE.

Among other things, a project must define:

• Which information is still a work in progress?
• When may information be shared?
• Who may review and approve information?
• Which version is authoritative?
• How are changes documented in a traceable way?
• Which roles and access rights apply?
• How is approved information archived?

The focus of a CDE is therefore not on individual software functions, but on the consistent and traceable control of information.

‍

CDEs for existing buildings

A CDE can also play a central role in refurbishment and existing-building projects. Digital building survey data, point clouds, existing drawings and BIM models are often created at different project stages and used by different participants.

A structured common data environment helps bring this information together consistently.

One possible information flow is:

Digital building survey → Point cloud → Existing-building model → IFC → CDE → Design and coordination → As-built documentation

This maintains a clear record of which data originated from the existing-building survey, which information was processed further and which version was approved for design or construction.

This can be particularly relevant for existing-building projects because the same building data may be used for different applications, such as design, energy-efficient refurbishment, tendering, BIM coordination or subsequent building operation.

‍

CDE and information requirements

A CDE does not exist in isolation. It is closely linked to a project’s information requirements and BIM processes.

The Auftraggeber-Informationsanforderungen (AIA), or Employer’s Information Requirements, define which information is needed for specific BIM use cases.

The BIM-Abwicklungsplan (BAP), or BIM Execution Plan, specifies how these requirements will be implemented within the project.

The common data environment then provides the shared information environment through which this information is made available, reviewed, approved and managed.

In simplified terms:

• AIA → What is required?
• BAP → How will it be implemented?
• CDE → Which rules govern how information is provided, reviewed, approved and archived?

‍

Common mistakes and misconceptions

• “CDE = cloud storage”: A central file repository alone is not a complete CDE. Information statuses, roles, version control and workflows are also essential.
• “CDE = BIM collaboration platform”: A collaboration platform is a technical software solution and can form part of a CDE. The CDE also encompasses the agreed information management processes and rules.
• “Document management systems are outdated”: Document management systems continue to perform important functions. However, their focus is more strongly centred on documents than on model-based BIM information management.
• No clear responsibilities: Without defined roles, it remains unclear who is authorised to review or approve information.
• Unclear file structures: Inconsistent naming and metadata make searching and collaboration more difficult.
• Parallel storage locations: If information is also distributed by email or stored in local project folders, conflicting data versions can quickly arise.
• Missing approval processes: Without clear statuses, working information may accidentally be treated as authoritative.
• Introducing the CDE too late: The information structure, roles and processes should be defined before data exchange begins wherever possible.
• Focusing on software rather than the information process: Even a powerful platform functions as a CDE only when roles, statuses and workflows are clearly defined.

‍

FAQ