Presentation is loading. Please wait.

Presentation is loading. Please wait.

An ARNG Project Autodesk Revit Case Study Mark Da Gama Rose Design Technology Manager – JACOBS.

Similar presentations


Presentation on theme: "An ARNG Project Autodesk Revit Case Study Mark Da Gama Rose Design Technology Manager – JACOBS."— Presentation transcript:

1 An ARNG Project Autodesk Revit Case Study Mark Da Gama Rose Design Technology Manager – JACOBS

2 Class Poll Audience Composition:  Architect/Interior Architect  Engineer (Structural/MEP)  Principal  IT/BIM Manager

3 Class Intentions  Stress How Early Decisions On A Project Have A Lasting Effect  Talk About What Worked And What Did Not Work  Show Recent Solutions To Issues That Arose On INARNG-AFRC  Stress That It’s All About The Process  Communication And Standards Are Key Especially As A Project Is Hampered By Its Weakest Link

4 Class Topics  INARNG-AFRC Project Background  BIM Mentality And Process  Expectations – Both Internally and of Client  Hardware  File Linking  Worksharing And Worksets  Model Performance Checks  Challenges And Decisions Made Within Each Discipline  Coordination Between Disciplines  Construction Document Creation  Making CAD Files Compatible With AEC 3.0 CAD Standards  Revit To 3D Studio Max Rendering Process  Summation And Closure

5 INARNG-AFRC Project Background Purpose : Joint Armed Forces Reserve Center to serve the peace-time missions of the assigned unit and space for all personnel to perform the necessary tasks that will improve the unit readiness posture Project Size: 168,095 SQ. FT. Design Deliverables: 35%Dec 2008 (8 Weeks) PDFs 65%Feb 2009 (8 Weeks) PDFs 95%Apr 2009 (8 Weeks) PDFs FINALJune 2009AutoCAD 2007

6 INARNG-AFRC Project Background Primary Spaces Include: Building’s permanent masonry-type construction consisted of:  Slab-On–Grade First Floor And Elevated Steel Structural System For The Second Floor  Brick And Concrete Block Units With Concrete Floors  Exterior Masonry Walls Combined With Interior Masonry And Steel Stud/Gyp. Board Partitions  Steel-Framed Roof Structure – Combination Membrane/ Sheet Metal Roof  Locker Rooms  Military Unit Storage Rooms Including Arms Vaults, Mechanical, Electrical And Equipment Rooms  Office Areas  Classrooms  An Assembly Hall  Commercial Kitchen

7 BIM Mentality and Process THINK BEFORE YOU DO – BIM Process as important as the:  Hardware Specs  Software Version Limitations  Team’s Learning Curve EARLY REVIT DECISIONS CAN HAVE A LASTING EFFECT ON THE PROJECT Key Steps in the project:  BIM Strategy Call  BIM Kickoff Meeting With Team  Maintain A Living, Breathing BIM Implementation Plan Throughout The Project

8 Expectations – Both Internally and of Client  Per the Client’s Scope of Work the only final documents of record were AutoCAD files  However, Jacobs’ internal mandate is to do projects in BIM…. This project was done using the Autodesk Revit 2009 platform

9 How were those Expectations Managed?  Strived To Plot All Construction Documents From Revit  Team Member Support Came From BIM Coordinator And Revit Discipline Leads  Tried To Have Weekly Bim “Lunch And Learns”  Needed To Have A 5 Minute “Huddle” For Revit Discipline Leads Just Because We Develop A Model Does Not Mean We Deliver A Model….Client Expectations/Budgets/Staffing/Billable Hours

10 Hardware  Revit Discipline Leads Had Dell T5400s – 64 Bit (Specs: 8GB RAM, 3.16 GHz, 512 MB Nvidia Video Card)  Most Team Members Had Dell T3400s (Specs: 4GB RAM, 3.16 GHz, 256 MB Nvidia Video Card)  One Rendering Computer: (Specs: Dual Quad core; 8GB RAM; Xeon Processor)  All Users With Dell T3400 Had 3gb Switch Enabled And Paging File Increased To 8GB  All Users Had Gigabit Switch To The Desktop Connections

