A series of parts may perform the same general function. They share
the same architecture and may share many components in common. The family
cannot be cited in a BOM as a subcomponent because the family members,
though similar, do not provide the same form, fit and function.
Example Part Families
- Company A makes turbine assemblies for an engine product line. The turbines
are very similar in design and share many parts. The family of assemblies
is managed as a group. BOM operations are performed on the whole group
at one time.
- Company B makes connectors that share architecture, components etc.
but have different form, fit and function.
Sequence Patterns
In creating a part family, you can specify a sequence pattern to use
in naming parts in that family. This establishes the length and number
of padding zeros for the next number generated for the part's name. The
format should mimic the sequence defined in the governing policy, and
must end with three periods. The numbering always starts at 1. For example,
if the governing policy sequence pattern is 1,2,3,... then a specified
sequence pattern of 0000 yields part numbers with 0001, 0002, 0003, etc.
Some examples:
Sequence Pattern |
Part Numbers Generated |
0000 |
0001,0002,0003... |
0010 |
0011,0012,0013...0020,0021... |
00B0 |
00B1,00B2,00B3...0010,0011,0012... |
B1 |
B1,B2,B3...10,11,12,13... |
0B505 |
0B501,0B502,...0B100,0B101,...01000,01001... |
Alpha characters can be used in a sequence pattern, but it is not
recommended. The alpha character is replaced with a number when the sequence
is incremented past the place value of the character. For example, if
the B is in the hundredths place, it would be replaced by 1 when the
sequence goes past 100.
Other options for naming parts include adding a suffix, prefix or
base setting.
|