Hi there,
Our design department is working on process improvements. One areawe are tackling is streamlining our component library withconfigurable parts. Our products are hand-built with pulled parts -each of which has a part number, right down to the last nut, boltand washer. All of the part numbers of these parts are attached tothe part's properties in SWX so that when we produce drawings, theBOM is correctly populated with a part number and description.
Currently, we have a part file for each diameter bolt used on thefloor (3/4", 5/8", 1/2", 1/4", etc.) and then 30 or moreconfigurations of each of those parts with the length of each bolt.Every diameter/length combination has a part number, but those partnumbers are arbitrary - they were assigned in the context of thesystem we use, not the physical realities of the bolt. They neverchange, but there's no way to derive the part number from thephysical characteristics of the bolt.
I'd like to find a way to condense our bolt library into a singlefile, making one smart component that will size itself correctly,and come up with the correct part number as well. I was thinkingthat Derived configurations might do the trick, but I would stillhave a tremendous amount of redundant data to deal with...
Any suggestions?SolidworksConfigurations design Tables
Our design department is working on process improvements. One areawe are tackling is streamlining our component library withconfigurable parts. Our products are hand-built with pulled parts -each of which has a part number, right down to the last nut, boltand washer. All of the part numbers of these parts are attached tothe part's properties in SWX so that when we produce drawings, theBOM is correctly populated with a part number and description.
Currently, we have a part file for each diameter bolt used on thefloor (3/4", 5/8", 1/2", 1/4", etc.) and then 30 or moreconfigurations of each of those parts with the length of each bolt.Every diameter/length combination has a part number, but those partnumbers are arbitrary - they were assigned in the context of thesystem we use, not the physical realities of the bolt. They neverchange, but there's no way to derive the part number from thephysical characteristics of the bolt.
I'd like to find a way to condense our bolt library into a singlefile, making one smart component that will size itself correctly,and come up with the correct part number as well. I was thinkingthat Derived configurations might do the trick, but I would stillhave a tremendous amount of redundant data to deal with...
Any suggestions?SolidworksConfigurations design Tables
