S02 - Handout - Autodesk Revit Structure - Management Templates Standards

Session 2
Autodesk® Revit® Structure -

Management, Templates, & Standards
Graham H Stewart, Ramboll UK
Class Description
This class is designed for structural engineering professionals with
beginning or intermediate experience in Revit Structure. This class will
cover a combination of best practices on how to manage
multidiscipline collaboration, setting up templates and general model
management principles including using scope boxes, filters, various
types of schedules and managing CAD files for large multiuser projects.
Attendees should have a general knowledge of Revit Structure.
Learning Objectives
At the end of this class, you will be able to:
• Learning objective 1 - Define standards and protocols for
multidiscipline collaboration
• Learning objective 2 - Create templates that address browser
organization, shared parameters, schedules, and title sheets
• Learning objective 3 - Apply general model management
principles
• Learning objective 4 - Manage CAD files for large multiuser
projects
About the Speaker:

Graham – Is UK Head of BIM at Ramboll with over 25 year’s experience
in the AEC industry (covering 15+ years using various 3D software
packages including 10+ years using Revit) specialising in BIM
Implementation. Responsible for managing group development of
Revit and UK BIM Implementation.
One of the original members of the #ukBIMcrew twitter hashtag you
can catch him at various UK and international events speaking and
promoting UK Best Practice.
Autodesk® Revit® Structure - Management,
Templates, & Standards
In 2009 Graham co-founded GRUG - The Glasgow Revit User Group

which holds meetings with like-minded professionals within the industry
covering Architecture, Structures, Building Services, Contractors &
Education.
Graham is also a Certified Autodesk Revit Architecture 2014, has
presented at AU2011/2012 and currently studying an MSc in BIM
Management at Middlesex University.
Email: graham.stewart@ramboll.co.uk
Twitter: StewartGH1970
Linkedin: http://uk.linkedin.com/in/grahamhstewart/
Blog: Revit5 (sorry it’s a bit out of date!)
Page 2 of 106
Table of Contents
Session 2 ........................................................................................................................ 1
Autodesk® Revit® Structure - Management, Templates, & Standards ............... 1
Graham H Stewart, Ramboll UK ................................................................................ 1
Class Description .................................................................................................. 1
About the Speaker: .............................................................................................. 1
Table of Contents .................................................................................................... 3
Forward ..................................................................................................................... 6
Define standards and protocols for multidiscipline collaboration ....................... 7
Project Kick Off Meeting ......................................................................................... 8
Model Exchange for Project Collaboration (Design data Exchange) ....... 12
Clash Avoidance Process ................................................................................. 13
Audit Process ...................................................................................................... 14
Model Exchange Matrix .................................................................................... 15
Navisworks Exchange Matrix ............................................................................ 16
What should you tell your collaborators? ........................................................... 17
Model Specific Information .................................................................................. 18
Project Specific Information ............................................................................. 19
Reference Information ...................................................................................... 20
Project Levels ...................................................................................................... 20
Linked Views........................................................................................................ 21
Project Phasing ................................................................................................... 21
Scope Boxes........................................................................................................ 22
Project Shared Coordinates ............................................................................. 22
Design Options ................................................................................................... 23
Model Information.............................................................................................. 24
Collaboration – General Points to Note: ............................................................ 25
Create templates that address browser organization, shared parameters,
schedules, and title sheets ....................................................................................... 26
Project Browser (Views) ......................................................................................... 27
Page 3 of 106
Browser Organisation Explained .......................................................................... 29

Section / Elevation / Callout / Plan Types .......................................................... 37
Plan Types For 2015 ................................................................................................ 38
View Templates ...................................................................................................... 39
View Template Filters ............................................................................................. 40
Materials .................................................................................................................. 41
Assigning Material by Object Styles: ................................................................... 42
Element Parameters .............................................................................................. 45
Filter Groups ........................................................................................................ 45
View Shading ...................................................................................................... 45
Analytical ............................................................................................................ 45
Design Confirmation .......................................................................................... 46
Contraints ............................................................................................................ 47
Level Filters .............................................................................................................. 48
Schedules ................................................................................................................ 49
Titleblocks ................................................................................................................ 56
Title Sheet Parameters ........................................................................................... 57
Formulas to Drive Graphics .................................................................................. 59
Main Title ................................................................................................................. 61
General Notes ........................................................................................................ 62
SHE Box .................................................................................................................... 63
Apply general model management principles .................................................... 64
Map Out Your Process........................................................................................... 65
File Maintenance on you Project ........................................................................ 66
Revit Origin .............................................................................................................. 67
Creating Selection Sets ......................................................................................... 68
Scope Boxes ........................................................................................................... 73
Issuing Model Data ................................................................................................ 76
Worksets................................................................................................................... 80
Transferring Project Standards To Old Projects .................................................. 81
Manage CAD files for large multiuser projects...................................................... 84
Page 4 of 106
AutoCAD Data Preparation ............................................................................. 84

CAD Data Revit Model Procedure: ................................................................. 85
Main Revit Model Process: ................................................................................ 86
Creating a New Revit Template from Scratch .................................................. 87
Page 5 of 106
Forward
Just a quick message to personally thank you for taking the time to
download these handouts, and hopefully, if you are at RTC Europe
2014 you can spare the time to attend my class.
The following handout is a combination of nearly 3 year’s work during

my time at Ramboll UK developing various standards, protocols and
their new Revit Structure 2012 -2015 templates.
Hopefully you will find the information contained within these handouts
useful and help give you some ideas to new workflows and standards
to adopt in your own company.
I hope I have explained enough for you to understand my thoughts,

but please feel free to contact me to discuss anything in this handout
or anything Revit or BIM related.
Kind Regards
Graham
Page 6 of 106
Define standards and protocols for

multidiscipline collaboration
The following section highlights various elements of collaboration that I

have come across that pop up time and time again.
 The Project Kick Off Meeting

A series of points to raise at the initial meeting to gather information
to pull together the Project Execution and Strategy Plans.
 Pictures speak a 000’s words – using process diagrams
Sometime a diagram is much better at conveying what you are
trying to say in the Project Execution and Strategy Plans, enclosed
are a few I have used.
 What do you tell/share with your collaborators
Don’t leave anyone in the dark! Tell everyone how to use your
model as much as possible so they understand your modelling
strategy.
 Model & Project Information
Using views to keep everyone up to date with revisions you have
made to the model and the template as well as other important
information.
 General points to note