11 File Linking INARNG-AFRC Project File Structure INARNG-AFRC INARNG-AFRC-A-CENTRAL.RVT INARNG-AFRC-A-DETAILS.RVT INARNG-AFRC-E-CENTRAL.RVT INARNG-AFRC-E-DETAILS.RVT INARNG-AFRC-P-DETAILS.RVT INARNG-AFRC-A-DRAWINGINDEX.RVT INARNG-AFRC-I-CENTRAL.RVT INARNG-AFRC-S-CENTRAL.RVT INARNG-AFRC-M-CENTRAL.RVT INARNG-AFRC-M-DETAILS.RVT INARNG-AFRC-F-CENTRAL.RVT INARNG-AFRC-F-DETAILS.RVT INARNG-AFRC-P-CENTRAL.RVT

12 File Linking 3 Main Reasons Why Discipline Models Were Separated Out: 1. Each Discipline Controlled Their Own Drawing Sheet Set 2. Prevented Disciplines “Stepping On Each Other’s Toes” Concerning Element Borrowing And Relinquishing 3. Model Performance Was Controlled Through The Opening And Closing Of Linked File Worksets

13 File Linking Negatives To Linking By Discipline  Systems Connections  Limitations on Tagging through the Link  Split Architecture from Interiors?  File Management Issues Magnified  Communication Needs To Be Especially High

14 File Linking A “Model” And Typical Detail File Was Created For Almost Every Discipline  Pros:  Model Performance  Streamlined Discipline Workflow  Cons:  View And Sheet Referencing  2 Files To Manage Settings And Coordinate Drawings for Submittals  Need To Be Very Clear Whether Drawing Sheets Are Located In “Model” File Or Typical Detail File

15 File Linking Important Considerations:  Renaming The Linked Instance  Pin Linked Instance  “Make Editable” Linked Project Files  Keep Same Name Of Linked Central Files (Project Prefix-Discipline Initial-CENTRAL.RVT)  INARNG-AFRC-A-CENTRAL.RVT  INARNG-AFRC-M-CENTRAL.RVT

16 File Linking INARNG-AFRC-DRAWINGINDEX.RVT Separated Out For Two Reasons: 1. Model Performance 2. Architectural Workflow – Allows Specialization Of Task

17 File Linking Downfalls  Time to Open Project File  Discipline Management Process  Sorting/Grouping of Discipline Sheets INARNG-AFRC-DRAWINGINDEX.RVT

18 Worksharing and Worksets “LARGE CHUNKS OF THE MODEL” Need Mentality “Why Do I Need To Create A New Workset?” Uses:  Workflow  Model Performance  View Visibility Control – Inside Of Project File  View Visibility Control – Between Project Files

19 Worksharing and Worksets Key Project Aspects:  Workset For Each Linked File  Minimal Amount Of User Created Worksets  Element Workset Classification Identified And Updated In BIM Implementation Plan  Naming Convention  *LINKED MECH  *LINKED STRUCT  Shell  Core

20 Worksharing and Worksets Key Project Aspects:  Only Discipline Leads Were Allowed To Create New Worksets  Checking Active Workset  Workset Classification Correction  Best Approach To Relinquishing?  Workset View Visibility (View Specific) VERSUS Closing Worksets (Global)

21 Worksharing and Worksets Key Project Aspects:  Taking Advantage of Closing Worksets  Element Borrowing Was Heavily Used Making Worksets “Editable” Allows 2 Main Benefits: 1. Prevents Anyone Else From Manipulating Elements Tied To That Workset 2. Revit Does Not Constantly “Ping” The Central File About Who Is Borrowing Elements Of That Workset

22 Model Performance Checks  **Open/Close** Drafting View  64 Bit Machines To Plot Out Submittals  Benefited From Using The 3GB Switch  Close Worksets When Possible  Work In Wireframe/Plot In Hidden Line  Review And Fix Warnings  Family Detail Level & Visibility In Plan/Elevation

23 Challenges and Decisions Made Within Each Discipline Common Challenges Amongst The Disciplines  Proximity of Team  Worksharing Monitor Usage  Saving & Relinquishing  Specialization of Task  AutoCAD Versus Revit Newbie Mentality  Ghost of Revit

24 Challenges and Decisions Made Within Each Discipline Architectural Challenges  “Elements Have Duplicate Mark Values”  Team Members Rotated In And Out  Wall Join Conditions

25 Challenges and Decisions Made Within Each Discipline Interiors Challenges  Adding Room Tags  Interior Elevations  Maintaining View & Sheet Consistency  Tile Patterns  Material Legend

