USACE BIM Design Review Process 2 - 5

USACE BIM Assisted Design
Review Process
3D Clash Detection and 2D Drawing Reviews Version: DRAFT 0.0
Last Modified: xx/xx/2011
Contents
General .............................................................................................................................. 2
BIM Workflow Overview .................................................................................................... 3
BIM Assisted Design Reviews .......................................................................................... 5
In-Progress BIM/Design Coordination Review .............................................................. 6
Quality Checks and Reviews (QCR) ............................................................................. 8
Project Delivery Team Review (Client Review) ............................................................. 9
Independent Technical Review ................................................................................... 10
Biddability, Constructability, Operability, and Environmental Review ......................... 11
Roles and Responsibilities .............................................................................................. 12
Technical Instruction ....................................................................................................... 16
Model Setup ................................................................................................................. 16
Create Project Coordination Master Model ................................................................. 17
Creating/Updating i-Models ......................................................................................... 19
Saving Overlay Files .................................................................................................... 21
Clash Job Setup .......................................................................................................... 22
Reviewing Clashes ...................................................................................................... 24
Perform Visual Model Check ....................................................................................... 26
Glossary .......................................................................................................................... 27
FILE: C:\Users\travis.wollet\Desktop\Design Review\USACE BIM Design Review Process 2 (5).docx Page 1 of 27

General

A significant benefit of utilizing BIM comes from the successful application of tools which aid in
identifying, communicating, and resolving design issues, errors, and omissions. This can include 3D
automated clash detection, visual checks, and 2D drawing markups. BIM is a process and dynamic
project review is a part of that process that encourages greater collaboration earlier and more
consistently throughout the design process. In this process, better informed decisions can be made
sooner in the design process resulting in less costly design changes than those typically made later in
the project or overlooked in a traditional CAD/2D workflow. A successful implementation of the BIM
process can reduce project risk, Requests for Information (RFI’s), Amendments and Modifications,
and result in a more effective design.
PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 2 of 27

Detection\USACE BIM Design Review Process.docx
BIM Workflow Overview
In order to understand the reasons for using BIM (Building Information Modeling), it is important to
clearly define what it is. First and foremost, BIM is a process that engages architects, engineers,
contractors, and owner/operators in a 3D data‐rich virtual environment for the initial purpose of
producing a better designed and constructed project through the real‐time use of the information
modeling.
 BIM is not a software package, it is a process. BIM software is used as a tool in the process,
but simply using BIM software does not mean that a team is engaged in or leveraging the
benefits of Building Information Modeling.
 Producing better buildings should be the goal of BIM, not producing better 2D drawings.
Construction drawings, while still important for communicating information to construct the
building, are secondary to the model and should be seen as one of many outputs of the BIM
process.
o When the contract supports it, early participation by the general contractor and
sub‐contractors in the design process can streamline decision making, reduce the
required construction documentation, and result in real‐time cost feedback of
design changes.
 The real‐time cross‐discipline design coordination of the BIM process allows decision making
to occur sooner in the design process and detect potential conflicts early on when design
changes are less costly and less time consuming.
o For this coordination to be most successful it requires that all disciplines invest in
the design from the beginning rather than waiting until other disciplines are nearly
finished to ‘shoe‐horn’ their system into the design, even if this means schematically
modeling systems for space reservation purposes.

The expectations of what is completed at project milestones are different in a BIM workflow than a
traditional CAD workflow. A successful BIM workflow front‐loads decision making and cross
discipline coordination in the model before any drawings are even started. It is more important at
early stages to ensure sufficient model development is completed across all disciplines in order to
conduct discipline coordination which can occur at a higher level of precision in 3D.

While the geometric accuracy and level of detail in the BIM model is important for spatial
coordination, the data associated with the modeled elements is equally important for design
validation. The BIM Review Process can provide tools to assist with the checking and verification of
important design standards and code issues. For example, processes can be defined and tools can be
used to identify all of the firewalls in the model to ensure fire compartmentalization in a building.
Another example is to define processes and tools to compare the current design with the approved
programmatic areas. Egress can be verified by establishing a query which highlights egress doors
which are below minimum required clear widths.


