The document presents a BIM Execution Plan case study for the Broward County Judicial Complex renovation, detailing the project's design, execution process, and organizational roles involved in BIM. It outlines the learning objectives for participants about implementing BIM strategies, clash detection, project coordination, and transitioning to the construction phase. Key elements include the project's goals, the structure of the BIM execution plan, and the iterative process of updates throughout its phases.

1. Chapter logo here
BIM EXECUTION PLAN
Case Study: Broward County Judicial Complex Renovation
Presented by:
Hernan A. Pagan
Project Manager
Russell and Dawson Inc.
hernan.pagan@rdaep.com
1Presented by Russell and Dawson

2. LEARNING OBJECTIVES 1
Participants will learn How to execute a BIM Execution Plan
 Breakdown of who is doing what, during each phase of design and construction
 Organizational roles between the trades
 File structure for large format projects
 When to do quality control and clash reports
 Bringing a project through LOD 100- 500
 Controlling roles and responsibilities during construction
Presented by Russell and Dawson 2

3. LEARNING OBJECTIVES 2
Participants will know when and how to use Clash Detection
 Reasons to use Clash Detection
 Step-by-step process of how participants should set up team meetings for clash report among various disciplines in order to resolve clashes
 Light walk-through of How to prepare a Revit file to a Navisworks format.
Presented by Russell and Dawson 3

4. LEARNING OBJECTIVES 3
Participants will learn how to co-ordinate various disciplines i.e. Architecture,
Structure, Electrical, Plumbing & HVAC
 Coordinating deliverables, formatting, roles and BIM uses
 Appropriately setting up meetings for coordination & reviewing reports on clashes.
Presented by Russell and Dawson 4

5. LEARNING OBJECTIVES 4
How to transition to Construction phase and use of BIM during Contract
Administration
 Using COBie
 Discussion of roles and responsibilities of the Architect vs the GC during the BCJC project
 Revit model ownership during construction phase as per the BCJC project
 Final deliverables to ownership from A/E/C
Presented by Russell and Dawson 5

6. PROJECT DETAILS
 Project Name
 Area
 Address
 Project Type
 Timeline
 Service Provided
 Design Tools Used
 Certification
 Architect
: BCJC Midrise Full Building Renovation
: 64,000 SQFT, Four-story facility
: 540 SE 3rd Ave, Fort Lauderdale, FL 33301
: Full Renovation
: 2013-2018
: Architectural Design services
: Autodesk’s AutoCAD and Revit Software
: LEED Gold [New Construction]
: Singer Architects Inc (a Russell and Dawson group company)
Presented by Russell and Dawson 6

7. PROJECT DETAILS
Presented by Russell and Dawson 7

8. PROJECT DETAILS
Presented by Russell and Dawson 8

9. ASSEMBLING THE BIM EXECUTION PLAN (BEP)
Presented by Russell and Dawson 9

10. BIM EXECUTION PLAN
What is a BIM execution plan (BEP)?
 From the first lines of our original document:
“This document is the project team’s BIM Execution Plan (v 3.5) for use during the design phases of the BCJC Midrise Renovation project. This
document summarizes the standards and procedures necessary for a coordinated BIM effort among multiple firms within the design team”
 This project format was a first for the County and is meant to set the standard for future projects
 The BIM Manager typically updates this document throughout the project duration
Presented by Russell and Dawson 10

11. BIM EXECUTION PLAN
Updating the BEP
 BCJC midrise BEP went through 7 revisions at each phase from Programming till Construction. The document was originally written
06/12/2013 & was finalized as Version 3.5 dated 03/07/2016
 It was found that as the project developed, so did the BEP. The new phases added need for additional clarification on roles and
responsibilities, until it was finalized at the permitting & construction phase
 We had multiple BIM managers review and edit the document throughout the project
 When the project was turned over to the construction team, they developed a similar document specific to their own tasks and
responsibilities during construction which mirrored the BEP during design.
Presented by Russell and Dawson 11

