Adding Families - Autodesk Revit Architecture 2015 Essentials - page 121

whereas component families are created and stored as RFA files outside the proj-
ect environment. In-place families should be used only for unique, one-of-a-kind
objects for which you require nearby geometry as a reference to design.
We will start by exploring system families because they reside directly in the
project. Then we will further explore component and in-place families later in
this chapter.
Working with System Families
The first type of family you need to understand is the system family. The best
way to characterize system families is to consider them the hosts for other types
of geometry. 3D elements such as walls, floors, ceilings, and roofs allow other
elements such as doors and windows to exist on them or in them. Other 3D ele-
ments, such as stairs and railings, are also system families.
System families are unique in that they create geometry by using a set of rules
applied to guiding geometry. If you think about a simple wall, for example, its
thickness is defined by a series of structural layers (framing, sheathing, and
finishes), its length is expressed by a linear path, and its height is established
by some set of horizontal boundaries (either a datum or another element like a
roof). As another example, a floor's thickness is defined by a series of structural
layers, its vertical location is determined by a datum (level), and its bound-
ary extents are defined by a series of lines. In the project, these rules are the
instance and type properties.
Some system families are 2D. These types of system families include text,
dimensions, and filled regions. Although the 2D variety of families are still con-
sidered system families, we think they are better referred to as project settings to
avoid confusing them with the more common understanding of families.
Loading System Families
Because system families exist only in the project environment, there are only
a few ways you can load them between projects. The first method is to use the
Transfer Project Standards command. This method transfers all the families and
types in a selected category between projects.
A more informal method of transferring system families is to use the Windows
Clipboard functions and copy/paste content between projects. This method is use-
ful if you want to load a limited number of specific families into your active project.
Although it isn't an active loading method, the final technique to manage sys-
tem families is to include them in your project templates. After you establish a