BIM Execution Plan - cmfac. · PDF file3 The intent of this BIM Execution Plan is to define a...
Transcript of BIM Execution Plan - cmfac. · PDF file3 The intent of this BIM Execution Plan is to define a...
1
BIM Execution
NTM Project‐ Sample
Fourth Edition 08‐15‐2012
2
Table of Contents
1.0 Overview P3 2.0 Mission Statement P3 3.0 BIM Uses P3 4.0 Level of Development P4 4.1 MEA table P4-5 4.2 BIM Project Design Milestones P6
5.0 BIM Project team: Roles, Responsibilities, and Contacts
PP6-8
6.0 Design Team Software Requirements
P9
6.1 Construction Team Software Requirements
P10
7.0 Hardware Requirements P10 8.0 Existing Conditions P10 9.0 Project Setup P10
10.1 Design File Naming Format P11 10.2 Construction File Naming Format P11 11.0 Design Model Files Setup P12 11.1 Project Base Point P12 11.2 Design Model Structure P13 11.3 Construction Model Files Setup P14
12.00 Model elements rules: General P14 12.01-12.07 Design Model elements rules PP15-19
12.10- 12.15 Construction Model elements rules PP20-24 13.0 Project Phases P25 14.0 Model Ownership of Elements P26
15.0-15.1 Files Exchange P27 15.2 Conversion Revit files to AutoCAD P28
16.1-16.2 Project Revisions P28 17.0-17.2 Project Coordination PP29-30
18.0 QR tags and Metadata PP31 Appendix A Sample of AIA E202 Model Element Table PP32-33
Appendix B Model Elements Authoring Table Appendix C Box.net Tutorial
The plan is subject to revisions and updates as necessary to accommodate team’s needs and
project developments.
1.0 Overview:
3
The intent of this BIM Execution Plan is to define a process of using building information modeling
(BIM) for NTM Addition and related work, including Parking structure, Cogen Plant, and generators.
The Plan defines scope of BIM work and delineates
roles and responsibilities,
project setup and workflow
authoring
models creation and ownership
project phases
file exchange protocol
framework of team collaboration
review and coordination process
software applications
Refer to Project Contract for specific information regarding project content, delivery methods, and
scope of work.
2.0 Mission Statement
The objective of using BIM is to
Provide smooth, model‐based, coordinated workflow
Improve team collaboration
Ensure quality in the design and construction of the project
Minimize amount of errors, and subsequently, RFIs and construction costs
Maximize project efficiency before and during the construction
Create a record model for after‐construction use (facility management, etc.)
3.0 BIM Use
BIM on this project is to be used for:
1. Design Authoring (New Conditions Modeling) Design Team
2. Existing and Demolition Conditions Modeling Design Team
3. Design Review Design Team
4. 3D coordination Design Team / Construction Team
5. Shop drawings Construction Team
6. Record Model Construction Team
7. Facility Management Construction Team
4
4.0 Level of development
This project to be developed for the following levels (per AIA Document E202–2008, Building
Information Modeling Protocol Exhibit) (see Appendix A for illustration).
BUILDING LOD
Shell of existing building LOD 100
New building addition LOD 300
Existing lobby LOD 300
New Cogen Plant LOD 200
New generators enclosures LOD 200
All work that require LOD 400 and LOD 500 to be performed by GC team.
Should GC requests the Design Team to perform any services to LOD 400/LOD 500, the project scope
should be reassessed accordingly.
4.1 Model Element Authoring Table
The following table defines the minimum level of detail (LOD) expected for specific types of building
elements. The table also outlines the progression of element detail through each phase of the design
process / record modeling.
This table is for a general illustration of the LOD/Model Elements Ownership. Refer to Project
Contract for specific information regarding project content, delivery methods, and scope of work.
Refer to Appendix “B” for an excel spreadsheet of this table for review and comments.
See the XLS file for Level of Detail standards
5
4.2 BIM Project Design Milestones
Project Milestone Date
Project BIM Kick‐off Meeting 11/29/2011
C/S SD Set issued for NTM Review 01/12/2012
Final C/S Schematic Design Submittal 02/03/2012
C/S Design Development Review Submittal 04/10/2012
Final C/S Design Development Submittal 05/01/2012
C/S CD Review Submittal 07/03/2012
C/S CD Submittal (Plan Check) 07/26/2012
TI SD Set issued for NTM Review 04/30/2012
Final TI Schematic Design Submittal 05/22/2012
TI Design Development Review Submittal 07/10/2012
Final TI Design Development Submittal 07/31/2012
TI CD Submittal (Plan Check) 09/25/2012
5.0 BIM Project team: Roles, Responsibilities, and Contacts
Creating BIM model is a collaborative effort. Each BIM team has specific responsibilities during the
project life as agreed upon at the beginning of the project. All Design Teams (architecture, structural,
MEP, civil) and Construction Team shall assign an individual to the role of BIM Lead to coordinate
their work with the entire Design/Construction Team.
6
Below is a brief outline of the responsibilities of each team and a list of primary contacts.
TEAM Team Responsibility Point of contact OWNER
Owner
Project oversight, management and coordination
Participant in the design process As‐built data Quality assurance Scheduling Project Coordination
Contact Name
Title
Address
(o)
(f)
(m)
DESIGN TEAM
Architect
Architectural design Project coordination Model exchange oversight and coordination
Quality control Architectural Design Record Model
Contact Name
Title
Address
(o)
(f)
(m)
Civil
Civil design Coordination and review
Contact Name
Title
Address
(o)
(f)
(m)
Structural
Structural design, Project coordination and review Structural Design Record Model
Contact Name
Title
Address
(o)
(f)
(m)
Electrical
Electrical design Project coordination and review Electrical Design Record Model
Contact Name
Title
Address
(o)
(f)
(m)
Mechanical
Mechanical design
Project coordination and review Mechanical Design Record Model
Contact Name
Title
Address
(o)
(f)
(m)
7
GENERAL CONTRACTOR
Contractor
Project coordination and review Clash detection As‐built Record model
Contact Name
Title
Address
(o)
(f)
(m)
Sub‐Contractor
and/or Fabricator
(as appropriate)
TBD
Off‐site fabrication and shop drawing design
8
6.0 Design Team BIM Software Requirements
Authoring Software
The Design Team is required to use parametric BIM Authoring software for this project. All
architects, engineers, and specialty consultants are required to use the following design
authoring software in its current 2012 version:
• Autodesk® Revit® Architecture
• Autodesk® Revit® MEP
• Autodesk® Revit® Structure
• Autodesk® Civil 3D
Autodesk® Revit® 2012 verticals will be used throughout the life of the project.
Coordination Software
All final internal and external model coordination and conflict detection are required to use the
following software in its native file format in its current 2012 version:
Autodesk® Navisworks® Manage
All project revisions between AE teams should be documented using the following software in
its native file format in its current 2012 version:
Autodesk Design Review 2012
All AE teams should be able to use the following software in its native file format in its current
version for communication with Owner:
Bluebeam PDF
9
6.1 Construction Team BIM Software Requirements
1. Contractor uses Autodesk® Revit® Architecture to author logistics models and to manage
model deliverables from the Design Team.
2. Autodesk® Navisworks® Manage will be used to compile the system models and execute
a comprehensive clash detection study.
3. Sub‐contractors will author their three‐dimensional shop drawings and as‐built models in
a platform compatible with Autodesk® Navisworks® Manage.
4. Autodesk® Revit® 2012 verticals will be used throughout the life of the project.
7.0 Hardware Requirements
Design and Construction Team members shall utilize computer hardware that is sufficient to
efficiently handle single model files of up to 500 MB and aggregate models of up to 1.5 GB.
8.0 Existing Conditions
1. Modeling of the existing conditions is to be performed by the Design Team based on
Owners provided as‐built information.
2. Before project starts, all Design Teams to perform a field survey of the site and to validate
and document the accuracy of the as‐built information
3. All Design Teams to exchange the field survey data affecting each other design.
4. MP and Electrical Design Teams to verify the extent of the demolition work and to update
Architects with necessary changes.
9.0 Project Setup
1. Architect to provide a cartoon set of the project.
2. Project documents to be prepared on 30x42 papersize
3. Architect to provide a Title Block for the project.
4. Architect to provide a key plan
5. Architect to illustrate a typical way of setting up a floor plan views (overall and partial).
6. Grids and levels are to be placed on the workset “Shared Levels and Grids”.
7. Architect to provide architectural sheet index (for reference).
10
10.1 Design File Naming Format
Files for exchange/final models should be formatted as follows:
NTM‐Architectural
NTM ‐Architectural‐TI
NTM ‐Structural
NTM ‐Mechanical
NTM ‐Plumbing
NTM ‐Electrical
10.2 Construction File Naming Format
1. The file naming convention enforced Contractor will consist of the following syntax:
a) NTM‐DDDD_LvX.XXX where DDDD represents to the project
discipline, LvX stands for level, and XXX is the file extension.
b) For example, the plumber would name their files
NTM‐Plumbing_Undg.rvt, NTM‐Plumbing_Lv1.rvt and NTM‐
Plumbing_Lv2.rvt etc.
c) The naming convention for construction models should not differ from
the design convention with the exception of the level identifier.
2. It is imperative once the file naming structure is in place that it does not change and that we
have full compliance to this standard by all parties involved. Variance from this standard
will not be tolerated.
3. If a file is modified or updated, it is to be saved as the exact same file name as the previous
version and uploaded to the appropriate directory. Archived versions will be saved.
11
11.0 Design Model Files Setup
1. All design models to be central files.
2. Each discipline to acquire the shared coordinates, grid lines, levels, and project north from
the Architectural model. Refer to 11.1 for Project Base Point and True North.
3. Preliminary models with acquired shared coordinates to be sent to the Architect team for
verification.
4. Verified models only to be used for design.
5. The final model will be the SITE file.
6. During the project, files of different disciplines could be interlinked as necessary as overlays.
7. Shared Design Models are to be cleaned up per #15.0 of this plan.
8. At the end of the project, separate model from each discipline are to be directly tied to the
SITE, without any additional levels of Revit or CAD links.
9. No DWG files to be linked to exchanged or finally submitted Revit files.
11.1 Project Base Point Coordinates and Angle to True North
12
11.2 Design Model Structure
13
11.3 Construction Model Files Setup/Coordination with Design Models.
1. The project grid lines established in the Architectural model will serve as the origin for all
subsequent models. Contractor will create a Revit family of 3D grids and labels and provide
the .dwg export to each participant for reference.
2. The intersection of grid lines E5 and EB at 0’0” will serve as our 0,0,0 reference throughout
the project.
3. The coordination will take place level by level and thusly the model files will be cropped or
represent a single level. The following table represents the range of each level:
Level Base constraint Top Constraint Total Height
Underground ‐15ʹ0ʺ 0’0” 15ʹ0ʺ
Level 1 0’0” 14’0” 14’0”
Level 2 14’0” 28’0” 14’0”
Level 3 28’0” 42’0” 14’0”
Level 4 42’0” 56’0” 14’0”
14
12.00 Model elements rules: General
1. Completeness of design
All physical building elements within the project are to be modeled (except those clearly
defined and excluded in the MEA Table) and are to represent the full and complete design of
each level and element of the building. For example, if a single level of a building is identical
to another level, each level is to be distinctly and completely represented in the Design and
Construction models. Same applies to the identical partial floor layouts.
2. Model property data
Both the Design and Construction Models are to accurately represent the geometric properties
of the building elements and/or systems in the model.
3. Model precision:
Project units should be rounded to the nearest 1/256”.
12.01 Design Model elements rules: General
1. Modeled elements must never be deleted (unless required by design changes).
2. Roof to be profiled by Architect and modeled by Structural Engineer
15
12.02 Design Model elements rules: Structural
1. Framing
a) Columns will be accurately located and sized.
b) Beams and girders will be accurately located and sized.
c) Foundations will be accurately located and sized.
d) Concrete walls will be accurately located and sized.
2. Existing
a) Existing beams and columns are places based on the best of the Design Team knowledge
given the as‐built drawings.
12.03 Design Model elements rules: Architectural
1. Rooms
a) Rooms are to be accurately bounded, completely enclosed, and not overlapping with other
rooms.
b) Rooms are to be used for MEP spaces
c) Rooms are to contain property data with the correct name and number.
d) Rooms will contain property data assigning it to the correct space, department, area, and
level.
e) Rooms are to be continuous spaces with the height of the space corresponding to the
ceiling height.
2. Closure and Adjacency
a) Rooms, spaces, departments etc. shall be properly enclosed using floors, walls, and ceilings
that are touching, but not overlapped.
b) Adjacent model elements shall be touching and not overlapping.
3. Walls
a) Existing wall are to be generic
b) New walls are to be of the correct wall types.
c) Walls shall be modeled to the correct height based on wall type.
4. Doors
a) Doors are to be associated with the correct level.
b) Doors are to contain the correct door type as property data.
16
12.04 Design Model elements rules: Mechanical
1. HVAC Equipment
AHUs, Fans, VAV boxes, and other major equipment within the building NTM‐Add
boundaries are to be modeled.
2. HVAC Distribution
Air distribution ducts for supply, return, ventilation and exhaust ducts, fire smoke
dampers, registers, diffusers, grilles and louvers are to be modeled to outside face
dimension. Duct hangers and supports and seismic bracing shall be modeled by the
mechanical contractor. Controls systems will not be part of the Revit model.
3. Mechanical Piping
All piping 3/4ʺ diameter and greater within building footprint and within five feet from
building shall be modeled to outside diameter of pipe or pipe insulation, whichever is
greater.
4. Equipment Clearances
Clearances shall be modeled for use in clash detection process and maintenance access
requirements.
17
12.05 Design Model elements rules: Plumbing
1. Fixtures
Piping of plumbing fixtures, sinks, toilets, tubs, shall be modeled in the pluming model
unless otherwise specified in the BIM execution plan. Plumbing fixtures will be
modeled in the Architectural model.
2. Equipment
Carriers, floor and roof drains, leaders, sumps, booster pumps, grease interceptors,
sediment separators and other major equipment shall be modeled.
3. Piping
Plumbing piping within building footprint and within five feet from building,
including hot and cold water piping, sewer piping, storm drain piping, gas piping,
compressed air piping, mains and branch valves and cleanouts shall be modeled.
Piping shall be modeled to outside diameter of pipe or pipe insulation, whichever is
greater. Pipe hangers, pipe supports, seismic bracing, fixture isolation and angle stop
valves will not be part of the design model, they shall be added detailing and
development of the contractor’s model.
4. Equipment Clearances
Clearances and access zones shall be modeled for use in clash detection process and
maintenance access requirements
12.06 Design Model elements rules: Fire Protection
Fire protection components inside building: Standpipes, main laterals, lateral runouts
and pipe routing for head connections, vertical standpipe drain piping, standpipe drain
assembly, hose connections, inspector test assemblies and zone valve feed assemblies.
Sprinkler head locations/head drops, pipe supports and seismic bracing, clean agent
fire protection systems, drains, sensors, heat and smoke detectors, notification devices,
control panels and related equipment shall be added detailing and development of the
contractor’s model.
18
12.07 Design Model elements rules: Electrical
1. Power
Transformers, emergency generators, main and distribution panels, switchgear,
receptacles, switches and junction boxes shall be modeled. Electrical feeders and
conduits 2” and larger shall be modeled, including underground runs.
2. Lighting
Permanently mounted light fixtures, lighting controls, switches and junction boxes shall
be modeled unless otherwise specified in the BIM execution plan.
3. Communications
All existing and new communications service controls, audio equipment, speakers,
phone and data ports and connections, both above ground and underground shall be
modeled. Cable tray routing shall also be modeled. Communications conduits 2” and
larger shall be modeled.
4. Security
All security devices, keypads, cameras and motion sensors shall be modeled.
5. Equipment Clearances
Clearances and access zones shall be modeled for use in clash detection process and
maintenance access requirements.
19
12.10 Construction Model elements rules: Architectural
1. Walls and Curtain Walls
a) Interior and exterior walls shall be modeled to exact height, length, and width.
b) Curtain walls systems are to be modeled according to their true profile including window
placement and mullion placement.
2. Doors, Windows and Louvers:
Doors, windows and louvers shall be modeled to represent actual size and location, both
interior and exterior.
3. Roof
The model shall include the roof with overall thickness including insulation, drainage
systems, major penetrations, access ladders and specialties.
4. Ceilings
The Ceiling system is to include correct act placements when applicable. Soffits, openings,
and slopes are also to be modeled.
5. Vertical Circulation
Elevators, stairs, handrails and guardrails are to be modeled with proper placement, width,
length, and height.
6. Specialty Equipment
All specialty equipment including but not limited to projectors and screens are to be
modeled in the proper and according to equipment specifications. Other fixtures including
plumbing fixtures and electrical fixtures shall be modeled according to assignments in the
BIM execution plan.
20
12.11 Construction Model elements rules: Structural
1. Foundations
Spread Foundations, Caisson Foundations, Pile Foundations, Mat Foundations, Load‐
bearing Wall foundations shall all be modeled according to their length, width, and
height.
2. Framing
Steel Columns, Steel Floor C‐Joists, Open Web Joists, Joist Girders, Steel Beams, Precast
Concrete Elements, Cast‐In‐Place Concrete Elements, Kickers, gusset plates are all to be
modeled to meet the intending design specifications.
3. Floors
All flooring is to be modeled to the proper depth and is to include any holes or
openings.
4. Wall Types
Load Bearing Walls (Masonry, Concrete, Cold‐Formed Steel, Wood, other) are to be
modeled with proper placement, proper openings, and with intended height, length,
and width specifications.
5. Miscellaneous Steel
Angles for openings, deck bearing, etc., channels for mechanical units, and lintels are to
be modeled.
21
12.12 Construction Model elements rules: Mechanical
5. HVAC Equipment
AHU, Fans, VAV boxes, compressors, chillers, cooling towers, air handlers, boilers,
hoods and other major equipment are to be modeled.
6. HVAC Distribution
Air distribution ducts for supply, return, ventilation and exhaust ducts, duct hangers,
seismic bracing, fire smoke dampers, control systems, registers, diffusers, grilles and
louvers are to be modeled to outside face dimension.
7. Mechanical Piping
All piping 3/4ʺ diameter and greater shall be modeled to outside diameter of pipe or
pipe insulation, whichever is greater.
8. Equipment Clearances
Clearances shall be modeled for use in clash detection process and maintenance access
requirements.
22
12.13 Construction Model elements rules: Electrical
1. Power
Transformers, emergency generators, main and distribution panels, switchgear,
receptacles, switches and junction boxes shall be modeled. Electrical feeders and
conduits larger than 3/4ʺ shall be modeled, including underground runs.
2. Lighting
Permanently mounted light fixtures, lighting controls, switches and junction boxes shall
be modeled unless otherwise specified in the BIM execution plan.
3. Communications
All existing and new communications service controls, audio equipment, speakers,
phone and data ports and connections, both above ground and underground shall be
modeled. Cable tray routing with hanger supports and seismic bracing shall also be
modeled. Communications conduit 3/4ʺ and greater shall be modeled.
4. Security
All security devices, keypads, cameras and motion sensors shall be modeled.
5. Equipment Clearances
Clearances and access zones shall be modeled for use in clash detection process and
maintenance access requirements.
23
12.14 Construction Model elements rules: Plumbing
5. Fixtures
All plumbing fixtures, sinks, toilets, tubs, shall be modeled in the pluming model
unless otherwise specified in the BIM execution plan.
6. Equipment
Carriers, floor and roof drains, leaders, sumps, booster pumps, grease interceptors,
sediment separators and other major equipment shall be modeled.
7. Piping
All piping to five feet outside building footprint, including hot and cold water piping,
sewer piping, storm drain piping, gas piping, pipe hangers, seismic bracing, valves and
cleanouts shall be modeled. Piping shall be modeled to outside diameter of pipe or pipe
insulation, whichever is greater.
8. Equipment Clearances
Clearances and access zones shall be modeled for use in clash detection process and
maintenance access requirements
12.15 Construction Model elements rules: Fire Protection
All fire protection components including main lines, branch piping, sprinkler heads,
valves, drains, pumps, tanks, sensors, heat and smoke detectors, notification devices,
control panels and related equipment shall be modeled.
24
13.0 Project Phases
1. Project will be phased as following:
Existing [Existing and Demo]
New Shell [Existing + New Shell]
New TI [Existing + New Shell + New TI]
2. All disciplines to follow phases as set in the NTM‐Architectural as described below
Create Phases as shown in NTM‐Architectural
Create a separate plan for each phase (as needed per project development)
Link NTM‐Architectural to your model
Select linked NTM‐Architectural > Properties>Edit Type>Phase Mapping
Map Phases as shown below:
25
14.0 Design Model Ownership of Elements
MODEL OWNERSHIP OF ELEMENTS
Modeled Element Discipline Owner Discipline Usage
• Grids Structural A, M, P & E – Copy Monitor
• Columns Structural A, M, P & E – Linked
• Exterior Architectural S, M, P & E – Linked
• Below grade veneer supported foundations Structural A, M, P & E – Linked
• Ramp slabs/stair steps & stair landing slabs Architectural S, M, P & E – Linked
• Landscaping, planters Architectural S, M, P & E – Linked
• Floor slabs on grade w/ recesses Structural A, M, P & E – Linked
• Foundation walls – retaining, stair / ramp
walls, entry foundations Structural A, M, P & E – Linked
• Roof deck (floor) Structural A, M, P & E – Linked
• Roof finish (floor) Architectural M, P & E – Linked
• RTU curbs Structural M, P & E – Linked
• Mechanical curbs Mechanical A, P & E – Linked
• Plumbing Fixtures Plumbing A, S, M & E – Linked
• Mechanical Fixtures Mechanical A, P & E – Linked
• Light Fixtures Electrical A ‐ Linked
26
15.0 Design Team Files Exchange
1. Models to be uploaded to Architect Share biweekly, end of Monday starting 12/05/2011.
2. Links to the model uploads to be sent to Architect and then shared with the team.
3. Before sending your file for exchange, do the following:
a) Open Revit
b) Select the file using Revit dialog box check both the Detach from Central and Audit
boxes.
c) Be sure to select Detach and Preserve Worksets when the dialog box appears.
d) Save the project into the proper subfolder in the _OUTgoing folder.
e) Remove all links (Revit and cad).
f) Purge all unused families.
g) Synchronize with central to remove your ownership from the worksets.
i. Be sure to select Synchronize and Modify Settings.
ii. Check all boxes that are not shaded including the compact file box
Make sure they are named as set forth above (10.0).
15.1 Design/Construction Team Data transfer
1. Contractor has established a service through Box, a web based collaboration platform, to
host and share files as needed on the project.
2. Refer to Appendix “C” for a tutorial for the use and function of the Box site.
3. Once a file is uploaded, notifications are sent to collaborators and an archived copy is
saved of each revision posted.
4. Collaborators will post updates as they are completed to their respective directory from
which Contractor will create the composite model.
5. Other project documents and data files can be posted and transmitted via the Box platform.
Submittals and RFI’s will be posted and replied to via Box.
27
15.2 Conversion Revit files to AutoCAD
With every scheduled submittal Architect should provide a set of architectural CAD plans
translated per NTM Layering Standards for use with NTM Facility Management program.
16.1 Design Team Project Revisions and Change Management
1. At the time of files exchange, all revised sheets/views to be printed to DWF files.
2. All project revisions for each discipline should be documented with revision clouds using
Design Review.
3. Architect to provide a sample revision plan (DWF file)
4. All A/E teams are required to archive project progress sets in PDF and native formats.
5. During construction, the Design Team shall maintain and update their respective Design
Models with all significant field changes made through RFIs, Change Orders, Bulletins, and
similar documents, including Architectural, MEP and Structural changes and coordinate
those changes with General Contractor and subcontractors. Should the 3D geometry of the
model changes, it likely is to be defined as significant. Owner will make final
determination on whether a change is significant or not. Design Team will be providing
these model updating services to Owner at no additional cost, with exception to changes to
the scope made by Owner.
16.2 Construction Team Project Revisions and Change Management
1. Sub‐contractors are required to maintain an as‐built representation of their systems.
Updates are to be continually posted as the models adapt and are modified to reflect actual
installed conditions.
2. Design changes which require a delta and a updated contract drawing will originate in
their respective model source. Those changes will be posted in conjunction to the printed
directive to the Box site where in turn they will be implemented in each affected system
model by the sub‐contractors.
3. At the conclusion of the project, each collaborating discipline will be required to submit a
model file representing their scope of work as specified in the Project’s LOD document and
defined by the AIA E202’s LOD description.
28
17.0 General Project Coordination Requirements
3D coordination is of critical importance to assure quality project document delivery.
Models submitted for clash detection shall be “clean” of all extraneous 2D references and/or 3D
elements.
Design Team is to produce a design in which all M/E/P/FP systems fit within the intended
spaces provided, including required clearances. To facilitate this, the Design Team is to have a
planned 3D spatial analysis and clash resolution process.
This spatial analysis and clash resolution process to include:
1. Regularly scheduled data exchange
2. Navisworks clash detection analysis
3. Area by area / discipline by discipline clash review
4. a clash resolution report /coordination log to include:
Priority (urgent, high, normal, low)
Clash ID/number
Clash name
Clash description
Clash tolerance (if needed)
Location (level/grid lines/distance)
Date found
Responsible party
Resolution
Date resolved
29
17.1 Design Team Project Coordination Requirements:
1. MEP and Structural Teams are required to perform internal coordination between disciplines
at least once a month using their BIM Authoring software capabilities or Autodesk®
Navisworks® Manage.
2. All AE Teams are required to perform internal coordination between disciplines at the end if
each phase using their BIM Authoring software capabilities or Autodesk® Navisworks®
Manage.
17.2 Construction Team Project Coordination Requirements:
1. Contractor will self‐perform the clash detection studies both on design models and as a process
to facilitate construction coordination. The process will engage the required sub‐contractors
and be conducted in an integrated, congruent engineering format. The use of the BIM trailer
on site will facilitate such sessions.
2. Clash reports will be posted prior to the coordination meetings in order to give the participants
time to formulate solutions rather than reactions to previously unknown issues. In order to
facilitate a productive session, sub‐contractors must post progress models within the allotted
time frame.
3. The design team is not required to actively participate in the construction coordination process,
but should be available as needed for confirmation and clarification of discovered issues.
30
18.0 QR Tags and Metadata
1. Contractor has developed and tested Two‐Level QR tags system to use with NTM Facility
Management Program.
2. QR tags will store project Metadata.
3. On the First Level, QR tags contain rooms’ Metadata.
4. On the Second Level, QR tags contain the following Metadata:
Product Data
Warranty Information
Operations and Maintenance Manuals
Maintenance Schedules
Instructional Videos
Progress Photos
Model Files
Shop Drawings
5. Firstly, the Facility Management team access rooms’ metadata. Secondly, they access the data
associated with all the items in the room coded with QR tags.
6. To build the First Level, Contractor needs the room schedule.
7. Architect to provide Contractor with the project room schedule, exported into Excel file.
8. To build the Second Level, Contractor has developed a Procurement Log to serve as the
minimum baseline for listing the items which require a Meta Data rich QR Tag. The
Procurement Log tracks the submittal requirements as required in the project specifications.
9. For QR tags to function, it is imperative that the Project working file structure migrates
seamlessly to Ownerʹs permanent file structure.
10. Owner to provide Contractor with detailed files/folder structure, description and setup
protocol, so that Contractor team can emulate that environment on their side as they procure
the files and build the database structure.
11. Contractor to appoint a BIM Administrator on site to manage QR tags and Metadata and
compile the tags for distribution to the subs and client.
31
A P P E N D I X “ A ” L E V E L O F D E V E L O P M E N T
There are 5 basic levels of development which do not reflect specific modeling guidelines for
any particular software, rather a generic definition of model content:
LOD 100 ‐ Essentially the equivalent of conceptual
design, the model would consist of overall building
massing.
LOD 200 ‐ Similar to schematic design or design
development, the model would consist of ʺgeneralized
systems or assemblies with approximate quantities, size,
shape, location and orientation.ʺ
LOD 300 ‐ Model elements are suitable for the generation
of traditional construction documents and shop
drawings.
Image
courtesy of Mortenson Construction
LOD 400 ‐ This level of development is considered to be
suitable for fabrication and assembly. The MEA for this
LOD is most likely to be the trade contractor or fabricator
as it is usually outside the scope of the architectʹs or
engineerʹs services.
LOD 500 ‐ The final level of development represents the
project as it has been constructed ‐ the as‐built conditions.
The model is suitable for maintenance and operations of
the facility.