안녕하세요,

오랫만에 포스팅합니다. 주말 잘 보내셨나요?
오늘은 Revit Family Content Management의 일부영상을 소개합니다.

When you load the family into a project and attempt to dimension to it, the strong reference planes with have preference over the weak ones. So if you hover over the element and there is a strong and weak reference plane in close proximity, the tool will snap to the strong one and you'll have to tab to get to the weak one.

If you assign an instance length parameter to reference planes in a family (so you get shape handles in a project environment), the strong and weak ones will behave differently once loaded into a project too. Once loaded into the project, aligning the strong reference plane to an element will stretch the family, whilst aligning the weak reference plane will move the entire family to that element without altering that instance parameter.

To create a family with nested and shared components, share the families before you nest them in a host family. The host family does not need to be a shared family.

When you create a nested family of shared components, the first decision you need to make is in what category the host family will belong. This decision has many downstream implications for tagging, scheduling, and ODBC information, as described in the examples below.

Window Family Example

A ganged window unit is created as a nested and shared family. In this case, the large center window was used as the host family and the 2 side windows were nested as shared families. This window is intended to be built on-site using the subcomponents that are purchased as separate units by the builder. The family was saved as Triple_window.rfa.

Nested windows

When the ganged unit shown above is loaded into a project, tagged, and scheduled, the result is as follows:

Nested and shared families loaded into a project

Notice that each window is tagged and scheduled separately. However, notice the ganged window name, Triple _window, is listed with the subcomponents. This window also represents the main window of the 3 window set.

In the example shown below, the same triple window family was created, but with a new window family used as the host family and both the fixed window and the double-hung windows loaded as shared families. Notice the difference in the tagging and scheduling.

Ganged window family started as a new family

In the example shown above, notice the host family schedules with each of the 3 subcomponent windows. If this is not your design intent, you should follow the previous example, where one of the subcomponents is the host family.

Bathroom Unit Example

A bathroom unit is created as a nested and shared family. The commercial toilet was used as the host family and the wall hung urinal and sink were nested as shared families. The family was saved as mens_bathroom.rfa

Nested urinal and lavatory sink

When the bathroom unit shown above is loaded into a project and scheduled, the result is as follows:

Nested and shared families loaded into a project

Notice that each urinal and lavatory sink is scheduled separately. However, notice that the mens_bathroom unit, is listed with the subcomponents.

To share a family before nesting it

1. Open a family to be shared, and click Create tabProperties panel (Family Category and Parameters).
   Attention: Annotation, profile, and in-place families cannot be shared families.
2. In the Family Category and Parameters dialog, under Family Parameters, select Shared.

   Although you can set most families as shared families, it only becomes relevant when the family is nested into another family and loaded into a project.

3. Click OK.
4. Save and close the family.

To nest shared families in a host family

1. Open the host family or start a new family.
2. Open the families that you want to nest, and share them.
3. Load and place a nested component within the host family.
4. Repeat this process for each nested component.
5. Save the family.

Creating Vertical Families

You can create vertical or non-vertical families. This option pertains only to families hosted by walls, floors, ceilings, roofs, and site surfaces. You can set a family component, such as a tree or a chandelier, to Always Vertical; once loaded into a project, the component remains vertical regardless of the slope of the host. In the case of a car or a park bench, you can set the Always Vertical option to No; this allows the car and the park bench to adapt to the slope of the host.

NOTE: The Always Vertical parameter does not apply to families created in non host-based templates.

Example of Vertical and Non-Vertical Families; 3 trees are set to Always Vertical, 2 trees are not.

To set the always vertical parameter for a family

1 In the Family Editor, click Settings menu ➤ Family Category and Parameters.

2 Select the check box to enable the Always Vertical parameter.

3 Click OK.

Cuttable and Non-Cuttable Family Categories

Cuttable Families

If a family is cuttable, the family displays as cut when the cut plane of a view intersects that family in all types of views.

In the Family Element Visibility Settings dialog, there is an option called When cut in Plan/RCP. This option determines if family geometry is shown when the cut plane intersects that family. For example, in door families, the geometry for plan swing is set to be shown when the door is cut in plan views and not shown when the door is not cut.

This option is never made available and is never selected for non-cuttable families. For some cuttable families, the option is made available, and you can select it. For other cuttable families, the option is never made available, but it is always selected.

The following table lists cuttable families and whether the option is made available for that family.

Non-Cuttable Families

The following families are not cuttable and are always shown in projection in views:

■ Balusters

■ Detail Items

■ Electrical Equipment

■ Electrical Fixtures

■ Entourage

■ Furniture

■ Furniture Systems

■ Lighting Fixtures

