integrated product, organization and process...

67
Integrated Product, Organization and Process design John Kunz The big idea: Integrated Product, Organization and Process design can support, at least, the design, fabrication, assembly and use of new products Rate Baseline ($K) Change Year-1 (K$) Revenue 100,000 2% 102,000 Cost of contracted work 85% 85,000 -2.0% 84,660 Cost of self-performed work 10% 10,000 2.0% 12,240 Gross Margin 5,000 5,100 Sales, G&A 2% 2,000 2,040 IT investment 70 Amortized costs of IT/yr 33% 23 Net income 3,000 3,037 Time to payback (years) 1.9 Net Income change (%) 1.2

Upload: others

Post on 12-Jul-2020

2 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Integrated Product, Organization and Process

design

John Kunz

The big idea: Integrated Product, Organization and Process design can support, at least, the design, fabrication, assembly and use of new products

Rate

Baseline

($K) Change

Year-1

(K$)

Revenue 100,000 2% 102,000

Cost of contracted work 85% 85,000 -2.0% 84,660

Cost of self-performed work 10% 10,000 2.0% 12,240

Gross Margin 5,000 5,100

Sales, G&A 2% 2,000 2,040

IT investment 70

Amortized costs of IT/yr 33% 23

Net income 3,000 3,037

Time to payback (years) 1.9

Net Income change (%) 1.2

*05-07-01

Finish

Final Program

Confirmation with

Pharmacology

Final Program

confirmation with LAR

KPFF

SRG Lab Task 37 Task 44 Project Mgt AEI Core Task 41 Task26 H Block Crew Task 23SRG / AEI

TechnicalAEI Core and

SRG LabHDCCO Costing

SRG

TechnicalKPFF

AEI Core

and TechHDCCO Core

Code Rev

ConsultantSolvent Tarter

H Block Crew

& Tech

SRG

Landscape

Tele Data

DesignCode Rev

Furniture

37.

*Reprogram

B#15 Shafts

34. *Finalize

Pharmacology

Program

33. *Finalize

LAR Program

32. *Finalize

Bio-Organic

Chemistry

Program

35. *Finalize

Protein Chemistry

Program 20. *Determine Scope of

package D including vivarium

changes

45. *Complete all

Basement/LAR Drawings

41. *Reprogram

bookends B#13 and

B#15

36. *Analyze

structural impacts

12. *Complete UG

utiliites

25. *Do Central Plant

design changes

19. *Determine vertical

utilities

22. *Complete catwalk drawings

52. Finalize landscape

26. *Finalize B#13 and

B#15

Exiting/architecural H

occupancy concept

*Lab and

vivarium

Programming

Complete

27. *Finalize B#13,

15 Shaft Size &

MEP Room

Locations

31.* AEI &

SRG

Determine

Design $/Time

Impact of

Change

23. *Reprogram

B#13 and B#15

Exterior Architecture

Bookend

Programming

Accepted by Genentech

Notice to proceed on

structural changes

Architect

program/MEP

oncepts

Established

By Design

Team

29. *Document

lab plan

1. *Redesign main MEP

distribution systems

SRG Management AEI Management

Genentech PM

SRG Lab Plan

Ken Mouchka

Task 27Task 38

Organization

5. *Finalize lab & Equipment

plans

Task 29

Task 28

30. *Approve

Change to

Design

Contract

21. *Prepare Plan Views for

Review of Concept w/City

39. *Finalize MEP

distribution and

section

Task4 Task22

Review 80%

documents

48. *Develop exiting

plan

49. Develop

reflected ceiling

plan

Turnover

reflected

ceiling plan to

AEI

Detailed Design 80 PC

Complete

3. Complete Tele Data Design

42. *Develop

Execution

Strategy

44. *Complete

B#14 Officing

Planning

18. *Detailed Lab

Program

Documentation

47. *Develop lab

DD plan

28. *Determine

segregation of lab

and tech space

G accept lab

equipment matrix

*Package B structural

modifications (CCD3A)

13. *Code Consultants

Review Concept for final

city Presentation

14. *HDCCO update Estimate of cost

of Program

Review skin changes w/db team

Lab Planning Program

Meetings with

Pharmacology

Lab planning Program Meeting with Protein

Chemistry

BMS Controls Meetings

(Weekly)

Lab Planning Program meeting with Bio

Organic 80% Drawing Review

Tele Data Coordination MeetingsSteel Detailing

Meetings

Genentech 80% Detailed Design

Review

Final Program

Confirmation with Officing

Weekly

Coordination

Meeting

Lab Planning Program

Meetings with Directors

50. Designate size, location of

13 MEP, teledata rooms

54. KPFF design

stairs for 13/1438. *SRG

Reprogram 13/14

interface, exiting,

stairs

43. *Changes in Steel

Forwarded to Steel

Detailers

46. *RA Furnture

Concept Complete

MEP, Teledata room design

*Design Budget &

Schedule for Changes

Approved

*Notice to proceed

with detailed design

24. *Complete B13,4 H

block occupancy

requirements on MEP

systems

17. *Risick

reprogram solvent

distribution and waste

Issue 80%

MEP CDs

(20) Incorporate

80% MEP review

comments

(19) Genentech review

80% drawings

53. Incorporate

comments, complete

Architectural detail

2. Initial redesign MEP branch

lateral distribution

G accept

13/14

Interface

*City Accept

exiting

*Package C

skin

modifications

55. KPFF design

stairs for 15/14

40. *SRG

Reprogram 15/14

interface, exiting,

stairs

B13 MEP HVAC,

conduit, piping mains

completed

MEP 80% Review

comments

incorporated

Package D and UG

addendum issued:

underground utilities,

vivarium catwalk

10. Draft Alternate means

15. Jeff reprogram HMIS

(3) *AEI design MEP

HVAC, Conduit &

piping mains B13

16. *HDCCO Determine

Schedule Impact

City Approval of

Alternate Means

for Program

8. Review Alternate

Means w/impact on LEL

and LFFH

(21-4) Finalize MEP Details,

update specs and p&ID's

(8) *Revise

MEP loads, MEP