‐ Difference between Design Quality vs Model Quality vs Drawing Quality
o

BIM Assisted Design Reviews

One of the biggest advantages of BIM is the ability to virtually design and construct the project prior
to ever breaking ground. The virtual model allows the design team to coordinate all disciplines in a
3D environment to identify potential conflicts, enables owner/operators to navigate the project to
address their operation and maintenance concerns, and lets the contractor work through
constructability and logistic scenarios all prior to construction. When a regimented 3D model review
process is implemented these advantages can yield a better design, cheaper/faster construction,
and more efficient building operations for the owner.

Within the Corps of Engineers there are many classes of design review that may vary in frequency,
participants, and content being reviewed. The following sections identify several classes of design
reviews and describe how the use of BIM along with Bentley Navigator can assist in the review and
enrich the effectiveness of it.

In-Progress BIM/Design Coordination Review
Design coordination has always been necessary during the design phases regardless of a CAD or BIM
workflow. However with BIM, regular model‐based coordination reviews involving all team
contributors is critical to the success of the project. Coordination meetings should commence
immediately following the initial design charette and persist throughout the duration of the project.
It is recommended that team coordination meetings be conducted weekly, but the size and
complexity of a project may warrant a more or less frequent meeting schedule. While the length of
the coordination meeting may increase or decrease over the course of the design phase, it is
important to maintain the frequency of the meetings in order to ensure thorough coordination of all
disciplines.

The following steps outline a suggested 3D model review process for a design team based on weekly
design coordination meetings.


Day 1: Prepare Models for Review
 At project start, Project BIM Coordinator sets up models (see Model Setup)
 After initial setup, Project BIM Coordinator Updates i‐Models

Day 2 & 3: Discipline Independent Model Review
The purpose of this review is to prepare for coordination with other disciplines while resolving all
issues that can be resolved independently before engaging other disciplines.
 Identify Design Issues (Discipline Lead)
o Check against OWN discipline
 Clash detection (see Reviewing Clashes)
 Visual check (see Perform Visual Model Check)
o Check against EACH discipline
 Clash detection (see Reviewing Clashes)
 Visual check (see Perform Visual Model Check)
 Assign and prioritize coordination issues (Discipline Lead)
o Create/assign Markups that can be resolved within your own discipline.
o Create Markups for cross‐discipline conflicts for discussion at coordination meeting.
 Assign priority to Markup
 Resolve issues within your own discipline (BIM Modeler)
o Make changes to design and model to address Markups which do not require cross‐
discipline coordination.
 Change Status of Markup to reflect progress
o Update i‐Models and perform Discipline Self‐Check again until satisfied.
 Project BIM Coordinator updates all i‐models prior to Coordination Meeting

Day 4: BIM Coordination Meeting
Design Team Lead facilitates coordination meeting with Discipline Leads, Project BIM Coordinator
and BIM Modelers. Design & coordination issues should be reviewed and discussed through the
model via Bentley Navigator.
 Applicable Discipline Leads: Review/Assign unclaimed cross‐discipline clashes.
o Markup ‘Assigned To’ and ‘Due Date’ properties should be updated to reflect
responsible persons/groups for each issue.
 After coordination meeting Discipline Leads and BIM Modelers resolve agreed upon clashes
until next review cycle.
o Markup ‘Status’ and ‘Approved By’ properties should be updated to reflect progress
on issues.
 All design issues should be coordinated through the model however if items are identified
while working in sheets, markups on sheets can occur for review during the coordination
meetings. Review of drawing‐specific items like notes, annotations, and dimensions are not
important at this stage.
Quality Checks and Reviews (QCR)
 Typically occurs 1‐2 weeks prior to each major submittal.
 Perform same steps as in Design Coordination Meeting
 Perform 2D Drawing Review
 Discipline Lead certifies that QCR of BIM requirements have been completed.