26 Challenges and Decisions Made Within Each Discipline Structural Challenges  Coordinating Design And Revit Production Workflow  Custom Truss Creation

27 Challenges and Decisions Made Within Each Discipline Mechanical Challenges  Systems Creation  Family Creation

28 Challenges and Decisions Made Within Each Discipline Electrical Challenges  Circuit Creation  Content Creation

29 Challenges and Decisions Made Within Each Discipline Plumbing Challenges  Filters Distinguished Pipe System Types By:  Color (Graphically)  Linetype (for construction documents)  Export Mapping To Systems Layers In AutoCAD  WAN workflow

30 Challenges and Decisions Made Within Each Discipline Fire Protection Challenges  Sprinkler Pipe Creation

31 Coordination Between Disciplines  Setting Structural Usage of Walls  Assigning Family Category & Sub- Category  Room Volume Coordination & Workflow  Room Tag Coordination & Workflow

32 Coordination Between Disciplines  To Host Or Not To Host?  Structural Column Grid Updates  Owning Linked Worksets  Concrete Plan to Prepare for Submittals

33 Construction Document Creation  Browser Organization – Crucial For Views And Sheets  Need To Sort By Working And Sheet Views And Then By Sub Discipline If Needed  Did not implement effectively on INARNG-AFRC

34 Construction Document Creation  Did Not Really Use Dependant Views  Had To Use Masking Regions As A Polygonal Viewport Clip

35 Construction Document Creation  View Templates  Not Enforced From The Start & Maintained Thereafter On INARNG- AFRC  Very Important To Set Up In The Beginning  Need To Have One For Each Type Of View – Should Be Part Of Template  Helps Alleviate “Ghost of Revit”

36 Construction Document Creation  Only Copy/Monitored Structural Column Grids And Levels  Section Cuts Apparent In Multiple Plans  MEP Disciplines Could Not Show Arrowhead On Space Tags

37 Construction Document Creation  Instead Of Keynotes (Could Not Number By Keynote Or Sheet) We Used Note Blocks  All Keyed Notes Per Type Of View Listed Regardless Of Shown Or Not  Strike Through Keyed Notes Not Applicable To View  Needed To Have Note Block And Corresponding Tag For Each Type Of View That Has Keyed Notes

38 Construction Document Creation Details  Imported And Exploded In Revit  Replaced With Detail Components  Incurred Numerous “Line Slightly Off Axis Sketch” After Importing  Text Style Converted To Revit

39 Navigating through the Export Process to Match AEC CAD Standards Checklist In Revit Before Exporting  Mapping Of Layers/Colors (Export Layers Txt File)  File > Export…Export Options  Miscellaneous  Text On Titleblock Should Be Set To Transparent  Had Issue With Section Headers Hatching – Needed To Edit Block Symbol

40 Navigating through the Export Process to Match AEC CAD Standards 3.0 Checklist In AutoCAD 2007 After Exporting  Linetype Scale – Scale Up X92 For 1/8”=1’-0”  Fill Patterns And Masking Regions Were Solid Hatch In AutoCAD Files  DWG File Naming Convention To Match AEC CAD Standards

41 Revit To 3DS Max Rendering Process 1. Exported Revit Discipline Models  Detach From Central  Remove All Links  Export 3d View To AutoCAD 2. In 3DS Max:  Linked In The Architectural.DWG  Linked In Each Other Discipline.DWG 3. The Model Only Edited If Needed For A Rendered View  Materials & Lights Added  VRAY – Rendering Engine

42 Rendering Images

43

44

45

46

47

48 Summation and Closure  Survey User Level Experience Per Discipline (1-5)  Establish Expected/Specific/Realistic Tasks By Team Members In Each Discipline Model (Roles And Responsibilities – Put In BIM Implementation Plan)  Standards Are Key – Templates, Bim Implementation Plan, Organized Details And Content  Acceptance Of Working In Revit And How It Will Be Done On A Project Is Crucial….Everyone Must Be On The Same Page 1Brand New User 2Worked On 1-2 Revit Projects 3Can Resolve Coordination Review Issues 4Can Fix Warnings; Cleans Up Workset Classification 5Advanced Parametric Family Creation; Revit Discipline Lead

49 Questions/Comments

50


Download ppt "An ARNG Project Autodesk Revit Case Study Mark Da Gama Rose Design Technology Manager – JACOBS."

Similar presentations


Ads by Google