Equipment

schedules

finalized

(13,15,16) MEP specs, P&ID's,

control sequences

Work Process

Meetings

(6) Coord B13 MEP

floor section

4. complete all Interior Architcture

*Cal OSHA Recommend

Determination of LFFH

51. Designate size, location

of 14 MEP, teledata rooms G accept

15/14

Interface

*Accept project

scope:budget

by Genentech

*City Approval of

H Concept

*Exterior

Programming

Accepted by Genentech

*Turnover lab and

vivarium DD plan

to AEI

Page 2: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product,

Organization and Process Design

2

This week overview

Day Take-home

Tuesday Introduction:

Theory: ICE, organizational modeling, big data,

templates, VDC POP/FFB framework, types of models

Practice: ICE session with Templates, Organization-

process model and analysis (SimVision) lab

Thursday Theory: Project definition

Practice: Organization-process model and analysis

(SimVision), continued, and big data (SEE-IT) labs

Page 3: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 3

The next three weeks we will …

• Do integrated design and analysis with VDC

and the ABC of your POP - FFB based on a

PBS, OBS and WBS using ICE, templates

and big data …

Page 4: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 4

Tuesday Learning goals

• Get basic familiarity with the POP project framework of

VDC

• Product – Organization – Process (POP)

• Function – Form – Behavior (FFB)

• Understand class organization, opportunities, methods

and expectations

• Motivate interest in Integrated Design enabled by

VDC:

• Opportunities in practice

• Fun, power and job opportunities of models, model-

based analyses

Page 5: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 5

Chalmers Integrated Product, Organization and

Process Design Agenda: July 9

• Big ideas: Integrated design and analysis;

elements of VDC

• Introductions

• Models: how to recognize and use different

types

• Business goals and objectives

• Course goals (and non-goals)

• Course Organization

• ORID

Object AttributeRequirement

Relationship Requirement

Predicte

d value

Observed

value -2 -1 0 1 2

Product

Product Scope

Product Scope . Building Spaces includes -

Project Goals

Project Goal . Capacity (people) >= 60 - ?o

Project Goal . Cost (M$) = 70 - ?o

Building

Goal . Net Energy Use (K-

BTU/ft2) <= 250 - ?o

Building

Goal . Quality conformance

(%) >= 12 - ?o

Organization Scope

Organization Scope . Actors includes - -

Organization Goals

Organization Goal . Predicted . Cost (K$) - <= - ?o

Organization

Goal . Observed . Response

Latency (days) 3 <= - ?o

Organization

Goal . Predicted . Peak

Backlog (days) 3 <= - ?o

Organization

Goal . Predicted . rework

(FTE-days) - <= - ?o

Process

Process Goals

Process Goal . Peak Quality Risk < 0.50 - -

Process

Goal . Schedule Growth

(months) < - ?o

Process Goal . Completion Date <= 1/1/09 - ?o

Process Task . Action: Object

Process Task . Design: Actor Actor that designs

Process Task . Predict: Actor Actor that predicts

Process Task . Assess: Actor Actor that assesses

Process Task . Build: Actor Actor that builds

Function Product Behavior

Organization

Qualitative Threshhold values

Structural

Design Subteam

Project

Coordination Meeting

Architectural

Design Subteam

Design PM

Client PM

Project

Engineers

Construction

PM

Procurement

Subteam

Start

Long Lead Purchasing

Apply Exc Permit

Seek Zoning Variance

Provide GMP

Select Key Subs

Project Coordination

Estimate Cost

GMP

Accepted

Choose Construction Methods

Select Subconsultants

Finalize Arch

Program

Estimate Time

Define Scope

Choose facade materials

Choose Struct.

System

Design Coordination

Ready

to

Excavate

Page 6: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Introductions

Briefly, please share

• Name

• Field of study

• One personal goal for this class

9 July 2013 Chalmers Integrated Product, Organization and Process Design 6

Page 7: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Agenda

AM session

• Welcome

• Introductions

• Course overview

• VDC models and

templates

• ICE-1: Work session-1

• ICE-1 session debrief

PM session

• ICE-1: Work session-2

• ICE-2 session debrief

• Project definition and

templates in some

detail

• Load web site and

software

9 July 2013 7 Chalmers Integrated Product, Organization and Process Design

Page 8: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 8

Traditional product models

+: Work in practice

: Ambiguities to

stakeholders

: computer analysis ...?

– Show value to owner

– List components

– Estimate cost

– Plan construction

– Identify interferences

Page 9: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 9

Models

• Physical

• Statistical

• Mathematical

Symbolic

Graphic

*05-07-01

Finish

Final Program

Confirmation with

Pharmacology

Final Program

confirmation with LAR

KPFF

SRG Lab Task 37 Task 44 Project Mgt AEI Core Task 41 Task26 H Block Crew Task 23SRG / AEI

TechnicalAEI Core and

SRG LabHDCCO Costing

SRG

TechnicalKPFF

AEI Core

and TechHDCCO Core

Code Rev

ConsultantSolvent Tarter

H Block Crew

& Tech

SRG

Landscape

Tele Data

DesignCode Rev

Furniture

37.

*Reprogram

B#15 Shafts

34. *Finalize

Pharmacology

Program

33. *Finalize

LAR Program

32. *Finalize

Bio-Organic

Chemistry

Program

35. *Finalize

Protein Chemistry

Program 20. *Determine Scope of

package D including vivarium

changes

45. *Complete all

Basement/LAR Drawings

41. *Reprogram

bookends B#13 and

B#15

36. *Analyze

structural impacts

12. *Complete UG

utiliites

25. *Do Central Plant

design changes

19. *Determine vertical

utilities

22. *Complete catwalk drawings

52. Finalize landscape

26. *Finalize B#13 and

B#15

Exiting/architecural H

occupancy concept

*Lab and

vivarium

Programming

Complete

27. *Finalize B#13,

15 Shaft Size &

MEP Room

Locations

31.* AEI &

SRG

Determine

Design $/Time

Impact of

Change

23. *Reprogram

B#13 and B#15

Exterior Architecture

Bookend

Programming

