Common Data Environment (CDE) and ISO 19650: essential for BIM project success

A Common Data Environment (CDE) is a platform that centralizes the storage, management, and sharing of information in AECO projects. In the world of BIM, effective data management and collaboration are essential for the success of any project. The BIM CDE, as defined by ISO 19650, plays a crucial role in this process.

In this article, we will explore in depth what a BIM Common Data Environment is, why the ISO 19650 CDE is today a strategic element in digital information processes, and what characteristics a platform must have to truly comply with the standard.

An ISO 19650 compliant CDE is not just a simple cloud archive, but an environment governed by rules, states, workflows, and tracked responsibilities, designed to collect, manage, and disseminate each information container through a structured process.

What is a CDE (Common Data Environment)?

In the increasingly complex landscape of construction, efficient information management is fundamental for the success of projects. Common Data Environments (CDE) emerge as essential pillars of this management, revolutionizing the way we store, manage, and share critical data.

CDEs represent a breakthrough in the industry, offering a cloud-based platform that serves as a “single source of truth” for all participants in construction projects. This digital repository not only centralizes information such as Building Information Modeling (BIM) data, but also extends to crucial documents such as contracts, cost estimates, and material specifications.

CDEs provide instant, real-time access to project data for all stakeholders, wherever they may be. Architects, engineers, contractors, and project managers can collaborate without geographical limitations, accessing the CDE via computers, mobile devices, and other field tools.

CDEs are not just passive data repositories; they are dynamic platforms that support the entire project lifecycle. They allow for the storage, modification, and sharing of information and are the engines that drive efficiency and collaboration in the construction industry.

According to the definition of ISO 19650-1, the Common Data Environment is a single, shared, and agreed source of information for a specific project or asset, used to collect, manage, and disseminate each information container through a managed process.

“agreed source of information for any given project or asset, for collecting, managing and disseminating each information container through a managed process”

Three concepts are central to this definition:

• agreed: the CDE is an information source agreed upon by the parties and regulated at the start of the project, typically through the Information Specification and other information management documents;
• managed process: the standard does not describe the CDE as a simple repository but calls for a managed process through which information containers are collected, controlled, shared, and distributed;
• information container: the object of management is not the generic file but the information container, i.e., an identifiable set of information equipped with metadata, status, revision, classification, and responsibility.

For this reason, a true BIM CDE (common data environment) is based on three inseparable pillars:

• people, i.e., roles and information responsibilities;
• processes, i.e., verification, review, approval, and publishing workflows;
• technology, i.e., the platform that implements and enforces these processes.

If one of these elements is missing, especially the procedural component, it cannot be considered a true ISO 19650 compliant BIM CDE, but only an advanced document solution or cloud storage.

The Key Features of a CDE

A CDE represents a single repository for all project data, ensuring easy and organized access for stakeholders. This centralization not only promotes consistency within the project but also the accuracy of information, reducing errors and discrepancies among work teams.

The key features of a CDE are:

• secure access: security is a priority in CDEs, with controls that limit access only to those with specific permissions. Each organization has its own secure workspace, protected for the duration of the project and available as an archive even after completion;
• efficient data sharing: CDEs facilitate collaboration among stakeholders by allowing simultaneous access and real-time updating of data. This capability for sharing significantly improves communication through centralized documents and discussions, reducing misunderstandings and increasing overall efficiency;
• version control: users can track various versions of drawings, documents, and measurements. This is particularly crucial in the cost estimation process and construction takeoff, ensuring that all participants can work with the most up-to-date information.

In addition to these basic operational features, a CDE ISO 19650 must add some distinctive elements that separate it from a simple repository:

• management of information containers with standardized metadata;
• traced states of the information container;
• structured information workflows for verification, review, and approval;
• complete audit trail of actions taken;
• granular permissions by phase, role, content, and responsibility;
• openBIM interoperability, supporting standards such as IFC, BCF and, in more advanced cases, IDS and bSDD.

It is also important to distinguish between CDE Solution and CDE Workflow. The former is the software platform, while the latter is the information process that regulates states, transitions, reviews, and approvals. A platform without structured workflows is not a compliant CDE but rather a cloud archive with collaborative functions.

The Benefits of the Common Data Environment: Here’s Why a CDE is Important

The establishment of a shared environment for data plays an important role in project management and offers numerous benefits, including:

