8 4.11.7 Parameter naming rules Spaces are now allowed in names. The naming scheme 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 (instead 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 regions. 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 naming 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 naming rules NEW! The naming scheme contains 4 fields.
Data transfer to Navisworks® DWG Export of views and sheets to AutoCAD® and other CAD software Import of DWG layout from AutoCAD® and other CAD software Import of contours, surfaces (3D faces), corridors and pipes from AutoCAD® Civil 3D® ADSK Export of data (model objects) to AutoCAD® Civil 3D® Import of objects (for family creation) from Inventor® IFC Export of data to third-party software that supports model import in IFC format Import of data from third-party software that supports model export to IFC format DWF/3D DWF Export of data for review and publishing Import of annotations and markups from Autodesk® Design Review to Revit® and AutoCAD® PDF/3D PDF Export of data for review and publishing – 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.
Field1 – view code (P, EX, IA, OA etc., see Table 2) Table 2. View codes Field1 value View code 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:
Naming of line patterns and line styles shall be based on the following format: <Field1>_<Field2>_<Field3>_<Field4>_<Field5> where: 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 ADSK_Schedules_Arial_3 ABC_ISOCPEUR_5_B ABC_ISOCPEUR_2.5_Red 4.11.18 Dimension Type Naming Rules Dimension 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:
Parameter name Data type Group Descriptions ADSK_Name TEXT Required COMMON Parameter for schedules, representing the element name and its main specifications ADSK_Tag TEXT Required COMMON Type, tag, index of a document/form ADSK_Weight Required COMMON Product weight per unit or linear density (for rebars, beams etc.) ADSK_Floor type TEXT Required ARCHITECTURE Floor type. Sent to the floor tag and floor schedule ADSK_Room type TEXT Required ARCHITECTURE Room type (residential, etc.). Used in apartment layouts ADSK_Floor makeup IMAGE Required ARCHITECTURE Graphical structure of the floor make-up ADSK_Bent reinforcement YESNO Required STRUCTURE Parameter is on for bent reinforcement, 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 Required STRUCTURE Needed for representation of compound products (reinforcement cages, embedded items, their compound elements etc.) ADSK_Equipment code TEXT Required MEP Equipment code according to the manufacturer’s catalog ADSK_Partition code TEXT Required MEP Conduits ADSK_Standpipe number TEXT Required MEP Standpipe designator in layouts and plans
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 minimizes 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 Links Using 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 Navisworks®, 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 between files. When using links, model should lie in the correct location respective to the pre-agreed system coordinates in the base file. Links between design disciplines Each individual discipline involved into the project should have its own model and carry responsibility for it. Model developed by a discipline can refer to the model of other disciplines in coordination purposes.
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 Analysis The clash analysis process is aimed at preparing to assignment of people responsible for their resolution. Normally, clash resolution is put in charge of the BIM authors who developed the respective parts of design. 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 coordination meetings. See section “BIM Coordination Meetings” of this Guide. 6.3.9 Resolving Clashes The 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 described 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 Meetings Coordination meetings shall be held in order to analyze found clash, look for the ways of their resolutions and assignment of responsible persons. Leaders of all relevant groups/departments/disciplines, 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 participants and their tasks, backlogged tasks identified at the previous meeting, matters of collective interaction, unresolved technical problems, amount of work on the contract and
dimensions, shape, spatial position, orientation, connections and all required attributes LOD 400 A model element is represented as a specific assembly with exact dimensions (including those of detail elements), shape, spatial position, orientation, detail connectors (bolts, rivets, welds, shaped elements, dowels, embedded items etc.), fabrication data and all required attributes Design stage creation of the design documentation Construction stage creation of the project execution plan LOD 500 A model element is represented as a specific assembly with actual dimensions, shape, spatial position, orientation and attributes required to pass the model to operation 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 phase for
Handrails Approximate geometry Same as LOD 100 Type, precise dimensions, exact visual representation, structure, location, material, tag Section/profile, fittings/accessories, manufacturer, part name, part number Heavy façade Approximate geometry Same as LOD 100 Type, precise dimensions, exact visual representation, structure, location, material, tag Section/profile, fittings/accessories, manufacturer Impost Approximate geometry Same as LOD 100 Type, precise dimensions, exact visual representation, structure, location, material, tag Section/profile, manufacturer Roof Approximate geometry Type, location, room boundary Precise dimensions, structure, material, slope, tag, fire rating Same as LOD 300 Plumbing fixtures Approximate geometry Location Type, precise dimensions, exact visual representation, tag Fittings/accessories, part name, part number Light façade Approximate geometry Same as LOD 100 Type, precise dimensions, exact visual representation, structure, location, material, slope, tag Section/profile, fittings/accessories, manufacturer, part name, part number Entrance ramp No specific requirements No specific requirements Type, precise dimensions, structure, location, material, slope, tag Section/profile
Table A.6. Example of LOD matrix for Structural Design Components Preliminary design Design / Detailed Design stage LOD 100 LOD 200 LOD 300 LOD 400 Wall No specific requirements Type, approximate geometry Precise dimensions, section/profile, location, material, tag, weight Fire rating Deck/ Roof No specific requirements Type, approximate geometry Precise dimensions, section/profile, structure, location, material, slope, tag, weight Exact visual representation, fittings/accessories, manufacturer, part name, part number, fire rating Column No specific requirements Approximate geometry Type, precise dimensions, section/profile, structure, location, material, tag, weight Exact visual representation, manufacturer, part name, part number Opening No specific requirements Approximate geometry Type, precise dimensions, location, tag Structure, fittings/accessories Truss No specific requirements Type, approximate geometry Precise dimensions, exact visual representation, location, material, tag, weight Section/profile, structure, fittings/accessories, manufacturer, part name, part number, fire rating Embedded details No specific requirements No specific requirements Type, approximate geometry, location, material, tag Precise dimensions, exact visual representation, section/profile, structure, manufacturer, part name, part number, weight Staircase No specific requirements Type, approximate geometry Precise dimensions, section/profile, structure, location, material, slope, tag, weight Manufacturer, part name, part number
Landing No specific requirements Type, approximate geometry Precise dimensions, section/profile, structure, location, material, slope, tag, weight Manufacturer, part name, part number Reinforcement No specific requirements No specific requirements Type, approximate geometry, section/profile, material Precise dimensions, location, tag, manufacturer, part name, part number, weight Foundation No specific requirements Type, approximate geometry Precise dimensions, section/profile, structure, location, material, slope, tag, weight Manufacturer, part name, part number Piles No specific requirements Type, approximate geometry Precise dimensions, section/profile, structure, location, material, tag, weight Manufacturer, part name, part number Braces No specific requirements Approximate geometry Type, precise dimensions, section/profile, location, material, tag, weight Exact visual representation, structure, manufacturer, part name, part number, fire rating Node points No specific requirements No specific requirements Approximate geometry, section/profile, location, material, weight Type, Precise dimensions, Exact visual representation, Structure, Tag Table A.7. Example of LOD matrix for Ventilation Systems Components Preliminary Design stage Design / Detailed Design stage
LOD 100 LOD 200 LOD 300 LOD 400 Air outlets No specific requirements No specific requirements Type, precise dimensions, location, tag, flow, velocity Manufacturer, part name, exact visual representation, fittings/accessories Ductwork No specific requirements No specific requirements Type, precise dimensions, section/profile, location, material, tag, flow, velocity, pressure Manufacturer, part name Air tubes No specific requirements No specific requirements Type, precise dimensions, section/profile, location, material, tag, flow, velocity, pressure Manufacturer, part name Connections No specific requirements No specific requirements Type, precise dimensions, section/profile, location, material Manufacturer, part name, exact visual representation Fittings No specific requirements No specific requirements Type, precise dimensions, location Manufacturer, part name, part number, exact visual representation, fittings/accessories, tag Equipment No specific requirements Type, approximate geometry Precise dimensions, location, tag, weight, flow, power Manufacturer, part name, exact visual representation, fittings/accessories Insulation No specific requirements No specific requirements Precise dimensions, location, material Manufacturer, part name Table A.8. Example of LOD matrix for Heating Systems Components Preliminary Design stage Design / Detailed Design stage LOD 100 LOD 200 LOD 300 LOD 400
Equipment Type, approximate geometry Precise dimensions, location Tag, weight, power Exact visual representation, manufacturer, part name, part number Cable trays No specific requirements No specific requirements Type, precise dimensions, section/profile, location Exact visual representation, tag, manufacturer, part name, part number Cable tray fittings No specific requirements No specific requirements Type, precise dimensions, location, material Manufacturer