Building Information Modeling for Masonry Phase II Project Project 2… · BIM-M Phase II Project: BIM-M Benchmark Framework Report 15 June 2014 Page 2 1. Executive Summary This report

Building Information Modeling for Masonry

Phase II Project

Project 2, Masonry BIM Benchmark

Pankow Foundation Grant RGA#01-14

Report 1

Development of Systems Models of Stakeholders and

Exchanges Involved in Masonry Construction Projects

delivered to

Charles Pankow Foundation

in support of the

Building Information Modeling for Masonry Initiative (BIM-M)

Georgia Institute of Technology

School of Architecture

Digital Building Laboratory

T. Russell Gentry, PI

Charles Eastman, co-PI

John Haymaker, co-PI

Bryan Lee, Graduate Research Assistant

David Biggs, BIM-M Coordinator

Project Manager

15 June 2014

BIM-M Phase II Project: BIM-M Benchmark Framework Report 15 June 2014 Page 2

1. Executive Summary

This report represents the second deliverable from the Phase II Building Information Modeling for Masonry

(BIM-M) project – and the first for the BIM-M Benchmark project. It focuses primarily on design, analysis, and

construction workflows in which stakeholders work together to complete a masonry project. We have

developed a framework for completing masonry case studies and use the Engineered Biosystems Building

(EBB) currently under construction on Georgia Institute of Technology campus as the first case study. The goal

of this document is to identify how stakeholders are executing the various processes, workflows, and

exchanges related to masonry – with or without BIM – throughout all project phases – and to formalize this

analytical framework for future case studies. The documentation will act as a reference and model for masonry

design, material procurement, construction process models for activities that take place both on and off the

construction site. Furthermore, this initial study will provide a blueprint for a course to be taught at Georgia

Tech in this coming fall semester. Graduate students in the Schools of Architecture, Building Construction and

Civil Engineering will be conducting additional case studies to the one currently being done on the Engineered

Biosystems Building. An appendix to this document contains the draft syllabus for the class.

2. Background

In January of 2014, the Digital Building Laboratory (DBL) at the Georgia Institute of Technology began the

process of creating a benchmark for the implementation of BIM in the masonry industry. This benchmark

would include models and documentation of virtually all aspects and their details of a masonry construction

project, including all stakeholders, document and material exchanges, work tasks, materials and supplies, etc.

Generally, in the masonry industry today, BIM has not received widespread acknowledgement and acceptance.

Many of the processes involved in the masonry industry are done manually, without any reference or

technological assistance. To a degree, masonry lacks the standardization of work and workflows and

classification of materials and systems which is integral for an industry to succeed and survive in modern

times. This issue pertains to all elements relating to masonry, including brick, CMU, and cast-stone.

Similar to the implementation of BIM for other building systems, BIM for masonry must first be addressed

through the observation, documentation, and development of current industry practices, which is precisely

what this Masonry BIM Benchmark project and the associated EBB case study aims to do. The EBB is an

ongoing project on the campus of the Georgia Institute of Technology. The new facility will provide a

collaborative space for interdisciplinary biomedical research. The project delivery method was Construction

Management at Risk, but there has been a push for collaboration and implementation of IPD principles by the

building owner, as part of its new initiative for BIM Implementation on all new construction projects on

campus. The structural style for the EBB is a typical frame of cast-in-place reinforced concrete columns and

beams. The masonry subcontractor’s scope on this project includes brick on a façade, CMU in the basement,

and cast-stone in certain areas of the facade.

The process models are being captured in the System Modeling Language or SysML. SysML is an emerging tool

for modeling of business processes, and has the advantage of earlier tools, like BPMN, in that it can represent

both processes, requirements and data. The software tool being used for this study is MagicDraw and its

SysML plugin. SysML allows for the modeling of various diagrams showing structure and process.

The BIM-M project and this case study are organized into five phases (Schematic Design, Design Development,

Construction Documents, Contractor Coordination, Subcontractor Installation), three masonry types (Brick and

CMU, Structural Masonry, Complex Masonry), and three states (Current No-BIM, Current BIM, Future BIM).


The EBB case study focuses on CMU and Brick and Current No-BIM/Current BIM and spans all five project

phases (see Figure 1).

Figure 1. EBB case study criteria.

Although the EBB case study focuses on the current level of BIM implementation, a goal of this project and the

course offered this fall is to explore the future state of BIM in the masonry industry. Many construction

processes have been effectively enhanced by BIM and other management tools. These tools have been

connected to CAD and other modeling software and building industry databases. By understanding and

modeling the masonry workflows in SysML diagrams, we will lay the groundwork for developing BIM tools

specifically for the masonry industry. Furthermore, integrating these diagrams with the Masonry Unit Database

will further enhance BIM implementation and greatly improve efficiency of the industry.

3. Project Stakeholder Map and Analysis

Part of this case study process is to understand the organization of project stakeholders. Figure 2 shows the

organizational structure using a SysML “block definition diagram,” which uses blocks to represent different

project stakeholders and arrows to represent their relationships (see Figure 2). As part of the case-study

process, the Georgia Tech team has been meeting with project team members and these meetings will

continue throughout the summer. Georgia Tech researchers have also been on-site at the EBB, observing

masonry installations.

The core of this stakeholder analysis can be captured in a few simple questions, which can be thought of as

identifying the “Current No-BIM” and “Current BIM” workflows:

1. What information do you need to do your work?

2. Who do you get the information from and in what form?

3. Do you receive any information in “machine readable” form such as spreadsheets, CAD drawings or

BIM models? If so, describe them.

4. How do you analyze or process the information you receive? Do you have to enter it into a computer

to do so?

5. If you receive machine readable information, can you query or convert it for your analysis tasks?

6. How do you format your information for downstream use by your clients or other stakeholders on the

team?


7. Do your downstream users ask for models? If so, what type? Do you know if they use the models?

8. Does anyone on the design and construction teams use digital tools to simplify their work without

being required by contract? If so, who, and what is it they do?


Figure 2. Organization of project stakeholders.


4. Project Masonry Scope

In addition to the stakeholders map and analysis, SysML can be used to create a map of the materials to

evaluate the full scope of a masonry project. The items of this material map can be applied to other process

maps and diagrams to accurately document all of the elements of a masonry project workflow. For the EBB,

the scope includes CMU, brick, and cast-stone (see Figure 3). The types of CMU blocks applied in the basement

are 4-inch, 6-inch, 8-inch single bullnose, 8-inch double bullnose, 8-inch open bottom bond, 8-inch solid

bottom bond beam. The brick façade consists of glazed masonry and red clay brick. The glazed brick colors are

navy and gold, and they are provided through Georgia Masonry Supply. The red clay brick currently includes