Some top items for discussion
Page 7 of 106
Project Kick Off Meeting
In order to prepare the Project Execution Plan there needs to be an

initial Project Kick Off meeting with all the relevant parties (ie BIM
Managers, BIM Coordination ie people that understand BIM but also
Project Managers that understand the design & the procurement
process) to gather information and share knowledge and experiences
and to fully understand the client’s present and future requirements.
Below is an initial list of points to raise with possible outcomes.
1. Project overview
 What are we trying to achieve – in the UK this is
assessed from the Employers Information Requirements
(EIR)
2. Project Team Capability
 Brief summary from each stakeholder with regards their
current capability with BIM (software, technology,
process) which in the UK can be assessed from the CPIx
BIM, IT & Resource Assessment forms
3. Project Goals
 To create a federated collaborated 3D model
 Embed an element of information into the models for
use with the asset/facilities management team, COBie
etc
 To replicate the planned construction programme into
the 3D environment (4D)
 To validate the model.
 To bring in any supply chain members models
 To hand over upon project completion a final digital
asset (AIM) for the clients use going forward.
4. Project team contacts.
 Names, Roles, Contact Details, Experience – In the UK
this information should match the CPIx Resource
Assessment Form
Page 8 of 106
5. Project Challenges
 Project timetable especially design vs procurement
 Teams experience
 Disparate software
6. KEY project delivery dates
7. Project protocols/modelling standards
 To assist in the production of the Project protocols, a
copy of each project stakeholders company modelling
standards? Is required
 Is there any agreed file naming or drawing naming
conventions in place? In the UK we should be following
BS1192:2007 / PAS1192-2:2013
 2d output? Non-graphical information should be
documented
8. Authoring Software and Compatibility
 Discipline, software, build version
9. Other proposed software
 Navisworks, Solibri etc
10. Technology
 Is there any special requirements for the project ie
minimum computer spec, WAN
accelerators/Riverbed/Revit Server etc
11. Model Spatial Organisation
 Has this been set? Do all models come together with
regards origin, level, rotation?
12. Proposed model structuring (Volume)
 One model or split by floor / zone or movement joints?
13. Informal issuing of models for co-ordination
 In the UK we would need to follow BS1192:2007 for the
process of the Common Data Environment (CDE)
 Timing?
 File formats?
 Extranet?
 Feedback process from co-ordination check – define.
Page 9 of 106
14. Project Deliverables.

 As built 2D drawings for architecture, Structure and all
trade contractors
 As built 3D (PIM) models for architecture, Structure and
all trades contractors
 7D (AIM) model with agreed level of embedded data.
15. Training and support
 Collaboration viewing software
 Authoring software
 Project specific modelling concerns
16. Future project meeting schedule
 Something that needs careful consideration at bid
stage!
In the UK the above agenda is mostly drive by the following documents

which cover all the requirements of UK BIM Level 2.
Page 10 of 106
After all this information is collected we can now begin to pull together
the Project Execution Plan which should have been in development
from bid stage! To ensure you have had initial thoughts prior on how
the project would be set up so there are no surprises.
To ensure key elements of the coordination process is understood we

should also prepare process maps as a high level overview of the
information.
Example of Ramboll’s Project Management Processes
Page 11 of 106
Model Exchange for Project Collaboration (Design data

Exchange)
The example below highlights the model exchange workflows between

consultants using a combination of various software platforms to assist
in OpenBIM.
RHINO
2D DWG
2D DWG
3D DWG
3D DWG
IFC
OTHERS
3D DWF
GC
REVIT NWD
Bentley
MICROSTATION
DWG NAVISWORKS
CAD
Bentley
Measure
MICROSTATION
Structural
NWD
2D DWG AutoCAD 2D DWG

EXCHANGE
3D DWG MEP 3D DWG
SOFTWARE
Page 12 of 106
Clash Avoidance Process
The example below highlights the exchange and clash rendition process and feedback at coordination meetings.
Clash Avoidance Process

(Wed – Fri + Mon – Tues) Week 1 (Wed – Fri + Mon – Tues) Week 2
Wednesday to Tuesday Tuesday Tuesday Wednesday Monday (AM)

Design Team
Download other Design Review clashes prior

Design Coordination/ Internal Review and Issue to ‘WIP’
disciplines latest coordination/ Clash to coordination
Clash resolution validation section of CDE
models for review review meeting
Monday
Coordination
Coordination Process meeting
Tuesday
Coordination
BIM
Meeting Report
Performed by Coordination Team issued
 Run through reported  Issue minutes of coordination meeting,

clashes. including actions per clash and any
Terminology:  Record actions. comments as part of The Contractors
CDE = Common Data Environment report.
 Include trending information such as
amount of entities and number of
Clash Renditions are thought to be most effective when undertaken on a two week cycle, this clashes per test.
gives the design team time to resolve the clashes before the next rendition workshop.  Save meeting report in the ARCHIVE
section of the CDE.
Audit Process
The example below highlights the audit process to ensure all steps are
followed.
Audit
Information
Manager
No No
Client Issue
QA/QC Audit
Data Audit Task Data QA/QC Audit Yes Document
Complies Information Complies End Process
Start Author Author Control
Manager
Yes
Audit
Information
Manager
Each gateway is fully defined.

Model Exchange Matrix
The following highlights the various file formats which each consultant
will need as part of the BIM interoperability process. This matrix
indicates the files which each consultant will issue as well as the file
formats they will need to receive.
Page 15 of 106
Navisworks Exchange Matrix
Autodesk NavisWorks is a BIM collaboration tool which is able to read a

multitude of different 3D file formats. Navisworks is used for BIM
collaboration and 3D review of published models by the design team.
Each consultant issues their files to the Shared Project Server, these files
are combined by the BIM team and are made available for viewing by
the design team and others.
Page 16 of 106
What should you tell your collaborators?
When working with other partners in Revit for collaboration it is

important to tell them everything you are doing to their model in order
for you to work efficiently.
By keeping them informed they can then adjust the way they set up
their models to suit how others are using their model.
Examples are:
 By Linked Views:
Why reinvent the wheel if other design team members have views set
up that you can use – This is important if we want to use architects
drawings as backgrounds for either structural or MEP drawings.
 Copied Scope Boxes
To ensure all views match the architect should set up layouts that the
rest of the design team should follow where appropriate – views are
best governed by assigning scope boxes to control boundary (at
present time this is a manual process of copying scope boxes from the
linked architects revit model – user wishlist item for the future, the ability
to copy/monitor scope boxes)
 Phases
