Autodesk® Revit®: A BIM Manager's Guide to Revit-alizing Your Office

1. Autodesk® Revit®: A BIM Manager's Guide to Revit-alizing Your Office Nauman Mysorewala BIM Manager, GBBN Architects. Consultant, PC TroubleShooters

2. Disclaimer: Speaker may make statements regarding advanced or simple features regarding this product. These statements are not intended to be a promise or guarantee of that these features will work exactly for you. They may provide you a cutting edge in your business. These statements about the product merely reflect the opinions of The Speaker which may not be correct. Implementation decisions should not be made based upon reliance on these statements. The Speaker assumes no obligation that these advanced-sounding statements may work for you. Since it is an Autodesk product your implementations WILL crash and there will be times you will be frustrated during implementation. You may email your questions to the speaker at a later date but under no circumstances the speaker is required to solve your issue. • AIA Credits! You should be able to claim AIA credits from the AU online page.

3. A Little about me… • B. Arch from Univ. of Cincinnati • BIM/CAD Manager for GBBN Architects, Inc. (Cincinnati Office) • BIM/CAD/Computer Consulting – PC Troubleshooters • Adjunct Faculty at College of Mount St. Joseph Interior Design Program • 2nd year teaching at Autodesk University • Autodesk Architecture Certified Professional 2009 • Autodesk Revit Architecture 2009 Certified Professional • 4+ years experience using Revit Architecture • 20+ years experience using AutoCAD/Architectural Desktop/AutoCAD Architecture

4. A Little About You…. • Architects • MEP • Structural • Others?

5. AGENDA & LEARNING OBJECTIVES • Understanding the benefits, planning and creating Network deployments • Standardizing Project Templates and deploying them • Creating company standards, libraries and deploying to your users • Training and on-going support

6. Revit-alize? • Creating planned Network deployments • Standardizing Project/Company Templates • Creating company standards, libraries, etc • Training and on-going support • Company management support

7. Network Deployment PlanningTo successfully deploy Autodesk Revit 2010 within your office(s) you need to answer some questions first: • Where is the network deployment stored? • Which server will be the license server? (for Network Licensing) • What flavor of Revit is being deployed? (Architecture, Structure, System, all three, just one, or two) • Which architecture Revit will be deployed for 32bit or 64bit or both. • Where is the central content stored & what folder structure you are going to follow (Revit’s, Custom, or Hybrid) • How are the users going to access the Revit OTB and Custom content (on server or locally) • Number of laptop users vs. desktop users? • Who is responsible for updating content? User rights • Which template is going to be the default template and where it is going to be stored?

8. Creating the Deployment • First Steps: • Pre-Install Revit on one machine to collect files from it. • Deployment Demo

9. Collecting the Files to be tweakedSave these files in the S:\software\Revit2010\Tweaks folder (S:\ = \\server\) • Revit.ini • (put this file in S:\software\Revit2010\Tweaks\Program folder) • Content.rcl • (put this file in S:\software\Revit2010\Tweaks\Program folder) The Revit.ini & Content.rcl file will be found in S:\software\Revit2010\x86\AdminImage\RevitSetup\RevitArchitecture (or your flavor of Revit) • Keyboardshortcuts.txt • (put this file in S:\software\Revit2010\Tweaks\Program folder) • Get this file from a local install in the \Autodesk Revit XXX 2010\Program” folder. • Subscription Advantage Pack for Revit 2010 has a great editing tool from within Revit Views>User Interface>Keyboard Shortcuts. • Import/export line weight files, fontmap files • (put these files in S:\software\Revit2010\Tweaks\Data folder) • Get these from the “%PROGRAMFILES%\ Autodesk Revit XXX 2010\Data\” folder • UIState.dat If you want to pre-populate the Quick Access Toolbar • (put this file in S:\software\Revit2010\Tweaks folder)(Vista/Win7-> %LOCALAPPDATA%\Autodesk\Revit\Autodesk Revit Architecture 2010\, XP %APPDATA%\Autodesk\Revit\Autodesk Revit Architecture 2010\)