• access to the most up-to-date information: one of the main advantages of CDEs is their ability to ensure that all team members (architects, engineers, contractors, and managers) have instant access to the latest information. This promotes seamless collaboration by allowing simultaneous updates, thereby reducing the likelihood of errors and misunderstandings during project execution;
• consistency of information: the centralization of the CDE ensures data consistency and reduces discrepancies and errors among different teams. This way, cost estimates, measurements, and contracts are always current and reliable information, providing a solid foundation for informed decisions;
• increased productivity: CDEs significantly enhance productivity by streamlining access to project data and facilitating efficient communication among teams;
• transparency and accountability within the project team: with a CDE, transparency is ensured through secure and controlled access to data and a complete audit trail to monitor changes and updates. This not only builds trust among team members and clients but also strengthens internal collaboration, improving overall project management.

To fully understand the benefits, let’s take a practical example and consider how information is managed and shared in a project context.

Imagine the typical flow of information in a project as an intricate maze of data. This network of information develops chaotically, and ensuring that the right information reaches the right people at the right time becomes a titanic challenge. Often, this information resides in various isolated systems, and its exchange occurs manually, a process subject to human errors. These errors can incur significant costs and cause unwanted issues.

Now, instead, imagine a shared data environment, a central hub where information flows in an organized manner. This common environment allows for better control over the flow of information. Construction documents, as well as other information like revisions and issues, are made available only to project team members once they have been carefully reviewed, approved, and released for their intended purposes. This ensures greater reliability and reduces risks associated with unreliable information.

The Value of the ISO 19650 CDE: From Document Management to Information Management

The most important advantage of a ISO 19650 compliant BIM CDE is the transition from archiving to active information management. Each information container goes through defined phases—creation, verification, sharing, approval, publication, and archiving—and each step is tracked, authorized, and made verifiable.

This approach enables:

• reducing review and approval times;
• standardizing processes across different projects;
• improving data quality, not just document quality;
• facilitating audits, compliance checks, and the management of any disputes;
• strengthening the continuity of information between design, construction, and project management.

With usBIM.platform you have a secure space for collaborative work and BIM coordination

The Concept of CDE According to ISO 19650

The ISO 19650 standard defines the concept of Common Data Environment in detail. According to this standard, a CDE should support three different conditions of information containers:

Work in progress – in this phase, the information is being developed by the author or the designated team. This information is not visible or accessible to others.

Shared – the information in this phase has been approved for sharing with others. This stage indicates that the information is ready to be shared and discussed with other project members.

Published – this stage indicates that the information has been approved for use in detailed design, construction, or facility management. The information in this phase is ready for operational use.

Archived – in addition to these three conditions of information containers, the ISO 19650 standard also requires an archived container (ARCHIVED), which records all operations of the other information containers in the form of a ledger. This allows for the development of a combined and collaborative information model.

HBIM models and Cloud platforms | Collaboration process

The Information Container: The Basic Unit of the CDE

The notion of information container is central: ISO 19650 does not refer to files in a general sense, but to persistent information units that are retrievable within a file, system, or application hierarchy. An information container can therefore be an IFC model, a CAD document, a PDF, a spreadsheet, a technical report, or a federated model, as long as it is identified and managed through consistent metadata.

Such metadata typically includes:

• container status;
• revision code;
• classification;
• responsible party;
• issue date;
• purpose of the information.

In this framework, naming conventions and suitability codes also play a significant role, allowing for the unique identification of information containers and understanding their maturity level, intended use, and approval status. It is this structure that makes the ISO 19650 CDE a regulated information management tool, rather than just a mere storage environment.

Full operational traceability is one of the most stringent requirements of a compliant environment: every action on the information container—modification, comment, status change, approval, revision—should be permanently recorded and accessible. In this sense, versioning, audit trails, and workflow history are not ancillary functions, but central elements to ensure compliance, control, and verifiability.

The Regulatory Framework

The CDE fits into a complex regulatory ecosystem. At the international level, the ISO 19650 series comprises five parts: concepts and principles, asset delivery phase, operational phase, information exchange, and information security.

Alongside ISO 19650, the framework for an advanced CDE also includes:

• ISO 23386, related to the methodology for describing, creating, and maintaining properties in interconnected data dictionaries;
• IDS (Information Delivery Specification), the buildingSMART specification for machine-readable validation of IFC models;
• EN 17412, which introduces the concept of LOIN (Level of Information Need), i.e., the level of information requirement.