12. TABLE OF CONTENTS
SECTION A BIM PROJECT EXECUTION PLAN OVERVIEW
SECTION B PROJECT INFORMATION
SECTION C KEY PROJECT CONTACTS
SECTION D PROJECT GOALS / BIM USES
SECTION E ORGANIZATIONAL ROLES / STAFFING
SECTION F BIM PROCESS DESIGN
SECTION G BIM AND FACILITY DATA REQUIREMENTS
SECTION H COLLABORATION PROCEDURES
SECTION I QUALITY CONTROL & LEVEL OF DEVELOPMENT
SECTION J TECHNOLOGICAL INFRASTRUCTURE NEEDS
SECTION K MODEL STRUCTURE
SECTION L PROJECT DELIVERABLES
SECTION M REVIT MODEL OWNERSHIP & COBIE RESPONSIBILITY
SEQUENCE/ STRATEGY
SECTION N BIM ROLES AND RESPONSIBLITIES DURING
CONSTRUCTION
SECTION O ATTACHMENTS
SECTION P GLOSSARY
Presented by Russell and Dawson 12

13. PROJECT GOALS / BIM USES
Presented by Russell and Dawson 13

14. PROJECT GOALS / BIM USES
Organization BIM Uses/ Project Goals
Architects Design Authoring, Design Coordination, Drawing Production, Clash Detection
& COBie Implementation
Asset Management, Design Reviews, Space Management & Tracking, Record
Modeling, Code Validation, Programming, Design Reviews, Existing Conditions
Modeling.
Structural Engineers Design Authoring, Code Validation, Design Reviews, Design Coordination,
Drawing Production & Clash Detection, Engineering Analysis, Structural
Analysis
Civil Engineers, Landscape Architects Drawing Production, Design Reviews
Engineers - Mechanical, Electrical, Plumbing & Fire Protection Design Authoring, Design Coordination, Drawing Production, Clash Detection
(MEP-F Specific) & COBie Implementation, Space Management And Tracking,
Engineering Analysis, Code Validation, Programming, Design Reviews, Existing
Conditions Modeling.
Construction Team To be determined
Presented by Russell and Dawson 14

15. PROJECT GOALS / BIM USES
Breakdown of roles within Architects Team BIM Uses/ Project Goals
Architect / Project Manager– Revit • Programming
• Existing Conditions Modeling
• Code Validation
• Design Authoring
• Design Coordination
• Drawing Production
• Record Modeling
BIM Manager – Revit, Navisworks, Excel • Clash Detection & Design Reviews
• Verifying Architectural, MEP, FP & Structural components, all fit in the
allotted space and do not clash.
• COBie Implementation, Space Management & Tracking
• Asset Management for equipment within building for Facility
Maintenance (FM) use once the building is turned over.
Presented by Russell and Dawson 15

16. ORGANIZATIONAL ROLES & COLLABORATION
PROCESS
Presented by Russell and Dawson 16

17. ORGANIZATION ROLES & COLLABORATION PROCESS
Singer Architects
A Russell and Dawson INC Company
MEP & Fire Protection
Delta G Consulting Engineers
Structural Engineers
S&F Engineers
Civil Engineering
Flynn Engineering
Landscape Architects
Architectural Alliance
LEED Consultation
Spinnaker Group
Cost Estimates
CMS
Construction Team
Pirtle Construction
OWNERSHIP
Presented by Russell and Dawson 17

18. ORGANIZATION ROLES & COLLABORATION PROCESS
Meeting Procedures:
MEETING TYPE PROJECT STAGE PARTICIPANT FREQUENCY LOCATION
Kick-off Notice to Proceed Entire Project Team Once County Gov. Center
Design Coordination Pre Design/Design
Development/Construction
Documents
Team Leaders
(A/E)
Weekly Conference Call
BIM Meetings Pre Design/Design
Development/Construction
Documents
BIM Managers Weekly / As required Conference Call/ County
Gov. Center
Note - BIM meetings mainly involve the participation of BIM Managers & Project Managers for coordination. However, the County & other interested parties may join if
requested and a physical meeting can be scheduled accordingly when required.
Presented by Russell and Dawson 18