Accepted by Genentech

Notice to proceed on

structural changes

Architect

program/MEP

oncepts

Established

By Design

Team

29. *Document

lab plan

1. *Redesign main MEP

distribution systems

SRG Management AEI Management

Genentech PM

SRG Lab Plan

Ken Mouchka

Task 27Task 38

Organization

5. *Finalize lab & Equipment

plans

Task 29

Task 28

30. *Approve

Change to

Design

Contract

21. *Prepare Plan Views for

Review of Concept w/City

39. *Finalize MEP

distribution and

section

Task4 Task22

Review 80%

documents

48. *Develop exiting

plan

49. Develop

reflected ceiling

plan

Turnover

reflected

ceiling plan to

AEI

Detailed Design 80 PC

Complete

3. Complete Tele Data Design

42. *Develop

Execution

Strategy

44. *Complete

B#14 Officing

Planning

18. *Detailed Lab

Program

Documentation

47. *Develop lab

DD plan

28. *Determine

segregation of lab

and tech space

G accept lab

equipment matrix

*Package B structural

modifications (CCD3A)

13. *Code Consultants

Review Concept for final

city Presentation

14. *HDCCO update Estimate of cost

of Program

Review skin changes w/db team

Lab Planning Program

Meetings with

Pharmacology

Lab planning Program Meeting with Protein

Chemistry

BMS Controls Meetings

(Weekly)

Lab Planning Program meeting with Bio

Organic 80% Drawing Review

Tele Data Coordination MeetingsSteel Detailing

Meetings

Genentech 80% Detailed Design

Review

Final Program

Confirmation with Officing

Weekly

Coordination

Meeting

Lab Planning Program

Meetings with Directors

50. Designate size, location of

13 MEP, teledata rooms

54. KPFF design

stairs for 13/1438. *SRG

Reprogram 13/14

interface, exiting,

stairs

43. *Changes in Steel

Forwarded to Steel

Detailers

46. *RA Furnture

Concept Complete

MEP, Teledata room design

*Design Budget &

Schedule for Changes

Approved

*Notice to proceed

with detailed design

24. *Complete B13,4 H

block occupancy

requirements on MEP

systems

17. *Risick

reprogram solvent

distribution and waste

Issue 80%

MEP CDs

(20) Incorporate

80% MEP review

comments

(19) Genentech review

80% drawings

53. Incorporate

comments, complete

Architectural detail

2. Initial redesign MEP branch

lateral distribution

G accept

13/14

Interface

*City Accept

exiting

*Package C

skin

modifications

55. KPFF design

stairs for 15/14

40. *SRG

Reprogram 15/14

interface, exiting,

stairs

B13 MEP HVAC,

conduit, piping mains

completed

MEP 80% Review

comments

incorporated

Package D and UG

addendum issued:

underground utilities,

vivarium catwalk

10. Draft Alternate means

15. Jeff reprogram HMIS

(3) *AEI design MEP

HVAC, Conduit &

piping mains B13

16. *HDCCO Determine

Schedule Impact

City Approval of

Alternate Means

for Program

8. Review Alternate

Means w/impact on LEL

and LFFH

(21-4) Finalize MEP Details,

update specs and p&ID's

(8) *Revise

MEP loads, MEP

Equipment

schedules

finalized

(13,15,16) MEP specs, P&ID's,

control sequences

Work Process

Meetings

(6) Coord B13 MEP

floor section

4. complete all Interior Architcture

*Cal OSHA Recommend

Determination of LFFH

51. Designate size, location

of 14 MEP, teledata rooms G accept

15/14

Interface

*Accept project

scope:budget

by Genentech

*City Approval of

H Concept

*Exterior

Programming

Accepted by Genentech

*Turnover lab and

vivarium DD plan

to AEI

Object AttributeRequirement

Relationship Requirement

Predicte

d value

Observed

value -2 -1 0 1 2

Product

Product Scope

Product Scope . Building Spaces includes -

Project Goals

Project Goal . Capacity (people) >= 60 - ?o

Project Goal . Cost (M$) = 70 - ?o

Building

Goal . Net Energy Use (K-

BTU/ft2) <= 250 - ?o

Building

Goal . Quality conformance

(%) >= 12 - ?o

Organization Scope

Organization Scope . Actors includes - -

Organization Goals

Organization Goal . Predicted . Cost (K$) - <= - ?o

Organization

Goal . Observed . Response

Latency (days) 3 <= - ?o

Organization

Goal . Predicted . Peak

Backlog (days) 3 <= - ?o

Organization

Goal . Predicted . rework

(FTE-days) - <= - ?o

Process

Process Goals

Process Goal . Peak Quality Risk < 0.50 - -

Process

Goal . Schedule Growth

(months) < - ?o

Process Goal . Completion Date <= 1/1/09 - ?o

Process Task . Action: Object

Process Task . Design: Actor Actor that designs

Process Task . Predict: Actor Actor that predicts

Process Task . Assess: Actor Actor that assesses

Process Task . Build: Actor Actor that builds

Function Product Behavior

Organization

Qualitative Threshhold values

Page 10: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 10

Virtual Design and Construction: Fundamental method of this integrated design and analysis class

• Use of integrated multi-disciplinary computer-based performance models and analyses of design–construction projects – Product (building, device, service)

– Organization

– Work Process

• to support (explicit, public) business

objectives – Describe: Visualize and describe project

– Explain reasons for designs and choices

– Evaluate choices

– Predict project performance

AEC IT investment by General Contractor

Rate

Baseline

($M) Change

Revenue 100,000 22%

Cost of work 85% 85,000 -2.0%

CM, Design, GC fees 10% 10,000 2.0%

Gross Margin 5,000

Sales, G&A 2% 2,000

IT investment 1,000

Amortized costs of IT/yr 33%

Net income 3,000

Time to payback (years)

Year-1

122,000

101,260

14,640

6,100

2,440

333

3,327

3.1

3-

year

payb

ack

Object AttributeRequirement

Relationship Requirement

Predicte

d value

Observed

value -2 -1 0 1 2

Product

Product Scope

Product Scope . Building Spaces includes -

