We are manufacturers of air movement and conditioning equipment. Our current product coding system is a rather a "descriptive" one. For example, FAN-BKT-MM020 is the code for fan bracket used in MM020 unit. Another example: FSU020-CASE means case for filter supplied unit model 020.
The advantage of this system is that all codes are meaningful. You know what it is as soon as you see it. However, as you can imaging, when you have thousands of products and parts, every time you create a new part you have to scratch your head. Different heads will come up with different way of coding. Some codes may be meaningful to that particular head who created them but totally confusing others....etc
So we come to the stage where we would like to adapt a modern, industry proven coding system.
What system do you use? Could you please shine some light on me? Thanks in advance.
Regards.
ad
Didn't find your answer? Ask the community — no account required.
*
**THE-RFI-EMI-GUY**
Ad; Do what the big boys do. Make up part numbers that mean absolutely nothing at all, change the kits and part numbers every few years so that nobody can figure out that their old stock still fits. If the item has an identifieable part number from an OEM supplier, blot it out, or worse yet make the OEM supplier relabel it and disavow any knowledge of it should a repair person try to get a replacement 5 years down the line. Install a "proprietary" chip in disposable items like batteries or ink cartridges to ensure a steady revenue flow until you decide to obsolete the product by choking off the supply chain. Then while you are at it, make your customers purchase a "service manual" which doesn't provide anything meaningful. Or don't bother at all with a manual, and when they call for help, offer to give them a "trade in" for a brand new overpriced unit.
I h>Hi
product coding system is a rather a "descriptive" one.
Another example: FSU020-CASE means case for filter
is as soon as you see it. However, as you can
new part you have to scratch your head. Different
to that particular head who created them but totally
coding system.
D
DarkMatter
On Fri, 10 Oct 2003 14:36:31 +1000, "ad" Gave us:
product coding system is a rather a "descriptive" one.
Another example: FSU020-CASE means case for filter
is as soon as you see it. However, as you can
new part you have to scratch your head. Different
to that particular head who created them but totally
coding system.
Get an MRP system that allows you to code in your new system, yet retain the former as well. Such as $th Shift. It allows the use of standard application to report on the data from as well, such as excel, etc.
As for as numbering schemas go... There are many. Good luck, and sorry, but that is all I have for you.
D
DarkMatter
On Fri, 10 Oct 2003 01:22:36 -0400, **THE-RFI-EMI-GUY** Gave us:
Top posting, non-contributory, no help trolling.
D
DarkMatter
On Thu, 09 Oct 2003 22:44:36 -0700, DarkMatter Gave us:
Uhhh... That would be "4th Shift".
A
ad
Thanks very much. I might ask you more questions later.
ad
R
Ross Mac
P
Paul Hovnanian P.E.
product coding system is a rather a "descriptive" one.
Another example: FSU020-CASE means case for filter
There's nothing wrong with descriptive part numbers, with a few caveats:
First, come up with a standard scheme for generating the numbers. For example,
Your two examples (above) have one with the product model on the end and the other at the beginning.
Second, consider what would happen if the same part is used in multiple products. The MM020-FAN:BKT001,rev1 might be the same part as an FSU020-MOTOR:BKT001,rev1
I've shown the BKT001,rev1 following a ':' delimiter. Ideally, the BKT001,rev1 would be a unique identifier (although not very descriptive by itself) for that part throughout the company and it would be relatively easy to identify that by what follows the special delimiter. Also, if it becomes necesary to add another field (standardsdo and should change), a new delimiter can be chosen so that the old part number can be deduced from the new part number.
On the other hand, keep the number of special characters within the capabilities of standard bar code character sets, printers, etc.
Parts of increasing rev number should be backwards compatible with older revisions so you'll always know a rev2 will substitute for a rev1.
Don't get stuck with fixed field lengths. You might have more than 999 bracket types, so make sure your numbering scheme will accept BKT1001.
Get input from all concerned parties before setting a standard. It is helpful to have each group put together some 'use cases' describing how they use the part number information. For example, if the stockroom finds that they are out of MM020-FAN:BKT001,rev1, how do they look up FSU020-MOTOR:BKT001,rev1 as an equivalent part?
Consider the effect of giving visibility to your customers (and competitors) this level of parts interchangeability. Your marketing people might want to charge a lot more for the MM020 parts than the FSU020 parts. Just some ideas.
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required
Report Content
You are reporting this content to the moderators. They will look at it
ASAP.