19. ORGANIZATION ROLES & COLLABORATION PROCESS
Project Delivery Schedule:
INFORMATION EXCHANGE DESIGN TEAM FREQUENCY DUE DATE NATIVE FILE TYPE
Design Authoring Architect Weekly Friday ( By 5 PM ) .RVT & PDF
Structural Engineer As Requested & Based on
Development
.RVT & PDF
MEP-FP Engineer Weekly Friday ( By 5 PM ) .RVT & PDF
Civil Engineer As Requested & Based on
Development
.DWG & PDF
Presented by Russell and Dawson 19

20. FILE STRUCTURE
Presented by Russell and Dawson 20

21. MODEL STRUCTURE
Programs Add-ons Purpose
Revit COBie Extension Revit add-in
Navisworks Addon
Modeling, Drafting & COBie information input
AutoCAD Drafting
Navisworks Manage Clash Detection
A360 Collaboration for Revit / BIM 360 Glue &
Field
Construction Administration
AiM / Assetworks Facility Management
Presented by Russell and Dawson 21

22. ORGANIZATION ROLES & COLLABORATION PROCESS
BIM USE DISCIPLINE SOFTWARE VERSION
Design Authoring Architecture Revit 2014-2015
Design Authoring Structure Revit 2014-2015
Design Authoring MEP-FP Revit 2014-2015
Design Authoring Civil AutoCAD -
Design Authoring Landscape AutoCAD -
Design Authoring Survey AutoCAD -
Review Broward County Revit 2015
Facilities Maintenance Coordination Broward County Revit, AiM, AssetWorks 2014-2015
COBie Implementation Broward County AiM, AssetWorks 2015
Construction Management/ COBie GC Revit 2015
3D Coordination / Clash Detection ALL Navisworks Manage 2014-2015
COBIE Export ALL COBie Extension Revit add-in 2014-2015
Construction Administration (RFIs
etc)
ALL A360 Collaboration for Revit / BIM
360 Glue & Field
2015
22

23. ORGANIZATION ROLES & COLLABORATION PROCESS
Model Structure: Naming Conventions, Model Link Structure
0602013001_ARCH_ CENTRAL_2014.RVT
0602013001 _STRUC_ CENTRAL_2014.RVT
0602013001_MECH_ CENTRAL_2014.RVT
0602013001 _ELEC_ CENTRAL_2014.RVT
0602013001_PLUM_ CENTRAL_2014.RVT
0602013001_FIRE PROTECTION_ CENTRAL_2014.RVT
0602013001 _FURN_ CENTRAL_2014.RVT
CAD Files (CIVIL)
CAD Files (LANDSCAPE)
CAD Files (SURVEY)
CAD Files (Arch. Exist & Phase 1 Furniture/Partitions)
ProjectNumber_Discipline_Central_Version.RVT (Should a file be upgraded to another
version of Revit, the original name will
remain as is, in order to preserve links &
file references.)
Architecture Model 0602013001_ARCH_CENTRAL_2014.RVT
Furniture Model 0602013001_FURN_CENTRAL_2014.RVT
Structure Model 0602013001_STRUC_CENTRAL_2014.RVT
Mechanical Model (HVAC) 0602013001_MECH_CENTRAL_2014.RVT
Electrical Model 0602013001_ELEC_CENTRAL_2014.RVT
Plumbing Model 0602013001_PLUM_CENTRAL_2014.RVT
Fire Protection Model 0602013001_FIRE
PROTECTION_CENTRAL_2014.RVT
LOD 350/400/500 models Similar file naming convention by GC
Presented by Russell and Dawson 23

24. QUALITY CONTROL & CLASH DETECTION
Presented by Russell and Dawson 24

25. QUALITY CONTROL & CLASH DETECTION
Quality Control
 Visual Check
• Ensure that design intent has been followed properly and there are no unintended model components
 Interference Check
• Detect problems in the model where two model components are clashing
 The entire design team is responsible for quality control.
Presented by Russell and Dawson 25

26. QUALITY CONTROL & CLASH DETECTION
 Why use Clash Detection?
 To verify all items fit within the confines of the structure
 Provides list of items which intersect with fire rated assemblies in order to provide appropriate fire rating
 RFIs based on MEP coordination are mostly eliminated and reduces delays to construction due to waiting for answers
 Provides a more accurate & cleaner Revit file to turn over to ownership for their future use.
