EduPuixa
Mechanical
- Apr 18, 2013
- 8
thread559-278946
Greetings everyone in this large and awesome community! I will allow myself and reignite same old topic about part numbering system, their revisions and file naming conventions.
First let me share my insights and pits along the way to where I am now. Five years since graduation I've been working in company which produced Make-to-Order parts, assemblies and machines. When I started there they already have used solidworks, but it was a mess in their file management - many folders with similar projects, parts named just how they look (bracket, hook, bracket1, etc.). If the project evolved you had, lets say, Folder-A and Folder-B (Folder-B is more upgraded product with more parts, more corrections, more fixes that didn't work on project before). In many times you can find Bracket1 in both folders but they look completely different. In times I needed to compare newest (current) model with one of previous versions, but with same file-names and lots of conflicts it wasn't possible. Unless I saved both assemblies as parts and then compared them.
One negative thing I would like to pint-out about small start-up companies (OK, maybe not the ones which start completely from zero, but ones who star using CAD to increase productivity) when you show them what you can do and how easier it is for manufacturing department afterwards, they just load you with work and you don't have tome to think-through, develop and implement good file management system in the beginning!
At least it's what happened to me and I had to design my system along the way, between modelling and detailing stuff for our production facility. From the start I new we needed part numbers to distinguish many parts that already existed and many,many more that would come. Only thing I new about part numbering was what I had learned in university - unfortunately it was significant numbering system. I started with it. It looked something like (AA.BB.CC.DDDD where AA-project, BB-main assembly, CC-subassembly, DDDD-Part) and for many projects it worked rally well. (Oh, at that time I didn't use revisions) Until I wanted to reuse already created parts on other projects. Then I realised I needed system that doesn't tie one part to one specific assembly in one specific project. And of course same thing goes for assemblies and sub-assemblies.
I thought about it a little (at least as long as I had time before I got next project forced forward) And with next project all my parts and assemblies started from C000001 and up. Don't ask why I put "C" in front of my P/N, I guess it's because company I worked in started with that letter.
Again, for some time and many projects this was great system - I could easily move parts and assemblies from one project to another with no problems what so ever. (Still no revisions used) But then one day I decided I want to see what changes I had made over the time our products developed. Also I wanted/needed to use configurations for mirror parts or tabulated parts and I needed to update my system. At that time I "improved" my P/N to something like this C000001AA[A], where C000001 - document number, AA - tab for mirror parts/tabulated parts, [A]-revision. It worked somewhat well, but the P/N length was changing - C000001 for simple part/assy with no revision, +AA/AB/AC/... if tabulated part with multiple configurations, +[A]//... if I revised the part/assy. Now it was workable, but kind a messy, and with weldments it was even more frustrating. And if you have tabulated part and need to revise only one configuration you have to bump-up rev for all configs or do some weird stuff which involves new configurations.
It was my worst decision But then I left that company.
For some time now I am working in different company. Up till now they only have had some hand-made sketches for production - no real drawings, no CAD. And heads of this company understand the importance of strong foundations for file management. So I took my time to get some more insight and upgrade my previous system before I start making drawings for production. Here are set of my requirements that I could think of:
[ul]
[li]P/N stays constant length;[/li]
[li]I can use configurations to create tabulated parts / multi-body parts / mirrored parts in single part file[/li]
[li]I can use revisions and compare / simultaneously open current rev and one of previous revs.[/li]
[/ul]
For the moment I have come up with following code: A-000000-122-B3 (dashes only for clarity)
[ul]
[li]A - Part group (F-fabricated, M-modified, P-purchased);[/li]
[li]000000 - Sequential number;[/li]
[li]122 - Tab (1XX-reserved for mirror parts, X22-reserved for tabulated parts)[/li]
[li]B3 - revision (B-major=part/assy, 3-minor=drawing only)[/li]
[/ul]
Part number is A-000000-122 and revision is only used in file name so I can open historical versions alongside current versions if need be. I also know that this kind a hybrid system, cause it has some intelligence in it, but it's so tiny that if it is ignored it won't make a difference (except for "A" - part groups).
As for revisions "B3" numerical bit (3) changes if I have to update only drawing (missing dimensions, additional dims, notes, etc. Alphabetic bit "B" bumps-up with some changes in part file itself. In this case I create new files (part/drawing/DXF/PDF) but P/N remains the same, only revs are bumped. I know this is not the best practice towards Form, Function, Fit. But I decided I could go this way if I have to make insignificant changes that doesn't compromise interchangeability both upstream and downstream.
For example, let's say I have a right angle reinforcement rib laser-cut from sheet metal P/N F-002598-001 (file name F-002598-000-A0) [dashes for clarity reasons only]. It has right angle corner chamfered to 10x45deg. to accommodate for welding seam (no grinding required from welder, just put and weld in place). After first prototypes we decide to decrease this chamfer to 6x45deg. In this case I'm going to bump major rev, new P/N F-002598-001 stays the same, but file name F-002598-000-B0 changes. In case I have to make a hole in this part or other feature I'm going to crate new file with new part number P/N F-002599-001 (file name F-002599-000-A0.
For the moment this approach looks kind a neat for me, cause if we have one project with many iterations over time it is possible to access all these variations and changes at any time and not only in PDF format but in SW native format and there is no risk of conflict between them when opening newer one and older one at the same time. And if a new customer places order that is more similar to base project than its last iteration, I can easily start from that in different direction. Also I don't have PDM system available and I plan to make a partslist and ECOs list in excel spreadsheet, at least for time being.
Would love to hear some thoughts about my ideas! Any questions and suggestions are welcomed as well!
Cheers, J.Sinkevics
Greetings everyone in this large and awesome community! I will allow myself and reignite same old topic about part numbering system, their revisions and file naming conventions.
First let me share my insights and pits along the way to where I am now. Five years since graduation I've been working in company which produced Make-to-Order parts, assemblies and machines. When I started there they already have used solidworks, but it was a mess in their file management - many folders with similar projects, parts named just how they look (bracket, hook, bracket1, etc.). If the project evolved you had, lets say, Folder-A and Folder-B (Folder-B is more upgraded product with more parts, more corrections, more fixes that didn't work on project before). In many times you can find Bracket1 in both folders but they look completely different. In times I needed to compare newest (current) model with one of previous versions, but with same file-names and lots of conflicts it wasn't possible. Unless I saved both assemblies as parts and then compared them.
One negative thing I would like to pint-out about small start-up companies (OK, maybe not the ones which start completely from zero, but ones who star using CAD to increase productivity) when you show them what you can do and how easier it is for manufacturing department afterwards, they just load you with work and you don't have tome to think-through, develop and implement good file management system in the beginning!
At least it's what happened to me and I had to design my system along the way, between modelling and detailing stuff for our production facility. From the start I new we needed part numbers to distinguish many parts that already existed and many,many more that would come. Only thing I new about part numbering was what I had learned in university - unfortunately it was significant numbering system. I started with it. It looked something like (AA.BB.CC.DDDD where AA-project, BB-main assembly, CC-subassembly, DDDD-Part) and for many projects it worked rally well. (Oh, at that time I didn't use revisions) Until I wanted to reuse already created parts on other projects. Then I realised I needed system that doesn't tie one part to one specific assembly in one specific project. And of course same thing goes for assemblies and sub-assemblies.
I thought about it a little (at least as long as I had time before I got next project forced forward) And with next project all my parts and assemblies started from C000001 and up. Don't ask why I put "C" in front of my P/N, I guess it's because company I worked in started with that letter.
Again, for some time and many projects this was great system - I could easily move parts and assemblies from one project to another with no problems what so ever. (Still no revisions used) But then one day I decided I want to see what changes I had made over the time our products developed. Also I wanted/needed to use configurations for mirror parts or tabulated parts and I needed to update my system. At that time I "improved" my P/N to something like this C000001AA[A], where C000001 - document number, AA - tab for mirror parts/tabulated parts, [A]-revision. It worked somewhat well, but the P/N length was changing - C000001 for simple part/assy with no revision, +AA/AB/AC/... if tabulated part with multiple configurations, +[A]//... if I revised the part/assy. Now it was workable, but kind a messy, and with weldments it was even more frustrating. And if you have tabulated part and need to revise only one configuration you have to bump-up rev for all configs or do some weird stuff which involves new configurations.
It was my worst decision But then I left that company.
For some time now I am working in different company. Up till now they only have had some hand-made sketches for production - no real drawings, no CAD. And heads of this company understand the importance of strong foundations for file management. So I took my time to get some more insight and upgrade my previous system before I start making drawings for production. Here are set of my requirements that I could think of:
[ul]
[li]P/N stays constant length;[/li]
[li]I can use configurations to create tabulated parts / multi-body parts / mirrored parts in single part file[/li]
[li]I can use revisions and compare / simultaneously open current rev and one of previous revs.[/li]
[/ul]
For the moment I have come up with following code: A-000000-122-B3 (dashes only for clarity)
[ul]
[li]A - Part group (F-fabricated, M-modified, P-purchased);[/li]
[li]000000 - Sequential number;[/li]
[li]122 - Tab (1XX-reserved for mirror parts, X22-reserved for tabulated parts)[/li]
[li]B3 - revision (B-major=part/assy, 3-minor=drawing only)[/li]
[/ul]
Part number is A-000000-122 and revision is only used in file name so I can open historical versions alongside current versions if need be. I also know that this kind a hybrid system, cause it has some intelligence in it, but it's so tiny that if it is ignored it won't make a difference (except for "A" - part groups).
As for revisions "B3" numerical bit (3) changes if I have to update only drawing (missing dimensions, additional dims, notes, etc. Alphabetic bit "B" bumps-up with some changes in part file itself. In this case I create new files (part/drawing/DXF/PDF) but P/N remains the same, only revs are bumped. I know this is not the best practice towards Form, Function, Fit. But I decided I could go this way if I have to make insignificant changes that doesn't compromise interchangeability both upstream and downstream.
For example, let's say I have a right angle reinforcement rib laser-cut from sheet metal P/N F-002598-001 (file name F-002598-000-A0) [dashes for clarity reasons only]. It has right angle corner chamfered to 10x45deg. to accommodate for welding seam (no grinding required from welder, just put and weld in place). After first prototypes we decide to decrease this chamfer to 6x45deg. In this case I'm going to bump major rev, new P/N F-002598-001 stays the same, but file name F-002598-000-B0 changes. In case I have to make a hole in this part or other feature I'm going to crate new file with new part number P/N F-002599-001 (file name F-002599-000-A0.
For the moment this approach looks kind a neat for me, cause if we have one project with many iterations over time it is possible to access all these variations and changes at any time and not only in PDF format but in SW native format and there is no risk of conflict between them when opening newer one and older one at the same time. And if a new customer places order that is more similar to base project than its last iteration, I can easily start from that in different direction. Also I don't have PDM system available and I plan to make a partslist and ECOs list in excel spreadsheet, at least for time being.
Would love to hear some thoughts about my ideas! Any questions and suggestions are welcomed as well!
Cheers, J.Sinkevics