Connect the Dots: A Series of Sessions

Transcription

1 Connect the Dots: A Series of Sessions These sessions will cover the procedures for working in a Large Team Workflow BIM Project. The software products used for these sessions are: Revit Architecture Revit Structure Revit MEP Navisworks Manage The Speakers: Marcus Kim, AIGA, Autodesk Consulting Ed Hannabas Autodesk Charlie Busa Autodesk 1

2 Connect the Dots: Architectural Designing the Body Marcus Kim, AIGA, Autodesk Consulting AB4719-P This course covers the Architectural Workflows as a team begins developing a project model. In addition to typical starting procedures like template setup, model building and workset creation, the collaboration process and strategy will be covered from the Architectural point of view. Learning Objectives At the end of this class, you will be able to: Understand the workflow involved with large projects Understand the importance of effective setup and templates Understand an effective workset strategy Develop best practices for coordination between design teams, and other disciplines About the Speaker Mr. Kim has extensive experience working on, and managing the production of monumental scale architecture projects in both AutoCAD and in Revit. After working in design and technical architecture with Epstein-ISI in Chicago, Illinois, he found the opportunity to move into Design Technology management, where he quickly excelled, and was later recruited by SOM to manage the BIM Program in their Chicago office. At Autodesk, Mr. Kim is a Business Consultant, and has assisted clients from basic to advanced Revit concepts, Revit implementation, and technical training. Mr. Kim has a BA in Architecture from the University of Illinois Chicago and an AAS in Computer Graphics from the American Academy of Art. Mr. Kim is also the chair of the first US Chapter of the internationally acclaimed organization, CGSociety. 2

3 Outline 0.0 Introduction Understand the Workflow Hardware Requirements bit systems bit systems... 5 Recommended 64 bit system Tips and Recommendations The Revit Project Workflow Defined... 8 Pre-Design:... 8 Schematic Design:... 9 Design Development:... 9 Construction Document: Revit Project Setup and Templates Project Browser Organization and Customization Organizing Worksets Revit Coordinate Systems Linking Revit Models Linking CAD Files Effective Collaboration

4 0.0 Introduction Since Revit s conception, it has been the goal of AEC firms to utilize BIM technology in ever growing projects. It wasn t too long ago that Revit projects were small in size, the hardware pushing the Revit files inadequate for the processing of the information. With every release of Revit, and advancements in hardware, the realization of large Revit projects has become a reality. Success for these large projects are still difficult because the procedures and organizational process of how to develop a large project has yet to be formalized, i.e. companies are experimenting with large Revit project workflow procedures. It is the goal of this class, to convey key criteria that are necessary for the success of a large scale Revit project. This section has been developed for the Architectural component of Revit. Though the lecture component of this class is 90 minutes and can cover only so much, the information contained in this packet goes beyond what was discussed and is relevant for the other flavors of Revit. Feel free to utilize the information in any manner you see fit to enhance the development of your Revit projects. 4

5 1.0 Understand the Workflow In order to attempt a project in Revit, there must be an understanding of Revit s workflow process. To begin with, to even attempt a Revit project, considerations must be made for the necessary hardware. It is extremely unforgiving later in a project, if it is discovered that current company hardware standards cannot meet the performance demands of the Revit project file. Similarly, even with the best hardware, when working on a Revit project, the design criteria for the model at each project phase may impact the workflow, not just in performance but in the expedient development of the Revit model. In many cases, companies who attempt the pilot Revit project, often times fail to realize such things as the Revit model s level of detail. For example, a schematic design Revit model which would only be documented at most an 1/8 = 1-0 (or 1:100 for metric projects) is being developed at almost a construction document quality level. Revit projects being developed in this manner can lead to unnecessary expenditure of time as well as impact performance for a project during an early project phase where a high level of detail considerations are not necessary. It is with these two premises that this section covers hardware requirements for a Revit project, as well as a point by point summary of what a Revit model needs to accomplish throughout the various phase of a project. 1.1 Hardware Requirements When working on large Revit projects, it is not enough to have a workstation with the minimum system requirements. Revit projects, especially large projects push extreme amounts of data. With the advent of 64-bit hardware and its availability, it is becoming less of a critical issue. Similarly what is listed as minimum system requirements especially the amount of RAM was considered just five years ago the maximum RAM you could have in a 32-bit system. The current minimum requirements for 32 bit systems Microsoft Windows 7 32-bit Enterprise, Ultimate, Professional, or Home Premium; Microsoft Windows Vista 32-bit (SP2 or later) Enterprise, Ultimate, Business, or Home Premium; or Microsoft Windows XP (SP2 or later) Professional or Home* Intel Pentium 4 or AMD Athlon dual core, 3.0 GHz (or higher) with SSE2 technology for Microsoft Windows 7 32-bit or Microsoft Windows Vista 32-bit (SP2 or later). Intel Pentium 4 or AMD Athlon dual core, 1.6 GHz (or higher) with SSE2 technology for Microsoft Windows XP (SP2 or later) 3 GB RAM 5 GB free disk space The current minimum requirements for 64 bit systems Microsoft Windows 7 64-bit Enterprise, Ultimate, Professional, or Home Premium; Microsoft Windows Vista 64-bit (SP2 or later) Enterprise, Ultimate, Business, or Home Premium; or Microsoft Windows XP Professional x64 edition (SP2 or later).* 5

6 Intel Pentium 4 or AMD Athlon dual core, 3.0 GHz (or higher) with SSE2 technology for Microsoft Windows 7 64-bit or Microsoft Windows Vista 64-bit (SP2 or later). Intel Pentium 4 or AMD Athlon dual core, 1.6 GHz (or higher) with SSE2 technology for Microsoft Windows XP Professional x64 edition (SP2 or later) 3 GB RAM 5 GB free disk space The following system recommendation is best for large Revit projects. Since the adoption of 64-bit systems, the speed of the processors and the available amount of RAM has drastically increased. At a certain point the workstations that are provided to Revit users can be over-kill, so a fine balance should be considered that weighs cost vs performance. Microsoft Windows 7 64-bit Enterprise, Ultimate, Professional, or Home Premium, Microsoft Windows Vista 64-bit (SP2 or later) Enterprise, Ultimate, Business, or Home Premium edition, or Microsoft Windows XP Professional x64 edition (SP2 or later) Quad Core Intel Xeon Processor (2.50 GHz, 2X6M L2, 1333) or equivalent AMD processor 8 GB RAM (or more) 1,280 x 1,024 monitor with true color 1 GB (or more) DirectX 10-capable graphics card with Shader Model 3 for advanced graphics. Tips and Recommendations When considering a workstation for your future projects, remember that the performance of the workstation and the ability of it to be stable when processing vast amounts of information are paramount to success. This is not to say throw money at the hardware requirements but take careful consideration when selecting it. Some points to consider when purchasing a Revit workstation: Processor Cores: Revit only utilizes multiple cores when tasked to render. All other Revit processes currently tasks only one core. Although the total amount of processing power for multiple cores may exceed any of your existing processors, due to the Revit s core usage this may be a downgrade for Revit. Also, when determining Processors, consider the other applications used, such as analysis applications, and visualization applications. What may be just good for Revit would not be as optimal for others System Memory: Best to fill all channels with same type of memory as opposed to mixing types or leaving channels empty. Fill all memory slots (dual / triple channel) as much "dual-rank" (2-, 4, or 8-GB) memory as you can afford. Memory availability is top priority for large Revit projects. In my opinion the standard workstation has 16GB of memory. Have enough memory slots to allow for future memory upgrades economically. 6

7 Graphics: Use an Autodesk certified graphics card that meets rendering and output needs. A graphics card impacts performance in Revit when navigating. It will allow for the best graphical user experience. A Revit Autodesk certified graphics card is recommended. Both AMD and NVIDIA has comparable cards, personally I do not have a preference as long as they are certified. With that said, the Architecture users may have a need for higher end graphics cards due to their need for visualization tasks. Consider the possibility of having two machine configurations. One for Architects, one for engineers Storage: 7200-RPM SATA disks unless large-volume rendering is required Also this will impact performance of certain Revit tasks beyond just rendering. Such as the regeneration of multiple views, printing of large multi-model Revit projects may force Revit to tap into the Virtual RAM. Operating Systems: Should be using a 64-Bit Operating system to deliver maximum memory performance. Remember that the total allowable RAM usage is dependent on the version of the operating for example in the case of Windows 7 the maximum RAM usage is as follows: Closing Comments o Starter: 8GB o Home Basic: 8GB o Home Premium: 16GB o Professional, Enterprise, Ultimate: 192GB Feedback taken from multiple customers has ranked following importance of hardware subsystems: 1. Memory 2. CPU a "very" close second 3. Graphics 4. Storage. As a general statement, the super high end specifications of workstation hardware can be leveraged with best practices such as good workset management, selective workset loading/unloading, and proper modeling procedures for families. However, even with this statement, there will be instances where the top of the line workstation is necessary to produce the final deliverable. To elaborate, you may be able to have a spec for typical Revit user workstation that will accommodate all productions tasks, and have a spec for workstation that can be accessed via RDP, for the final deliverable tasks. 7

8 1.2 The Revit Project Workflow Defined For multi-disciplined projects with a focus on Integrated Project Delivery (IPD), the Architecture workflow is typically the lead process that dictates a Revit project and coordinates all disciplines into one coordinated effort. It is crucial from the onset of a Revit project, that the clarity of the design for the Revit project meets requirements for the final deliverable documentations. Due to the nature of the Architectural Design process, projects are typically separated into the following phases: Pre-Design (PD) Schematic Design (SD) Design Development (DD) Construction Document (CD) The requirements of the Revit model are different for each phase, and therefore it is important to understand what is critical for development at each phase. With this understanding, it is possible to leverage Revit to meet each phase with a tiered solution, maximizing the development of the Revit design and geometry. For the purpose of describing each phase and the possible integration of workflows with other disciplines, responsibilities have been broken down separately into Architectural (A) and Structural (S). Pre-Design: A: Often referred to as Preliminary Design (PD), the pre-design phase involves Architectural Design Teams extensively utilizing modeling and drafting tools to address basic programming project requirements. The design teams will consider multiple iterative design concepts and select a final design solution that meets the project requirements. Often, the tools utilized for this process incorporate other design packages such as, but not limited to, the following: o o o Google SketchUp Rhino AutoCAD Although these tools are appropriate for use early in the design process, a drawback to their use has been the repetition of production effort when the design team moves into the Revit platform. As an alternative, the team can utilize Revit s conceptual modeling tools to develop the design during this phase of the project. The key advantage to this approach is that the conceptual design work produced in Revit can be easily converted to other Revit geometry as the project transitions into subsequent phases. S: Typically structural engineers have minimal involvement in the PD phase, beyond advising the architects on what is possible from an engineering perspective. 8