Project Delivery Team Review (Client Review)
 Participants:
a. Installation Stakeholders & Specialists
b. Design Team
 Client Review: Go to client with projector for Design Review through the model
a. Establish what has been coordinated and analyzed
i. Energy & Lighting Analysis
ii. Structural & ATFP
iii. Cost & QTO?
iv. System Coordination and Integration
b. Renderings/Animations of the model
c. Space Program fulfillment – (SpacePlanner ‐ Thematic Maps)
d. Setup Saved views to demonstrate how the design meets the requirements
i. Specific Views/content for specific user reviewer
ii. Telecom, Fire Protection, Security, Etc.

Independent Technical Review
Van, we need to add stuff here
PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 10 of

Detection\USACE BIM Design Review Process.docx 27
Biddability, Constructability, Operability, and Environmental Review
Van, we need to add stuff here

Roles and Responsibilities
Districts and projects will have different composition of roles whereby one person on a project may
fulfill one or more roles.
i. Project Manager (PM):
a. Schedule and fund design team labor for performing reviews.
b. Coordinating external reviews to include impasses between design team and review
team.
c. Coordinating customer design requirements.
d. Deliver BIM Submittal to the customer which includes the Design Review report.
e. Facilitates the ITR and Design Review.
ii. Design Team Lead (DTL)
a. Responsible for interdisciplinary project coordination.
b. Schedule and facilitate the Design Coordination Meetings which includes the Inter‐
Discipline Coordination issues not resolved in the Discipline Self‐Check process.
c. Facilitates QCR.
iii. Discipline Lead (DL)
a. Lead designer/decision maker for a specific discipline.
b. Perform or oversees Discipline Self‐Check process and decisions.
c. Participates with Inter‐Discipline Coordination issue resolution.
d. Corrects or assigns work tasks to change the BIM to resolve issues.
e. Verifies that changes to the model adequately address design problems identified.
f. Verifies that work tasks are completed and that additional issues which may have arisen
are addressed.
g. Responsible for final signoff on BIM QA/QC Certification Report prior to issuing for QCR.
iv. Project BIM Coordinator (PBC)
a. Person responsible for interdisciplinary BIM coordination.
b. Creates initial setup for design review process when notified by DTL.
c. Responsible for periodic updates to review models according to the review schedule
defined by the DTL.
d. Primary interface for the design team with the BIM Manager and ProjectWise
Administrator.
v. BIM Modeler (BM)
a. Designer or BIM user in a discipline who uses BIM tools and processes in a project.
b. Completes work tasks assigned by DL.
c. Notifies and coordinates with DL when potential issues are identified through visual
checks and clash detections.
vi. BIM Manager (BMG)
a. Person responsible for consistency and efficiency for all BIM projects and coordinates
with the CAD Manager and ProjectWise Administrator.
b. Assist design team with review process standards and workflow guidance when
requested.
c. Responsible for overall BIM system and process infrastructure and not individual project
review process oversight.
d. Primary interface with the team for the BIM Manager is through the Project BIM
Coordinator.
vii. ProjectWise Administrator (PWA)
a. Responsible for overall ProjectWise system and process infrastructure and not individual
project review process oversight.
b. Coordinate with Project BIM Coordinator for automated review model updates.
viii. External Reviewer

BIM Review Classifications

1. Clash Detection
2. Visual Inspection
3. QA Model Data Query
Examples of BIM Review by Discipline

 Architecture
a. Ducts in front of windows (visual)
b. Firewall (Visual)
c. Arch Fenestrations (Windows/Doors/Louvers) vs. Structural Cross Bracing (Clash AND Visual)
d. Verifying minimum door width for egress (Data)
e. Program Validation (Data)
 Civil
a. Site utilities aligned with building utility connections at 5’ line. (Clash)
b. Building is oriented on site correctly (Visual and Data)
c. 1354 Real Property (Data)
d. Storm water runoff (Data)
 Electrical