List all phasing into project with clear descriptions
 Linked RVT:
List all models you have referenced into your model for coordination
including: name, revision & date
 Linked CAD:
List all CAD files you have referenced into your model either as
backgrounds or details.
Page 17 of 106
Model Specific Information
The following view has been set up as a one stop shop for everyone
using the model to get information you think others will need to
understand the modelling process.
RED Box
This sheet uses the standard Revit revision system.
GREEN Box
Template Revisions - This lists all amendments you have made to the
current model settings.
Page 18 of 106
Project Specific Information
Any information you feel the design team or fellow staff members need
to know how the model has been created should be added here.
From 2014 the View Template Schedule has been added.
Page 19 of 106
Reference Information
All linked RVT/CAD files used to form part of the model should be stated
here along with description, revision & dates.
Project Levels
List all main structural levels being used in the project.
From 2014 the Project Levels Schedule has been added.
Page 20 of 106
Linked Views
Any linked views that you are using as backgrounds for any drawings
should be noted.
Project Phasing
This should match the architects model phasing but should also contain
any specific structural phasing.
Page 21 of 106
Scope Boxes
List any copied scope boxes from other linked models.
Project Shared Coordinates
List the Project Shared Coordinates – Note: This should also be stated in
the Project Execution Plan.
Page 22 of 106
Design Options
List any Design Options being used are to be named.
Page 23 of 106
Model Information
Use this as a one stop shop to specific all project information that will
apply to all Title Sheets.
Note: All this information can also be added via Manager > Project
Information
Note 1: BLUE Box - To get your Revit Version Build please go Help >
About
Page 24 of 106
Collaboration – General Points to Note:
Note the following points that should be noted and discussed with the
design team.
 Always modify host elements rather than delete them and replace
with new elements.
 All rooms must be defined correctly and properly enclosed with
bounding elements
 All models must be phased mapped to ensure correct results when
linking models
 Any copy/monitored elements must be placed on the same
workset as the linked model
 All linked models from other design team members must also come
with any supplementary linked CAD, RVT files UNLOADED for
information
 Ensure that the Room Bounding parameter of all floors and walls IS
selected by default
 Ensure Room Bounding parameter of all Architectural columns IS
NOT selected
 Care should be taken with certain structural elements such as
Structural Beams, Structural framing, Slab Edges etc. cannot be
Room Bounding. Where these elements specifically interact with the
Architectural walls they can leave gaps between the Architectural
walls and the slabs, etc.
Page 25 of 106
Create templates that address browser

organization, shared parameters,
schedules, and title sheets
The following example shows how I current have set up our company
standard browser which breaks it down to 9 unique groups with a
further 6 sub-groups.
By doing this we are able to split the browser up so that we work in

specific environments each of which have defined view types ie
sections, elevations, call-outs etc to avoid these being seen in other
groups.
Using these Views we can assign:
Technician – User, Documentation, Coordination
Engineer – User, Coordination, Analytical
The above can be refined to suit the experience & collaboration levels
of each party.
This also helps separate key views ie documents clear and clean for
issue.
Page 26 of 106
Project Browser (Views) Browser Organisation

& Filtering Properties
Page 27 of 106
Project Browser (cont. – Legends, Schedules & Sheets)
Page 28 of 106
Browser Organisation Explained

01. User Review For all users to create their own respective ‘working’ views.
These views should be duplicated from the existing
documentation views where appropriate.
Note 1: 3D View: UR-Constraints - User Review highlights
ALL elements Constrained (GREEN), Constrained in 2
directions (BLUE)
Note 2: 3D View: UR-Designed - User Review highlights ALL

elements Not Designed (RED)
Note 3: The following constraints apply to ALL Views:

Levels NOT defined as Structural are highlighted
Note 4: ALL views to have UR- suffix
02. Documentation Views that are generated from the model, and placed on
sheets for printing, complete with annotation.

Views as assigned to RUK_Scope Box
Scope Boxes as turned OFF
Levels not defined as Structural are turned OFF (2013
onwards)
Note 2: ALL Loading Plans to have LO- suffix
03. 2D Views that are drawn in 2D and placed on sheets for
Documentation printing (material specific); complete with annotation. N.B:
this includes any views referenced from AutoCAD.
04. Reinforcement Reinforcement specific views (including 2D Reinforcement
Documentation details), to be placed on sheets for printing.
Note 1: ALL views to have RF- suffix
Page 29 of 106
05. Note & General Notes and Abbreviations, to be placed on sheets

Abbreviations for printing
06. Coordination Views in which other discipline drawings can be linked-in
and left visible for anyone to refer to, at any time,
regardless of how many people are working in the project
(eliminates reference ownership problems on multi-user
projects).
Note 1: Location of ALL constrained dimensions (Pre-2015).
Levels not defined as Structural are highlighted RED (2013
onwards)
Note 2: ALL views to have CO- suffix
Page 30 of 106
07. Analytical Views in which only the analytical model should be shown.
Note 1: 3D View: AN-3D View highlights ALL adjusted
elements as RED Dashed
Note 2: 3D View: AN-Fastrak Integration Status highlights ALL

any changes from round tripping with CSC Fastrak Software
Note 3: ALL views to have AN- suffix

Note 4: 3D View: AN-Fastrak Object Styles highlights the
various element types
Note 5: 3D View: AN-Node Connection Status (2014

onwards) highlights all unconnected nodes
08. Navisworks 3D views for exporting to Navisworks, for clash detection

Export Views (.nwc).
Note 1: ALL views to have NW- suffix
Note: Making any geometry changes in any of the above views will
affect other drawings.
Page 31 of 106
This highlights all the various view types that can be set up in the
template. The purpose in setting up so many views is to avoid further
users wasting time doing the same task over and over e.g you will
notice that we have 10 floor levels above ground and 3 basement
levels complete with 3D views all pre-defined for the user to amend to
suit.
For users to create their own respective ‘working’ views. These views
should be duplicated from the existing Documentation views where
appropriate.
Page 32 of 106
Views that are generated from the model, and placed onto sheets for
printing, complete with annotation.
Views set up to structure the browser for 2D drafting views
Page 33 of 106
Views set up to structure the browser for Reinforcement views
Views for general notes, abbreviations etc – any legends that you wish
to share with other projects should be placed here which will be
facilitated by using “Insert Views From File”.
Page 34 of 106
Views in which other discipline drawings/models can be linked-in and

