Revit Technology Conference 2007 Documentation in Revit

Introduction Who am I? What do I do? What do you do? What you may expect Leverage and efficiencies Tips and tricks, traps, best practice, workarounds What I may expect Learning and sharing chris.n@c3consulting.com.au CAD/BIM Strategic Consulting Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary How long have users been using Revit? How many people using Revit on projects on small projects (under $2m)? Ditto ($2m - $5m) Ditto ($5m - $25m) Ditto ($25m +) New era of technology development – exciting times.

RTC 2006 Recap: RTC 2006 - Documentation Basic Documentation Glen Cunnington – Monumentum Documentation Management - Prepare you plan of attack! Review - Audit the design model Standards - Establish your practice standards Views - Prepare the views you intend to document Sheets - Setting up drawings Annotation - Annotating your views Detailing - Adding detail to your views Production - Printing, exporting and revising Advanced Documentation Gary Kleyn & Daniel Smith, Glanville Architects Download the PDF of the talk from the RUGS website http://www.rugsyd.com.au Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary

Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Information Aesthetics (Look & Feel) Establishing Standards Templates Family Creation Production Summary Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary

Control First you must control your model Design Philosophy Placeholder vs. elements Revit 2D views are live representations of 3D models Sometimes too alive! Need to protect and lock various elements: Invisible objects, reference planes, placeholders Must be disciplined and communicate Harder to hide laziness or lack of knowledge Direct impact on team members Benefits: Improved teamwork and workflow Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Good idea to lock: Scope Boxes Masses (placeholders) Grids Views (on sheets) Reference planes View References (Sections/Elevations/Callouts) Discipline and communication most important when using Worksharing

Control (Continued) Controlling Views Dependent Views Once you’ve created one set (across one level), you can Apply Dependent Views to other parallel views that share the same scale Customise View Reference families to suit your needs, eg. Breakline appearance View purposes and types Use Shared Parameters Callouts (linked vs. dummy) Eg. for linking GA plans to dependent views Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary CONTROLLING VIEWS Demonstrate using Health Clinic sample project: GA plan vs. Parent Parent vs. dependents Create dependent view for east wing Add scope box to east wing and associate view to east wing scope box Pin scope boxes Add dummy callouts to part floor plan Fix grids to east wing in new view, propagate thru views, associate to scope box Create multiple dependent views for First floor (highlight importance of same-scale application) Show matchlines and ‘breakline’ view references Show view disciplines and visual effects resultant Reapply dependent views to electrical plans UNCHECK ‘PRESS AND DRAG’ OPTION! CONTROLLING THE BROWSER Demonstrate View organisation (various examples) using shared/project parameters Show temporary section markers thru stair, (inspection only) show hidden line tool on stairs CONTROLLING THE SHEETS Show views under sheet nodes – access to sheet (and type of view indicated) Show view list Show sheets vs milestones Show sheets organised by primary/secondary series

Control (Continued) Controlling Views Section boxes View properties Great for inspecting the model View properties Explore and try everything View Templates Apply by scale (use project browser to help sort by scale) Scope Boxes Don’t confuse with Section Boxes Marvellous way to control ref planes, grids, levels and view extents

Control (Continued) Controlling the Browser Controlling the Sheets View organisation Not on sheets Custom Shared Parameters Housekeeping Sorting to see what is important and perhaps quickly eradicate old or redundant views Controlling the Sheets Schedules Sheet organisation Sheet access to views

Hybrid Revit Pros and cons Prepare drawings Gain speed, but can lose quality of info Users familiar with format, but have less control Prepare drawings Consider appropriate use Clean up drawings (hatching, anonymous blocks, purge) Maintain naming conventions Keep names intuitive if you intend to use multiple files Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Gain speed, but lose quality of information – particularly 3D/BIM Some familiarity with DWG format, but less control over individual objects PREPARE DRAWINGS Consider project needs and ‘appropriate’ use – possibly short term only Clean up drawings, ensure nothing at 0,0 if coords system is far away Remove hatching, remove floating objects (eg. On frozen layers) Purge everything, even consider renaming layers Bind all xrefs??? (No longer required if xrefs are attachments) MAINTAIN NAMING CONVENTIONS Difficult to rename linked files throughout a project – best to establish naming convention and stick to them. LINKING vs IMPORTING Link preferable to importing Consider ‘this view only’ Place into workset (invisible by default) Don’t explode Can be good to trace over geometry and then detach the file to keep the Revit project clean Trace over technique can be a good learning mechanism for new users (DWGs, photos, sketches etc.) IMAGES Constrain/Don’t Constrain proportions Get draw order right Calibrate and LOCK if tracing over Can be good for presentation purposes (rough) – eg. Sky background to East Elevation of Clinic

