It is recommended to save the created clash tests in a separate file for reuse in similar designs. The clash check report and summary report shall be generated. See Appendix C, Tables C.1. and C.2. 6.3.8 Clash Analysis The clash analysis process is aimed at preparing to assignment of people responsible for their resolution. Normally, clash resolution is put in charge of the BIM authors who developed the respective parts of design. Some recommendations on the clash analysis procedure are given in Appendix F, section 7 “Clash Analysis”. Analysis and assignment of persons responsible for resolution are usually being done at the coordination meetings. See section Coordination of this Guide. “BIM Meetings” 6.3.9 Resolving Clashes The clash resolution process is aimed at making corrections in the source discipline BIM models, preparing the models to the next clash check, and reducing to zero the number of total clashes in the design. The clash analysis results shall be returned from Navisworks® to Revit®. This procedure is described in detail in Appendix F, section 8 of “Resolution Detected Clashes”. Resolving of each particular clash is confirmed by changing its status to when the test “Resolved” is re-run. Resolution of clashes shall be documented in the re-run check reports. 6.4 BIM Coordination Meetings Coordination meetings shall be held in order to analyze found clash, look for the ways of their resolutions and assignment of responsible persons. Leaders of all relevant groups/departments/disciplines, the BIM Manager(s)/Coordinator(s) and the project manager shall participate. Coordination meetings are held as appropriate. They include discussing the general issues of the implementation of BIM project, as well as issues related to clashes identified during inspections. In particular, discussions cover the progress of the project in the modeling context, location of participants and their tasks, backlogged tasks identified at the previous meeting, matters of collective interaction, unresolved technical problems, amount of work on the contract and
It is recommended to save the created clash tests in a separate file for reuse in similar designs. The clash check report and summary report shall be generated. See Appendix C, Tables C.1. and C.2. 6.3.8 Clash Analysis The clash analysis process is aimed at preparing to assignment of people responsible for their resolution. Normally, clash resolution is put in charge of the BIM authors who developed the respective parts of design. Some recommendations on the clash analysis procedure are given in Appendix F, section 7 “Clash Analysis”. Analysis and assignment of persons responsible for resolution are usually being done at the coordination meetings. See section “BIM Coordination Meetings” of this Guide. 6.3.9 Resolving Clashes The clash resolution process is aimed at making corrections in the source discipline BIM models, preparing the models to the next clash check, and reducing to zero the number of total clashes in the design. The clash analysis results shall be returned from Navisworks® to Revit®. This procedure is described in detail in Appendix F, section 8 “Resolution of Detected Clashes”. Resolving of each particular clash is confirmed by changing its status to “Resolved” when the test is re-run. Resolution of clashes shall be documented in the re-run check reports. 6.4 BIM Coordination Meetings Coordination meetings shall be held in order to analyze found clash, look for the ways of their resolutions and assignment of responsible persons. Leaders of all relevant groups/departments/disciplines, the BIM Manager(s)/Coordinator(s) and the project manager shall participate. Coordination meetings are held as appropriate. They include discussing the general issues of the implementation of BIM project, as well as issues related to clashes identified during inspections. In particular, discussions cover the progress of the project in the modeling context, location of participants and their tasks, backlogged tasks identified at the previous meeting, matters of collective interaction, unresolved technical problems, amount of work on the contract and
f4bf0790-9a63-47fc-80f8-eb93d5f6eff4.docx