Presented by Russell and Dawson 26

27. QUALITY CONTROL & CLASH DETECTION
Using Navisworks for Clash Detection
INFORMATION EXCHANGE DESIGN TEAM FREQUENCY DUE DATE NATIVE FILE TYPE
3D Coordination / Clash
Detection
Architect Project Milestone &
Periodically As Needed
DD :
06/09/2014; 06/16/2014;
06/23/2014
50% CD:
08/25/2014; 09/15/2014;
09/29/2014
100% CD:
12/01/2014; 12/29/2014;
01/05/2015
.NWC
Structural Engineer Project Milestone &
Periodically As Needed
.NWC
MEP Engineer Project Milestone &
Periodically As Needed
.NWC
Civil Engineer N/A
Weekly reports were generated and sent out on almost every Monday.
Presented by Russell and Dawson 27

28. QUALITY CONTROL & CLASH DETECTION
Clash Report Meetings
 Typically, meetings would be internal coordination sessions between the A/E design & project team
 Construction team’s (GC) attendance, up to permitting phase, is welcome but not mandatory
 If the owner’s involvement is needed to resolve any issues, a notification would be provided to the owner for follow up meetings or input
 Each discipline must submit a clean *.RVT file minimum 3 days before the meeting
 Prior to the meeting, architects would run the clash model and generate a clash report for the meeting
 During the clash detection meeting, the group would review the main clashes and discuss the strategy to resolve the conflicts
 Within a week after the meeting, the Project team would revise model to address clashes found.
Presented by Russell and Dawson 28

29. QUALITY CONTROL & CLASH DETECTION
NAVISWORKS File Setup
 Verify all work sets are correct, run ‘purge’ of excess families
 Duplicate all RVT files and clean up files to minimize size.
• Create new 3D view for clash detection, eliminate all other views(to reduce file size and help speed up clash detection).
• Unload all links, remove all CAD files, turn off/ remove unwanted objects
 Convert all files to Navisworks file .NWC via Revit Navisworks add-on.
Presented by Russell and Dawson 29

30. QUALITY CONTROL & CLASH DETECTION
Navisworks Clash Setup
 Import files into Navisworks
 Select worksets/ families to be tested
 Verify the dimensional tolerance for clashes in order to reduce unnecessary clashes
 Review clashes, approve non-clashes, adjust 3d views provided as required to clarify the clashes on the report
 Export clash report format and send it to your team.
Presented by Russell and Dawson 30

31. QUALITY CONTROL & CLASH DETECTION
Typical File Output
Presented by Russell and Dawson 31

32. QUALITY CONTROL & CLASH DETECTION
Clash Log for the BCJC Project
Presented by Russell and Dawson 32

33. LEVELS OF DEVELOPMENT
Presented by Russell and Dawson 33

34. LEVEL OF DEVELOPMENT
Setting a Target For the Level of
Development (LOD) will Depend on the
Future Use of the Project
•BCJC Midrise Renovation was intended to be used heavily by the Facility
Management for the maintenance of the building. Construction Operations
Building Information Exchange Formatting (COBie) was requested as the
primary format for specific systems within the building.
• COBie is a data format for BIM which focuses on asset information on
objects within the project.
Presented by Russell and Dawson 34

35. LEVEL OF DEVELOPMENT
COBie Development Stages:
1. LOD 100 – Schematic Design
2. LOD 200 – Design Development
3. LOD 300 – Construction Docs.
4. LOD 350-400 – Construction Input
5. LOD 500 – Facility Management
Presented by Russell and Dawson 35

36. LEVEL OF DEVELOPMENT
Architectural & MEP-FP Teams:
 LOD 100 - Overall building massing indicative area, height, volume, location, and orientation may be modeled in three dimensions or
represented by other data.
 LOD 200 - Model elements are modeled as generalized systems or assemblies with approximate quantities, size, shape, location, and
orientation.
 LOD 300 - Model Elements are modeled as specific assemblies accurate in terms of quantity, size, shape, location, and orientation. Non-
geometric information may also be attached to Model Elements and equivalent to 100% construction documents.
 Non-graphic information may also be attached to the Model Element.