Hybrid Revit (continued) Linking vs Importing Linking is usually preferable Don’t have to keep all the imported files – clean up whenever possible and appropriate Place into dedicated workset (invisible by default) Don’t explode ‘Trace over’ technique - Working with images Calibrate and pin the image Presentation styles can be made easy by importing images as backgrounds (use in view or on sheet under views)

Other Views 3D isometric 3D perspectives 3D details/cutaways Schedules Grouping of fields Working vs. Production purposes Room and Area fills Consider your needs before commencing Area schemes define what you want to measure Shadows and shading Thirsty on resources Greater depth and clarity Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Demonstrate: 3D isometric (save view icon) 3D inspection views using section box Create 3D cutaway thru stair section detail SCHEDULES Group and Show on Options Bar Easier to cut than to add fields Combine Area schedule with Color fill – composite views on sheet Room and Areas SHADOWS AND SHADING Demonstrate 3D elevations over 2D on sheet (show text coming thru) Thirsty on resources – keep physical image sizes low, use medium or low raster quality when printing Greater depth and clarity applied to work.

Worksets Worksets vs. Worksharing Defining worksets Consider carefully according to project needs Central vs. Local files (automation) Relinquishing Save to Central Central File Management Audit periodically Compact periodically Review Warnings periodically Restoring from Backups Moving (Always ‘Save As’) Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Borrow notes from Workset newsletters

2D vs. 3D Detail groups Detail components Underlay model Repeating details 2 pick families Space Bar Underlay model Check your progress Drafting views Imported Details Clean up first, don’t keep in project Legend views Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Demonstrate 2D groups, showing exclusion of items (RMC to restore) Detail components fast and simple to create, but less integrity within model (not good long term option) Repeating details – show sample file from Autodesk, customised AUS version 2 pick families great – eg. ????? Space bar – pre- and post- applied to components, and detail lines (& walls) Show how underlay works – finding the right level to see your roof… DRAFTING VIEWS save to new RVT file Re-use legacy DWG data – but beware legacy crap! LEGEND VIEWS Great for non-system families (eg. Dimensioning components) Can’t tag or dimension sample items

Annotations Tags Text Dimensions Note Block Grid types Leaders Arrowheads (limitations) Dimensions Rounding Define styles by purpose Note Block Keynoting Grid types Detail Components Symbols Spot Levels Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Consistency and clarity should rule supreme. Range of tags can be achieved by family types (visibility parameters) or separate families. Establish a system and stay methodical (we show room numbers only at this scale, but room numbers AND names at this scale) – this may also vary by project type or size. Name text families according to use (eg. ‘2.0mm (notes)’) Ultimately there should be minimal text and maximum tags – drawing from the model. May need to modify tag templates if you want to use a font other than Arial. No easy way to change fonts en mass. Arrowheads still limited – can’t open an arrow more than 90 degrees, can’t have arrowhead different line thickness to leader line. As of 2008 – free-end leaders can remain associative to referenced objects. Create dimensions according to purpose (not scale as per AutoCAD!), eg. Standard, overall, grids, to check, rounded off etc.. Note block Can have multiple grid types – useful for campus arrangements (remember scope boxes) or even primary vs secondary, or structural vs ceiling etc. Symbols: North points should be symbols drawing stamps key plans Breaklines (not as detail components) Spot levels fantastic for reference and working purposes, eg. Locating levels of plinths on sloping sites (c/w relative levels) Set up FFL, FL, SFL, FCL and Surface RL spot levels – you MAY find a use to support two sizes of each, depending on how much you want these to stand out.

Information Aesthetics Line Styles Be clear and consistent with naming Consider naming by purpose or object type (eg. ‘Fence’) Lineweights Vanilla (OOTB) lineweights not appropriate Customise only once (in template) Transfer if required via Transfer Project Standards Line patterns Not difficult, but still no support for complex line patterns Linework tool View visibility Filters Halftones Underlays Composite views 3D over 2D elevations All topography vs. crop region Filled Regions Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Lineweights should be set up as early as possible, with much testing on a real project to ensure satisfaction. Looks daunting, but look for patterns. Vanilla lineweights are not great (who needs an 8 or 9mm lineweight?) Line Styles (linetypes) should be set up to be clearly understood. One way to help standardise is to name them by purpose (eg. Electrical wiring, building extents)… You can’t select a line and apply a line pattern as an override, so definitions must be well resolved. Currently a very difficult type of object to clean up. Line patterns are not so difficult. Same rules re consistency apply. Old trinity model from AutoCAD worked well, though still no proper support for complex linetypes yet (eg. Zigzag or embedded text etc.) Establish filter lists early in response to project needs (what do you need to show and what would you like to be able to show better?). Keep them collated and document what they’re for (screen grabs of samples are a must). Halftones are applied automatically if views are set to different disciplines – would like some control over this. *Linked views don’t show cross-discipline. 3D vs 2D info: consider benefits of better data – gets more competitive tenders, clients/buyers get more engaged, construction faster. Try to minimise use of filled regions on their own, as they are so cosmetic, and usually cover up iniquities. Better within detail components.