10. Creating an install script: • DOS Batch files are still king. Using it we will: (I personally use InnoSetup & DOS Batch files together. (You can also use ORCA to create a transform and point to tweaked files instead of xcopy) • Copy tweaked Revit.ini, Edited keyboardshortcuts.ini , content.rcl • Install Revit 32 or 64 bit • Copy custom content to local machine (if needed) XCOPY “S:\software\Revit2010\Tweaks\Program\*.*” /s/e/y/i/d/r/EXCLUDE:S:\software\Revit2010\Tweaks\exclude.txt “%PROGRAMFILES%\Autodesk Revit Architecture 2010\Program\“ XCOPY “S:\software\Revit2010\Tweaks\Data\*.*” /s/e/y/i/d/r/EXCLUDE:S:\software\Revit2010\Tweaks\exclude.txt “%PROGRAMFILES%\Autodesk Revit Architecture 2010\data\“ REM 2. Decide which Revit architecture to install 32bit or 64bit :INSTALL if "%programfiles(x86)%XXX"=="XXX" GOTO 32BIT echo 64-bit Windows installed :64bit S:\software\Revit2010\AdminImage\Setup.exe /qb /I S:\software\Revit2010\x64\AdminImage\Revitalize-Arch-64.ini GOTO END :32BIT echo 32-bit Windows installed S:\software\Revit2010\AdminImage\Setup.exe /qb /I S:\software\Revit2010\x86\AdminImage\Revitalize-Arch-32.ini :COPYCONTENT XCOPY “J:\Standards\Revit\*.*" s/e/y/i/d/r/EXCLUDE:S:\software\Revit2010\Tweaks\exclude.txt C:\OFCStandards\Revit\ :END Echo all done Pause EXCLUDE FILE .zip .rar .bak .tmp .cab .00

11. Installing Service Packs Guess How? Using Batch files • @echo off • reg QUERY "HKLM\SOFTWARE\Autodesk\Revit\Autodesk Revit Architecture 2010\ServicePack2" • IF ERRORLEVEL 1 GOTO REGNOTFOUND • :REGFOUND • GOTO END • :REGNOTFOUND • REM REG NOT FOUND. Install Service pack 2 • if "%programfiles(x86)%XXX"=="XXX" GOTO 32BIT • S:\software\Revit2010\updates\Autodesk_Revit_Architecture_2010-x64_Update_2.EXE /q • GOTO END • :32BIT • S:\software\Revit2010\updates\Autodesk_Revit_Architecture_2010-x86_Update_2.EXE /q • :END • For Subscription Advantage Pack, just Substitute ServicePack3 for ServicePack2

12. Tweaking Files Tweaking the files can be accomplished using notepadCollecting the files to be tweaked • Revit.ini • S:\software\Revit2010\x86\AdminImage\RevitSetup\RevitXXXcopy this to S:\software\Revit2010\Tweaks\Program folder • Content.rcl • S:\software\Revit2010\x86\AdminImage\RevitSetup\RevitXXX copy this to S:\software\Revit2010\Tweaks\Program folder • Keyboardshortcuts.txt • “%PROGRAMFILES%\ Autodesk Revit XXX 2010\Program” copy this to S:\software\Revit2010\Tweaks\Program • Import/export line weight files, fontmap files • “%PROGRAMFILES%\ Autodesk Revit XXX 2010\Data” copy this to S:\software\Revit2010\Tweaks\Data folder • UIState.dat If you want to pre-populate the Quick Access Toolbar • Vista+: “%LOCALAPPDATA%\Autodesk\Revit\Autodesk Revit XXX 2010\” • XP: “%APPDATA%\Autodesk\Revit\Autodesk Revit XXX 2010\”

13. Revit.ini • Most of the tweaking in Revit.ini will be in the Directories section [Revit.ini] [Directories] DefaultTemplate=C:\OFCStandards\Revit\MYCOMPANY Imperial 2010.rte FamilyTemplatePath=C:\ProgramData\Autodesk\RAC 2010\Imperial Templates DataLibraryLocations=Imperial Library=C:\ProgramData\Autodesk\RAC 2010\Imperial Library,Metric Library=C:\ProgramData\Autodesk\RAC 2010\Metric Library,Imperial Detail Library=C:\ProgramData\Autodesk\RAC 2010\Imperial Library\Detail Components,Metric Detail Library=C:\ProgramData\Autodesk\RAC 2010\Metric Library\Detail Components,My Company=C:\OFCStandards\Revit\ ProjectPath=C:\RevitLocal (Create Local File data store) ImportLineweightsNameDWG=C:\Program Files\Autodesk Revit Architecture 2010\Data\MYCOMPANY-importlineweights-dwg.txt ExportLayersNameDWG=C:\OFCStandards\Revit\ MYCOMPANY-exportlayers-dwg-AIA.txt ExternalParameters= C:\OFCStandards\Revit\MYCOMPANY-SharedParameters.txt [ExternalApplications] [ExternalCommands] • External app files need to also be copied using the install script • Manually add External Apps lines or use Add-in Manager in the SDK Note: User added folders to Placesbar using “Add Current Folder to Places” in Open dialog box do not get saved to Revit.ini. Instead these get saved in the registry at: HKEY_CURRENT_USER\Software\Autodesk\Revit\Autodesk Revit Architecture 2010\Profiles\AllAnavDialogs

14. Content.rcl • Used to install factory content • Tweak to convert UNC pathing to Mapped pathing • No need to tweak if you are not copying deployment to multiple servers • (partial content.rcl file) • [Bundle_NAImperial.cab_2] • …… • name=North American Imperial • filename=NAImperial.cab • …… • fullpath=\\server\software\Revit\AdminImage\ContentENU\NAImperial.cab • Change to • fullpath=S:\software\Revit\AdminImage\ContentENU\NAImperial.cab

15. Server to Local Content Sync Guess How? Using Batch files • @Echo OFF • XCOPY “J:\Standards\Revit\*.*" s/e/y/i/d/r/EXCLUDE:S:\software\Revit2010\Tweaks\exclude.txt C:\OFCStandards\Revit\ • REM Set the custom content read-only so users cannot modify it. • ATTRIB +r "C:\acadusercustom\Acadarch\Revit\GBBN\*.*" /S Call above lines to the users logon script or add the batch file to the registry under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run. e.g. (add this using REG ADD command in install script)

16. Deploying it to the users • Browse to your server • Right Click on Install Script

17. Standardization: Folder Structure: • Standard Content • Copy the OTB content folder • Depending on the Revit flavor add custom folders e.g. for Revit Architecture: Details, Generic Models, Groups, Schedules, System Families, Templates. • Project FoldersMany companies have different requirements, but for Revit I would recommend a few folders to organize the project files • Current • Consultant Models • Families • Export • CAD imports (this will house actively used CAD linked files from Consultants, etc) • Plots (to house PDF’s,DWF’s,etc) • Archive (To store past phase files, SD, DD, CD, etc)

18. Standardization: File Naming • Project files • Every company has different conventions for numbering and naming • Prior to 2010 release we had procedures to create local files. In 2010 you can use the automated creationlocation was specified when creating the deployment Step 7.4 User Files • Families • Prefix families with a 00Initial of Company (for standard content e.g. 00G_Family) • Project name (for project families, e.g. 01_Project Family) • Downloaded content or project content which has been approved and published in the Standard, should be renamed with the above convention • Create a family submission folder for unapproved content • Add a custom text parameter in your families to add a version/date. This way it will be easier to troubleshoot families in the future • Also refer to the Revit® Model Style Guide at Autodesk Seek http://style.guides.s3.amazonaws.com/Revit_Model_Style_Guide_v2.zip

19. Standardization: Process Guidelines: • Location of and Naming Local files (if not using 2010 auto creation) • Reload latest or Synchronize with Central after opening the local file • Saving guidelines, • When and how often to synchronize with central, • Saving at the End of Day & always Relinquish (with workset exceptions) • Switch to before saving at the end of day to speed up load process for the next time. • Once a week performing cleanup activities • Create a new Local file (local files get bloated more than the central file) • Audit the Central file • Purge if needed • Compact the central file • Rename Standard Families/Types (OTB or Office Standard) before modifying in Family editor.

20. Standardization: View naming Conventions: • Each project is different and each Discipline has different requirements • Develop a View naming convention for your projects • Create a Published and a Working view for Plans. • Prefix each view: WRK (working) or PUB (Publish) ENG (Enlarged) EXST (Existing) i.e. WRK First Floor, PUB First Floor. EXST First Floor, • 3D Views: • 3D Views for publishing should be prefixed with PUB – 3D View-Desc, i.e. PUB – Exterior SW, PUB – Section – Lobby, PUB – Camera – Room 1212 • Elevations: • Exterior elevations named with direction North, South, East, West. e.g. PUB SouthPartial elevations are to be prefixed with Part and a minimal description. • Interior Elevations: identified with the Room# and Direction. E.g. PUB 1232 N, PUB 1232 Office South. • Sections: • Building Sections: PUB - Direction - Column Grid #. E.g. PUB - NS – Col D • Wall Sections: PUB – Elevation Direction – Nearest Column Grid #. e.g. PUB – N – B • Interior Sections: PUB – Room # - Desc. e.g. PUB – 1212 – Casework, PUB – Clg – 1212 – Soffit

21. Standardization: View naming Conventions: (continued) • Details: Create multiple types • Interior Details: PUB – Room # - Description. E.g. PUB – 1212 – Type of Detail • Plan Details: PUB – Column Grid Intersection – abbreviated Description. • Wall Section Details: PUB - Wall Section (as named under wall sections above) – Level/Description • Misc Details: PUB – Description • Drafting Views: • Drafting Views are used to create details from scratch or importing details from AutoCAD. If the Drafting Views published it should have the PUB Prefix. Since Drafting Views can be of wide variety, naming conventions will need to be developed for your specific needs • Legends • Schedules • Custom Browser Organizations

22. Standardization • Worksets: • Develop naming convention for Worksets. Based on project type, etc • E.g. Naming worksets based on system or group, e.g. 1St Floor Exterior, 1st Floor Interior, 1st Floor HVAC, 1st Floor Electrical, etc • Worksets are not layers, but remember your AutoCAD days • Educating users about creating objects on the correct workset • Will help speed up working in project

23. Customizing the TemplateLot of classes offered this year on templates. This list is by no means complete • What not to include: • Do not make your project templates heavy . • Do not include everything that a project MAY use • Educate users about Standard Content folders and its content • System Families can be loaded either via Copy/Paste • Details: • Adding details that a project may use will unnecessarily weigh the template down. • Some details are appropriate to add, like standard mounting heights, abbreviations, patterns etc. • Worksets: • Cannot have Worksets in templates so no problem here. • Utilize your procedure and guidelines to dictate naming conventions • Title Blocks • Add most commonly used Title block, not everything the company has

24. Customizing the Template: What to include • Project Information Parameter for the version of the template • Title Blocks: • Add at least the standard size titleblock in the template • Add other sizes to Standard Content library. • Title Sheet: • Most all projects will have a title sheet • Layout Title Sheet • Partition (wall) Types: • Standard partition numbering/naming system helps. • System Families: • Use the idea above for walls to create commonly used system families • Prefix with a 00Initial to distinguish company content • View Templates: • Cannot stress the importance of View Templates • Helps tremendously with standardization

25. Customizing the Template: What to include • Initial Sheet Set: • Gives project teams a good working start • Helps maintain company standard numbering system • Add two parameters to control the browser organization and drawing list

26. Customizing the Template: What to include • Miscellaneous Company Standards: • Fill Patterns • Object Styles • Line Styles • Line Weights • Line Patterns • Annotations • Callout Tags • Elevation Tags • Section Tags • Title Mark • View types, e.g. • Building Section, Wall Sections • Interior Elevations, Exterior Elevations • Plan Details, Walls Section Details • Materials & Patterns

27. Training and On-going Support • Training is key to implement Standards • Continued Project Consultation by the BIM Manger to ensure compliance to the standards • Incorporate Process, Guidelines and Company Standards into any Revit Training My favorite Tutorial book for Revit training: Commercial Design Using Autodesk Revit Architecture 2010 by Daniel John Stine ISBN: 978-1-58503-512-0 • Utilize Subscription eLearning or AU Online video recordings

28. On-going Support • Be a constant contact for the Project Teams • Create point-people that are “advance users” to answer everyday questions • Online Forums (Autodesk or AUGI, etc) to search or post issues • Subscription customers can create a support request. They are great for recovering corrupt files or hard to figure out issues. Access it from within Revit product.

29. Conclusion • We have covered a multitude of topics to help standardize Revit and create a company standard. The key is to educate the users to follow the standard. It may take a few extra minutes for the users to follow the guidelines, but it will result in a much streamlined, efficient working project. • If you have any comments or suggestions or need consulting help please feel free to contact me at (513-777-9917) or email me at bimologist@cadbazaar.com or visit http://www.pctroubleshooters.com • Thank you • Nauman Mysorewala Please Fill out the Class Survey before 8pm the day of class and be entered to win a trip to AU 2010

30. Please Fill out the Class Survey before 8pm the day of class and be entered to win a trip to AU 2010