9 Schematic Design: A: With the Revit conceptual model in place, during the schematic design (SD) phase, the Architectural team will begin to integrate system and model family components to define a more accurate representation of the Revit geometry. During the SD phase, a level of detail (LOD) accuracy of the model is not as necessary, and the team can begin to utilize generic system family components such as walls, floors, ceilings, roofs, as well as a basic kit of model component family parts such as doors, windows, curtain walls to begin defining a more accurate representation of the building. The relevance of the model geometry should meet the SD phase documentation requirements, and preliminary sheets with annotations defined in the Revit project. S: During the latter portions of the SD phase, Structural Engineers will take control of the Levels and Grids of a project, and begin sizing the required structural members. The relevance of the model geometry should meet the SD phase documentation requirements, and preliminary sheets with annotations defined in the Revit project A & S: Begin initial coordination of Revit files. Design Development: A: As the Revit project progresses into the Design Development (DD) phase, generic system families and model component families are replaced with those that contain a higher LOD. During this phase, items such as assemblies for walls, floors, roofs can be further specified, and rooms, schedules, and detailed call-outs such as walls sections and enlarged plans can be further developed. At the end of the DD phase, the accuracy of the Revit model geometry in both LOD accuracy as well as the general I in BIM is in place. S: Engineers will continue to further develop the super-structure of the building, also including analytical calculations to validate the integrity of the structure. Further refinements to the LOD of the model are also made, including but not limited to foundations, columns, framing, re-bar, schedules, and call-outs such as wall sections and details. At the end of the DD phase, the accuracy of the Revit model geometry in both LOD accuracy as well as the I in BIM is in place. A & S: Weekly coordination of Revit files among all disciplines involved, including MEP. Construction Document: A & S: With the majority of the modeling now complete, during the CD phase both Architecture and Structural disciplines are considered to be in an additive workflow. The model geometry as defined in the DD phase has changed little, but through an additive process, views are created defining the highest LOD required in a set of construction documents. Final considerations are made regarding information contained within the schedules, and the information is reviewed for compliance. 9

10 Closing Comments The workflow as outlined defines a workflow for a Design, Bid, Build type project. In the case of Design Build projects, there will be differences in the Level of Detail requirements for each phase. Having an understanding of the Revit requirements for the Design Build project prior to execution will be paramount for success. 10

11 2.0 Revit Project Setup and Templates Of important consideration is how a Revit project is started from the configuration standpoint. How the Revit template is set up, and configuration of critical items such as the Project Browser organization, and justification of Revit s coordinate system would allow for ease of user interaction with the file, as well as a consistent understanding of how the files relate spatially. As Revit project files get larger, and such things as worksharing is enabled, further strategies, some as simple as having a file naming convention, or more complex concepts such as a well defined workset strategy will facilitate a more coordinated Revit project, and set the Revit production team for success. 2.1 Project Browser Organization and Customization Creating views is the method utilized to derive the appropriate Plans, Sections, Elevations, Callouts from the Revit model. You are not limited to a finite number of views that can be created, and therefore it is important to organize the views in the project browser. This becomes increasingly important later in a project where we will have hundreds if not thousands of views that are utilized for multiple purposes such as working views, sheet views, export views, coordination views etc. By default Revit organizes views by Category, (i.e. Floor Plans, Ceiling Plans, Elevations, Sections, Legends, Schedules, and Sheets), then alpha numerically. (Figure 2.1a) The main problem with this type of sequencing is that the default categories will have way too many views assigned to them. What if you had more than one Level 2 view, what if you had five? How would you be able to differentiate between them? The Project Browser is organized and sequenced based on parameters that are listed in the view properties. Because of this, you can customize the way the Browser is organized from the Browser Organization Properties window. This can be accessed from the View Tab User Interface Browser Organization. 11

12 The Browser Organization Properties (Figure 2.1b) By specifying an option in the Group by parameter, you have the ability to sequence how the Project Browser categorizes and lists the views that you create. (Figure 2.1c) In Figure 2.1c you can see by the settings that the view is categorized by Discipline then by the view Family. In this method, you can separate the views in clearly defined Categories, and have the ability to easily navigate the Project Browser For increased flexibility in the Project Browser, you can create additional parameters for the View Properties. Custom parameters can be added from Project Parameters tool listed in the Manage Tab. In the following example (Figure 2.1d), custom instance view parameters were created from the Project Parameters Window. View Usage View Type 12

13 (Figure 2.1d) Both the View Usage and View Type parameters have pull down menus. All available View Usage and View Type parameters are available to you. Once you specify these parameters, the view will be listed in the appropriate section of the Project Browser. If you do not specify a View Usage and a View Type parameter, the view will be listed in the??? section of the Project Browser. This is done because the parameters were not assigned to the view. Important Note: The organization method of the Project Browser should be controlled by the Project Team Lead or the BIM Manager. The project team must be educated on how to categorize and assign views. Just remember a created view does the team no good, if no one can find it. 13

14 3.0 Organizing Worksets Worksets are utilized in Revit s work-sharing environment. The worksets allow you to divide up the Revit model so that multiple people can work on them. Although many users are tempted, do not think or worksets as layers. Think of Worksets as assemblies and components. In AutoCAD it is perfectly appropriate to have a layer for wall, door, window, but in Revit you may have worksets such as Exterior Envelope, Podium, Core, FFE. In Large Revit projects, how you separate the model into worksets will be the difference between a stream-lined Revit model and a large clumsy model. Through the effective use of worksets, it provides extreme advantages for the Revit team developing the project. As a note, because of the advantages of worksets, even single user Revit projects are often converted to the work-sharing enabled. At the time Revit worksharing is enabled, elements that are not part of a standard Revit workset are assigned to a default Workset1. After the project workset names are defined, the model objects in Workset1 are allocated to the new worksets. Although you have the ability to rename any workset, it is recommended that you keep the name of Workset1 as named because this is the one default workset that can never be deleted from the Revit project. Workset1 can be used as a temporary workset for those unsure of what workset to assign a model object. A 3D view with Workset1 visible can be used periodically to re-assign these temporary elements to more appropriate worksets. Effective Workset Strategy: An effective workset strategy for a large Revit project allows the Revit team to selectively filter what information is loaded into the available RAM of the user s workstation. Each workset can be loaded or unloaded from the Worksets manager when you start the project. (Figure 2.2a) 14

15 If you choose No for a workset, as the Revit file opens it will not load model objects that are assigned to the workset to the physical RAM. In Figure 2.2a you can see how the worksets for Site and FFE are being turned off at startup. The worksets that are turned off are also specific to the Local file and will not affect other users. Ultimately, by only selectively opening worksets that you need will allow for a lighter Revit file that is more responsive and can be easily manipulated. In the event that you need to see the information from a workset, then it is just a matter of turning it back on. The Shell workset turned on (left) and turned off (right) (Figure 2.2b) Important Note: Just remember to turn all worksets on when you are ready to print. This will ensure that the views you set up for print will be complete and without issue. Workset Naming: Implement a good workset naming convention. As a best practice, one person on the project team such as the team lead should be responsible for the maintenance and creation of the worksets. Typical team members should not create worksets on their own. If you allow this, you will see your Revit project spin quickly out of control. When new worksets are created, be sure to communicate this to the Revit team. New worksets are of no use if no one utilizes them. As a sample convention, the naming could follow this convention: [DISC] [SYSTEM] [ZONE] Examples: ARCH-Core-Entry ARCH-Shell-Base ARCH-Rooms-Level01 INTR-Demising INTR-FFE-Level01 INTR-Units-Ballroom HVAC-Equipment SITE-Planting What is important about the naming convention is that it is clear and easy to understand. You want to make sure that the Revit team assigns developed model geometry onto the correct worksets. Important Note: One of the biggest problems that can occur on a Revit project is when vast quantities of Revit objects assigned to wrong worksets. This causes the entire workset strategy to become ineffective. The first line of defense is educating your Revit project team on the importance of worksets. Defining a clear understandable workset naming convention helps take the guess work away. 15

16 4.0 Revit Coordinate Systems In the process of sharing Revit models on a collaborative project, one of the most important considerations is the basis of a common coordinate system. Agreement on a fixed point that represents the (X=0, Y=0, Z=0) will allow for an easy and consistent means of referencing Revit and CAD data into the host Revit model. The determination of this point as a best practice should be a major part of a BIM project kick off plan. This section will define the components of the Revit coordinate system, and best practices for project configuration. In Revit there are two main coordinate systems that must be considered, the project internal, and shared. Both have features and limitations. Utilizing the correct coordinate system properly will allow for the easiest collaboration of the Revit models, as well as any additional supporting CAD based files. Project Internal: Every Revit file has a Project Internal coordinate system referred to as Project. This is referenced in several locations in Revit such as the export settings for CAD files, within the type properties of level datum for the Elevation Base, and type properties of Spot Coordinate objects. (It is strongly recommended that all Revit geometry is created within 1 mile of this point.) The Project Internal coordinate system is equivalent to the WCS (World Coordinate System) commonly utilized by other 3D applications. Therefore in Revit, the true origin (0, 0, 0) of the Project Internal coordinate system, referred as the Start Up Location, is a fixed point in the Revit file that cannot be changed. Also, an associated component of the Project Internal coordinate system is the direction of the Y-axis is representative of Project North. This setting is default in all orthogonal views, and recommended that your building geometry has a direct relationship to the Project North, as it would be viewed on a Sheet. Shared Coordinates: Simply, the Shared Coordinate is a user defined coordinate system that has an origin point and a rotational value that defines the True North in relation to the Project North. The Shared Coordinate can be synchronized between multiple Revit models, and AutoCAD drawings. Through the Shared Coordinates, it would be possible to specify an alternate coordinate system with an origin that represents the (0,0,0) of a geodetic survey marker, or a station pin. Important Note: In Revit there is no visible graphic icon that represents the Project Internal coordinate system. As a default when you start a new Revit project utilizing the out of the box template, two objects belonging to the Site category, Project Base Point, and Survey Point coincide with the Project Internal coordinate system. Moving the Survey Point (SP) away from Start Up Location sets the user defined Shared Coordinate. (Figure 4.0) 16