a. Verify clearance for access panels (Clash)
b. Water lines over electrical panels (Visual)
c. Interior Lighting Power Density (Data)
 Fire Protection
a. Fire Protection throws not blocked with clearance modeled. (Clash)
b. Sight line to emergency exit signs. (Visual)
c. Calculated maximum occupancy. (Data)
d. Detection Radius coverage. (Visual)
 Geotechnical
a. Coordinate subsoil strength with Structural Foundation (Data)
b. Boring holes vs. Utilities (Clash)
 Interiors
a. Furniture vs. Walls and Floors (Clash)
b. Clearance for egress around Furniture (Visual)
c. Equipment and Furniture placement in front of windows (Visual)
 Landscape
a. LEED verification (preserve open spaces) (Visual)
b. Parking per occupancy (Data)
c. Sidewalks lead to doors (Visual)
d. Standoff distance verification from parking (Visual and Data)
 Mechanical
a. Ducts vs. Lighting vs. Structure (Clash)
b. Access clearance modeling (Visual)

i. Equipment has been modeled
ii. Equipment has associated clearance modeled
iii. Clash check with objects and not clearances
iv. Clearance vs. clearance clash to be suppressed.
c. Electrical connection coordinated with Electrical Power (Data)
d. HVAC Duct System verification (Visual and Data)
 Plumbing
a. Plumbing Fixtures for water reduction (Data)
b. Plumbing System verification (Visual and Data)
c. Equipment room access and coordination (Clash)
 Structural
a. Framing vs. Mechanical Duct vs. Electrical Lighting (Clash)
b. Slabs on top of supporting members (Clash and Visual)
c. Integration with Structural analysis (Data)
d. Soft clearances for fire proofing (Clash)
 Survey
a. Existing conditions modeled in the correct location (Data and Visual)
 Telecommunication
a. Clearances around equipment panels (Clash)
b. Meets I3A requirements (Data)
c. Security access to equipment (Visual and Data)

Technical Instruction
Model Setup
Before beginning BIM Assisted Design Review some files need to be prepared to support the
workflow. Project review is performed using Bentley i‐Models, which are read‐only records of the
BIM model to ensure information‐rich, reliable, secure, and accurate data with provenance to the
native design authoring application(s).

1. There needs to be a person who has permissions across all discipline folders. It is essential that
all i‐Models are updated across all disciplines on a regular interval in order to coordination is
based on current design information.
2. Project BIM Coordinator (PBC) Creates Project Coordination Master Model (PCMM)
3. PBC Creates i‐Models of PCMM three days before BIM Coordination Meeting (completed by
close of business, 5‐20 minutes)
4. PBC creates one overlay file per discipline (see Saving Overlay Files)
i. PBC creates initial Clash Jobs setup for each disciplines (see Clash Job Setup)
 Level 1: Discipline Self‐Clash
 Level 2: Discipline against EACH discipline
 Level 3: Element‐specific check for common coordination issues
a. ex. Ducts clashing with Beams
 Level 4: Final comprehensive clash report
a. Discipline against ALL Disciplines

Create Project Coordination Master Model
1. Project Coordination Master Model (PCMM) should be created as soon as DMM’s are
created and only needs to be done once.
a. Open Bentley Building Suite
b. Create a new file named: [ProjectCode]_PCMM.dgn
i. Located in ...\Con_Docs\BIM_Models\_Coordination\ folder
2. In PCMM reference Discipline Master Models (DMM) for each Discipline
a. Make sure Ignore When Live Nesting reference setting is OFF for each referenced
b. Attachment method should be Coincident World (default)
c. Assign Logical Names to each referenced DMM using the discipline name
i. Example: DMMA – Architectural Master Model
d. Once attached make sure all DMM nested references are relevant and visible. If no
references appear in the DMM, check that Ignore When Live Nesting is OFF in the
DMM.

** INCLUDE DIAGRAM OF REFERENCE STRUCTURE **