left visible for anyone to refer to, at any time, regardless of how many
people are working in the project (eliminates reference ownership
problems on multi-user projects).
Views in which only the analytical model should be shown.
Page 35 of 106
3D views for exporting to Navisworks for clash avoidance (.nwc).
Views with reference information and guidance for the user ie key
information from you companies QA/QC, modelling procedures etc.
Page 36 of 106
Section / Elevation / Callout / Plan Types
The following section, elevation and callout view types have been set
up to suit the browser view groups. As these view types have
associated pre-defined filters, this enables them to be view specific i.e.
a user-review section will only be seen in user-review views, and not in
any other views so wouldn’t appear in any documentation etc.
Section Types Available: Detail View/Callout Types Available:

(Full Building Section) (Local Section)
RUK-AnalyticalSection RUK-AnalyticalSection
RUK-CoordinationSection RUK-CoordinationSection
RUK-DocumentationBuildingElevation RUK-DocumentationBuildingSection
RUK-DocumentationBuildingSection RUK-DocumentationRebarSection
RUK-DocumentationRebarSection RUK-DocumentationCoreSection
RUK-DocumentationCoreSection RUK-UserReviewSection
RUK-UserReviewSection
Building Elevation Types Available:
RUK-UserReviewElevation
RUK-CoordinationElevation
RUK-AnalyticalElevation
Note 1: For Sections there are 2 types from the drop-down : Detail View
(local floor sections) & Section (full building sections)
Note 2: Instead of elevations we have set up a section type called
RUK-DocumentationBuildingElevation to use as sections allow for
greater flexibility.
Page 37 of 106
Plan Types For 2015
With the release of 2013 we can now link View Templates to Plan Types
which means when you are creating a level you now have the option
to create multiple copies for different types.
Note 1: You can now also assign and lock view types to all views (See
Properties - Identity Data > View Template) which means you cannot
change any visual graphic settings, filters etc also note you cannot
Override Elements by Category only by Element – this also applies to
the sun glasses.
Note 2: If you wish to override any of the above you need to either
1. change view template to none
2. duplicate view template and edit where necessary – preferred
method
Tip: If you need to create a lot of duplicate views based on the master
levels please refer to the following Case App – Multiple View
Duplicator.
Page 38 of 106
View Templates
Below is a comprehensive list of view templates that I have created in

order to satisfy most view types – this means we have set up the most
commonly user drawings types to suit our company standards.
Note 1: As elevations & drafting views can only be assigned to a single

view type you will need to apply a view type to drafting views once
created then adjust the RUK View Group/Sub Group to suit.
Page 39 of 106
View Template Filters
Note the following Filters that are applied to the View Templates
GREEN Box
The section type filters are applied to control the visibility of the various
sections types.
BLUE Box
The material filters are applied to correctly shade elements in
elevation.
Note: For workset projects set up each material as a separate workset

then edit the above Filters and replace Filter_Material with Workset >
Equals > Material Name.
Page 40 of 106
Materials
Model Families loaded into Revit Structure have their material

properties set to ‘By Category’ and then defined globally in the Object
Styles.
Applying generic surface patterns to these materials, through the
materials dialogue box, produces undesired results where tops of walls
and sides of slabs do not shade correctly. It is thus necessary to employ
graphic overrides in views to overcome this. Filters have therefore
been set-up in all views and view templates for all structural elements,
to obtain the desired shading in plan, section and elevation. The Filter
Material parameter needs to be manually input for each element from
the following list, or retrospectively applied in order to achieve this:
Filters [Filter Material Parameter]
 Concrete – Insitu
 Concrete – Precast
 Concrete - Mass
 Timber
 Steel
 Aluminium
Note: You can also apply the view filters to worksets set up for different
materials instead of the above method of filtering by the Filter Material
Parameter. Working this way means you would have a workset for
each material in the project. You can easily amend the filters in the
template to filter by workset (once set up in the project) if doing this –
Just make sure you are on the correct workset when drawing your
elements.
As a background the above method of using the Filter Material

Parameter has been used so that we can pre set up all the material
filters which we can edit once the project has been set up for
worksharing. This avoids the user having to do this manually for every
project as we cannot pre set filters for worksets projects in the
template.
Page 41 of 106
Assigning Material by Object Styles:
Note the following procedure to assign materials to object styles – note

that by creating new object styles this will also help in assigning new
layers when exporting CAD files ie instead of exporting Structural
Framing member to the one common CAD layer we can now assign
various layers based on material.
For this example we will use Structural Framing concrete & steel families
1. Open - \Structural\Framing\Concrete\Concrete – Rectangular
Beam
2. Go to Manage > Object Styles
3. Select New under Modify Subcategories– create a new sub
category – Beam - Concrete
4. Go to Create > Family Types
5. Set Structural Material to By Category
1. Open - \Structural\Framing\Steel\UB-Universal Beams

3. Select New – create a new sub category – Beam - Steel
Points 4 & 5 as above
1. Open - \Structural\Framing\Steel\Rectangular Hollow Sections
3. Select New – create a new sub category – Beam - Steel – Hollow
Points 4 & 5 as above
Now that we have these amended families we can now load these
into your template.
In the template we can now assign materials to the new Object styles
that have appeared.
Page 42 of 106
Note the following default materials that have been assigned to the
following Object Styles.
Curtain Panels
Structural Columns
Structural Connections
Structural Foundations
Page 43 of 106
Structural Framing
Structural Stiffeners
Page 44 of 106
Element Parameters
The following parameters have been added to elements to allow us to

included additional information which can we used as noted.
Filter Groups
RUKLevelInformation This is used to help split elements by level ie
B3-B2, 01-03 or B, GF etc
RUKStructuralCategory This is used to separate framing members
between BRACING and TRUSS
RUKHostReference This is use to state any host Ref ie for Door
and Windows you would enter the host wall
ref or for Truss the Truss Ref
RUKViewFilter This group is used to amend the view ie turn
elements off, change the colour, lineweights
etc.
RUKComments Add any comments of information for others
to note
RUKZoneInformation Please add any zone information Note: This
is in addition to using worksets.
View Shading
Filter Material
Note: For workset projects set up each material as a separate workset
then edit the above Filters and replace Filter_Material with Workset >
Equals > Material Name – once set up you will no longer need to fill out
the Filter_Material Parameter.
Analytical
RUK_Analytical Model Adjusted This is a tick box for any
adjustments ie rigid links
Note: This will show up in the Analytical 3D View as RED.
Page 45 of 106
Design Confirmation
RUK_Element Designed This is a tick box to indicate member

