12.12.2015 Views

Massport BIM and Lean Update

ACECMA-Massport_BIM_and_Lean_12012015

ACECMA-Massport_BIM_and_Lean_12012015

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Massport</strong> <strong>BIM</strong><br />

<strong>and</strong> <strong>Lean</strong><br />

<strong>Update</strong><br />

Danielle Arciero, <strong>Massport</strong><br />

Joeseph A. Barra, Esq., Robinson + Cole LLP<br />

Luciana Burdi, <strong>Massport</strong><br />

1


• <strong>BIM</strong> Guide Overview<br />

• <strong>BIM</strong>/<strong>Lean</strong> <strong>Update</strong><br />

• <strong>BIM</strong> Exhibit Document Summary<br />

• As-Built <strong>and</strong> Record Process


• The <strong>BIM</strong> Guide for Vertical <strong>and</strong><br />

Horizontal Construction supports<br />

<strong>Massport</strong>’s multi-year vision for<br />

<strong>Lean</strong> <strong>and</strong> <strong>BIM</strong><br />

• <strong>Lean</strong> <strong>and</strong> <strong>BIM</strong> are equally essential<br />

enablers in <strong>Massport</strong>’s strategy for<br />

innovative project delivery<br />

• <strong>Massport</strong> expects <strong>BIM</strong> to be used<br />

<strong>and</strong> maximized within a <strong>Lean</strong><br />

collaboration environment


• Terminology<br />

• It’s a different language<br />

• Process Changes<br />

• <strong>BIM</strong> is a new process with new phases<br />

<strong>and</strong> new submissions<br />

• <strong>BIM</strong>xP<br />

• Document the reality for all to follow<br />

• <strong>BIM</strong> Uses & Data Requirements<br />

• Define what adds value, <strong>and</strong> what<br />

data is useful<br />

• New Submissions<br />

• Analysis, simulations, lifecycle data


Value Mapping<br />

Defines<br />

Conditions of<br />

Satisfaction (CoS)<br />

Visible Decision<br />

Making Process<br />

Develop <strong>and</strong><br />

produce well<br />

Coordinated<br />

Documents<br />

12 external <strong>and</strong> 11 internal<br />

<strong>BIM</strong> Execution Plan (<strong>BIM</strong>xP) Contents<br />

Align <strong>BIM</strong> Uses <strong>and</strong> <strong>Lean</strong> Tools<br />

To Supports CoS<br />

Use of Pull Plan<br />

Clash Avoidance<br />

Tracking Progress<br />

PPC<br />

<strong>BIM</strong> to support<br />

Decision Making<br />

Use of A3s<br />

Trade Modeling<br />

Underst<strong>and</strong> Ex.<br />

Conditions<br />

<strong>Lean</strong> Tools<br />

Support CoS<br />

Execution<br />

Laser<br />

Scanning<br />

Modeling<br />

Ex Cond.<br />

CoS<br />

What adds value<br />

to a project<br />

<strong>BIM</strong> Uses<br />

Support CoS<br />

Execution<br />

Constraints<br />

Prevents an activity<br />

from starting,<br />

advancing, or<br />

completing as<br />

planned.<br />

© 2014 Luciana Burdi


SUMMARY OF MASSPORT<br />

<strong>BIM</strong> EXHIBIT<br />

I. GENERAL<br />

II. RESPONSIBILITY FOR MODEL<br />

DEVELOPMENT<br />

III. RESPONSIBILITY FOR MODEL OWNERSHIP<br />

IV. RESPONSIBILITY FOR MODEL<br />

MANAGEMENT<br />

V. RESPONSIBILITY FOR MAINTENANCE OF<br />

DIGITAL DATA<br />

VI. <strong>BIM</strong> EXECUTION PLAN


I. GENERAL<br />

a. Applies only to projects using CM At-Risk<br />

b. <strong>BIM</strong> Exhibit is a Contract Document that bolts on to<br />

Owner’s existing Owner/Designer <strong>and</strong> Owner/CM<br />

contract forms<br />

c. Project Designer is required to bolt <strong>BIM</strong> Exhibit on to<br />

its Subconsultant agreements to the extent that such<br />

downstream vendors receive Digital Data<br />

d. Project CM (Constructor) is required to bolt <strong>BIM</strong><br />

Exhibit onto its Subcontractor <strong>and</strong> Trade Contractor<br />

agreements to the extent that such downstream<br />

vendors receive Digital Data


I. GENERAL (con’t)<br />

e. Anticipates use of <strong>BIM</strong> Execution Plan (<strong>BIM</strong>xP) in<br />

order to customize digital risks <strong>and</strong> responsibilities<br />

for the particular project<br />

f. Definitions reference back to Owner’s <strong>BIM</strong> Guidelines<br />

(Guidelines)<br />

g. No impact to risks already identified in underlying<br />

agreements (unless specifically identified)


II.<br />

RESPONSIBILITY FOR MODEL<br />

DEVELOPMENT<br />

