© 2011 Autodesk DL4998-P: Connect the Dots – Engineering: Getting the Body Fit Ed Hannabas Business Consultant-Autodesk

© 2011 Autodesk Class Summary  This class is for intermediate to advanced users on the best practices for creating Revit Structural 2012 and Revit MEP 2012 templates. This class will also discuss the workflow and interaction of between engineers and architects as the design process evolves. Information will be provided on the correct setup of preferences for the structural and MEP engineers to achieve maximum results from the Revit models.

© 2011 Autodesk Learning Objectives At the end of this class, you will be able to:  Understand the workflow involved with large projects  Develop an effective plan for setup and templates  Develop an effective workset strategy  Develop best practices for coordination between design teams, and other disciplines

© 2011 Autodesk Understand the workflow involved with large projects

© 2011 Autodesk Planning is the key  Identify Project Team  We will identify certain key roles that should be a part of the project team  Some of these roles are quite different from typical CAD projects  Create a list of the other discipline’s role and contact information

© 2011 Autodesk Training Requirements

© 2011 Autodesk Team Members  Revit Administrator  Collect input from Project Managers in order to setup the project  Define Browser organization and naming conventions and project folder locations.  Develop a modeling work plan  Advise modeling team on best practices  Prepare training documentation for basic and advanced training.  Maintain the Revit Organizational Chart.  Establishes Meeting times and requirements for coordination and interference checks.  Keeping file naming accurate.  Managing the project folder system.  Auditing, compacting and creating new project files as required.

© 2011 Autodesk  Model Manager  Implementation of the modeling strategy and CAD standards.  Coordinate changes with other discipline model managers  Validating the level of detail and controls as defined for each project phase  Participating in design review and model coordination sessions  Communicating issues back to internal and cross-company teams  Properly storing discipline models in the collaborative project management system  Review and fix critical warnings

© 2011 Autodesk  Content Creation Specialist  Responsible for the creation and organization of the project specific families.  Implement style guide or specifications guide on how content shall be created and maintained  Responsible for transferring modeling content from one party to another  Validating modeling content during each phase

© 2011 Autodesk Content Creation Specifications  Family name and category  Materials and finishes  Visibility requirements  Annotation requirements  Symbolic requirements  Scheduling requirements  Sketch or cut sheet information  Approval process

© 2011 Autodesk  Documentation Specialist  Responsible for the organization of views, sheets, drawing lists and print sets.  Manage View Templates.  Coordinate with Project Manager to find out what is required at each submittal.  Confirm that Level of Detail requirement is met with each submittal.

© 2011 Autodesk

Develop an effective plan

© 2011 Autodesk Write it down!  Create a Written Plan  This is needed to identify the workflow and naming conventions for the project  Identify who is responsible for what part of the project  Identify what software is being used in the project Model NameModel ContentProject PhaseAuthoring CompanyAuthoring Tool Architectural Model Architectural objects, code information Conceptualization / Program of Requirements Phase Autodesk Revit Architecture Civil Model Topography, site utilities to within 5 feet of perimeter, hard and soft surfaces, other site objects Criteria Design / Schematic Design Phase Autodesk Civil 3D Structural Model Structural steel members, bearing and shear walls, analytical structural model, lintels Criteria Design / Schematic Design Phase Autodesk Revit Structure Mechanical Model Mechanical systems, equipment, load information, utilities within 5 feet of building perimeter Criteria Design / Schematic Design Phase Autodesk Revit MEP Electrical Model Electrical systems, equipment, load information, utilities within 5 feet of building perimeter Criteria Design / Schematic Design Phase Autodesk Revit MEP Plumbing ModelPlumbing systems, equipment, load information, utilities within 5 feet of building perimeter Criteria Design / Schematic Design Phase Autodesk Revit MEP File Names for Models Should Be Formatted as: DISCIPLINE-Project Number-Building Number.rvt (example: ARCH BL001.rvt) Architectural ModelARCH- Civil ModelCIVIL- Mechanical ModelMECH- Electrical ModelELECT- Plumbing ModelPLUMB- Food Service ModelKITCHEN- Structural ModelSTRUCT- Energy ModelENERGY- Construction ModelCONST- Estimate ModelCOST- Coordination ModelCOORD-

© 2011 Autodesk Level of Development  Review Individual content and modeling requirements  What is the deliverable  Establish Level of Development for each phase or submission

© 2011 Autodesk How Many Models  There needs to be a visual map of all of the models  Their interdependency needs to be understood  Their purpose needs to be clearly identified

© 2011 Autodesk Reference File  Project coordination needs one unique reference system.  This Reference system is based on one or several “Single User” files which contain following information:  Project Base Point X, Y coordinates, Elevation and Angle to True North  Survey Point X, Y coordinates and Elevation  Grids  Levels  Property Lines

© 2011 Autodesk Meeting Schedule

© 2011 Autodesk Analysis Tools

© 2011 Autodesk View Templates and Naming Conventions  View Templates should be created to assist in creating new views  Working and Plotting Views  The present system of naming views with the model views: View Name: - -.  A review process should be put into place to ensure these conventions are being followed.  The Revit Documentation Specialist should establish a schedule for reviewing the model, typically on at least on a weekly basis. A more timely review may become necessary depending on the project timeline and deliverables.

© 2011 Autodesk Develop an effective workset strategy

© 2011 Autodesk Worksets  Workset allocation shall be done in a logical manner that allows for other members of the design team to collaborate and/or assist with the model development without recourse to complicated introductions to the project methodology.  A project shall be broken into a sufficient number of Worksets to avoid congestion in workflow. This also provides the means for adequate control over the efficiency of the model.  The Model Manager shall manage the borrowing permissions and workset ownership.  Too many Workset decrease the efficiency of the Worksharing process.

© 2011 Autodesk

Develop best practices for coordination between design teams, and other disciplines

© 2011 Autodesk Project Review

© 2011 Autodesk Model Management  Create a new Central File and back up Central File at least once a week  Audit and when possible purge the file  Compact the Central File

© 2011 Autodesk Review Warnings

© 2011 Autodesk Upgrading a Project  Everyone SWC relinquishing everything.  Everyone Close Revit.  Everyone delete all locals related to this project.  Backup the Central File (however you do this)  One person open the file in new version.  Agree to warning indicating that your file will no longer be compatible.  Wait for upgrade.  Save local.  Save over the original central, making this file the new central file (option in the save dialog).  Close Revit.  Now test, but it “should” be safe for others to work.

© 2011 Autodesk Autodesk University Session Feedback Your feedback is very important to Autodesk. You can complete the session survey on your mobile device, PC, or at a survey station. Each completed session survey enters you in that day’s drawing for a free AU 2012 pass. You can help make AU 2012 better! Complete the AU Conference Survey at a survey station and receive an AU 2011 T-Shirt.

© 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.