Project Goals

Project Goal . Capacity (people) >= 60 - ?o

Project Goal . Cost (M$) = 70 - ?o

Building

Goal . Net Energy Use (K-

BTU/ft2) <= 250 - ?o

Building

Goal . Quality conformance

(%) >= 12 - ?o

Organization Scope

Organization Scope . Actors includes - -

Organization Goals

Organization Goal . Predicted . Cost (K$) - <= - ?o

Organization

Goal . Observed . Response

Latency (days) 3 <= - ?o

Organization

Goal . Predicted . Peak

Backlog (days) 3 <= - ?o

Organization

Goal . Predicted . rework

(FTE-days) - <= - ?o

Process

Process Goals

Process Goal . Peak Quality Risk < 0.50 - -

Process

Goal . Schedule Growth

(months) < - ?o

Process Goal . Completion Date <= 1/1/09 - ?o

Process Task . Action: Object

Process Task . Design: Actor Actor that designs

Process Task . Predict: Actor Actor that predicts

Process Task . Assess: Actor Actor that assesses

Process Task . Build: Actor Actor that builds

Function Product Behavior

Organization

Qualitative Threshhold values

Chalmers Integrated Product,

Organization and Process Design

Structural

Design Subteam

Project

Coordination Meeting

Architectural

Design Subteam

Design PM

Client PM

Project

Engineers

Construction

PM

Procurement

Subteam

Start

Long Lead Purchasing

Apply Exc Permit

Seek Zoning Variance

Provide GMP

Select Key Subs

Project Coordination

Estimate Cost

GMP

Accepted

Choose Construction Methods

Select Subconsultants

Finalize Arch

Program

Estimate Time

Define Scope

Choose facade materials

Choose Struct.

System

Design Coordination

Ready

to

Excavate

Page 11: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product,

Organization and Process Design

11

Multidisciplinary Design and Analysis – using VDC

Disciplines:

• Architecture

• Engineering

• Construction

• Operations

Stakeholders:

• Design – build

professionals

• Owner

• Others

Design

• Virtual

• Graphical

• Object-based

Analysis

• Model-based

when possible

• Quantitative

when possible

• Multi-

Stakeholder

• Graphical

description

Page 12: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 12

Integrated design and analysis Big Ideas

• Build VDC project models early and often, before committing large money or time

• What – Objectives, Designs and Behaviors of Product, process,

organization

• How: – Detailed: to show the product, process, organization entities that

use > 10% of project time, money

– Virtual: in the computer

– Visual: multi-discipline, multi-view, for multiple stakeholders

– Integrated: relating the product, organization and process

– Objective-based: set and track explicit public objectives

Page 13: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

13

Plus-Delta of Civil Engineering

• Provides fixed physical

assets and wealth

• High global demand for

infrastructure and

housing

• Opportunity to impact

global climate challenge

significantly

Page 14: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

14

Plus-Delta of Civil Engineering

• Provides fixed physical

assets and wealth

• High global demand for

infrastructure and

housing

• Opportunity to impact

global climate challenge

significantly

• Low productivity

compete with other ways

to spend $

• High energy use and

rising energy costs

• Structural reliability <<

societal need (Chile)

Persson, Sustainable City of

Tomorrow

Guilllermo Gomez, PUChile

US Department of Commerce,

compiled by P. Teicholz

Page 15: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

15

An example - Malmo, Sweden:

The best example of

sustainable development in

the world:

– Best design and analysis

methods (~2000)

– Best construction

methods

– Project provides some

good data on

performance vs.

predicted

But

• Energy: 20 of 20 buildings used more than predicted

– Prefabrication needed for intended energy performance

• Land: much greater density needed even for next project

– Development model did not last even a decade

• Data granularity: so coarse that improvement difficult to plan

• Human capital: people on project mostly lost to next phase

Page 16: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

16

An example - Malmo, Sweden:

Message: measure performance

The best example of

sustainable development in

the world:

– Best design and analysis

methods (~2000)

– Best construction

methods

– Project provides some

good data on

performance vs.

predicted

But

• Energy: 20 of 20 buildings used more than predicted

– Prefabrication needed for intended energy performance

• Land: much greater density needed even for next project

– Development model did not last even a decade

• Data granularity: so coarse that improvement difficult to plan

• Human capital: people on project mostly lost to next phase

Page 17: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

CEE 243 March 29 17

Malmo, Sweden: Actual energy

much worse than Predicted

Page 18: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

CEE 243 March 29 18

Malmo, Sweden: Actual energy

much worse than Predicted

Page 19: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Fundamental issue: outcome reliability

• Structures (Chile, post-earthquake) -- good:

– ~500K/~5M homes damaged or destroyed: <2σ

– ~4 joint failures /~100 in (collapsed) buildings: 2σ

– 4/~10,000 post-1985 buildings collapsed in major

damage area: >3σ

• Energy – not good:

– 20/20 buildings used more energy than predicted –

Malmo, Sweden, 2001 (range 70 – 340% greater)

– 121 LEED buildings use 30% more energy per

square foot than average for U.S. buildings

• Neither structure nor energy performance meets

societal needs

19

Page 20: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Fundamental issue: process reliability

• Structures (Chile, post-earthquake)

– ~4 joint failures /~100 in (collapsed) buildings: 2σ

• Sources of failure - infrequent but important problems:

quality of joint construction, material composition, soft story

design, asymmetrical designs

• Energy:

– ↑ prediction variability:

• ↑ Inter-tool with same designer

• ↑ Inter-consultant with same tool

– ↑ component performance variability, e.g., infiltration from

leaky building joints (Malmo)

• Structure and energy performance:

– Good (historically), but

– Neither meets societal needs need to manage risk

20

Page 21: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

21

AEC Breakthrough Objectives

Practice: 2002 Objective: 2015

Schedule 1-6 y Design

~1.5 y Construct

Variance 5-100%

1 y Design

< .5 y Construct

Variance < 5%

Cost Variance 5-30% Variance < 5%

Delivered quality Large Variance

Good?

Productivity impact?

0 variance, by POE

Great, by POE

