3D Coordination:

Clash Detection
Reporting
Guidance for Preparing Clash
Detection Reports

Version 1.0 • 10/01/2020

UNCLASSIFIED
1. Introduction
The US Department of State (DOS) Bureau of Overseas Buildings Operations (OBO)
provides this guidance to assist in developing a Clash Detection Report (CDR).

The CDR documents 3D geometric conflicts found by comparing 3D models of building

systems, including permanent design elements, temporary construction elements, and
operational elements, including clearances or other furnishings. The CDR records each
instance of a clash with a unique ID, allowing the project team to track its status towards
resolution. This report and workflow support OBO’s implementation of the 3D
Coordination BIM use. The goal of 3D Coordination is for OBO contractors (design
consultants and construction contractors) to eliminate field conflicts and coordination
issues before installation.1

This reporting guide illustrates OBO’s expectations and supplements the sections in the
OBO BIM Requirements, OBO BIM and CAD Standards, and the BIM Execution Plan (BEP).
These documents provide additional information that governs clash detection and
reporting requirements, its standards, and its usage during the execution of a project.

1.1. OBO BIM Requirements

Section 3.6 3D Coordination of the OBO BIM Requirements states when contractors must
provide the Clash Detection Report as well as the 3D coordination models used to
identify the 3D geometric conflicts. Section 3.2.1 BIM Execution Plan (BEP) directs
contractors to document the BIM plan in the BEP, which includes all BIM uses, such as
3D Coordination.

1.2. OBO BIM and CAD Standards

Section 4.5 3D Coordination: Clash Detection Report of the OBO BIM CAD Standards
describes the information that contractors must include in a CDR. The CDR incorporates
the details of each specific clash and the project-level reporting of clashes.

1.3. BIM Execution Plan (BEP)

Sections 1.2 BIM Uses and 1.3 Project Phases & Milestones of the BIM Execution Plan
(BEP) is where contractors list 3D Coordination as a BIM use for the Design and

1
https://www.bim.psu.edu/3d_coordination/
Construction Phase(s). See OBO BIM Requirements for the appropriate project phase to
start 3D Coordination.

Sections 3. PROJECT BIM GOALS, 7. COLLABORATION PROCEDURES, and 8. QUALITY

CONTROL ACTIVITIES AND STRATEGY is where contractors identify how they will deploy
3D Coordination to maintain quality control (QC) over the project.

2. Sections of the Clash Detection Report

There are two main sections of the CDR: 1) Project Clash Summary and 2) Clash Tests.

The Project Clash Summary provides a summary of the current number and type of
clashes and their progress towards resolution over time. The Clash Tests include
detailed information about each clash or clash group.

2.1. Project Clash Summary

The purpose of this section is to summarize the overall magnitude and impact that
clashes have on the project.

Here is a list of required reporting entities, their descriptions, and examples, as identified
in the OBO BIM and CAD Standards Section 4.5.1.
Table 1: Clash Test Reporting Entities

Reporting Entity Description Example

Report Name The name of the clash report. CD-1 90% Clash
Report (All disciplines)
Clashes The cumulative count of all clashes detected 55
for all disciplines.
New The number of new clashes detected since the 8
last report.
Active The number of clashes under review at the 35
time of the report.
Reviewed The number of clashes reviewed by the 12
project team since the last report.
Approved The number of clashes reviewed, and the 0
solution approved by the COR.
Resolved The cumulative count of clashes designated 0
closed by the COR.
After submitting the first CDR, each updated CDR will provide a resolution status update
on previous clashes to evaluate the progress made toward resolving existing conflicts as
well as reporting any new clashes. The Contractor is to provide the CDRs status
cumulatively at each submittal to illustrate the progress made on resolving clashes. See
the example in Section 3.1.

2.2. Clash Tests

This section of the CDR provides detailed information about the clashes. The Contractor
must organize clashes by discipline(s) or clash group(s) and provide a clash test
summary with the following information as identified in the OBO BIM and CAD
Standards Section 4.5.2.
Table 2: Clash Test Summary Reporting Entities

Reporting Entity Description Example

Clash Test The name of the discipline(s) or clash group Structural vs.
analyzed for clashes Mechanical
Clashes The cumulative count of clashes in this clash test. 15

New The number of new clashes detected, in this clash 2

test, since the last report.
Active The number of clashes, in this clash test, under 12
review at the time of the report.
Reviewed The number of clashes, in this clash test, reviewed 1
since the last report.
Approved The number of clashes, in this clash test, reviewed, 0
and the solution approved by the COR.
Resolved The cumulative count of clashes, in this clash test, 0
designated closed by the COR.
Finally, each clash within a clash group must include the following reporting entities:

Table 3: Individual Clash Reporting Entities

Reporting Entity Description Example

Thumbnail A thumbnail image of the clash.

Clash ID Unique ID number of the clash. Clash ID

Clash Test The name of the discipline(s) or clash Plumbing vs. Structure
group analyzed for clashes
Clash Level The level or story of the building the Entry Level
clash occurs
Clash Title Clash name generated by the clash Plumbing vs. Structure:
detection system that also describes the Group 9 01 - Entry Level
systems and location of the clash.
Project Name The name of the project. OBO Embassy Building

Date Created The date the clash was detected. 01/Apr/2020

See examples in sections 3.2 and 3.3.

3. Examples
The following examples are for illustrative purposes and do not specify any particular
application.

3.1. Clash Resolution Status Update Report

Below is an example of cumulative clash detection reports provided by the Contractor
for three project submittals. Note the trendline of clashes over time when comparing
the various submittals.
 Table 4: Project Clash Resolution Summary Example

Report Name Clashes New Active Reviewed Approved Resolved

CD-1 60% Clash

Report (All 47 47 47 0 0 0
disciplines)

CD-2 90% Clash

Report (All 55 8 35 12 0 0
disciplines)

CD-3 100% Clash

Report (All 45 0 24 15 6 10
disciplines)

3.2. Clash Report

Below is an example of a report of an individual clash within a clash group. A 3D
Coordination Model Management application generates this report. The required
reporting entities are called out for reference.

Figure 1: Individual Clash Report Example

3.3. Example – Comprehensive Clash Test Report
Below is a comprehensive clash report example generated from a 3D Coordination
Model Management application. This example contains a clash test summary in the top
section, followed by an individual clash report within the clash group.

Figure 2: Comprehensive Clash Report Example

PREPARED BY:

in partnership with Onuma,

Strategic Building Innovation,
and Quinn Evans Architects CONTACT: BIM@state.gov