three mixed types, Tucker, Mobile, and Natchez, which are all products of the Cherokee Brick & Tile Company.

Cast-stone will also be used in certain areas in the façade. This diagram not only enhances the Benchmark

project but will also prove useful to the Masonry Unit Database project.

Figure 3. Project masonry scope map

5. Project Phase Process Models

This case study on the EBB has been divided into five main phases for modeling purposes, as described in

previous reports. In SysML, the phases are modeled using activity diagrams. The rounded blocks represent

specific actions and the arrows represent the order in which those actions occur. The non-rounded blocks

indicate materials, documents, and any other items that are exchanged among stakeholders and actions. Swim

lanes, similar to the ones used in Business Process Modeling Notation (BPMN), denote which stakeholders

perform certain actions. Since the EBB project and the process of receiving stakeholder input is still ongoing,

these diagrams are not yet final and will be updated throughout the summer.

Schematic Design Phase

In the schematic design phase, the owner – which is Georgia Tech and its related organizations, or simply

Georgia Tech – identified the project and its requirements. The design process primarily involved Georgia Tech


and the architect, Cooper Carry and Lake Flato. In this phase, the overall form of the EBB was established, and

the building was mostly modeled in SketchUp. One important factor in the schematic design process was the

selection of the architectural materials, specifically the masonry. In this project, five different small-scale

mockups were used to develop the brick selection and pattern used on the building.

Figure 4. SysML activity diagram of schematic design phase.

Figure 4 shows the Schematic Design phase modeled with two main stakeholders. The full, black circle

represents the start node, or where the activity begins. The black and white-outlined circle represents the end

node of the entire activity. The upside-down pitchfork symbol on the “Architectural Material Selection” action

denotes a call activity node, which is used to link to another diagram to further specify the marked action (see

Figure 5).

Architectural Material Selection

In this stage, Cooper Carry / Lake Flato coordinated with the masonry suppliers, primarily Georgia Masonry

Supply and Cherokee Brick, to select the desired type, color, and number of bricks to be used on the façade of

the EBB. This process involved multiple models which were created throughout the design phase. At first, dry

stacking was done in the office and on site to properly identify which color patterns would be used. Layer,

mortared mockup created, with Jollay Masonry providing the mockups at no charge to the architecture team.

Figure 5. SysML activity diagram of architectural material selection.


Figure 5 shows an expanded view of the “Architectural Material Selection” action initiated in Figure 4. The

crossed circle after the “Create Sample Board” action represents the end of that specific chain of actions for

the “Georgia Masonry Supply” swim lane. The large block labeled “Check conformity with design intent”

represents a larger action that can be divided into more detailed, individual actions.

Design Development Phase

In the design development phase, several factors of the initial design were tested, including energy modeling,

structural modeling, and cost estimation. In this phase, the owner and architect worked closely together to

fine-tune the design and models, while receiving input from various consultants. The models were developed

beyond the aesthetic representations and constructed using BIM software, specifically Autodesk Revit.

Figure 6. SysML activity diagram of design development phase.

As shown in Figure 6, the design development phase includes five swim lanes for the five main stakeholders

involved in this process. Several of the action blocks have item blocks, labeled “«centralBuffer»,” below them.

These represent the specific documents or other phase deliverables that are produced from those actions.

Construction Documents Phase

In the construction documents phase, Cooper Carry / Lake Flato produced all of the architectural construction

drawings and worked in conjunction with Jollay Masonry to produce the final masonry specifications. At this

stage, Jollay Masonry provided a critique and markup of the masonry details in the EBB – even before they

were formally selected as the mason contractor for the project. The schedules were finalized, and the models

and drawings were coordinated to correct any issues before construction. One unique element of the EBB was

the inclusion of a BIM Execution Plan, which was authored by Georgia Tech. Appendix 2 provides a copy of the

Georgia Tech BIM Execution Plan template. This plan required that all current and future projects to use BIM

and adopt the ideals of Integrated Project Delivery. This means that despite being a Construction Management

at Risk project, there was much coordination and collaboration early on in the project.


Figure 7. SysML activity diagram of construction documents phase.

Although there was collaboration in this process, most of the construction documents were produced by

Cooper Carry / Lake Flato, therefore, this phase is represented using an activity diagram without swim lanes.

Also, more stakeholder input is needed for these and future phases. As seen in Figure 7, the “Define Wall

Openings” action block contains an upside-down pitchfork symbol, which is expanded in Figure 8.

Define Wall Openings

Figure 8 shows the expansion of the “Define Wall Openings” action. In this process, Cooper Carry / Lake Flato

gathered all of the architectural and masonry specifications to produce detailed drawings of the various wall

openings and special conditions.

Figure 8. SysML activity diagram of define wall openings.

In Figure 8, the vertical, black bars represent moments with multiple inputs and/or outputs for one or more

actions. The diamond marks a decision making process which results in two different paths or outcomes.


Contractor Coordination Phase

The contractor coordination phase marks the beginning of the construction phase (Figure 9). The EBB is

currently in this phase. Due to the lack of complete input from stakeholders, the analysis and documentation

of this phase is not yet complete – and these diagrams should be considered a work in progress. In this phase,

the General Contractor / Construction Manager, McCarthy, manages the construction of the entire facility

while overseeing the operations of the various subcontractors onsite, including Jollay Masonry.

Figure 9. SysML activity diagram of contractor coordination phase.

Subcontractor Installation Phase

In the subcontractor installation phase, Jollay Masonry coordinates with McCarthy to install the entire

masonry scope of the EBB, which includes brick, CMU, and cast-stone. Although BIM is rarely used in

traditional masonry jobs, Jollay Masonry has made an effort to incorporate new technologies into its

workflows. The two main types of installation covered in the following diagrams are the brick façade and

basement CMU.

Brick Façade

The brick façade consists of three types of red clay brick and two types of glazed masonry, navy and blue. The

project manager, Matt Jollay, handles most of the offsite coordination, while making the occasional site visit to


consult with other project managers and contractors. The superintendent, Danny League, oversees all of the

work tasks onsite, including managing the masons and crew.

Figure 10. SysML activity diagram of subcontractor installation on brick facade.

Figure 11. SysML activity diagram of review construction documents.

Vivarium Level

In the basement of the EBB, there is a vivarium, which will house many types of animals for research. This

facility requires the use of CMU throughout the entire floor. This process involves a lot of coordinated labor

among the masons and crew, which is managed by the superintendent, Danny League.


Figure 12. SysML activity diagram of subcontractor installation on vivarium level.

Figure 13. SysML activity diagram of error detection and rework.


In Figure 13, a second superintendent from Jollay Masonry, John Anderson, is introduced. In addition to acting

as the superintendent for brickwork on the façade, Mr. Anderson conducts error checking to compare the