a. Model is the Project’s primary Contract Document<br />

b. Designer is to coordinate <strong>and</strong> incorporate the Digital<br />

Data of its own subconsultants as well as the design<br />

of the Owner’s separate consultants<br />

c. Designer is responsible for detecting <strong>and</strong> remedying<br />

interferences by <strong>and</strong> between the Design Model <strong>and</strong><br />

the Discipline Models.<br />

d. Designer retains ultimate responsibility for Model’s<br />

design content <strong>and</strong> development throughout the<br />

entire project


II.<br />

RESPONSIBILITY FOR MODEL<br />

DEVELOPMENT (con’t)<br />

e. Owner is responsible for defining the Model’s Level of<br />

Development (LOD) as more specifically described in the<br />

<strong>BIM</strong>xP<br />

f. Constructor is responsible to coordinate the Digital Data<br />

of its subcontractors <strong>and</strong> trade contractors <strong>and</strong> to deliver<br />

construction information to the Designer at intervals<br />

prescribed in the <strong>BIM</strong>xP.


II.<br />

RESPONSIBILITY FOR MODEL<br />

DEVELOPMENT (con’t)<br />

h. Constructor is responsible for detecting <strong>and</strong><br />

remedying interferences between the Design Model<br />

<strong>and</strong> the Trade Models<br />

i. St<strong>and</strong>ard of Care for design services is consistent with<br />

underlying Owner/Designer Agreement


III. RESPONSIBILITY FOR MODEL<br />

OWNERSHIP<br />

a. Owner retains all legal rights <strong>and</strong> title to the<br />

Model <strong>and</strong> grants a use license to the project<br />

team.<br />

b. Unauthorized Use of Model triggers<br />

indemnity to those who innocently rely upon<br />

such unauthorized use


IV. RESPONSIBILITY FOR MODEL<br />

MANAGEMENT<br />

a. Identifies the Parties’ responsibilities when<br />

Co-locating<br />

b. Identifies the Parties’ responsibilities when<br />

using a Virtual Network<br />

c. As-Builts: Designer is to verify <strong>and</strong> update the Model<br />

with information from the Constructor<br />

d. St<strong>and</strong>ard of Care for Model development services is<br />

uncoupled from the Designer’s professional st<strong>and</strong>ard<br />

of care


VI. <strong>BIM</strong> EXECUTION PLAN<br />

a. <strong>BIM</strong>xP is NOT a Contract Document<br />

b. Describes process for further <strong>BIM</strong>xP<br />

development<br />

c. Identifies elements of <strong>BIM</strong>xP:


Current As-Built & Record Document<br />

Process<br />

CM/GC<br />

A/E<br />

MPA<br />

Contractor<br />

As-Builts<br />

PDF or DWG<br />

Redlines<br />

LEGEND<br />

Civil<br />

Structural<br />

MEP/FP<br />

Architectural<br />

+ + +<br />

Contractor Files<br />

+<br />

As Designed<br />

MEP/FP <strong>and</strong><br />

Structural<br />

+<br />

Contractor<br />

As-Builts<br />

PDF, DWG,<br />

or RVT<br />

overlaid<br />

with<br />

Contractor<br />

As-Builts<br />

Record<br />

Architectural<br />

+<br />

Record<br />

MEP/FP <strong>and</strong><br />

Structural<br />

+<br />

Record Civil<br />

FINAL<br />

RECORD<br />

PDF,<br />

DWG, or<br />

RVT<br />

Design Files


Future As-Built & Record Document<br />

Process<br />

CM/GC<br />

A/E<br />

MPA<br />

Federated<br />

Model<br />

+<br />

Trades/Subs<br />

Native Files<br />

+<br />

Point Cloud<br />

Civil<br />

Structural<br />

MEP/FP<br />

Minimum<br />

Requirements for<br />

Civil, MEP/FP,<br />

<strong>and</strong> Arch to be<br />

defined in <strong>BIM</strong>xP<br />

LEGEND<br />

Navisworks<br />

Native File Format<br />

Point Cloud<br />

Revit<br />

Revit<br />

Architectural<br />

+<br />

Point Cloud<br />

As Designed<br />

MEP/FP <strong>and</strong><br />

Structural<br />

+<br />

As-Built<br />

Federated<br />

Model<br />

+<br />

Trades/Subs<br />

Native Files<br />

Point Cloud is<br />

Linked to Revit<br />

File by Architect<br />

• May be<br />

linked to<br />

Revit as<br />

reference to<br />

as-built<br />

conditions<br />

• Engineer to<br />

review <strong>and</strong><br />

sign-off<br />

Record Revit<br />

Architectural<br />

+<br />

As Designed<br />

MEP/FP <strong>and</strong><br />

Structural<br />

+<br />

As-Built<br />

Conditions<br />

Point Cloud<br />

+<br />

Record<br />

Federated<br />

Model<br />

+<br />

Trades/Subs<br />

Native Files<br />

FINAL<br />

RECORD

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!