In modern construction management, establishing a robust Common Data Environment (CDE) is essential for preventing information silos, reducing rework, and maintaining data integrity. Aligned with the ISO 19650 framework, a CDE serves as the central digital repository for all project information, drawings, models, and site inspection reports.
In this technical article, we explore the core architecture of a Common Data Environment, the four main information states under ISO 19650, and practical workflows for field engineers on construction sites.
1. What is a Common Data Environment (CDE)?
A CDE is a single source of truth used to collect, manage, and disseminate all documentation, models, and data related to a project lifecycle. Key benefits include:
- Version Control: Guarantees that site teams execute works using the latest approved drawing revision.
- Traceability: Maintains complete logs of document approvals, RFIs (Requests for Information), and submittals.
- Interoperability: Facilitates seamless coordination between structural, architectural, and MEP disciplines.
2. The Four ISO 19650 Information States
| Information State | Description & Purpose | Access Permissions |
|---|---|---|
| Work in Progress (WIP) | Unapproved design models and calculations actively being developed by a specific team. | Internal task team only (e.g., Structural Design Team). |
| Shared | Information checked and verified to be shared across disciplines for coordination. | All project stakeholders (Architectural, MEP, Structural). |
| Published | Authorized documents approved for construction, procurement, or manufacturing. | Site Engineers, Contractors, Consultants, and Client representatives. |
| Archived | Historical record of all container revisions throughout the asset lifecycle. | Information Managers and Project Administrators. |
3. CDE Workflow for Field & Site Engineers
- Inspection Requests (IR): Site engineers generate digital IRs directly linked to the latest published model in the CDE platform (e.g., ACC, Trimble Connect).
- Clash Resolution Verification: Reviewing structural rebar details against MEP penetration sleeves before authorizing concrete pouring.
- As-Built Submittals: Updating the digital record in real time as variations occur on site, preparing data for final facility management handover (COBie).
Site Engineer's Insight: Adhering to strict CDE file naming standards and approval workflows eliminates communication breakdowns between office design teams and site execution engineers.
ليست هناك تعليقات:
إرسال تعليق
تعليق