17 The following examples show the possible configurations of the Project Internal coordinate system, the Shared Coordinate, the Survey Point, and the Project Base Point. Figure 4.1 Example A Figure 4.1 Example B (Figure 4.1) The Project Internal (PI), Project Base Point (PBP), and Survey Point (SP) all in alignment. The grids were constructed so that the intersections of Grid 1 and Grid A coincide with the Start Up Location (SUL) of the PI. The direction of the Project North and True North are parallel. (It is strongly recommended that a relationship is made between the grid system and the Project Internal coordinate system.) The PI and PBP are in alignment. The grids were constructed so that the intersections of Grid 1 and Grid A coincide with the SUL of the PI. The SP has been relocated to coincide with the bottom left intersection of the property line which creates a user defined Shared Coordinate. The direction of the Project North and True North are parallel. (Figure 4.2) Figure 4.2 Example A The PI and PBP are in alignment. The grids were constructed so that the intersections of Grid 1 and Grid A coincide with the SUL of the PI. The SP has been relocated to coincide with the property line. A rotation of 45 degrees has been added to the survey point which denotes the direction of True North from Project North. The view of Example A has been oriented to be orthogonal with Project North. 17

18 Figure 4.2 Example B The PI and PBP are in alignment. The grids were constructed so that the intersections of Grid 1 and Grid A coincide with the SUL of the PI. The SP has been relocated to coincide with the property line. A rotation of 45 degrees has been added to the survey point which denotes the direction of True North from Project North. The view of Example B has been oriented to be orthogonal with True North. Important Note: The examples A and B of Figure 5.2 convey identical information. Only the orientation of Project North and True North are represented differently. In Revit you can rotate the direction of True North from the Manage Tab Position Rotate True North. (Figure 4.3) Figure 4.3 Example A Figure 4.3 Example B The intersection of Grid 1 and Grid A is aligned to the PI. The SP has been relocated to coincide with the bottom left intersection of the property line, which creates a user defined Shared Coordinate. The PBP has been un-clipped* (see following section for clipped and un-clipped definitions) and moved away from the PI creating a new unique (0, 0, 0). In this example there are three independent coordinate systems that have been developed. The PBP has been un-clipped* (see following section for clipped and un-clipped definitions) and moved away from the PI creating a new unique (0, 0, 0). The SP has been relocated to coincide with the bottom left intersection of the property line, which creates a user defined Shared Coordinate.The intersection of Grid 1 and Grid A is aligned to the PBP. In this example there are three independent coordinate systems that have been developed.!!!this is not a recommended configuration!!! Important Note: In the case of Figure 4.3, Examples A and B. The PBP was un-clipped and moved away from the location of the PI. The PBP in this case creates a new independent (0, 0, 0) The origin defined by the PBP is not to be confused with the Start Up Location (0, 0, 0) of the PI. Unless your project requires another reference point beyond the Survey Point (SP), it is recommended that the Project Base Point (PBP) always stay in alignment to the Project Internal (PI) 18

19 Clipped vs Un-Clipped: In the previous section, we examined the Project Base Point (PBP), and the Survey Point (SP). The location of these objects in relation to the Project Internal (PI), defines additional coordinate systems. In the case of the PBP and the SP, each object can be in a Clipped state and an Un-Clipped state. (Figure 5.4) (Figure 4.4) As a default when starting a new Revit project from the default out of the box template. The SP and the PBP are aligned to the PI (See Figure 4.4, G.). These three coordinate systems are in perfect alignment. To see the PBP and SP graphically in Revit, go to the default Site view, or from any plan view go to the Visibility Graphics, go to the Site category and check the boxes for Project Base Point and Survey Point. The PBP and the SP can be selected independently. As a default the PBP and the SP are in a clipped state (See Figure 4.4, B and D). When you independently select the PBP or SP, it will show you tracking data to the right of the symbol (See Figure 4.4, H and J). The tracking data reports the pertinent (X, Y, Z) of the PBP and the SP. The following examples describe the Clipped and Un-Clipped characteristics of the Project Base Point (PBP) and the Survey Point (SP) 19 (Figure 4.5)

20 In Figure 4.5, both the SP and the PBP are Clipped. Note the following characteristics. The PBP is in alignment with the Project Internal. The tracking data of the PBP will always report the position relative to the Shared Coordinate The origin of the SP is the same as the (0, 0, 0) of the Shared Coordinate. The tracking data is reporting the SP s position relative to the (0, 0, 0) origin of the Shared Coordinate. Rather you move the Clipped PBP, or you move the Clipped SP, the relationship between the two points are identical. i.e. You are performing the same operation. Important Note: The Internal reference to the tracking data of the Survey Point is the default name assigned to the Shared Coordinate. The name of the Shared Coordinate can be updated from the Location Tool available in the Manage Tab. (Figure 4.6) In Figure 4.6, The Survey Point was first relocated in the same manner as described in Figure 4.5. Afterwards the PBP and the SP were Un-Clipped and moved. Note the following. The position of the Project Internal and the Shared Coordinate remains in the same position. The tracking data of the Un-Clipped PBP is reporting its position relative to the (0, 0, 0) of the Shared Coordinate The tracking data of the Un-Clipped SP is reporting its position relative to the (0, 0, 0) of the Shared Coordinate The position of the PI does not impact the tracking data of the PBP nor the SP. 20

21 Important Note: Unless it is absolutely critical to have an additional point beyond the Shared Coordinate origin, keep the PBP aligned to the Project Internal origin. TIP and Trick: Why Un-Clip the Survey Point (SP) and move it? You may have a situation where the origin of the Survey Point represents the origin of a Geodetic Survey Marker. This point may be miles away from your Revit Geometry which has a close proximity to the Project Internal. When you Un-clip the Survey Point you do not impact the origin of your Shared Coordinate. You can then move your Un- Clipped Survey Point in close proximity to your project. Major Advantages are as follows: By having the SP and PBP within close proximity, Revit will not have to compute the miles of virtual space. Revit will be happier from a computational standpoint and With the SP and PBP visible, when performing a Zoom Extents. Revit will not zoom out in such a way that items are too small to be visible 21

22 5.0 Linking Revit Models Coordinating Revit models is a very important part of collaboration between disciplines. It is through the linking of Revit models that we are able to share information. In Revit we reference other models into our Revit model by linking them into place. Section 1.0 discussed the various coordinate systems within Revit. It is with the understanding of the coordinate system that a linking strategy can be devised. When doing any Revit project, there are only two methods that can be seriously considered. Linking by Auto - Origin to Origin Linking by Auto - Shared Coordinates Linking by Origin: We looked at the Project Internal (PI) coordinate system which has a true (0, 0, 0) origin. When multiple Revit models are involved, by coordinating the model geometry in relation to the true internal origin allows for the easiest means of overlaying model information. In practice, an example would be utilizing the PI to represent the intersection of grids at the lower left limit of a project. Linking models with this origin as a common point of reference will ensure that the Revit project models will be lined up correctly. (Figure 5.0) This method is the easiest and most straightforward method of ensuring the proper alignment of models. Within Revit, the Link Revit window, the Auto - Origin to Origin will automatically align the Project Internal origin of one model with the Project Internal origin of another. Important Note: The Auto Origin to Origin only aligns the PI of the referenced model to the PI of the host model. Do not confuse the PI with the PBP. 22

23 Linking by Shared Coordinate: An alternative means to referencing Revit models is through the use of Shared Coordinates. This method is useful when the Revit models involved have no common origin (Figure 5.1) In Figure 5.1, because the Project Internal origin is different for the Architecture model and the Structural model, an alignment based on Auto Origin to Origin would result in an undesirable alignment of the building geometry. (Figure 5.2) In Figure 5.2, the Survey Point of the architecture model was relocated to the bottom left corner of the property line. The Structural model was then referenced in and manually aligned by matching the grid lines. The Survey Points of the two models were synchronized, allowing for a common Shared Coordinate. Important Note: Developing a Shared coordinate system is an intricate process and must be thoroughly planned out prior to implementation. 23

24 6.0 Linking CAD Files CAD files can be referenced in to your Revit model for coordination. Similar to Revit files they can be referenced by two primary methods which will help maintain alignment. Linking by Auto Origin to Origin Linking by Auto Shared Coordinates Linking by Origin: We looked at the Project Internal (PI) coordinate system which has a true (0, 0, 0) origin. This point coincides with the World Coordinate System (WCS) (0, 0, 0) of CAD based files. If the geometry contained within the CAD files have the same relationship to the WCS, as Revit geometry has a relationship to the PI, the alignment of the two points would bring the geometry together. This would be similar to the condition shown in Figure 6.0. Linking by Shared Coordinate: An alternative means to referencing CAD files is through the use of Shared Coordinates. Initially when CAD files are referenced, only the Auto Origin to Origin, Auto Center to Center, and the various Manual placement methods are applicable. Once the CAD file is placed in Revit, align the CAD geometry so that there is a relationship to the Revit geometry. See Figure 3.0 (Figure 6.0) Important Note: In Figure 6.0, the construction of the CAD file denotes the geometry at a 30 degree angle from the X-axis of the WCS coordinate system. The direction of the Y-axis is representative of the True North direction. The alignment of the CAD file was achieved by linking the CAD file into Revit, and then rotated to have the same orthogonal grid conditions as the grids in the Revit file. By doing this there is clear representation of Project North and True North Utilize the Acquire Coordinates command in Revit and select the CAD file. This will synchronize the coordinates between the Cad File and the Revit File 24

