PBS+WBS+020511

PBS+WBS+020511 - Project Information Management and...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Project Information Management and Organization: How to organize scope, schedule, resource, and cost information Product Breakdown Structure Work Breakdown Structure Organization Breakdown Structure Cost Breakdown Structure CEE100, May 2, 2011
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Projects are characterized by their product , organization , and process and their respective functions, forms, and behaviors Product Organization Process Function Form Behavior
Background image of page 2
Examples from Bay Street Project Bay Street Project Information Courtesy of DPR Construction, Inc., Redwood City, CA Artist Rendering of Part of Bay Street Project 3D Model of Part of Bay Street Project Parking Structure The concepts in this presentation are illustrated with examples from the Bay Street Project in Emeryville, CA.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
•PL1: Project – PL2: Buildings / Major Project Elements •PL3: Systems – PL4: Components »PL5: Parts Product Breakdown Structure (PBS) Product Breakdown Structures organize the information about a building or facility (Product-Form) in several levels of detail.
Background image of page 4
Bay Street PBS Example •PL1: Bay Street Project – PL2: Parking Structure •PL3: Structural System – PL4: Wall 1 »PL5: Rebar for Wall 1
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
• PL1: Project – PL2: Buildings / Major Project Elements •PL3: Systems – PL4: Components » PL5: Parts Product Breakdown Structure A PBS represents the scope of project from the designer and owner perspective. It can be organized and coded according to the 12-category Uniformat. The levels of detail relate to the major design phases: PL1: Feasibility Studies -> link to owner’s business case PL2: Conceptual Design -> decisions about major project elements PL3: Schematic Design -> decisions about systems, layout PL4: Design Development -> decisions about component types and dimensions PL5: Detailed Design, Construction Documents, Shop Drawings -> decisions about specific parts } 2D, 3D CAD, Specifications 2D CAD (some 3D for fabrication)
Background image of page 6
Uniformat-based organization for project scope linked to cost (Source: Means Building Cost Estimating)
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This project did not use a formal, shared product breakdown structure
Background image of page 8
WL1: Construction project • WL2: Construction areas WL3: Sub-areas • WL4: Building units / Disciplines – WL5: Master Schedule Activities » WL6: Objects WL7: Operations At each level of detail, the WBS lists all the activities required for the project. On WL5, these activities become the basis for the project’s Master Schedule (WL5) that establishes the contractual milestones. It is typically managed by the general contractor and is usually summarized for the interface with the owner and elaborated into more detail for the interface with subcontractors and vendors. } WL1-3:
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 28

PBS+WBS+020511 - Project Information Management and...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online