Comments on: Why Smart Numbers are Dumb: SolidWorks Guidelines for File Names

By: skudwoofer

skudwoofer — Wed, 25 Nov 2009 22:19:49 +0000

Dave, are you still at Brammo? I'm on the fence about intelligence in part #s, probably not a good idea IF, read IF you have the means to manage the part #s thru some sort of Database, but if you are managing a project thru lets say excel or windows explorer, it might make more sense, what a coincidence… great discussion, lots of early morning thoughts around this and revision management, whether or not to model top down, bottom up, master sketch… It's like learning to play the guitar well, lots of practice and mistakes.

By: Josh M

Josh M — Fri, 20 Nov 2009 19:40:49 +0000

interesting site, typically part numbers are handled through a PDM system, but I suppose if you don't have one you would need a manual way to number parts. I like the idea you have though… a global sequence.

By: peterb73

peterb73 — Thu, 19 Nov 2009 21:05:41 +0000

In our organization there are certainly people who like smart numbering systems. Those people tend to be the people who "lay hands" on the parts; designers and people on the shop floor spring to mind. Then we've got the folks who never come into contact with a part... just the paper that represents the part. Those folks tend to be more the doc control and purchasing sorts.

We've been using the part-numbering.com service, http://www.part-numbering.com, and we've set up smart part numbers there. But we're using a global sequence for all parts, no matter what number format was use to generate the part number. This seem to be keeping everyone moderately happy... a vast improvement from where we were.

By: Francois

Francois — Tue, 24 Mar 2009 08:23:17 +0000

Hi Devon,

Are those file name generated automatically based on the custom properties of the documents, or you have to do it manually? If they are done automatically could you give me the name of the software used to generate those file names. Because if they use the custom properties of the document to name the files then you do not have to worry about using the file in an other assembly, as you just have to change the custom properties to generate the new name. But this system only works if the file name is generated automatically.

By: chewie

chewie — Thu, 12 Mar 2009 18:02:49 +0000

I agree with Josh when it comes to naming SolidWorks files under directory 0280A001 but how do we add revision number? Will it be all under another directory 0280A001_01 (01 as revision 1) with Part as 0280A001-100_01or the revised file under a new directory Rev-01? Please advise. Thanks

By: Daniel

Daniel — Mon, 07 Jul 2008 04:21:12 +0000

I read similar article also named rt Numbers are Dumb: SolidWorks Guidelines for File Names | SolidSmack – SolidWorks 3D CAD Technology Design Blog, and it was completely different. Personally, I agree with you more, because this article makes a little bit more sense for me

By: Josh

Josh — Fri, 15 Feb 2008 17:37:47 +0000

Hi Bill, file cabinet organization is a nightmare huh. One company I worked with used binders instead. We had shelves of binders. 1 HUGE binder for each projects, (with a smart number of course so you could tell what it was by looking at it.) but then we had to use one part from one binder in another… oh man.

By: Josh

Josh — Fri, 15 Feb 2008 16:37:47 +0000

By: Bill Bredlow

Bill Bredlow — Thu, 14 Feb 2008 19:44:45 +0000

Josh,

I disagree with only on part of your article. Smart numbers did not work well in the days of file cabinets. The countless hours wasted in meetings attemping to define numbering conventions that never worked. Had I only spent those hours sailing!

By: Bill Bredlow

Bill Bredlow — Thu, 14 Feb 2008 18:44:45 +0000

Josh,

By: William Russum

William Russum — Mon, 11 Feb 2008 22:51:24 +0000

I find that in routine daily tasks intelligent part numbers help. I have spent hours locating fasteners at companies which apply random numbers to fasteners.

I have spent too much time locating things like fasteners. If I can save a great amount of time location 30 or 100 fasteners needed for an assembly.

If I need a 10-32 socket head cap screw 5/8″ long in stainless then, I just go to the rack and locate the part number 1032SHC10-SS. 10-32 is size, shc is code for type, 10 is length in 16ths, and -SS is stainless steel.

I have spent hours locating fasteners at companies which apply random numbers to fasteners. Now it only takes minutes.

By: William Russum

William Russum — Mon, 11 Feb 2008 21:51:24 +0000

I find that in routine daily tasks intelligent part numbers help. I have spent hours locating fasteners at companies which apply random numbers to fasteners.

I have spent too much time locating things like fasteners. If I can save a great amount of time location 30 or 100 fasteners needed for an assembly.

If I need a 10-32 socket head cap screw 5/8" long in stainless then, I just go to the rack and locate the part number 1032SHC10-SS. 10-32 is size, shc is code for type, 10 is length in 16ths, and -SS is stainless steel.

I have spent hours locating fasteners at companies which apply random numbers to fasteners. Now it only takes minutes.

By: Don Hindman

Don Hindman — Tue, 05 Feb 2008 17:57:13 +0000

I agree with most of your observations except eliminating the intelligent number altogether. What we did was to create the first part of the number with some important characteristics we know will be static. the balance of the number is used for uniqueness. In our industry no two trailers are alike yet the characteristics are. All we do is set up a set of families with values so the families are corraled. The last 3 digits create a unique number.
As long as the fit form and function are common that new value can be added to the family. If not, then a new family is created. It works and the company I worked for before this one has used it successfully for over ten years.

By: Don Hindman

Don Hindman — Tue, 05 Feb 2008 16:57:13 +0000

By: Josh

Josh — Wed, 30 Jan 2008 12:37:25 +0000

Hey Rollin, when I go over numbering systems with people, it always comes to one deciding factor. where’s the component used. The first thing a lot of people want to do is put location or purpose in a number. suddenly it’s used somewhere else and the number is now useless. it inherently becomes dumb as it’s used for a different situation. Some make a duplicate part with a new number, but that’s just bad practice, in my opinion.

When you’re finding things through a database, it doesn’t matter so much how or where they are stored. Hence vault type systems. In a manual system folders are better and it’s definitely possible to combine the two.

Currently, we store each drawing and it’s native files in their own folder. It was set up like this from the “file cabinet’ mentality even though we find everything through a database search. It does help sort when working with a lot of different customers that you need to send documents to.

Hope you find somethig that works well for your situation.