Coordination Standards

Coordinating various disciplines using BIM Work-flow requires the team to follow specific set of standards early in the process.

Assuming that the models are developed by using the appropriate BIM Modeling Standards (previously discussed) and using standards specific to BIM coordination will make the process efficient and productive.

Coordination Software

Software features required for BIM Coordination are very different from the ones needed for modeling. Selected software should have the capability to seamlessly communicate 3D Models with the modeling tool and having a live link is ideal to coordinate model updates. Identifying the right coordination software to bring all discipline models into one 3D Integrated BIM Model and identify and document the various design issues that are in the project is the first step.

Model Conversion Standards

BIM Design coordination is an iterative process involving repetition of coordination exercise multiple times during this process. Defining and documenting the process and formats of converting BIM Models for Coordination will help avoid confusing at every iteration.

File Sharing Standards

Sharing information openly to all project stake holders is a critical step taken toward succeeding in a BIM project. Organizing a cloud based folder structure (FTP etc ) with right permission levels to all team members to share models through out the project will enable efficient coordination. Also, document the frequency of file sharing in such a way that all team members are working on the same version of design at all times.

Meeting Schedules

BIM Coordination is a true collaborative exercise and requires the team to meet either virtually or physically at one location to carryout the coordination exercise. Typical project coordination meetings are organized every 2 weeks to ensure that major issues identified early in the process. Providing access to the models 1 day before the meeting will help the team to prepare the files required.

Issue Prioritization/Clash Detection

Every project during early coordination activities will identify several issues (clashes) and it can get overwhelming for the team to manage. A clash detection matrix documenting the issue prioritization will help organize this process into various iterations and also avoid ripple effect of clashes. Typical practice involves identifying issues between larger and less flexible elements such as structure vs. gravity driven pipe work etc.

Issue Documentation & follow-up

Documenting multiple issues identified at various meetings is important. This will enable the team to understand the progress made and also monitor the status of each individual issue (resolved, pending etc) and the responsible parties to help define follow up activities accordingly.