Chapter 8 translates the foundational preparations into an actionable, day-to-day workflow. The authors introduce the Common Data Environment (CDE) workflow as the operational engine of any BIM project. The CDE is explained through its four sequential states.
State 1: Work in Progress (WIP) : Each discipline (architecture, structure, MEP) maintains its own model in a private workspace. Team members can edit freely without affecting others. The WIP is not coordinated; conflicts within the discipline are resolved here.
State 2: Shared: When a discipline's model reaches a milestone (e.g., completion of structural framing), it is published to the Shared area. Other disciplines can now reference this model for coordination. The Shared area uses version control; old versions are archived before new versions replace them.
State 3: Published: After coordination checks (clash detection, compliance with standards), models move to Published. Published models are contractually reliable and can be issued to clients or used for construction.
State 4: Archived: Every previous version of every model is permanently preserved in the Archive. This provides an audit trail for disputes, insurance claims, or understanding historical decisions. The chapter provides detailed guidance on weekly coordination cycles. A typical cycle: Monday: teams work in WIP; Wednesday: publish to Shared; Thursday: run clash detection, assign responsibility for clashes; Friday: teams update WIP based on clash results.
The chapter also covers naming conventions (standardized formats for files, folders, and objects), coordinate systems (ensuring all models align to the same origin point and rotation), and model health checks (automated tests for missing properties, duplicate objects, or geometry errors). The authors emphasize that the CDE is a set of behaviors and protocols, not a specific software product; many platforms can implement these principles.
Comments
Post a Comment