Professional Documents
Culture Documents
Document Version 01
SECTION 1. OBJECTIVE
1.1 Introduction/purpose
The intent of this project BIM Execution Plan is to provide a framework that will let the
owner, architect, engineers, and construction manager to deploy building information
modeling (BIM) technology and best practices on this project faster and more cost-
effectively.
This plan delineates roles and responsibilities of each party, the detail and scope of
information to be shared, relevant business processes and supporting software. The BEP will
be revisited and updated at each design phase and at the onset of construction.
This new construction office building project will benefit from building a digital 3D model to
visualize and coordinate the design prior to construction. The implementing of BIM will
facilitate a higher level of collaboration between the design teams, GC and the
subcontractors/trades.
For the purpose of this project, BIM will be used for the following uses:
• Design authoring
• Record modelling
• 3D Coordination
• Engineering analysis
• Design reviews
• Cost estimation
• Existing conditions modelling
• Digital fabrication
• 3D Control and planning
• Building maintenance scheduling
• Asset management
Below are the primary contacts from each stakeholder for BIM-related topics. These contacts
should be used to obtain information and answer any questions related to their organizations
models or downstream needs relevant to BIM and BIM deliverables.
Design Contacts
Construction Contacts
Below is a list of all the uses for which the technology of BIM will be used by the project team:
The table given below indicates the model elements that need to be modelled in each discipline and the
parties who are responsible for it.
All members of the Project Team are to use the same shared coordinates system in all models as
defined by the lead designer and recorded in the project BIM Execution Plan.
In order to accurately and consistently locate the models produced by individual project team
members the following factors should be used:
➢ Buildings and site locations shall be set at the correct longitude and latitude.
➢ True north should be set correctly.
All performed scope of work shall be in 3D format except as noted in the trade specific description.
a. All models should include separate 3D representations of required clearances and/or access
requirements for equipment access, light clearances, overhead cable tray access, etc. These
clearance/access models should be in a separate layer(s) for each trade clearly labeled as such.
b. Modeled insulation should be in a separate layer from other model elements and labeled as such.
The table given below describe what needs to be modelled in each discipline.
HVAC Piping Piping types with insulation, piping materials, access panels,
valves, equipment, concrete pads, bases, flanges/coupling,
hangers (including seismic), racking. Piping less than 1” will not
be coordinated and is shown for intent only.
Plumbing Drawings Piping types, insulation, pipe material, access panels, valves,
equipment, concrete pads, bases, flanges/couplings, hangers
(including seismic), racking steel, gravity fed piping (sloped per
code), in-wall plumbing systems being prefabricated. Piping less
than 1” will not be coordinated and is shown for intent only.
Fire Protection Drawings Piping, sprinkler heads, branches, access panels, valves,
equipment, concrete pads, bases, flanges/coupling, hangers
(including seismic).
Electrical Drawings: All conduits larger than 1”, conduit racks and supports, cable
trays, access panels, equipment, concrete pads, bases,
disconnects, breakers, panels, light fixtures, pull boxes, junction
boxes, lighting supports, hangers.
Architectural Drawings: Ceilings (hard and lay-in), soffits with framing, shaft and wall
chase locations, wall thickness and heights, exterior walls, curtain
walls, windows, detailed wall section, roof section, room
schedule, area schedule.
Structural Drawings Foundation/Footings, grade beams, elevator pits and walls, shear
wall locations, precast concrete locations, columns, beams,
bracing (especially x-bracing), slabs, curbs, ramps.
This Information Exchanges worksheet is intended to communicate all required model delivery and
exports required between project team members to facilitate coordination and follow-on uses of
BIM across the project.
3.3 Software
Models submitted for coordination and uploaded to the Collaboration site are to follow the file
naming structure provided below:
Examples:
HP-L01-2023-10.dwg
PL-DWV-L01-2023-10.dwg
ST-L01-2023-10.nwc
Multiple updates may be made in a given week using the same file name. The final update for the
week will be considered the final submittal for the week.
Each discipline shall model their systems components to ensure proper coordination with
all other disciplines. The intent of this coordination is to identify all clashes in the merged
model and resolve them prior to field installation.
• All elements in the models shall be ACIS solid objects (not polymesh or polysurface
elements).
• Include only the specific subcontractor’s scope of work. (Do not include any
architectural, structural, or other trades’ elements – The intent is to avoid duplicate
elements within the combined model)
• Systems that are too dense and complicated to model (e.g. electrical room equipment
and fire pump room equipment) may be represented by 3D no-fly zones.
• Hangers and seismic bracing shall be included for each scope. Clash
avoidance/detection pertaining to hangers and bracing is the last step of coordinating
a floor, and as such, these components should be modeled last.
• Include only the work that is to be constructed – remove any “scratch” work or 2D
reference drawings before posting a model. • Use proper Project Base Point and
orientation
For uploading model, use color coding and model abbreviation below.
Milestone Date
Preliminary Coordination Meeting XX/XX/2023
First Coordination Meeting XX/XX/2023
Basement Floor FAB Model Completion XX/XX/2023
Ground Floor FAB Model Completion XX/XX/2023
First Floor FAB Model Completion XX/XX/2023
Second Floor FAB Model Completion XX/XX/2023
a) Coordination meetings will typically occur each Monday at x:xx via xx-xx.
b) Weekly model submittals are due two days prior to the coordination meeting (Friday at
7:00pm).
c) Web-based weekly coordination meeting (for the duration of the coordination period).
Note that in-person meetings may be required to resolve major conflicts.
e) Subcontractors are expected to have offline dialogue with other trades in order to resolve
and coordinate simple clashes.
f) Subcontractors shall bring any of their submittals (e.g. light fixture product data)
necessary for coordination to the 3D coordination meetings.
h) At the conclusion of each coordination meeting the Merged Model(s) with saved
viewpoints of open issues will be posted to Procore for the team’s use and record
b) Subcontractors shall review the content of the merged model in Navisworks on a weekly
basis and identify design/trade issues. They will begin resolving these issues prior to
weekly coordination meetings and be prepared to discuss their issues with the team.
c) The day before the coordination meeting, LEGO will collect the most current models at
the end of the day and review the clash detection ran by the subcontractor. The
subcontractor will be responsible for preforming its own clash detection against the deep
site utilities
e) LEGO requires subcontractors to update their models with an NWC and a DWG if any
revisions are made.
f) It shall be the goal of the Design/Construction Teams to reduce the number of changes
during construction due to major building interferences to zero. LEGO will lead the
coordination process.
g) LEGO will hold a preliminary BIM coordination meeting. Each Contractor must be
represented by the individual that is directly responsible for the coordination of the
project.
h) The preliminary coordination meeting will establish parameters that cannot be changed
during the process such as “(0,0,0)” for all the trades to use for their drawings insertion
point. Once this is agreed upon it cannot be moved.
j) LEGO will build the federated model and generate the clash reports using Autodesk
Navisworks 2018. Each contractor revises their models based upon resolution decided
during coordination meetings, to be completed prior to the next coordination meetings.
k) File sharing software and frequency of upload will be discussed at this meeting.
l) All files uploaded for coordination shall be in NWC or DWG format. Each trade shall be
coordinated with architectural and structural prior to upload. Revit files may be uploaded
in native format, but a corresponding NWC or DWG file must be provided.
m) Weekly submittals must include a short description of changes since previous submittal
submitted via email to the entire coordination team.
n) Coordination Meetings are NOT to be used as clash detection meetings. The clash report
shall be issued in advance of the meeting or directly after the meeting.
o) Every contractor shall be represented at each meeting. The Architect and Engineers are
encouraged to attend as well.
q) Subcontractor shall identify design conflicts with elements for their scope of work and
submit relevant RFIs to LEGO in a timely manner.
s) The Architect may be required to update the Architectural design model to reflect
necessary changes that are surfaced during the coordination process.
LEGO will provide a file sharing site (Procore) as a central depository of coordination related
documents.
4.5 Procore
LEGO will use Procore as a central depository to share all documents related to the project. Each
subcontractor will be provided a folder to upload all of their deliverables to Procore.
e. Once the model is free of collisions, a sign-off meeting will be held. All trades are required to
attend. A model sign-off sheet will be issued that will include the final drawing file name (as
described in Appendix A) for each trade. All trades will sign.
f. The Signed-off NWD will be uploaded to Collaboration for the use of each trade. It is the
responsibility of each trade to ensure that items that are not shown in the model are field
coordinated around all other trades.
Meeting Date:
Component Models:
Filename File Description File Date File Author