-
Website
http://www.solidsmack.com/ -
Original page
http://www.solidsmack.com/solidworks-tip-engineering-design-practices/2008-06-19/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Charles Culp
34 comments · 2 points
-
Brian
51 comments · 9 points
-
MatthewWest
32 comments · 2 points
-
Bruce Buck
72 comments · 6 points
-
Dave Moore
49 comments · 1 points
-
-
Popular Threads
-
Ask The Reader: Are You Upgrading to Windows 7? {Poll}
1 week ago · 21 comments
-
FreshFiber’s 3D Printed iPhone Case Puts the Fancy in Your Pants
1 day ago · 2 comments
-
The Rockin’est LED PocketWatch Mod EVER, Designed With a lil’ SolidWorks
2 days ago · 3 comments
-
Get Into SolidWorks World 2010 for Free. No Beet Throwing Required. #SWW10
4 days ago · 5 comments
-
Two Super Sizzlin’ Ways to Shape… Using SolidWorks Loft to Point
3 days ago · 2 comments
-
Ask The Reader: Are You Upgrading to Windows 7? {Poll}
The next would be DOCUMENTATION!!!! You need to DOCUMENT everything that you've outlined above, so that ANYONE or any new employee can refer to it and see exactly what they're supposed to do.
You're absolutely right about a passionate employee, but unfortunately not everyone is as pumped up as the rabid CAD-masters roaming the office. So on TOP of having documentation, you need to have periodic meetings with EVERYONE involved with the systems. Get their feedback, give training, adjust your procedures/structure as necessary. Many times, as you go along, you'll find that what you thought was a great idea in the beginning, it turning out to be a nightmare and hurt productivity, so you may need to regroup, rethink and adjust your plan of attack to get thing moving along. And even then, you're going to have people who just won't follow the rules and do their own thing. Best you can do is try to work with them, accommodate them, or just send Josh to come whoop them into shape! :)
What I don't like about SolidWorks library hardware is they are still not completely defined once inserted, you need to add a relation to keep them from spinning in place. Our models have a lot of hardware, PEM and Screws, and it's a pain going through all of this. I've submitted this to SolidWorks as an improvement, guess we'll see.
After going through the selection process to get the right model I then have to manually enter information such as Description, Material, Vendor, Part Number, etc...
There is nothing more frustrating than having 10 identical hardware components all named something different.
Why can't this selection information populate the configuration properties of the library model upon creation instead of the user's having to manually re-enter the same information used to select the part.
If you have a team that is new to SolidWorks who have run amok with their part and sub-assembly files (i.e. saving parts and sub-assems in different folders on a server; no libraries used) what's the best way to clean up the mess?
I've become the "computer cad guy" for our university project, and we're all used to pro/e since that's what is normally used through out the ME department here.