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.
A ganged window unit is created as a nested and shared family. In this case, the large fixed center window was used as the host family and the 2 side windows were nested as shared families. The family was saved as Gang_Fixed Host.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 the double hung windows are tagged and scheduled separately. The fixed window that was the host is not included in the schedule and not tagged. However, notice the ganged window name, Gang_Fixed Host, is listed with the subcomponents. This window represents the main window composed of the of the 3 subcomponent windows.
In order to get both the fixed and double hung sub-component windows to tag and schedule, the same triple window family was created, but this time a new window family is 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.
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 and the commercial toilet is not included. However, notice that the mens_bathroom unit, is listed with the subcomponents.
To share a family before nesting it
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.
To nest shared families in a host family