A collaboration strategy should be defined, considering the following items:
Table 17 illustrate how to define the type of meetings held during the project, including coordination meetings, owner updates, progress meetings, etc. It also indicate the required attendees and the scope of the meeting.
Table 17: Project meetings
Meeting Type | Phase | Frequency | Participants | Location | |
Table 18 illustrate how to document the type and frequency of meetings related to BIM Coordination. It also indicate the required attendees and scope of the meetings.
Table 18: BIM Coordination meetings
Meeting Type | Phase | Frequency | Participants | Location |
Examples to how outline the deliverables required and the anticipated date for completion.
Deliverable | Date |
Deliverable | Date |
Before starting the Project, a color scheme could be defined to distinguish systems. Table 19 shows an example of a color code system.
Table 19: Example of a BIM model elements color code
In relation to the Integrated (Federated) Model/ Integration Processing accordance with the Project Schedule the Project BIM Manager usually will be responsible for performing clash detection with the design and/ or trade models. The clashes should be organized for review by the Project Team. Once clashes have been reviewed, a potential resolution will be assigned to a specific team member to be solved in a timely manner.
If any system has interference or clash with a differing system, a discipline hierarchy for resolutions based on the consensus of the project team should be defined.
The project owner is responsible for the quality of all models to be presented. The disciplines should check the model quality within themselves. The BIM manager is responsible for controlling the quality of the model, considering the coordination of all disciplines, within the framework of its defined responsibilities. In this section, checklists are created within the scope of the BEP and models are evaluated according to this list.
Table 20 presents an example of the checks that could be performed in the models to assure quality.
Table 20: BIM Checks
Check | Definition | Responsible party | Software program(s) | Frequency |
Visual check | Ensure there are no unintended model components and the design intent has been followed | All model author(s) | Navisworks, Revit Other | Each milestone deliverable |
Interference check | Detect programs in the model where any building components are clashing including hard and soft | All model author(s) | Navisworks, Revit other program(s) TBD | |
Standards check | Ensure that the BIM standards have been followed | All model author(s) | Navisworks, Revit Other | Continuous |
Model integrity checks | Describe the QC validation process used to ensure that the Project Facility Data set has no undefined, incorrectly defined, or duplicated elements and the reporting process on non-compliant elements and corrective action plans | All model author(s) | Navisworks, Revit Other | Weekly |
Model Review / Model Checker | An automated global model review and report feature | All model author(s) | Revit Other | Each milestone deliverable |
In the model checking requirements the software to perform an automated model review of the Project should be defined. Additional rules may be added to the configuration files by the project BIM team for project-specific requirements.
In addition, models should include dimensioning as needed for design intent, analysis, and construction. Thus, the Level of Accuracy (LOA) of the model should also be defined.
The BIM team should perform an automated model review of project model using, for example, the Revit Model Review application (an add-in application available through the Autodesk subscription website) or by using Autodesk Model Checker (also an add-in application for Revit).