CE Consultants – Douglas Alexander
Part Numbering Structure Guidelines
Draft: Rev
Date:
Component Engineering
Proposal/Checklist for Part Numbering System
Must be:
1.
Easy to create and easy to maintain
The owner of the part number assignment and upkeep operations must be able to
access, change, delete, or obsolete a number or a description quickly to ensure
that all data circulating through the MRP system is current.
2.
Uniform in construct
Both the part number and the description should have a consistent format such
that the entire database appears as if created by one individual at one point in
time. Therefore the procedure for creating a part number should include:
A.
Standard abbreviations for descriptor place holders
B.
Standard sequence of descriptor place holders grouped by part attributes
C.
Part type major critical parameters to allow for rapid selection of precise
part
3.
Logical
A third party, not previously familiar with the numbering system, should be able
to look at our numbering system and “figure it out” without coaching.
4.
Comprehensive
Every part type existing and potential should be considered when assigning major
class code groupings. This may require an unused block of class codes being held
in reserve until such time as the device type is required. EX. 070- through 079may be designated as a general diode class “block” with subtypes 077 being
LEDs 078,varactors, 079, zener etc. while all the other class codes in the 07X
block are reserved for additional diode subtypes like, switching, rectifiers, etc.
This level of class code granulation allows for both existing and projected part
types and expedites the search process by minimizing the search results list. If the
part type options are anticipated to exceed 10, then a larger block may be held in
reserve or we move to a three digit class code beginning with “1”; allowing for
999 class codes.
5.
Expandable without being excessive in capacity
This applies to the number of placeholders in the part number, which would be
indicative of the number of part types and options anticipated. Every placeholder
is an additional keystroke and another potential for human error. Therefore, the
expandability should be reasonable and allow for anticipated technologies not yet
in play at the company, while maintaining the minimum requirement structure.
CE Consultants – Douglas Alexander
Part Numbering Structure Guidelines
Draft: Rev
Date:
Component Engineering
6.
Accurate
The numbering and descriptor assignments must be true to the manufacturer’s
specifications and double-checked against all AVL references. It is not acceptable
to include a parametric in a description that is not identical to the entire
manufacturers listed in the AVL for the same part number; even though the
parametric may not critical to the current design, it may become a critical
parametric on subsequent designs and therefore may not be a direct sub for the
same parts in the AVL.
7.
Accessible
If an individual, who has not been licensed for an Agile seat, requires the
information, the part number listing should be available in real time either through
a spreadsheet auto update posted on the Intranet or a web-based service that
allows limited access.
8.
Easily searchable
See Item 4. The Agile system allows for custom search macros such that all class
codes are available though drop-down selection boxes so the operator does not
have to type in the part type to begin a search. The Agile administrator should
pre-prepare this search capability so the operator has the most expeditious search
experience. This means other custom pre-prepared searches can be based upon
key words or key fields.
9.
Allow for grouping of part types
The more uniform the assignment methodology, the easier it will be to group part
types together for stockroom binning, kitting, and audit purposes.
10.
Practical with adequate number of place holders to allow for comprehensive
report formatting
The column width of each field will determine how much information can be
placed on standard paper formats. Too many placeholders for either the part
number or the descriptor limits the number of other columns of data that could
“fit” on the report and remain readable; not having to reduce the font size so
significantly, that while all the data may be present, it requires a magnifying aid to
read. When posting to the Intranet, avoiding column wrapping will also avoid
confusion as to what data applies too what column header.