construction documents to the actual layout of masonry structures onsite. If there are errors, those blocks and

some walls may need to be demolished and reconstructed. In this case, a CMU wall that was constructed in the

vivarium level was not in the correct location, according to the control lines off which construction was

measured. After rechecking construction drawings and drawn control lines and considering the installation of

other systems, such as MEP, the masonry crews demolished and reconstructed the block wall.

In the case of the EBB, the re-measuring of the building frame and masonry substrate took approximately one

man-month of superintendent labor. The errors identified and coordination required were communicated

through a number of ad-hoc means – but none of this occurred through a BIM or even CAD-enabled process –

and so this is considered “current state no-BIM”. In Figure 14, a selection of the type of coordination required

is provided. Not all of these coordination issues were raised at EBB, but they are the most commonly

encountered by the mason contractor. Most of this information involves the checking of existing building

geometry, and the communication of adjustments required before brick veneer installation can begin. In

future BIM states, much of this communication can and should be made using BIM for masonry tools.

1.Re-align construction joint with center of windows southeast façade.

2. Remove relief angles between three windows – metal panel here not brick.

3. Relief angle drops 0.8 in. – caulk joint will increase to 1.25 in. thick. Resolve?

4. Trim projecting leg of relief angle 0.25 in.

5. Steel stud window framing out – brick will not wrap opening.

6. Steel outriggers for shade not aligned with curtain wall or brick coursing per A1102 D7.

7. Improper waterproofing for below-grade application.

Figure 14. Examples of masonry coordination issues required before start of veneer installation.


6. Fall Curriculum

The framework outlined in this document will be used as a blueprint for the case-study course to be taught at

Georgia Tech. Professor Gentry will lead the course and Professors Haymaker and Eastman will assist. Bryan

Lee, a graduate student in the School of Civil Engineering, will act as the teaching assistant for the course. The

case study that he is completing at the EBB building will form a basis for the additional case studies to be

completed by graduate students in our Schools of Architecture, Building Construction and Civil Engineering.

Appendix 1 to this document provides a draft of the syllabus.

7. Target Buildings for Fall Case Study Research

The Georgia Tech team is looking for owner/designer/contractor/supplier teams willing to provide their

buildings as case-study materials for the additional case studies that will be completed as part of the course

described above.

And so we are looking to identify at least three projects where members of the design and construction team

are willing to travel to Georgia Tech (or connect with us electronically), to talk about their design and

construction process associated with masonry. We will ask that the teams share project documentation

(plans, documents, specs, shop drawings, etc.).

1. Name/Location of the Project

2. Short Description of Masonry Scope

3. Stakeholder List and Contacts (phone/email)

4. Architect

5. Energy Analyst / Green Building Consultant

6. Structural Engineer

7. Mechanical Engineer

8. Mason Contractor

9. General Contractor

10. Masonry Supplier(s)

11. Mechanical Contractor

The general organization of the stakeholders is shown in Figure 2 for the EBB building or in a more generic

form in Figure 15, below.


Figure 15. Stakeholder organization for BIM-M Benchmark projects.

At this time we have identified five potential buildings for the case-study projects. None of the project teams

as described in the diagram above have been fully identified or are fully committed at this time. It is incumbent

on the BIM-M stakeholder community to help Georgia Tech identify the projects and to encourage the

stakeholders in the projects to work with us so that we can fully document the case-studies.

1. Enotah Residence Hall at Young Harris College (Brick/CMU/Plank) Lord Aeck and Sargent Architects, KSI

Structural Engineers, Hardin Construction General Contractors.

2. Brekenridge Place, Ithaca New York, Holt Architects, Ryan Biggs Structural Engineers.

3. Fleming Residence Hall at Emory University, Oxford campus (Brick/CMU/Plank) Cooper Carry

Architects, Brassfield and Gorrie General Contractors.

4. Charles A. Dana Fine Arts Building at Agnes Scott College (Brick load bearing, historic mid-century

modern building). John Portman, Architect. (this would be a “pretend” project focused on BIM

modeling and renovation of historic buildings as no restoration of this building is planned at this time).

5. Kennesaw State University WellStar College of Health & Human Services (Brick/CMU/Concrete Frame),

Cooper Carry Architects.

8. Summary and Comments

The case study work continues but our initial findings reinforce the fact that the implementation of BIM

software for masonry will only succeed if we understand the transactions, queries and analyses that take place

in the masonry industry – and develop software-enabled workflows that facilitate these activities. We found it

surprising that a mason contractor would need to invest an entire month of senior superintendent time to re-

measure a building frame, before the start of masonry installation. This was on a BIM-enabled job where the

general contractor was laser scanning, updating BIM models, etc. Nevertheless, the building model did not

sufficiently match the as-built geometry and the mason contractor felt he had no option but to re-measure the

Architect

MasonrySupplier

MasonContractor

Structural Engineer

DESIGN PHASE

GeneralContractor

MasonContractor

MasonryCrews and

Masons

MechanicalContractor

PrimaryStructuralContractor

MasonrySuppliers

--------------BrickCMU

Cast StoneMortar/Grout

Accessories

AE Team------------Architect

S EM E

CONSTRUCTION PHASE

EnergyAnalyst


building. In addition, the mason superintendent did not have digital tools to help transmit the re-measured

information to the other building stakeholders, in this case the general contractor, the curtain wall installer,

and the concrete subcontractor, the waterproofing contractor and the miscellaneous metals installer and

therefore these communications took were in the form of annotated photographs, hand sketches, memos, etc.

And so the BIM Benchmark project will be critical as it proceeds to capture the detailed workflows of

architects, structural engineers, energy analysts, mason contractors, etc. as they work through their processes

on various types of masonry projects. What we need from the industry is an assessment of these workflows –

as documented in this report -- especially those that involve masonry procurement and installation. The

Georgia Tech team would like to have an initial review of the document by Darrell McMillian, BIM-M Project

Manager for the Mason Contractors Project, and then follow up with the mason contractors that he is working

with, through a webinar and follow-up survey. This can be joint activity between the Benchmark and Mason

Contractor projects.

In addition, we would like to assist industry stakeholders in creating their own workflows – which will

dramatically increase the body of knowledge we have on information workflows. Figure 16 below shows an

internal workflow from Midwest Cast Stone. The exact nature of each element in the workflow is not

important – but what is important is that each of the blue squares represents “information” – an order, a CAD

file, an RFI (request for information), an email, etc. All of these information pieces can be part of a BIM-

enabled process, but we need this level of detail from our stakeholders as we proceed towards the Phase III

BIM-M software specification.


Figure 16. Flow of information and material in a custom cast stone masonry process