has been designed
RUK_Design Reference Analytical Ref or other ref code
RUK_Designed By Engineers name
RUK_Design Date
RUK_Beam Start Load For adding any loadings (tagged)
RUK_Beam End Load For adding any loadings (Tagged)
RUK_Rebar Allowance Reinforcement allowance kg/m3 to
schedule tonnage
RUKFireRating Fire Rating for specific elements – this
can then be used for the production
of Fire Rating plans and models
RUKSpecificationClause–Finishes coating finishes by reference to
the relevant clause in the
specification
RUKSpecificationClause–Material material designation (including
sub-grades) by reference to the
relevant clause in the specification
RUKEnvironmentalCategory Steel: C1, C2, C3 etc in accordance
with ISO12944
Concrete: XC3/4, XF1 etc in accordance
with BS8500-1
Timber: Service Class 1, 2 or 3 in accordance
with BS EN 1995-1-1
RUKCDEStatusCode All elements should have a CDE Status Code
as per PAS1192-2 Section 9.2.3 – Table 3 – for
model validation to ensure others know
what your elements have been release for.
RUKWorkPackage This is used in conjunction with any contract
specific workpackage to help assist when
transferring to Navisworks.
Page 46 of 106
Contraints
RUK_Member Constrained This is a tick box to indicate

member has been constrained
RUK_Member Two Directions Constrained This is a tick box to indicate
member has been constrained
in 2 directions ie horizontal + vertical
Note 1: These will show up in the Coordination 3D Views as GREEN &

BLUE
Note: 2: From 2015 r2 we now have reveal constraints.
Note 3: Other parameters that need to be considered are IFC which
will not be discussing in the class, but please refer to the following
templates that have just been release for further information and
guidance.
http://help.autodesk.com/view/RVT/2015/ENU/?guid=GUID-4EED7335-
DCC7-48AD-A8BD-8156CAB27A33
http://revit.autodesk.com/library/html/index.html
 IFC Metric Template.rte. This file allows you to create new projects
that are already set to the IFC standard.
 IFC Parameter Upgrade.rvt. This file enables you to upgrade an
existing project to contain IFC parameters by reading the
instructions contained in the IFC Parameter Upgrade.rvt file.
 IFC Shared Parameters.txt. This file contains the shared IFC
parameters if you want to manually update an existing project to
contain all or some of these parameters.
Note: It is recommended that you use the IFC Parameter Upgrade.rvt

file. If you use IFC Shared Parameters.txt, you must add parameters one
at a time, setting the correct categories for each. If you use IFC
Parameter Upgrade.rvt, you can use the Transfer Project Standards tool
to add the parameters in one operation.
Page 47 of 106
Level Filters
Revit 2013 onwards

Structural Levels Applies to all view types except
Documentation – Turns ALL
Structural Levels RED
Structural Levels NOT Applies to ONLY Documentation
views types – Turns off ALL Levels
that are not classes as Structural
Levels
i.
Note: To turn a level off in Documentation Views ie reference levels

please ensure Structural is NOT ticked.
Page 48 of 106
Schedules
The following schedules have been created in order to work out the
following structural quantities:
Concrete Volume
In order to get a total sum of volumes you need to use the Material :
Volume parameter
Concrete Weight
This has been calculated by simply multiplying the volume by the
weight per m3
Material: Volume / 1 m³ * 2.4
Reinforcement Tonnage
This has been calculated by the use of a shared parameter Rebar
Allowance
Material: Volume * RUK_Rebar Allowance / 1000 m³
Steel Tonnage
This is calculated by replacing the W parameter in all families by a
shared parameter RUK_W – this enables us to now calculate the weight
of steel properly by multiplying it by its length instead of using
volumetric calculations which is inaccurate
Length / 1000 mm * RUK_W
Note: In order for us to check steel tonnage we can also calculate this
based on the cut length and also by using the volumetric method
(Material : Volume/1)*7.85 which is based on Detail Level : medium –
this will then give us an overall plus/minus value.
Page 49 of 106
RC BEAM MATERIAL TAKEOFF SCHEDULE
These Framing Schedules are filtered by and must contain a Type Mark
beginning with BC.
Page 50 of 106
STEEL BEAM MATERIAL TAKEOFF SCHEDULE
Page 51 of 106
These Beam Schedules are filtered by and must contain a Type Mark
beginning with BS and not contain BRACING or TRUSS in
RUKStructuralCategory.
Page 52 of 106
STEEL BRACING MATERIAL TAKEOFF SCHEDULE
These Beam Schedules are filtered by RUKStructuralCategory which

must contain BRACING
Page 53 of 106
TRUSS MATERIAL TAKEOFF SCHEDULE
Page 54 of 106
These Beam Schedules are filtered by RUKStructuralCategory which

must contain TRUSS.
Note: RUKHostReference must contain the TRUSS host reference ie

TR01.
Please ensure ALL framing members of the Truss contain this in order for
the group to work.
Page 55 of 106
Titleblocks
The following section highlights various parameters and formulas that

have been adopted to create a titleblock that can change to suit
various scenarios.
The titleblock shown is an A1 indicating:

 General Notes
 Date/Time Stamp
 SHE Box for drawing specific Safety Health and Environment
Information (This is to suit the Construction Design Maintenance
(CDM) Regulations in the UK)
 Help notes to assist the user
Page 56 of 106
Title Sheet Parameters
Instance Parameters (Apply ONLY to the current Title Sheet)
Sheet Name Viz On = Browser Sheet Name is used

Off = Drawing Title Lines 1-4 are used
(Standard)
Scale Viz On = Revit Controlled Scale
Off = Use parameter ‘Sheet Scale’ to manually
specify scale
SHE Box Used to turn On/Off the SHE Box on the Title
Sheet
General Notes Used to turn On/Off the General Notes on the
Title Sheet
Page 57 of 106
Type Parameters (Apply to ALL Title Sheets)
RUK Drawing No This is selected via the Title Sheet Family Type
Date/Time Stamp Used to turn On/Off the stamp
AEC Drawing No This is selected via the Title Sheet Family Type
Help Used to turn On/Off all RED guidance notes
Office Address Select an office from the drop down list
Page 58 of 106
Formulas to Drive Graphics
In most titleblocks we use the simple Yes/No parameter.to drive most

of the layout.
An example of avoiding over excessive numbers of parameters we