++ productivity

Safety Good Better

Sustainability Poor 25% better than 2002

Globalization Some >= 50% of supply and

sales

Page 22: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

22

(Multiple) Predictable performance objectives:

*Changed in 2010

Controllable Process

[Conformance to plans]

Outcome

[Performance]

Product, organization,

process designs

Latency: mean <= 1; 95% within 2

working days

Safety: 0 lost hours

Coordination activity:

planned, explicit, public,

informed > 90%

Field-generated Requests for

Information: 0

Schedule: 95% on-time

performance

Facility managed

Scope: 100% of items

with > 2% of value, time,

cost or energy

Rework volume: 0 (for field

construction work); objective = 10-

20% (virtual work)

Cost: >= 95% of

budgeted items within 2%

of budgeted cost

Prediction basis: > 80%

of predictions founded

*Function (quality) conformance

(%): >= 99%

Delivered Scope: 100%

satisfaction

Design versions: 2 or

more >= 80%

Schedule conformance (%): >=

80%

*Sustainability: >75%

better energy, water,

materials, than 2002,

profitably

Staff trained in VDC: >=

4/project

Cost conformance (%): >= 95%

Page 23: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 23

Wasted human, technical, and biological resources

Photos: Courtesy SPS

Source: http://mainegov-

images.informe.org/spo/recycle/focus/midmaine/landfill.jpg

Page 24: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

VDC models use and require lots of tools

• Learning use of these tools beyond scope of this

class

9 July 2013 24 Chalmers Integrated Product, Organization and Process Design

Organization

Project specifications Revit

Bentley

Architecture

Tekla

Structures VDT MSP P6 POP MACDADI

Product functional objectives (goals) yes yes

Product systems and components scope yes yes some names

Product behavior specification and values yes yes

Organization functional objectives (goals) yes yes

Organization responsibility for components, systems

& tasks yes

Organization scope yes names names

Organization behavior specification and values yes yes

Process Task functional objectives (scope) yes yes

Process Task scope yes yes yes names

Process behavior specification and values yes yes

Project goals and assessed goodness yes yes

Project options yes

Project preferences, qualitative threshold values yes

Product Process Integrated project

Models

Page 25: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 26

Integrated design and analysis – using VDC –

provides

Integrating theoretical framework to

• Describe functional intent and designs

• Describe and predict engineering behaviors

• Systematically manage projects and the

business using the predictions and observed

data, to

• Achieve measurable business objectives

• Address reliability

Page 26: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

VDC model content: VDC templates help make managerial levers visible to all

9 July 2013 Chalmers Integrated Product, Organization and Process Design 27

• Elements of a project that can and must be managed:

– Product

– Organization

– Process (design + construction)

• Views of each element that can and must be managed – Functional intent

• Program Function, Schedule, Cost, Sustainability, ….

– Form (Scope) -- design choices for project elements

• Physical, organizational, process task elements

– Behaviors (predicted, observed)

• Quality (Functional performance), Cost, Schedule, Safety

Page 27: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 28

In-class exercise - Tuesday

For a new-generation smart phone app, sketch and define:

• Product

– Functions: product design intent, to include

• Functions

• User interface (UI)

• Additional services

– Design forms: designed scope, e.g., buttons, …

– Behaviors: observable (or estimated) performance, e.g., # designed buttons = # actual = 3

• Organization: teams to design, build, test

• Process: tasks to design, build, test

Page 28: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 29

In-class exercise - Tuesday

Deliverables: • Sketches: product, organization, process

• Templates (you create them):

– Deliverables

– Metrics and Assessed performance

– Controllable factors

– Risks and Next Steps

Process:

• Groups of ~4

• 20 minutes for ICE session x 2

• 10 minutes for presentations, discussion after each session

• Lunch break between sessions

Page 29: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 30

Submission-1: Homework for this week

Deliverables:

• Sketches: product, organization, process

• Templates:

– Deliverables

Planned

deliverables

Deliverable

format

Responsible

team,

individuals

Receiving

teamDue date

Due date

met

(Yes/No)?

Expected

LODComments

BIM per spec BIMEach

individualclass today Yes per spec

BIM

conformance

check

Excel

spreadsheetClass partner class today Yes per spec

Room

schedule

Excel

spreadsheet

Each

individualclass today Yes per spec

Window and

door schedule

Excel

spreadsheet

Each

individualclass today No per spec

4D animationMovie in .avi

format

Each

individualclass today Yes per spec

Comments on

4D

Annotations

on BIM

Each

individualclass today Yes

per your

judgment

Lab Deliverables

Page 30: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 31

Submission-1: Homework for this week

Deliverables:

• Sketches: product, organization, process

• Templates:

– Deliverables

– Metrics and Assessed performance

Prediction

Name CommentTarget

valueTolerance: +-∆

How to use in

managementSource of data

Type [P,

O]

Stakeholders

who saw data

last week

Collection

frequency Objective Weight

Predicted/

measured

value (how

you are doing)

Assesed

value

MQuality: POE satisfaction wrt

program (%)100 5

Guide

commissioning, next

job

Client

assessmentO Owner only

Turnover time

+ 6-24 months40 86 1

ECost conformance to plan (item

actual - predicted/predicted)100 5 Plan next job

Client

assessmentO PM only Turnover time 25 98 3

T Schedule conformance to plan (%) 100 10 Plan next jobClient

assessmentO All on team Turnover time 35 ? NA

RPredicted Cost conformance to plan

(item actual - predicted/predicted)100 5

Attention

management

Periodic project

progress reportP Subteam only Weekly 15 99 3

IProduction schedule conformance to

plan (%)90 10

Attention

management

Periodic project

progress reportP Owner only Weekly 10 75 2

Metrics

Intent Evaluation

Page 31: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 32

Submission-1: Homework for this week

Deliverables:

• Sketches: product, organization, process

• Templates:

– Deliverables

– Metrics and Assessed performance

– Controllable factors

Factor Type Factor Range of options Constraints Action(s) for this week

Action Taken?

(Yes, Partial,

No)

Product Detail of water line in 3DFeatures of size from 1 mm to >