25 Upon Synchronizing the CAD and Revit file, the Revit file will automatically align the Survey Point to the WCS. (See Figure 7.1) You can then synchronize the Shared Coordinate of the Revit file to any other Revit file that is referenced. Once the Shared Coordinate is establish between the files, you can begin linking in your CAD file by Shared Coordinates to any Revit file that has a synchronized Survey Point. (Figure 6.1) Best Practice: Civil Engineers will call out the location of the Architects building based off of real coordinates. The (0, 0, 0) of the engineer s coordinates can therefore be the Survey Point of your Revit file. The advantages of the Survey Point in Sync with the origin utilized by Civil will allow for the easiest collaboration between the Architect and the Civil Engineer. Similarly when exporting Revit data to a CAD format, the export by Shared Coordinates feature will ensure that the exported CAD data will utilize the same coordinate system as the Civil Engineer. 25

26 7.0 Effective Collaboration Copy Monitor Collaboration Review Navisworks This section is briefly covered in the lecture Connect the Dots: Architectural Designing the Body. For more detail on this subject, see the final section of this series, Connect the Dots: Minding the Whole 26

27 Connect the Dots Engineering: Getting the Body Fit Speaker(s) Ed Hannabas-Autodesk Code DL Minute Seminar: 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. Learning Objectives At the end of this class, you will be able to: Understand the workflow involved with large projects Understand the importance of effective setup and templates Understand an effective workset strategy Develop best practices for coordination between design teams, and other disciplines About the Speaker Ed Hannabas has over 25 years of experience in the building industry working with both architects and engineers. For the past five years, he has worked with engineering firms across the country implementing Autodesk Revit MEP and Revit Structure. He also assists in creating content in order to speed up their start up process. His prior experience in the building industry included working for firms that included projects from single story office buildings to multi-story office buildings, churches, hospitals, industrial projects, and hotels. He has served in the role of CAD manager and also as a project coordinator Understand the workflow involved with large projects Revit Structure and MEP Standards: To successfully implement Revit Structure and Revit MEP in your firm, it is vital to establish and document standards for your company. These standards are quite a bit different from the CAD standards that we have had for years. These standards should include drafting conventions, file management and naming conventions, and role definitions for personnel involved in Revit projects. To use Revit successfully a clearly defined management team should be defined, something most firms have not had to address, other than appointing a project engineer. There are many more roles necessary in a Revit project. 27

28 In the previous paragraph, drafting conventions were placed in parenthesis to emphasis that this is much more involved when using the Revit software. We are no longer concerned with layers, but we are concerned about the appearance of our final documents. The creation of standard View Templates is essential to producing consistent construction documents. Templates should be created not only for floor plans and elevations, but also for your details and sections. 28

29 It is becoming increasingly more common to group views in working and printing groups. This is especially true for the HVAC and piping where often different colors are used to differentiate systems within each of these disciplines. The MEP project browser is typically broken up by discipline, then further divided by the type of plan, either floor or ceiling plans. Our primary concern in the past has been the file structure of the Windows environment. Once we enter the Revit environment, the file structure of the project browser takes on a greater importance. It is essential that a clearly defined system for the naming views is established and it must be strictly enforced. The creation of additional view filters is sometimes utilized to more closely match a firms previous naming conventions; a naming system for sheets should also be clearly delineated. One item often overlooked is to establish a naming convention for families which can often lead to duplicates or the family being used. Project Browser Organization Creating views is the method utilized to derive the appropriate Plans, Sections, Elevations, Callouts from the Revit model. You are not limited to a finite number of views that can be created, and therefore it is important to organize the views in the project browser. This becomes increasingly important later in a project where we will have hundreds if not thousands of views that are utilized for multiple purposes such as working views, sheet views, export views, coordination views etc. Revit Structure Project Browser 29

30 Revit MEP project Browser By default Revit organizes views by Category, (i.e. Floor Plans, Ceiling Plans, Elevations, Sections, Legends, Schedules, and Sheets), then alpha numerically. 30 (Figure 3.0)

31 The main problem with this type of sequencing is that the default categories will have way too many views assigned to them. What if you had more than one Level 2 view, what if you had five? How would you be able to differentiate between them? The Project Browser is organized and sequenced based on parameters that are listed in the view properties. Because of this, you can customize the way the Browser is organized from the Browser Organization Properties window. This can be accessed from the View Tab User Interface Browser Organization. The Browser Organization Properties (Figure 3.1) By specifying an option in the Group by parameter, you have the ability to sequence how the Project Browser categorizes and lists the views that you create. (Figure 3.2) 31

32 In Figure 3.2 you can see by the settings that the view is categorized by Discipline then by the view Family. In this method, you can separate the views in clearly defined Categories, and have the ability to easily navigate the Project Browser For increased flexibility in the Project Browser, you can create additional parameters for the View Properties. Custom parameters can be added from Project Parameters tool listed in the Manage Tab. In the following example (Figure 3.3), custom instance view parameters were created from the Project Parameters Window. View Usage View Type (Figure 3.3) Both the View Usage and View Type parameters have pull down menus. All available View Usage and View Type parameters are available to you. Once you specify these parameters, the view will be listed in the appropriate section of the Project Browser. If you do not specify a View Usage and a View Type parameter, the view will be listed in the??? section of the Project Browser. This is done because the parameters were not assigned to the view. Important Note: The organization method of the Project Browser should be controlled by the Project Team Lead or the BIM Manager. The project team must be educated on how to categorize and assign views. Just remember a created view does the team no good, if no one can find it. 32

33 Revit Structure Standards: One item of additional concern for Revit Structure users are the settings for rebar cover has this will ensure that the rebar is inserted by code or by the correct design criteria. Standard abbreviations can also be established in the structural template to ensure consistent nomenclature in tags. Structural Settings The values that are entered on this tab reflect the plotted representation of the drawings. Therefore, the visible representations that are set with these values will change based on the view scale of the drawing. 33

34 Analytical Model Settings: 34

35 When enabled, automatic analytical model checking provides a warning when the analytical model of your project may not be correct. Use these settings when most of the structure has been modeled and you need to monitor if changes made to the model cause elements to become unsupported or analytical models to become inconsistent. It is not recommended to enable these setting in the early stages of a project. The number of elements unsupported during model creation is significant. The Tolerances options set tolerances for both the Analytical/Physical Model Consistency check and the Auto-Detect of the analytical model. Support distance. Specifies the maximum allowable distance between the physical model of an element and the physical model of the supporting element. If it exceeds this tolerance, a warning is issued during a consistency check. Analytical-to-physical model distance. Specifies the maximum allowable distance between the analytical and physical model. If it exceeds this tolerance, a warning is issued during a consistency check. Analytical adjustment distance. Specifies the maximum allowable analytical model distance from the default location. If it exceeds this tolerance, a warning is issued during a consistency check. Horizontal auto detect. Specifies the maximum horizontal distance between the analytical and physical model. Vertical auto detect. Specifies the maximum vertical distance between the analytical and physical model. If you are a Subscription Member you can download the Extensions for Revit 2012 and this gives you some additional resources for selecting and defining structural parts. 35

36 Revit MEP Standards: Revit MEP users typically require a longer set up time than the other disciplines in order to have a usable template. So much of the other disciplines are driven by international codes or standards, whereas MEP information is typically not that well defined. It is sometimes necessary to have several templates in order to comply with different jurisdictions and codes. Each discipline within MEP must establish default settings in order for the software to perform as anticipated. 36

37 The Electrical discipline also has a number of options to setup. Load Classifications are next. In the Load Classifications dialog, specify the load classification type, using one of the following methods: o From the left pane, select an existing type. o Click to add a new load classification type. 37

38 o Click to copy an existing type. o Click to rename a load classification selected from the list. Click to delete load classifications that are not assigned to connectors in the project. Demand factors are assigned to load classifications, and load classifications are assigned to device connectors. The estimated load for a device is calculated by multiplying the load by the demand factor. Building and Space settings. Revit provides default schedules and settings for the building and space parameters used to calculate heating and cooling loads. You can adjust many of these settings to change the default values used for heating and cooling loads analysis. This allows you to establish parameters for the overall building model, and then modify individual spaces to create an accurate analysis for heating and cooling loads. 38

39 Panel Schedules. On the Modify Panel Schedule Template tab, you can specify the formatting options, as shown in the table here. To edit a template Click Manage tab Settings Panel Panel Schedule Templates Edit a Template. If you want to... then... 39

40 define primary settings click Set Template Options. Examples are schedule width and circuit table format. add a parameter select a cell, then select a category and click add Parameter. See Adding Panel Schedule Parameters. remove a parameter select a cell, then click cleared of parameters. Remove Parameter. The column is create a parameter to add to the template use the Project Parameters dialog. See Creating Project Parameters. format the unit of measure select a cell, then click Format Unit. Change the units or unit symbol and click OK. See Setting Project Units. add a calculated value to a cell select a cell, then click Calculated Value. See Adding a Formula to Panel Parameter Types. combine parameters select a cell and click Panel Parameters. Combine Parameters. See Combining freeze or unfreeze the height and width of all rows and columns click. You can continue to resize frozen rows and columns using Resize Column and Resize Row, but are prevented from resizing them using grips. 40

41 insert a column select cells, then select an placement option from the Column drop-down menu. Insert delete a column select cells, then click Delete Column. resize a column select cells, then select Resize Column and specify a value in the dialog. Select multiple columns to set them all to one size. insert a row select one or more rows, then select a placement option from the Insert Row drop-down menu. delete a row select one or more rows and click Delete Row. resize a row select one or more rows, then click value in the dialog. Resize Row and specify a merge or unmerge cells select multiple cells, then click Merge/Unmerge. insert a graphic select one or more cells, then click specify the image file. Insert Graphic and edit cell borders select one or more cells, then click Edit Borders and specify 41