can use the formulas:
not plus and as indicated below.
If we take Sheet Scales Viz this is currently off because the formula
specifies not(Scale Viz) ie if Scale Viz is On then Sheet Scale Viz is Off.
Page 59 of 106
To create the drop down Office Address List:
 created by each office address formed as a generic annotation

family
 create an Office Address parameter with Type of Parameter set to
Family type: then select Generic Annotation
 load in all the office addresses, select them and assign label to
Office Address
Page 60 of 106
Main Title
Page 61 of 106
General Notes
Title sheet when SHE Box is turned OFF.
Page 62 of 106
SHE Box
Title sheet when SHE Box is turned ON.
Page 63 of 106
Apply general model management

principles
This section is a general overview of various points that should be

looked at to help assist better management of your model.
Note the following quick win items:
 Revit Viewer
This does not require a license so is great for just viewing the model and
avoids any mistakes by the user being unable to save or make any
changes but it is limited l
 Orient To View
A good method to help assist the coordination and understand of your
model is to set up 3D views of each floor – this is easily done by using
Orient to View from the View Cube.
 Weekly To-Do List
A simple sets of rules to help improve model performance
 Remove any unnecessary views/Tidy Project browser
 Check Warnings
 Purge unused
Page 64 of 106
Map Out Your Process
Page 65 of 106
File Maintenance on you Project
Note the following file management procedure that will help keep the
file size as small as possible and avoid errors.
• Because of the memory leaks that are within Revit you should
completely close out of Revit at least once a day and restart the
program.
• Every day you open the project you should be making a new
local file. This helps keep a consistent local file.
• If your models crashes perform the following steps (ensure
everyone has sync’d with the central file and closed down all
local files):
1. Open up the recovery model and perform a sync to ensure
everything has been saved over.
2. Audit the central file
3. Create a new local file – Note: Ensure all members of the
project create new local files.
Revit Files with multiple users

1. Create a new Central File every month or at different
stages of the project (eg. Stages 2, 3 or at major
milestones)
2. Audit the Central File weekly
3. Create a new Local File every day.
Note: When creating a new Local File always appendage the existing
file so that backups are kept, these can be deleted every week or
every month depending on how often new Local Files are created
(see above)
Purge unused regularly but check what is being removed – Note: This
should only be done by the lead BIM Project Coordinator.
Page 66 of 106
Revit Origin
The Revit origin is marked in plan with two reference planes in the
template file. You should:
• Model all circular/elliptical/symmetrical buildings with their
centre positioned on the origin point. All sports grounds should be
modelled with the centre of the pitch on the origin point.
• Model all rectilinear buildings with bottom left grid intersection on
the origin point.
RUK-Scope Box
Project Origin:
0,0
Structural Plans have been set up with a Scope Box called RUK_Scope
Box with all initial Levels assigned to it.
All view boundaries should be defined by scope boxes especially

dependent views as these are easier to control if you make changes
later.
Page 67 of 106
Creating Selection Sets
Another way of using filters is the ability to create selection sets which in
turn can show up in filters.
By using this method you can quickly set up filters without having to go
through all the normal rules.
Quick Tip: For all saved section sets please prefix with SS-
Note: When you create a saved selection set this also appears in the
filter list (Important – you cannot edit this filter and if you select this filter
and click edit you will be unable to create or edit any filter) Please
ensure you have set up a filter prior to creating saved selection sets.
Example: This example shows a wall loading plan (Figure 1) where

selection sets have been set up to identify different walls loadings as
different colours.
Filters have been used to change the colour of the selection sets
(Figure 3)
To Create a Selection Set: Pick an element(s) then in Manage (Figure
2) pick save (please prefix with SS-)
To Edit a Selection Set: In Manage (Figure 2) pick Edit, then select the
required prefixed SS- selection set (Figure 4) then pick Edit – then use
Add to/Remove from Section (Figure 5) to make amendments
Filter Case Study:

The Problem: (Figure 6)
To create a 3D view that highlights all walls in the model that have the
incorrect naming. As all walls are named 2??-level-W(unique
reference) we are looking for walls that do not start with 2.
Solution: (Figure 7)
Create a filter which looks at wall categories only and filters by Mark
that does not being with 2.
This Filter is then used to surface shade walls soild RED.
Note: 2 No additional filters have been added to show all walls that do
being with 2 and are made transparent and switch all elements off
except walls.
Page 68 of 106
Figure 1
Page 69 of 106
Figure 2
Figure 3
Figure 4
Page 70 of 106
Figure 5
Figure 6
Page 71 of 106
Figure 7
Page 72 of 106
Scope Boxes
Scope boxes perform functions as noted below:
Grids & Levels should be assigned to a name scope box to ensure

uniformity of grid and level extents between views. This works best for
orthogonal/square buildings rather than round buildings with radial
grids because the scope box can only be cubic and radial grids won't
usually conform to this shape on plan.
Views – Scope boxes can also be used to align views at specific angles
without the need to rotate views on title sheets – this can be useful if
you have a project where you have various angled areas you wish to
show orthogonal on plan.
Quick Tip: How to remember the rotation of scope boxes?

As a scope box does not remember its rotation angle set up ref lines
(named with same name as scope box) to show the angle the scope
box has been rotated.
Page 73 of 106
Cast Study 1:
Problem:
Project had 5 unique areas at different orientations with 5 surrounding

towers all at different levels.
Surrounding towers had to show floors plus levels
Main model had to be split up to show each area orthogonal on
drawing sheets.
Solution:
• Each area had a unique scope box with all grids and levels
assigned
Page 74 of 106
• Dependent views where set up each one assigned to a different

scope box
Page 75 of 106
Issuing Model Data
The design team should agree and document a Data Exchange

Protocol as part of the Project Execution Plan. Revit model file size can
often exceed 250mb for a single file; as such it is not possible to
distribute the information by email. Methods such as FTP, Extranet or
Online Document Management Systems are some of the methods
which can be used for sharing large files.
All contributing stakeholder are responsible for performing the

following checks before distributing their model(s) among the project
team. Each discipline should be prepared, if requested to provide
proof that their models have been reviewed, checked, and approved
in accordance with the Project Quality Plan.
Check Definition Software Program Frequency Output