1mNone important Model features size > 20 mm

Product Location of in-water equipmentAdjust both equipment location,

water width/depth profile Size of equipment model equipment located in water this week

Organization Number of BIM authors <1 – many FTEsAdjust author count up and down

slowlyBudget BIM author work

Organization Number of BIM reviewers Author team – hundreds Size of BIM review facility Budget BIM reviewer work

Process Construction duration 6 months to 2 yearsNeed to plan prefabrication early

to shorten construction periodGet owner preference

Process Size of weekly pre-con tasksOne task for whole team/week to

all tasks with > 0.5 FTE-day

Availability of staff to plan,

manage schedule

Build short-interval production plan and

schedule at feasible LOD

Controllable Factors

Page 32: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 33

Submission-1: Homework for this week

Deliverables:

• Sketches: product, organization, process

• Templates:

– Deliverables

– Metrics and Assessed performance

– Controllable factors

– Risks and Next Steps

Identified risk

Potential

impact of risk

($, time,

effort)

Severity:

Low,

Medium,

High

Parties

affected by

risk

Individuals

responsible for

mitigating

design,

approval

Earliest

analysis/ last

responsible

moment dates

Mitigation

activity

Resolution

date met

(Yes/No)?

Comments

BIM ready

partner teams

available

Dramatic

schedule High

Client Early partner

relationship

team

Day-1/ end of

concept phase

BIM

training for

partner

staff

Best to set

expectat-ions

early

Sea level rise

Costs/

curtailed

operations

Medium OperationsConcept

design team

Day-1/ end of

ConceptDikes 100-year risk

Goverment

plan OK

Delay open

dayMedium Operations Core group

Day-1/

facility open

Engage

government

review

Ongoing risk

Paint spec

unclear or

inappropriate

Cost: use

contingency;

schedule delay

LowClient Core group

Day-1/

facility open

Vet across

different

examples

Risks - Example

Personal goal

or objectiveAction (what you plan)

Process (how you will do the

work)

Frequency (how often

you will do the work)

Next week

Next quarter

Next year

Group goal or

objective

Next week

Next quarter

Next year

Next Steps

Page 33: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Tuesday afternoon

• ICE session: project definition using

templates

• SimVision lab (continued Thursday)

• Introduction to Big Data; SEE It Lab

9 July 2013 Chalmers Integrated Product, Organization and Process Design 34

Page 34: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 36

Business uses of VDC template models

• At a glance, identify: – Most important (e.g., top-10) Functions and Scope (Forms)

of the Product, Organization, Process?

– Metrics to measure; current predicted behaviors?

• Identify product, organization and process elements with greatest risk.

• For the most important or highest risks, check that: – Product forms have associated actors and tasks with risks

that compound or mitigate the product element risk;

– Organization actors have associated forms and tasks with risks that compound or mitigate the actor risk;

– Process tasks have associated actors and product forms that mitigate the product element risk, not compound it.

• Evaluate goodness of design re objectives, alternatives; compare with other designs

Page 35: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product,

Organization and Process Design

37

Class overview: http://www.stanford.edu/~kunz/Chalmers/

Page 36: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 38

Course Goals

• Use the method of Integrated Concurrent Engineering (ICE);

• Build and interpret simple descriptive models of the Product,

Organization and Process (POP) of projects using Excel-based

templates;

• Build and interpret organization and process models using the

SimVision tool;

• Experience use of "big data" – access and interpret the status of large

volumes of operational energy system data;

• Create checklists to assure initial readiness for and final

completeness of tasks that high uncertainty and for which the

knowledge required exceeds that of any individual;

• Create a business plan to obtain significant funding for an enterprise

of personal interest.

Page 37: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 39

Course Non-goals

• Study every system ever built

• Study every visualization/AI/design/planning

technology

• Development expertise

• Preparation for technology research

• Survey understanding only

• Excessive work

Page 38: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Course organization

• Instructor:

– John Kunz ([email protected])

• Office Hours: after class, and anytime my office door is

open

• Class Schedule: 11:10 - 12:30 and 1:30 to 4:00 on Tuesdays

and Thursdays

• Classes will meet in the CIFE lab, Room 292, Y2E2, Please

work in groups of about three for ICE sessions and to prepare

submissions. Please read and take assessments on your own.

• Web site: http://www.stanford.edu/~kunz/Chalmers

9 July 2013 Chalmers Integrated Product, Organization and Process Design 40

Page 39: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Details

• Lab login id: su\CEE242

• Password: orgdes242

• Dinner in Palo Alto:

Thursday July 18 or 25?

• Apps for your laptop:

9 July 2013 Chalmers Integrated Product, Organization and Process Design 41

Page 40: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

ORID +/∆ Analysis

9 July 2013 Chalmers Integrated Product, Organization and Process Design 42

Level of Questions

Purpose Questions to Answer

O Objective

Level

To examine the data

To identify factual information

What do you see?

What factual statements can you make based on the data?

R Reflective

Level

To encourage connections

To encourage free flow of ideas and imagination

What surprised you?

What encouraged you?

What discouraged you?

How does this make you feel?

I Interpretive

Level

To identify patterns and determine their significance or meaning

To articulate underlying insights

What does the data tell us? What are insights for you?

What is the good news?

What are limits? What else is there to learn?

D Decisional

Level

To propose next steps

To develop an action plan

To make decisions

To experience “coming together”

What are next steps?

What decisions can we make?

What is our action plan for moving forward?

Page 41: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

ORID +/∆: Focused Conversation and Analysis

Objective

What do you

recall seeing?

Reflective

Positive

What do you

feel positive

about?

Reflective

Negative

What do you

find negative?

Interpretive

What sense do

you make of it?

Decisional

What

agreements

can be made

now?

(c) 2010 43

Page 42: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Tuesday afternoon

Page 43: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01
Page 44: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01
Page 45: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01
Page 46: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Student-mentioned important content from day-1

(JK perspective)

Integrated concurrent engineering (ICE)

9 July 2013 48 Chalmers Integrated Product, Organization and Process Design

Page 47: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Un-mentioned important content from day-1

