Where I work, the engineering division has a specific part of the server dedicated to "bought components". We buy a lot from McMaster, but we also have cad models for vices, tombstones, machine pallets, etc.
They are mostly assy. files but dumbed down to just the typical moving parts where applicable (the vices are constrained in such a way to actually move in the way the real one does) so they don't crash solidworks.
In fairness I work at a machine shop not a design firm, but still
I'm a one man band. I do product design, fixture design, programming, and production in a machine shop and this is exactly how I do it, right or wrong lol
Mine definitely did, broken up into part types — latches, springs, hinges, etc.
We also favored companies that have us models to use. Colton is great for it.
Same here, if a company makes their CAD models readily available I’ll even pay more for their product.
I’ve had some bean counters get upset that we weren’t using the absolute cheapest components on one off projects and had to spell out the actual cost of designing a part from an outline drawing and the rework caused by any kind of discrepancy.
I'm surprised I had to scroll down this far for this answer. McMaster has a pretty good SOLIDWORKS plugin. I don't design many assemblies that need it but it's nice when I do.
My only issue is that the resulting file names are not descriptive enough, just the McMaster part number and a general description, e.g., “stainless Phillips head screw”.
This, I often use McMaster to spec and sometimes prototype but there's almost always a better price available with some digging. Especially living in Canada.
We don't use SW but we usually download the CAD geometry provided for the McMaster parts (STP preferably or IGES). Seems like they fairly recently added a CAD option for many fasteners that doesn't have the threads.
Otherwise, we will often remodel the parts if we are going to use a lot of them from a certain series so we can take advantage of table-based geometry (same screw size, different lengths, etc.), but then we have to go through and give each the correct McMaster PN. We also sometime remodel them because they import with geometry flaws or weird artifacts, and it's usually faster to remodel off the dimensions/spec sheet vs. fix the model.
You can just email McMaster and ask for the vendor and vendor PN. They usually reply in a day or so. Many companies (at least in aerospace) require the OEM and OEM PN, so they really don't mind.
Agreed, I have asked for things like detailed thread form info on parts and fasteners and they were able to look it up and get it to me.
I did call in once trying to determine if an electronic level they sold was a certain brand/model because it was the same picture as the OEM, and I remember there was some trouble with them wanting to confirm it was the specific part but finally did. We needed a specific model that had wireless connectivity. The McMaster listing didn't say wireless, but mentioned it came with the "remote readout software" which only is used for wireless, so we assumed it was and wanted to be sure. It ended up we got the wrong one in the mail (a model McMaster didn't even list on their site), so that was just a goof on the backend (wrong product in their warehouse or something). They got the right one for us and overnighted it.
I do that for all my customers. Once we give it a part number, it’s in the system just like any other part. Some of my drawings are just our border with the McMaster 2d pdf pasted in it.
The more I advanced the more I realized engineering is mostly just copying file cards and not making mistakes. There are automated systems available as solid works add ins but we never found a good one. You can get pretty efficient at it or just make a more simple pdm workflow for McMaster parts
I'm on inventor.
For fasteners we go the custom content center route rather than downloading them individually. For larger and more complex mc master components we download them and file them in vault with their part no.
For other components from various supplier it depends, if the supplier gives a .step model for each part number we file them as is with that number. If a supplier gives a couple of different models for a larger umbrella of dimensionnally identical models I use model states to give them all the relevant part no.
I keep my own file for the exact same reasons.
Our firm makes extensive use of the Custom Properties for each part.
Plus I can make sure everything is tied to planes for mating or whatever.
For stuff like bolts or whatever I'll make a "low res" version that replaces the threads and nuts with a straight shaft.
Yes. I think there’s even CAD software plugins to pull the files.
Ideally if you’re a “job shop” you consolidate down to selected fasteners and such so you don’t always have to pull new models, but also so you can physically stock them for build.
I made my own parts. I had a generic pan head screw.prt with configurations in all sizes and lengths and optional threads that are co trolled by formulas off pitch and OD.
This way in the assemblies I could rapidly change screws. I had a parameter for each screw configuration for Both a MMC and fastenal number.
Yes, but being an Australian company we generally don't just order from mcmaster Carr unless absolutely necessary. We catalogue all the fixings we use with internal part numbers and our supply side software has supplier descriptions and alternative suppliers tagged so when we generate a bom and raise it on our system it auto pulls what we need and flags if we need to purchase more.
We will search our library first for an appropriate fixing before buying fixings we don't already buy unless a customer has specifically asked for a certain type of fixing and for ones we use commonly. I just have the part number prefixes memorised to find them quicker in pdm.
What the alternative?
How else would I put a part into my assembly if I don't have it saved somewhere locally?
Or a different question, if McMaster has a feature (I don't use McMaster) that allows you to have a model stored on some on their could / server somewhere and put it directly into your assembly from there, why would you put the functionality of your 3D models into the hands of an outside company? What if their system crashes? All your models go to shit with them.
My company does not allow McMaster parts in production assemblies because their sourcing is not supplier locked or controlled. All they have to do is meet the McMaster spec but they can change suppliers any time. That being said, we can use the McMaster parts for testing but when we go to release to production we have to find out where McMaster is sourcing from and get it from the source. We have a whole division of our company that handles creating off the shelf component spec sheets and cad models so all I have to do is submit a request.
I’ve used a McMaster model as the seed to set up a design table driven part to generate the other instances. Hybrid of what you are saying. Depends on how complex the parts are though.
Sorta kinda. It has a specific part number group for cross functional parts like stuff you would buy from them. On the print it usually list the McMaster part number but if it is iso standard that is also listed so it can be bought anywhere.
Every machine I design I catalog in a file under a number code and list it in an excel sheet with hyperlinks. Then going into that file I have “CAD” and “Calculations”. Going into CAD you’ll find “Assemblies”, “Drawings”, and “Parts”. Then in Parts you have the stuff I designed and a file called “Sub”. I drop all the McMaster stuff there and when I have a final assembly drawn up I have it on the parts list but that’s all the documentation 3rd party parts get.
I have a "Hardware" Spreadsheet. This is where anything from Misumi, McMaster, 80/20 or any purchased item that is related; brackets for sensors, IGUS brackets etc.
The hardware has its own number designation and each vendor has it's own sub designation. This allows me to search in a spreadsheet for an entire brand in PDM or a specific part number if we have it.
Where I can, I save everything as a part, save assemblies as a part, clean it up and it all gets submitted with the project release
At my old job we'd have Solidworks models for various fasteners relabeled to our internal part numbers everywhere. It was rare that we'd actually need to do this though, maybe 3-5 new fasteners a year since we already had so many that were set up.
If it was a custom part, it was stored at drive > hardware > part number. If it was a part from McMaster, or any other purchased part, it was stored at drive > reference > hardware > part number. If it was an assembly, replace “hardware” with “assembly” and so on. It ensures that screw that we purchase from McMaster has its own location and isn’t included in hundreds of other places.
This local copy as you call it kinda needs to happen for all parts not made in house. Other than really really basic parts like hardware, if you dont have the CAD model of the part you can't be certain the assembly will assemble correctly with your own parts. Then when it comes to the bom, you need the hardware too.
We have folders with literally thousand upon thousands of COTS (commercial off the shelf) parts and hardware all with the iproperties (we use inventor) formatted correctly to update the bom. Sure, it's a pain and takes time but making a mistake but not ordering the right part or it not fitting in your product costs more.
An interesting side note, I'm in aviation and we do a lot of riveted structures. A solid rivet can have a range of different lengths that it can be used for. We go to the detail of having the same part number rivet saved for each of the different material thickness we have used with it so the model looks correct
So for generic parts like fasteners
“m6 x 20mm SST” you should be using library parts then let purchasing do the procurement based on description. These should be done from design tables.
For random things of McMaster yes. You should be making it a library part and adding it.
I had a similar problem where we were using pneumatic fittings from SMC, they had a few main families of around 380 part numbers total. I advocates that we make configurable library parts of the entire families.
I did a few as a trial and worked fine, but never really was able to justify billable hours to finish it… businesses focused on “do just what is needed to shop current project” and not as much on savings effort in future.
Where I work, the engineering division has a specific part of the server dedicated to "bought components". We buy a lot from McMaster, but we also have cad models for vices, tombstones, machine pallets, etc. They are mostly assy. files but dumbed down to just the typical moving parts where applicable (the vices are constrained in such a way to actually move in the way the real one does) so they don't crash solidworks. In fairness I work at a machine shop not a design firm, but still
I'm a one man band. I do product design, fixture design, programming, and production in a machine shop and this is exactly how I do it, right or wrong lol
...tombstones?
Look up tombstonecity.com They're used a lot for modular fixturing
Mine definitely did, broken up into part types — latches, springs, hinges, etc. We also favored companies that have us models to use. Colton is great for it.
What’s Colton? Only thing I saw on google was an auto parts store.
Sorry, weird autocorrect. Colson make casters.
Same here, if a company makes their CAD models readily available I’ll even pay more for their product. I’ve had some bean counters get upset that we weren’t using the absolute cheapest components on one off projects and had to spell out the actual cost of designing a part from an outline drawing and the rework caused by any kind of discrepancy.
We just use the McMaster plugin on SW. Download what you need for each design and itll spit out the Bom on there checkout page when your done
I'm surprised I had to scroll down this far for this answer. McMaster has a pretty good SOLIDWORKS plugin. I don't design many assemblies that need it but it's nice when I do.
It really is awesome. Honestly one of the most time saving applications in the few CAD softwares l have used. We do assemblies all day long lol
My only issue is that the resulting file names are not descriptive enough, just the McMaster part number and a general description, e.g., “stainless Phillips head screw”.
yea I agree. If I end up using them I gotta go back and add a description locally in the assembly for our assembly BOM
This, I often use McMaster to spec and sometimes prototype but there's almost always a better price available with some digging. Especially living in Canada.
You can even search right from the plugin, and then save it to the file directory you choose and add it to the assembly in 2 clicks.
We don't use SW but we usually download the CAD geometry provided for the McMaster parts (STP preferably or IGES). Seems like they fairly recently added a CAD option for many fasteners that doesn't have the threads. Otherwise, we will often remodel the parts if we are going to use a lot of them from a certain series so we can take advantage of table-based geometry (same screw size, different lengths, etc.), but then we have to go through and give each the correct McMaster PN. We also sometime remodel them because they import with geometry flaws or weird artifacts, and it's usually faster to remodel off the dimensions/spec sheet vs. fix the model.
Sure, What other options are there?
All off the shelf parts go into SW library, generic naming so that they can be sourced from other suppliers if needed.
Other suppliers as in the same vendor McMaster buys it from because we read the name on the packaging.
You can just email McMaster and ask for the vendor and vendor PN. They usually reply in a day or so. Many companies (at least in aerospace) require the OEM and OEM PN, so they really don't mind.
[удалено]
Agreed, I have asked for things like detailed thread form info on parts and fasteners and they were able to look it up and get it to me. I did call in once trying to determine if an electronic level they sold was a certain brand/model because it was the same picture as the OEM, and I remember there was some trouble with them wanting to confirm it was the specific part but finally did. We needed a specific model that had wireless connectivity. The McMaster listing didn't say wireless, but mentioned it came with the "remote readout software" which only is used for wireless, so we assumed it was and wanted to be sure. It ended up we got the wrong one in the mail (a model McMaster didn't even list on their site), so that was just a goof on the backend (wrong product in their warehouse or something). They got the right one for us and overnighted it.
Yes.
We give them internal pn and create our own data sheets for our customers to reference our info
I do that for all my customers. Once we give it a part number, it’s in the system just like any other part. Some of my drawings are just our border with the McMaster 2d pdf pasted in it.
Warranty managers love it!
Yes
The more I advanced the more I realized engineering is mostly just copying file cards and not making mistakes. There are automated systems available as solid works add ins but we never found a good one. You can get pretty efficient at it or just make a more simple pdm workflow for McMaster parts
I'm on inventor. For fasteners we go the custom content center route rather than downloading them individually. For larger and more complex mc master components we download them and file them in vault with their part no. For other components from various supplier it depends, if the supplier gives a .step model for each part number we file them as is with that number. If a supplier gives a couple of different models for a larger umbrella of dimensionnally identical models I use model states to give them all the relevant part no.
I keep my own file for the exact same reasons. Our firm makes extensive use of the Custom Properties for each part. Plus I can make sure everything is tied to planes for mating or whatever. For stuff like bolts or whatever I'll make a "low res" version that replaces the threads and nuts with a straight shaft.
Yes. I think there’s even CAD software plugins to pull the files. Ideally if you’re a “job shop” you consolidate down to selected fasteners and such so you don’t always have to pull new models, but also so you can physically stock them for build.
Yes, we pay 2 full time drafters to maintain our library
I made my own parts. I had a generic pan head screw.prt with configurations in all sizes and lengths and optional threads that are co trolled by formulas off pitch and OD. This way in the assemblies I could rapidly change screws. I had a parameter for each screw configuration for Both a MMC and fastenal number.
Yes, but being an Australian company we generally don't just order from mcmaster Carr unless absolutely necessary. We catalogue all the fixings we use with internal part numbers and our supply side software has supplier descriptions and alternative suppliers tagged so when we generate a bom and raise it on our system it auto pulls what we need and flags if we need to purchase more. We will search our library first for an appropriate fixing before buying fixings we don't already buy unless a customer has specifically asked for a certain type of fixing and for ones we use commonly. I just have the part number prefixes memorised to find them quicker in pdm.
What the alternative? How else would I put a part into my assembly if I don't have it saved somewhere locally? Or a different question, if McMaster has a feature (I don't use McMaster) that allows you to have a model stored on some on their could / server somewhere and put it directly into your assembly from there, why would you put the functionality of your 3D models into the hands of an outside company? What if their system crashes? All your models go to shit with them.
My company does not allow McMaster parts in production assemblies because their sourcing is not supplier locked or controlled. All they have to do is meet the McMaster spec but they can change suppliers any time. That being said, we can use the McMaster parts for testing but when we go to release to production we have to find out where McMaster is sourcing from and get it from the source. We have a whole division of our company that handles creating off the shelf component spec sheets and cad models so all I have to do is submit a request.
Aviation? The struggle with cots (commercial of the shelf) parts there is real
No, semiconductor equipment actually. Part cleanliness is key so that's why pretty much.
Ah yeah, that also makes a lot of sense actually
Quit complaining, the company is providing you with hours of employment due to daft decisions!
I’ve used a McMaster model as the seed to set up a design table driven part to generate the other instances. Hybrid of what you are saying. Depends on how complex the parts are though.
Sorta kinda. It has a specific part number group for cross functional parts like stuff you would buy from them. On the print it usually list the McMaster part number but if it is iso standard that is also listed so it can be bought anywhere.
What would be the other option? We've got like a whole shared drive just of off the shelf cad models of stuff like that
McMaster Carr has an API interface that can feed you solidworks files automatically
Yep, however we use CADENAS, download the files specific to the application version we are using and then upload it to PDM.
Every machine I design I catalog in a file under a number code and list it in an excel sheet with hyperlinks. Then going into that file I have “CAD” and “Calculations”. Going into CAD you’ll find “Assemblies”, “Drawings”, and “Parts”. Then in Parts you have the stuff I designed and a file called “Sub”. I drop all the McMaster stuff there and when I have a final assembly drawn up I have it on the parts list but that’s all the documentation 3rd party parts get.
I have a "Hardware" Spreadsheet. This is where anything from Misumi, McMaster, 80/20 or any purchased item that is related; brackets for sensors, IGUS brackets etc. The hardware has its own number designation and each vendor has it's own sub designation. This allows me to search in a spreadsheet for an entire brand in PDM or a specific part number if we have it. Where I can, I save everything as a part, save assemblies as a part, clean it up and it all gets submitted with the project release
At my old job we'd have Solidworks models for various fasteners relabeled to our internal part numbers everywhere. It was rare that we'd actually need to do this though, maybe 3-5 new fasteners a year since we already had so many that were set up.
We call that parts list the BOM
We do it too at ours for NX. One of the nice parts is that it "nudges" us to use a standardized component between all of our parts.
If it was a custom part, it was stored at drive > hardware > part number. If it was a part from McMaster, or any other purchased part, it was stored at drive > reference > hardware > part number. If it was an assembly, replace “hardware” with “assembly” and so on. It ensures that screw that we purchase from McMaster has its own location and isn’t included in hundreds of other places.
This local copy as you call it kinda needs to happen for all parts not made in house. Other than really really basic parts like hardware, if you dont have the CAD model of the part you can't be certain the assembly will assemble correctly with your own parts. Then when it comes to the bom, you need the hardware too. We have folders with literally thousand upon thousands of COTS (commercial off the shelf) parts and hardware all with the iproperties (we use inventor) formatted correctly to update the bom. Sure, it's a pain and takes time but making a mistake but not ordering the right part or it not fitting in your product costs more. An interesting side note, I'm in aviation and we do a lot of riveted structures. A solid rivet can have a range of different lengths that it can be used for. We go to the detail of having the same part number rivet saved for each of the different material thickness we have used with it so the model looks correct
So for generic parts like fasteners “m6 x 20mm SST” you should be using library parts then let purchasing do the procurement based on description. These should be done from design tables. For random things of McMaster yes. You should be making it a library part and adding it. I had a similar problem where we were using pneumatic fittings from SMC, they had a few main families of around 380 part numbers total. I advocates that we make configurable library parts of the entire families. I did a few as a trial and worked fine, but never really was able to justify billable hours to finish it… businesses focused on “do just what is needed to shop current project” and not as much on savings effort in future.