<?xml version="1.0" encoding="UTF-8"?>
<!--Arbortext, Inc., 1988-2015, v.4002-->
<!DOCTYPE pubsConcept PUBLIC "-//PTC//DTD PUBS DITA Concept//EN"
 "pubsConcept.dtd">
<?Pub Inc?>
<pubsConcept id="AboutFamilyTables-021EB59C">
<title>About Family Tables</title>
<prolog>
<metadata><keywords><keyword translate="no">MODULE@fundamentals,ProCmdMmFamTab@CMD,proe_modelcheck_family_info@OnlineHelp,proe_modelcheck_ft_def_vals@OnlineHelp,proe_modelcheck_ft_std_parms@OnlineHelp,proe_modelcheck_gen_components@OnlineHelp,proe_modelcheck_instance_name@OnlineHelp,ftb_edit_table@DLG,__top_invis_menu@part@family#tab,proe_mdxmdo_about_editing_a_mechanism_model@OnlineHelp,proe_about_working_with_family_tables@OnlineHelp</keyword>
</keywords></metadata>
</prolog>
<pubsConbody>
<p>Family Tables are collections of parts (or assemblies or features)
that are essentially similar, but deviate slightly in one or two aspects,
such as size or detail features.</p>
<p>For example, wood screws come in various sizes, but they all look
alike and perform the same function. Thus, it is useful to think of
them as a family of parts. Parts in Family Tables are also known as
table-driven parts.</p>
<p>The following figure shows a family of bolts. The generic is at
the top of the figure, and its instances are underneath. The generic
is the parent.</p>
<p><image href="image/img00048.png" scope="local"></image></p>
<p>Using Family Tables, you can:</p>
<ul>
<li><p>Create and store large numbers of objects simply and compactly</p
></li>
<li><p>Save time and effort by standardizing part generation</p></li>
<li><p>Generate variations of a part from one part file without having
to re-create and generate each one</p></li>
<li><p>Create slight variations in parts without having to use relations
to change the model</p></li>
<li><p>Create a table of parts that can be saved to a print file and
included in part catalogs</p></li>
</ul>
<p>Family Tables promote the use of standardized components. They
let you represent your actual part inventory in <ptcProduct
conref="..\..\..\conref_pn.dita#pubsTopic-1-A872B923/PTCCreoParametric-E96269BB"
></ptcProduct>. Moreover, families make it easy to interchange parts
and subassemblies in an assembly, because instances from the same
family are automatically interchangeable with each other.</p>
<section><title>Family Table Structure</title><p>Family Tables are
essentially spreadsheets, consisting of columns and rows. They consist
of the following three components:</p><ol>
<li><p>The base object (generic object or generic) on which all members
of the family are based.</p></li>
<li><p>Dimensions and parameters, feature numbers, user-defined feature
names, and assembly member names that are selected to be table-driven
(hereafter referred to as items).</p></li>
<li><p>Names of all family members (instances) created by the table
and the corresponding values for each of the table-driven items.</p
></li><?Pub Caret -2?>
</ol><p>Rows contain instances of parts and their corresponding values;
columns are used for items.</p><p>The column headings include the
instance name, and the names of all of the dimensions, parameters,
features, members, and groups that were selected for the table. Dimensions
are listed by name (for example, <codeph>d9</codeph>) with the associated
symbol name (if any) on the line below it (for example, <codeph>depth</codeph
>). Parameters are listed by name (dim symbol). Features are listed
by feature number (for example <codeph>F107</codeph>) with the associated
feature type (for example [<codeph>cut</codeph>] ) or feature name
on the line below it.</p><p>The generic model is in the first row
in the table. The table entries belonging to the generic can be changed
only by modifying the actual part, suppressing, or resuming features;
you cannot change the generic model by editing its entries in the
Family Tables.</p><note><p>Family Table names are not case-sensitive.
Therefore, any subsequent references to inserted names show them in
uppercase letters.</p></note><p>For each instance, you can define
whether a feature, parameter, or assembly name is used in the instance
either by indicating whether it is present in the instance (<codeph
>Y</codeph> or <codeph>N</codeph>) or by providing a numeric value
(in the case of a dimension). All dimension cells must have a value,
either a number or asterisk (*) to use the generic's value.</p><p
>All aspects of the generic model that are not included in the Family
Table automatically occur in each instance. For example, if the generic
model has a parameter called <codeph>Material</codeph> with a value <codeph
>Steel</codeph>, all instances will have the same parameter and value.</p
><p>You can scroll horizontally through a Family Table to see additional
information. The Instance Name column remains visible as you scroll.</p
><p>Family Table functionality varies with your <ptcProduct
conref="..\..\..\conref_pn.dita#pubsTopic-1-A872B923/PTCCreoParametric-E96269BB"
></ptcProduct> module licenses.</p><table>
<tgroup cols="2"><colspec colname="1" colwidth="27.27*"/><colspec
colname="2" colwidth="72.73*"/>
<thead>
<row>
<entry valign="top"><p>Module</p></entry>
<entry valign="top"><p>Available Family Table Functionality</p></entry>
</row>
</thead>
<tbody>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1"><p>Basic <ptcProduct
conref="..\..\..\conref_pn.dita#pubsTopic-1-A872B923/PTCCreoParametric-E96269BB"
></ptcProduct></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2"><p>Create table-driven
parts by adding dimensions to the Family Table</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1"><p>Assembly</p
></entry>
<entry colname="2" morerows="0" nameend="2" namest="2"><p>Create table-driven
assemblies by adding to the Family Table subassembly and part names,
as well as assembly dimensions.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1"><p>Pro/FEATURE</p
></entry>
<entry colname="2" morerows="0" nameend="2" namest="2"><p>Create table-driven
user-defined groups whose group feature dimensions can be table-driven,
invariable, or variable.</p><p>Add table-driven groups to a part Family
Table.</p></entry>
</row>
</tbody>
</tgroup>
</table></section>
</pubsConbody>
<related-links>
<linklist>
<link format="dita" href="About_Multi-Level_Family_Tables.dita"
scope="local" type="pubsConcept"><linktext>About Multi-Level Family
Tables</linktext></link>
<link format="dita" href="About_User-Defined_Feature_Family_Tables.dita"
scope="local" type="pubsConcept"><linktext>About User-Defined Feature
Family Tables</linktext></link>
<link><linktext>###proe_fund_ten_sub_about_family_tables_1@OnlineHelp###</linktext>
</link>
</linklist>
</related-links>
</pubsConcept>
