Embed Size (px)
Citation preview
MOSCOW 2016
CORPORATE BIM GUIDEFor Building/Construction Projects
(Revit® and AutoCAD® Civil 3D®)
TEMPLATE
Revision 2.0
ABOUT THIS DOCUMENTDeveloped by CONCURATOR, LLC
AUTHORS
Neboysha Novkovich, ConcuratorSenior Technical Consultant
Sergey Benklyan, ConcuratorSenior Project Manager
Igor RogachevAutodesk Certified InstructorAutodesk Elite Expert, Autodesk Civil 3D Certified Professional
Ilya Yemelyanov, Autodesk ConsultingTechnical Consultant, AEC Solutions
Petr Manin, AutodeskTechnical Director
Alexander Popov, AECOM RussiaBIM Manager
Roman Mitin, CISPChief Development Officer
Dmitry Chubrik, BIM for BusinessCEO
Alexander Osipov, BIM AcademyCEO
Alexander Zuyev, BIM AcademyBIM Planner
REVIEWERS
Andrey Shakhramanyan, SODIS LABCEO
Andrey Yaremenko, SODIS LABHead of BIM Department
Arsentiy Sidorov, NTC EtalonCEO
This guide is based on the experience of Autodesk Consulting.Autodesk Consulting team has been developed both national (NBIMS, PAS) and corporate BIM Guides for companies from Europe, Middle East, Asia, USA and Russia in AEC, mining and infrastructure industries.
This Guide is a part of Russian country kit, which, in addition, contains three project templates (Architectural, Structural and MEP), and a set of basic Revit families and template descriptions.
All additional materials are specific for Russian norms and regulations and are only available in Russian; therefore, this delivery consists of English version of BIM Revit Guide only. All extra files will be made available upon request.
II
DISCUSSION FORUM
If you have any questions or comments on this standard, please visit: http://autode.sk/2dfAFSp
If you want to adopt this standard in your organization, please do not hesitate to contact us: [email protected]
TERMS OF USE
This standard may be freely distributed and used in any format necessary, for the purpose of development corporate BIM Guides. Reference to this standard is required in all derived documents.
Autodesk, Inc. © 2016. All rights reserved.
III
TABLE OF CONTENTSNew Versions of Project Templates and Shared Parameter File..............................................8
Terms and Definitions Section: What’s New and Changed.......................................................8
The Naming System: What’s New and Changed.......................................................................8
3D Coordination: Significant Additions to the Validation Process..............................................9
1 SCOPE.....................................................................................................................................13
2 NORMATIVE REFERENCES...................................................................................................14
3 TERMS AND DEFINITIONS.....................................................................................................15
4 SETTING UP AND ORGANIZING THE BIM PROCESS.........................................................21
4.1 Employer Information Requirements (EIR)........................................................................21
4.2 BIM Execution Plan (BEP).................................................................................................21
4.3 Roles and Responsibilities.................................................................................................22
4.4 Resources..........................................................................................................................24
4.5 Common Data Environment (CDE)....................................................................................26
4.6 Basic Rules of BIM Data Exchange...................................................................................29
4.7 Data Security & Saving......................................................................................................29
4.8 Folder Structure and Naming Conventions........................................................................29
4.9 Model File Naming Conventions........................................................................................31
4.10 Data Exchange Formats and Interoperability..................................................................32
4.11 Revit® Settings.................................................................................................................33
4.11.1 Configuring Revit® Global Settings............................................................................33
4.11.2 General Revit® Content Naming Rules......................................................................34
4.11.3 Loadable Family Naming Rules................................................................................35
4.11.4 Loadable Family Type Naming Rules.......................................................................36
4.11.5 System Family Type Naming Rules..........................................................................36
4.11.6 Workset Naming Rules..............................................................................................37
4.11.7 Parameter Naming Rules..........................................................................................38
4.11.8 View Naming Rules...................................................................................................38
4.11.9 View Template Naming Rules...................................................................................41
4.11.10 Filter Naming Rules.................................................................................................42
4.11.11 Level Naming Rules................................................................................................43
4.11.12 Sheet Naming Rules...............................................................................................43
4.11.13 Fill Pattern / Fill Pattern File Naming Rules............................................................44
4.11.14 Filled Region Naming Rules....................................................................................44
4.11.15 Line Pattern Naming Rules.....................................................................................45
IV
4.11.16 Line Style Naming Rules.........................................................................................45
4.11.17 Text Type Naming Rules.........................................................................................46
4.11.18 Dimension Type Naming Rules...............................................................................47
4.11.19 Material Naming Rules............................................................................................47
4.11.20 Texture File Naming Rules......................................................................................48
4.11.21 Grid Type Naming Rules.........................................................................................49
4.11.22 Project Phase Naming Rules..................................................................................49
4.11.23 Arrowhead Type Naming Rules..............................................................................49
4.11.24 Shared Parameter File............................................................................................50
4.11.25 Project Template.....................................................................................................52
4.11.26 Family Templates....................................................................................................53
4.12 AutoCAD® Civil 3D® Settings...........................................................................................54
4.12.1 General DWT Template Configuration......................................................................54
4.12.2 DWT Template Types...............................................................................................54
4.12.3 Development and Approval of AutoCAD® Civil 3D® Templates.................................55
4.12.4 Location and Configuration of the Pipe Network Catalog.........................................56
4.12.5 Layer Naming............................................................................................................56
4.12.6 Style Naming.............................................................................................................57
4.12.7 DWT Template Naming.............................................................................................57
4.12.8 Object Naming...........................................................................................................58
4.12.9 Subassembly Object Naming....................................................................................58
4.12.10 Subassembly Naming (PKT files)............................................................................59
5 BUILDING INFORMATION MODELING PROCESS................................................................60
5.1 General Principles of Data Segregation.............................................................................60
5.2 Using Links........................................................................................................................61
5.3 LOD-based Development of Model Components..............................................................62
5.4 Using 2D Elements for the 3D Model Detailing.................................................................63
5.5 Levels of Development. Model Development Methodology...............................................63
5.6 Work with DWG Drawings.................................................................................................65
5.7 Drawing Compilation..........................................................................................................66
5.8 Modeling in Revit®..............................................................................................................66
5.8.1 Preliminary Data and Information................................................................................66
5.8.2 Project Template library..............................................................................................66
5.8.3 Family Library..............................................................................................................67
5.8.4 Data Segregation by Discipline and Templates Selection..........................................67
5.8.5 Creating the Project Files............................................................................................67
V
5.8.6 Project Base Point and Survey Point..........................................................................67
5.8.7 Conveying Shared Coordinates to Each Discipline Project Files................................67
5.8.8 Vertical and Horizontal Space Decomposition............................................................68
5.8.9 Project Division into Worksets.....................................................................................68
5.8.10 Creating the Central File and Local Copies..............................................................69
5.8.11 Managing the Workset Elements..............................................................................70
5.8.12 Using Families in the Project.....................................................................................70
5.8.13 Creating the Federated Model...................................................................................74
5.8.14 Project Release.........................................................................................................75
5.8.15 An Example of Information Model Development Process.........................................75
5.9 Modeling in AutoCAD® Civil 3D®........................................................................................76
5.9.1 Project Coordinate System..........................................................................................76
5.9.2 Transitions between Coordinate Systems...................................................................77
5.9.3 Using Coordinate System Displacement for Existing Infrastructure Assets................77
5.9.4 Working in the Revit® and AutoCAD® Civil 3D® Shared Coordinate System...............78
5.9.5 AutoCAD® Civil 3D® Baseline Data.............................................................................78
5.9.6 Geological Model.........................................................................................................79
5.9.7 Topography.................................................................................................................80
5.9.8 Existing Utility Networks..............................................................................................81
5.9.9 Existing Facilities and Infrastructure............................................................................82
5.9.10 Export from AutoCAD® Civil 3D® to Navisworks®......................................................82
5.9.11 Export from AutoCAD® Civil 3D® to AutoCAD®..........................................................83
5.9.12 Export from AutoCAD® Civil 3D® to Revit®................................................................83
5.9.13 Data Exchange between AutoCAD® Civil 3D® and Revit® Using ADSK....................84
5.9.14 Export from AutoCAD® Civil 3D® to InfraWorks® 360................................................84
5.9.15 Working With a Subassembly Library.......................................................................85
5.9.16 Grouping SAC Objects..............................................................................................85
6 VALIDATION PROCESS..........................................................................................................86
6.1 General Quality Control Strategy...................................................................................86
6.2 Various Kinds of Inspection............................................................................................86
6.3 3D Coordination Checks................................................................................................87
6.3.1 Model Preparation by Discipline..................................................................................89
6.3.2 Exporting models by discipline—sending data to Navisworks®...................................90
6.3.3 Creating the Federated Model.....................................................................................90
6.3.4 Clash Matrix................................................................................................................90
6.3.5 Creating Selection Sets and Search Sets...................................................................91
VI
6.3.6 Visual Check for Clashes............................................................................................91
6.3.7 Automated Clash Check..............................................................................................92
6.3.8 Clash Analysis.............................................................................................................92
6.3.9 Resolving Clashes.......................................................................................................93
6.4 BIM Coordination Meetings............................................................................................93
7 BEST PRACTICES...................................................................................................................94
7.1 Ensuring Model Quality......................................................................................................94
7.2 Effective Ways of Template Creation.................................................................................95
7.3. Revit® Architectural Template Checklist............................................................................96
7.4 Data Segregation between Disciplines..............................................................................98
APPENDIX A.............................................................................................................................100
LOD Specifications................................................................................................................100
APPENDIX B.............................................................................................................................122
BIM Execution Plan (BEP) Template.....................................................................................122
APPENDIX C.............................................................................................................................130
Clash and Design Error Report Templates............................................................................130
APPENDIX D.............................................................................................................................132
Autodesk Revit® Model Validation Checklist..........................................................................132
APPENDIX E.............................................................................................................................135
Example of collaborative BIM process...................................................................................135
APPENDIX F.............................................................................................................................136
Recommendations on Using Autodesk Navisworks® Manage for Clash Detection...............136
VII
CORPORATE BIM GUIDE for Revit® and AutoCAD® Civil 3D®
The Corporate BIM Guide: new and updated topics in Revision 2.0
New Versions of Project Templates and Shared Parameter FileNew project templates have been created for the architectural solutions, structural solutions and MEP disciplines. These templates shall be used for developing the design and producing the de-sign documentation in the Autodesk Revit® 2017 environment.
New template versions are fully consistent in regard to using parameters and Revit® content nam-ing.
In addition to templates, the unified shared parameter file has been created with consideration for the best Russian and world practices. This file shall be used for the entire design, regardless of discipline. Parameters in the file are grouped by distinction (required/optional) and discipline.
Links for download of templates and the shared parameter file can be found in this Standard.
Terms and Definitions Section: What’s New and ChangedThe terms and definitions list has been modified on the results of practical usage, discussions in the expert community and world’s best practices. Some definitions (2D, 3D etc.) have been re-moved, while several others (BIM model, BIM uses etc.) have been improved.
The Naming System: What’s New and ChangedThe naming system that is used for project files and Revit® content has been revised. The most significant changes are related to the field sequences in names.
All naming rules have been modified, and some rules have been split in two, e.g. Fill Pattern / Filled Region Naming Rules (Revision 1) transformed into Fill Pattern / Fill File Naming Rules and Filled Region Naming Rules (Revision 2).
8
3D Coordination: Significant Additions to the Validation ProcessThe 3D Coordination Checks section in this new Revision describes the basics of model prepara-tion by discipline and export to Navisworks® Manage for the federated model generation. The sec-tion also contains the clash matrix basics and an example.
Section that deals with using Navisworks® Manage defines requirements and recommendations on creating the selection sets, visual design error / clash check and automated clash check.
A new appendix has been added: Recommendations on using Autodesk Navisworks® Manage for clash detection
Revision 2.0: Additions and Modifications Table
Section Description
1 3. Terms and Definitions Some definitions (2D, 3D etc.) have been removed, while several others (BIM model, BIM uses etc.) have been im-proved.
2 4.9 Model file naming conventions
The project file naming scheme now contains 6 fields (in-stead of 7).
3 4.11.2 General Revit® content naming rules
Using spaces is allowed everywhere except loadable fami-lies names. In other words, spaces are allowed if the con-tent remains within the Revit® environment, but strictly for-bidden if the content becomes a part of the file system.
4 4.11.3 Loadable family naming rules
The loadable family naming scheme now contains 6 fields (instead of 9).
5 4.11.4 Loadable family type naming rules
The type naming rules have been split and now are sepa-rate for loadable and system families.
6 4.11.5 System family type naming rules
7 4.11.6 Workset naming rules
The workset naming scheme now contains 5 fields (instead of 4).
8 4.11.7 Parameter naming Spaces are now allowed in names. The naming scheme
9
rules now contains 2 fields.
9 4.11.8 View naming rules The view naming scheme now contains 7 fields (instead of 8). Tables of codes and descriptions have been modified.
10 4.11.9 View template naming rules
The view template naming scheme (6 fields) has been added.
11 4.11.10 Display filter naming rules
The display filter naming scheme now contains 3 fields (in-stead of 2).
12 4.11.11 Level naming rules
The rule definition has been improved. The naming scheme contains 1 field that is also a part of the view naming scheme.
14 4.11.13 Fill pattern / Fill file naming rules
The fill pattern / filled region naming rules have been split and now are separate for fill patterns / fill files and filled re-gions.
15 4.11.14 Filled region naming rules
16 4.11.15 Line pattern naming rules
The line style naming rules have been split and now are separate for line patterns and line styles.
17 4.11.16 Line style nam-ing rules
18 4.11.17 Text type naming rules
The text type naming scheme now contains 6 fields (instead of 5).
19 4.11.18 Dimension type naming rules
The dimension type naming scheme now contains 4 fields (instead of 6).
20 4.11.19 Material Naming Rules
The material naming scheme now contains 6 fields (instead of 5).
21 4.11.20 Texture file nam-ing rules
NEW! The naming scheme contains 4 fields.
10
22 4.11.21 Grid axis type naming rules
The grid axis type naming scheme (2 fields) has been added.
25 4.11.24 Shared Parame-ter File
Table of shared parameters has been added.
27 5.3 LOD-based develop-ment of model compo-nents
The section has been revised. The LOD concept is now de-scribed in more detail.
28 Appendix A. LOD specifi-cations
Manufacturer, Part Name and Part Number attributes have been moved from LOD 300 to LOD 400 in Tables A2, A6, A7, A8, A9, A10.
No more requirements for cables in Table A10.
29 Appendix C. Clash and Design Error Report Templates
Appendix C now contains three tables: Automated clash check report template, Automated clash check summary report template, Visual design error check report template.
Additions
1 6.3 3D coordination checks
2 6.3.1 Model preparation by discipline
3 6.3.2 Exporting models by discipline—sending data to Navisworks®
4 6.3.3 Creating the aggregated model
5 6.3.4 Clash matrix
6 6.3.5 Creating selection sets and search sets
7 6.3.6 Visual check for clashes
8 6.3.7 Automated check for clashes
9 6.3.8 Clash analysis
11
10 6.3.9 Resolution of clashes
11 Appendix F. Recommendations on using Autodesk Navisworks® Manage for clash de-tection
12
1 SCOPE
This Guide is intended to support organizations involved in the process of creation and use BIM models for building projects, and focuses primarily on adaptation the best practices for efficient ap-plication of Revit®, AutoCAD® Civil 3D® and Navisworks®. However, this Guide does not restrict the use of any other software tools.
The provisions of this Guide are indicative only and may be freely used as a template for develop-ment corporate guides.
The guide does not regulate the specifics of the development, workflows and requirements related to the composition and structure of the information model for specific design disciplines. It provides guidance and approaches for the development of documents on information modeling standardiza-tion.
This document represents the second revision of the guide. It will be further developed and ex-panded depending on its practical application experience.
The objectives of this Guide are:
To accumulate the best world practices in the area of BIM standardization and adapt this knowledge to maximum extent for practical use in the Russian Federation.
To maximize production efficiency through adopting a coordinated and consistent approach to working in BIM.
To define the standards, settings and best practices that ensure delivery of high quality data and uniform drawing output across an entire project.
To ensure that digital BIM files and folders are structured correctly to enable efficient data sharing whilst working in a collaborative environment.
The guide features the information modeling technologies application to the following BIM uses:
Development, coordination, approval and release of design documentation on the basis of BIM models.
Interdisciplinary coordination of spatial solutions and identification of conflicts by composing the aggregated models.
Rational and visual inspection of the BIM-based design decisions.
It is expected that this Guide will be used by experts with the requisite experience and qualifica-tions.
All the advice outlined in this document is for information only. The authors and contributing com-panies take no responsibility for the utilization of these procedures and guidelines. Their suitability should be considered carefully before embarking upon any integration into your current working practices.
13
14
2 NORMATIVE REFERENCES
This Guide is written with reference to the following documents:
ISO/TS 12911:2012 Framework for building information modelling (BIM) guidance;
BS 1192:2007 Collaborative production of architectural, engineering and construction infor-mation. Code of practice;
PAS 1192-2:2013 Specification for information management for the capital/delivery phase of construction projects using building information modelling;
AEC (UK) BIM Technology Protocol, Version 2.1 June 2015;
AEC (CAN) BIM Protocol for Revit, Version 2 September 2014;
AEC (UK) BIM Protocol Project BIM Execution Plan, Version 2.0 September 2012;
The BIM Project Execution Planning Guide and Templates - Version 2.0, Pennstate;
AEC (UK) BIM Protocol for Revit Model Validation Checklist, Version 2.0 September 2012;
Employer’s Information requirements. Core Content and Guidance Notes, Version 07 28.02.13, BIM Task Group;
AIA Contract Document G202-2013 Building Information Modeling Protocol Form;
Level of Development Specification 2015, BIMForum;
Building Component Catalogue with Level of Development Specification (LOD), Version 2.0 / June 2015, MT Højgaard;
Dutch Revit Standard, Ver.2.1, 30-01-2015;
Australian and New Zealand Revit Standards(ANZRS Standards);
Singapore BIM Guide, Version 2;
THE PORT AUTHORITY OF NY&NJ, Engineering Department, E/A Design Division BIM Standard, JUNE 2014;
MT Højgaard CAD-BIM Manual, Date: 08 Oktober 2013;
Revit Model Content Style Guide (RMCSG) version 2.1;
GOST R 1.4-2004 “Standardization in the Russian Federation. Standards of organizations. General.”
GOST R 21.1101-2013 “System of design documents for construction. Main requirements for design and working documents.”
15
3 TERMS AND DEFINITIONS
The following terms are used in this Guide.
3.1 Basic BIM Terms and Definitions
Building Information Model (BIM Model): Object-oriented digital representation of physi-cal, functional and other characteristics of the construction object in 3D as a complex of rich data elements in accordance with the goals, objective and requirements of the particular design.
Note: A BIM model in a native format is a 3D representation of the construction object, where every model element is linked to its counterpart displayed in views/drawings/schedules.
Building Information Modeling: Process of creation and management of the construction object data, forming the basis for decision making throughout the entire life cycle.
BIM Project: Design of the construction object created using Building Information Modeling (BIM) technology.
BIM uses: Methods and corresponding processes of creating and using BIM models in var-ious stages in order to achieve one or more project objectives.
BIM Execution Plan (BEP): A technical document normally created by a design or con-struction company for setting rules of interaction with subcontractors. Shall be approved by the employer. Specifies the employer information requirements, the ways of using BIM models, the rules of file naming, the strategy of model spatial division, the required levels of detail in the various design stages, the roles of the process stakeholders and other aspects.
Level of Development (LOD): The level of development of a BIM element. LOD sets the minimum amount of geometric, spatial, quantitative, as well as any attribute information necessary for modeling at a particular stage of the construction object life cycle.
Element: Part of the building information model representing the component, system or assembly within the construction object and/or the construction site.
Component (Revit® Loadable Family): An individual element that can be reused, such as a door, furniture, facade panel, etc.
Geometry Data: Data represented by means of geometry shapes properly arranged in space.
Attribute Data: Model element information that can be represented in the alphanumeric form. Can contain identification, physical, technical, technological, economical, ecological and other properties of a building element.
16
Common Data Environment (CDE): The software environment enabling the design data sharing. CDE is based on rules and procedures that facilitate management of BIM model creation and collaboration between design team members.
Federated Model: Assembly of distinct models to create a single, complete model of the construction object. Changes made in any of such models are not applied to other ones.
Clash Detection: Process of finding design errors resulting geometric intersections such as the intersection of two or more objects, violations of tolerances or logical dependencies between elements, etc.
Employer Information Requirements (EIR): BIM project owner requirements defining the information to be provided to the owner throughout the design development, as well as the requirements for information standards and regulations that the project participants shall adhere to.
Information Exchange: Collection and presentation of information that meets the require-ments for its format and degree of confidence in a pre-set stage of the project.
RVT: Basic Revit® model file format.
RTE: Revit® template file.
RFA: Revit® loadable family file.
RFT: Revit® family template file, used for creating new families. Each Revit® category has its own family template.
NWC: Navisworks® file format enabling data exchange with RVT, DWG, IFC etc.
NWD: Navisworks® Document file format. Intended for batch saving all model data into a single file and transfer to third parties. Transfer settings are configurable.
NWF: The basic Navisworks® working file format. Contains links to the loaded design files by discipline, as well as all viewpoints, animations, construction simulations, clash checks and information model environment.
DWG: The native file format for AutoCAD® data files. It contains all the pieces of informa-tion a user enters, such as designs, geometric data, maps, etc.
PDF: Cross-platform electronic document format developed by Adobe Systems. There are many PDF viewers, including the official Adobe Reader.
DWF: An open file format developed by Autodesk for sharing, viewing, printing and review-ing design data. Opens in the free Autodesk® Design Review software, as well as in Web browsers and on mobile devices using the Autodesk 360 cloud-based services. The DWF information may also be used in Revit® and AutoCAD®.
FBX: Technology and file format that is used to ensure compatibility of various 3D graphics software. Revit® information model is exported in this format to the visualization applica-tions, such as 3ds Max®.
17
ADSK: Files for the exchange of information between Revit® / AutoCAD® Civil 3D® and In-ventor® / Revit®.
BCF: File format for exchange of notes/comments related to the design. Attaching the screenshots is supported.
DWT: Template file in AutoCAD® and AutoCAD® Civil 3D®.
IFC: Industry-standard open and versatile format for BIM data exchange.
gbXML (Green Building XML): An open XML-based format for storing and exchanging geometric information on building envelopes. It is used to transfer data from BIM models to thermal performance calculation software.
GOST: Russian National Standard.
3.2 Basic Revit® Terms and Definitions
Category: A group of elements used for the construction object modeling: windows, doors, walls, floors etc. Categories are classified depending on their purpose:
o model categories;o view categories;o annotation categories.
Each category has its own set of properties and parameters, as well as the behavior and interac-tion rules. Categories cannot be created or edited by users.
Families: Groups of elements with a common set of parameters, identical use, and similar graphical representation.
System Families: Are created and edited in dialog mode; follow the severe system restric-tions. Can be only stored within project files, templates and families.
Loadable Families: Are created and edited in the built-in editor by means of combining the geometry elements, constraints and parameters. Can be stored within project files, tem-plates and families, as well as in separate RFA files.
In-place Families: Are created and edited in-place within the design file, in the family editor by means of combining the geometry elements, constraints and parameters. Establishing the geometric constraints with other design elements is possible.
Nested Families: Loadable families used inside other families; can be constrained. Ignored in quantities/schedules.
Shared Families: Nested families that can be counted towards the quantities/schedules and used in tags.
Types: Family elements differing by the property/parameter values.
18
Elements: Data instances that get individual location/relation properties and parameters within the design.
Type Catalog: A logical sequence of loadable family data in TXT format with the appropri-ate file naming. Using catalogs allows to only load the needed types in a large loadable family.
Templates: Preconfigured files that are used to create new designs and families.
Family Templates: Templates containing the required baseline data and settings to create certain categories of new loadable families.
Project Templates: Templates containing the required baseline data and settings to create new designs for certain disciplines. Also define which kinds of design documentation shall be released.
Worksets: Collections of model elements, families, views and settings. Supports appoint-ment of the owner and the borrower for the processes of team work:
o Owner: User who has the right to edit model elements and worksets.o Borrower: User who only has the temporary right to edit workset elements.
Central File: Project file that contains the worksets and is stored in a network folder that is accessible to all project participants.
Local File: A copy of the repository file created by opening it and immediate resaving to a local folder. Another way to get the local file is opening the repository file with Create New Local option enabled. The folder for storing a local file is set in Options dialog under Default path for user files. Changes in local files are synchronized with the central file.
Family Editor: A special Revit® work environment; contains only tools needed for family creation.
Parameter: Property of a Revit® element which can be formed and set either while creating a family in the Family Editor or in the design file itself. Parameters allow you to change the element without editing it in the Family Editor.
Project Parameter: A parameter that is created in the design file and can be assigned to any element category. It can be counted towards the schedules. Inclusion of project param-eters into tags is not supported.
Shared Parameter: A parameter that can be included into schedules and tags; it can be shared across various projects. You need to specify the file for storing a common parame-ter during its creation. If the file does not exist, it shall be created in the process of the de-sign development.
Shared Parameter File: A structured file of TXT format; contains the shared parameter definitions.
View: Display of the model data in various perspectives, sections and representations. There are graphic views (plans, sections etc.) and text views (schedules etc.)
19
Project Browser: Revit® control that displays the hierarchy of all views, schedules, sheets, families and groups.
Unique Reference System: The file containing the definition of absolute and relative coor-dinates of the project, as well as the direction of true north. There is only one Unique refer-ence system file in each project. Its main role is the spatial coordination of all BIM model disciplines.
Space Decomposition File: The file containing grid axes and levels. It shall be loaded as a link into all discipline design files. Axes and levels in these files are created then by means of Copy/Monitor tool. That makes possible to centrally control the position of the grid axes and levels throughout the whole design.
Shared Coordinates: Absolute and relative coordinates of the project shared by all design disciplines through the Unique reference system.
Grid Axes: Elements of horizontal space decomposition in the BIM model.
Levels: Elements of vertical space decomposition in the BIM model (by floor and by key elevation).
3.3 Basic AutoCAD® Civil 3D® Terms and Definitions
AutoCAD® Solids: 3D objects in AutoCAD®, created by AutoCAD-based software.
AutoCAD® Civil 3D® Russian Country Kit: Package with settings, templates, etc. for the various versions of AutoCAD® Civil 3D® released by Autodesk. The Country Kit ensures compliance with National Codes and Standards of Russia.
Workspaces: Sets of menus, toolbars and dockable windows (such as the Properties pal-ette, DesignCenter, and the Tool palettes window) that are grouped and organized so that you can work in a custom, task-oriented drawing environment.
Automatic AutoCAD® Civil 3D® Object Naming: The naming system based on the Name template Editor settings. Numeration schemes and template words are supported.
Pipe Network Catalog: AutoCAD® Civil 3D® catalog with definitions of all pipe network ele-ments accessible for insertion into the drawing. It is the crucial design component, set be-fore the work with pipe networks in AutoCAD® Civil 3D® begins.
Local Coordinate System: A system of plane rectangular coordinates in Gauss projection. Local systems are created in the National geodetic coordinate system; Gauss projection with elements of Krasovsky ellipsoid is used. This is implemented in the Year 1963 coordi-nate system (SK-63) and in the local coordinate systems of the Russian Federation sub-jects. There is an own local coordinate system in each subject of the Russian Federation: Moscow has MSK-50, St. Petersburg and Leningrad region have MSK-64, etc.
Autodesk Geotechnical Module: An AutoCAD® Civil 3D® extension for automated cre-ation geology models of the AutoCAD® Civil 3D® surfaces.
20
Custom Subassembly: AutoCAD® Civil 3D® subassembly that meet your specific design requirements, created by using Autodesk Subassembly Composer or by using program-ming tools.
Autodesk Subassembly Composer (SAC): AutoCAD® Civil 3D® extension. Provides an interface for composing and modifying complex subassemblies, without a need for pro-gramming.
PKT: Files created using Autodesk Subassembly Composer (SAC) which contain informa-tion about custom elements. PKT files are then imported into AutoCAD® Civil 3D® software.
SAC Flowchart: Set of SAC elements, located in the Flowchart or Sequence. Determines the behavior of custom elements.
SAC Codes: Codes for the flowchart elements. The syntax is (‘CODE’).
21
4 SETTING UP AND ORGANIZING THE BIM PROCESS
4.1 Employer Information Requirements (EIR)EIR is a document included into the design specifications in order to shape the requirements to information provided to the client during the BIM project development and on its completion.
Employer information requirements form the basis of the BIM Execution Plan (BEP).
Details of information requirements depend on the client’s BIM competence level.
The document shall contain the following sections:
Goals and objectives of using BIM on the project.
Work stages and information delivery milestones.
Minimum requirements for the number of modeled design disciplines and depth of modeling (for each discipline).
Requirements for the level of development (LOD) for each stage and discipline.
Requirements for the model elements classification system (if applicable).
Requirements for the content and format of design output.
Requirements for the BIM models testing regulations.
Requirements for the approval and change procedures, file exchange format and shared network resources.
Other sections, as applicable.
4.2 BIM Execution Plan (BEP)The main objective of the BIM Execution Plan (BEP) is the planning and organization of effective collaboration of all design team members at all stages of BIM project.
The BEP is a dynamic and a periodically changing document.
The BEP should be developed in collaboration with all information modeling process participants (both internal and external). All participants shall reach a consensus on how to set up, organize and control the information model. Such a consensus should be documented in the BEP.
The BEP shall define and document the following aspects:
22
Goals and objectives of the use of BIM in accordance with the employer information re-quirements (if applicable).
BIM final results.
Infrastructure needed for successful project execution.
BIM process.
See details on the BEP compilation in Appendix B, “BIM Execution Plan (BEP) Template”.
4.3 Roles and ResponsibilitiesThere are three primary functions in BIM process:
Strategic
Management
Production
The main functions should be distributed among the Roles.
The Fig.1 shows the roles (BIM Manager, BIM Coordinator, and BIM Author) and correspondent responsibilities. In small projects and small companies, most of responsibilities can be performed by one person or a group of persons.
Fig.1. Roles and responsibilities
23
Strategic function
Execution of this function is assigned to the BIM Manager.
Primary responsibilities are:
Developing the corporate BIM strategy
Best practice / research
Creating BIM processes and workflows
Creating and supporting BIM standards and protocols
BIM implementation
Training strategy
It is important to understand how vital a BIM Manager’s role is. It is not simply a rebranded CAD Manager, nor does it replace the CAD Manager’s role. It is about understanding what BIM can achieve: vision, engaging external stakeholders, collaborating partners. Somebody credible has to be responsible for the BIM strategy, the process change and the cultural impact. In-house or out-sourced, successful models cannot be built without a strategic manager.
Management function
Execution of this function is assigned to the BIM Manager and/or BIM Coordinator.
This is a project focused role, primary responsibilities being:
BIM Execution Plan
Auditing the project data and modeling principles
Participation in the interdisciplinary coordination meetings
Content creation and distribution, content quality control
Each project needs Coordinator(s) to help set up the project, audit the model and co-ordinate with all collaborators. Multi-disciplinary co-ordination with BIM is essential. Coordinator(s) may manage several small projects.
Production function
Execution of the function is assigned to the BIM Authors. They are discipline-specific designers working on different parts of the project with skill and experience in BIM software.
This is a project focused role, primary responsibilities being information creation.
BIM experience is not essential to produce the model but technology skills are. Therefore all the employees at this level should have the appropriate skills.
24
4.4 ResourcesThe following resources are needed to support the information modeling process:
Software
Hardware
Network resources
BIM content / resource libraries
To improve the efficiency of using BIM and ensure the consistent and high quality design, re-sources and content must be shared between all project participants.
Software
This Guide considers Revit® as the basic software for building design, while AutoCAD® Civil 3D® is used for infrastructure design. Aggregation of model and spatial coordination are carried out in Au-todesk Navisworks® Manage.
Any potential implementation of software upgrade during the course of a live project shall be re-viewed for its appropriateness by the BIM Manager/Coordinator.
Implementation of any upgrade shall be in line with corporate BIM strategy.
Hardware
The hardware used for BIM implementation shall meet the requirements imposed by the software developers at least for the next three years. It also shall have a sufficient level of fault tolerance and data security. A server is required for the centralized data storage and processing; a worksta-tion is installed at each user’s seat.
The server is the main storage place for project data. It shall provide selected user groups as well as individuals (as defined in the information security policy) permanent controlled access to the data. To ensure the reliability and security of the data, it is recommended to develop a solution for backup and archiving.
The workstation must ensure reliable operation on the user’s workplace. Key parameters affecting the overall performance are processor speed, RAM size, graphic card performance, disk perfor-mance, display resolution. Using SSD drives is strongly recommended for modern CAD software. 64-bit hardware and software systems are preferred for professional use.
Using monitors with a minimum resolution of 1920x1080 (HD) is recommended at each designer’s work seat. Using a dual-monitor system is even better.
You can find the full list of hardware requirements for Revit®, AutoCAD® Civil 3D® and Navisworks® on the Autodesk website:Revit® 2017: http://autode.sk/2e7RZrXAutoCAD® Civil 3D®: http://autode.sk/2dXtzmM Navisworks®: http://autode.sk/2e7SVfT
25
Network Resources
Communication between workstations and the server, as well as BIM design collaboration in real time are carried out through the network. The network shall have a sufficient capacity with a sug-gested data transfer rate of 1 Gigabit/s and uninterrupted access to the server. Uninterrupted ac-cess to network shared folders can be ensured using Revit Server.
Disks represent the physical storage media, so they shall have the sufficient access speed, as well as be reliable and fail-safe.
Resource Libraries
Content libraries hold components (families), design / family templates, materials and texture raster files for use within BIM. They are put on the file server.
The following rules shall be observed when working on BIM projects:
Content is developed in accordance with this Guide and the associated best practice guide-lines.
Project content shall be reviewed periodically by the BIM Manager for inclusion in the Cen-tral BIM Resource Library.
Project BIM Resource Library
This shall be the repository for the storage of project specific standards where deviation from this Guide is required due to project or client requirements.
Standards, templates, title blocks and other data produced in the process of the project de-livery shall be held within the Project BIM Resource Library.
Additions or modification to content held within this resource shall be carried out in a con-trolled manner and be at the prior approval.
Central BIM Resource Library
Standard templates, title blocks, material library families and other non-project-specific data shall be held within the server based Central BIM Resource Library.
Additions or modification to content held within this resource shall be carried out in a con-trolled manner and be at the prior approval.
Content shall be segregated by software product and version.
When content is updated for use in newer product version:
o The original data shall be kept and maintained.o The updated version of the content shall be created in the appropriate location for that
product & version. This avoids „forwards incompatibility‟ when using content with the version of the software for which it was originally created.
26
4.5 Common Data Environment (CDE)A major constituent of collaborative environments is the ability to communicate, re-use and share data efficiently without loss or misinterpretation.
This Guide is aligned with BS1192:2007 Collaborative Working, which defines the process for de-sign collaboration and efficient data sharing in Common Data Environment.
A Common Data Environment (CDE) approach allows verified and coordinated information to be shared between all members of the multidisciplinary project team. The recommended data ex-change diagram is shown in Fig.2.
Fig.2. Data exchange diagram within a multi-disciplinary design group
There are four phases to CDE:
1. Work in Progress2. Shared3. Published / Issued4. Archive
BIM information is passed through the 4 areas where the information is:
authored, checked, reviewed and approved for use outside of the authoring team (Work In Progress (WIP) area)
shared with other disciplines to use as reference material for their own design development and authorized to publish (Shared area)
published (in non-changeable formats) for use by the total project team (Published / Issued area)
27
stored and maintained for knowledge, regulatory and legal requirements (Archive area)
The phases of CDE are illustrated on Fig.3.
The CDE can be implemented in a number of ways, depending on organizational preference: as a folder structure, a project extranet or a PDM system, such as Vault®.
When using a PDM system, it is recommended, for each area, that you maintain status information and version control in the project files.
Fig.3. Common Data Environment structure
Work In Progress
WIP model files (local and repository) shall be developed in isolation and contain information for which each stakeholder is responsible.
These shall be stored in, and worked on from the team’s WIP section of the local filing system.
It is common practice that each stakeholder has access only to its own area of CDE.
Prior to sharing, the data shall be checked, approved and validated.
28
WIP model files are reviewed and approved by the task team manager and the BIM Manager/Co-ordinator.
Shared
To facilitate coordinated, efficient working, each party shall make their design data available for project-wide formal access through a shared repository.
Sharing of models shall be carried out on a regular basis in order that other disciplines are working to latest validated information.
Files stored in the Shared Area shall be write-protected.
Changes to the shared data shall be effectively communicated to the team through change register or other suitable notice, such as e-mail.
The Shared Area shall also act as the repository for formally issued data provided by/handed to customer and other external organizations that is to be shared across the project. In the absence of shared resources, the Customer can receive files via email or use a cloud storage to place them in its own CDE.
BIM model copied into the SHARED area can be used by the BIM Manager/Coordinator to build consolidated multidisciplinary BIM models (e.g., using Navisworks®) and to carry out clash checks or to collect data requested by client, company executives and other departments.
Published / Issued
Drawings, sheets and model files shall be stored in the Published Area of the folder structure once formally checked, approved and authorized in accordance with corporate quality procedures.
A record of all issued deliverables shall be maintained in softcopy and hardcopy where appropri-ate.
Only those drawings which it has been deemed necessary to revise will be re-issued following modification work.
Archive
The archive is composed of copies of all design data versions.
Archiving of all output data from the BIM shall be stored in the Archive Area of the project folder, including published, superseded and “As Built” drawings and data.
Archived data shall reside in logical folder repositories that clearly identify the archive status, e.g. 09-12-15 Stage D Design.
29
4.6 Basic Rules of BIM Data Exchange Validation of the BIM data prior to sharing shall check that:
File format, Revit® version and naming conventions conform to the corporate BIM Guide.
Elements used in the model correspond to data classification according to Revit® cate-gories, or to the corporate classification (coding) system of structural components and building systems.
Model files are up-to-date, containing all users’ local modifications.
Model files are detached from central file.
Any associated data required to load the model file is made available.
Model file has been audited, purged of unused content and compressed.
Any changes since the last issue are communicated to the design team.
4.7 Data Security & SavingAll BIM project data shall reside on network servers, which are subject to regular back-ups.
Staff access to BIM project data held on the network servers shall be through controlled access permissions set in the server software.
Revit® local files shall be saved back to Central hourly. At the completion of work at the end of the day borrowed elements and worksets shall be released.
Revit® save reminder interval shall be set to e.g. 30mins.
4.8 Folder Structure and Naming ConventionsThe defined structure shall follow the principles of BS1192:2007’s ‘Work In Progress (WIP)’, ‘Shared’, ‘Published’ and ‘Archived’ segregation of data within a designated set of folders.
All design data (excluding a local user’s copy of Central file) shall be held within the standard project folder structure located on a central network server or appropriate Document Management technology. This includes all WIP components or assemblies.
30
Central Resource Library Folder Structure
Standard templates, title blocks, families and other non-project-specific data (Fig.4) shall be held within the server based Central Resource Library, with restricted write access.
Fig.4. Central resource library folder structure
Local Project Folder Structure
Local copies of central project models do not need to be backed up as changes are regularly syn-chronized with the central file(s).
They shall be stored on the user’s hard drive – not in “My Documents”– according to the folder structure below in Fig.5.
Fig.5. Local project folder structure
Project Folder Structure
The folder structure shown in Fig.6 is provided as an example arrangement.
Fig.6. Project folder structure
Numeric prefixes in the names of folders and files are used for proper sorting of files and folders.
31
4.9 Model File Naming Conventions
4.9.1 General rules for model files naming
It’s recommended to separate fields by an underscore character “_”.
All fields in the file name start with an uppercase character, followed by lowercase ones. Within a field, CamelCase shall be used instead of a space to separate words.
Abbreviations and codes shall be written in uppercase.
The following characters shall be avoided in names:
, . ! “ £ $ % ^ & * ( ) { }[ ] + = < > ? | \ / @ ’ ~ # ¬ ` ‘
4.9.2 Recommended fields in a file name
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>_<Field6>
Field1: Project Code
An abbreviated code or number identifying the project.
Field2: Originator (Company) Code
An abbreviated code or number identifying the originating stakeholder.
Field3: Building/Zone
Identifier of which building/facility, area, phase or zone of the project the model file relates to if the project is sub-divided by zones.
Field4: Design Discipline
Field5: Description
Descriptive field to define the type of data portrayed in the file, or a unique file number.
Field6: Software Release
32
Example: 1895-13-2_APM5_MainBuilding_OV2_3D_R16
Note: If the Employer Information Requirements contain the file naming rules, then these rules shall be used in the project after mutual approval with the contractor.
4.10 Data Exchange Formats and InteroperabilityBIM model is an ideal platform for sharing data on the building object.
Interoperability between software products is of paramount importance for successful BIM working. File protocols ensure such an interoperability.
General Rules of Data Transfer
Data exchange formats and rules (protocols) shall be agreed by all BIM project participants and formalized in the BEP.
Requirements and limitations of the target software/hardware system shall be understood in order that BIM data can be prepared appropriately for exchange.
Data exchange protocol between different software/hardware systems shall be verified through sample testing to ensure data integrity is maintained.
Prior to export / import data, it’s necessary to purge all the excess information that could destabi-lize the data structure.
The appropriate export layer tables shall be used during export from Revit® to CAD.
Exchange Formats for Revit® Platform
Table 1 shows the recommended exchange formats for Revit® platform and their most frequent us-age methods.
Table 1 contains a partial list of formats supported by Revit®.
This Guide does not restrict use of other formats, taking the common data exchange rules into ac-count.
Table 1. Recommended exchange formats for Revit® platform
FormatApplication methods
For data export For data import
RVTData exchange within Revit® platform Data exchange within Revit® plat-
formData transfer to Navisworks®
33
DWG
Export of views and sheets to Auto-CAD® and other CAD software
Import of DWG layout from Auto-CAD® and other CAD software
Import of contours, surfaces (3D faces), corridors and pipes from AutoCAD® Civil 3D®
ADSKExport of data (model objects) to Au-toCAD® Civil 3D®
Import of objects (for family cre-ation) from Inventor®
IFCExport of data to third-party software that supports model import in IFC for-mat
Import of data from third-party soft-ware that supports model export to IFC format
DWF/3D DWFExport of data for review and publish-ing
Import of annotations and markups from Autodesk® Design Review to Revit® and AutoCAD®
PDF/3D PDFExport of data for review and publish-ing
–
FBX Export of models to 3ds Max® –
SKP –Import of data from Trimble SketchUp
SAT Export of 3D data Import of 3D data
4.11 Revit® Settings
4.11.1 Configuring Revit® Global Settings
Revit® global settings are configured in the Options dialog box. This Guide defines the minimum configuration.
General Tab
Save reminder interval shall be set taking into account the total amount of work and the number of participants in the workgroup. Recommended values are 30 to 60 minutes.
Usernames are essential for the team work. Ambiguous usernames shall be excluded.
Username can represent either a combination of first name, patronymic and last name, or a 2/3-symbol code in uppercase. By default, Revit® suggests the name used for the operating system login.
34
Worksharing update frequency shall be set to a maximum value.
User Interface Tab
Tools and analyses shall be configured according to each seat’s needs. If any tools are not needed to a user they shall be disabled.
Keyboard shortcuts allow quick start of most commands with the use of the keyboard. A complete list of commands which can be launched in such a way is accessible via the Keyboard shortcuts dialog box.
Graphics Tab
Use Hardware Acceleration (Direct3D) is on by default. Should any model display issues arise in a particular workplace, disable the hardware acceleration.
Change of background color is not recommended, as Revit® functionality is generally optimized for the white background.
File Locations Tab
Most frequently used templates shall be identified and put to the table. The leading five templates will be easily accessible from the Recent Files page that opens right after Revit® is launched.
The remaining tabs of the Options dialog box do not require any intervention.
4.11.2 General Revit® Content Naming RulesThe following naming rules hierarchy is proposed:
General rules define the common naming scheme; if no other rules exist then general rules shall be applied without any exception.
Local rules are related to a particular name element and may allow exceptions to the gen-eral rules, e.g. in using the dot symbol or special characters < > / \ | etc.
If a particular type of Revit® content doesn’t have a separate naming scheme yet, general rules shall be applied. This type of content will get an own scheme at a certain point.
The following naming rules and conventions represent a general approach and recommendations for the development of the naming convention system on the basis of best practices.
General rules for Autodesk Revit® content naming:
Name is composed of fields that are separated by a preset character. All fields in the file name start with an uppercase character. All fields shall be separated by an underscore character. Using spaces is allowed everywhere except loadable families names. Naming shall rely on the top-down principle. Abbreviations and codes shall be written in uppercase.
35
The following characters shall be avoided in names: , ! £ $ % ( ) ^ & { }[ ] + = @ ’ ~ ¬ ` ‘ and the following characters shall be never used: \ | / ? : * ” < >
Rules of Cyrillic and Latin alphabets usage shall be specified in the BEP. This Guide pre-sumes that Cyrillic character set may be used unless a local rule forbids it.
Mathematical symbols shall not be used in parameter names, as this causes problems in the formulas. Particular attention shall be paid to the minus sign.
The dot symbol is allowed in classification numbers, as well as a field separator character where necessary.
The “x” symbol, where needed, shall be in Cyrillic.
If any additional fields need to be featured in a name, they shall be entered at its end.
4.11.3 Loadable Family Naming Rules
Naming of families and types shall be based on rules set in 4.11.2.
The following format is suggested for loadable families naming:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>_<Field6>
where:
Field1 – author code
Field2 – functional type
Field3 – functional subtype
Field4 – manufacturer
Field5 – description, a distinctive feature of an item
Field6 – GOST
Field1 and Field2 are required; Field3, Field4, Field5 and Field6 are optional.
If the family doesn’t contain any 3D geometry, “-2D” shall be added to Field2.
All fields in the file name start with an uppercase character, followed by lowercase ones. Within a field, CamelCase shall be used instead of a space to separate words.
Examples:
ABC_Door_ Double_ WoodInterior_GOST6629.88
ABC_Window_Threefold_ GOST23166.99
ABC_WaterCloset-2D_WallHung_Grohe_Sensia
ABC_Pump_Circulating_Grundfoss_NK
36
ADSK_Tag_Window_GOST 21-501-2001
4.11.4 Loadable Family Type Naming Rules
Naming of family types shall be based on the following format:
<Field1>_<Field2>_<Field3>
where:
Field1 – description
Field2 – size designator
Field3 – description 2 (swing for windows and doors, composition of wall / floor / roof, additional designators for doors and windows)
Field1 is required, remaining fields are optional.
Catalog name (if any) provided by the manufacturer may be used.
Examples:
Family: (ABC_Door_ Single_WoodInterior_GOST6629.88)
Type: DG_21.9_LS
Family: (ABC_Fan_Axial_Innovent_Univent)
Type: 1.6-2-1
4.11.5 System Family Type Naming Rules
Naming of system types shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>
where:
Field1 – author code
Field2 – functional type
Field3 – functional subtype
Field4 – manufacturer
Field5 – description, a distinctive feature of an item
Field6 – GOST
37
For greater flexibility, all fields are optional.
Examples:
Family: PipeType: Aquatherm_Fusioterm Shtabi SDR7.4
Family: DuctType: Rectangular_SmokeRemoval_GOST 19904–90
Family: DuctType: Conduit_IEC_Elecor
Family: WallType: Exterior_Brick250 ut100 brick120 -st20 -490
4.11.6 Workset Naming RulesWorksets shall be named consistently and logically, in order to facilitate project navigation. Pay attention to the fact that worksets for all disciplines shall be defined in the BEP. This ensures that all disciplines know what to expect from the linked models.
When using linked files a separate workset shall be created for each of them.
The following format is suggested for worksets naming:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>
where:
Field1 – support field. Prefix “#” is recommended for worksets that are not intended for other disci-plines.
Field2 – project portion code, if applicable
Field3 – discipline code
Field4 – location in project (for smaller objects) or function/system (for larger objects)
Field5 – workset description/contents
For greater flexibility, all fields are optional.
Examples:
007_AC_EastWing_Partitions
PE_ColdWater_Pipes
#_AC_Duplicates
#_Shared levels and grids
38
#_Linked PE model
4.11.7 Parameter Naming Rules
Naming shall adhere to common rules. Parameter names must contain the information necessary for their convenient grouping depending on tasks for which they were defined. Parameter naming rules for specific tasks should be described in the BEP.
Naming of parameters shall be based on the following format:
< Field1>_< Field2>
where:
Field1 – author code (shared parameters only). Field1 cannot be used in names of design/family user parameters. Author code ADSK applies to the recommended Autodesk shared parameters. ADSK code shall never be used in corporate parameters.
Field2 – description – a word describing the object the parameter is applied to (if available) or a word used to group parameters. Contains the property parameter is associated to, as well as prop-erty name.
Naming shall rely on the top-down principle. Common terms and definitions allow using the tradi-tional wording (“Minimal power” instead of “Power minimal” etc.). For support parameters (those that drive size, visibility and other element features) it’s recommended to put the object first: "Win-dowSill Depth", "WindowSill Height".
Examples:
Length
Section Width
ADSK_Apartment area
ADSK_Air flow rate
4.11.8 View Naming RulesNaming of views shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>_<Field6>_<Field7>
where:
Field1 – view code (P, EX, IA, OA etc., see Table 2)
Table 2. View codes
Field1 View code
39
value
WV Working view
P Ready for Print
EX For export
IA Incoming assignment
OA Outgoing assignment
C Coordination
I Image (visualization)
Field2 – discipline code (AR, STR, HVAC…).
Field3 – zone.
Field4 – level identifier
Field5 – view family code (see Table 3)
Table 3. View family codes
Field5 value View family
3D 3D views
FP Floor plans
RCP Reflected Ceiling plans
S Sections
CO Callouts
E Elevations
S Site
DV Drawing view
Field6 – view description
Field7 – alphanumeric view designator
Examples:
WV_HVAC_Block A_-01 Floor_Ventilation
P_AR_-02 Floor Basement_Masonry_1-5 A-B
EX_AR_13 Floor TechFloor_PE_Masonry_1-5 A-B
40
P_STR_05 Floor_Layout_Callout 1
I_AR_Exterior_Base view
I_AR_Interior_3 floor_Meeting room 105
EX_Export to Navisworks
P_AR_Section 1
WV_Doors data entry
P_AR_01 Floor_Door assembly schedule
P_AR_Door assembly group schedule
P_HVAC_Extended callout schedule
EX_PL* Pipe fitting schedule
*PL- plumbing
Field1, Field4 (for plans), Field5 (for exported views) and Field6 are required. All other fields are optional.
Naming requirements for views to be exported to various formats/software:
1. Autodesk Navisworks®
If a view is intended for export to Autodesk Navisworks®, Field5 shall contain the word “Navis-works” (“N” in uppercase). Only one such view can exist within a design. When the RVT model is imported into Autodesk Navisworks®, all model elements that present in this view are taken into account.
2. Autodesk AutoCAD®
All words in the view name must start with the uppercase character, because white spaces are au-tomatically deleted during the DWG export.
Example:
E_AT_TechFloor_PE_Masonry Plan_1-5-A-B
3. Autodesk 3DS MAX.
All words in the name must be written in Latin alphabet, because 3DS MAX doesn’t support Cyril-lic.
41
4.11.9 View Template Naming RulesView templates represent an effective way to control the look and image settings for different types of display. View templates in Revit® are classified as plans, sections and elevations.
The name of the template must be sufficiently informative so as the user can clearly understand the corresponding type.
View templates naming shall adhere to the common rules.
Naming of view templates shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>_<Field6>
where:
Field1 – author code
Field2 – project phase code (omitted if the template is suitable for several phases)
Table 4. Project phase codes
Field2 value Project phase
Stage SD Schematic design
Stage DD Design development
Stage CD Construction documentation
Field3 – discipline code
Field4 – view code (P, EX, IA, OA etc., see Table 2)
Field5 – view family code
Table 5. View family codes
Field5 value View family
3D 3D views
FP Floor/structure plans
RCP Reflected Ceiling plans
S Sections
E Elevations
SQ Schedules, quantities
42
L Layout (column positions, water disposal)
Field 6 – description
Examples:
ADSK_ Stage SD _AR_P_FP_Masonry
RTG_ Stage SD _AR_P_FP_Zoning
ADSK_Stage CD_STR_P_FP_Underlying reinforcement
ADSK_Stage CD_AI_P_S_Color
ADSK_HVAC_SV_FP_Ventilation
For greater flexibility, all fields are optional.
4.11.10 Filter Naming RulesFilters are used to manage view appearance.
Filter naming shall adhere to common rules.
Special characters are allowed in the filter descriptions.
Naming of Filters shall be based on the following format:
<Field1>_<Field2>_<Field3>
where:
Field1 – author code
Field2 – filtered object
Field3 – filter description
For greater flexibility, all fields are optional.
Examples:
ADSK_Section_Working* – all sections whose names begin with “Working”
Wall_*200* – walls whose names contain “200”
Walls_Thickness<200 – walls that are thinner than 200mm
43
ADSK_ Reinforcement_Tag ≠ PM1 – reinforcement that doesn’t belong to the PM1 structure
Syntax of filtering condition may be duplicated in Field3 for better understanding.
4.11.11 Level Naming Rules
Level name in the view naming pattern (ref. 4.11.8) corresponds to Field4, the level identifier.
<Field1>
where:
Field1 – level name
Examples:
01 Floor
-01 Floor KR -3.600
12 Floor Rooftop
Level name shall begin with a number, followed by the defining word (Floor, Level, etc.) and the description (if needed), e.g. elevation value or function.
All floor numbers must contain the same number of digits: 2 digits (-05, 01, …, 99) if the building is less that 100 floors high, or 3 digits (-005, 001, …, 099, 112) if it is higher than 100 floors.
4.11.12 Sheet Naming Rules
Sheet naming shall adhere to the common rules in accordance with GOST 2.104-68 “Unified sys-tem for design documentation. Basic inscriptions.”
Sheet names are derived from name of views placed on them.
Sheet naming rules shall be described in detail in the BEP.
Examples:
Elevation within axes A-G. Elevation within axes G-A.
Sections 1-1, 2-2, 3-3
Floor plan at elevation 0.000
Plan extract within axes 3-15, V-D at elev. +5.200
44
4.11.13 Fill Pattern / Fill Pattern File Naming RulesFill pattern / fill pattern file naming shall adhere to common rules.
Naming of fill patterns and fill pattern files shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>
where:
Field1 – author code
Field2 – fill pattern type (U - drafting, M - model) (for fill pattern files only)
Field3 – material description, filled region usage, fill description
Field4 – fill angle
Field5 – fill size
Field1, Field2 and Field3 are required; other fields are optional.
Examples:
ABC_M_BrickFacade_0_250.pat – fill pattern file
ABC_Masonry_45_1mm
ABC_AngledDown_-45_1mm
ABC_Cross_0_1.5mm
4.11.14 Filled Region Naming Rules
Filled region naming shall adhere to common rules.
Naming of filled regions shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>_<Field6>
where:
Field1 – author code
Field2 – fill pattern type (U - drafting, M - model)
Field3 – short fill description
Field4 – fill angle
Field5 – fill size
Field6 – color
45
Field1, Field2 and Field3 are required; other fields are optional.
Examples:
ABC_U_Ground_45_2mm_Brown
ABC_U_Vertical_90_2mm_Blue
ABC_U_Fill_Black
ABC_M_BrickFacade_0_250mm
4.11.15 Line Pattern Naming RulesLine pattern naming shall adhere to common rules.
Naming of line patterns shall be based on the following format:
<Field1>_<Field2>_<Field3>
where:
Field1 – author code
Field2 – pattern name
Field3 – pattern dimensions in the following format: s3 p2 t p2, numbers represent segment lengths, s = dash, p = space, t = dot
Field3 is optional and only describes sizes in abstract line patterns (dashed, dashed-dotted, dash – 2 dots, etc.)
Examples:
ADSK_DashDot_s3 p1 t p1
ADSK_Dash_s3 p1
ADSK_Centerline
RTG_Hidden lines
4.11.16 Line Style Naming Rules
Line style naming shall adhere to common rules.
Naming of line patterns and line styles shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>
where:
46
Field1 – author code
Field2 – purpose of line style or name of line pattern
Field3 – line color
Field4 – line weight
Examples:
MHP_Centerline_2
ADSK_Solid_Red_5
ADSK_Base thin
RTG_Base thick
4.11.17 Text Type Naming Rules
Text type naming shall adhere to common rules.
Naming of text types shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>_<Field6>
where:
Field1 – author code
Field2 – purpose
Field3 – font name (specified if differs from the standard one)
Field4 – text height in mm (units shall be omitted). Specified if differs from the standard one (2.5mm).
Field5 – B, I, U definitions and the width ratio. If the latter equals to 1, it shall be omitted
Field6 – Description 2, color, transparency etc. (if needed)
Field1 and Field2 are required, other fields are optional.
Examples:
ABC_Header
ADSK_Main text
ADSK_Main text_cnd0.8
ADSK_Schedules
47
ADSK_Schedules_Arial_3
ABC_ISOCPEUR_5_B
ABC_ISOCPEUR_2.5_Red
4.11.18 Dimension Type Naming RulesDimension type naming shall adhere to common rules.
Naming of dimension types shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>
where:
Field1 – author code
Field2 – style purpose: e.g. “Checking”
Field3 – dimension text font (specified if differs from the standard one)
Field4 – text height in mm (specified if differs from the standard 2.5mm)
Field5 – text compression ratio (specified if differs from 1)
Field6 - transparent/obscure background
For greater flexibility, Field3 and Field4 are optional.
Examples:
ADSK_Standard
ABC_Checking
ABC_Rounding to integer_ISOCPEUR_2.5
4.11.19 Material Naming Rules
Material naming shall adhere to common rules.
Naming of materials shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>_<Field5>_<Field6>
where:
Field1 – author code
48
Field2 – material category, e.g. Concrete
Field3 – material subcategory, further defining its properties
Field4 – material class/grade or color
Field5 – material manufacturer
Field6 - type: T, F, FT – indicates availability of thermal and fhysical parameters
For greater flexibility, all fields are optional.
Examples:
RT_HeatInsulation_Rockwool_WAS50_Paroc_T
ZPP_Ceramic Brick_Solid
CCR_Plaster_Lime
ABC_Concrete_B15
4.11.20 Texture File Naming Rules
Texture file naming shall adhere to common rules.
Naming of texture files shall be based on the following format:
<Field1>_<Field2>_<Field3>_<Field4>
where:
Field1 – author code
Field2 – material category, e.g. Concrete
Field3 – material subcategory, further defining its properties
Field4 – description
For greater flexibility, all fields are optional.
Examples:
RT_HeatInsulation_Rockwool_WAS50
ZPP_Brick_Ceramic_Solid
CCR_Plaster_Lime
ABC_Concrete_InSitu
49
4.11.21 Grid Type Naming RulesNaming of grid axes shall be based on GOST R 21.1101-2013, section 5.3.
<Field1>_<Field2>
where:
Field1 – axis callout size in millimeters. Unit not included.
Field2 – description.
Both fields are required.
Examples:
10_at start
8_on both sides
4.11.22 Project Phase Naming Rules
Project phase naming conventions shall be formalized in the BEP.
4.11.23 Arrowhead Type Naming RulesArrowhead naming shall adhere to common rules.
The following format is suggested for naming of arrowheads:
<Field1>_<Field2>_<Field3>_<Field4>
where:
Field1 – author code
Field2 – arrow (tick) style
Field3 – tick size
Field4 – arrow angle
For greater flexibility, all fields are optional.
Examples:
ABC_Arrow_2.5mm_30
ABC_Diagonal_3mm
ADSK_Dot_1mm
50
4.11.24 Shared Parameter FileShared parameters can be created and used in loadable families, as well as in the design itself. In the latter case, they can be assigned to any category of Revit® elements.
Recommendations on using the Shared Parameter file:
● Revit® can simultaneously work with only one Shared Parameter file. In the process of de-sign development you may link several different files one after another, so as to use shared parameters from a number of files.
● As the organization can use several Shared Parameter files, starting a project, make sure you use the correct file.
● It’s recommended to establish the corporate Shared Parameter file, in order to ensure the parameter naming consistency during the content creation.
● The corporate Shared Parameter file is held in the Standards folder within the Central BIM resource library along with the respective design template.
● All project participants shall get the Shared Parameter file with a read-only access. Changes in the Shared Parameter file can be only introduced by BIM-manager / coordina-tor, and all project participants shall be informed. Whenever you add a new shared parame-ter a backup copy shall be created in prior.
● When the creation of project-specific families requires the definition of shared parameters, a file shall be created within the project’s BIM resource folder. Once this content is approved for the corporate library, the associated Shared Parameters will be appended to the central Shared Parameter file.
● When a new parameter is created, it is recommended to enter a description that would greatly facilitate the further management of the Shared Parameter file.
● Shared Parameter file shall not contain parameters that belong to the Exported Parameters group.
● Groups and parameters shall be named in accordance to the parameter naming rules.
● Group numbering shall be formalized and respected in the Shared Parameter file for all dis-ciplines (applicable if each of them used its own file). E.g. Architecture shall always use number 1, etc.
● Shared Parameter files shall be configured by the BIM Manager/Coordinator.
● The complete list of shared parameters is company-specific.
● Some examples of shared parameters are shown in Table 6.
51
● Table 6. Examples of a project’s shared parameters
Parameter name Data type Group Descriptions
ADSK_Name TEXT Required COMMON Parameter for schedules, representing the element name and its main specifi-cations
ADSK_Tag TEXT Required COMMON Type, tag, index of a docu-ment/form
ADSK_Weight NUM-BER
Required COMMON Product weight per unit or linear density (for rebars, beams etc.)
ADSK_Floor type TEXT Required ARCHITEC-TURE
Floor type. Sent to the floor tag and floor schedule
ADSK_Room type TEXT Required ARCHITEC-TURE
Room type (residential, non-residential, etc.). Used in apartment layouts
ADSK_Floor makeup IMAGE Required ARCHITEC-TURE
Graphical structure of the floor make-up
ADSK_Bent reinforcement YESNO Required STRUCTURE Parameter is on for bent re-inforcement, off for straight bars
ADSK_Product tag TEXT Required STRUCTURE Tag of an embedded item or a reinforcement cage in a structure
ADSK_Type of element KZh
INTE-GER
Required STRUCTURE Needed for representation of compound products (rein-forcement cages, embed-ded items, their compound elements etc.)
ADSK_Equipment code TEXT Required MEP Equipment code according to the manufacturer’s cata-log
ADSK_Partition code TEXT Required MEP Conduits
ADSK_Standpipe number TEXT Required MEP Standpipe designator in lay-outs and plans
52
4.11.25 Project TemplateThe template is a raw design file with RTE extension. When creating a new project by choosing a particular template, user selects and applies a certain configuration contained in the template. Template file itself remains unchanged, while the new design file is saved with a different exten-sion, RVT.
When creating project templates, you should:
• Use effective creation methods; check the template against the Revit® template checklist (see section 7.3).
• Create a separate template for each discipline. However creation and use of the same tem-plates for all disciplines is also allowed; settings in architectural template are common to all disciplines, and that must be considered when determining the order of template creation.
All Revit® design disciplines shall rely on the project template developed in advance.
Project template shall be developed by the BIM Manager/Coordinator in accordance with the ap-proved procedure. The template shall be put into the corporate template library.
Changes must be introduced into templates by the BIM Manager/Coordinator in accordance with the approved procedure.
4.11.26 Family Templates
Loadable families shall be created on the basis of family templates which carry RFT extension.
Family template files contain all necessary property sets and define the behavior of family.
There are separate template files for each Revit® category. The template choice depends on the category of family to be created.
A family shall be created using the corresponding category template. Incorrect template selection can cause wrong display and/or wrong behavior of the model element and/or errors in schedules.
Examples of family templates for model elements:
Metric_Door.rft
Metric_Column.rft
Metric_Beam.rft
Metric_Window.rft
Metric_DuctElbow.rft
Examples of family templates for annotation elements:
Metric_SectionHead.rft
53
Metric_DoorTag.rft
Metric_ElectricalEquipmentTag.rft
Metric_RoomTag.rft
Examples of family templates for title blocks:
A0_Metric.rft
A1_Metric.rft
Example of family template for a mass element:
MetricUnits_MassElement.rft
4.12 AutoCAD® Civil 3D® Settings
4.12.1 General DWT Template ConfigurationAll AutoCAD® Civil 3D® project data is stored in drawing files (DWG). Therefore storage scheme for AutoCAD® Civil 3D® settings has the same structure as AutoCAD and is based on DWT files.
The key point is to set the location of DWT templates when creating a new drawing.
It is not allowed to store DWT templates on local workstations. All templates should be located in a shared network folder. The editing privileges may have
only BIM Manager / Coordinator. In AutoCAD® global settings on each workstation you must set a network folder where DWT
templates are located. In AutoCAD® global settings you must specify a template that will be used by default when
creating a new drawing (QNEW command).
4.12.2 DWT Template TypesIt is recommended to create templates using templates included in AutoCAD® Civil 3D® Russian Country Kit.
Templates shall be discipline-specific:
Survey – SV General layout – GL Roads – RD Railways – RW Pipe networks – PN Basic – No prefix
54
General – No prefix.
Each block should include one or more templates. Templates should include only those styles and settings that are needed for a discipline.
The General template includes all styles. Not recommended for use; it is used only for project man-agement.
Basic template contains minimum number of styles. It shall not contain any layers other than layer “0” which holds all existing AutoCAD® Civil 3D® objects. The number of surface/section display styles shall be minimal as well. This template is intended for secondary disciplines and is tweaked by the BIM Manager/Coordinator for completing specific tasks.
The Basic template is necessary for the BIM manager’s individual tasks aimed to obtain custom data. For this purpose, in the Basic template, all styles are located on the layer "0". BIM manager creates custom layers and objects based on this template.
4.12.3 Development and Approval of AutoCAD® Civil 3D® TemplatesTemplates are developed in accordance with the requirements of regulatory documentation and company standards.
AutoCAD® Civil 3D® templates are created by the BIM Manager/Coordinator.
A group of reviewers is convened prior to start of work; their areas of responsibility are consulting and template testing. Members of the group are appointed by the BIM Manager/Coordinator.
The template creation procedure consists of the following stages:
Collecting baseline data (drawings and models) from BIM authors and other project partici-pants.
Creation of the initial template version. Coordinating and testing the template with all project stakeholders, collecting the change
proposals. Implementing changes, compiling and coordinating the updated template version. Final coordinating and approving by the review group. Accepting templates by the BIM Manager/Coordinator, placing them to the central server
location.
The central server location is set up in the AutoCAD® Civil 3D® options. All kinds of AutoCAD® Civil 3D® templates shall be put there. Only the BIM Manager/Coordinator has rights to incorporate changes to template names and internal structure. Other project participants have the read-only access to the templates. If the need to change the template arises, the initiator of change shall no-tify the BIM Manager/Coordinator by e-mail. The purpose of such a notification is to justify the ne-cessity and to describe in detail the essence of the changes. After that the BIM Manager/Coordina-tor initiates the change process.
Exact number of templates and their contents are defined by the BIM Manager/Coordinator de-pending on the project requirements.
55
4.12.4 Location and Configuration of the Pipe Network CatalogPipe Network Catalog is necessary for pipe design.
Pipe Network Catalog is composed along with the DWT template. The process of Catalog creation and modification is the same as for the DWT template.
Pipe Network Catalog shall not be stored locally. It shall be put into a server location. Each work-station accesses the Catalog using the path to the server folder.
4.12.5 Layer Naming
Naming of layers shall be based on the corresponding company standard used for AutoCAD®. In the absence of such a standard it is necessary to comply with the following requirements.
Do not use “C-*-*” naming convention set up in the AutoCAD® Civil 3D® Russian Country Kit tem-plate. Adherence to the scheme defined in the Kit would lead to confusion and emergence of a lot of empty layers.
The BIM Manager/Coordinator defines the method of AutoCAD® Civil 3D® objects placement: ei-ther on a single layer or on a separate layer for each object. Naming of AutoCAD® Civil 3D® layers shall be based on the following format:
<Field1>_<Field2>_<Field3>
where:
Field1 – abbreviation of a discipline. Abbreviations that only belong to a particular discipline tem-plate (e.g. PZM or POR) are not allowed.
Field2 – object type: surface, alignment, label etc. Spaces are not allowed; CamelCase shall be used instead of a space to separate words.
Field3 – object name, if placement of each new object on its own layer have been configured. Oth-erwise the field shall be omitted.
Example (an own layer is created for each new object):
GP_Surfaces_Grading
Example (all objects are put on the same layer):
GP_DesignLabels
4.12.6 Style Naming
In the process of developing an AutoCAD® Civil 3D® template, new styles should be given new names. The names are formed by adding a prefix to the short name of the company for which a template is developed. Use the underscore as a separator between the prefix and the style name:
56
<Field1>_<Field2>
Field1 – Company name (abbreviated)
Field2 – Style name. You can use spaces.
Example: XXX_ Contours
When preconfigured templates are used, editing object styles by end users is not recommended. If you need to make changes to a style, it is not allowed to edit an existing style. To do this, you must copy the most appropriate style and give it a new name. The name is formed by adding the name of the author between the company name and the style name:
<Field1>_<Field2>_<Field3>
Field1 – Company name (abbreviated)
Field2 – Author name
Field3 – Style name. You can use spaces.
Example: XXX_ Smith_Contours
If you need to create a new style, it is not allowed to edit an existing style. To do this, you must copy the most appropriate style and give it a new name. The name is formed by adding the name of the author between the company name and the style name:
<Field1>_<Field2>_<Field3>_<Field4>
Field1 – Company name (abbreviated)
Field2 – Author name
Field3 – Style name. You can use spaces.
Field4 – Description
Example: XXX_ Smith_Contours_0.1m
4.12.7 DWT Template NamingNaming of parameters shall be based on the following format:
<Field1>_<Field2>
where:
Field1 – template name with a discipline-specific prefix. Spaces are not allowed.
Field2 – template version number.
Example: Template_GP_1.25
57
4.12.8 Object NamingAll AutoCAD® Civil 3D® objects automatically get their names and numeric indexes at their cre-ation. It’s not recommended to adhere to this automatic naming. AutoCAD® Civil 3D® objects must have individual names that describe an object and its role in the project in maximum detail.
It’s strictly prohibited to use automatic names for the following objects:
Alignments Surfaces Assemblies Sections Corridors Grading Sites Pipe networks
4.12.9 Subassembly Object NamingNames of all objects created in Autodesk Subassembly Composer (SAC) shall be in Russian or in the official language of project. Multilingual naming is not allowed. English abbreviations that are created by default may be used for points, links and solids:
Points: P1, P2, P3… Auxiliary points: AP1, AP2, AP3… Links: L1, L2, L3… Auxiliary links: AL1, AL2, AL3… Solids: S1, S2, S3… Offset Geometry: O1, O2, O3… Loop: LO1, LO2, LO3…
All these elements must have codes in Russian or in the official language of project.
Points, links and solids without codes are not allowed for assemblies in the subassembly library.
Methods of naming for points, links and solids are defined by the BIM Manager/Coordinator de-pending on the project requirements.
Decision element has 2 solutions, True and False; both must have scenario names corresponding to the occurred event.
Due to some SAC technical limitations, spaces need to be replaced with underscores “_” in names of Target Parameters and Input/Output Parameters. Consequently, DisplayName fields are to be completed with extensive parameter names (without underscores).
Naming rules for SAC objects shall be set in full detail by the BIM Manager/Coordinator in the BEP.
58
4.12.10 Subassembly Naming (PKT files)Three types of names are used:
Names in the line Subassembly Name in SAC Names in the PKT file names Names in the AutoCAD® Civil 3D® Tool Palette.
For all three types of names is recommended to use the base name.
Rules for a base name:
<Field1>_<Field2>_<Field3>
Field1 – Abbreviated company name
Field2 – A brief description (use underscore instead of spaces) or code (in the case you include these elements in the list for coding)
Field3 – Subassembly version
Example:
XXX_DitchedConnectionToExistingTerrain_v1.01
For names under Subassembly Name in SAC (Packet Settings tab) the base name should be changed in accordance with the technical limitations of SAC. In particular, you cannot use spaces, periods, commas, etc. Therefore, the base name must be converted into the following form:
XXX_DitchedConnectionToExistingTerrain_v101
In addition, Description field in SAC (Packet Settings tab) is mandatory for library assemblies. It must describe assembly behavior and peculiarities in detail in the official language of project.
The common operating system restrictions are applied to the PKT file names. This means that the base name can be used as is.
For AutoCAD® Civil 3D® Tool Palette, the names are inherited from Subassembly Name of SAC. It is recommended to change the names of the Tool Palette by replacing underscores with spaces and other punctuation:
XXX Ditched connection to existing terrain v1.01
59
5 BUILDING INFORMATION MODELING PROCESS
5.1 General Principles of Data SegregationThe purpose of segregation is to lay a foundation for multi-user access to the model and to ensure the effective teamwork.
The following practical approaches are recommended during the information model development:
Model structure shall take into account all BIM-covered design disciplines (see Table 7).
Table 7. Principles of data segregation
Discipline Segregation principles
Architecture By floor or floor group
Structural By functional joints, grips of concrete and metal structures
MEP - Mechanical By system: air supply, air exhaust, air conditioning etc.
MEP – Plumbing By system: cold water supply, hot water supply, water waste
A model file shall contain data from one discipline / project stakeholder only (although ex-ceptions may apply for Building Services where multiple disciplines converge).
No more than one building shall be modeled in a single file.
Further segregation of the geometry may be required to ensure that model files remain workable on available hardware. Elements are included into worksets either individually or by category / location / task distribution etc.
In order to avoid duplication or coordination errors, clear definition of the data ownership throughout the life of the project shall be defined and documented.
Element ownership may transfer during the project time-line – this shall be explicitly identi-fied in the BEP.
Where multiple models make up a single design, a container model should be considered, whose function is to link the various assemblies together for coordination/clash detection purposes.
Data segregation within a model may depend on planned ways of information transfer (ex-port) as well as on model final delivery format.
60
Models shall initially be created as isolated, single-user files. The model will be sub-divided as additional members of the design team are introduced.
In order to ensure better hardware performance, users shall only open portions/models that contain current objects of interest.
No other views than necessary for the current task shall be created.
All models and their portions (worksets) shall be named in accordance with the established rules.
All project participants shall regularly save their work and synchronize models with central location, so as to provide actual information to other stakeholders. In addition, this mini-mizes risk of data loss.
Linked files shall be included into their own worksets. Users shall prefer creating links, avoiding file import.
Synchronization procedure shall be defined in the BEP.
5.2 Using LinksUsing links allows leveraging additional geometry and data in your designs. They can represent either portions of a design that is too large to manage, or data of another discipline that may be developed by a contractor.
Some models require splitting of one object into several more manageable parts, which are then reassembled into a single file i.e. a consolidated model.
As an example of creation of such file, we can consider creation of a consolidated model in Navis-works®, which aggregates files of different design disciplines created in Revit®.
If the model data is segregated into individual files, the following guidelines need to be observed:
Tasks shall be distributed between participants in order to minimize the need to switch be-tween files.
When using links, model should lie in the correct location respective to the pre-agreed sys-tem coordinates in the base file.
Links between design disciplines
Each individual discipline involved into the project should have its own model and carry responsibil-ity for it.
Model developed by a discipline can refer to the model of other disciplines in coordination pur-poses.
The following guidelines shall be observed:
61
Agreed project location coordinates and the direction of true north shall be documented from the outset, and no deviation shall take place. If you see a need for any changes in the coordinates and the direction of true north, it should be documented in the BEP.
Possession of the elements shall be properly identified and tracked using the Matrix of cor-respondence of LOD and project stages (see Appendix A, Table A.3). This matrix shall be included in the BEP, in order to assign responsibility for each model element for the target LOD at each stage.
Designers who develop a specific design discipline can create a blank model for related discipline in advance to reserve space for subsequent insertion of adjacent model, which does not exist yet. For example, architects can create an empty file for structural model, pre-load it and thus make room for the insertion of the real model when it will be ready.
With models produced for Building Services, several disciplines may be collated in a single model, as a single piece of equipment may require connection to various services. In this scenario, the model may be split in various ways. The BEP shall be consulted in defining the project-specific strategy.
5.3 LOD-based Development of Model ComponentsThe following main principles shall be observed when creating and using the components in the project:
All components shall reside in the library of the specific project or in a central company li-brary.
Components generated during the design development shall be stored in the WIP area of the Common Data environment.
The intended purpose of the components shall be considered during content creation.
The BIM Manager/Coordinator will assess and verify minimum quality compliance before submitting new objects to the central corporate library.
Components shall be developed with the LOD required at the particular stage of design process.
Components of the information model shall be created with the minimum necessary geo-metrical information. The less 3D geometry the information model contains the faster and easier it will be handled.
Revit® allows creating and using families that make use of Coarse, Medium and Fine levels of detail.
Further purposes of the BIM will lead to additional specifications of the content, which should be built to suit the purposes of the deliverables. Information can be added to the ex-isting components either by means of creation of shared parameters and their assignment
62
to specific categories of elements within the design itself, or by separate addition of these parameters to each library component. Method that is to be used shall be defined in the BEP.
A corporate shared parameter file is encouraged in order to maintain consistency of vari-able naming during content creation. Where multiple LODs of the same component do ex-ist, care should be taken to ensure that the same Shared Parameters are incorporated into the objects, in order to maintain data integrity.
Detailed definitions of various LODs are in the Appendix A to this Guide.
5.4 Using 2D Elements for the 3D Model DetailingThe information modeling process allows the use of plain drawings to complement the BIM-model with all necessary information.
The particular BEP shall dictate the point at which intelligent 2D detailing begins to be utilized to prepare the published output.
Detailing and enhancement techniques shall be used whenever possible to reduce model complex-ity, but without compromising the integrity of the model. Detailing is carried out by using Revit® rib-bon Detail panel.
5.5 Levels of Development. Model Development MethodologyLevel of Development system:
Level of Development (LOD) sets the minimum amount of geometric, spatial, quantitative, as well as any attribute information necessary for modeling at a particular stage of the con-struction object life cycle.
Level of Development system is intended for:
Assist all design participants, including technical employers, in a clear understanding and definition of the required results of works on building information modeling.
Planning of building information modeling: in the shared work environment, where other participants depend on the model information model. Design work plan is of paramount im-portance, because model users need to know when they can get the necessary information to properly plan their work.
The Level of Development system includes five basic levels: LOD 100, LOD 200, LOD 300, LOD 400 and LOD 500. They correspond to milestones of the development process, from conceptual to the actual representation. There are many intermediate stages between the basic levels. Thus, the definitions of Levels of Development represent the minimum requirements, so the element reaches
63
the appropriate Level of Development only after all the requirements established by the definition of this level are met. Levels of Development are cumulative; in other words, definition of each sub-sequent level includes the definitions of all the previous levels. For instance, in order to correspond to LOD 300, the element must also meet all the requirements for LOD 200 and LOD 100.
For the basic LOD specification, see Appendix A. Intermediate LODs, if any, shall be specified in the BEP.
There are three aspects of Levels of Development for each model element: completeness of the geometry detail, graphical representation and completeness of attribute data (properties/parame-ters).
Graphical representation: basic geometry display mode (appearance/view, color, material texture etc.)
Completeness of the geometry detail: definition of an element’s geometric parameters (shape, spa-tial position, dimensional envelope, length, width, height, thickness, diameter, area, volume, sec-tion area, slope, level, type etc.)
Completeness of attribute data: definition of the element’s property/parameter set (labeling, corpo-rate classification code, materials, weight, technical and technology parameters, manufacturer, part name, part number etc.)
Parameters (graphical, geometric and attributive) are assigned to the model elements on the basis of the following:
Modeling goals, objectives and required results
BIM use (for instance, extracting all needed geometric and attributive parameters from the model elements for Quantity Take-off)
Project execution stage
Needed scales for drawing release
Needed data for schedules/quantities
Required visualization quality (for instance, highly-detailed photorealistic)
Other applicable requirements
The implementation of the LOD concept is accomplished by means of standards (LOD specifica-tions) of sequential transformations (progressions) for representation of BIM model elements. Along with this, matrix of correspondence between level of detail and project stages is formalized. These procedures regulate the requirements for LOD for various design disciplines. Basic LOD specification and sample matrices for the main design disciplines are listed in Appendix A.
BIM model development methodology makes it possible to use elements with low LOD in the early stages of design. Such elements only need to fill the desired size, and they can be used until the definition completes. Elements gradually become more detailed and obtain more geometric at-tribute components (more LOI), i.e. are transferred from lower to higher LOD.
64
Using elements with predetermined LOD allows determining the expected BIM content on the com-ponent level at different design stages and provides the ability to control BIM project execution.
The following shall be taken into account during the BIM model development:
Elements with lower level of detail (LOD 100 or LOD 200) can be used for design concept studies.
Elements with higher level of detail (LOD 300 or LOD 400) can be used in later design stages.
LOD matrix is necessary in order to unambiguously understand requirements for all design levels and disciplines.
5.6 Work with DWG DrawingsWhen working with 2D content originating from other software (such as AutoCAD® DWG draw-ings), consider the following recommendations:
Avoid using CAD drawings in Revit® as details. They must first be converted into Revit® ob-jects. If the use of CAD drawings cannot be avoided, these files should be linked rather than imported.
If there are linked 2D drawings in the model, team members that are responsible for the sheet compilation shall make sure that all information in these drawings is verified and ap-proved and that it is inserted into the design directly from the CDE Shared area.
Unnecessary elements shall be purged from the CAD files; files shall be audited then.
Avoid CAD files that contain proxy objects and SHX fonts.
Make sure that XRefs are minimized in the CAD file. XRefs shall be attached before insert-ing them into the design.
Existing library of standard 2D details shall be converted from DWG to RVT format.
Use of CAD files needed to support the final documentation shall be minimized where pos-sible.
5.7 Drawing CompilationDrawing compilation and preparation for publication can be carried out in two ways:
Fully assembled compilation of views and sheets within the BIM environment (preferred)
65
Export views in the form of output files for assembly and graphical enhancement using 2D detailing tools within a CAD environment. Such a way is not covered by this standard and should be avoided where possible.
Sheet composition direct from within the BIM
Drawing sheet composition from within a BIM environment shall be established through the linking of views, callouts and elevations to drawing sheets fully within the BIM authoring software.
Care shall be taken to ensure that any referenced data is available and visible prior to the publica-tion of documentation.
5.8 Modeling in Revit®
5.8.1 Preliminary Data and InformationBefore the development of BIM project starts, the following shall be added to the preliminary data that is composed of design specifications, Employer Information Requirements (EIR), engineering survey results etc.:
BIM Execution Plan (BEP)
Project template libraries for all disciplines
Library of all necessary families.
5.8.2 Project Template libraryProject templates are pre-configured project files that contain downloaded standard families, fields for general project information, sheet elements and customized documentation styles. They pro-vide the basis of the project standardization and increase efficiency, especially in the early stages of model development.
It is recommended to create a separate standard template for each discipline. All templates are included into the template library, which is a part of the company’s central BIM resource library.
5.8.3 Family LibraryIt is necessary to prepare a library of components for the design in advance.
Rules and best practices presented in 5.3, “LOD-based development of model components”, shall be taken into account when you create the components.
66
5.8.4 Data Segregation by Discipline and Templates SelectionThe final result of information modeling process represents a summary model of the construction object, i.e. model aggregated from the individual discipline models. Each design discipline devel-ops its model in a separate design file.
Before the project starts, each discipline chooses the appropriate template from the company tem-plate library.
5.8.5 Creating the Project Files
It is assumed that each design discipline develops its model in a separate file. Each discipline can be represented by one or more design professionals. In the case of team work, you must create a file repository for each discipline.
When you create a design file, the corresponding prepared template must be taken from the library for each design discipline. You also may use a common template for all disciplines including archi-tecture.
5.8.6 Project Base Point and Survey Point
Project base point and survey point exist in every project. They are hidden by default and cannot be deleted.
Project base point represents the project coordinate system origin. All coordinates and elevations are measured relative to this system. The column grid origin shall be aligned with the project base point.
Survey point is a point in the real world; it should be snapped to known geodetic points. It is used to define absolute coordinates and orientation of the project. If absolute coordinates are missing, it is recommended to align the survey point with the project base point.
5.8.7 Conveying Shared Coordinates to Each Discipline Project Files
The first step is to create the Unique reference system file. In this file geodetic coordinates, eleva-tions and north direction are configured. The Unique reference system file may also include survey data and site terrain model, if available.
Unique reference system file creation is followed by preparation of space decomposition file which contains the definition of the horizontal (column grid) and vertical (levels) division.
After that, you shall start creating files within each discipline. These files are loaded into the Unique reference system; each of them is positioned in horizontal and vertical directions and gets the shared coordinates. This ensures the coordination of all discipline design files. A link to the space decomposition file is added for each discipline, and the Copy/Monitor tool is used to create grid axes and levels.
67
Coordinate system match in different files is crucial, especially if designers intend to load the files into Navisworks®—for example, for clash checking.
Creation of the Unique reference system file and conduction of shared coordinates into the disci-pline-specific files are performed by the BIM Manager/Coordinator in accordance to the applicable regulations.
5.8.8 Vertical and Horizontal Space Decomposition
At the design start for each discipline, right after the creation of design files, you need to complete space decomposition in vertical and horizontal directions.
Vertical division is carried out through the creation of levels and corresponding views. Levels shall be established before placing the column grid. The names of levels and views shall conform to the naming rules set out in this standard.
Horizontal division is carried out through the creation of column grid axes whose names shall com-ply with the naming rules.
Using space decomposition file is recommended for the purpose of centralized management of levels and column grid axes.
5.8.9 Project Division into WorksetsDepending on the construction object size, teamwork through the introduction of worksets may be organized. It may be done for separate disciplines or for the whole project as well.
The workset is defined as the set of design object elements which allows teamwork but enables editing of specific elements for only one designer.
Worksets allow multiple users to simultaneously work on a model file through use of a central file and synchronized local copies. Properly utilized, worksets can significantly improve efficiency and effectiveness on large and multi-user projects.
The following shall be observed when using worksets:
Appropriate worksets shall be established and elements assigned, either individually or by category, location, task allocation, etc.
When you create a workset each model element gets a new property: workset that it be-longs to. Each element can simultaneously belong to only one workset.
To improve hardware performance only the required worksets shall be opened. Revit® en-sures that elements contained in closed worksets are still updated if changes made in open Worksets impact them during model regeneration.
Local file shall be created each time after it was closed for any reason. It is not a good prac-tice to open an old local file.
68
A design shall be broken into a sufficient number of worksets to avoid congestion in work-flow. This also provides the means for adequate control over the efficiency of the model.
Worksets shall be named following the conventions defined in the BEP.
All team members shall “Save to Central” hourly.
The Project BIM Coordinator shall allocate a pre-defined, unique slot for each team mem-ber to “Save to Central”. This avoids machines hanging whilst several users try to save si-multaneously.
The “Work-sharing Monitor” tool (available by Subscription) could be used to coordinate “Save to Central” commands across the team.
Users shall not leave the save to central process unattended, and shall resolve any issues which arise to avoid delays to other team members.
If a user accidentally starts synchronization with the repository while another user has al-ready launched this procedure, he/she shall immediately suspend synchronization as long as another user completes it.
5.8.10 Creating the Central File and Local CopiesCentral file is created when you first save the design that contains worksets. This file should be available to all BIM model development participants.
Local files are created by opening the central file and immediate resaving it to a local folder. An-other way to do that is opening the central file with Create New Local option enabled.
Central file is created by the BIM Manager/Coordinator.
Local files are created by each BIM author on his/her own computer.
The central file shall only be opened by the BIM Manager/Coordinator for the purposes of project administration. Other participants are only allowed to open the central file for the purposes of local copy creation.
5.8.11 Managing the Workset Elements
Two methods exist when using worksets to enable multi-user access to a model file:
borrowing elements
owning worksets (Fig.7)
69
Fig.7. Managing the workset elements
In both cases, the user becomes a temporary holder of elements. If another user needs to work with an element, he/she shall request permission from the holder, who may allow or deny the re-quest. An element that is in possession of another team member cannot be edited.
Ways of using worksets in multi-user environment shall be strictly regulated. Regulatory proce-dures shall be defined by the BIM Manager/Coordinator.
Synchronization accompanied by the relinquish of all worksets and borrowed elements shall be performed whenever the user leaves his/her workplace.
5.8.12 Using Families in the ProjectLoadable, system and in-place families are used in projects.
All families developed in-house or provided by building products, equipment and construction ma-terials manufacturers, as well as acquired from third parties and passed through the quality checks become an integral part of the company’s central BIM resource library.
Library families can be developed both within the organization and by external parties, including equipment manufacturers.
The portion of the central library components that is used in a particular design is part of the design BIM resource library. If there is a need to create new families in the course of design development, they are developed according to certain rules, as described in the relevant regulations. These fami-lies are saved in the library of a specific design.
Names of all families and types shall accord with the naming rules.
Development of Families
All families shall be developed on the basis of the pre-defined methodology (see 5.4).
To use the agreed names and avoid redundant data when creating parametric families, shared pa-rameters are recommended. The corporate shared parameters file shall be applied for this pur-
70
pose. This is particularly important when using different LOD for the same element, since there will be several different versions of the file.
The following recommendations shall be observed during the family creation:
Accurate definition of the family’s purpose, expected behavior and necessary parameters is needed.
Parameters can help to determine which element data should be included into scheduled. You need to plan this in advance.
Needed LODs shall be planned for the family in advance.
Revit® supports three levels of model elements graphical representation; this shall be taken into account during the family planning.
When determining the level of detail for the family geometry, keep in mind that there is no need to model the geometry that will not be visible in the design. You do not need to dupli-cate geometry which can be used for different levels of detail.
More detailed family means the larger file size. The larger the file, the slower family loading and regeneration.
Careful attention shall be paid to the selection of the appropriate family template file, as it will determine the further behavior of the component.
Component visibility in different views can be adjusted. For example, for a floor plan you can specify that the 2D projection of the element should be displayed, while 3D views will show it as the three-dimensional body.
When you create parameters, use the Edit Tooltip tool to add a description. Ability to add parameter tooltips was first introduced in Revit® 2015.
Complex families need documentation describing the functionality and the key parameters that determine the behavior of the family.
Use type catalogs when you create families that contain a lot of different types.
Avoid importing CAD geometry into the family file.
Use subcategories for more precise control of the family elements’ visibility.
Nested Families
Families can contain other (nested) families.
The following recommendations shall be observed when nested families are used:
Depth of nesting shall not exceed two levels. The deeper the nesting, the slower is the fam-ily update.
Use families that are nested into several other families carefully: loading of a changed nested family into the design causes the change of all families that contain it.
71
For each particular family, the number of families nested into it shall not exceed 6.
If the nested families’ parameters need to be included into schedules/quantities, assign the “Shared” parameter to the family in Editor.
Family File Size
Family file size shall be minimal, but for each individual case it is necessary to assess the ap-proach rationality: sometimes it is more efficient to use one complex family that allows addressing a lot of issues, than bring in a lot of more simple families.
To make the file size smaller, the following recommendations shall be observed:
Unused elements shall be purged and the family file itself shall be audited before using it in the design.
Nesting of families shall be kept minimal.
Non-standard materials and textures shall be avoided where possible.
Only elements that are covered by the required LOD shall be modeled.
All CAD underlays and raster images shall be deleted from the family file.
CAD files shall never be xploded in the family.
Creating Types in Loadable and System Families
Sometimes during the design development it turns out that the author finds no suitable type of a particular model component. In such a case, creation of a new type based on an existing one is allowed.
Creating a new type based on an existing one shall be done by means of making a copy and as-signing a new name. Editing of existing types is not recommended.
Family Validation
Families that are being created shall be validated:
in the Family Editor environment,
in the design environment.
During the family validation in the design environment, it is recommended:
to validate behavior of all family parameters,
if a large number of families are being created, allocate a tester person (different from the family author) who will perform a “spot validation” on up to 10% of components.
Validation in the Family Editor Environment
72
Check all family parameters to ensure the correct geometry change when the parameters are adjusted.
Check all types in family: change the type, apply it, and then review the geometry to make sure that all sizes and proportions are retained.
For hosted families: check that they are properly adjusted to the changes in the host size. Change the host thickness and make sure that the family correctly changes its geometry.
Check all views for correct display of family graphics at different levels of detail and differ-ent visual styles.
Check constraints/dependencies:
o check grips on the geometry edges to make sure that all geometry is snapped either to reference planes or to the witness lines,
o check the dimension parameter to make sure it is snapped to the reference plane / wit-ness line and not to the geometry itself.
Check connectors:
o right choice of the connector type,o linking connectors,o flow direction.
Validation in the Design Environment
Load the family into a design and check all views for the correct display. If the family has a catalog, use it to load the required types.
Visually inspect the family in all views, at all levels of detail (coarse / medium / fine) and all visual styles.
Check all types in family: change the type, apply it, and then review the geometry to make sure that all sizes and proportions are retained.
Create new types, change all parameters and check the display in all views.
Change all materials and check correctness of their assignment to geometry. To better check the material assignment, change all material parameters to the “glass”. If any part of the geometry does not appear as “glass”, it becomes clear that the parameter is wrongly assigned.
For hosted families:
o place the family onto a host that has the specified thickness and make sure that the family behaves correctly on all applicable hosts,
o adjust host thickness (25-400%) and check whether family geometry becomes de-tached,
o re-check the family appearance to make sure the geometry display is correct,o perform a test visualization,
73
o check the work of Copy/Paste, Rotate and Mirror commands.
5.8.13 Creating the Federated ModelThe primary purpose of the federated model creation is checking for clashes. The first such check shall be performed e.g. when the model is 30% ready.
Federated model shall be created if the design data are segregated by discipline and the model is developed in separate files (either within the company or along with subcontractors).
Using Navisworks® is recommended for the federated model production. Before exporting to Navis-works®, each model should be passed through the Revit® Interference Check tool for clash analysis within a particular discipline.
The following shall be taken into account:
To simplify the analysis and validation of the federated model, each design discipline shall be developed in a separate file according to the rules of data segregation defined in the BEP. If you have a large number of files within any particular discipline, then, in order to optimize the structure of the federated model, creation of a separate federated model for this discipline is allowed. This model becomes part of the whole design’s federated model.
All unused elements shall be disabled in each model file.
All discipline models shall be in the actual state (i.e. reside in the Shared CDE area).
All previously found coordination issues shall be already discussed within the design team.
Each discipline’s model can be brought in Navisworks® in RVT or NWC format. The latter is produced in Revit® using the Navisworks® export extension.
Before you create the final federated model it’s necessary to group the elements according to their function in the discipline files and prepare individual NWC files for aggregation. For this purpose special coordination views are created in Revit®. They only contain the ele-ments needed for clash checks, and accordingly, export shall be performed with the Visible In View option set.
During the design process, parameters need to be added to the Revit® model elements so as to provide subsequent grouping by creation of search sets in the Navisworks® federated model.
In order to avoid unnecessary manipulations, discipline design files shall have the same coordinates. Use the Shared Coordinates option when you export from Revit® to the NWC format.
Given that all views from Revit® will be transferred to the model aggregation software, some views can be pre-configured there. It is recommended to group such views in Revit® by means of the Project Browser.
74
5.8.14 Project ReleaseThis standard assumes that design documentation is created directly from the BIM model.
Project release is the process of preparation to delivery in the following formats:
electronic design documentation, PDF or DWF,
model(s), RVT,
federated model, NWD.
Project release also includes publishing and archiving.
The following shall be observed for the design documentation:
Publishing design documentation in PDF format is carried out by sending the annotated sheets to a virtual PDF printer.
Publishing design documentation in DWF format is carried out by exporting the annotated sheet sets (Application Menu>Export>DWF/DWFx).
Preparing the Model to Publishing/Archiving
The following recommendations shall be observed for publishing/archiving:
Model shall be archived before each checkout at any design stage.
Unneeded and unused elements shall be purged from the model before archiving.
If there are linked files they shall be included with the model itself.
5.8.15 An Example of Information Model Development ProcessAn example of information model development process for a select design discipline is demon-strated in Appendix E.
5.9 Modeling in AutoCAD® Civil 3D®
Design development assumes creation of BIM models that comprise sets of data corresponding to the goals and objectives of the specific project stages and phases.
Various design stages require using of different levels of detail (LOD) in the model.
This standard provides for the use of model elements that have various levels of detail (LOD 100 to LOD 400) in accordance with the basic LOD specifications for infrastructure (see Appendix A, Ta-ble A4: LODs of the basic elements of infrastructure BIM models, their use and properties at the various design stages.)
75
5.9.1 Project Coordinate SystemThe coordinate system in AutoCAD® Civil 3D® acts as the basic coordinate system for the entire project, including data coming from other disciplines. Therefore, the selected coordinate system will have influence on all subsequent design decisions, up to the project delivery and operation of the facility.
That means that the choice of the project coordinate system is a crucial point. The decision must be taken by the BIM Manager/Coordinator in coordination with surveyors who prepare baseline data for the design.
There are two possible variants of establishing the project coordinate system.
Variant 1
Geodetic underlay was created by surveyors without the participation or influence of the BIM Man-ager/Coordinator; transition to a different coordinate system is not required.
In this case the BIM Manager/Coordinator shall request the coordinate system from the company or department that conducted site survey. This information will be essential for the transition to an-other coordinate system or for the correct import of GIS data.
In most cases this would be a local coordinate system.
Using a local coordinate system is not prohibited, but they have certain limitations. The major limi-tation is the inability to pass data on the object’s spatial position to the GPS/GLONASS positioning devices or terrain/map positioning services, such as InfraWorks® 360 and others. All services of this kind are based on the WGS 84 coordinate system, therefore the transition from local coordi-nate systems to WGS 84 is required.
Variant 2
The BIM Manager/Coordinator is able to influence the choice of coordinate system before geodetic underlay creation begins.
In this case the BIM Manager/Coordinator shall not take a decision solely. It is necessary to gather a working group, which should be composed of project executives, surveyors and the BIM Man-ager/Coordinator. The working group, acting in collaboration, shall establish the coordinate system in accordance with the project goals and specifications.
5.9.2 Transitions between Coordinate Systems
To go from the different coordinate systems you need to use functionality of AutoCAD® Map 3D, embedded into AutoCAD® Civil 3D®.
It’s not permitted to use design data obtained as a result of the transition/transformation of coordi-nate systems, if such actions were performed by the BIM Manager/Coordinator without getting ap-proval from a qualified geodesy expert.
76
The algorithm of transition from one coordinate system to another should be done in the following sequence:
Create a source coordinate system in the AutoCAD® Map 3D coordinate library. Create a target coordinate system in the AutoCAD® Map 3D coordinate library. Assign the current coordinate system to the current drawing. Assign the target coordinate system to an empty drawing. Insert the data from the source drawing in the empty drawing using the AutoCAD® Map 3D
query tool.
Note that copying the data between the drawings with different coordinate systems does not work. Only an AutoCAD® Map 3D query is allowed.
5.9.3 Using Coordinate System Displacement for Existing Infrastructure As-setsParallel use of various software where different coordinate systems ideology is established (Revit®, Inventor® etc.) causes coordinate system compatibility problems. This is due to the fact that coordi-nate values most commonly used in AutoCAD® or AutoCAD® Civil 3D® go beyond the limits permis-sible in solid modeling and architecture suites.
The simplest and most reliable way to combine data from various software products is the dis-placement of the origin point.
The essence of this method is based on specifying the base point in the territory of the designed facility which will be treated as zero point in other software suites. Its location in AutoCAD® Civil 3D® represents the displacement value to be added to the coordinates of the objects coming from other software suites.
AutoCAD® Civil 3D® acts here as the source of origin point coordinates. To do this:
Create a separate drawing that will serve as the reference for all project participants. Create an AutoCAD® block that looks like a crosshairs in this drawing. Center of the
crosshairs will be treated as the base point. The block must be positioned so that the dis-tance to the most faraway objects that originate from other software does not exceed 9,000 meters. The exact maximum distance is selected in accordance with the software technical limitations.
If objects that are located more than 9,000 meters off the base point come from other soft-ware, it is recommended to split the site territory into several zones and create the own base point for each of them.
Reference drawing is imported into a software suite and is positioned so that the base point is at X=0, Y=0, Z=0 for the design model. Reference drawing should be rotated so that it’s not needed to add the axes rotation angles when the file is inserted in the general model.
When such a model is inserted into AutoCAD® Civil 3D® or Navisworks®, you just need to add the displacement coordinates of the axes, which were extracted from the coordinates of the base point.
77
5.9.4 Working in the Revit® and AutoCAD® Civil 3D® Shared Coordinate Sys-temIf AutoCAD® Civil 3D® and Revit® are the only sources of the design data, it is allowed to work in the shared coordinate mode.
This mode is not recommended for linearly extended objects due to potential distortions.
The advantage of this method is that no additional actions are required in AutoCAD® Civil 3D® and Navisworks®. All operations are carried out in Revit® models.
5.9.5 AutoCAD® Civil 3D® Baseline Data
To perform the BIM-based design, the following sets of baseline data in the AutoCAD® Civil 3D® (DWG) drawing format are required:
Digital elevation model in the form of an AutoCAD® Civil 3D® surface or a set of surfaces. AutoCAD® Civil 3D® surfaces describing the territory (asphalt, gravel, walkways etc.) Topographic underlay represented as a set of AutoCAD® objects. Existing utilities data, presented as AutoCAD® Civil 3D® pipe and structure objects. Existing facilities data, presented as AutoCAD® solids. Geological model presented as a set of AutoCAD® Civil 3D® surfaces and AutoCAD®
solids, indicating the volume of geological bodies.
It is recommended to build a set of baseline data from AutoCAD® Civil 3D® objects in a single DWG drawing.
To achieve higher performance when working with a single DWG baseline data drawing, it is rec-ommended to represent geological layers, models of buildings and engineering structures as Auto-CAD® 3D solids in separate files. These file are stored in a shared folder and are linked to the sin-gle DWG drawing as AutoCAD® XRefs without displacement and scaling. XRef are of Overlay type, and no path is specified.
In addition, it is recommended to prescribe the need for NWC and/or NWD format baseline data in addition to the AutoCAD® Civil 3D® DWG drawings in the survey specifications and Employer Infor-mation Requirements. These files shall contain data exported from the baseline set in AutoCAD® Civil 3D® format. Baseline data shall be saved in the separate AutoCAD® Civil 3D® files before ex-port to NWC or NWD:
digital elevation model, surfaces describing the territory, existing utilities, existing facilities and infrastructure, geological model.
Export of data from AutoCAD® Civil 3D® to NWC format shall be done with the NWCOUT com-mand. If AutoCAD® Civil 3D® does not recognize this command, you must install the Navisworks® NWC File Export Utility, which can be downloaded from the official Autodesk site.
78
Before executing NWCOUT, drawing shall be prepared for export as follows:
all AutoCAD® Civil 3D® objects that do not need to be exported shall be turned off by using the “None” style or via AutoCAD® layer system,
all AutoCAD® objects shall be turned off or frozen via AutoCAD® layer system.
Presence of any objects or layers other than needed is not allowed.
5.9.6 Geological Model
The geological model is a set of AutoCAD® Civil 3D® triangulation models (surfaces) that represent the top and base of geological layers. It also contains AutoCAD® solids that display the strength of the geological layer boundaries and are spatially limited by surfaces.
The geological model is put together within the area bounded by earth bores on the pre-construc-tion survey plan.
The top and base surfaces of geological layers are found upon the bore arrangement and geologi-cal cross-sections.
You can create geological surfaces using either Autodesk Geotechnical Module tools or standard tools for creating and editing of AutoCAD® Civil 3D® triangulation surfaces.
Triangulation top and base surfaces of geological layers are finalized for compliance with shaped geological cross-sections represented in the baseline data.
If there is a lense (i.e. layer end point is located between the bores) then this point is added to the surface of the corresponding geological layers.
If the geological layer surfaces intersect then two points are added on the intersection line (at the beginning and at the end of the intersection segment). Points are added to all related surfaces.
Solid models are built at the location of earth bores. These models illustrate the bore content by means of conventional AutoCAD® 3D solids, created in accordance with the bore diagram.
AutoCAD® 3D solids are also inserted between the geological layer surfaces.
Solids are distributed between layers in accordance with the geological layer structure.
Solids are formed by sweeping geological layer faces along the vertically oriented path.
Using AutoCAD® Civil 3D® standard tool for automatic creation of AutoCAD® 3D solids (_AeccEx-portSurfaceToSolid) is only allowed when layer top and base boundaries coincide. Otherwise, the resulting solid will be incorrect.
If the geological layer file size exceeds 15 MB, the file shall be divided into several parts.
Names of AutoCAD® Civil 3D® geological surfaces are formed from the following components (no spaces allowed):
<Field1>_<Field2>_<Field3>_<Field4>
79
Field1 – subgrade number
Field2 – short description
Field3 – designation of layer top or base
Field4 – additional suffix if there are several similar surfaces
Example:
9_Silt_sandy_loam_Top_1
In addition, for inspection and control purposes geological model catalog shall contain the following information:
layout of mine openings with the number of each one; results of geological survey post-processing in the form of geological cross-sections. Tab-
ular information is duplicated in Microsoft Excel; bore data: number of bore, number of geotechnical element, absolute elevation and geo-
logical layer strength; tables of guideline and calculated values of subsoils.
5.9.7 TopographyThe drawing of topographic situation is formed in AutoCAD® Civil 3D® model space in the project coordinate system. Drawing units are metric.
Various groups of AutoCAD® file objects are structured by means of layers.
Layer names are specified in accordance with a codifier used for handling the survey data pre-pared in AutoCAD®.
Graphical schematic symbols for topographical plans are formed of AutoCAD® blocks. The block names are specified in accordance with the classification system established in Russian Federa-tion or in the project territory.
It’s not allowed to create of topographic signs in the third-party software.
5.9.8 Existing Utility Networks
Existing utilities can be modeled in the following ways:
Variant 1
Utility networks are represented by AutoCAD® Civil 3D® pipe and structure models. Names and el-evations of AutoCAD® Civil 3D® pipe networks correspond to names and elevations of existing utili-ties.
Variant 2
80
Utility networks are represented by AutoCAD® Civil 3D® feature lines. Names and elevations of fea-ture lines correspond to names and elevations of existing utilities.
Variant 3
Utility networks are represented by 3D polylines. Polylines are distributed between the layers in accordance with the names of existing utilities, are annotated in the plan view and have the same elevation values as the existing utilities.
Variant 1 is recommended. Variant 2 and 3 are also permitted but require some additional actions from the BIM Manager/Coordinator who needs to compose models of AutoCAD® Civil 3D® pipes and structures.
In the case of baseline data incompleteness some assumptions are made for modeling the exter-nal networks. These assumptions shall be agreed between the BIM Manager/Coordinator, profes-sionals who create the survey model and subject matter experts who are able to complete the missing data in accordance with the regulations (laying depth, structure diameters, pipe diameters, etc.)
Intersections with existing utility networks are not allowed.
Extra information shall accompany models of existing utilities: structure tables with indicated num-bers of each one, laying depth and diameters of the incoming and outgoing pipes. Structure num-bers shall match the numbers indicated in the plan view.
5.9.9 Existing Facilities and InfrastructureThe exact list of facilities and infrastructure to be modeled is defined in the project specifications or in the EIR.
This portion of design requires careful pre-assessment of data on facilities/infrastructure needed for designers and the BIM Manager/Coordinator. To do this, you must weigh the complexity of cre-ating objects, upcoming design decisions and the existing infrastructure, and then select only needed objects and the level of detail. The overvaluation of project needs can lead to serious hu-man and financial costs that will have no effect.
To obtain data on existing facilities and infrastructure, in addition to traditional methods, we recom-mend methods of photogrammetric survey and photogrammetric data processing in Autodesk Re-cap.
All objects in this portion should be formed of the following types:
AutoCAD® Civil 3D® triangulation surfaces AutoCAD® 3D Solids AutoCAD® Civil 3D® corridors AutoCAD® Civil 3D® pipes and structures
81
5.9.10 Export from AutoCAD® Civil 3D® to Navisworks®
AutoCAD® Civil 3D® data can be exported to Navisworks® by:
Method 1. Import a DWG file to Navisworks®.
Method 2. Export an NWC file from AutoCAD® Civil 3D® using the NWCOUT command.
Method 1 is not recommended, because AutoCAD® Civil 3D® objects may be not correctly handled. Instead, use the method 2. Method 1 is only recommended for transferring AutoCAD® objects.
If AutoCAD® Civil 3D® does not recognize the NWCOUT command, the free Navisworks® NWC ex-port utility must be installed.
Before executing the NWCOUT command you should:
Turn off all AutoCAD® Civil 3D® data you don’t want to export by applying the style "Noth-ing" or through the AutoCAD® layers
All AutoCAD® data should be turned off or frozen through the AutoCAD® layers.
Be sure your DWG file contains only data you want to export.
It is not allowed to create a single NWC file that contains all design objects or disciplines. Data passed to NWC file shall be segregated by discipline/object.
For example, for pipe networks you should create several individual NWC files by system (drainage, water, gas, etc.). If the infrastructure asset is too large, as well as if the design is divided into phases, it is recommended to separate these files by zones or stations. For the auto roads subdiscipline it is recommended to split files by the station value, by road type and by zones (queues).
The division by object and by discipline is necessary to maximize the clarity and convenience in the Navisworks® selection tree.
Naming of NWC files should be done with the following factors taken into account:
names will act as landmarks in the Navisworks® selection tree, and therefore they shall be as short and descriptive as possible;
spaces are not allowed; use the underscore “_” instead; if the design model number is required in the name, object description shall be added in
brackets.
5.9.11 Export from AutoCAD® Civil 3D® to AutoCAD®
Do not open AutoCAD® Civil 3D® drawings directly in AutoCAD®. Instead, use AutoCAD® Civil 3D® export utility and then open the exported file in AutoCAD®.
It is recommended to use AutoCAD® Civil 3D® 2015 or later.
After exporting the size of the drawing is reduced, and AutoCAD® Civil 3D® data is converted into a set of AutoCAD® 3D objects.
82
5.9.12 Export from AutoCAD® Civil 3D® to Revit®
You can export:
1. AutoCAD® Civil 3D® surfaces.
2. Pipes, corridors and connection points.
Exporting AutoCAD® Civil 3D® Surfaces
There are three methods of exporting surfaces from AutoCAD® Civil 3D® to Revit®:
Exporting surfaces as contours
You apply a surface style to represent a surface as a set of contour lines, and then export to DWG (or extract contours from the surface).
The resulting surface has a very low accuracy. Complex terrain elements and retaining walls can-not be modeled. Therefore, this method is not recommended, although can be used for visualiza-tions.
Exporting surfaces as 3D faces
You apply a surface style to represent a surface as a set of 3D faces, and then export to DWG (or extract 3D faces from the surface).
If your surface is not complex, the resulting surface will have enough accuracy. Complex terrain elements and retaining walls cannot be modeled.
Exporting surfaces using COGO points
This method requires polylines, lines or break lines. Do the following:
Convert the surface into a set of 3D faces. Create COGO points on lines denoting a complex terrain. Increment should be less than
1 m. The smaller the increment, the higher the precision of the surface in Revit®. Create a surface and convert it into 3D faces. Export 3D faces to Revit® using DWG.
This method is recommended in case of a complex terrain.
Exporting pipe networks and corridors
Corridors and pipe networks should be exported as AutoCAD® 3D solids.
Converting AutoCAD® Civil 3D® corridors into AutoCAD® solids is possible, starting with AutoCAD® Civil 3D® 2015.
You can use AutoCAD® Civil 3D® Productivity Pack to convert pipe networks into AutoCAD® solids but this software may work incorrectly in some cases. If your AutoCAD® Civil 3D® Productivity Pack doesn’t work correctly or not available in your company, you can do the following:
83
Select the pipe elements and execute the EXPLODE command. This creates an instance of AutoCAD® block.
Execute the EXPLODE command again. This creates an AutoCAD® solid. Export the drawing to AutoCAD® and then to Revit®.
5.9.13 Data Exchange between AutoCAD® Civil 3D® and Revit® Using ADSKADSK format makes a data exchange between AutoCAD® Civil 3D® and Revit® easier.
Using the ADSK format is recommended only if you double-check coordinates.
5.9.14 Export from AutoCAD® Civil 3D® to InfraWorks® 360 Exporting surfaces, alignments, profiles, pipe networks, corridors and corridor surfaces from Auto-CAD® Civil 3D® to InfraWorks® 360 should be done through the IMX format. Ensure that coordinate systems in AutoCAD® Civil 3D® and InfraWorks® 360 are the same.
You can use formats other than IMX when you work in InfraWorks® 360.
To export loops from AutoCAD® it is recommended to create AutoCAD® Civil 3D® parcels using loops. Parcels should be transmitted through the ODF file format by exporting AutoCAD® Civil 3D® objects to SDF files (_AeccExportToSDF command).
5.9.15 Working With a Subassembly Library
Subassemblies can be created by BIM Manager / Coordinator or by team members.
It is not allowed to add subassemblies that have any warning message in the EventViewer tab in SAC!
Before adding to the library, any subassembly must be tested by BIM Manager / Coordinator.
Subassemblies should be stored in a shared folder on a local network. The edit privileges are as-signed only to BIM Manager / Coordinator.
Each seat should have a separate palette. It is recommended to split the elements by the type of tasks and place each type to a separate palette.
5.9.16 Grouping SAC Objects
The SAC objects must be grouped. In particular, the objects with branching and other complex ele-ments should be placed into the Flowchart. The objects with strictly consecutive elements should be placed to Sequence.
It is not recommended to place the following elements to the basic Subassembly Flowchart:
84
Geometry; Advanced Geometry; Auxiliary.
They should be grouped in Flowchart or Sequence.
85
6 VALIDATION PROCESS
Validation is the process of checking the modeling results for compliance. The validation goals are finding out whether the model conforms to EIR and company standards, is accurate, optimized and complete, supports seamless identification and extraction of information from the BIM-model ele-ments, is free of clashes and so forth.
6.1 General Quality Control StrategyThe BIM Manager/Coordinator shall develop and implement the quality control system for BIM models based on regular inspections and coordination meetings.
The quality control system shall be based on an agreed set of rules, requirements and procedures of this standard.
Each BIM author shall be responsible for the quality of information models in his/her design disci-pline.
6.2 Various Kinds of InspectionValidation should be conducted in the following areas or their combinations:
checks of the spatial position and geometrical parameters, checks of data, 3D coordination checks.
All checks are carried out either in the manual mode (visually) or in an automated way using a vari-ety of software (Revit®, Navisworks®, Microsoft Excel and others).
Checks of the spatial position and geometrical parameters shall include:
Verification of model elements’ compliance with the LOD requirements (geometric compo-nent). Excessive and insufficient levels of development are identified.
Checking for conformity between the coordinate system and the base file. Checking the accuracy of model elements (analysis of elements’ junctions). Checking the absence of duplicated and overlapping elements.
Such inspections are recommended on a weekly basis, but this may vary depending on the partic-ular project.
Checking of data is needed to determine to what extent the data is systematized, classified and structured in accordance with the requirements of this standard and a specific project. The latter shall be recorded in the BEP. The checking shall be conducted on a weekly basis.
Recommended checks are listed in Appendix D, “Model Validation Checklist”.
86
Before the model file is placed in the published data area, it shall be disconnected from the reposi-tory file, and all unused elements and links shall be purged.
6.3 3D Coordination ChecksThis standard established the procedure of making an Autodesk Revit® BIM model ready to clash checks and carrying out such checks in Navisworks® Manage.
3D coordination checks are aimed at finding and resolving all conflicts between model elements in an early stage, before the construction begins.
A clash is an event in which two or more objects in a BIM model collide against each other, due to spatial coordination problems between parts of the model. Clash can be classified in the following way, depending on the kind of intersection:
Hard: physical intersection of element geometries
Clearance: intersection of specified clearance zones around the model elements
It is recommended to perform 3D coordination checks in Navisworks® software:
Visual checks: in Navisworks® Manage/Simulate
Automated checks: in Navisworks® Manage.
The BIM Manager/Coordinator has the responsibility for carrying out automated clash checks, in-forming all stakeholders and managing the process of error resolution.
The diagram of the clash check in a multidisciplinary design is shown on Fig. 8.
87
Fig.8. Clash check process
Fig.9 shows in detail the processes of federated model creation and checking for clashes.
Fig.9. 3D coordination process
3D coordination process consists of the following:
88
Model preparation by discipline with due regard to the requirements
Export to NWC format or creating a set of NWD files in batch mode
Creating the federated model
Creating selection sets and search sets with consideration for the clash matrix developed in advance
Visual checking for potential design errors and documenting found instances. Creating the report (see Appendix C, Table C.3)
Automated checking for clashes and documenting found instances. Creating the report (see Appendix C, Tables C.1 and C.2);
Clash Analysis
Resolving clashes
6.3.1 Model Preparation by Discipline
Model preparation by discipline is aimed at creating conditions for quick selection and grouping of the federated model elements in the Navisworks® environment.
When developing the design in Revit®, BIM models shall be prepared to effective handling in Nav-isworks®.
Before exporting a BIM model, you shall set up export parameters in Revit® and Navisworks® envi-ronments (see sections 1.1 and 1.2 in Appendix F).
BIM models for each discipline shall be developed in the unified coordinate system.
Note: Unified coordinate system for all disciplines ensures the correct location of submodels in the federated model.
Each model exported from Revit® shall contain views that only include elements participating in the clash checks. It’s recommended to hide all other elements.
Selection of elements in Navisworks® will be facilitated if you create the corresponding parameters in Revit®. The parameters shall be named in such a manner as to undoubtedly identify the model elements.
Note: When working with large files, some issues may arise caused by the specific manner of memory handling in Revit®. For this reason, if you encounter troubles during export from Revit®, it’s recommended to save the design file, close it, and then restart Revit®. Should the issues persist, restart the operating system as well.
In order to have the opportunity to seamlessly update the federated model, you need to fine tune the Navisworks® performance (see Appendix F, section 1.3 “Optimization of the Navisworks® per-formance”.)
89
6.3.2 Exporting models by discipline—sending data to Navisworks®
Exporting models by discipline is aimed at getting integrated files for the subsequent sending out to Navisworks® and formation of the federated model.
BIM models can be sent from Revit® to Navisworks® in one of the following ways:
Direct export to the NWC format
Import the Revit® project file (RVT) in Navisworks® environment
NWD files creation in batch mode
In order to ensure the update of federated model after any modification of the discipline models, new export from Revit® shall be done without changing the names of the compound files.
See the detailed export description in Appendix F, section 2 “Model Export by Discipline – Trans-ferring Data to Navisworks®”.
6.3.3 Creating the Federated ModelThe purpose of the federated model creation is the consolidation of several single-discipline mod-els and checking for clashes.
The federated model shall be created by loading compound files that were generated by exporting models from Revit® by discipline (see Appendix F, section 3 “Creating the Federated Model”).
6.3.4 Clash MatrixClash matrix is a table defining the groups of elements that shall be checked for spatial intersec-tions. An example of the clash matrix is shown in Fig.10.
The purpose of the clash matrix creation is the preliminary assignment of the groups of elements for participation in the clash check procedures.
The clash matrix shall be created in accordance with the check priorities (see Appendix F, section 4.1 “Clash Matrix”).
The check priorities may vary depending on the particular design, its goals and tasks.
The clash matrix content and its final appearance for the particular design shall be defined in BEP.
90
Fig.10. An example of the clash matrix
6.3.5 Creating Selection Sets and Search SetsThe purpose of the sets creation is preparing the model to the automated clash checks.
Selection sets and search sets shall be created on the basis of the clash matrix, as described in Appendix F, section 4.2 “Creating Selection Sets and Search Sets”.
Using intelligent search sets is recommended for the automated checks.
It is recommended to export the created sets into a separate file for reuse in similar designs.
6.3.6 Visual Check for Clashes
The visual check is aimed at detecting clashes that cannot be found by means of the automated check.
The visual check shall be carried out by means of the model walk-through using the navigation, section and measurement tools.
Clashes that were detected shall be documented using the review tools. See Appendix F, section 5.2 “Documenting the Detected Clashes”.
The visual check report shall be generated. See Appendix C, Table C.3.
Note: Keep in mind that the model walk-through is performed on the perspective view. If you call the SwitchBack tool, Revit® creates a perspective camera view which is not a working view. So, before calling the SwitchBack, it’s recommended to switch to an orthographic view for quick posi-tioning of an element in Revit®. If you need to use SwitchBack during the object walk-through/fly-through then set the Walk/Fly mode off before switching to an orthographic view.
91
6.3.7 Automated Clash CheckThe automated check is aimed at the fast-track detecting multiple clashes in the federated model using the Navisworks® Manage functionality.
Using intelligent search sets, as well as selection sets, is recommended for identification of ele-ments that have to be included.
The recommended automated check process is shown in Fig.11.
Fig.11. The recommended automated clash check process
The automated check process is composed of:
Creating a clash test
Selecting elements for checking
Setting test criteria and options
Running the test
Creating clash check reports
For the more detailed description of the automated clash check procedure, see Appendix G.
It is recommended to save the created clash tests in a separate file for reuse in similar designs.
The clash check report and summary report shall be generated. See Appendix C, Tables C.1. and C.2.
6.3.8 Clash AnalysisThe clash analysis process is aimed at preparing to assignment of people responsible for their res-olution.
Normally, clash resolution is put in charge of the BIM authors who developed the respective parts of design.
92
Some recommendations on the clash analysis procedure are given in Appendix F, section 7 “Clash Analysis”.
Analysis and assignment of persons responsible for resolution are usually being done at the coor-dination meetings. See section “BIM Coordination Meetings” of this Guide.
6.3.9 Resolving ClashesThe clash resolution process is aimed at making corrections in the source discipline BIM models, preparing the models to the next clash check, and reducing to zero the number of total clashes in the design.
The clash analysis results shall be returned from Navisworks® to Revit®. This procedure is de-scribed in detail in Appendix F, section 8 “Resolution of Detected Clashes”.
Resolving of each particular clash is confirmed by changing its status to “Resolved” when the test is re-run.
Resolution of clashes shall be documented in the re-run check reports.
6.4 BIM Coordination MeetingsCoordination meetings shall be held in order to analyze found clash, look for the ways of their reso-lutions and assignment of responsible persons. Leaders of all relevant groups/departments/disci-plines, the BIM Manager(s)/Coordinator(s) and the project manager shall participate.
Coordination meetings are held as appropriate. They include discussing the general issues of the implementation of BIM project, as well as issues related to clashes identified during inspections. In particular, discussions cover the progress of the project in the modeling context, location of partici-pants and their tasks, backlogged tasks identified at the previous meeting, matters of collective in-teraction, unresolved technical problems, amount of work on the contract and compliance with the BEP, validation and finding solution for the identified conflicts, assignment of professionals respon-sible for resolution, need for additional resources.
Coordination meetings can be combined with other meetings, devoted to the implementation of the project based on BIM.
93
7 BEST PRACTICES
7.1 Ensuring Model Quality
Model Maintenance
Revit® models must go through the maintenance on a regular basis in order to improve stability, speed and efficiency. Irregular maintenance can cause distortions in the models and thus directly affect the work performance of all design disciplines.
The maintenance process includes checking Revit® model, model file compression, verification and elimination of errors, eliminating unused items, removing unnecessary views etc.
Central File
It is prohibited to open the central file during the everyday design process. Its opening is only al-lowed for the purpose of model maintenance.
The central file shall be re-created and re-saved as a new file at regular intervals to prevent the appearance and accumulation of redundant data. This action shall be carried out regularly. Saving frequency is set out empirically, depending on the model size.
Local files are created daily to improve efficiency. Avoid continuing design work at the beginning of the working day by opening of the saved local file (Update Time Stamp) and reloading the latest changes (Reload Latest). Such practice is only allowed if the models are temporarily disconnected from the network.
Compression of Central File and Local Files
Central file compression reduces the storage size when saving files that use the worksets. Nor-mally Revit® applications only add the new and changed items to the existing files during the save operation. This increases file sizes, but speeds up the save process. The compression process overwrites the entire file and removes obsolete data to save space.
Since the compression process takes longer than the usual saving, compression shall only be done if the interruption of the working process is permitted. Compression shall be launched by the BIM Manager/Coordinator.
Importing and Linking Files
To speed up handling of models that contain linked files you shall unload all links that are not nec-essary for a particular task. As required, files can be reloaded.
Warning Messages
94
All warnings, in particular related to geometric errors, clashes and incorrect settings of engineering systems, shall be checked on a regular basis, and their causes shall be eliminated. Users shall re-move the cause of the warning message, and the BIM Manager/Coordinator shall view a list of messages as frequently as possible.
Current number of warning messages shall not exceed 200. A larger number of warnings influ-ences the model appearance and can cause other problems with the model.
Ordinary warnings are not as important as the geometric errors and engineering systems warnings. They may be ignored; however they also affect the efficiency.
Archiving the Model
The model shall be archived before publishing. For the aggregation of models and all the related files eTransmit function should be used.
Models shall be archived at their integrity on each date and at each stage of the documentation publication. Archiving shall also include related files and the set of published documents in DWF/PDF format. Archived files are stored in a folder with the appropriate label.
Saving the Model
The maximum number of backup copies of the Revit® model shall be at least five times greater than the total number of users working with it. If the team is less experienced, it is permissible to increase this figure to ten. Available storage space shall be requested from IT professionals re-sponsible for the project. Also note that overwriting the repository file causes the loss of all previ-ous network backups. Don’t forget to archive the project before overwriting the central model!
Backup copy of the central file shall be saved daily; it has to be done by copying the whole central file folder.
Synchronize with Central command shall be executed at least hourly. It is necessary to avoid model hang-up: synchronized saving shall be coordinated and carried out at regular intervals, es-pecially if large group of specialists share one model. Worksharing Monitor can be used to review the modeling activity level.
Revit® save reminder interval shall be set to 30mins.
An initial view that contains mostly text shall be specified in the design files in order to speed up the file opening process.
7.2 Effective Ways of Template CreationThough this list is not exhaustive, many of recommendations given here will improve productivity and efficiency.
Create a new empty drawing view, which will be used to open the design, and specify it as the Starting View. It is displayed when you open the design file, regardless of which view
95
was active before the last save. This will prevent loading graphically rich views, free up more RAM and increase the project loading speed. The Starting View may, for example, contain a description of the company standard main parameters.
Do not include too many families in one template. To reduce the project size, load only those families that are used often (for example, the most basic windows and doors).
Set the parameters in advance and add the key notes (if your company uses them) for any families that are loaded in the project.
Don’t load too many wall types; 5 or 6 most frequently used is quite enough. Set all the parameters for wall types included in your design (for example, type label, class
of fire danger, etc.) Set up a few default sheets for permanent use: for example, the title page for a specific set
of drawings. Typically, this list looks the same in all projects, so it shall be prepared in ad-vance with room left for images, schedules, etc. The same recommendations apply to the sheet that contains details.
Create view templates that will define the design standards when creating new views. Upload a few standard title blocks. Attach one or two title blocks for presentations and load
the standard title block for design documentation. Attach title blocks for additions. Set up standard schedules. Create a room schedule, window opening fill quantity and
equipment schedule. This will allow having schedules at hand during the design develop-ment.
Create a few drawing views for standard parts (e.g. parts of doors and windows) which are regularly used in all designs.
If renovation projects constitute a considerable portion of the company’s business then set up the stages and graphics overrides.
Use the Transfer Project Standards feature to import elements from other templates.
Migrate templates to the newest Revit® release before the new project starts.
7.3. Revit® Architectural Template ChecklistA list of items to be included in the design template follows below.
Sheets: Create and set up sheet skeletons for project release.
Line styles: Set up standard styles and purge unneeded ones.
Line weights: Set up standard weights and purge unneeded ones.
Line patterns: Set up standard patterns and purge unneeded ones.
Text styles: Set up standard styles and purge unneeded ones.
Dimension styles: Set up standard styles and purge unneeded ones.
Title blocks: Load standard title blocks.
Wall types: Set up standard types and attach a few shared types to be used to create quick sketches. Only the most frequently used types will be required.
96
Roof types: Set up standard types.
Slab and floor types: Set up standard types.
Ceiling types: Set up standard types.
Project Browser arrangement: Customize the arrangement and display of views and sheets in Project Browser. The arrangement is often based on the user parameters.
Parameters: Define and add all necessary parameters.
Door families: Create the most frequently used templates and add them to the template.
Window families: Create the most frequently used templates and add them to the tem-plate.
Keynotes: Create a classifier and select the keynote file (if the company uses the classifi-cation system).
Quantities and schedules: Create the most frequently used schedules, such as door schedules and window schedules.
Legends: Create the standard legends, such as door/window legends, flooring schedule etc.
DWG export: Define the export settings in accordance with the corporate CAD standard.
DWG import: Define the import settings if needed.
Title sheet: Set up the title sheet.
Shared data sheet: Set up the shared data sheet.
Project units: Set up the project units.
File locations: Define project file locations for quick navigation and saving.
Site parameters: Define and set up the contour display, sections and parcel boundaries.
View templates: Create standard view settings and save them as the view templates.
Fill patterns: Create and load needed fill patterns.
Materials: Create and set up the most needed materials.
Object styles: Add new object styles and review the existing ones.
Phases: Create if needed. Inclusion into a separate template may be required.
Levels: Create the needed levels on the elevation views.
Color fills: Create the basic color fills if needed
97
Display filters: preset the display filters in accordance with the planned design require-ments.
Ticks: Set up if needed.
Tags: Configure to match the standards and load the most needed ones into the template.
Temporary dimensions: Set the temporary dimension properties.
Snaps: Set up the snap parameters.
Hotkeys: Set up the most frequently used hotkeys. Their desired combination can be ex-ported to an XML file.
View level of detail: Set up the LOD for the newly created views.
Annotation symbols: Customize annotation symbols to match the standards; load the most commonly used ones, such as North arrow, grid axes, elevations marks, etc. into the template.
Additional components: Add other frequently used families (furniture, columns, entourage etc.) to the template.
7.4 Data Segregation between DisciplinesWhen large and complex projects are developed in the multi-disciplinary environment it’s recom-mended to divide the model into portions in accordance with the strategy agreed between partici-pants of the design team and documented in the BEP. Model file size can act as one of the criteria for the division. A good practice is to divide the model when it exceeds 150 MB.
Linking enables additional geometry and data to be referenced into a model. This may be either other parts of a design which are too big to manage in a single file, or data from another discipline or external company.
When linking files, the following important aspects shall be taken into account:
Task allocation shall be considered when dividing the model so as to minimize the need for users to switch between models.
Division shall be determined by the BIM Manager/Coordinator in conjunction with the project leads. It shall be documented in the BEP.
Actual coordinates shall be set by using the Shared Coordinates function for re-pinning models with the Project Location panel tools.
Each sub-model shall be reopened and the other sub-models Linked in as required using the “By Shared Coordinates” insertion method.
When the file is divided into the sub-models, the workflow illustrated in Fig.12 shall be observed.
98
Fig.12. Splitting a file into sub-models
Each separate discipline whether internal or external, involved in a project shall have its own model and is responsible for the contents of that model. A discipline can Link in another discipline’s Shared model for reference.
Shared Coordinates and Project North rotation shall be agreed and documented at the out-set.
Details of any discipline-specific requirements, such as the difference between Finished Floor Level and Structural Slab Level, shall be fully documented in the BIM Execution Plan.
The Copy and Monitor tools in Revit® shall be used to duplicate and relate Levels and Grids, as well as to duplicate and trace pieces of equipment.
The Copy Monitor tools shall not be used for other element categories without a full under-standing of limitations, such as the creation and update of certain elements is not reflected in the monitoring process.
Ownership of elements shall be properly communicated and tracked through the project time-line (e.g. floors may be created by the Architectural team, but are then adopted by the Structural team to form part of the load-bearing structure).
99
APPENDIX A
LOD SpecificationsTable A.1. Definition of basic Levels of Detail of a BIM model
LOD Definition Basic use Model / element examples
LOD 100 A model element is represented as a set of mass ele-ments with ap-proximate di-mensions, shape, spatial positions and orientation, or as a 2D sym-bol
Preliminary De-sign stage; justi-fication of in-vestment and creation of ar-chitectural con-cept
LOD 200 A model element is represented as an object or an assembly that reflects a part of a building system with preliminary dimensions, shape, spatial position, orienta-tion, and all re-quired attributes
LOD 300 A model element is represented as an object or an assembly that belongs to a par-
Design stage; creation of the design docu-mentation
100
ticular building system with ex-act dimensions, shape, spatial position, orienta-tion, connec-tions and all re-quired attributes
Detection of clashes be-tween disci-plines
LOD 400 A model element is represented as a specific assem-bly with exact di-mensions (includ-ing those of de-tail elements), shape, spatial position, orienta-tion, detail con-nectors (bolts, rivets, welds, shaped elements, dowels, embed-ded items etc.), fabrication data and all required attributes
Design stage
- creation of the design docu-mentation
Construction stage
- creation of the project execu-tion plan
LOD 500 A model element is represented as a specific assem-bly with actual dimensions, shape, spatial position, orienta-tion and attributes required to pass the model to op-eration
Construction stage: creation of an “as-built” model
“As-built” model is created by modification of the BIM model on the basis of post-completion documentation and/or laser scans of the building/facility. It may be used at the operation
101
phase for vari-ous purposes
102
Table A.2. Example of LOD matrix for Architectural Design
ComponentsPreliminary Design stage Design / Detailed Design stage
LOD 100 LOD 200 LOD 300 LOD 400
WallType, approximate
geometry
Precise dimensions, location, room bound-
ary
Exact visual representation, structure, material, slope, tag, fire rating
Manufacturer, part name, part number
DeckType, Approximate
geometry
Precise dimensions, location, room bound-
ary
Exact visual representation, structure, material, slope, tag, fire rating
Same as LOD 300
FloorNo specific re-
quirementsNo specific require-
ments
Type, approximate geometry, precise dimensions, ex-act visual representation, structure, location, material,
slope, room boundary, tag
Manufacturer, Part name, Part number
ColumnApproximate ge-
ometryType, precise dimen-
sions, locationExact visual representation, section/profile, structure,
material, room boundary, tagSame as LOD 300
CeilingNo specific re-
quirementsNo specific require-
ments
Type, approximate geometry, precise dimensions, ex-act visual representation, structure, location, material,
slope, room boundary, tag
Manufacturer,part name, part number
WindowApproximate ge-
ometryType, location
Precise dimensions, exact visual representation, structure, material, tag
Manufacturer, fittings/acces-sories
DoorApproximate ge-
ometryType, location
Precise dimensions, exact visual representation, structure, material, tag, fire rating
Manufacturer, fittings/acces-sories
StaircaseApproximate ge-
ometryLocation
Type, precise dimensions, structure, material, slope, tag
Same as LOD 300
LandingApproximate ge-
ometryType, location Precise dimensions, structure, material, tag Same as LOD 300
103
ComponentsPreliminary Design stage Design / Detailed Design stage
LOD 100 LOD 200 LOD 300 LOD 400
HandrailsApproximate ge-
ometrySame as LOD 100
Type, precise dimensions, exact visual representation, structure, location, material, tag
Section/profile, fittings/acces-sories, manufacturer, part name,
part number
Heavy façadeApproximate ge-
ometrySame as LOD 100
Type, precise dimensions, exact visual representation, structure, location, material, tag
Section/profile, fittings/acces-sories, manufacturer
ImpostApproximate ge-
ometrySame as LOD 100
Type, precise dimensions, exact visual representation, structure, location, material, tag
Section/profile, manufacturer
RoofApproximate ge-
ometryType, location, room
boundaryPrecise dimensions, structure, material, slope, tag, fire
ratingSame as LOD 300
Plumbing fix-tures
Approximate ge-ometry
LocationType, precise dimensions, exact visual representation,
tagFittings/accessories, part name,
part number
Light façadeApproximate ge-
ometrySame as LOD 100
Type, precise dimensions, exact visual representation, structure, location, material, slope, tag
Section/profile, fittings/acces-sories, manufacturer, part name,
part number
Entrance rampNo specific re-
quirementsNo specific require-
mentsType, precise dimensions, structure, location, mate-
rial, slope, tagSection/profile
RoomApproximate ge-
ometryType, room boundary Precise dimensions, tag Same as LOD 300
104
Notes to Table A.2
Types
– Name of element that reflects all relevant information on which can uniquely identify and classify the element.
Indicates that the name clearly reflects an element and its function.
Table A.3
Types
Category Description Examples
Wall In the parameters of the walls must be indicated whether the wall is a structural wall, or a self-supporting wall, or a curtain wall, interior or outer wall.
Brick_250_Plas-ter_20_(290), Outer_structural_render_(350)
Deck In the parameters of the deck the deck type must be indi-cated.
Concrete_slab_160_floor_80_(240),
Beamless_Pre-cast_160
Floor Floor may be part of the deck, or be an independent ele-ment. Floor boarding with insulation can be specified as a single layer, with parameters such as pitch and type of boarding.
Floor_tile_12_ad-hesive_3_CPS_40_FNC_25(80),
Floor_linoleum_12_base_8_(20)
Column The parameters must be specified whether the item is structurally self-supporting and non-bearing, as well as the type of material (concrete / steel / wood). This infor-mation may be contained in the name of the element in the form of reference to section type/size.
Con-crete_300x300,
I-bar_I25K_GOST _6020-83
Ceiling It is necessary to specify the type of ceiling, option and material. To specify an option it is sufficient to specify the manufacturer.
Ceiling_counter-ceiling_ARM-STRONG_600x600
Window The following parameters are required: material (PVC / wood), GOST, the number of glass units.
Win-dow_1300x1500_GOST_23166-
105
99,
Window_PVC_1300x1500_dbl_glass_pane
Door Material (wood / steel), single / double. Instead of mate-rial, you can specify the GOST.
Door_PVC_2100x900_Int
Door_DPV_S_B_Pr_2100-970_GOST_30970-2002
Staircase Material (concrete / steel / wood), the angle, the size of the steps, structural features (stringers). All data can be known from the type.
ST45-24.9_Se-ries_1.450.3-7.94_issue2
Landing Material (concrete / steel / wood), thickness. LD_con-crete_1800x2500x350
Handrails Height of handrails, material, GOST. Handrails_Roof_800mm_steel
Wall panel Material, thickness, series. Wall_panel_steel_0.7mm_Poly-styrene_100mm_Steel_0.7mm
Impost Profile part number according to manufacturer’s cata-logue or material of the profile and its dimensions.
Profile_Sq.50x100mm_LSTK
Roof Materials, thickness of layers, manufacturer. Roof_metal_tile_25mm_boarding_40_Paroc_150+framework_150
Plumbing fixtures Purpose, level, power, room type. Wash-basin_wall_400x600_ceramic
Wash-basin_floor_kitchen_steel
Light façade Name, material, place. Bas_relief_wall_gypsum
106
Corner_deco-rate_wall_PVC
Equipment Purpose, power, room type. Table_kitchen_1.2x1.5m
Electrical Equip-ment
Purpose, power. Elevator_ 1250x2500
Entrance ramp Material, type. Entrance_ramp_concrete_tile_30
Approximate geometry
- 3D model has to determine the maximum size of the element, such as width, length, height, and basic shape, which determines the shape of the element, loading etc. (see Fig.13).
Approximate geometry means that the element is placed in the model at the indicative location (wall, floor, and ceiling).
Fig.13. Approximate geometry
General size can be also specified by an analog.
Precise dimensions
- Indicates that the element has a certain size and appearance (except for the cases when the ob-jects have the same or very similar appearance) (see Fig.14).
107
Fig.14. Precise dimensions
Exact visual representation
- Indicates that the appearance corresponds to the actual prototype. The appearance should uniquely determine the functionality of the item, its type, and manufacturer.
108
Table A.4
Exact visual representation
Category Description Example
Wall
Deck
Floor Type and material.
Column If there are column details, they should be displayed.
Ceiling Color, material, type.
Window Color, swing direction, handles, translucency.
Door Color, swing direction, handles, translucency (if any).
Staircase
Landing
109
Handrails Type, baluster.
Heavy façade Color, pattern.
Impost Color, size.
Roof
Plumbing fixtures Color, appearance.
Light façade Color, appearance.
Equipment Functionality, front side, color and class of equipment at cost (premium / economy).
Electrical Equip-ment
Functionality, front side, color and class of equipment at cost (premium / economy).
110
Entrance ramp
Section/profile
- It indicates that the section corresponds to the design.
Structure
- Indicates that elements consist of specified structures.
Wall, floor slab, floor, ceiling, wall panel, roof, entrance ramp: parameters indicating structural ele-ments (for example: beams, sheet thickness).
Window, door, handrail, impost, light façade: structural elements such as frames.
Staircase, landing: with beams and stringers.
Location
- It indicates that the element does not intersect with other elements.
Fittings/accessories
- An element has additional details, apparently identifying its functional purpose, the direction of opening, etc.
Table A.5
Fittings/accessories
Category Description Example
Wall
Deck
Floor
Column
Ceiling
Window Handles, ventilation units. See table A.4
Door Handle, lock, door frame. See table A.4
Staircase
Landing
Handrails Embedded fittings, terminal parts, patterns. See table A.4
Heavy façade Connectors, embedded metals, hairpins (if any). See table A.4
111
Impost
Roof
Plumbing fixtures Mixing valves, showers, etc. See table A.4
Light façade
Equipment Office appliances and objects reflecting element func-tionality (phone, first aid kit).
See table A.4
Electrical Equip-ment
Control panels, power boxes, and additional lamps. See table A.4
Entrance ramp
Material
- Indicates that the element has Material as an additional parameter, or Material is specified in the name.
Tag, manufacturer, part name, part number, weight, power
- Indicates that the element has a parameter that can be specified in the drawings and specifica-tions, in accordance with standards.
112
Table A.6. Example of LOD matrix for Structural Design
ComponentsPreliminary design Design / Detailed Design stage
LOD 100 LOD 200 LOD 300 LOD 400
WallNo specific require-
mentsType, approximate
geometryPrecise dimensions, section/profile, location,
material, tag, weightFire rating
Deck/Roof
No specific require-ments
Type, approximate geometry
Precise dimensions, section/profile, structure, location, material, slope, tag, weight
Exact visual representation, fittings/ac-cessories, manufacturer, part name, part
number, fire rating
ColumnNo specific require-
mentsApproximate geome-
tryType, precise dimensions, section/profile, structure, location, material, tag, weight
Exact visual representation, manufac-turer, part name, part number
OpeningNo specific require-
mentsApproximate geome-
tryType, precise dimensions, location, tag Structure, fittings/accessories
TrussNo specific require-
mentsType, approximate
geometryPrecise dimensions, exact visual representa-
tion, location, material, tag, weight
Section/profile, structure, fittings/acces-sories, manufacturer, part name, part
number, fire rating
Embedded de-tails
No specific require-ments
No specific require-ments
Type, approximate geometry, location, mate-rial, tag
Precise dimensions, exact visual repre-sentation, section/profile, structure, man-
ufacturer, part name, part number, weight
StaircaseNo specific require-
mentsType, approximate
geometryPrecise dimensions, section/profile, structure,
location, material, slope, tag, weightManufacturer, part name, part number
113
ComponentsPreliminary design Design / Detailed Design stage
LOD 100 LOD 200 LOD 300 LOD 400
LandingNo specific require-
mentsType, approximate
geometryPrecise dimensions, section/profile, structure,
location, material, slope, tag, weightManufacturer, part name, part number
ReinforcementNo specific require-
mentsNo specific require-
mentsType, approximate geometry, section/profile,
materialPrecise dimensions, location, tag, manu-facturer, part name, part number, weight
FoundationNo specific require-
mentsType, approximate
geometryPrecise dimensions, section/profile, structure,
location, material, slope, tag, weightManufacturer, part name, part number
PilesNo specific require-
mentsType, approximate
geometryPrecise dimensions, section/profile, structure,
location, material, tag, weightManufacturer, part name, part number
BracesNo specific require-
mentsApproximate geome-
tryType, precise dimensions, section/profile, lo-
cation, material, tag, weight
Exact visual representation, structure, manufacturer, part name, part number,
fire rating
Node pointsNo specific require-
mentsNo specific require-
mentsApproximate geometry, section/profile, loca-
tion, material, weightType, Precise dimensions, Exact visual
representation, Structure, Tag
114
Table A.7. Example of LOD matrix for Ventilation Systems
ComponentsPreliminary Design stage Design / Detailed Design stage
LOD 100 LOD 200 LOD 300 LOD 400
Air outletsNo specific require-
mentsNo specific require-
mentsType, precise dimensions, location, tag, flow, velocity
Manufacturer, part name,exact visual representation,
fittings/accessories
DuctworkNo specific require-
mentsNo specific require-
mentsType, precise dimensions, section/profile, location, mate-
rial, tag, flow, velocity, pressureManufacturer, part name
Air tubesNo specific require-
mentsNo specific require-
mentsType, precise dimensions, section/profile, location, mate-
rial, tag, flow, velocity, pressureManufacturer, part name
ConnectionsNo specific require-
mentsNo specific require-
mentsType, precise dimensions, section/profile, location, mate-
rialManufacturer, part name, ex-
act visual representation
FittingsNo specific require-
mentsNo specific require-
mentsType, precise dimensions, location
Manufacturer, part name, part number, exact visual repre-
sentation, fittings/acces-sories, tag
EquipmentNo specific require-
mentsType, approximate
geometryPrecise dimensions, location, tag, weight, flow, power
Manufacturer, part name,exact visual representation,
fittings/accessories
InsulationNo specific require-
mentsNo specific require-
mentsPrecise dimensions, location, material Manufacturer, part name
115
Table A.8. Example of LOD matrix for Heating Systems
ComponentsPreliminary Design stage Design / Detailed Design stage
LOD 100 LOD 200 LOD 300 LOD 400
EquipmentNo specific require-
mentsType, approximate geome-
tryPrecise dimensions, location, tag, weight, flow,
power
Manufacturer, part name,exact visual representation,
fittings/accessories
PipesNo specific require-
mentsNo specific requirements
Type, precise dimensions, location, material, tag, flow, pressure
Manufacturer, part name
FittingsNo specific require-
mentsNo specific requirements Type, precise dimensions, location
Manufacturer, part name, part number, exact visual
representation, tag
ConnectionsNo specific require-
mentsNo specific requirements Type, precise dimensions, location, material Manufacturer, part name
InsulationNo specific require-
mentsNo specific requirements Type, precise dimensions, location, material Manufacturer, part name
116
Table A.9. Example of LOD matrix for Water Supply, Drainage and Sewage Systems
ComponentsPreliminary Design stage Design / Detailed Design stage
LOD 100 LOD 200 LOD 300 LOD 400
EquipmentNo specific require-
mentsType, approximate geome-
tryPrecise dimensions, location, tag, weight, flow,
power
Manufacturer, part name,exact visual representation,
fittings/accessories
PipesNo specific require-
mentsNo specific requirements
Type, precise dimensions, location, material, tag, flow, pressure
Manufacturer, part name
FittingsNo specific require-
mentsNo specific requirements Type, precise dimensions, location
Manufacturer, part name,exact visual representation,
fittings/accessories, tag
ConnectionsNo specific require-
mentsNo specific requirements Type, precise dimensions, location, material Manufacturer
InsulationNo specific require-
mentsNo specific requirements Type, precise dimensions, location, material Manufacturer, tag
117
Table A.10. Example of LOD matrix for Electrical Systems
ComponentsPreliminary Design stage Design / Detailed Design stage
LOD 100 LOD 200 LOD 300 LOD 400
Lamps No specific requirementsNo specific re-
quirementsType, approximate geometry, location,
tag, power
Precise dimensions, exact visual representation, fittings/accessories,
manufacturer, part name, part number
Switches No specific requirementsNo specific re-
quirementsType, approximate geometry
Precise dimensions, exact visual representation, tag, manufacturer,
part name, part number
Switchboards Approximate geometry Type, location Precise dimensions, tagExact visual representation, manu-facturer, part name, part number,
weight
Equipment Type, approximate geometryPrecise dimen-sions, location
Tag, weight, powerExact visual representation, manu-facturer, part name, part number
Cable trays No specific requirementsNo specific re-
quirementsType, precise dimensions, section/pro-
file, location
Exact visual representation, tag, manufacturer, part name, part
number
Cable tray fittings No specific requirementsNo specific re-
quirementsType, precise dimensions, location,
material Manufacturer
118
Table A.11. Base LOD specification for infrastructure projectsA.11.1. TerrainLOD 100 LOD 200 LOD 300 LOD 400
Geometry:Existing terrain is displayed as a 2D sur-face (plane) with a reference point which is average for the area. If large elevation differences occur, then several surfaces (planes) on different levels are allowed.
Geometry:Existing terrain is displayed as a 3D sur-face based on points, contours and tri-angles, without any complex elements and further editing. Open access data may be used.
Geometry:Existing terrain is displayed as a 3D sur-face, complex elements are included. The surface does not require further editing.
Geometry:Existing terrain is displayed as a set of 3D surfaces, complex elements are in-cluded. Geological survey data and aux-iliary surfaces are added.
Object type(s):2D/3D surface.
Object type(s):3D surface.
Object type(s):3D surface, breaklines (feature lines, polylines, solids)
Object type(s):3D surfaces, breaklines (feature lines, polylines, solids), AutoCAD® solids, point clouds
Properties:Layer, name of surface, mean elevation.
Properties:Layer, name of surface, surface eleva-tions.
Properties:Layer, name of surface, surface eleva-tions.
Properties:Layer, name of surface, surface eleva-tions, solid volumes. Volume between surfaces.
Where used:Conceptual design, initial studies.
Where used:Conceptual design, preliminary design, feasibility study
Where used:Preliminary design, basic design, design documentation, construction manage-ment planning, implementation planning
Where used:Basic design, design documentation, construction, construction management planning, implementation planning
119
A.11.2. Slope modeling
LOD 100 LOD 200 LOD 300 LOD 400
Geometry:Excavation outline is displayed as a 2D surface (plane) with a reference point which is average for the area. If large elevation differences occur, then several surfaces (planes) on different levels are allowed.
Geometry:Excavation outline is connected to the target surface through a slope (approxi-mate) or a retaining wall. The slope or retaining wall is determined by the low-accuracy breaklines or grading objects.
Geometry:3D surface (without complex elements) with 3D breaklines and grading objects. Slope and elevation values are accurate and can be modified; the whole object is then rebuilt accordingly.
Geometry:Detailed 3D surface with complex ele-ments, 3D breaklines and grading ob-jects. Slope and elevation values are accurate and can be modified; the whole object is then rebuilt accordingly.
Object type(s):2D/3D surface
Object type(s):3D surfaces, 3D breaklines
Object type(s):3D surfaces, 3D breaklines, grading objects
Object type(s):3D surfaces, 3D breaklines, grading ob-jects
Properties:Layer, name of surface, mean elevation
Properties:Layer, name of surface, surface eleva-tions, breakline elevations
Properties:Layer, name of surface, surface eleva-tions, breakline elevations, slope values, volumes
Properties:Layer, name of surface, surface eleva-tions, breakline elevations, slope values, volumes
Where used:Conceptual design, initial studies.
Where used:Conceptual design, preliminary design, feasibility study
Where used:Preliminary design, basic design, design documentation, construction manage-ment planning, implementation planning
Where used:Basic design, design documentation, construction, construction management planning, implementation planning
120
A.11.3. Excavation for foundations
LOD 100 LOD 200 LOD 300 LOD 400
Geometry:Rough excavation (foundation not in-cluded) is displayed as a 2D surface (plane) with a bottom reference point which is average for the area. If large elevation differences occur, then several surfaces (planes) on different levels are allowed.
Geometry:Rough excavation (foundation not in-cluded) is displayed as a 2D surface (plane) with a bottom reference point which is average for the area. Connec-tion to the existing surface is made through the vertical walls or arbitrary near-vertical slopes.
Geometry:3D excavation with foundation cuts and correct outcropping. Foundation cuts have vertical walls or near-vertical slopes. Surface inside the excavation is approximate.
Geometry:Detailed 3D surface with foundation cuts and grading objects. Slope and eleva-tion values are accurate and can be modified; the whole object is then rebuilt accordingly.
Object type(s):2D/3D surface
Object type(s):3D surfaces, 3D breaklines, low-accu-racy grading objects
Object type(s):3D surfaces, 3D breaklines, low-accu-racy grading objects
Object type(s):3D surfaces, 3D breaklines, grading objects
Properties:Layer, name of surface, mean elevation
Properties:Layer, name of surface, surface eleva-tions, breakline elevations, approximate volumes
Properties:Layer, name of surface, surface eleva-tions, breakline elevations, slope values, volumes
Properties:Layer, name of surface, surface eleva-tions, breakline elevations, slope values, volumes
Where used:Conceptual design, initial studies.
Where used:Conceptual design, preliminary design, feasibility study
Where used:Preliminary design, basic design, con-struction management planning, imple-mentation planning
Where used:Basic design, design documentation, construction, construction management planning, implementation planning
121
122
APPENDIX B
BIM Execution Plan (BEP) Template
Company Name
Project Name
123
1 BEP
2 Summary
To be filled in after the writing of the plan.
3 Project Details
3.1 Project Description
3.1.1 Project Name
3.1.2 Client
3.1.3 Location
3.1.4 Asset Type
3.1.5 Asset Area
3.1.6 Asset Structure
Building / Facility Number of Stories Area
3.2 Project Phases and Milestones
4 Project Requirements
4.1 LOD Matrix
BIM model shall comply with the requirements defined in the LOD matrix. The matrix defines a list of element categories that will make up the model, and a set of attribute information attached to elements.
LOD matrix shall contain:
Company classification code with reference to the Revit® categories Project milestones Attributes of the model elements BIM uses with reference to the categories and attributes Description of each LOD.
5 Roles and responsibilities
5.1 Roles and Descriptions
5.1.1 BIM Manager
An employee who coordinates tasks among the disciplines. Creates a consolidated model that ag-gregates information from all disciplines.
5.1.2 BIM Coordinator
124
An employee who coordinates the execution of BIM uses on the project level. Deeply understands the requirements of the project; has a good command of the tools (BIM software).
Add other roles as required.
5.2 Task Team
Task team chart. Names, organizational structure. Example:
The names and contact details of the individuals fulfilling the necessary project roles:
Name Role Company Manager Contact Email
Data exchange takes place via the BIM Manager.
5.3 Data Exchange Protocol
Description of data exchange process. Rules for using e-mail and electronic document manage-ment systems. File transfer & publication policy.
6 Scope of BIM Work
6.1 BIM Uses
BIM on this project is to be used for:
3D coordination Design review Shop drawings Schedules.
125
Project Manager
Task Team Member
Task Team Member
Task Team Member
Task Team Member
Task Team Member
BIM Manager
BIM Coordinator
BIM uses:
BIM Use Teams Stages
xx xx xx Technical Design
3D coordination
Design review
Shop drawings
Schedules
6.1.1 BIM Use: 3D coordination
A model-based process that employs software solutions to detect clashes.
6.1.2 BIM Use: Design review
The process of using the model information to validate design decisions by project stakeholders.
6.1.3 BIM Use: Shop drawings
The process of generation of drawing views from the model, as well as the creation of details and annotations required to complete design documentation.
6.1.4 BIM Use: Schedules
The process of using software solutions to collect, organize and share information in the form of tables.
7 Design Model
7.1 Design Model Structure
The design model shall be divided into disciplinary models. Each discipline shall maintain its own central model file.
Description of the structure.
7.2 Unique Reference System (Base Model)
A single reference file is required to coordinate the project. This file contains the project coordinate system definition and the direction of true north.
7.3 Breakdown File
126
A file containing a breakdown of the project both horizontally and vertically. It is the central place of management of grids and levels.
7.4 Disciplines & Subcategories
Discipline Subcategory Description
7.5 BIM Strategy
Factors that affect the BIM strategy.
Criterion Description Impact Solution
Project Type Factors that affect the approach to modeling
Client Requirements LOD matrix
Project Stages Design stage There is no need to model with a high level of detail (only basic design volumes and equipment).
Level of details is de-fined in LOD matrix. Families of equipment and structural ele-ments are required.
Project Breakdown
To be completed
7.6 Model File Structure
Type File Name
Base file
Grid/Levels
Linked drawings
127
Linked models
7.7 Model Authors
Model Author (role) Name Contacts
7.8 Modeling Guide
The main provisions and recommendations for the creation of a model that will meet the require-ments of the LOD matrix and selected BIM uses.
7.9 Maximum File Size
Maximum Revit® file size – 150M.
8 Collaboration Plan
8.1 Software Platform for Collaboration
Describe the software platform for collaboration.
8.2 Project Folder Structure
The company creates a hierarchical structure of shared folders. Every participant has to know where to save and where to get the information.
Describe the top level folder structure.
8.3 Folder structure for Work In Progress (WIP) zone
Describe the folder structure.
8.4 Folder structure for Shared zone
Describe the folder structure.
8.5 Folder structure for Published zone
Describe the folder structure.
8.6 Information Exchange Protocol
Project team members publish their models in Revit® format for coordination.
9 Model Creation Roadmap
Roadmap of model creation that matches the structure of the design models and files.
Number Disci- Central Start Finish Format Publish Project Com-
128
pline File Date Stage ment
10 Quality Assurance
Model quality assurance procedures.
10.1 Coordination Meetings
Date, format and agenda of meetings.Report templates.Team assignment templates.
11 Software & Hardware
11.1 Software
BIM Task Software Product Re-lease
Models Revit® 2015
Review Autodesk® Design Review, Navisworks® Man-age
2013,
2015
3D coordination Navisworks® Manage 2015
Drawings Revit® 2015
Schedules Revit® 2015
11.2 Hardware
According to software system requirements.
12 Templates
12.1 Revit® Templates
Template descriptions. Description of views & filters. Template naming conventions.
12.2 Navisworks® Templates
Description of templates. Templates of customized search sets according to the structure of the model.
13 Shared Parameters
Description of company parameters, names and uses. Recommendations.
129
14 LOD
Determine LOD with reference to the required criteria. Determine the subcategories for families. Determine the appearance of elements depending on the discipline, the view type and its scale.
15 Naming Conventions
15.1 Model Naming Conventions
Define the rules for model names.
15.2 View Naming Conventions
Define the rules for view names.
15.3 Workset Naming Conventions
Define the rules for workset names.
15.4 Family Naming Conventions
Define the rules for family names.
15.5 Sheet Naming & Numbering Conventions
Define the rules for sheet names & numbers.
15.6 Filter Naming Conventions
Define the rules for filter names.
130
APPENDIX C
Clash and Design Error Report TemplatesTable C.1. Automated clash check report template
Table C.2. Automated clash check summary report template
Table C.3. Visual design error check report template
131
APPENDIX D
Autodesk Revit® Model Validation ChecklistProject code
Central file name
Date
Prepared By
Approved By
Standard
Positive results of 38
Negative results of 38
No. Description Criterion
(reference)
Result Comment
Yes No
Location and parameters
1 The coordinates of the survey point correspond to the base file
2 The coordinates of the base point of the project correspond to the base file
3 The grid axis and levels corre-spond to the architectural model file
4 Model elements comply with LOD
5 No duplicated and superimposed elements (no messages in the Re-vit® Warnings dialog)
Data
132
6 The folder structure of the project complies with the standard
7 Shared parameters comply with the standard
8 A standard project template is used
9 Model elements comply with LOD
10 The elements are placed correctly on the worksets
Names comply with the standard:
11 - Model file
12 - Families
13 - Types
14 - Worksets
15 - Parameters
16 - Views
17 - View templates
18 - Filters
19 - Levels
20 - Fill Patterns
21 - Fills
22 - Sheets
23 - Line types
24 - Line styles
25 - Materials
26 - Grid lines
27 - Text styles
28 - Dimension styles
133
29 - Stages
30 - Arrows
31 Sheet elements correspond to the standard template
32 Schedules correspond to the stan-dard template
33 Text styles correspond to the stan-dard template
34 Dimension styles correspond to the standard template
35 Line weights correspond to the standard template
36 Line types correspond to the stan-dard template
37 There are no unused families
3D coordination
38 There are no conflicts with models in other parts of the project
134
APPENDIX E
Example of collaborative BIM process.
135
136
APPENDIX F
Recommendations on Using Autodesk Navisworks® Manage for Clash Detection
1 Model Preparation by Discipline
Preparation of models for each discipline assumes their spatial coordination. See sections 5.8.6 and 5.8.7 of this Standard.
In addition to the spatial coordination, the following actions are recommended:
Setting options of the model export from Revit® to the NWC file format
Setting options of the RVT file import in Navisworks®
Optimization of the Navisworks® performance
Creating views to be exported
Creating and assigning the additional design parameters
1.1 Setting Options of the Model Export from Revit® to the NWC File Format
Export options are set up in Navisworks Options Editor – Revit dialog box (Fig.15)
137
Fig. 15. An example of the export module settings in Navisworks®
Convert Element Parameters – All: enables access to all Revit® model element properties in Navis-works®.
Export – Current view: allows to prepare several views in Revit® and generate the needed amount of compound NWC models.
1.2 Setting Options of the RVT File Import in Navisworks®
An example of settings is shown in Fig.16.
Fig.16. An example of the RVT import settings in Navisworks®
1.3 Optimization of the Navisworks® Performance
When the NWC is opened in Navisworks®, it becomes write-protected, so users cannot edit, re-place or delete it. In order to have the NWC file updated during the NWF loading into the opened federated model, you need to check the Close NWC/NWD files on Load option (see Fig.17).
138
Fig. 17. Optimization of the Navisworks® performance
1.4 Creating Views to be Exported
It is recommended to create separate views in Revit® for exporting the model to Navisworks®. Only those elements that are needed for clash checks shall be displayed in such views.
View templates shall be used in order to quickly apply the view settings.
1.5 Creating and assigning the additional design parameters
It is recommended to create the additional design parameters in Revit®. That shall enable quick selection of model elements in Navisworks®, when needed.
Parameter naming scheme shall ensure their quick and unambiguous identification in the Navis-works® environment (for instance, they all may have the “NW_” prefix) when using the model ele-ment search tool.
Using parameters speeds up the creation of search sets.
2 Model Export by Discipline – Transferring Data to Navisworks®
The following ways are recommended for transferring a BIM model from Revit®:
Direct export from Revit® into NWC format using the utility which is added to Revit® during the Navisworks® install
Import the Revit® design file (RVT) in Navisworks®
Batch creation of NWD files using the Batch Utility.
139
2.1 Exporting Models from Revit® into NWC Format
The recommended export settings are shown in Fig. 15.
Before the export operation, the view that has been set up for exporting to Navisworks® shall be opened.
The export module shall be called, as seen in Fig. 18.
Fig.18. The NWC Export command
When you execute the NWC export command once again, use the same target file name. If you do so, updating the federated model would be just enough to incorporate the latest modifications of the BIM model.
2.2 Import the Revit® Project File (RVT) in Navisworks®
Before importing the Revit® project file, make sure that there is a view with “Navisworks” substring in its name and that the view has been set up for export.
The RVT import settings in Navisworks® are shown in Fig. 16 of this Appendix.
2.3 Batch creation of NWD files
Batch creation of NWD files shall be performed using the Batch Utility (Fig.19).
140
Fig.19. The Batch Utility main window
NWD files can be used for creating the federated model in the same way, as the NWC files.
3 Creating the Federated Model
The federated model shall be created using the Append command (Fig. 20).
Fig.20. Calling the Append command
141
The federated model details are displayed in the selection tree.
3.1 Recommendations on working with the federated model
The Navisworks® federated model shall be saved in the NWF format, which is the main working format in the product. NWF file contain links to discipline models, saved viewpoints, selection sets and search sets, all comments and tags, animation etc., that is, the complete content that was gen-erated in Navisworks®.
3.1.1 Documenting Actions with the Federated Model
The main Navisworks® working format, NWF, contains the actual data only.
If you need to keep the history of the federated model, use the NWD format that holds all snap-shots of the BIM model inside.
NWD save interval shall be defined in BEP. In addition to the Navisworks®-originated content, ele-ments of all models are physically represented in this format.
3.1.2 Working with Large BIM Models
Large BIM models can be divided into portions that are smaller and better manageable. You may have, for instance, a separate model for each building within the project.
In order to better manage the federated model, creation of intermediate NWD files where elements are grouped by discipline is allowed. An example of such model structure is shown in Fig.21.
Fig.21. An example of the large federated model structure
4 Creating Selection Sets and Search Sets on the Basis of the Clash Matrix
4.1 Clash Matrix
The Clash matrix shall be created in accordance with the check priorities.
142
Priority 1: Critical clashes that shall be resolved as early as possible in the design process (clashes between air ducts and walls, etc.)
Priority 2: Major clashes that shall be resolved at the coordination meetings in the design process (clashes between structural elements and electric equipment, etc.)
Priority 3: Less severe clashes that shall be resolved on a regular basis in the design and construction process (clashes between water supply systems and mechanical equipment, etc.)
The priority of checks may vary, depending on the particular project and its tasks.
A template of the clash matrix is shown in Fig.22.
Fig.22. A sample template of the clash matrix
For each particular project, you shall mark the fields that define the groups of elements to check, keeping in mind the priority of checks. See Fig.10 in this Standard.
The completed matrix becomes an integral part of BEP.
143
4.2 Creating Selection Sets and Search Sets
Creation of selection sets and search sets for clash checking is supported in both Navisworks® Manage and Navisworks® Simulate. Search sets can be exported from Navisworks® Simulate to Navisworks® Manage using the XML format.
Creation of selection sets and search sets shall be based on the clash matrix that defines the groups of BIM model elements to check.
Model element properties shall be included in the search (see Fig.23).
Fig.23. Model elements search dialog box
Elements that were found shall be saved as a set. Saved sets reside in the Sets palette (Fig.24).
Fig.24. Sets palette
It’s recommended to use the intelligent search sets for selecting elements during the checks. These sets, when turned to, perform the search of elements that satisfy the specified conditions.
144
Navisworks® supports complex search criteria based on more than one property (OR operation, see Fig.25). As a result, all model elements that satisfy either specified condition are being se-lected.
Fig.25. Creating a complex search criteria
WARNING! Search sets are sensitive to the property names. That’s especially important in setups where Russian and English software versions are used concurrently. Sets that were created in a Russian version will not work in an English one, and vice versa.
The following recommendations shall be observed for the efficient work with the federated model in Navisworks®:
4.2.1 Setting the Selection Resolution
Model element search is based on the properties of elements. In order to speed up the search and selection of elements, it’s recommended to activate Set Selection Resolution To First Object right-click menu option (Fig.26).
145
Fig.26. The right-click element selection menu
Such a setting ensures display of the maximum number of properties in the Properties window af-ter selecting an element (Fig.27).
Fig.27. The selected element properties window
5 Visual Check for Design Errors
5.1 Searching for design errors146
The visual check shall be carried out by means of the federated model walk-through and fly-by us-ing the navigation, section and measurement tools. Clashes that have been found shall be docu-mented using the review tools.
It is recommended to use the Lock option for better measurement accuracy (Fig.28).
Fig.28 Locking during the measurements
Using the Appearance Profiler tool is recommended for enhanced visual check.
5.1.1 Appearance Profiler
The Appearance Profiler tool enables the visual separation of various model systems (Fig.29).
Fig.29 Color separation of building systems
The tool settings shall be saved in a separate DAT file, for easy Appearance Profiler application in other designs. That allows to standardize building systems visualization within the BIM model in a corporate level (Fig.30).
147
Fig.30 The Appearance Profiler dialog box
WARNING! All Appearance Profiler settings shall be saved before the Navisworks® session is closed. Otherwise, the settings will be lost.
5.2 Documenting the Detected Clashes
The following recommendation shall be observed:
Notes in the model shall be created using tags that are very convenient for documenting purposes. Each tag contains the view point and a comment identifying the time/date and author.
Saved Viewpoints window collects the views from all tags and allows to quickly change the view.
Use the Find Comments tool (Fig.31) to search for a comment.
148
Fig.31. The Find Comments window
Group the viewpoints into folders (Fig.32) for more efficient handling them.
Fig.32. Grouping the saved viewpoints
5.3 Creating the Visual Design Error Check Report
Each record in the visual check report (see Appendix C, Table C.3) shall contain the viewpoint, comment, clashing element IDs and the name of a person responsible for the clash resolving.
6 Automated Check for Clashes
BIM Manager/Coordinator takes the responsibility for carrying out automated checks, notifying all stakeholders and supervising the resolution activities.
Automated clash checks are carried out in the Clash Detective module.
The automated check process is composed of:
Creating a clash test149
Selecting elements for checking Setting test criteria and options Running the test Creating clash check reports
6.1 Creating a clash test
The test shall be created during the first launch of the Clash Detective. After the test is created, model element selection options become active.
6.2 Selecting elements for checking
Using the search sets is recommended for element selection. The search sets have to be created beforehand (see Fig.24) or loaded from an XML file.
An example of search sets for a clash check is shown in Fig.33.
Fig.33. Model element selection for checking
6.3 Setting test criteria and options
Test criteria are set in the lower left-hand part of the Clash Detective window (Fig.34).
150
Fig.34. Setting the test criteria
In the figure, (1) defines the scope of check; (2) describes the method of check.
The minimum required parameter set for checking includes:
– Selection of surfaces as part of the geometry to be checked.
Type:
• Hard: two objects spatially intersect.Tolerance represents the depth of intersection. If the depth lies within the toler-ance value, then it is assumed that the clash can be resolved on-site, and there is no impact on schedule and budget.
• Clearance: while the two objects do not physically intersect, the clearance zones around them overlap. Detection of such kind of clashes is especially im-portant when, for instance, insulation around pipes and ducts has to be taken into account.Tolerance represents the thickness of the insulation layer.
• Duplicates: two objects are identical both in type and position.
Tolerance: depth of intersection or thickness of the clearance zone around an element (see above). Depends on the type of check.
6.4 Running the test
After the elements to be checked are selected and criteria are set, the test shall be run by clicking the Run Test.
Subsequent tests can be initiated from the Results tab by clicking the Re-run Test (Fig.35).
151
Fig.35. Clash Detective window, Results tab
6.5 Creating the Automated Clash Check Report
6.5.1 Check Results
The list of detected clashes and their statuses is displayed in the Results tab (Fig.36).
Fig.36. List of clashes found during the clash check
Each clash may have one of the following status values:
New: clash gets this status during the very first check.
Active: clash has not been resolved by the moment of test re-run.
Resolved: clash has been resolved by the moment of test re-run. The Compact command removes the resolved clashes from list.
Reviewed: relates to assignment of a responsible for resolution.
Approved: actually this is not a clash. Name of approver, date and time of approval are displayed.
152
Reviewed and approved clashes are automatically moved to the end of list (Fig.37).
Fig.37. Clash statuses
6.5.2 Creating the Report
The report is generated on the Report tab in Clash Detective (Fig.38).
Fig.38. Clash Detective window, the Report tab
A sample automated clash check report form is shown in Appendix C, Table C.1.
153
The clash resolving progress may be traced in the summary report (see Appendix C, Table C.2).
7 Clash Analysis
The following recommendations shall be observed during the clash analysis:
Grouping clashes (Fig.39) makes the clash management more efficient.
Fig.39. Grouping clashes
Using the Inclusive option of the Filter by Selection tool (Fig.40) speeds up the clash analy-sis and their grouping.
Fig.40 Filtering with the Inclusive option
The Inclusive option limits the displayed list: only clashes that involve the selected element are shown. You may include such clashes into groups and handle them (e.g. change status and re-sponsible person) collectively (Fig.41).
154
Fig.41. Selecting a group of clashes
The clash analysis process results in the assignment of people responsible for their resolution. See Appendix C, Table C.1.
8 Resolution of Detected Clashes
After the list of clashes has been reviewed and analyzed, the check results shall be handed over to the assigned responsible persons.
There are two ways of handing over the results:
The SwitchBack tool
Using the Item ID
8.1 The SwitchBack Tool
It’s recommended to use the SwitchBack tool for handing over the check results. It allows to select a model element in Navisworks® and switch to the same element (setting the appropriate view) in Revit®.
Navisworks® Manage and Revit® shall be launched on the same PC. The SwitchBack shall be ac-tive in Revit® (Fig.42).
155
Fig.42. Activation of SwitchBack in Revit®
Don’t forget that the perspective view is the basic one in Navisworks®. After switching to Revit®, the perspective view is created/set, however such a view is not a working one in Revit®.
That’s why you need to set an orthographic view in Navisworks® before using SwitchBack.
8.2 Using the Item ID
The element’s Item ID is unique in the design, and it is often used for the quick search purposes.
Navisworks® displays Item IDs in the clash check report(Fig.43).
Fig.43. Item ID in the clash check report
The element can be found in Revit® by its Item ID.
156
DISCUSSION FORUM
If you have any questions or comments on this standard, please visit: forum.autodesk.ru
BIM GUIDE FOR INFRASTRUCTURE
We have also developed the BIM Guide for infrastructure.
Download BIM Guide for Infrastructure
AUTOCAD® CIVIL 3D® AND REVIT® TEMPLATES
Design template (architectural) V.2017: http://autode.sk/2docmq7 Design template (structural) 2017: http://autode.sk/2d5v2Wx Design template (HVAC/plumbing) 2017: http://autode.sk/2e75jdS Shared parameter file: http://bit.ly/2ep3sE0Design templates for AutoCAD® Civil 3D® were included into the product.
TERMS OF USE
This standard may be freely distributed and used in any format necessary, for the purpose of development corporate BIM Guides. Reference to this standard is required in all derived documents.
Autodesk, inc. © 2017. All rights reserved.
Москва 2015
![[1974] 1 W.L.R. 1192](https://img.pdfslide.us/doc/110x75/577cdb071a28ab9e78a72fb6/1974-1-wlr-1192.jpg)