Creating/Updating i-Models
An i‐Model is a container for multi‐discipline information published from known sources in a known
state at a certain point in time. The i‐Model combines all the graphics and business data intelligence,
as defined by the design application, into a single deliverable container for distribution. Because an
i‐Model optimizes the business data, the result is decreased file size and easier navigation. An i‐
Model contains links back to the original source data from which the i‐model was derived,
facilitating the life cycle review workflow
1. Open PCMM with Bentley Building Suite mode if not already open
a. File > Open, select [ProjectCode]_PCMM.dgn
b. Select User:_Coordination and Project: ProjectCode from pull‐down menus at right
2. Create/Update i‐Models
a. File > Publish i‐model
i. Leave Force republishing of all files AND Create a package unchecked. Cick
OK.
ii. Published i‐model will be created in the
..\Con_Docs\BIM_Models\_Coordination\ folder with the extension
dgn.i.dgn
 i‐Models instances will be created in each discipline folder for files
referenced by the Discipline Master Models.
iii. Processing the models can take some time the first time going through the
process. If it processes quickly, verify that Ignore When Live Nesting is OFF
in the Reference dialog.
3. Check the Message Center to verify all i‐model published successfully.
4. Exit Bentley Building Suite mode.



Saving Overlay Files
Bentley Navigator uses the concept of overlay files. An overlay file is a V8 DGN file that references
the original i‐Model file and works as a container for review‐specific content such as markups, saved
views, and clash detection jobs, while protecting the original file from modification. When opening
an i‐Model Bentley Navigator creates and opens a temporary overlay DGN file. If you modify this
overlay file and try to close or switch to another file, you will be prompted to save the changes to a
permanent overlay file. However, when you close the overlay file without doing any modifications, it
is deleted. Bentley Navigator will open existing overlay files directly rather than attempting to
create an overlay over an overlay.
1. Start Bentley Navigator using the Project Review > Bentley Navigator (SELECT series 3)
shortcut in the 09Q4b_V8i TriServices Workspace
2. Open i‐model
a. Choose appropriate Project and select __Coordination as the User.
b. Open file: …/BIM_Models/_Coordination/[ProjectCode]_PCMM.dgn.i.dgn
3. Save one overlay file per discipline
a. Save in the …\Con_Docs\BIM_Models\_Coordination\ folder
b. File > SaveAs, [ProjectCode]_PCX.overlay.dgn where X is the discipline designator.
i. Ex: [ProjectCode]_PCP.overlay.dgn for the Plumbing Coordination overlay
file.

Clash Job Setup
1. Using Bentley Navigator, open one of the discipline overlay files
([ProjectCode]_PCX.overlay.dgn)
2. Open the Clash Detection dialog by selecting the Clash Detection icon (located in the Clash
Detection task of the Task Menu)
TIP: Dock the Clash Detection window at the bottom of the screen by dragging the window and
releasing it on top of the glyph that appears at the bottom while the window is being dragged
3. Set up Discipline Self‐Clash Job
a. From the Clash Detection dialog, create a New Clash Job (Job > New Job or Blank
Sheet icon in top left)
i. Name the clash job “1 [ACTIVE DISC]_[ACTIVE DISC]”
 i.e. 1 MECH_MECH, 1 ARCH_ARCH
ii. With the new clash job selected in the left pane, make sure the Criteria tab
is active and expand the References window
b. Drag/Drop the active discipline DMM from References dialog to Set A
i. The “active discipline DMM” is the Discipline Master Model coinciding with
the discipline identified for the active overlay file
c. Check the box for Self Check in Set A
d. Save Job (Job > Save or diskette icon in Clash Detection window)
4. Setup Clash Job for active discipline against EACH Discipline
i. Name the clash job “2 [ACTIVE DISC]_[DISC_X]”
 i.e. 2 MECH_ELEC, 2 ARCH_STRUC
