Back to tabs Family tables Parametrics

Assembly design intent Basic guidelines Attach part surfaces to part surfaces only if the assembly will never change. Attach parts to skeleton features to prevent regeneration failures when component parts change or parts are omitted from the assembly. Never use the "save as" command in the workspace to copy assemblies. This leads to complex dependencies and creates unwanted copies of component parts. If multiple instances of the same part are needed in an assembly, use the "repeat" or "pattern" function to place components. Family tables Use family tables when creating multiple assemblies that are similar but vary in overall length or width. Build the generic assembly with components that have family tables. Assign instance in the family table. Select the correct component instance for each assembly instance Use family tables when creating multiple assemblies that are similar but vary in number, quantity, and position of component parts. Build the generic assembly by assembling all possible combinations of components. Assign instances in the family table and select the correct components for each instance. When modifying assemblies with family tables, be sure all instances of the assembly and component parts are present in your workspace. Use the "verify" command before checking in new or modified assembly models with family tables. This makes all instances visible in commonspace (instances are created from the generic model, they do not have physical object files). Parametrics Assemblies automatically update to changes in design parameters. Parameters you defined in your part models can be driven in the assembly by parent-child dependencies, user created relationships, family tables, skeletons, and Pro/PROGRAM routines. These relationships should be developed during the planning stages of your project using top-down design techniques. Test your assembly models. Flex geometry by modifying key driving parameters and checking for the expected results.