42 line weight and cell border. edit shading select cells, then click Edit Shading. See Shading Phase Columns in Single-Phase Panels. edit a font select cells, then click Edit Font. horizontally align text in the rows under a column heading select cells, then select an alignment option from the Horizontally Align drop-down. vertically align text in the rows under a column heading select cells, then select an alignment option from the Vertically Align drop-down. finish editing the template click Finish Template. cancel the edits made to the template click Cancel Template. 42

43 It may also be necessary to modify the Project Units for the different disciplines, HVAC, Electrical or Piping. As Revit MEP continues to expand its analysis and design capabilities the user has the ability to fine tune equipment, fittings and parts to aid in this process. Possible values are: Not Defined, Coefficient, and Specific Loss for mechanical equipment. Pipe fittings loss methods can now be tied to an ASHRAE table. You can also go to this site and download a viewer that shows you the ASHRAE tables and the fitting it is attached to. This is a plugin for Revit MEP 2012 and it will appear as a TAB on the ADD-INS. This will show you the values for duct fittings. 43

44 Once we have established our basic settings for our templates we are now ready to assemble our project team. Organizing Worksets: Worksets are utilized in Revit s work-sharing environment. The worksets allow you to divide up the Revit model so that multiple people can work on them. Although many users are tempted, do not think or worksets as layers. Think of Worksets as assemblies and components. In AutoCAD it is perfectly appropriate to have a layer for wall, door, window, but in Revit you may have worksets such as 1st Floor Framing, Exhaust Systems, Exterior Envelope, Vertical Circulation, Core, or Roof Framing. In Large Revit projects, how you separate the model into worksets will be the difference between a stream-lined Revit model and a large clumsy model. Through the effective use of worksets, it provides extreme advantages for the Revit team developing the project. As a note, because of the advantages of worksets, even single user Revit projects are often converted to the work-sharing enabled. This separation provides the user the ability to divide up the model if the model becomes too large as the project progresses. At the time Revit worksharing is enabled, elements that are not part of a standard Revit workset are assigned to a default Workset1. After the project workset names are defined, the model objects in Workset1 are allocated to the new worksets. Although you have the ability to rename any workset, it is recommended that you keep the name of Workset1 as named because this is the one default workset that can never be deleted from the Revit project. Workset1 can be used as a temporary workset for those unsure of what 44

45 workset to assign a model object. A 3D view with Workset1 visible can be used periodically to re-assign these temporary elements to more appropriate worksets. Effective Workset Strategy: An effective workset strategy for a large Revit project allows the Revit team to selectively filter what information is loaded into the available RAM of the user s workstation. Each workset can be loaded or unloaded from the Worksets manager when you start the project. (Figure 4.0) If you choose No for a workset, as the Revit file opens it will not load model objects that are assigned to the workset to the physical RAM. In Figure 4.0 you can see how the worksets for Site and FFE are being turned off at startup. The worksets that are turned off are also specific to the Local file and will not affect other users. Ultimately, by only selectively opening worksets that you need will allow for a lighter Revit file that is more responsive and can be easily manipulated. In the event that you need to see the information from a workset, then it is just a matter of turning it back on. The Shell workset turned on (left) and turned off (right) 45

46 (Figure 4.1) Important Note: Just remember to turn all worksets on when you are ready to print. This will ensure that the views you set up for print will be complete and without issue. Workset Naming: Implement a good workset naming convention. As a best practice, one person on the project team such as the team lead should be responsible for the maintenance and creation of the worksets. Typical team members should not create worksets on their own. If you allow this, you will see your Revit project spin quickly out of control. When new worksets are created, be sure to communicate this to the Revit team. New worksets are of no use if no one utilizes them. As a sample convention, the naming could follow this convention: [DISC] [SYSTEM] [ZONE] Examples: ARCH-Core-Entry ARCH-Shell-Base ARCH-Rooms- Level01 INTR-Demising INTR-FFE-Level01 INTR-Units-Ballroom HVAC-Equipment SITE-Planting What is important about the naming convention is that it is clear and easy to understand. You want to make sure that the Revit team assigns developed model geometry onto the correct worksets. Important Note: One of the biggest problems that can occur on a Revit project is when vast quantities of Revit objects assigned to wrong worksets. This causes the entire workset strategy to become in-effective. The first line of defense is educating your Revit project team on the importance of worksets. Defining a clear understandable workset naming convention helps take the guess work away. Revit Coordinate Systems: In the process of sharing Revit models on a collaborative project, one of the most important considerations is the basis of a common coordinate system. Agreement on a fixed point that 46

47 represents the (X=0, Y=0, Z=0) will allow for an easy and consistent means of referencing Revit and CAD data into the host Revit model. The determination of this point as a best practice should be a major part of a BIM project kick off plan. This section will define the components of the Revit coordinate system, and best practices for project configuration. In Revit there are two main coordinate systems that must be considered, the project internal, and shared. Both have features and limitations. Utilizing the correct coordinate system properly will allow for the easiest collaboration of the Revit models, as well as any additional supporting CAD based files. Project Internal: Every Revit file has a Project Internal coordinate system referred to as Project. This is referenced in several locations in Revit such as the export settings for CAD files, within the type properties of level datum for the Elevation Base, and type properties of Spot Coordinate objects. (It is strongly recommended that all Revit geometry is created within 1 mile of this point.) The Project Internal coordinate system is equivalent to the WCS (World Coordinate System) commonly utilized by other 3D applications. Therefore in Revit, the true origin (0, 0, 0) of the Project Internal coordinate system, referred as the Start Up Location, is a fixed point in the Revit file that cannot be changed. Also, an associated component of the Project Internal coordinate system is the direction of the Y-axis is representative of Project North. This setting is default in all orthogonal views, and recommended that your building geometry has a direct relationship to the Project North, as it would be viewed on a Sheet. Shared Coordinates: Simply, the Shared Coordinate is a user defined coordinate system that has an origin point and a rotational value that defines the True North in relation to the Project North. The Shared Coordinate can be synchronized between multiple Revit models, and AutoCAD drawings. Through the Shared Coordinates, it would be possible to specify an alternate coordinate system with an origin that represents the (0,0,0) of a geodetic survey marker, or a station pin. Important Note: In Revit there is no visible graphic icon that represents the Project Internal coordinate system. As a default when you start a new Revit project utilizing the out of the box template, two objects belonging to the Site category, Project Base Point, and Survey Point coincide with the Project Internal coordinate system. Moving the Survey Point (SP) away from Start Up Location sets the user defined Shared Coordinate. (Figure 5.0) 47

48 The following examples show the possible configurations of the Project Internal coordinate system, the Shared Coordinate, the Survey Point, and the Project Base Point. (Figure 5.1) Figure 5.1 Example A Figure 5.1 Example B The Project Internal (PI), Project Base Point (PBP), and Survey Point (SP) all in alignment. The grids were constructed so that the intersections of Grid 1 and Grid A coincide with the Start Up Location (SUL) of the PI. The direction of the Project North and True North are parallel. (It is strongly recommended that a relationship is made between the grid system and the Project Internal coordinate system.) The PI and PBP are in alignment. The grids were constructed so that the intersections of Grid 1 and Grid A coincide with the SUL of the PI. The SP has been relocated to coincide with the bottom left intersection of the property line which creates a user defined Shared Coordinate. The direction of the Project North and True North are parallel. (Figure 5.2) Figure 5.2 Example A The PI and PBP are in alignment. The grids were constructed so that the intersections of Grid 1 and Grid A coincide with the SUL of the PI. The SP has been relocated to coincide with the property line. A rotation of 45 degrees has been added to the survey point which denotes the direction of True North from Project North. The view of Example A has been oriented to be orthogonal with Project North. 48

49 Figure 5.2 Example B The PI and PBP are in alignment. The grids were constructed so that the intersections of Grid 1 and Grid A coincide with the SUL of the PI. The SP has been relocated to coincide with the property line. A rotation of 45 degrees has been added to the survey point which denotes the direction of True North from Project North. The view of Example B has been oriented to be orthogonal with True North. Important Note: The examples A and B of Figure 5.2 convey identical information. Only the orientation of Project North and True North are represented differently. In Revit you can rotate the direction of True North from the Manage Tab Position Rotate True North. (Figure 5.3) Figure 5.3 Example A Figure 5.3 Example B The intersection of Grid 1 and Grid A is aligned to the PI. The SP has been relocated to coincide with the bottom left intersection of the property line, which creates a user defined Shared Coordinate. The PBP has been un-clipped* (see following section for clipped and un-clipped definitions) and moved away from the PI creating a new unique (0, 0, 0). In this example there are three independent coordinate systems that have been developed. The PBP has been un-clipped* (see following section for clipped and unclipped definitions) and moved away from the PI creating a new unique (0, 0, 0). The SP has been relocated to coincide with the bottom left intersection of the property line, which creates a user defined Shared Coordinate. The intersection of Grid 1 and Grid A is aligned to the PBP. In this example there are three independent coordinate systems that have been developed.!!!this is not a recommended configuration!!! Important Note: In the case of Figure 5.3, Examples A and B. The PBP was un-clipped and moved away from the location of the PI. The PBP in this case creates a new independent (0, 0, 0) The origin defined by the PBP is not to be confused with the Start Up Location (0, 0, 0) of the PI. 49

50 Unless your project requires another reference point beyond the Survey Point (SP), it is recommended that the Project Base Point (PBP) always stay in alignment to the Project Internal (PI) Clipped vs. Un-Clipped: In the previous section, we examined the Project Base Point (PBP), and the Survey Point (SP). The location of these objects in relation to the Project Internal (PI), defines additional coordinate systems. In the case of the PBP and the SP, each object can be in a Clipped state and an Un-Clipped state. (Figure 5.4) As a default when starting a new Revit project from the default out of the box template. The SP and the PBP are aligned to the PI (See Figure 5.4, G.). These three coordinate systems are in perfect alignment. To see the PBP and SP graphically in Revit, go to the default Site view, or from any plan view go to the Visibility Graphics, go to the Site category and check the boxes for Project Base Point and Survey Point. The PBP and the SP can be selected independently. As a default the PBP and the SP are in a clipped state (See Figure 1.4, B and D). When you independently select the PBP or SP, it will show you tracking data to the right of the symbol (See Figure 5.4, H and J). The tracking data reports the pertinent (X, Y, Z) of the PBP and the SP. The following examples describe the Clipped and Un-Clipped characteristics of the Project Base Point (PBP) and the Survey Point (SP) (Figure 5.5) 50