b. With the new clash job selected in the left pane, make sure the Criteria tab is active
and expand the References window
c. Drag/Drop the active discipline DMM from References dialog to Set A
d. Drag/Drop the DMM coinciding with DISC_1 from References window to Set B
window. Save Job (Job > Save or diskette icon in Clash Detection window)
e. Repeat Steps a‐d until the active discipline has a Clash Job against each of the other
disciplines
i. MECH_ARCH; MECH_ELEC; MECH_FIRE; MECH_PLUMB; MECH_STRUC;
MECH_TELE; etc.
5. Setup Clash Job for Discipline against ALL Disciplines (to only be used for submittal reporting
purposes)
i. Name the clash job “4 [ACTIVE DISC]_ALL”
 i.e. 4 MECH_ALL
b. With the new clash job selected in the left pane, make sure the Criteria tab is active
and expand the References window
c. Drag/Drop the active discipline DMM from References dialog to Set A
d. Drag/Drop ALL the other discipline DMM’s from References window to Set B
window. Save Job (Job > Save or diskette icon in Clash Detection window)


Reviewing Clashes
A key component of any successful design review workflow is the ability to analyze the accuracy of
your 3D models, to ensure that all components are properly spaced for installation, and to avoid
costly change orders. The capability to identify and resolve conflicts in the design phase before
construction starts will help to reduce your risk, improve the quality of your models, and save you
money by avoiding on‐site errors that can result from inaccurate design. It is important that the
decision makers are reviewing the clashes in order to streamline the design process and resolve
conflicts quickly. Discipline teams should take ownership and resolve clashes that are clearly their
responsibility prior to the weekly coordination meeting. Clashes not claimed by any one discipline
prior to the coordination meeting should be discussed and assigned during the coordination
meeting. Clash detection should be performed early and often as it helps identify potential conflicts
and promotes cross‐discipline coordination early in the design process when costs associated with
design changes are lowest.

Certain clashes are acceptable and can be marked as “Accepted”, however, it is recommended that
“Accepted” clashes be reviewed periodically to verify that the clash condition is still acceptable. An
example of an acceptable clash would be a pipe running perpendicularly through a wall above the
ceiling.
There are three main types of clashes:
 Hard Clash: Occurs when two modeled elements share the same digital space in the BIM model.
 Soft Clash: Occurs when a modeled component intrudes on a defined clearance that we define
around another set of modeled components.
o Ex. Spray‐on fire‐proofing on a steel structure or insulation around duct/piping.
 Operational or Functional Clash: Occurs when an object intrudes on the space required for the
movement of a building component. This is the hardest type of clash to detect. While it is good
practice to model an object to represent the operational space, this is not always practical.
o Ex. The swing of a door or the space required to change a filter in an air‐handling unit.
1. Using Bentley Navigator, open [ProjectCode]_PCX.overlay.dgn
a. Where “X” indicates the discipline for review
2. Perform Clash Detection Check
a. Check Discipline against itself (DL)
i. Expand the Clash Detection Task from the Task menu and select the Clash
Detection icon
ii. Select the Clash Job for review
 Example: ARCH_ARCH
b. Expand Clash Job to review the Clash Results
i. If the Results are not showing, this indicates that the Clash Job has not been
processed yet.

ii. Update the Clash Results by selecting the Process button at the bottom
right‐hand corner of the dialog.
 If the Results were not previously displayed under the Clash Job,
they will now be discovered and displayed in the Results tab.
 Clash Detection processing time varies based on the complexity of
model and applied rules
 Save the Clash Job
5. Review Intra‐Discipline Clashes
i. Select a clash in the Results tab list.
a. The model will zoom in on the clashing items and turn the rest of the model
transparent
b. Navigate between clashes using the Previous Clash and Next Clash icons at the top
left of the Clash Detection dialog
ii. Assign a status to clashes
a. For acceptable clashes, change Status from New to Accepted and give a brief
description of why it is acceptable in the description field on the far right.
iii. Selecting Accepted as the status will automatically populate the Accepted
By and Accepted On fields with the active username and current time.

 Change Status to Assigned for clashes requiring