(JK perspective)

Familiarity with the integrated POP project framework of VDC

• Product – Organization – Process (POP)

• Function – Form – Behavior (FFB)

• Perspectives that a project can and must manage

Page 48: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01
Page 49: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Reflections - Thursday

51

Page 50: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Details

• Career planner July 18 – OK

• Dinner at our home: July 25 or 18?

• Submission-1

9 July 2013 52 Chalmers Integrated Product, Organization and Process Design

Page 51: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 53

Product design forms: 3D drawing

Page 52: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 54

Product design forms: Object-Oriented 3D BIM

Modeled objects:

• Walls

• Floors

• Windows

• Doors

• Columns

Page 53: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 55

Organization, Process Models

Model (SV)

• Organization

• (Design) work process

Simulation behavior

predictions:

• Gantt chart

• Risks

Structural

Design Subteam

Project

Coordination Meeting

Architectural

Design Subteam

Design PM

Client PM

Project

Engineers

Construction

PM

Procurement

Subteam

Start

Long Lead Purchasing

Apply Exc Permit

Seek Zoning Variance

Provide GMP

Select Key Subs

Project Coordination

Estimate Cost

GMP

Accepted

Choose Construction Methods

Select Subconsultants

Finalize Arch

Program

Estimate Time

Define Scope

Choose facade materials

Choose Struct.

System

Design Coordination

Ready

to

Excavate

Page 54: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 56

Integrated Concurrent Engineering (ICE)

Given

• Objective = “extreme collaboration”

(1 week)

• Excellent POP software

• Collocated team

• iRoom

• Good generic POP model

• SD (DD) phase

Performance change

XC

Good

traditio

nal

Latency

(secs)0

20000

40000

60000

Latency (secs)

Duration (days)

XC

Good traditional

0

50

100

150

200

250

300

Duration

Page 55: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Templates and checklists

Templates: standard

representations

• POP model: Function,

Form, Behavior of P, O, P

• Breakdown structures:

– Product

– Organization

– Process

• Task content: object,

action, resources (crew,

equipment)

Checklists: Tasks and OK

that was done well

• Run ICE sessions

• Create POP models

• Process to define project,

build BIM, exchange

data, do analyses (x5)

9 July 2013 Chalmers Integrated Product, Organization and Process Design 57

Page 56: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Example Checklist Step in detailed

schedule Checks to make

before start of step

Necessity for success: “monitor and challenge”

Page 57: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Templates

9 July 2013 Chalmers Integrated Product, Organization and Process Design 59

Templates Examples0. Project summary - background

Background

Included 1. Specifification of intent - wants

BIM Uses Example

Deliverables Example Lab Deliverables

BIM content specification Example Lab Spec

Coordination Commitments

ICE session pre-plan Example

Metrics - Client intent and project objectives Example BIM Lab metrics

Controllable factors ExampleOperations Agreement Example

Team Charter

Application of VDC

2. Models of project design content - dos

Personal BIM - snapshot Example

Personal organization design - snapshot

Task Commitments - production plan Example

Design versions

3. Predicted and measured project performance

– attributesPersonal BIM-based analysis - snapshot Example

Personal metrics - graph Example

4. Evaluated project performance – gotsAssessed performance Example

Risks Example

Assessed VDC status Example

VDC Methods Application Assessment

Comments

5. Planned next steps

Next Steps

Force Field

Last updated 7/3/2013

Page 58: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Big data

• SEE IT: extract energy use data for this building from Building

Management System (BMS)

• ~750,000 points – this room

• How do you interpret these data?

9 July 2013 60 Chalmers Integrated Product, Organization and Process Design

Page 59: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Big data

• SEE IT: extract energy use data for this building from Building

Management System (BMS)

• ~750,000 points – this room

• How do you interpret these data?

9 July 2013 61 Chalmers Integrated Product, Organization and Process Design

Page 60: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 62

How we spend time in meetings

DESCRIPTIVE (40%)

• When do we have access to

Area C?

• What wall sections do these

numbers refer to?

• Where are you placing the

crane?

EXPLANATIVE

(20%)

What drives the finish

times for the rides?

PREDICTIVE (10%)

Can we get access to the

lagoon a week earlier?

EVALUATIVE (30%)

Does this milestone

meet contract?

Page 61: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Submission-1: due midnight July 12 (Friday)

Task: describe and analyze your project and organization

design for a pre-defined test case

Submit:

• Template file (group submission)

• ORID analysis on what you learned this week

9 July 2013 Chalmers Integrated Product, Organization and Process Design 63

Page 62: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Chalmers Integrated Product, Organization and Process Design

64

Skills for success

• Good engineer: design, analyze, manage

• Research methods

• Communication

– Written/Oral

– Programming

– Colleagues, sponsors, stakeholders

• Integrated use of quick-response, careful

analysis, reflection

Page 63: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product,

Organization and Process Design

65

Speculations: VDC

Symbolic Model • Objectives • Testing • Representation • Reasoning • User Interfaces • Systems Interfaces

Pro

ject P

hase

Discipline

VDC will enable a small number of collaborating stakeholders

to do rapid Multidisciplinary Design and Analysis

Page 64: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 66

Learning goals

• Get basic familiarity with the POP project framework of

VDC

• Product – Organization – Process (POP)

• Function – Form – Behavior (FFB)

• Understand class organization, opportunities, methods

and expectations

• Motivate interest in Integrated Design enabled by

VDC:

• Opportunities in practice

• Fun, power and job opportunities of models, model-

based analyses

Page 65: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product, Organization and Process Design 67

2013?, … 2015?

2013?, … 2015?

What do you have? … What do you want?

Page 66: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

9 July 2013 Chalmers Integrated Product,

Organization and Process Design

68

This week overview

Day Take-home

Tuesday Introduction:

Theory: ICE, organizational modeling, big data,

templates, VDC POP/FFB framework, types of models

Practice: ICE session with Templates, Organization-

process model and analysis (SimVision) lab

Thursday Theory: Introduction to big data

Practice: Organization-process model and analysis

(SimVision), continued, and big data (SEE-IT) labs

