BIM Implementation in a Lean Operating System

3,014 views
2,775 views

Published on

Presentation given at the June 2010 National BIMForum in Kansas City, MO (Co-presented with Jan Reinhardt, Adept Project Delivery). This presentation describes the implementation and use of BIM/VDC tools and processes within a Lean Operating System, primarily from the perspective of the Construction Manager. This approach to implementation results in the sustainable use of BIM/VDC tools and processes, supported by all project participants.

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,014
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • (Jan’s slide)
  • (South’s slide)Motivation: “Why”Lean Principles: “What”Get through this part rather quickly… we’ll start with the definition of Lean and echo what you’ve heard from Dennis and othersThen Jan and I will discuss some Lean principles that will show up in the next portion of our material.We know that, here, you’ll be hearing material you’ve already heard – that’s intentional – we’d like you to hear some of these concepts several times from different perspectiveso they’ll sink inImplementation: “How”Spend the bulk of our time here… The “Application” portion – we’ll discuss the implementation of BIM tools in a Lean Operating SystemConclusion: Tie our materialtogether with a few closing thoughts. We’ll finish our session with time for Take Aways and Questions
  • (Jan’s slide)
  • (South’s slide)Challenge / Question: How will the team use BIM tools?Scenario 1: “Add-on” to an existing process – not being used as the effective tool that it is. “BIM off the shelf” – BIM for marketing / so we can “check the box” in RFPs / RFQsScenario 2: In the context of Lean system, BIM is implemented to support lean operation. tools are used in a creative way to refine, augment and further develop process… or change it all togetherLean a guide for Designing Processes?  Lean MUST!!! be used for designing processes – not just for construction, but for design, for the entire project delivery! NEXT SLIDE(Times are changing – yes, use Lean approach for D-B-B, D/B and IPD, but know that lines are being blurred between Design and Construction – The only way to adjust is through Lean Op Sys)
  • (Jan’s slide)
  • (South’s slide)Motivated by desire to determine connections… their significance, and where the value moves from ONE action, concept or component to the next(slide fades from chaotic mind map to value stream)Then… we map that value stream.. We’ll talk a bit more about that laterObviously – we won’t address every connection – this is a start; this is a part of our motivation, the “why” behind the material you’re seeing hereFinally, before we move forward:*** Learner vs Knower*** Trade Contractor vs Sub Contractor
  • (South’s slide)A Means Of Operation L O S-----------------l Philosophy l Add Elimination l & l  Value  of l Principles l Waste----------------- l results l Reliable Flow & Consistent Resultselimination of wasteful processes and operations to
  • (South’s slide)Back track through concepts to define “Lean” again
  • (South’s slide)I won’t read these – you can skim the list and examples. The most common one, though, is the rework….Like the way waste is defined categorically:** Muda – work/effort that is unproductive, that simply is not necessary for adding value** Mura – Unevenness / inconsistency ** Muri – results from work that is not standardizedDefine types of Waste; use clear examples (Rework: “Have you ever seen a sleeve misplaced?”)
  • (South’s slide)
  • (South’s slide)*** One Piece Flow:One piece of work, moving from one stage to the next. One Piece Flow not as easy to comprehend as it may sound – Conceptually, “Easy” – In practice, takes serious consideration to connect to daily job functions*** Visual Control: This IS as easy as it sounds – but so easy that we can miss significance. What looks simplistic and silly, is actually exactly what we need to optimize the flow of our work
  • (Jan’s slide)
  • (Jan’s slide)
  • (Jan’s slide)
  • (Jan & South slide)Multiple disciplines involved / engaged: This applies to Communication and Human Interaction as well… 5 minutes of the Architect’s eyes on an issue with the builder WILL save 5 hours one month down the line
  • (South’s slide)Kicking off new project – establishing process for coordination and collaboration – this project is a complex MOB, connected to a patient tower, supported by services connecting through the adjacent tower; it has an ambulatory surgery center (with unique support requirements); and design is evolving (yes, we’re building this from DD drawings with a well defined GMP)Therefore, we really need a sound approach to this challengeHistory/Context; Current Conditions/Issues; Goals/Targets; Root Cause Analysis; Counter measures / Plan of Action; Follow-up / Controls (Accountability & Application of metrics); Timeline – When???Countermeasures / plan of action refers to (1) feed back cycle, (2) general spatial coordination guidelines, (3) weekly schedule for file sharing, meeting and coordination; the material in this document is supported by several value streams that indicate process flow – there is a significant amount of information, process, procedure and expectation condensed into this document – this summarizes our collaborative effort, this is out reference and our North starPrinciples: Deliberate Decision Making (significant research & engaging all stakeholders); fast & decisive implementation; continuous improvement
  • (Jan’s slide)
  • (Jan’s slide)Comments on appropriate “Content” vs. correct process/accuracy created to utilize the model
  • (Jan’s slide)Misaligned “level of detail” to “level of definition” (here, valves are modeled, but stub-up is totally in the wrong place)
  • (South slide)We use this tool as a visual control to COMMUNICATE – For example: trade contractors are now empowered like never before to communicate issues and solutions upstream and down stream: The CM and the Mechanical Contractor are able to identify, illustrate and explain their concern rather than just communicating verbally or through written word (which isn’t always great) – able to do this VERY FAST – in time to actually save cost and scheduleThis model ends up in the field – whether it’s RFIDs or a print of the 3D electrical room that’s getting panels installed this week, VALUE is Added
  • (South’s slide)Breakdown of the model / we see this in the File Naming Convention  Speaks to how “WORK” is broken up In this case, per building, per floor, per area, per trade, per systemAble to understand, visualize, and discuss our work in manageable pieces This is a formalized process, with buy-in from team members; this convention allows data to be identified, stored, accessed and discussed with Minimal Support (e.g. we don’t need to WAIT for someone to tell us the significance of a particular file – it’s all in the file name)One-Piece-Flow  process “work” in well defined, manageable piecesReliable  we know what we’re getting (and it’s very simple orgaization) Just in Time  not waiting for the Entire set data to be completed, each piece is completed one at a time, base on requirements of schedule
  • (Jan’s slide)
  • (South’s slide)Define “What” - Define “How” Be willing to Fix the Constraint (rather than apply a “work around”)
  • (South’s slide)Clash Avoidance vs. Clash DetectionLet’s Focus on the “Coordination Meeting” Meetings:Class Room StyleFocus on the problemLaser pointersInvolve and enable your peopleSmartBoardsVisual ControlInvolvement of the extended networkMake deliberate decisions
  • (South’s slide)Document Issues (Clash Reports)  effective documentation = issues cannot be ignored, actionable items WILL be addressedBECAUSE “Peer pressure is a free tool” learned early in life – every participant is aware of everyone else’s contributions, successes and failures Meetings:Class Room StyleFocus on the problemLaser pointersInvolve and enable your peopleSmartBoardsVisual ControlInvolvement of the extended networkMake deliberate decisions
  • (Jan’s slide)Description of Clash Report as: visual control, redundant check, continuous improvement, one piece flow, stop to fix problems
  • (Jan’s slide)(Lean concepts in red)
  • (South’s slide)The place where we get our information – where files are shared, stored and retrieved – this should also serve as the archive for all of our work (we want to be able to define when, why and how a decisions was made at any given point in the past  continuous learning)This file storage and organization is tied directly to the Breakout of the Model and the File Naming Conventions – the organization “fits” these files, the whole system “fits” how we use these files… we would say that the FIT is perfect, but the File Sharing Platform is constantly “learning” (we’re constantly finding the refinement, the optimization that brings it to the next level of usefulness) Transparency – sets course for a sort of “auto-correction” – this recalls the discussion about “drive” – what drives us? We want to have purpose; for most of us, there is purpose behind the quality of our work – in a transparent environment, our purpose is front and center, our drive is allowed to push us in the right direction
  • Jan
  • (South’s slide)Compare implementation of BIM tools on two similar projects (Cook North Tower and Cook MOB)Project A: No significant “buy-in” from external coordinator; Poor pulse on needs of project (pull) – lack of project knowledge/familiarity – results in possible implementation of non-value adding actions/stepsProject B: Buy-in from team “Internal” coordinator is project’s PE and/or Eng - have significant project and people knowledge – Heavily engaged in project details/intricacies and deep in relationships with stakeholders (architects, engineers, trade contractors, owner’s rep); Excellent pulse of project needs, expectations, etc. – understand “feelings” of participants (who’s stretched too thin, who has capacity, who’s struggling, who’s succeeding) and much better positioned to react accordinglyNOTE Significant growth from Project A to Project B, Lessons Learned
  • (South’s slide)
  • BIM Implementation in a Lean Operating System

    1. 1. BIM in the Lean Operating System<br />South Cole<br />Jan Reinhardt<br />1<br />Linbeck<br />ADEPT Project Delivery<br />scole@linbeck.com<br />jan.reinhardt@adeptpd.com <br />
    2. 2. Outline<br />Motivation<br />Lean Principles<br />Implementation of BIM in a <br /> Lean Operating System<br />Conclusion<br />2<br />
    3. 3. Motivation – context<br />Adoption of BIM<br />Experimentation with processes around BIM<br />Challenges in BIM<br />Size of models<br />Management of the BIM process<br />Accuracy of information<br />Level of completeness of information<br />Current information<br />3<br />
    4. 4. Motivation – How will the team use BIM tools?<br />Team performance in BIM implementation<br />Scenario 1:<br />BIM is used merely as a substitution for a drawing<br />The traditional process is being followed<br />Scenario 2:<br />BIM tools are used in a creative way to improve the current process in support of Lean<br />Can Lean be a guide for “designing processes”?<br />4<br />
    5. 5. Motivation – Opportunity<br />Reference: The Toyota Way (J. K. Liker)<br />BIM facilitates “definition” (vs. vagueness) in the construction process<br />Principles from lean manufacturing become more and more applicable to the construction process<br />5<br />
    6. 6. Motivation – Connection<br />Response to the Question:<br /> “How is this all connected”<br />6<br /> BIM<br />Vision<br /> IPD Lean Architect<br /> A3 Engineer Value <br /> Owner<br /> Flow Last Planner<br /> Builder<br /> Process Level of Detail <br />End Goal<br /> Scope<br />
    7. 7. What is Lean?<br />A Means of Operation:<br />7<br />Lean Operating System <br />The Lean Operating System (LOS) is founded on a philosophy and set of principles that add value by creating reliability and producing consistent results in the day-to-day running of organizations and in the delivery of construction projects. Elimination of wasteful processes and operations results.<br />
    8. 8. What is Lean?<br />What is Waste?<br />Any Process or Action that does not add Value<br />8<br /><ul><li>What is Value?
    9. 9. What the customer needs at the end of the Process</li></ul>External<br />Internal<br />
    10. 10. What is Lean?<br />9<br />WASTE<br /><ul><li>Defects in products:Rework, Field orders & Punch Lists
    11. 11. Overproduction:Fabricating material or ordering it too soon, JIC thinking
    12. 12. Inventory:Material stored at site or yard, work in process, unused tools & parts, forms and stashes
    13. 13. Unnecessary processing: unnecessary reporting, any non-value added steps
    14. 14. Unnecessary movement of people:Treasure hunts, looking for files, poor layout of work area (ergonomics)
    15. 15. Transport of goods: moving material; unnecessary hand-off work
    16. 16. Waiting:waiting for equipment, plans, info, orders, or material</li></li></ul><li>The right process will produce the right results<br />Continuously experiment and improve the process<br />Define Value, Map Value Stream<br />Engages stakeholders<br />Use pull driven approach<br />Define what is needed<br />Create what is defined<br />Not more<br />Execute flawlessly<br />Lean Principles<br />10<br />
    17. 17. Lean Principles<br />One Piece Flow<br />Small batches, minimal inventory<br />Visual Control<br />Visually Indicates Issue / Status<br />11<br />Normal Operation<br />We will stop in less than one hour<br />Work Stopped<br />
    18. 18. Lean Principles <br />Just in time<br />No inventory<br />Correct sequence<br />Stop the process to fix problems immediately<br />It is okay to stop the process for the right reasons<br />No short cuts<br />12<br />
    19. 19. Lean Principles<br />Standardize work processes<br />Increase reliability<br />Increase efficiency<br />Use reliable, tested technology<br />Deliberate decision making, fast and decisive implementation<br />13<br />
    20. 20. Lean Principles<br />Minimize movement<br />Movement of material does not create value<br />Steps in process to create “buildable” design<br />Engage the extended network of collaborators<br />Leverage expertise<br />Create buy-in<br />Enable and develop your people<br />14<br />
    21. 21. Lean Principles<br />Redundant checks<br />Measure twice, cut once<br />Be aware of the costs of re-work<br />Multiple Disciplines involved / engaged<br />15<br />
    22. 22. Process Development & Deployment<br />A3, Planning/Research, Interviewing Stakeholders<br />Deliberate Decision Making (research & stakeholders), fast & decisive implementation<br />16<br />Implementation of BIM in the LOS<br />
    23. 23. Implementation of BIM in the LOS<br />Characteristics of models<br />Structure<br />Content<br />Level of Detail<br />Accuracy<br />Status of the model (current or old)<br />Who created it for what purpose<br />File Formats<br />Reliability of the model – <br /> can the model be trusted<br />Standardization = efficiencies<br />Vagueness = friction, inefficiencies<br />Level of Definition<br />17<br />
    24. 24. AIA – E202<br />Content, accuracy<br />Frequency of updates? Structure?<br />18<br />Implementation of BIM in the LOS<br />
    25. 25. Content of Models<br />Furniture, Architectural details<br />Abstractions can work very well<br />Misleading Level of Detail vs. Level of Definition<br />John Tobin: “Atomic BIM” http://www.aecbytes.com/buildingthefuture/2008/atomicBIM.html<br />19<br />Implementation of BIM in the LOS<br />
    26. 26. 20<br />Implementation of BIM in the LOS<br />Fast feedback<br />Estimating<br />E.g.: GSF, Exterior Wall Areas, Number of doors<br />Defining Value <br />Coordination<br />Visual Controls to identify problems early<br />Communication<br />Redundant Checks, one piece flow<br />Optimum<br />Optimum<br />Spectrum<br />Spectrum<br />One Detailed <br />Model<br />Detailed Model – <br />Long Longer Cycles<br />Many Less <br />Detailed Models<br />Lighter Model-<br />Shorter Cycles<br />
    27. 27. Breakout of model into manageable pieces<br />One file per floor per trade<br />Supports the flow<br />Formalize the process<br />Definition of naming conventions<br />Definition of model break-up<br />One piece flow<br />Reliable, tested technology<br />Just in time<br />21<br />Implementation of BIM in the LOS<br />CCMC-NG_SSR_DES_MPIPE_L06<br />_ALL_050_V0003_2010-01-19.dwg<br />
    28. 28. Who participates in the BIM effort?<br />Exclusive vs. inclusive<br />Prescriptive vs. evolutionary<br />Enable the team<br />Project based team planning sessions<br />Project based team training sessions<br />Enable and empower the team<br />22<br />Implementation of BIM in the LOS<br />
    29. 29. Implementation of BIM in the LOS<br />Create the right “flow”<br />Involve the right people at the right time<br />Allocation of responsibility and authority<br />Create clarity<br />Map out the process and the value stream<br /> “WHAT” “HOW”<br />23<br />
    30. 30. Meetings<br />Fine tune efficiency of meetings; processes and tools<br />24<br />Implementation of BIM in the LOS<br />
    31. 31. Meetings:<br />Class Room Style<br />Focus on the problem<br />Laser pointers<br />Involve and enable your people<br />SmartBoards<br />Visual Control<br />Involvement of the extended network<br />Make deliberate decisions<br />25<br />Implementation of BIM in the LOS<br />
    32. 32. Clash Reports<br />26<br />
    33. 33. Standardized process<br />Visual controls (color)<br />One piece flow (frequent meetings)<br />Redundant checks (frequent meetings)<br />Jointly developed<br />Standardized acronyms<br />Manage the flow and resources<br />27<br />Implementation of BIM in the LOS<br />
    34. 34. File Sharing Platform<br />All files in one place…<br />ONE place where we post, retrieve and archive the latest and greatest files<br />Transparency breeds self corrective behavior<br /> (Thad Allen, Commandant of the U.S. Coast Guard)<br />Minimize Movement<br />Standardize workflow<br />Frequent and redundant checks<br />One piece flow, pull<br />28<br />Implementation of BIM in the LOS<br />
    35. 35. Application of Lean in BIM<br />Pre-coordination<br />MEP coordination before buy-out of project<br />Creation of a subcontractor coordinated design model<br />Purpose: reliable allocation of space before final coordination<br />Significant acceleration of the coordination process<br />Stop the flow to fix problems at the earliest opportunity<br />29<br />
    36. 36. Linbeck Case Study:<br /> Two similar projects<br />Project A:<br />External coordinator<br />Project B:<br />Coordinator internal to project team<br />Results indicate importance of Lean principles<br />30<br />Implementation of BIM in the LOS<br />
    37. 37. Conclusion<br />Effective BIM is about the process<br />Lean is the ideal operating system for implementing new processes and tools<br />Violation of Lean principles results in reduced performance<br />The Value of BIM is GREATLY enhanced if used within a Lean Operating System<br />31<br />
    38. 38. South Cole<br />Jan Reinhardt<br />32<br />scole@linbeck.com<br />jan.reinhardt@adeptpd.com <br />

    ×