design/modeling changes
i. Selecting Assigned as the status will automatically
fill in the Assigned By and Assigned On fields with
the active username and current time.
ii. Assign the clash to a person by typing their name in
the Assigned To field
iii. Provide a description of the clash in the Description
field (last column)

 If more than a brief description is needed , create a Markup
by clicking on the Create Markup button:


Perform Visual Model Check
Performing a visual inspection of the model is an important measure to detect errors in the design
or modeling that otherwise might not be apparent in the 2D sheets or detectable by the clash
detection process. These inaccuracies might be items floating in space, duct/piping that does not
align, or exterior louvers placed directly in front of a beam. By not identifying and correcting these
inaccuracies downstream outputs from the model such as quantities, cost estimates, fabrication, or
2D drawings could be falsely impacted. Additionally, visual checks can identify design and
constructability issues that likely would not be discovered until in the field, which would result in
expensive change orders.

Regular visual model checks should be performed by the architect/engineer responsible for the
design and engineering of the project.
1. Using Bentley Navigator, open [ProjectCode]_PCX.overlay.dgn
a. Where “X” indicates the discipline for review
2. Perform visual check
a. Clip Volume
b. Leverage Project Explorer to hide or display references/levels or change the color
and/or transparency of references/levels.
c. Item Browser
d. In addition to looking for clashes, also look for modeling anomalies such as items
outside of the building extents

Glossary
1. USACE review process
a. Design Coordination Meetings – Regularly scheduled meetings conducted by the
design team during the project.
b. QCR – Quality Control Review is an internal review by the design team before
submitting for external review.
2. ITR – Independent Technical Review is a review performed before a Design Review by an
outside group which can include another District or an A/E.
3. Design Review – Review by the customer, user representatives, and USACE resident/area
offices (construction management) which commonly use Dr. Checks for collecting review
comments.
4. BIM review process
5. Discipline Self‐Check – Process of a discipline checking and resolving conflicts which they
have control over. This process is required prior to Inter‐Discipline Coordination.
6. Inter‐Discipline Coordination – Process of two or more disciplines collaborating to resolve
issues which require negotiation. Discipline Self‐Checks are required to be performed prior
to Inter‐Discipline Coordination.
7. A Clash Job is a definition such as ARCH vs. ARCH or ARCH vs STRUCTURAL and has all of the
settings for performing that clash detection process.
8. Clash type classifications
a. Level 1: Discipline against self
b. Level 2: Discipline against other disciplines
c. Level 3: Component check against component
d. Level 4: Final comprehensive clash report
e. Hard clash
a. Cross bracing clashing with a window
f. QA Check
a. Cross bracing in front of a window
9. .dgn.i.dgn is an i‐Model. I‐Models have references to other i‐Models.
10. .i.dgn is an i‐Model package. A package can have embedded or non‐embedded references to
other imodels.
11. BIM QA/QC Certification Report requires the Discipline Leads to ensure that the model is
sufficiently detailed to reflect design intent, is free of hard conflicts, and that items
identified as acceptable are valid.


USACE BIM Design Review Process 2 - 5

Uploaded by

Copyright:

Available Formats

USACE BIM Design Review Process 2 - 5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

USACE BIM Design Review Process 2 - 5

Uploaded by

Copyright:

Available Formats

USACE BIM Assisted Design

FILE: C:\Users\travis.wollet\Desktop\Design Review\USACE BIM Design Review Process 2 (5).docx Page 1 of 27

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 2 of 27

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 3 of 27

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 4 of 27

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 5 of 27

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 6 of 27

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 8 of 27

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 9 of 27

Van, we need to add stuff here

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 10 of

Van, we need to add stuff here

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 11 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 13 of

Examples of BIM Review by Discipline

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 14 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 15 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 16 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 17 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 18 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 19 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 20 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 21 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 23 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 24 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 25 of

Perform Visual Model Check

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 26 of

PATH: pw:\\NWS-AS01PJW.nws.ds.usace.army.mil:cenws01\Documents\Research and Development\BIM\Clash Page 27 of

You might also like