Wall, Floor, Roof and Ceiling family objects do not exist as separate family files, they only exist within a Revit file. They can however be transferred between Revit projects. Use Transfer Project Standards command to import all types, or copy and paste individual objects of the desired type to import individual types.
Description vs Used For
There are two ways of naming System families. A name that:
describes the system family literally (e.g. Concrete 200mm)
describes what the system family is used for (e.g. Core Wall)
Both uses are valid.
If the system family is always used for a particular purpose, and you may want to globally change it later, then using a system family based on use is best. Otherwise it is helpful to everyone if the name describes what it is.
System Families Named by Use
System families whose names are based on what they are used for just use ordinary words.
System families may be tagged and scheduled, or they may be used to represent something in the model.
A system family that will be be tagged and scheduled always begins with a prefix an asterisk (*).
A system family that is used to represent something that won't be be tagged and scheduled always begin with a prefix of an underscore (_).
The names should generally follow these rules:
Must have an asterisk or underscore as prefix.
Put most important information to the left, with importance diminishing towards the right.
(e.g. use Sewer-main, NOT Main Sewer)
Don't make the name too long. It is not helpful if the names is wider than the dialog box it appears in.
Be literal – the name should be understandable by anyone.
For example:
System Families Named by Description
Family objects should generally follow these rules:
Put most important information to the left, with importance diminishing towards the right.
Make sure all of the same type of object are named the same, (e.g. use fcs or cement sheet, but not both.)
Be literal – the name should be understandable by anyone.
When describing sizes, always do it in the order of WIDTH then HEIGHT.
Where:
For example:
Refer to Practice > Scheduling for more information on codes.
Standard Wrap Codes
Standard Wall Function Codes
Where:
For example:
Where:
For example:
.B1.01+T1.02 (230)=f.e
.T1.02+T1.01
external wall, base brick structure 230 overall max. thickness, top timber structure, external.
internal wall, base timber structure T1.02 code, top timber structure, T1.01 code, internal. (typically base plasterb’d on timber studs, upper part studs only).
Where wall type codes are not known include overall thickness. If there are more than one Basic wall type starting with the same characters use the wall type’s full name. For example:
.B1.xx230+T1.xx110=f.e
.B1.xx_-/brick110/-+S1_fcs12/stud92/pb13=f.e
base brick structure 230 thick, top timber structure 110 thick, external wall.
base brick structure, top stud wall FCS external, PB internal, external wall.
.floor code
_construction
=function
Where:
For example:
.roof code
_construction
Where:
For example:
.ceiling code
_construction
Where:
For example:
.T1.01_pb10/furring32, joists190/-
compound ceiling, timber code, structure is 190mm timber joists with plasterboard on 32mm furring channels.
Basic ceiling types are not very useful; they are a thin plane that don’t show up with any thickness in sections. Also when placing faced based families they tend to go in upside down - on top of the ceiling instead of below it.
DON’T USE THEM unless they are a quick and dirty fix for modelling.
.material
Where:
For example:
.Plasterbd
basic ceiling, plasterboard material.