Page 67: Integrated Product, Organization and Process designweb.stanford.edu/~kunz/Chalmers/W12013V3.pdfModels Interface • Physical • Statistical • Mathematical Symbolic Graphic - *05-07-01

Integrated Product, Organization and Process

design

John Kunz

The big idea: Integrated Product, Organization and Process design can support, at least design, fabrication and assembly

Rate

Baseline

($K) Change

Year-1

(K$)

Revenue 100,000 2% 102,000

Cost of contracted work 85% 85,000 -2.0% 84,660

Cost of self-performed work 10% 10,000 2.0% 12,240

Gross Margin 5,000 5,100

Sales, G&A 2% 2,000 2,040

IT investment 70

Amortized costs of IT/yr 33% 23

Net income 3,000 3,037

Time to payback (years) 1.9

Net Income change (%) 1.2

*05-07-01

Finish

Final Program

Confirmation with

Pharmacology

Final Program

confirmation with LAR

KPFF

SRG Lab Task 37 Task 44 Project Mgt AEI Core Task 41 Task26 H Block Crew Task 23SRG / AEI

TechnicalAEI Core and

SRG LabHDCCO Costing

SRG

TechnicalKPFF

AEI Core

and TechHDCCO Core

Code Rev

ConsultantSolvent Tarter

H Block Crew

& Tech

SRG

Landscape

Tele Data

DesignCode Rev

Furniture

37.

*Reprogram

B#15 Shafts

34. *Finalize

Pharmacology

Program

33. *Finalize

LAR Program

32. *Finalize

Bio-Organic

Chemistry

Program

35. *Finalize

Protein Chemistry

Program 20. *Determine Scope of

package D including vivarium

changes

45. *Complete all

Basement/LAR Drawings

41. *Reprogram

bookends B#13 and

B#15

36. *Analyze

structural impacts

12. *Complete UG

utiliites

25. *Do Central Plant

design changes

19. *Determine vertical

utilities

22. *Complete catwalk drawings

52. Finalize landscape

26. *Finalize B#13 and

B#15

Exiting/architecural H

occupancy concept

*Lab and

vivarium

Programming

Complete

27. *Finalize B#13,

15 Shaft Size &

MEP Room

Locations

31.* AEI &

SRG

Determine

Design $/Time

Impact of

Change

23. *Reprogram

B#13 and B#15

Exterior Architecture

Bookend

Programming

Accepted by Genentech

Notice to proceed on

structural changes

Architect

program/MEP

oncepts

Established

By Design

Team

29. *Document

lab plan

1. *Redesign main MEP

distribution systems

SRG Management AEI Management

Genentech PM

SRG Lab Plan

Ken Mouchka

Task 27Task 38

Organization

5. *Finalize lab & Equipment

plans

Task 29

Task 28

30. *Approve

Change to

Design

Contract

21. *Prepare Plan Views for

Review of Concept w/City

39. *Finalize MEP

distribution and

section

Task4 Task22

Review 80%

documents

48. *Develop exiting

plan

49. Develop

reflected ceiling

plan

Turnover

reflected

ceiling plan to

AEI

Detailed Design 80 PC

Complete

3. Complete Tele Data Design

42. *Develop

Execution

Strategy

44. *Complete

B#14 Officing

Planning

18. *Detailed Lab

Program

Documentation

47. *Develop lab

DD plan

28. *Determine

segregation of lab

and tech space

G accept lab

equipment matrix

*Package B structural

modifications (CCD3A)

13. *Code Consultants

Review Concept for final

city Presentation

14. *HDCCO update Estimate of cost

of Program

Review skin changes w/db team

Lab Planning Program

Meetings with

Pharmacology

Lab planning Program Meeting with Protein

Chemistry

BMS Controls Meetings

(Weekly)

Lab Planning Program meeting with Bio

Organic 80% Drawing Review

Tele Data Coordination MeetingsSteel Detailing

Meetings

Genentech 80% Detailed Design

Review

Final Program

Confirmation with Officing

Weekly

Coordination

Meeting

Lab Planning Program

Meetings with Directors

50. Designate size, location of

13 MEP, teledata rooms

54. KPFF design

stairs for 13/1438. *SRG

Reprogram 13/14

interface, exiting,

stairs

43. *Changes in Steel

Forwarded to Steel

Detailers

46. *RA Furnture

Concept Complete

MEP, Teledata room design

*Design Budget &

Schedule for Changes

Approved

*Notice to proceed

with detailed design

24. *Complete B13,4 H

block occupancy

requirements on MEP

systems

17. *Risick

reprogram solvent

distribution and waste

Issue 80%

MEP CDs

(20) Incorporate

80% MEP review

comments

(19) Genentech review

80% drawings

53. Incorporate

comments, complete

Architectural detail

2. Initial redesign MEP branch

lateral distribution

G accept

13/14

Interface

*City Accept

exiting

*Package C

skin

modifications

55. KPFF design

stairs for 15/14

40. *SRG

Reprogram 15/14

interface, exiting,

stairs

B13 MEP HVAC,

conduit, piping mains

completed

MEP 80% Review

comments

incorporated

Package D and UG

addendum issued:

underground utilities,

vivarium catwalk

10. Draft Alternate means

15. Jeff reprogram HMIS

(3) *AEI design MEP

HVAC, Conduit &

piping mains B13

16. *HDCCO Determine

Schedule Impact

City Approval of

Alternate Means

for Program

8. Review Alternate

Means w/impact on LEL

and LFFH

(21-4) Finalize MEP Details,

update specs and p&ID's

(8) *Revise

MEP loads, MEP

Equipment

schedules

finalized

(13,15,16) MEP specs, P&ID's,

control sequences

Work Process

Meetings

(6) Coord B13 MEP

floor section

4. complete all Interior Architcture

*Cal OSHA Recommend

Determination of LFFH

51. Designate size, location

of 14 MEP, teledata rooms G accept

15/14

Interface

*Accept project

scope:budget

by Genentech

*City Approval of

H Concept

*Exterior

Programming

Accepted by Genentech

*Turnover lab and

vivarium DD plan

to AEI