■ Mechanical Equipment

■ Parking

■ Planting

■ Plumbing Fixtures

■ Specialty Equipment

REVIT Parameter Types

A type catalog is an external text file (TXT) that contains the parameters and their values that create the different types in a specific family.

Following is a sample type catalog TXT file:

,Manufacturer##other##,Length##length##centimeters,Width##length##centimeters,Height##length##centimeters

MA36x30,Revit,36.5,2.75,30

MA40x24,Revit,40.5,3.25,24

When loading the corresponding family, you would see the following type catalog:

There are several ways to create a comma-delimited .txt file. You can type it in using a text editor like Notepad, or you can use database or spreadsheet software to automate the process.

You can export your project to a database using ODBC, and then download the element type tables in comma-delimited format. See Exporting to ODBC in the Revit Architecture 2009 Help.

As you create the type catalog, follow these rules:

■ Save the type catalog file name with a .txt extension; the file must have the same name and same directory path as the Revit Architecture family, for example, Doors/door.rfa and Doors/door.txt.

■ The left column lists types.

■ The top row of the file is for parameter declaration. Format is columnname##type##unit.

■ Use decimals.

■ Parameter names are case sensitive.

■ You can use single or double quotes. If you are using double quotes, you need to enter "" for Revit Architecture to understand it as double quotes.

■ Valid unit types are length, area, volume, angle, force, and linear force.

■ Valid units: Valid units and suffixes:

■ For length: inches ("), feet ('), millimeters (mm), centimeters (cm), or meters (m).

■ For area: square_feet (SF), square_inches (in2), square_meters (m2), square_centimeters (cm2), square_millimeters (mm2), acres, or hectares.

■ For volume: cubic_yards (CY), cubic_feet (CF), cubic_inches (in3), cubic_centimeters (cm3),

cubic_millimeters (mm3), liters (L), gallons (gal).

■ For angle: decimal_degrees (°), minutes ('), seconds (").

■ For force: newtons (N), decanewtons (daN), kilonewtons (kN), meganewtons (MN), kips (kip),

kilograms_force (kgf), tonnes_force (Tf), and pounds (P).

■ For linear force: newtons_per_meter (N/m), decanewtons_per_meter (dan/m), kilonewtons_per_meter (kN/m), meganewtons_per_meter (MN/m), kips_per_foot (kip/ft), kilograms_force_per_meter (kgf/m), tonnes_force_per_meter (Tf/m), pounds_per_foot (P/ft).

■ You can enter a value for parameters of type Family Type. To declare the Family Type parameter in the parameter declaration, you would enter column-name##other##. The column name is the same as the Family Type parameter name. In the type catalog file, enter values as Family Name : Family Type. Be sure there are spaces before and after the colon. So for a family file called Chair-Executive.rfa with a type called Big Boss, you would enter Chair-Executive : Big Boss. If the family file has only one type, and it is the same name as the family, you do not need to include the Family Name.

■ Revit Architecture applies project unit settings to type catalogs when loading a family.

Lookup table

Lookup tables are used to define parameter values in an external comma-separated values (CSV) file.

This lets you specify multiple part sizes that are based on a table without creating a separate family type for each size. Revit provides a size_lookup function that can be used to read the necessary values from a CSV file.

Data from lookup tables for is stored within the family and use the size_lookup function. See Managing Lookup Tables. For upgraded projects, you can define the location of lookup table files with the LookupTableLocation parameter in the Revit.ini file. Folders are created for each type of content installed.

Lookup tables are used in conjunction with type catalogs. For information about creating type catalogs, see Creating a Type Catalog.

The syntax for the size_lookup function uses the following format:

result=size_lookup(LookupTableName, LookupColumn, DefaultIfNotFound, LookupValue1, LookupValue2, ..., LookupValueN)

Family Types Dialog - Lock Parameter

This concept showed up a couple releases ago if I recall correctly. I'm referring to this bugger:

The help file says:

"You can maintain the parametric relationships between labeled dimensions by locking them. To lock a dimension directly in the drawing area, click next to the dimension."

"When a labeled dimension is locked, all of the associated parameters also lock. This means that as the dimensions are moved in the drawing area, the associated parameters are constrained and the dimension value is preserved."

"Note: Locked dimensions and their associated parameters cannot be changed in the drawing area. Use the Lock column in the Family Types dialog to change them."

"When a labeled dimension is unlocked, all of the referenced geometry unlocks and is unconstrained."

"To lock a labeled dimension from the Family Types dialog
• Click a dimension in the drawing area.
• Click Modify | Dimensions tab | Properties panel Family Types.
• Select Lock to constrain a parameter."