This is the way I wanted to do it. One assy called Model 670 & one assy called Model 678. Parts would have 2 config separate finish properties. However I only want 1 BOM and I don't know how to have separate FINISH columns.Dwight Livingston wrote:
David
The usual ASME-type parts list requires part numbers. Each of the component versions, painted and unpainted, would have it's own number. One assembly would have one of the painted item and none of the chrome, while the other assembly would have none of the painted and one of the chrome, etc. Using configurations, you can drive a SolidWorks BOM to work this way.
This works well, however in PDM it will show up as one assy.Dwight Livingston wrote:
Since you are not doing it this way, I would keep it simple. I would give each component two properties, one called "FINISH (MODEL #670)" and the other called "FINISH (MODEL #678)" or whatever those hard-to-see number are. You can then add columns in the BOM that call on those properties.
So what's the problem there? Other than your BOM looking a certain way, what requirements do you have? You could make assembly and part configurations, but it's a lot of bother. I wouldn't do it without good reason. We are set up so that all our components are documented and when placed in an assembly they show up in the BOM automatically. We don't get much labor saving doing it that way (it's a pain in the butt) compared to just typing up a BOM, but we do get a lot of error reduction. In your case, where you are not tying drawing numbers together, I wouldn't think it was worth it.
This works well, however in PDM it will show up as one assy.
My reason is that I have people looking at the data thru the web portal. I want them to be able to search for Model 670 and get all the data related to this model. Even though all components are the same, the fact that some parts have a different finishes requires different model numbers. I hope this makes sense.Dwight Livingston wrote:
So what's the problem there? Other than your BOM looking a certain way, what requirements do you have? You could make assembly and part configurations, but it's a lot of bother. I wouldn't do it without good reason. We are set up so that all our components are documented and when placed in an assembly they show up in the BOM automatically. We don't get much labor saving doing it that way (it's a pain in the butt) compared to just typing up a BOM, but we do get a lot of error reduction. In your case, where you are not tying drawing numbers together, I wouldn't think it was worth it.
This works well, however in PDM it will show up as one assy.
The usual ASME-type parts list requires part numbers. Each of the component versions, painted and unpainted, would have it's own number. One assembly would have one of the painted item and none of the chrome, while the other assembly would have none of the painted and one of the chrome, etc. Using configurations, you can drive a SolidWorks BOM to work this way.
Since you are not doing it this way, I would keep it simple. I would give each component two properties, one called "FINISH (MODEL #670)" and the other called "FINISH (MODEL #678)" or whatever those hard-to-see number are. You can then add columns in the BOM that call on those properties.