51 In Figure 5.5, both the SP and the PBP are Clipped. Note the following characteristics. The PBP is in alignment with the Project Internal. The tracking data of the PBP will always report the position relative to the Shared Coordinate The origin of the SP is the same as the (0, 0, 0) of the Shared Coordinate. The tracking data is reporting the SP s position relative to the (0, 0, 0) origin of the Shared Coordinate. Rather you move the Clipped PBP, or you move the Clipped SP, the relationship between the two points are identical. i.e. You are performing the same operation. Important Note: The Internal reference to the tracking data of the Survey Point is the default name assigned to the Shared Coordinate. The name of the Shared Coordinate can be updated from the Location Tool available in the Manage Tab. (Figure 5.6) In Figure 5.6, The Survey Point was first relocated in the same manner as described in Figure 1.5. Afterwards the PBP and the SP were Un-Clipped and moved. Note the following. The position of the Project Internal and the Shared Coordinate remains in the same position. The tracking data of the Un-Clipped PBP is reporting its position relative to the (0, 0, 0) of the Shared Coordinate The tracking data of the Un-Clipped SP is reporting its position relative to the (0, 0, 0) of the Shared Coordinate The position of the PI does not impact the tracking data of the PBP nor the SP. 51

52 Important Note: Unless it is absolutely critical to have an additional point beyond the Shared Coordinate origin, keep the PBP aligned to the Project Internal origin. One new practice that has emerged is the creation of a file that contains only grid lines and levels. This serves as a master file that is linked into all models and eliminates the duplication of these elements. This file serves as the point of origin for all models. The ownership of this file needs to be established before the project begins. Model Mapping: Once the Project Team has been assembled, it becomes necessary to develop a map or plan for how the model will be divided up. Generally, large project models should be split into smaller parts, by wings, floors, discipline, etc.. The primary purpose of this split is to maximize performance. Work stations processing smaller chunks of the building will allow the user to be more efficient. This method can also allow different disciplines to better control the content of their models. Working on a portion of the building can also make software operations and screen regeneration time decrease. The two main ways of splitting a project into multiple files are based on location/function and discipline. The location/function style could be based on wings, floors, or different buildings on a campus. This breakup of the model will vary from project to project based on the size of the model and/or the location of team members. Also, parts of the model to be created in traditional CAD software or other platforms should be identified and a means of importing and exporting documents should be established. Level of Detail: A Level of Detail Table should be created to establish the protocols, expected levels of development, and authorized uses of Building Information Models and assigns specific responsibility for the development of each Model Element to a defined level of development at each project phase. The following tables will ensure teams are not over modeling and that the correct level of development is met for each identified phase. 52

53 53

54 The final table will resemble this: There are several examples of this type of table out from the AIA and many other organizations. The main purpose here is establishing a set of guidelines to assist each discipline in the development of the model and their families. Revit Structure and MEP Project Teams: The time spent before actual design begins working the Architects, Structural Engineers, MEP Engineers, Interior Designers and the other disciplines involved in an upcoming project cannot be over stated. The faster that decisions can be made on the makeup of a project, the less rework and lost production time there will be later on. Typically, one of the first decisions made is whether or not a project will use shared coordinates. The introduction to this paper identified how this project was positioned and the options available to the project team. Key team players should be identified as soon as possible; Design Manager and Revit Administrator - should be appointed to oversee the entire project and all disciplines. The structural and MEP team should also assign members to certain key roles. 54

55 Model Manager or Revit Champion - should be assigned to assist with team member problems, implementation of the modeling strategy and CAD standards. This person will also be responsible for the coordination of levels and grids of all MEP, Structural and Architectural Models, coordinates changes with other discipline model managers, validating the level of detail and controls as defined for each project phase, combining or linking multiple models, participating in design review and model coordination sessions, communicating issues back to internal and cross-company teams, review and fix critical warnings, and modify architectural elements inside the Structural Models (Stairs, Elevators, Doors, and Openings). Content Creation Specialist - this person is should also be assigned as the one responsible for the creation and organization of the project specific families, transferring modeling content from one party to another, and validating modeling content during each phase. Revit Documentation Specialist - assigned to the team to be responsible for organizing and assigning type marks to elements (annotations); responsible for the organization of views, sheets, drawing lists and print sets, responsible for the organization of imported files and exported files, be responsible for exporting to CAD and Navisworks, manage View Templates, coordinate with Content Manager for what needs to be in content for appropriate views, coordinate with discipline Design Manager to find out what is required at each submittal, and confirm that Level of Detail requirement is met with each submittal. Office Model Manager - should be appointed if several offices are involved in the project and utilized as a primary point of contact between the different offices. The addresses and phone numbers of each individual should be compiled and published in a list that is made available to all project members. The chart on the following page provides graphic representation of the various roles and their interaction with other disciplines. 55

56 Revit Structure Workflow: Now that standards and templates have been created and we have outlined our plan on where we are going to model, we can actually begin to work on our model. The structural workflow is in large part dictated by the Architect. Typically, the first item of consideration is to determine if there will be a live link to the Architectural model or, if the model will only be updated at predefined times. A decision should also be made about whether the architect or the structural engineer will control the grid system. With the decisions being made, the structural team can begin creating the model template file. The structural team can decide on the number of work sets that will be necessary for the project and start identifying any special content that might be necessary for the project, trusses, slabs, piers, columns, etc. Upon receipt of the first copy of the Architectural model, the structure team can begin to work. It is a good practice to create a 56

57 work set for each linked model to help control their positioning and visibility. Once the architect s model is linked in, the next step would be to copy in the levels the architect has created. Upon completion, the structural team can then begin creating their views for their model. At the same time, if the Architect created the grid lines, they can be copied in. Revit 2011 has made it easier to manipulate and even tag objects from a linked file. The next step in the process is to identify if any other elements are necessary to be copied or monitored from the architectural model. This determination will be based on conversations with the architect and on the project itself. In many cases the copying or monitoring of the levels and grids is all that is necessary. At this point the structural team can start to create the structural model by adding in structural walls and columns. One point to consider at this juncture is if any analysis software is going to be used. This can have a large impact on the modeling process. Typically, analysis packages work the best with Revit when the model is exchanged in small pieces rather than modeling two or three floors at one time. The importing and exporting of small pieces tends to result in less errors or problems. There are numerous analysis programs on the market and it would be almost impossible to go into all the workflows involved in just one article. One aspect of the Revit workflow that is often overlooked is the continued coordination of work internally within the team and externally with the other teams. It is good practice to have some type of Instant messenger service for the various teams to provide a way to communicate more easily to all team members. Voice mails are often missed and the same is true for s. This instant messenger service is also a good method to avoid editing requests between project members. Members within the structural team should always keep everyone within the team aware of what they are working on. This is especially true of administrative functions such as naming and creating views and sheets. A decision should be made within the team on who will perform coordination reviews and in every case a report should be generated and disseminated to all team members. The same can be said for interference detection process. It is generally a good practice to perform internal interference checks, even if Navisworks is being utilized for the entire project. Overall coordination of the entire project is one of the most challenging tasks in a Revit project. There should be regular meetings of all the Model Managers, usually on a weekly or biweekly basis. During this meeting the schedule should be reviewed to make sure everyone is on track. Any model issues and other items that have arisen since the last meeting should be addressed and assignments or deadlines should be issued to ensure all issues are resolved or marked for follow up. There is also a need to have a meeting of only Model Managers for conducting review of the interference conditions. Out of this meeting a plan should be generated on who is responsible for correcting the issue and a deadline should be established for completion of the corrections. It is also essential that a support network be established in writing so all project members know who to contact if a problem arises. This should be a layered approach with the Revit Champion for each discipline being the first point of contact. There should also be guidelines established for how long each level of support spends on an issue before it is escalated to the next level. For instance if the Revit Champion cannot resolve the issue in thirty minutes, the issue then 57

58 would be pushed up to the next level of support, typically the Revit Administrator. The Revit Administrator can then determine if the issue needs to be forwarded to Autodesk Support. Upon completion of the project, the workflow should not stop. An after-action or lessons learned report should be created and disseminated to everyone involved in the Revit process. This will result in the reduction of repeating the same mistakes in the next project and elevate the knowledge base of the Revit process. There should also be a review of each discipline s model to determine if any items created during the project need to be transferred to the discipline s template. Families created during the project should also be reviewed to determine if alterations need to be made to make them applicable to future projects. The Revit workflow is an evolving process that may never end. Revit MEP Workflow: Now that we have our standards and templates created and we have outlined our plan on we are going to model, we can begin work on our model. The MEP workflow is in large part dictated by the Architect. Typically, the first item of consideration is if the is a live link to the Architectural model or if the model will only be updated at predefined times. A decision should also be made about whether the architect or the MEP engineer will control the grid system. With the decisions being made, the MEP team can begin creating the model template file. The MEP team can decide on the number of work sets that will be necessary for the project and start identifying any special content that might be necessary for the project, trusses, slabs, piers, columns, etc. Upon receipt of the first copy of the Architectural model, the MEP team can begin to work. It is a good practice to create a work set for each linked model to help control their positioning and visibility. Once the architect s model is linked in, the next step would be to copy in the levels the architect has created. Upon completion, the MEP team can then begin creating their views for their model. At the same time if the Architect created the grid lines, they can be copied in also. Revit 2011 has made it easier to manipulate and even tag objects from a linked file. The next step in the process is to identify what if any other elements are necessary to be copied or monitored from the architectural model. This determination will be based on conversations with the architect and on the project itself. In many cases the copying or monitoring of the levels and grids is all that is necessary. One new feature of Revit MEP is the ability to batch copy fixtures from the Architectural model. This allows for much easier workflow especially for the plumbing and piping disciplines. 58

