Common Data Environment (CDE) Workflow

Coordination describes the requirements and protocols for information exchange among project parties and across collaboration platforms such as authoring software, revision software, and coordination CDE platforms. Below are a list of Common Data Environment (CDE) checklists to perform at information delivery milestone, in accordance with information exchange requirements:

1. Has any project-specific expansion of the standard status codes and revision system been defined?

2. Has a classification system been defined?

3. Has an information container ID codification standard been defined?

4. Does the codification standard define how model renditions/exports are to be given different container names?

5. Have all the potential CDE solutions been reviewed?

6. Have security considerations been considered when

Plugin allows users to view BCF issues in authoring software selecting the potential CDE solution(s)?

7. IF many CDE used, have they been implemented in a collaborative manner and workflow?

8. Has any particular testing been done?

9. Is there agreement on how information containers will be transferred between solutions?

10. Has a clear CDE workflow been implemented?

11. Has the project got a clear documented set of standard methods and procedures of how metadata is assigned?

12. Is it working with tables/classification systems?

13. Has it been confirmed what each status code means?

14. Has rules been confirmed?

15. Has it been made clear how each metadata assignment is made in CDE?

WIP Model reuploaded to CDE under correct revision under “Documents”

1. Most current

2. Used mainly for issue

3.

OpenBIM Cordination Workflow

This table describes the phases of the coordination workflow used in the Pre-construction phase.

Stage Process Description

1 Authoring Software The appointed party develops generative and parametric models using desktop software, such as Revit, ArchiCAD, and Tekla. According to MVD specifications, disciplines export required data for BIM use in IFC format in order to visually validate and comment on issue management in validation software.

2 Review Software IFC models are validated by disciplines and uploaded to CDE (BIMSync) to be approved by the BIM manager. Collection of discipline models are then federated and clash detection performed with a clash matrix in BIM Collab. Issue management delegates issues to be managed by discipline managers and issues are exported as a BFC to CDE to be referenced by all parties.

3 Cloud Software All parties can access BCF issue management tracking and perform additional issue tracking on the CDE platform. Information exchange requirements are specified in the BEP, and are typically delivered at information delivery milestones. By downloading the BIMSync Revit plugin, disciplines can access and manage issue tracking data from proprietary software Revit. Once issues have been addressed discipline can issue comments and change the status of the issue. Once all issues have been resolved, members can export edited IFC from the plugin directly into BIMSync.

4 Repeat Until all exchange information requirements have been met, the exchange of information is repeated. It is possible to simplify the process by using plugins such as the BIMSync Revit plug.