(image courtesy Midwest Cast Stone, Kansas City, Kansas.

The case studies that will be produced this fall as part of the BIM-M Benchmark course are important, but

equally important are industry-validation of these workflows, and the generation of additional workflows

which can be shared with our stakeholders.


Appendix 1: Syllabus for Fall BIM-M Benchmark Course

BC 6550: Design and Construction Processes

CEE 8813G: Special Problems in Construction Engineering

ARCH 6215: Contemporary Architecture and Construction Technology

Tuesday

6:00 p.m. – 9:00 p.m.

instructors: Russell Gentry ([email protected] ) with

John Haymaker ([email protected] )

Chuck Eastman ([email protected] )

Bryan Lee ([email protected] )

COURSE DESCRIPTION + OBJECTIVES

Design and Construction Processes is cross-listed in the Schools of Architecture, Building Construction, and

Civil and Environmental Engineering and provides an introduction into design, contract, and performance

documents for successful execution of integrated project delivery systems or IPD. According to the

American Institute of Architects, IPD is a “project delivery approach that integrates people, systems, business

structures and practices into a process that collaboratively harnesses the talents and insights of all

participants to optimize project results, increase value to the owner, reduce waste, and maximize efficiency

through all phases of design, fabrication, and construction.” 1 In many construction projects today, the use

of Building Information Modeling (BIM) and the subsequent sharing of data and models across design and

construction teams is taking place even in projects that are not formally contracted as IPD projects – and the

course will emphasize BIM processes as part of IPD. BIM and IPD are not fully defined or implemented in the

AEC industry today, and the course will focus on identifying existing processes, and developing new

processes for the future.

In the past, this course has focused on a specific type of construction or as a case study so as to provide a

context for the discussion of design and construction processes in an integrated project delivery

environment. Recently, the course has focused on green building processes, and on the design and

construction of the new Caddell Building on the Georgia Tech campus. This year, the course will focus on

the design and construction of buildings using masonry as an architectural and structural material and will

continue with the case-study approach. The focus on masonry gives the class access to the resources and

stakeholders in the Building Information Modeling for Masonry Initiative (BIM-M) 2.

The course is open to graduate students in construction, architecture and civil engineering – and students

from the various disciplines will be expected to champion their stakeholder viewpoints in the classroom

discussions and assignments. In addition, all students are expected to develop skills in process modeling as

part of the class. The lectures will introduce Business Process Modeling Notation (BPMN) and System

Modeling Language (SysML) as techniques for capturing the development and flow of information and

materiel in design and construction activities. These activities will be defined formally in the course but

include the following:

Design Processes

Form-Generation

1 American Institute of Architects, 2007, Integrated Project Delivery, A Guide, Version 1. Retrieved from: http://info.aia.org/siteobjects/files/ipd_guide_2007.pdf 2 http://www.bimformasonry.org/

mailto:[email protected]




http://info.aia.org/siteobjects/files/ipd_guide_2007.pdf

http://www.bimformasonry.org/

Design and Construction Processes Fall 2014 DRAFT updated 1 June 2014 Page 2

Material Selection

Structural Analysis and Design

Energy Analysis

BIM Model Development

Contract Document Production

Construction Processes

QTO and Cost Estimating

Construction Scheduling

BIM Model Validation (e.g. Clash Detection)

Material Procurement and Tracking

Construction Site Installation

COURSE PROCEDURES AND ORGANIZATION

The seminar will meet on Tuesday evening from 6 to 9 p.m. In general, each class period will include a

lecture or case-study presentation, software demonstration or tutorial, and time for group work and update

reports. Professionals from the BIM-M project including architects, structural engineers, general contractors

and mason contractors will present their work representing current practices in the AEC industry. Software

vendors will present tutorials on the use of their software in design and construction operations.

Independent learning, initiative, and project-based work will be critical in this course. Each group will receive

a masonry building (either built or under construction) as the basis for their case study and will be given

access to the design and construction teams responsible for the projects. The teams will have access to

some of the building information in model form, but will be expected to generate and/or analyze some

building models as part of the class. Student teams will work with their professional stakeholder groups to

elucidate workflows in masonry design and construction and develop process models that document these

workflows. The process models will document the AEC industry in its current normative state; in the best

state possible using current software and delivery methods; and in the so-called future state.

Architect

MasonrySupplier

MasonContractor

Structural Engineer

DESIGN PHASE

GeneralContractor

MasonContractor

MasonryCrews and

Masons

MechanicalContractor

PrimaryStructuralContractor

MasonrySuppliers

--------------BrickCMU

Cast StoneMortar/Grout

Accessories

AE Team------------Architect

S EM E

CONSTRUCTION PHASE

EnergyAnalyst


The final grades will be assigned primarily on the development of team-based case studies and the

presentations and reports prepared based on these case studies. Class members must be willing to work on

the same team for the entire semester, and to contribute constructively to the work product of the team.

Individual contributions to the final team product will be assessed by the team members themselves,

through a peer-review process, and by the faculty.

At the beginning of the semester, we will survey students to identify strengths and interests, and will form

cross-functional teams of students. We expect that each team will have and/or develop the following

strengths/capabilities:

1. Architectural design and modeling

2. Structural analysis and design

3. Project scheduling, QTO and cost-estimating

4. BIM model navigation and querying

5. Masonry construction

6. Process and system modeling

We recognize that not every team will have the full skill-set required at the start of the semester, and the

tutorials will be structured to bring the students up to speed. The teaching assistant for the course (Bryan

Lee) has already completed one case study in preparation for the semester, and will act as a resource for all

of the student teams.

COURSE SCHEDULE

The preliminary course schedule is laid-out below. The invited guest lectures are identified in BOLD and are

not confirmed at this time.

Week Date Lecture

1 19 Aug

Syllabus Review

Review of the Design and Construction Processes and Delivery Methods

Introduction to Masonry Construction and the Masonry Industry

2 26 Aug

IPD and Process Modeling Lecture

Team Formation

Intensive BIM tutorials and workshops

3 2 Sep Architecture Lecture: Rick Fredlund, Cooper Carry Architects

Intensive Process Modeling tutorials and workshops

4 9 Sep Structural Engineering Lecture: Jamie Davis, Ryan Biggs Associates

Current Practice Schematic Design and Design Development Lecture

5 16 Sep

Current Practices in Masonry BIM Lecture: Mark Swanson, International Masonry

Institute

Current Practice Schematic Design and Design Development Workshop

6 23 Sep General Contractor Lecture on IPD, BIM and Masonry Construction: T B D

Current Practice Construction Documents Lecture and Demonstration

7 30 Sep

Software Vendors Viewpoint (1/2): IPD, BIM and Masonry Construction:

Michael Gustafson, Autodesk; Tom Cuneio, CADBLOX;

Current Practice Construction Documents Workshop


Week Date Lecture

8 7 Oct

Software Vendors Viewpoint (2/2): IPD, BIM and Masonry Construction:

Bill Pacetti Jr., Tradesmens; Carl Taylor, Tekla

Midterm Review 1: Presenting current state process models and measurements Current

9 14 Oct Fall Semester Break

10 21 Oct

Mason Contractor Lecture on BIM and Masonry Construction: Matt Jollay, Jollay

Masonry

Practice Construction Planning and Installation Lecture

11 28 Oct

Material Supply Lecture, Two Viewpoints: TBD, Gate Precast and TBD, Georgia

Masonry Supply

Continued work on Process Models and BIM Models

12 4 Nov

BIM-enabled Information Flows: Information Delivery Manuals and Model View

Definitions, Chuck Eastman, Georgia Tech Digital Building Lab

Future of IPD and BIM in Masonry Construction Lecture

13 11 Nov Midterm Review 2: Future State BIM Process Presentations

14 18 Nov Project Working Session

15 9 Dec Final: Presentations comparing current and future state processes

Invited Reviewers

David Biggs, BIM-M Coordinator

Dave Sovinski, International Masonry Institute

Bob Thomas, National Concrete Masonry Association

Brian Trimble, Brick Industry of America

FINAL ASSIGNMENT

The final assignment for each group will be the completed case study on the assigned masonry building.

The students will present their case study to the professional team and will complete a written report as well.

The elements of the final report will include the following:

1. Introduction and vision statement for current state, best practices and future state of IPD and BIM in

masonry construction

2. Summary of the masonry materials and systems on the project

3. Matrix and narrative of project stakeholders and responsibilities

4. Narrative and presentation of all building models3 developed or used as part of the project

5. Process models in SysML for five project phases and for three states (current state, best practice

state, future state) – see figure below.

3 Used in this context the term “building model” is an embodiment of the building and may include a traditional BIM model, project schedule, structural analysis, cost estimate, energy model, etc.


MasonryCase-Study

Future State

Best Practice

Current State

SchematicDesign

Future State

Best Practice

Current State

DesignDevelopment

Future State

Best Practice

Current State

ConstructionDocuments

Future State

Best Practice

Current State

ContractorCoordination

Future State

Best Practice

Current State

SubcontractorInstallation

P r o j e c t P h a s e

RESOURCES

The course does not have a required textbook. The following reference texts and papers will be used during

the semester.

Sanford Friedenthal, Sanford, Moore, Alan, Steiner, Rick (2011) A Practical Guide to SysML: The Systems

Modeling Language, Morgan Kaufmann, 640 pp., ISBN: 978-0-12-385206-9.

Beall, Christine (2012) Masonry Design and Detailing, Sixth Edition, McGraw-Hill Education,

ISBN: 9780071766395.

Eastman, Chuck, Teicholz, Paul, Sacks, Rafael, Liston, Kathleen (20111) BIM Handbook: A Guide to Building

Information Modeling for Owners, Managers, Designers, Engineers and Contractors, 2nd Edition,

Wiley, ISBN-13: 978-0470541371.

(2012) Integrated Project Delivery Contracts and Guidebook, No. 300 (Tri-Party Agreement for Integrated

Project Delivery) and 301 (Building Information Modeling (BIM) Addendum), Consensus Docs.

(2010) Integrated Project Delivery for Public and Private Owners,

http://www.aia.org/aiaucmp/groups/aia/documents/pdf/aiab085586.pdf.

Senescu, R., and J. Haymaker, (2013). “Evaluating and Improving the Effectiveness and Efficiency of Design

Process Communication,” Advanced Engineering Informatics, 27(2), 299–313.

Clevenger, C. M., Haymaker, J. R., & Ehrich A. (2012). “Design exploration assessment methodology: testing

the guidance of design processes,” Journal of Engineering Design, 24(3), 165-184.

American Institute of Architects and AIA California Council (2007) Integrated Project Delivery: A Guide,

http://info.aia.org/siteobjects/files/ipd_guide_2007.pdf .

Florez Laura, Castro-Lacouture Daniel, and Gentry Russell, (2014) “Workflows in Masonry Construction:

Analysis of Labor Requirements”, 9th International Masonry Conference, 7-9 July 2014, Guimaraes, Portugal.

http://www.aia.org/aiaucmp/groups/aia/documents/pdf/aiab085586.pdf

http://info.aia.org/siteobjects/files/ipd_guide_2007.pdf


Witthuhn, Tyler , Gentry, T. Russell , Sharif, Shani and Elder, Jeff, (2014) “Masonry Product Models for

Building Information Modeling”, 9th International Masonry Conference, 7-9 July 2014, Guimaraes, Portugal.

Gentry, T.R., Eastman, C.E. and Biggs, D.T., (2013), “Developing a Roadmap for BIM in Masonry: A National

Initiative in the United States”, 12th Canadian Masonry Symposium, June 2-5 2013, Vancouver, BC, Canada.

Augenbroe, Godfried (2011) “The role of simulation in performance based building” in Building Performance

Simulation for Design and Operation, Henson, Jan L.M., and Lamerts, Roberts (eds.), Spon Press [limit review

to the text discussing system frameworks, aspect systems, and decision making]

GRADING

Participation and Leadership 10%

Individual Homework Assignments 30%

Case Study Project Work 30%

Final Submission and Presentation4 30%

Total 100%

ADDITIONAL GEORGIA TECH REQUIREMENTS

The Student Bill of Academic Rights - http://www.catalog.gatech.edu/rules/22.php

Academic Honor Code - http://www.catalog.gatech.edu/rules/18b.php

Access Disabled Assistance Program for Tech Students - http://www.adapts.gatech.edu/

4 The grade for the final submission will be based on the role that the students are playing in the class and on the completeness of their portion of the group projects. Grades will be assigned by the instructor and by the final review panel, and students will complete a peer review of their teams’ performance.

http://www.catalog.gatech.edu/rules/22.php

http://www.catalog.gatech.edu/rules/18b.php

http://www.adapts.gatech.edu/

Appendix 2: Georgia Tech BIM Execution Plan Template1

The Georgia Tech BIM Execution Plan template is a public document and is shared here to provide an

example of how sophisticated building owners are requiring BIM on their projects. This execution plan

can be considered as a broad definition of “Current BIM” state. As can be seen in the BIM execution

plan, there are some requirements that indirectly impact the masonry BIM model (e.g., the modeling

requirements for exterior walls) but at this point there are not explicit requirements for the modeling

of masonry in the BIM model.

1 Retrieved from: http://www.facilities.gatech.edu/dc/standards/2011_0531_GT_BIM_Execution_Plan_Template_v1.0.pdf

http://www.facilities.gatech.edu/dc/standards/2011_0531_GT_BIM_Execution_Plan_Template_v1.0.pdf

Georgia Tech BIM Execution Plan Template

September

2011 Version 1.0

Contents Contents ..................................................................................................................................................................................................... 2

Agreement ................................................................................................................................................................................................. 3

1 Overview ........................................................................................................................................................................................... 4

2 Project Initiation ................................................................................................................................................................................ 4

2.1 Project Information .................................................................................................................................................... 4

2.2 Core Collaboration Team ............................................................................................................................................ 4

2.3 Project Goals and Objectives ....................................................................................................................................... 4

2.4 Collaborative Process Mapping (Coordination Plan) ...................................................................................................... 4

2.5 Project Phases / Milestones ........................................................................................................................................ 6

3 Modeling Plan ................................................................................................................................................................................... 6

3.1 Model Managers ........................................................................................................................................................ 6

3.2 Planned Models ......................................................................................................................................................... 8

3.3 Model Components ................................................................................................................................................... 8

3.3.1 File Naming Structure ...................................................................................................................................................... 9

3.3.2 Precision and Dimensioning ............................................................................................................................................ 9

3.3.3 Model Attribute Data ....................................................................................................................................................... 9

3.3.4 Modeling Level of Detail ................................................................................................................................................ 10

3.4 Detailed Modeling Plan ............................................................................................................................................ 10

3.4.1 Programming/ Pre-Design Phase ................................................................................................................................... 11

3.4.2 Schematic Design Phase ................................................................................................................................................ 11

3.4.3 Preliminary Design Phase .............................................................................................................................................. 11

3.4.4 Construction Documents Phase ..................................................................................................................................... 12

3.4.5 Agency Review & Bidding Phase .................................................................................................................................... 12

3.4.6 Construction Phase ........................................................................................................................................................ 12

3.4.7 Close Out (Design Team) ................................................................................................................................................ 13

3.4.8 Close Out (Contractor) ................................................................................................................................................... 13

3.5 Analysis Plan ............................................................................................................................................................ 13

3.5.1 Analysis Models ............................................................................................................................................................. 13

3.6 Detailed Analysis Plan .............................................................................................................................................. 14

3.7 Clash Detection Process ........................................................................................................................................ 14

4 Concurrent As-Built Modeling Plan ................................................................................................................................................. 14

5 Construction Capture Schedule ....................................................................................................................................................... 15

6 Collaboration Plan ........................................................................................................................................................................... 15

7 Document Management ................................................................................................................................................................. 15

8 Document Management Solution ................................................................................................................................................... 16

Agreement By signature below, this BIM Execution Plan is herewith adopted and incorporated into the Agreement, dated _________, for Professional Design Services between _____________________________ and Georgia Tech.

Owner Date

Architect Date

Construction Manager Date

Structural Engineer Date

Mechanical Engineer Date

Electrical Engineer Date

Plumbing Engineer Date

Additional Party as Needed Date

Additional Party as Needed Date

1 Overview The intent of this BIM Execution Plan is to provide a framework that will let the owner, architect, engineers, and construction manager 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. All text that is RED is for illustrative purposes only, and should not be construed as a formalized response to this execution plan. Items in red are for reference only; items in RED should be deleted and/ or replaced with relevant project information.

2 Project Initiation This section defines the Core Collaboration Team, the project objectives, project phases, and overall communication plan throughout the project’s phases.

2.1 Project Information Project Name:

Project Number:

Project Address:

Project Description:

2.2 Core Collaboration Team List all stakeholders that form the project management team below. These individuals share in the responsibility of providing oversight pursuant to validation of the project program, cost and value.

Contact Name Role/Title Company Email Phone

2.3 Project Goals and Objectives List all project goals and objectives below.

Project Goal Objective Achieved if Project Timeframe

2.4 Collaborative Process Mapping (Coordination Plan) All stakeholders on the project are to briefly describe and identify their roles and responsibilities below. The purpose of the process map is to plan events, coordination, and the deliverables for each milestone. Role owners, described as a column will reflect their responsibilities per project phase.

Owner Architect Consulting Engineers Construction Manager Commissioning Agent

Programming/ Pre-Design Phase


Preliminary Design Phase


Agency Review & Bidding Phase

Construction Phase (Contractor)

Close-out (Design Team)

Close-out (Contractor)

2.5 Project Phases / Milestones This section identifies all stakeholders involved in completing project phase milestones. Start and completion dates will correspond with the approved project schedule. Stakeholders involved shall be the contributing parties assigned to those tasks within the phases for the project.

Project Phase / Milestone Estimated Start Date Estimated Completion Date Project Stakeholders Involved

Programming/ Pre-Design Phase


Preliminary Design Phase


Agency Review & Bidding Phase (Contractor)

Close-out (Design Team)

Close-out (Contractor)

3 Modeling Plan Advance planning around which models will need to be created during the different phases of the project, which will be responsible for updating models and distributing them, and predetermining the content and format of models as much as possible, will help your project run more efficiently and cost-effectively during every phase.

3.1 Model Managers Each party—such as the owner, architect, contractor, or sub-consultants—that is responsible for contributing modeling content should assign a model manager to the project. The model manager from each party has a number of responsibilities. They include, but are not limited to:

• Transferring modeling content from one party to another

• Validating the level of detail and controls as defined for each project phase

• Validating modeling content during each phase

• Combining or linking multiple models

• Participating in design review and model coordination sessions

• Communicating issues back to the internal and cross-company teams

• Keeping file naming accurate

• Managing version control

• Properly storing the models in the collaborative project management system

Stakeholder Company Name Model Manager Name Email Phone

3.2 Planned Models In the table below, outline the models that will be created for the project. List the model name, model content, project phase when the model will be delivered, the model’s authoring company, and the model-authoring tool that will be used. For models that will not be used or created in your project, just leave the row blank, and add rows for model types you anticipate needing that are not already listed. Items in RED are listed as an example.

Model Name Model Content Project Phase Authoring

Company Authoring Tool

Architectural Model Architectural objects, code information Autodesk Revit Architecture

Civil Model Topography, site utilities to within 5 feet of perimeter, hard and soft surfaces, other site objects

Autodesk Civil 3D

Structural Model Structural steel members, bearing and shear walls, analytical structural model, lintels

Autodesk Revit Structure

Mechanical Model Mechanical systems, equipment, load information, utilities within 5 feet of building perimeter

Autodesk Revit MEP

Electrical Model Electrical systems, equipment, load information, utilities within 5 feet of building perimeter

Autodesk Revit MEP

Plumbing Model Plumbing systems, equipment, load information, utilities within 5 feet of building perimeter

Autodesk Revit MEP

Energy Model Energy data, run iterations, life cycle costing, peak loads

Autodesk Ecotect/ EQuest

Construction Model Scheduling information, sequencing information

Autodesk NavisWorks

Estimate Model Costing data, quantity takeoffs Autodesk Quantity Takeoff

Coordination Model Design Intent Models and Fabrication information

Autodesk NavisWorks

3.3 Model Components As an aid to usability during later phases of your project, specify what the content, level of detail, and file naming structure of your models should look like.

3.3.1 File Naming Structure Determine and list the structure for model file names and data format.

File Names for Models Should Be Formatted as:

DISCIPLINE-Project Number-Building Number.rvt (example: ARCH-20090001-BL001.rvt). Confirm with GT.

Architectural Model ARCH-

Civil Model CIVL-

Mechanical Model MECH-

Electrical Model ELEC-

Plumbing Model PLMB-

Food Service Model KTCH-

Structural Model STRC-

Telecommunications TCOM-

Audio Visual AVIS-

Energy Model ENRG-

Construction Model CNST-

Estimate Model COST-

Coordination Model COOR-

3.3.2 Precision and Dimensioning Models should include all appropriate dimensioning as needed for design intent, analysis, and construction. With the exception of the exclusions listed below, the model will be considered accurate and complete. In the table below, enter which items’ placement will not be considered entirely accurate and should not be relied on for placement or assembly.

Items that Will Not Be Considered Accurate for Dimensioning or Placement

Architectural –

MEP –

Civil –

Construction –

Food Service –

Structural –

3.3.3 Model Attribute Data The level of property information in the modeling objects and assemblies depends on the types of analysis that will be performed on the model.

Specify model and model component COBie data per the GT BIM Requirements. The team will be required to add information to the BIMs that will add value to GT’s facility management systems. In support of COBie, the Project Team is required to utilize attributes within the GT BIM template to assist in generation of required information for contribution to the GT FM data structure. See Appendix 7.2 of the GT BIM Requirements.

See Section 4.2.2 of the GT BIM Requirements

See Section 4.3.1.1 of the GT BIM Requirements for COBie data requirements. The team is expected to understand data requirement for all phases of the work, and should show how data capability requirements influence the planning and collaboration for this project. Diagramming expected and anticipated events, solving workflow dynamics for the collaborative team will address the intent of the BIM project.

3.3.4 Modeling Level of Detail Specify the level of detail in your models below. The level of detail can be defined by exclusions and/or by object size. The level of detail described here should reflect descriptions listed within the AIA E202.

Exclusions: List the objects excluded from the model in the table below. Items that Will Be Excluded from the Model

Architectural –

MEP –

Civil –

Construction –

Food Service –

Structural –

Size: Any object smaller than [1”] will not be included in the model.

3.4 Detailed Modeling Plan For each phase of the project, the project team should create a detailed modeling plan, which should include the modeling objectives, models included, and the roles and responsibilities of model authors. Model objectives and model manager roles and responsibilities by phase are outlined below.

3.4.1 Programming/ Pre-Design Phase

3.4.1.1 Objectives: Provide initial design based on conceptual parameters established by the owner, ensure that code and zoning requirements meet project objectives, and establish a 3D reference point of model coordination. Provide Program of Requirements and all space considerations for reference in the model.

3.4.1.2 Model Roles: A model may or may not take shape during the Conceptualization / Program of Requirements phase. If a model is created, its role will be to depict the visual concept and general layout of the project along with space requirements.

3.4.1.3 Responsibilities: The architect’s designated model manager will establish a baseline model to be used as the basis for other models. During the Conceptualization / Program of Requirement phase, the model managers from all parties will establish modeling standards and guidelines.

3.4.2 Schematic Design Phase

3.4.2.1 Objectives: Provide spatial design based on input from the Conceptualization / Program of Requirement phase; provide initial design for building system and attributes including architectural, structural, and MEP; identify initial coordination issues between building systems; receive input from suppliers and fabricators regarding system cost, placement, fabrication and scheduling.

3.4.2.2 Model Roles: The Architectural model will show the general design and layout of the building structure and act as the baseline for all other subsystem designs, such as MEP and Structural models. The subsystem designs will be used to show the initial selection and layout of building components. The Architectural model and Consulting Engineers’ model will be used to inform the Energy Models.

3.4.2.3 Responsibilities: Once the baseline conceptual structure has been created, the architect’s model manager will send the model to the sub-consultants so they can develop their designs. The consulting engineers’ designated model managers will audit and deliver the completed models to the architect’s model manager. The architect’s model manager will review the models to ensure compliance with the phase requirements. Once the models meet the requirements, the architect’s model manager will link or combine cross-disciplinary models. The architect’s model manager should coordinate with the consulting engineers’ model managers to eliminate duplicate or redundant objects.

3.4.3 Preliminary Design Phase

3.4.3.1 Objectives: Provide final design of building and building systems; resolve coordination issues between building systems; provide a Construction model capable of analyzing schedule, cost, and constructability.

3.4.3.2 Model Roles: The Architectural model will continue to act as the baseline for all other subsystem designs. The subsystem designs will be modified accordingly to represent the enhanced design.

3.4.3.3 Responsibilities: The consulting engineers’ model managers will use the Architectural model to revise and complete their designs. Once the models are complete, the consulting engineers’ model managers will deliver their models to the architect’s model manager. The architect’s model manager will review the models to ensure compliance with the phase requirements. The architect’s model manager will provide the construction manager’s model manager with the Architectural model and the Consulting Engineers’ models.

3.4.4 Construction Documents Phase

3.4.4.1 Objectives: Finalize design of the building and all building systems, prepare documentation for agency review, and provide construction modeling that highlight constructability, trade coordination, and fabrication.

3.4.4.2 Model Roles: All design models will be used to reflect the design. The models will then be used to generate the contract documents. The Construction model will be used primarily for estimating, scheduling, and constructability analysis.

3.4.4.3 Responsibilities: The architect and engineer's model managers will prepare contract documents for agency review based on the Design Intent models.

3.4.5 Agency Review & Bidding Phase

3.4.5.1 Objective: Revise Design Intent models based on agency feedback on all models.

3.4.5.2 Model Roles: The design models will be adjusted to reflect agency feedback. The Construction model will be enhanced and further used for estimating, scheduling, construction sequencing, trade coordination, and constructability analysis.

3.4.5.3 Responsibilities: The architect’s model manager will communicate agency comments back to the design team. The consulting engineers’ model managers will revise their design models accordingly and submit them back to the architect. The architect’s model manager will provide the construction manager’s model manager with the Architectural model and the Consulting Engineers’ models.

3.4.6 Construction Phase

3.4.6.1 Objectives: Update Architectural and Consulting Engineers’ models based on submittals, RFIs, or owner-directed changes; maintain the Construction model based on construction activities. The construction team will submit RFIs and submittals through the collaborative project management system.

3.4.6.2 Model Roles: The Architectural and Consulting Engineers’ models will be revised throughout construction, based on owner directives and As Built comments. The models will always reflect the revised contract documents. The Construction model will be used for scheduling analysis, construction sequencing, and trade coordination.

3.4.6.3 Responsibilities: The architect’s model manager will work with their consulting engineers to answer the RFIs and submittals and adjust the models accordingly. The construction manager’s model manager will update the Construction model and will work with the architect to develop the Architectural and Consulting Engineers’ models.

3.4.7 Close Out (Design Team)

3.4.7.1 Objective: Use the Architectural and Consulting Engineers’ models for facility management, with the possibility of use in ongoing operations.

3.4.7.2 Model Roles: The Architectural and Consulting Engineers’ models will be used to represent the actual assembly of the building from construction.

3.4.7.3 Responsibilities: The architect will deliver the models at the end of the project to the owner.

3.4.8 Close Out (Contractor)

3.4.8.1 Objective: Use the Architectural and Consulting Engineers’ models for facility management, with the possibility of use in ongoing operations.

3.4.8.2 Model Roles: The Architectural and Consulting Engineers’ models will be used to represent the actual assembly of the building from construction.

3.4.8.3 Responsibilities: The contractor will deliver the models at the end of the project to the owner.

3.5 Analysis Plan By listing and specifying what types of analysis your project will likely require at the beginning of your project, you can ensure that your key models will include the relevant information, making the analysis easier and more efficient.

3.5.1 Analysis Models Your project’s scope of work may require performing certain kinds of analysis, such as the ones listed below, based on existing or specially created model(s). In most cases, the quality of the analysis depends on the quality of the original model that the analysis is derived from. Therefore, the project team member performing the analysis should clearly communicate the analysis requirements to the original model authoring team member.

3.5.1.1 Quantity Takeoff Analysis The objective of quantity takeoff analysis is to use modeling property data to automate or simplify the quantity takeoff process. This information from the quantity takeoff tool can then be imported or tied to cost-estimating software. In order for the quantity takeoff process to work seamlessly, the original modeling author will need to include the relevant property information in the design and an agreement of modeled content communities to estimate.

3.5.1.2 Scheduling Analysis Scheduling analysis lets the project team use the project model to analyze the timeline and sequencing for construction. This information can then be used to modify or adjust the construction schedule. Tools currently exist that allow project team members to visualize the construction over time, but no systems exist yet that interact automatically with scheduling tools.

3.5.1.3 Visualization Analysis Visualization tools let the project team view the design or construction of the project in 3D, giving them a more accurate perspective of the product.

3.5.1.4 LEED Rating/Energy Analysis LEED (leadership in energy and environmental design) Rating/Energy Analysis tools help the project team evaluate the impact of design decisions on sustainability and energy consumption. This analysis model is usually based on the main Architectural model, after which material and building system inputs can be used to evaluate the project’s sustainability and energy consumption.

3.5.1.5 Structural Analysis Structural analysis tools use the model to analyze the building’s structural properties. Structural analysis programs typically use the finite element method (FEM) to measure the stresses on all structural elements of the design. For structural analysis to work seamlessly, the original structural modeling tool needs to be compatible with the structural analysis tool, and the original structural model property data must include information about the structural elements.

3.6 Detailed Analysis Plan For each type of analysis that may be performed for your project, list the models used for the analysis, which company will perform the analysis, the file format required for the analysis, the estimated project phase, and the analysis tool that will be used. If there are, other special instructions associated with the analysis, mark the Special Instructions column and list the details in the Special Instructions table in the next section.

Analysis Analysis Tool Model Analyzing C

Project Phase File Format R i d Visualization Architectural & Structural Model .rvt/.nwf

Structural Structural Model .rvt

Quantity Takeoff All Models .rvt

Scheduling /4D All Models .rvt/.nwf

Cost Analysis /5D All Models .rvt/.nwf

Energy/LEED Architectural Model .IFC/ .rvt/.gbXML

Daylight/Lighting Architectural Model .IFC/ .rvt/.FBX

3.7 Clash Detection Process Clash detection analysis is done to check for interferences between the designs of one or many models. To reduce change orders during construction, clash detection should be performed early and continue throughout the design process. For clash detection to work properly your project’s models, need to have a common reference point and they must be compatible with the clash detection tool.

4 Concurrent As-Built Modeling Plan As-built modeling will be a collaborative effort between the Architect and consultants and the construction team. During the construction process, the design team will incorporate changes triggered by requests for information (RFIs), architect’s supplemental instructions (ASIs) and change orders in into the Architectural and Consultant models. At specified dates during the construction process, the construction team will provide the design team with necessary changes due to shop drawings, coordination drawings and change orders. As required, the completed form of the

construction will also be verified at these specified dates using laser scanning. The design team will then incorporate the changes reported by the construction team into the Architectural and Consultant models. At the end of construction, it will be the updated Architectural and Consultant models that are used for facility management.

5 Construction Capture Schedule Event Date Parties involved

Construction Capture 1 Construction team, Design Team, [Laser Scanning]

Construction Capture 2 Construction Team, Design Team, [Laser Scanning]



6 Collaboration Plan Creating a collaboration plan early on—including defining permissions and file structures—will help team members efficiently communicate, share, and retrieve information throughout the project. It lets you get the most out of your collaborative project management system, saving time and increasing your ROI.

7 Document Management A Collaborative Project Management system will have to be researched and agreed upon prior to start of project. The requirements of the Collaborative Project Management system are:

• Be web-based or web-enabled—so all relevant, authorized project team members can remotely access it.

• Accommodate different permissions profiles for different project team members.

• Allow communication through either internal messaging or system-generated email.

• Include document management capability that lets the project team create a customized and permission-based folder structure, which offers upload, download, and version control capabilities.

• Include a viewer that allows the project team to view .dwg, .dgn, .plt, .dwf, .pdf, .tif, .jpg, .doc, and .xls files.

• Include construction management capabilities for the tracking of requests for information (RFIs), submittals, design review, meeting minutes, daily reports, issues, correspondence, and transmittals.

• Able to interact with the file folder structure in the document management section.

• Able to automatically accept raw data from the clash detection tool.

• Include bid management capability, and this bid management solution should allow the project team to post the contract drawings and specifications for viewing in the form of a Plan Room.

• Allow for cost management controls, and this cost management capability should include budgeting, contracting, change orders processing, and payments applications tracking.

• Allow the project team to run reports based on the information in the system.

• Allow for the workflow and routing throughout the document, construction and cost management components of the solution.

8 Document Management Solution A document management solution will be provided by the owner. The document management solution that will be used is called [TBD]. The architect will setup the site and set up all permissions for the site. The architect will lead a training session for the entire project team on how to use the site. The site will be maintained from the signing of this document until the occupation of the building.