Book a demo
Login
A Common Data Environment (CDE) is an agreed environment for collecting, managing, sharing, and controlling information throughout the lifecycle of a project or asset. It provides project participants with a governed source for documents, models, engineering data, registers, and other information that must be coordinated across organizations.
Under ISO 19650, a CDE is not simply a software platform or shared document repository. It combines defined information management processes with technology so that information moves through controlled states, revisions, approvals, and authorization before it is relied upon by the wider project team. This distinction between the CDE workflow and the technology supporting it is also emphasized in industry guidance.
For complex capital projects involving owner-operators, EPCs, contractors, and suppliers, this controlled environment helps prevent fragmented information, duplicate files, outdated revisions, and uncertainty about which information is approved for use.
A Common Data Environment provides a managed framework for project information so that participants can access the appropriate information, understand its status, and work from controlled versions.
A CDE can contain much more than BIM models. Depending on the project, it may manage drawings, engineering documents, models, schedules, registers, structured data, correspondence, and other information containers. This broader information-management role is an important part of the CDE concept: NBS, for example, explicitly distinguishes CDE content from information created solely in a BIM environment.
The objective is not merely to put information in one place. It is to establish a controlled process for creating, reviewing, sharing, approving, publishing, and preserving information throughout the project lifecycle.
ISO 19650 provides an international framework for managing information over the lifecycle of built assets using building information modelling and structured information management.
A central principle is that information containers progress through managed states. In a typical ISO 19650 CDE workflow, information moves through:
Movement between these states is governed by review and authorization rather than uncontrolled file sharing. ISO 19650-oriented CDE processes also address identification, revision control, status or suitability, classification and auditability.
This is why implementing a CDE is as much an information governance process as a technology decision.
A CDE establishes rules for how information enters, moves through, and leaves the shared project environment.
Typical CDE capabilities include:
Together, these controls help project participants determine not only where information is stored, but whether it is current, approved and suitable for a particular purpose.
That distinction is critical on multidisciplinary projects where hundreds of organizations and users may create, review or consume information at different stages.
A Common Data Environment and BIM are closely related, but they are not the same thing.
BIM provides methods and models for creating, coordinating and using information about a built asset. The CDE provides the managed environment through which relevant models, documents and other project information are exchanged and controlled.
Oracle, NBS and other major industry sources therefore describe the CDE as extending beyond the model itself: it connects teams with the wider project information required to design, construct and ultimately operate an asset.
This also explains why the concept applies beyond conventional building construction. The same underlying problem exists on large industrial projects: many disciplines and organizations must create and exchange controlled information about one physical asset.
A CDE should not be confused with a shared folder or cloud storage service.
Platforms such as SharePoint can form part of an information-management solution, but simply storing files centrally does not by itself establish a CDE. The defining element is the managed process around the information: status, revisions, permissions, approvals, authorization and traceability.
A CDE and an Engineering Document Management System (EDMS) are also related but not identical.
An EDMS is primarily concerned with managing engineering documents and document-control processes. A CDE has a broader information-management role and may encompass models, documents, structured data and other information produced by multiple project participants.
In practice, the capabilities can overlap considerably, and a project may use multiple integrated technologies to implement its overall CDE process.
On oil and gas, LNG, energy, chemical, pharmaceutical and other asset-intensive projects, the CDE concept extends beyond conventional drawing and BIM coordination.
Information must ultimately describe and support thousands of physical assets that will be operated and maintained for decades.
Important requirements can therefore include:
This makes the relationship between the CDE and Asset Information Management (AIM) particularly important.
The project is not finished with its information simply because construction is complete. Controlled project information must become usable asset information for operations.
One of the most important outputs of a well-managed Common Data Environment is reliable information at handover.
During project execution, documents and data are created by engineering teams, EPCs, equipment manufacturers, suppliers and other contractors. If these deliverables are not consistently identified, reviewed, linked and approved as they enter the project environment, information problems accumulate until the end of the project.
A governed CDE helps maintain the information history and approved record required to assemble the final Document Handover Package.
For asset-intensive facilities, handover also requires relationships between documents and physical assets to survive the transition into operations. A drawing may need to be associated with specific equipment or tags; supplier documentation must remain connected to the equipment it describes; and approved asset information must be transferred into downstream operational systems.
The Master Tag Register (MTR) therefore complements the CDE by providing a controlled register of tagged assets against which engineering and supplier information can be structured.
A useful distinction is the relationship between the CDE and the information models managed through it.
During project delivery, controlled information contributes to the project information required to design and construct the asset. During operation, validated information can contribute to the Asset Information Model (AIM) used to support management of the operational asset.
Industry guidance describes the AIM as being managed within a CDE and emphasizes that asset owners need to define what information is required and how it will be maintained.
For owner-operators, this makes information requirements established during the project critical. The long-term value of a CDE depends not only on storing project records, but on delivering structured, trustworthy information that can continue to support the asset after handover.
Sharecat supports the asset-information layer around a Common Data Environment by connecting engineering documents, supplier information and structured equipment and tag data.
Rather than treating documents and asset data as unrelated deliverables, Sharecat helps structure information against the physical assets it describes. Supplier submissions can be managed through Supplier Data Management workflows, while equipment and tag information can be connected through the Master Tag Register (MTR).
This is particularly important at handover, where owner-operators need more than a collection of approved files. They need information that can be validated, traced to the correct assets and transferred into operational systems.
In this way, Sharecat complements the broader CDE process by helping turn controlled project information into structured, usable asset information across the project-to-operations transition.
What is a Common Data Environment (CDE)?
A Common Data Environment is an agreed environment for collecting, managing and sharing project or asset information through controlled processes. It helps project participants work with appropriately reviewed, authorized and traceable information.
What is a Common Data Environment under ISO 19650?
ISO 19650 describes the CDE as the agreed source through which information containers are collected, managed and disseminated using a managed process. The CDE workflow controls how information progresses through states such as Work in Progress, Shared, Published and Archived.
What is the difference between BIM and a CDE?
BIM concerns the creation and management of information about a built asset, including digital models. A CDE provides the governed environment and processes through which BIM models and other project information can be shared, reviewed and controlled.
Is a CDE the same as an EDMS?
No. An EDMS primarily manages engineering documents and document-control processes. A CDE can encompass a wider range of project information, including documents, models and structured data, and governs how that information is exchanged between project participants.
Is SharePoint a Common Data Environment?
SharePoint can provide technology used within a CDE implementation, but storing documents in SharePoint does not automatically create a CDE. A CDE also requires defined information states, permissions, revision controls, approval and authorization processes, metadata and governance.
Why is a CDE important for project handover?
A CDE maintains controlled information throughout project execution so that approved documents and data can be identified and transferred at handover. For asset-intensive projects, the information also needs to retain its relationships to equipment, tags and other asset identifiers.
ISO
27001
Certified
