© 2011 Autodesk CM5708 Connecting the Dots: Implementing Autodesk® Revit® Server for Multi-Firm Collaboration Nauman Mysorewala BIM/CAD Manager GBBN Architects, Inc.

© 2011 Autodesk A little about me  B. Arch from Univ. of Cincinnati  BIM/CAD Manager for GBBN Architects, Inc.  Blog at  Autodesk Revit Architecture Certified Professional 2011  Autodesk Architectural Desktop Certified Professional 2009  18+ years experience using Autocad/Architectural Desktop  Contact: 

© 2011 Autodesk Class Summary This class will cover procedures and techniques for a successful implementation of Revit Server between consultants for a true integrated project delivery (IPD) collaboration scenario. After this class, you will be able to install Revit Server within your organization and create easily distributable virtual Revit Servers for remote sites. You will learn to connect the sites via VPN for secure communications without exposing your internal networks to other consultants.

© 2011 Autodesk Learning Objectives At the end of this class, you will be able to:  Create and distribute virtual Revit Server machines using VMware  Set up central and local Revit Servers  Deploy Revit Server in a VMware® virtual environment  Describe workflows and technical requirements for multi-firm collaboration with Revit Server  Create a Soft-VPN network using LogMeIn Hamachi  Prerequisites:  Understanding of what Revit Server is  Some IT knowledge

© 2011 Autodesk What is Autodesk Revit ® Server?

© 2011 Autodesk What is Autodesk Revit ® Server?  Autodesk Revit Server is the server application for Revit Architecture, Revit Structure, and Revit MEP. and it allows server-based work-sharing for Revit projects across a wide area network (WAN).  The Revit Server network architecture consists of a single central server that connects with multiple local servers.  Revit Server helps speed up work-sharing across WAN. Central Model 1. Updates come in from other users on the Local LAN/WAN 2. Updates are sent to the Local Server cache. 4. Local User updates are pushed via the local server to the Central Server. LAN WAN Local User 3. Updates are made available to Local Users upon their request. Local Server Local User Graphic Courtesy ASI/Autodesk

© 2011 Autodesk Advantages/Challenges for using Autodesk® Revit® Server for Multi-Firm Collaboration

© 2011 Autodesk Advantages:  Any size  Any complexity  Multiple Project Members  Any geographical Location*  For latency <100ms  Concurrent access and modification  Speeds up access for LAN users connected to the Central Server  Speed benefit for WAN users  Always current model for all team members  Better Collaboration

© 2011 Autodesk Challenges  Secure shared connection between multiple firms  Security/Disclosure issues  Cost Issues  Capable Hardware needed  Software License(s) cost  Can be slow/fail due to high latency and network speeds  Educating all team members of working in a shared environment  Need of a technical guru as a liaison/implementer/troubleshooter to work with Multi-firm IT departments  Can only host RVT files  CAD/Raster data need to be linked locally or via shared drive on same server

© 2011 Autodesk Overcoming the Challenges with Autodesk® Revit® Server for Multi-Firm Collaboration

© 2011 Autodesk Secure Network Connections  A secure two-way communications between firms is required  Site to Site VPN using hardware routers  Hardware VPN with VPN Client  Isolating Collaboration network from corporate network  SoftVPN solutions like LogMeIn Hamachi  LogMeIn Hamachi  Much greater flexibility  Easily deployable/managed  Low Cost  Timeout issues need planning and configuring

© 2011 Autodesk Security/Disclosure issues  Problems of everyone sees everything  Possible solution is to have Project based Virtual Revit Servers?  High cost of capable hardware and Software Licenses  Administration nightmare  No granular control, everyone can modify everything  Team members need to be educated  Trust  Creating a secured shared network  Separating corporate traffic from consultants  Hardware based VPN  Software based VPN

© 2011 Autodesk Cost Issues  Capable Server Hardware recommended  Not all Firms may have upgraded equipment  Can be run on a non-server machine  Virtual Servers  Hardware assisted Virtualization a requirement for virtualized 64bit clients  Most newer CPUs provide Hardware assisted Virtualization  Cost of CPUs/RAM for multiple Virtualized clients  Windows Server 2008/R2 64bit required*  Cost of Windows 2008 license(s)  Not all firms have upgraded to Windows 2008

© 2011 Autodesk Can be slow/fail due to high latency and network speeds  Recommended latency requirements are <100ms  High Latency results in communication errors between servers  Check whitepaper on high latency network on  WAN connections are asymmetric (much lower upload speeds)  Smaller Firms may be affected  May result in slower syncs  WAN acceleration devices like Riverbed help  First time opening of models will be slow on WAN connections  Issues with dropped/high latency connectivity  Cannot Save-to-Central  Cannot make changes to model  Can work on Elements already owned  Linked Models may be slow to load  CAD/Linked Data access will be slow if hosted on a WAN server

© 2011 Autodesk Educating team members  Lack of granular controls in Autodesk Revit Server  Admin controls on Revit Server Interface  Issues of Trust  Everyone can modify everything  Separate models for each discipline is still needed  Opening other discipline models could be an issue  All team members working in the model must have unique usernames  Can only connect to ONE Revit Server at a time (even with multiple Revit Sessions)

© 2011 Autodesk Communications  Revit Editing Requests  Telephone  Instant messaging  Skype/AIM/Live Messenger/QQ etc.  Project Bluestreak (  Track project team activities  Stay in constant communication with your project team  Autodesk Bluestreak Desktop PC & iOS client  Share files with your team  Autodesk Revit Activity Stream App

© 2011 Autodesk Need of a technical guru  More than a BIM Manager role  Managing and negotiating with partner firm’s IT departments  IT Technical Expertise (Windows 2008 Server, Hardware, etc.)  Revit Server Expertise  Networking Expertise  TroubleShooter  Goto person for model locks,  Technical glitches  Connectivity issues / High Latency issues  etc

© 2011 Autodesk Installing Autodesk Revit ® Server: Create a Windows Server 2008 R2 VM in VMware Install Revit Server Central/Local

© 2011 Autodesk System Requirements for both Central and Local Servers  Windows Server 2008/2008R2 (64bit)  Secure Network access to all local servers and clients  IIS 7 or IIS 7.5 (R2) .NET 3.51 Virtualized Revit Server environment:  Virtualization software License* to create virtual machine VMware (officially supported), Oracle Vbox, etc.  Windows 2008 Server License  Hardware assisted virtualization support (req. to host 64bit OS)  Preferably a dedicated network card for VM to use

© 2011 Autodesk Creating a distributable Autodesk Revit ® Server

© 2011 Autodesk Create a New Windows Server 2008 R2 VM Vmware Virtualized Revit Server environment: Virtualization software License* to create virtual machine VMware (officially supported), Oracle Vbox, etc. Windows 2008 Server License Hardware assisted virtualization support (req. to host 64bit OS) Preferably a dedicated network card for VM to use

© 2011 Autodesk Installing and configuring Autodesk Revit ® Server 2012

© 2011 Autodesk Configuring SoftVPN LogMeIn ® Hamachi ®

© 2011 Autodesk Hamachi ®  Free version is for non-commercial use.  It is only $199* a year for commercial license. 256 clients  Create an account  Setup a Network  Create a Deployment to send to consultants  Manage users online

© 2011 Autodesk Distributing, Connecting and Using Servers

© 2011 Autodesk References: Help for detailed installing, configuring and troubleshooting can be found at

© 2011 Autodesk Autodesk, AutoCAD* [*if/when mentioned in the pertinent material, followed by an alphabetical list of all other trademarks mentioned in the material] are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2011 Autodesk, Inc. All rights reserved.