Presented by Russell and Dawson 36

37. LEVEL OF DEVELOPMENT
Construction Team & Facility Management:
 LOD 400 - The Model Element is graphically represented within the Model as a specific system, object or assembly in terms of size, shape,
location, quantity, and orientation with detailing, fabrication, assembly, and installation information.
 LOD 500 - BIM for Facility Management Model Elements are modeled as constructed assemblies-actual and accurate in terms of size, shape,
location, quantity, and orientation. Non-geometric information may also be attached to modeled elements. Facilities Management
information made available to Construction Operations Building Information Exchange (COBIE) standards.
 Non-graphic information may also be attached to the Model Element.
Presented by Russell and Dawson 37

38. LEVEL OF DEVELOPMENT
COBie Responsibilities Sample
Presented by Russell and Dawson 38

39. LEVEL OF DEVELOPMENT
COBie Responsibilities Sample
Presented by Russell and Dawson 39

40. LEVEL OF DEVELOPMENT
COBie Export Sample
Presented by Russell and Dawson 40

41. BIM ROLES AND RESPONSIBLITIES DURING
CONSTRUCTION
Presented by Russell and Dawson 41

42. BIM ROLES AND RESPONSIBLITIES DURING CONSTRUCTION
Revit Model Ownership & COBie Responsibility Sequence/ Strategy
42

43. BIM ROLES AND RESPONSIBLITIES DURING CONSTRUCTION
 The Architecture/Engineering (A/E) design team will develop LOD 300 BIM models during the bidding/permitting phase to incorporate County
comments, permitting comments, pre-construction RFI’s, and any coordination changes prior to construction.
 The construction team (GC) shall work with Owner and design team to develop the Virtual design & Construction (VDC) plan based on BEP
version 3.5 for implementation during construction, to include BIM uses such as: 3D Coordination (clash detection), Phase Planning (4D
Modeling), Digital Fabrication, Cost Estimation (quantity take-offs), Existing Conditions Modeling, Space Management and Tracking, and COBie
information input into Revit models.
 Latest Revit models shall be provided to the GC after permits are approved and at issuance of Notice to Proceed 1 to GC, for development of the
LOD 350/400/500 models (shop drawings) as defined by BIM forum and as required by County.
 Not all items may need to be developed to LOD 350/400. GC shall coordinate with County and develop MEP-FP, Architectural & Structural items
to LOD level required for each discipline as directed by County.
 Once construction begins, the GC shall be responsible for all LOD 350/400/500 Revit model developments and any changes to COBie data
based on field verification, constructability, final product selection & installation.
 The GC shall use BIM 360 Field for the gathering of COBie field data from Construction Manager/ Superintendent and all sub-contractors in order
to integrate all information into the BIM models throughout construction.
Presented by Russell and Dawson 43

44. BIM ROLES AND RESPONSIBLITIES DURING CONSTRUCTION
 GC shall review subcontractors BIM proficiency and qualifications.
 For instances where drawing modifications are required from A/E team to provide sketches, Supplemental Instructions, etc.
 Construction team (GC) shall be responsible to provide a location and access for the upload/ download of the latest Revit models by A/E teams /
sub-contractors to add information, answer RFI’s, etc. Construction team (GC) shall keep daily backups of all models. Should the GC give
ownership of the same model to multiple subcontractors, the GC shall be responsible for organizing and merging all new information into one
model including, but not limited to: shop drawing sheets, views, updated Revit components, COBie information, etc.
 At the end of construction phase, the GC shall provide COBie deliverables to the Owner for Facilities Maintenance (FM)/ Operations &
Maintenance (O&M) as required by the County. The GC shall also deliver a construction model (LOD 500) to the Owner for FM / O&M use at end
of construction.
 At the end of construction phase, the GC shall provide as-built full size drawings and PDFs and transfer the latest Revit models to the A/E team for
Review.
Presented by Russell and Dawson 44

45. LEED
Presented by Russell and Dawson 45

46. THE PROJECT
LEED Scorecard
Presented by Russell and Dawson 46

47. Broward County Judicial Complex Management
Thank you.