CDE in British Standards – Agile BIM Part 3/10

This post (CDE in British BIM Standards) is part of the “Agile BIM” series. Click below to check out other posts.

1. Why BIM? Origins of New Solutions – Agile BIM Part 1/10
2. British Approach to BIM – Standards and Protocols – Agile BIM Part 2/10
3. CDE in British Standards – Agile BIM Part 3/10
4. Why is CDE so important in BIM? – Agile BIM Part 4/10
5. Przykłady platform wymiany danych CDE – zwinny BIM cz. 5/10
6. What is BIM? – Agile BIM Part 6/10
7. BIM vs. Traditionally Managed Construction Projects – Agile BIM 7/10
8. Agile Project Management – Introduction to Agile – Agile BIM 8/10
9. Translating Agile Principles into BIM – Agile BIM Part 9/10
10. How to Make BIM Agile? – Agile BIM 10/10

CDE in British BIM Standards

The Common Data Environment (CDE) is a collaborative space for inter-disciplinary and project information, managed by the client through the Information Manager. The Information Manager ensures the security of resources, their integrity, and establishes rules, standards, and protocols for information exchange and sharing. The CDE environment in BS 1192:2007+A2:2016 is defined across four areas described below:

1. Work In Progress (WIP)

This area is where project information creators develop and modify data. Processes in this area are generally outside the interest of other parties unless related to a shared project. Note that this is not a single space but several distinct WIP areas used by different design offices and their subcontractors.

Information produced, such as models and project documents, after passing internal verification, is transferred to the Shared area. This enables the project team to manage their data effectively, ensuring consistency and readiness for further sharing.

2. Shared Area

This is the area where information from creators meets feedback (from clients or other team members) who provide comments or change proposals. Important processes in the Shared area include inter-disciplinary coordination, including resolving clashes between elements from different disciplines. Control over this process is facilitated by suitability codes (e.g., S1 – Suitable for inter-disciplinary coordination, S2 – Suitable for information (non-graphic data and documents), S3 – Suitable for commenting and verification (graphic and non-graphic data)) and revision numbers P01, P02, P03… which correspond to iterative steps (model versions). 3D models from the Shared area act as external references in the WIP area for other disciplines.

Clients (Investors) in the Shared area can verify proposed solutions from designers and their compliance with their expectations.

3. Published Area

The iterative method of producing project information described in the previous two areas continues until the client authorizes the presented solutions, meaning they are satisfied with the project’s objectives (functional, aesthetic, operational, economic, environmental, etc.). This leads to approval for publishing documentation, which usually means meeting formal contract requirements according to the Employer’s Information Requirements (EIR) and approving the documentation as official project documentation for that stage.

4. Archive

This area is mainly for inactive or replaced versions and provides the client with access to all information produced during the project.

Why CDE in British BIM Standards is crucial?

In the next post, we will discuss why the CDE environment is vital in BIM projects and what benefits it provides. Undoubtedly, an agile approach to BIM requires a solid foundation in the form of a well-managed CDE environment.

References

https://bim-level2.org/en/standards/