Establishing Standards Required for Graphics Processes Best Practice Naming Conventions Views Families Object Styles Subcategories (similarity to layers) Details Save as views Utilities to save model items and views Presentation of standards Knowledgebase vs. manual format Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Establish common graphics: lineweights, linestyles, detail level, line patterns etc. Establish common processes and document them for reference by all – encourage suggestions for improvement Ditto for best practice – hold workshops and discuss which approaches are successful and which aren’t. Maintain consistency in nomenclature inside and outside of projects. Ditto for Object styles

Templates Use appropriate numbers of preloaded components ‘Shopping trolley’ approach using sample projects Easy platform for establishing BIM standards Multiple templates Base (office-specific) Project Type Client Sample files System Families Materials Environment settings Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Template can have half your work done before you start (and done correctly) Protect your office template (as always) Encourage suggestions for further improvement Over the long term, develop multiple templates depending on project types and requirements. Use sample files ‘the chef approach’ (however this can circumvent learning)

Family Creation Library structure Library management and distribution Importing images into workspace Content philosophy Generic Manufacturer specific 2D vs. 3D geometry Masking Regions Type Catalogs (*.csv files) Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary LIBRARY STRUCTURE Be consistent and keep it intuitive. Avoid duplication wherever possible. Keep clean (batch-delete backup files regularly) MANAGEMENT AND DISTRIBUTION Central library model vs. deployed locally – discuss issues Can import images into workspace when creating families – good for reference. These don’t come through to the model. Generic vs. Manufacturer specific – build Generic content first, as it holds more value. Dangers lurk in being too specific with selected items. Revit’s modelling limitations can necessitate 2D symbolic linework in many cases. Masking regions new to 2008 – useful in lieu of 3D geometry. Resourcing better objects – sketchup objects from Formfonts or 3D Warehouse. Maximise use of type catalogs – don’t develop too much content without these! (Still awaiting resizability of dialog)

Production Plotting PDF DWF Use with third party app to batch-rename output files if required DWF 2D or 3D format Markup and review using Autodesk® Design Review Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary Establish standard setup configurations in template Beware resource limitations with raster-heavy views/sheets Beware zoom scale and ‘left-over’ view/sheet lists PLOTTING PDFs Choice of one or separate documents Ensure you have PDF software that will (at least partly) recognise the document name. Use Flash Renamer to edit printed filenames if required DWF Need to check on this HTML EXPORTING shaded views – beware filesize! Export rendered images – don’t keep them embedded in view as Renderings PROJECT BROWSER can help you revise your drawings REVISION MANAGEMENT – still needs some work by Autodesk if you don’t like numbers-only methodology ARCHIVING – save as new file or new central file (don’t copy file). Saving as a new central file eliminates the need to detach from central, but ensure all users have relinquished all and STC’d.

Production Exporting Leveraging project browser Revision Management Rendered images Shaded views Leveraging project browser Maximise sorting capabilities Use it like a batch processor to apply sheet parameters en mass Revision Management Vanilla (OOTB) options not appropriate for Australian conventions Archiving Save as new (central) file Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary

Summary Be disciplined and consistent Communicate with your colleagues Think outside the square Try new ideas Always strive for better methods and information CCC - ‘Conveying the Correct information Clearly’ New technology where to from here? Sidenote: Uncanny Valley Introduction RTC 2006 Overview Control Hybrid Revit Other Views Worksets 2D vs 3D Annotations Aesthetics Standards Templates Family Creation Production Summary

Uncanny Valley Basic Theory Established by Masahiro Mori in 1970 …as a robot is made more humanlike in its appearance and motion, the emotional response from a human being to the robot will become increasingly positive and empathic, until a point is reached beyond which the response quickly becomes that of strong repulsion. However, as the appearance and motion continue to become less distinguishable from a human being's, the emotional response becomes positive once more and approaches human-to-human empathy levels.

Uncanny Valley examples of characters/beings lacking in likeness Dr. Hiroshi Ishiguro.

Summary To ponder: Our building images can be like this, where the client (or other viewer) doesn’t buy into an image if it falls into the valley. Sometimes it’s safer to use a heavily stylized image, suggestive of a concept. The equivalent of this in a character analogy could be the Simpson – poor (human) likeness, but we still relate strongly…