Check there are no
unintended model
QA/QC
Visual Check components and the Autodesk Revit Ongoing
Report
design intent has
been followed
Carry out
interference check to
identify areas in the
Interference Autodesk QA/QC
model where two or Fortnightly
Check Navisworks Report
more building
components are
clashing.
Collaborative Resolve identified Internal
Autodesk QA/QC
Design conflicts Design
Navisworks Report
Review Review
Verify that the BIM QA/QC
and CAD Standard Autodesk Revit Report
have been followed Model Review & submitted
Standards
(fonts, dimensions, Revit Model Ongoing with
Check
line styles, symbols Validation model(s) in
etc) Checklist native
format
Page 76 of 106
Analysis the BIM to

make sure the model
has no undefined,
incorrectly defined or QA/QC
duplicated elements, Report
Model
all elements are Solibri Model At each submitted
Integrity
shown in native 3D Checker Milestone with
Check
model are present in model(s) in
IFC model, clashes IFC format
have been resolved
and data standards
are compliant
Review the BIM QA/QC
against Project Report
Building
specific codes Solibri Model At each submitted
Code
Checker Milestone with
Validation
model(s) in
IFC format
Page 77 of 106
Revit Model Validation Checklist

Revit File Details
Model Name
Date
Prepared By
Approved By
Model Preparation
Check model file name conforms to Standards ☐
All users to “Save to Central” relinquishing all editing rights ☐
Review and fix all warning messages where possible ☐
Check that all families conform to Standard naming
☐
conventions
Check Line Styles conform to Standard naming conventions ☐
Check that all content is in the correct Workset and conforms
☐
to Standards
Check model is correctly assembled through visual inspection ☐
Document Phasing / Design Options if used ☐

Update Model Matrix if required ☐
Update revision on Splash Sheet ☐
Update Project Information ☐
Validation of Model
Open Central file with Detached from Central and Audit
☐
selected
Remove non transmittal linked-in files ☐
Remove all non-required Views / Legends / Schedules /
☐
Sheets / Images
Remove unwanted Design Options ☐
Purge model (repeat process three times as materials are

☐
only removed after the parent object has been removed)
Update Save to Central view with any relevant model notes ☐
Save file to publish folder with same name ☐
Page 78 of 106
Note 1: The following Case App that will assist to Delete Sheets, Views,
and Revit Links –
http://www.apps.case-inc.com/content/free-delete-sheets-views-
and-revit-links
Note 2: You can also use the eTransmit for Revit (subscription) app
which will copy a Revit model and dependent files to a single folder for
issue.
The model is now ready for distribution via the process agreed in the
Data Exchange Protocol.
Page 79 of 106
Worksets
A good workflow is to set up an ADMIN user to lockdown certain

aspects of your model to restrict user functionally ie Grids & Levels,
Scope boxes, Ref Planes.
This can be further enforced by setting up an additional workset called
ADMIN for any specific elements the Project BIM Coordinator wants to
control.
By doing this we keep important changes under the control of the
Project BIM Coordinator (admin).
To achieve this, you only need a separate admin User Name in
Options. Once inside as admin create a Workset and call this as Admin
. Now you can move the items you want to work on the new set, and
before you close the file, make sure you do not relinquish User-created
worksets.
Now if you try to delete or amend any of the admin controlled

elements you will get the following message:
Page 80 of 106
Transferring Project Standards To Old Projects
If you have an old project and you wish to transfer parameters,

text/dimension styles etc then please note the following process.
Note 1: Please ensure you backup your project prior to continuing with
this process.
Note 2: Ensure all users delete all local files.
4. Ensuring you are the ONLY user and create a new local file.
5. Whilst keeping the 1st model open (point 1), create a new project
using R -> New -> Project, then ok using the current Template.
6. Using View -> Switch Windows (or use Alt-Tab) go into your 1st model
(point 1)
7. Using Manage -> Transfer Project Standards – Select Copy from:

Project 1
8. Now pick Check None, then select all of the categories as noted
below
Page 81 of 106
Page 82 of 106
9. Once the transfer has taken place you may receive the following
message.
From here you can decide to either Overwrite, New Only or Cancel.
In most cases you will overwrite but if your model is very old you may
wish to just pick New Only in order for you to select which elements you
change at a later date.
10. Review your model and update as required ie text, dimensions,

section types etc etc also load in any revised families ie Annotation
Tag, Title Sheets from from office standards folder.
Note: A good point of reference is to check the date of families in this

directory and load in any that are newer than the original date of
your model.
Page 83 of 106
Manage CAD files for large multiuser

projects
Were possible all CAD Data should only be linked into a Revit model
through the process of ‘linked view’ from a linked master CAD Data
Revit model. By doing this all members of the team are kept up to
date with the latest drawings controlled by the Project BIM
Coordinator.
With multi-model projects this ensure all users are using the correct
CAD data and will also eliminate potential CAD corruption in the main
model – one good point is by using By linked view – you can rapidly
switch between CAD layouts within the same view without having to
copy/paste from other floors.
By using this process we also significantly reduce the amount of RAM
resourcing being used by linked CAD data.
Note: Files must not be linked to local office drives or user desktops use
FULL network path ONLY.
AutoCAD Data Preparation
AutoCAD data to be imported should be correctly prepared prior to

linking into the Revit project models. The following procedures should
be carried out on the base
AutoCAD file(s) prior to linking:
 Remove or bind all Xrefs
 Delete all unnecessary layers including frozen and switched off
layers.
 Delete all hatching.
 Check the UCS is located at a suitable location in or close to the
model information.
 Purge (including nested blocks)
 Audit
 Save into an earlier release format such as AutoCAD 14, 2002 etc...
Page 84 of 106
CAD Data Revit Model Procedure:
1. Set up a new model to act as a placeholder for all CAD data.

Setting up Views:
As the CAD Data Revit model is only a placeholder for CAD data,
levels are not necessarily important but you may wish to link in the
main model and copy/monitor all the required levels and a few grids
to ensure the CAD data is easily located.
2. Link in original model
3. Copy/monitor all required levels then create floor plans
4. Copy/monitor a few gridlines to ensure CAD Data can be easily
located
Linking in CAD Data:

1. Ensure you are in the correct view / level
2. Select File, Import/Link, CAD Formats
3. Browse to the project subfolder
4. Select the dwg file to be linked
5. Ensure the following options are selected within the bottom of the
dialog box – Note that Import units & Positioning: will be to specific
project requirements.
6. After the CAD data is linked ensure you pick this element and in the
Options Bar select Foreground – this will ensure the CAD data is
overlaid ie on top of all revit information.
Page 85 of 106
Main Revit Model Process:
Now that we have the CAD data Revit model set up – we can now link
this placeholder into various revit models.
Link in the placeholder:

1. Link in the CAD data Revit model using Origin to Origin (Note this
may need to change to suit overall project set up)
2. In your view type VV (Visibility/Graphics) > Revit Links – you will see
your CAD data Revit model – pick By Host View under Display
Setting.
The pick By linked view then under the Linked view: select the
appropriate level
3. After you pick ok a few times you will see that the linked view has
been overlaid onto your plan.
Note this this procedure can be applied to Section and Elevation

views.
Page 86 of 106
Creating a New Revit Template from Scratch
As an extra here is a complete list of what I go through to create a new

template from scratch – normally this process takes 1-2 days including
testing.
1. Start new template based on 2015 structures Out Of The Box

2. Transfer project standards from Revit 2014
3. Transfer project standards from Revit 2014 office template for Object
Styles - Override
4. Create 2 ref planes at 0,0 names RUK-OriginRefEW & RUK-
OriginRefNS
5. Create section types for User, Documentation, Coordination, Core,
Reinforcement, Analytical & Elevation
6. Create elevation types for User, Coordination & Analytical - DO NOT
INCLUDE DOCUMENTATION
7. Rename existing 2 levels then create additional levels
8. Create level 0 ref plane and name it RUK-Level0Datum
9. Create Structural Plan Types
10. Create Plans for RUK View Groups 01, 02, 06
11. Assign RUK Scope Box to 02 Documentation Plans
12. Delete existing analytical views, site and elevations
13. Create 3D Views of Plans for RUK View Groups 01, 02, 06
14. Copy all schedules, drafting views, legends & sheets
15. Load all company family content
16. Load all structural members as per 2014 template

17. Purge unwanted elements - 360 (2014)
Page 87 of 106
Page 88 of 106
Page 89 of 106
Page 90 of 106
Page 91 of 106
Page 92 of 106
Page 93 of 106
Page 94 of 106
Page 95 of 106
Page 96 of 106
18. Delete M_Callout

19. Delete both M_Section Heads
20. Delete M_View Title then rename all associated view titles etc
21. Purge unwanted elements - 6 (2014)
Page 97 of 106
22. Load in all tags, symbols etc not transferred over

23. Assign all the correct tags to Loads Tags And Symbols
24. Load all title sheets
25. Reinforcement Settings - update Area & Path Reinforcement
settings
26. Reinforcement Settings and Abbreviations
27. Set all loaded families Rebar Allowance to 0
28. Import Lineweights
29. Fix all text styles to suit company standards
30. Fix lineweight to suit company standards
31. Fix linestlyes to suit company standards
32. Fix arrows and ticks to suit company standards
33. Purge unwanted elements 2015 - 210/3
Page 98 of 106
Page 99 of 106
Page 100 of 106

Page 101 of 106

Page 102 of 106

Page 103 of 106

Page 104 of 106

Page 105 of 106

“The greater our knowledge increases, the greater our ignorance

unfolds” JFK
Thank you for taking the time to attend my class.
If you would like to discuss any of the class content or have suggestions
or different points of view then I would love to hear from you as
knowledge is something that should be shared for everyone to benefit.
I would like to thank…..

My family and friends, the following reviteers who through discussion
and past presentations have inspired some of my class content
Allan Brown – Technical Director at URS Corporation Ltd,
Michael Boyd – BIM Manager at WSP
Matthew Perry – Senior Technician at Buro Happold,
plus colleagues from around the world at Ramboll for their support.
I look forward to meeting you all again at future Events.
Page 106 of 106

S02 - Handout - Autodesk Revit Structure - Management Templates Standards

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

S02 - Handout - Autodesk Revit Structure - Management Templates Standards

Uploaded by

Copyright:

Available Formats

Session 2

Autodesk® Revit® Structure -

About the Speaker:

In 2009 Graham co-founded GRUG - The Glasgow Revit User Group

Browser Organisation Explained .......................................................................... 29

AutoCAD Data Preparation ............................................................................. 84

The following handout is a combination of nearly 3 year’s work during

I hope I have explained enough for you to understand my thoughts,

Define standards and protocols for

The following section highlights various elements of collaboration that I

 The Project Kick Off Meeting

Project Kick Off Meeting

In order to prepare the Project Execution Plan there needs to be an

Below is an initial list of points to raise with possible outcomes.

14. Project Deliverables.

In the UK the above agenda is mostly drive by the following documents

To ensure key elements of the coordination process is understood we

Example of Ramboll’s Project Management Processes

Model Exchange for Project Collaboration (Design data

The example below highlights the model exchange workflows between

2D DWG AutoCAD 2D DWG

Clash Avoidance Process

Wednesday to Tuesday Tuesday Tuesday Wednesday Monday (AM)

Download other Design Review clashes prior

 Run through reported  Issue minutes of coordination meeting,

Each gateway is fully defined.

Model Exchange Matrix

Navisworks Exchange Matrix

Autodesk NavisWorks is a BIM collaboration tool which is able to read a

What should you tell your collaborators?

When working with other partners in Revit for collaboration it is

Model Specific Information

Project Specific Information

From 2014 the View Template Schedule has been added.

List all main structural levels being used in the project.

From 2014 the Project Levels Schedule has been added.

List any copied scope boxes from other linked models.

Project Shared Coordinates

List any Design Options being used are to be named.

Collaboration – General Points to Note:

Create templates that address browser

By doing this we are able to split the browser up so that we work in

Project Browser (Views) Browser Organisation

Project Browser (cont. – Legends, Schedules & Sheets)

Browser Organisation Explained

Note 2: 3D View: UR-Designed - User Review highlights ALL

Note 3: The following constraints apply to ALL Views:

Note 1: The following constraints apply to ALL Views:

Note 1: ALL views to have RF- suffix

05. Note & General Notes and Abbreviations, to be placed on sheets

Note 2: 3D View: AN-Fastrak Integration Status highlights ALL

Note 3: ALL views to have AN- suffix

Note 5: 3D View: AN-Node Connection Status (2014

08. Navisworks 3D views for exporting to Navisworks, for clash detection

Views set up to structure the browser for 2D drafting views

Views set up to structure the browser for Reinforcement views

Views in which other discipline drawings/models can be linked-in and

Views in which only the analytical model should be shown.

3D views for exporting to Navisworks for clash avoidance (.nwc).

Section / Elevation / Callout / Plan Types

Section Types Available: Detail View/Callout Types Available:

Building Elevation Types Available:

Plan Types For 2015