Part Number & Description - How do you do it?
Back in the old days, it seemed we were limited to about 8 charactors for a file of any kind, be it a CAD file or a text document. Most places I worked used the 8 charactor file for the drawing number and on the drawing was the longer name of the part. Upside was that if you had the drawing in hand, you could search for the drawing file on CAD, since it was the same as the drawing number. The downside - the drawing/file number contained almost no description of the part for searching or browsing the directories. Due to a unique number, there were never (almost never) any duplication of parts.
Then I have worked for folks who could have cared less about file conventions and just gave names to part files as Windows software allowed it. Problem was - it became easy to create duplicate files in separate directories or drives.
Sooooo, where are you folks at today with your drawing/file number and description/file names?
Here's a technique I used for one client I had, I used for the file name BOTH a drawing number and description. For example, a file might be called DN0001 - BRACKET, SUPPORT. Rather than have a drawing format with separate drawing number and description location, I combined both. So the above file name- description would be used in that block. The BOM contained the same too.
This approach had two benefits: It prevented duplication via a unique part number within the file name and allowed the part's description to be viewed or searched in a directory.
Worked great. Just like in the old days, I'd have a block of part numbers and my client had a block of part numbers. We could make the description what ever we wanted, but due to the unique part number, there could be no duplication.
How do you handle part/file/descriptions in your applications?
Just courious!
Thanks!
Bill
Back in the old days, it seemed we were limited to about 8 charactors for a file of any kind, be it a CAD file or a text document. Most places I worked used the 8 charactor file for the drawing number and on the drawing was the longer name of the part. Upside was that if you had the drawing in hand, you could search for the drawing file on CAD, since it was the same as the drawing number. The downside - the drawing/file number contained almost no description of the part for searching or browsing the directories. Due to a unique number, there were never (almost never) any duplication of parts.
Then I have worked for folks who could have cared less about file conventions and just gave names to part files as Windows software allowed it. Problem was - it became easy to create duplicate files in separate directories or drives.
Sooooo, where are you folks at today with your drawing/file number and description/file names?
Here's a technique I used for one client I had, I used for the file name BOTH a drawing number and description. For example, a file might be called DN0001 - BRACKET, SUPPORT. Rather than have a drawing format with separate drawing number and description location, I combined both. So the above file name- description would be used in that block. The BOM contained the same too.
This approach had two benefits: It prevented duplication via a unique part number within the file name and allowed the part's description to be viewed or searched in a directory.
Worked great. Just like in the old days, I'd have a block of part numbers and my client had a block of part numbers. We could make the description what ever we wanted, but due to the unique part number, there could be no duplication.
How do you handle part/file/descriptions in your applications?
Just courious!
Thanks!
Bill