59 One item to consider at this point is that if the Architectural and MEP teams are located in the same office or even for the same firm in different locations, is to create a library of fixtures and equipment that are shared between the disciplines. This would allow the MEP team to copy the original from the Architect s file and reduce duplication of effort on the part of the MEP team. The next task for the MEP team is to decide if the MEP model is to going to be split up between disciplines. The first item of concern is how much interaction is there going to be between the disciplines. It is common practice to separate the plumbing model on very large projects, due to the complexity of the plumbing model. Many times there are three separate models for MEP, one for each discipline. At this point the MEP team can start to create the MEP model by adding in spaces and zones. The workflow in MEP typically would next perform some type of analysis on the model. The Revit MEP software is capable of performing analysis organic to the software. This has been a subject that has been greatly debated on the value of performing analysis using the Revit software. At the very least it provides the MEP designer with at least some values to begin the design. 59

60 Once spaces and zones have been placed the Revit file can be exported via GBXML to a variety of analysis software packages for HVAC or lighting design. This analysis information can then be imported back into the Revit model to fill in design information within the spaces and zones. The Revit MEP model can also be exported to Autodesk 3DS Max software for point to point light calculations. At this point the MEP designers can begin to place equipment and fixtures in the model. The designers would then begin to layout the main trunk lines, panels or main pipes. It is a best practice to not connect all of the branches until the design process has evolved enough to reduce the amount of modifications to the model. It is also advisable to create small systems and add equipment to these systems and gradually increase the size of each system. The Revit System Browser should be utilized to keep track of equipment and fixtures that have not been added to a system. 60

61 One aspect of the Revit MEP workflow that is often overlooked is the continued coordination of work internally within the team and externally with the other teams. It is a good practice to have some type of Instant messenger service for the various teams to provide a way to communicate more easily to all team members. Voice mails are often missed and the same is true for s. This instant messenger service is also a good method to avoid editing requests between project members. Members within the MEP team should always keep everyone within the team on what they are working on. This is especially true of administrative functions such as naming and creating views and sheets or naming systems. A decision should be made within the team on who will perform coordination reviews and in every case a report should be generated and disseminated to all team members. The same can be said for interference detection process. It is generally a good practice to perform internal interference checks, even if Navisworks is being utilized for the entire project. Overall coordination of the entire project is one of the most challenging tasks in a Revit project. Typically, there should be a regular meeting of all the Model Managers, usually on a weekly or biweekly schedule. During this meeting the scheduled should be reviewed to make sure everyone is on track. Model issues and other items that have arisen since the last meetings should be addressed and assignments or deadlines should be issued to ensure all issues are resolved or marked for follow up. There is also a need to have a meeting of only the Model Managers for conducting review of the interference conditions. Out of this meeting a plan should be generated on who is responsible for correcting the issue and a deadline should be established for completion of the corrections. It is also essential that a support network be established in writing so all project members know who to contact if a problem arises. This should be a layered approach with the Revit Champion for each Discipline typically being the first point of contact. There should be guidelines established for how long each level of support spends on an issue before it is escalated to the next level. For instance if the Revit Champion cannot resolve the issue in thirty minutes, the issue then would be pushed up to the next level of support, typically the Revit Administrator. The Revit Administrator can then determine if the issue needs to be forwarded to Autodesk Support. Upon completion of the project, the workflow should not stop there. An after action or lessons learned report should be created and disseminated to everyone involved in the Revit process. This will result in the reduction of repeating the same mistakes in the next project and elevate 61

62 the knowledge base of the Revit process. There should also be a review of each discipline s model to determine if any items created during the project need to be transferred to the discipline s template. Families created during the project should also be reviewed to determine if alterations need to be made to make them applicable to future projects. Review Warnings: This is one aspect that is often overlooked in the overall workflow, but it is a critical element to keeping the model functioning properly. As team members work they receive warning that are often ignored or overlooked while in the design process. However, over time these warnings begin to affect the performance of the model. These warnings should be reviewed on a regular basis and resolved in order to keep the model operating in the most efficient method. 62

63 Collision Detection: It is very important prior to the commencement of the project to establish how interference conditions will be monitored and corrected. A regular series of meetings between all disciplines should be scheduled on a recurring basis. The results of these meetings should set a deadline or timetable for interference conditions to be resolved. It is also crucial to identify what means will be used to track these interference conditions, whether Revit will be used to identify these conditions or some other software such as Autodesk Navisworks will be used. This workflow should be documented so that all team members know what is expected of them. Final Remarks: In order to achieve a successful project and meet deliverables, it has very little to do with the software, but very much to do with the management of the project. A BIM execution plan should be written and distributed to all project members prior to the commencement of the project. The identification of content and information required for the project need to be identified as soon as possible. There are numerous examples of these BIM execution plans available to provide a template to get you started. In very large projects, this is especially important as it is often difficult to change direction once a project has begun. Much like a large ship, you can change course, but if you wait too late to make that decision you will often hit something in the process. 63

64 Connect the Dots: Wrap Up - Minding the Whole Charlie Busa - Autodesk DL5452-P The primary focus of this class is the assembly of the overall model in Autodesk Navisworks and how the model can be used to help the entire team gain a better understanding of the project. Workflow processes for exporting the Autodesk Revit models, aggregating the models in Navisworks, and reviewing the results of interference detection will be covered. This class will also review the entire series of classes and help to tie them all together. Best practices around team planning, workflow planning, and team expectations are key to a successful BIM project and will be covered in the second portion of the class. Learning Objectives At the end of this class, you will be able to: Understand best practices for setting up and performing collision detections in a Revit BIM project. Understand how to setup your Revit models to ease import and use in Navisworks Manage Learn Collision Detection strategies and planning Know the steps needed for successful project review meetings About the Speaker: With nearly two decades of industry experience Charlie specializes in building design automation, process, and workflow improvement, as well as standards implementation. He provides consulting and training services for architectural and engineering firms to help define, implement, and improve their design technologies. A frequent instructor at AU, and now an employee with Autodesk Consulting, he has served as an AEC Technical Consultant and now a Business Consultant since Charlie is also a co-author of the book Introducing Autodesk Revit Architecture charlie.busa@autodesk.com 64

65 65

66 Building Model Clash Detection: The goal of clash detection is to report physical interferences between building objects and also to verify that required clearances exist between model elements. Determining these interferences early in the project during the design stages will reduce and potentially eliminate major design changes late in the project and unexpected interferences being discovered during construction. The results will be smoother flowing and more profitable design phases and also a more predictable construction phase that continues on schedule with a reduced number of change orders. Being the final stage of BIM design project this action is completely dependent on having well-crafted and accurate 3D BIM models created by the various team members involved in the project. If the models are not accurate the clash detections cannot be relied upon to produce valuable information. 66 As with all other aspects of a BIM project planning the clash detection procedures is highly recommended beginning when the BIM project plan is created. This documentation will provide a framework that will guide the project participants through the entire project and will detail the clash detection requirements, procedures and responsible parties. Without a plan to perform the clash detections the results may be unreliable or not representative of what is required by the client and project. Planning: While there will be areas of consistency across all projects each project will have different objectives for the clash detection procedures. Having these objectives identified very early in the project and then specific definitions created to meet the objectives will allow the project team to prepare for the clash detection procedures. Vague goals of 100% clash free models do not provide enough information to the project team to enable them to efficiently check the model. There are beneficial, the good, clashes that help to create the building structure and maintain building performance and detrimental clashes, the bad, that require redesign and/or change orders. The goal of running clash detection is to identify all of the bad clashes during the design stage of the project and collaboratively determine the best solutions for both the project team and the overall project. Clash Detection Requirements: The BIM project plan will contain a listing of specific interference types that will not be accepted by the client at model delivery. The interference types should be itemized by discipline or by element type so that it is clear to the entire project team what items will need to be checked and what items they will need to be checked against. This listing will be used as a guide for the clash detection requirements and procedures for the building

67 project. Large BIM projects are made up of multiple files. The various consultants involved in the project will typically produce at least one file per discipline and in some cases multiple files per discipline. Each discipline and file will need to be organized into a clash detection process matrix that outlines which disciplines and files will be clash checked and against which other disciplines and files. This matrix will provide a guide to dividing the Navisworks models into sets for clash detection runs. The matrix may be generated in a text format or as a graphic as illustrated below. Element Categories Categorizing the building model elements and defining the types of clash detection interrogations is the next step in preparing the model. Based on the clash detection matrix created earlier the project team can build selection sets in Navisworks to be used during the clash detection runs. Using the matrix as a starting point for creating the sets will help the project team check the model for unwanted clashes while also keeping within the project guidelines. The categorization of model elements should be done at both the Major and Minor levels. The categories will be created in conjunction with the clash elimination requirements listed in the BIM project plan. The information contained in the BIM project plan will describe the type of clash detections that will be required for final model delivery and which element types will need to be checked against which. Specific categories will vary by project and project type but here are some category examples applicable to this building project. Architecture o Walls o Floors o Ceilings o Curtainwall Systems o Roofs 67

68 Structure o Foundations o Structure o Floors Mechanical o Equipment o Pipe o Ducting Plumbing o Supply o Waste Electrical o Equipment o Fixtures o Devices Fire Protection o Piping o Controls Fixture, Furnishings and Equipment o Casework o Furnishings Other o By Project Model Preparation: Based on information gathered during the Planning, Clash Detection Requirements and element categories steps the design team can begin preparing the Revit models for clash detection use. The Revit models are the preferred place to begin the clash detection setup as the design team is the team responsible for ensuring the final delivered design meets the clash detection requirements established earlier in the project. It is easier for the design team to assign elements to the appropriate categories which will then be used during the clash detections. A series of Revit parameters created in each project file will allow the design team to categorize the elements as needed to match the original project objectives. These parameters can then be searched and selected using the Find Items tools in Navisworks for actual clash detection use. Scheduling: Clash Detection interrogation typically begins the design development phase, at about 35% of project completion. In some projects clash detection interrogation may begin earlier if sufficient modeling decisions have been made and modeling completed. Once the process has begun it is a regularly scheduled operation that is part of the project workflow. The specifics of how clash detection will be incorporated into the project 68