How to Choose the Right Common Data Environment for Construction Projects

In the dynamic field of construction, choosing the right Common Data Environment (CDE) can make the difference between the success and failure of a project. Here are the key factors to consider when evaluating a CDE:

1. usability and accessibility for all team members: an intuitive and easy-to-use CDE is essential for reducing the learning curve and ensuring that all team members can quickly adapt to the system. A user-friendly interface not only minimizes training costs but also accelerates system adoption, improving overall project efficiency;
2. seamless integration and interoperability: a flexible CDE should seamlessly integrate with the software used in construction, such as BIM tools. This ability for fluid data exchange between different systems enhances interoperability and simplifies complex workflows;
3. high security standards: given the sensitivity of the information involved in construction projects, a robust CDE must offer high security standards. Features such as role-based access control, advanced data encryption, and a complete audit trail are essential to protect data from unauthorized access and cyber threats;
4. economic sustainability: assessing the overall cost of the CDE is crucial to ensure a balanced budget for the project. This includes licensing fees, implementation costs, etc. It is also crucial to consider the level of access required by various stakeholders, seeking a solution with flexible pricing structures that adapt to the specific sizes and needs of each project;
5. customization for the diverse needs of stakeholders involved in the project: each construction project involves a diverse range of stakeholders with specific needs for data access, file types, and integrations. Finding a CDE that can effectively meet these various needs is essential to foster efficient collaboration and achieve successful project outcomes.

To rigorously evaluate a platform, it is useful to check for at least these functional requirements:

• management of information containers with structured metadata;
• compliant and tracked container statuses;
• configurable verification and approval workflows;
• task assignment based on roles;
• versioning with workflow history;
• complete and immutable audit trail;
• project dashboard for monitoring processes;
• structured forms and checklists for data collection;
• granular permission management;
• openBIM interoperability.

Another decisive criterion for selection concerns the system’s ability to support BIM role-based workflows rather than just named users. This way, processes can be standardized at the organizational level and easily adapted to the individuals actually involved in each project.

Practical Checklist: the 10 Requirements of an ISO 19650 Compliant CDE Platform

To objectively assess a BIM CDE platform, it’s not enough to verify if it allows uploading, sharing, and versioning files. A true ISO 19650 compliant CDE must support information containers, states, workflow, roles, audit trail, and interoperability. This is why an evaluation checklist based on technical and regulatory requirements can be useful.

This checklist can also be used as a practical criterion for comparing platforms. From an evaluative perspective, each requirement can be classified as compliant, partially compliant, or non-compliant. In this way, the choice of the Common Data Environment BIM is based not on generic commercial statements, but on verifiable elements: the ability to govern the lifecycle of the information container, ensure traceability, support regulated workflows, and ensure openBIM interoperability.

Real-time evaluation with the interactive ISO 19650 CDE checklist: click the answers and immediately get the score and compliance verdict.

The main CDE software on the market

The main providers of Common Data Environment (CDE) solutions are:

• usBIM.platform by ACCA software: the first Italian collaborative platform certified IFC by buildingSMART international designed to streamline all activities in the construction supply chain. It is governed by security systems for access, with accessibility according to predefined rules for the various actors involved in the process. The platform allows for online project navigation, management of the model in IFC format, viewing and modifying data, adding objects, and federating multiple IFC models. usBIM.platform supports a wide range of file formats, including IFC, DWG, DXF, PDF, 3D, Office, GIS, and point clouds, and offers functionalities for reviewing/validating project documentation, tracking actions, automatic backups, and data disaster recovery. usBIM.platform is registered in the STAR of the Cloud Security Alliance, ensuring high cloud security standards are provided and manages cloud data in compliance with the European regulation 2016/679 regarding privacy, known by the acronym GDPR (General Data Protection Regulation). usBIM.platform adheres to the CISPE Code of Conduct, which guarantees users access to reliable and fully GDPR-compliant cloud infrastructures;
• Autodesk BIM 360, now part of Autodesk Construction Cloud, offers complete workflow management capabilities within a cloud-based solution, providing real-time access to all project information. This platform supports various construction documents, including RFIs, reports, schedules, and drawings;
• Oracle Aconex is known for its robust integration capabilities and focus on improving collaboration. Aconex provides a centralized platform for managing project information, ensuring that all stakeholders have access to the most up-to-date data;
• Trimble Connect integrates well with Trimble’s software suite, such as Tekla and SketchUp. It offers robust data sharing and centralization capabilities, making it a useful tool for MEP professionals, subcontractors, and architects. Trimble Connect is designed to facilitate collaboration and improve project efficiency through real-time data access and management;
• Fieldwire provides centralized data storage, task management, and coordination capabilities and is an excellent choice for on-site project management. Fieldwire is available as a mobile application, ensuring that project teams can access and update information in real time, regardless of their location;
• Bentley ProjectWise manages project data and documents in a structured and collaborative manner. It offers data management functionalities (including CAD and BIM), collaboration, security, and workflow management. It provides an organized and easy-to-navigate structure for project files and documents, thereby enhancing the efficiency and productivity of construction and infrastructure projects;
• Procore is an all-in-one construction management software built to help users complete quality projects safely, on time, and within budget. It allows construction professionals to collaborate on projects from any internet-connected device, providing access to all project documents, contracts, RFIs, subtitles, schedules, drawings, and more;
• Allplan Bimplus enables interdisciplinary collaboration among all those involved in the construction process. It is an open platform based on the BIM model that uses cloud technology for the entire project lifecycle, from design to construction and usage;
• oceanBIM provides BIM services for the construction industry. It includes tools for drawing management, conflict checking, construction simulation, and file and log management.

usBIM.platform: ecosystem and features

In the case of usBIM.platform, the value lies not only in the central platform but also in the ecosystem of integrated apps that expand the concept of CDE BIM into a more evolved model. In this logic, the platform is the informational core, while specialized applications support:

• • visualization and navigation – usBIM.browser for consulting IFC files and models;
  • coordination and clash detection – usBIM.clash for identifying interferences and usBIM.resolver for collaborative resolution;
  • collaboration and issue management – usBIM.bcf for issue management according to the openBIM BCF standard;
  • model federation and IFC management – usBIM.federation for federating disciplinary models and usBIM.editor for native management of IFC files;
  • 4D scheduling – usBIM.gantt for temporal management;
  • digital twin – usBIM.geotwin for territorial digital twin;
  • facility management – usBIM.maint for operational maintenance management.

A particularly relevant aspect of this evolution is the governance of information quality. Tools like usBIM.dataquality allow for the definition of information requirements, structuring data according to standards such as ISO 23386 and ISO 23387, linking data templates, classifications, and properties, and validating models through machine-readable rules, for example with IDS. This expands the role of the CDE: not only document management but also control of quality and consistency of BIM data.

Practical Applications of Common Data Environment in the Construction Industry

The integration of Common Data Environment (CDE) in construction projects revolutionizes information management, promoting collaboration and enhancing operational efficiency. This approach is particularly advantageous in complex projects, where coordination among different teams is essential to avoid errors and delays. Let’s look at some concrete examples of how CDEs are used in the AECO sector:

• data storage: CDEs allow for the storage and management of a wide range of critical documents, such as permits, contracts, floor plans, and safety plans, on a unified platform. This centralization helps project managers navigate documentation efficiently, ensuring that the necessary information is always accessible when needed;
• compliance with building codes and regulations: CDEs integrate document management features, auditing, and automated workflows to identify and resolve potential compliance issues. This ensures that construction projects adhere to all relevant laws and standards while reducing the risk of legal disputes;
• integration of Building Information Modeling (BIM): the integration of CDEs with BIM enables project teams to access and modify digital models in real time without relying on costly specialized software. This direct collaboration ensures that every change is immediately updated, improving overall accuracy and reducing conflicts and misunderstandings among various project participants.

The practical applications of CDEs extend to various projects (we will see some examples below), whether it’s an infrastructure project or a skyscraper, CDEs streamline the sharing and management of data, ensuring that all project participants work from a centralized and up-to-date repository of information.

This approach is particularly useful for all activities where the value lies not only in the final document but also in the process that generated it: interdisciplinary checks, formal approvals, surveys, model validations, issue management, and information requirements.

The Common Data Environment and Various Project Types: Examples and Successful Case Studies

Common Data Environment (CDE) has been successfully implemented in various construction projects, showcasing their practical benefits. For example:

• railway stations: during the construction project of the Šumice railway station, the implementation of a BIM CDE revolutionized the management of as-Built documentation, improving maintenance planning efficiency. This transition automated 65% of the conversion process, significantly reducing manual effort;
• residential constructions: in residential projects, CDEs support project managers in monitoring progress, allocating resources, and managing budget constraints in real-time. This immediate access to data allows for quick and informed decisions, enhancing operational responsiveness and reducing associated risks;
• highways and bridges: in complex infrastructure projects such as highways and bridges, CDEs facilitate communication and real-time updates between field teams and office teams. This integrated workflow reduces communication errors, optimizing execution and improving overall project efficiency;
• smaller construction projects: even in smaller-scale projects, CDEs play a crucial role by improving access to and sharing of information. This advanced collaboration capability ensures that all team members are aligned and informed, enhancing the overall quality of the final outcome.

At a more advanced level, CDE is evolving from a document-centric model to an information-centric model. In the first case, the platform manages documents, versions, states, and approvals; in the second, it also manages structured data contained in forms, data templates, metadata, and checklists, making them queryable at the project level.

This means being able to answer operational and managerial questions such as:

• which information containers have completed a certain verification;
• which models meet specific information requirements;
• what is the status of progress checks by discipline;
• what data is available for maintenance or the digital twin.

It is here that the Common Data Environment BIM becomes a tangible enabler of information continuity between design, construction, management, and maintenance of the asset.

The implementation of Common Data Environment Software in construction projects is not without challenges, but it is evident that a CDE is a crucial element in managing construction projects. So start now and request a presentation of usBIM.platform to discover a secure, efficient solution, compliant with the UNI EN ISO 19650 standard and certified by buildingSMART International on openBIM^® standards!

Discover right away in this video the CDE software to manage your projects in openBIM.

Real-time evaluation with the interactive ISO 19650 CDE checklist: click the answers and immediately get the score and compliance verdict.

FAQ

What is a CDE in BIM?

A CDE (Common Data Environment) in BIM is a unique and shared digital environment where all information containers of a construction project are collected, managed, and distributed through a structured process defined by the ISO 19650 standard.

What is the difference between CDE and cloud storage?

Cloud storage is an online storage space that holds files. An ISO 19650 compliant CDE manages information containers with metadata, statuses, verification and approval workflows, roles, traceability, and audit trails. Cloud storage archives passively; the CDE actively governs the information lifecycle.

What are the statuses of the information container according to ISO 19650?

ISO 19650 specifies four main statuses of the information container: Work in Progress (WIP), Shared, Published, and Archived. Each status transition should be tracked and authorized.

What is an information container?

An information container is the standardized translation of the concept of “file” in ISO 19650. It is a persistent and identified set of information, equipped with mandatory structured metadata such as status, revision, classification, responsible party, date, and purpose.

What does “CDE Solution” and “CDE Workflow” mean?

The CDE Solution is the technological platform. The CDE Workflow is the information process made up of rules, statuses, transitions, revisions, and approvals. The distinction is essential because a platform without structured workflows cannot be considered a true ISO 19650 compliant CDE.

How to choose an ISO 19650 compliant CDE?

To choose a compliant CDE, it is advisable to check at least these elements: management of information containers, tracked statuses, configurable workflows, roles, versioning, audit trail, dashboards, structured forms, granular permissions, and openBIM interoperability.

Essential Glossary

BIM — Building Information Modeling.

bSDD — buildingSMART Data Dictionary. Multilingual open data dictionary for construction.

Information Requirements Document (IDR) — Document that defines the informational requirements of a project.

CDE — Common Data Environment. Data Sharing Environment compliant with ISO 19650.

Information container — Basic unit of information in the CDE, with structured metadata.

CRA — Check, Review, Approve. Process of verification, review, and approval.

Data Template — Machine-readable data model compliant with ISO 23387.

IDS — Information Delivery Specification. buildingSMART standard for IFC validation.

IFC — Industry Foundation Classes. openBIM standard for model exchange.

ISO 19650 — International standard for digital information management in construction.

ISO 23386 — Standard on methodology for properties in data dictionaries.

ISO 23387 — Standard on data templates for built assets.

LOIN — Level of Information Need. Level of informational need.

openBIM — Open approach to informational exchange based on standards such as IFC, BCF, IDS, and bSDD.

Suitability code — Suitability code that indicates the status and purpose of the information container.

Workflow — Structured operational flow associated with the information container.