69 should be identified in the project plan. Having this information prior to beginning the clash detection process will set expectations for the entire project team. Model Clash detection examinations will be performed numerous times throughout the duration of the project. As the project progresses clash detections will be run to verify that previously identified clashes have been resolved and to determine if any new clashes have been created. Clash Detection Review For optimum results representatives from all firms on the project team should assemble as scheduled and review the clash results live on the same screen. This provides an opportunity for all team members to see and understand the clash as a group. Once the clash is understood the people present in the room can make decisions on how to best resolve and eliminate the clash. Modeling may or may not be a part of the review meeting as determined by the project team. The more important aspects are to have decisions made during the meeting for resolving any clashes that were detected during the process. Firms that are responsible for multiple disciplines within the project should resolve and eliminate any clashes within their scope of responsibility prior to the team review meeting. When it is not practical to setup a team meeting where all can be in the same room the next best method is by way of internet based technologies. The final option is to export reports from Navisworks Manage and distribute to the team for clash resolution and elimination. This will also require some type of interactive meeting, whether internet based or telephone to reach a decision on how to best resolve complex clashes. Steps for Clash Detection: 1. Create Revit Parameters 2. Assign Values to Parameters 3. Setup Views in Revit Models 4. Export Geometry 5. Import Geometry 6. Setup Views 69

70 7. Select Geometry / Create Selection Sets 8. Run Clash Detective 9. Review Results 10. Share Results 11. Update Geometry in Project Models 12. Export Geometry to NWC 13. Update Navisworks NWF 14. Re-run Clash Detective 15. Review Results 16. Share Results 1. In Revit - Create Shared Parameters for use in Navisworks to help define the clash detection selection sets. Utilizing shared parameters will allow the use of the same parameters in different Revit files. The parameters may be a mix of Type and Instance. A total of 6 parameters should be sufficient to define effective search sets in Navisworks. 2. In Revit Assign values to the Shared Parameters based on information obtained earlier in the project. This can be done at each instance through type properties but may be easiest by building a schedule that allows you to change many items quickly without searching the model. The schedule also gives you a fast method of perusing the model to see if there are items that have had assignments missed. 3. In Revit - Setup a specific 3D view for exporting the building models. Turn off display of the model elements that you do not need to include in the clash detection. Any elements contained in the Revit RVT project file that are not visible in the view will not be exported to the Navisworks NWC file. In addition determine whether the linked files should be exported or not and change the export setting. (See Settings Listing in Appendix A) 4. In Revit - Export the view to NWC file format for use in Navisworks Manage. The Add-Ins tab contains the Navisworks 2011 export plug-in tool. The NWC file format is the only file format the exporter can create. 5. In Navisworks - Create a New file in Navisworks and Append the NWC file into the file. I suggest creating all of the NWC files that are part of your firm s modeling responsibility and then 70

71 Append the multiple NWC files in one step. Use Project Internal Coordinates when exporting the NWC file(s) unless the project has been setup using shared coordinates. 6. In Navisworks - Setup and save views that will be used to visualize the model. The views will also provide a repeatable method of reviewing specific views of the model for verifying correct assembly or review. 7. In Navisworks Based on the matrix and categorization already determined select objects and create search sets using the custom parameters and their values. The Properties tab in the Selection Tree window provides a very fast and easy method of reviewing the parameters and sub-parameter settings that have been included in the NWC file. Review the model and then create the search sets using Find Items. 8. Create selection sets from the search sets and retain the search sets for later use. The Clash detection runs should be performed using selection sets so that the runs can be reproduced exactly when verifying whether the clashes have been resolved or not. Search sets are fluid and will change with any model or object parameter changes. The selection sets can be created under Major category folders by discipline or model author in the Sets window making selection of sets for clash detection logical and intuitive. 9. In Navisworks Create clash tests in Clash Detective and then run the clash detections. Once the clash tests have been created and steps 7-11 completed the same tests can be re-run to verify that collisions have been eliminated. 10. In Navisworks Review the results. Ideally the review is done live with all of the project consultants in one room where clash resolutions can be discussed and a plan of action determined to eliminate the clash. 11. In Navisworks If needed export the Clash Detection results to the project team for remote review. The project team will receive 71

72 both a text listing of each clash and also an image of the clash for easy identification. 12. In Revit Update model geometry based on the decisions made after reviewing the previous clash detection results. During the review process, whether it is done in one location or remote, the responsibility for eliminating the clash is assigned to one of the disciplines. Arriving at the best decision for the overall project will be much easier in one location, particularly for complex clashes. 13. In Revit Export view to NWC and use the same file name therefore overwriting the original NWC file. The NWC files are linked into the NWF file and will be updated in the NWF file when opened. 14. In Navisworks Re-open the NWF file so that the Navisworks model is up to date. NWC files are automatically updated when the file is opened and are linked into the NWF. 15. In Navisworks Re-run the clash detections that were saved in the previous clash detection checks. The clash detections saved from the earlier interrogations can, and should, be re-used so that the test is exactly the same. 16. In Navisworks Review the results as before ideally the project consultants will all be assembled in one room for the review session. 17. In Navisworks - If needed export the Clash Detection results to the project team for remote review. Items number 8-14 repeat until no detrimental clashes are found in the BIM model. Project Planning The previous four sessions covered the steps involved when working as part of a large team on a Revit project. The technologies used to create the BIM project and the processes have fundamentally changed many aspects of project interaction and assembly. Being successful in a Large Team Workflow project requires more than just intelligent use of the software tools. To fully succeed project teams will need to review and adapt their current workflow processes to better fit the new workflows that are needed when involved in a BIM project. The workflows can also benefit non BIM projects but will be clearly beneficial in BIM. 72

73 Many organizations have come to understand how important the planning stage of the project is and how much the planning can impact the success of the project. There are numerous project plan templates available on the internet from numerous sources, including Autodesk. These documents are referred to by a variety of names such as BIM Execution Plan, Project Execution Plan, Project Plan, Etc. Regardless of their exact titles these plans all have been created with the goal of helping the project team stay coordinated throughout the duration of their projects. You can refer to these templates to gather ideas on how to create a template that best serves your organization s needs. Proper planning at the kickoff stage of a project will reduce the number of project problems that occur during the course of the project. Develop a template for BIM projects that encompasses all that you anticipate needing in your future BIM projects. While the individual projects will always have unique requirements the template can act as a checklist to ensure that all team members including owners, and contractors if already selected, have a clear understanding of the roles and responsibilities of the project team. 1) Project &Team Outline a) Project Goals b) Firm Names and Roles c) Project Team contact information and responsibilities d) Staffing Plan 2) Contractual Obligations a) Project Schedule b) Project Phases c) Construction Sequencing Models 3) Model Guidelines a) Model Plan b) Level of Development c) Model Use d) Derivative Model Use e) Design Ownership f) Model Sharing/Exchange Plan g) Modeling Level of Detail 4) Data Guidelines a) Data Requirements b) Data Level of Development c) Data Output Requirements d) Data Schedule Requirements e) Material Take-Offs/Quantities 5) Interference (Clash) Detection a) Clash Detection Requirements b) Clash Detection Schedule c) Clash Detection Coordinator 73

74 d) Clash Detection Meeting Location(s) 6) Deliverable Documents a) Paper b) Electronic DWG or DGN c) Electronic 2D, PDF & DWF d) Electronic 3D Dumb Models (DWG, DGN) e) Electronic 3D Intelligent Models (NWD, DWF, IFC) f) Visualization & Animation g) Full BIM Model This list represents many of the types of information that should be coordinated at the beginning of a project. Having this information readily available for all project participants removes many of the questions that will arise as the project progresses. Once design has begun the key element for BIM success will be team communication. The all too familiar habit of working in isolation where you only share information with other team members when necessary will cause much consternation across the entire project team. There should be open communication between different disciplines and also within the discipline teams themselves so that the amount of unnecessary labor or re-work is greatly reduced. This will not happen without good team communication. Usually the project models are shared live when working within the same firm and often when working with external consultants. Once the model has been shared all parties linking the model will see any changes the next time they open their files. The easiest method to ensure good communication is for the project team to hold frequent meetings as the design progresses and participation in the meetings should be required. This will foster an open relationship among the project team members and lead to a more successful project. Project leads and Project Managers can help the team to hold their regular meetings and to make them productive. Links to Sample BIM Plans: Autodesk, Inc. BIM Deployment Plan USACE USACE PxP PSU BIM Project Execution Planning Guide and Templates IU Building Information Modeling Guidelines and Standards 74

75 Appendix A: NWC Exporter Settings: The window below shows settings that will provide all of the data needed from the Revit model to easily setup the Clash detections in Navisworks. (Figure 1) Figure 1 Convert construction parts Parts created from original model elements will be exported to the NWC file. If parts have been used in the project this setting should be enabled. Note that even if parts have been hidden in a view they will be exported when enabling this setting, not the original element Convert Element IDs Creates a properties tab labeled Element ID with the Revit ID listed. If not enabled the Revit ID is available on the ID properties tab. Convert Element Parameters: o None No parameters from the Revit model are exported to the NWC file and only the basic 75 Figure 2

76 properties available in Navisworks are available in the Navisworks session. Note that any custom or element parameters will not be available in Navisworks. (Figure 2) o Elements Exports a partial list of element parameters and all custom parameters. This creates an Elements Properties listing in the Selection tree properties tab. (Figure 3) Figure 3 o All In addition to the parameters exported using Elements the All option includes additional object information such as Base Level, Base Offset, Phase Information and more. (Figure 4) o o Convert element properties Adds project specific types of information to the export such as Workset ID, Assembly Information and original part information if parts are enabled. (Not Shown) Convert linked files When enabled linked files (Revit & CAD) are included in the exported NWC file. If there is a master file for the building model this can be the simplest method of exporting to Navisworks from Revit. The linked files are available as sub items in the selection tree under the master model and all parameters and properties are included. (Figure 5) Figure 4 Figure 5 o o o Convert room as attribute Includes the room properties of elements placed in a room, furniture, Etc but does not include the room volume. Convert URLs Includes any URL information attached to model elements as a property. Coordinates determines whether the model is exported using the Project internal coordinate system or the current Shared Coordinate System. Use the current project setting for export. 76