Scott Perman

Your Workflow Sucks

Discussion created by Scott Perman on Jan 9, 2020
Latest reply on Apr 15, 2020 by Dennis Dohogne

I've been working in Cad software since the mid 90's.  First it was 2D ACAD, Ideas then NX.  I started using solidworks in 2016, and became active on these forums in early 2019 (when SW2019 gave me lots of free time while it was busy.)  


In my time on these forums, I've seen numerous references that people's problems are caused by their workflow.  In the past I've taken those comments as "you don't know how to use CAD software.  Your problems are all your own creation."  As of today, I've changed my opinion.  Whether intended that way or not, I know interpret those comments as "Solidworks is a little finicky.  [I'll avoid using the b word for now.]  If you want to have success with this software, you should follow this recipe that experienced users have learned to be the most productive."


Here is an example of what I face on a regular basis.  Last time I opened this model, the crossbar was above the machine where it belonged, and the history tree had no warnings or errors.  The next time I open the assembly, one of the actuators has flipped, causing all sorts of issues.  I fixed it once, saved everything, closed out of SW.  The next time I opened the assembly it had similar issues.



I still don't understand why the software can't handle this, but it's time to quit wishing SW was something it isn't, and quit wasting time doing things in a manner that SW doesn't like.  So I'm headed to my alcove to let the assimilation begin.  (Resistance truly is futile.)


I'm curious to see how SSP gets implemented to meet my needs.  My assemblies are typically multiple layers deep, with some sub assemblies flexible, and most having multiple configurations.  It amazes me that the software can keep the relations straight between all the different part and assembly files (at least that is my rudimentary understanding of SSP) but it can't deal with complicated assembly constraints.  I do my best to have parts exist independently on their own.  As finicky as SW is in certain area, this sure seems like a recipe for disaster, but apparently not.      


NX (at least as I was taught) had a similar workflow, but it was all driven by coordinate systems, not sketches.  CS are extremely powerful as implemented in NX. (I think this functionality was added to UG when it merged with IDEAS.  The CS driven methodology existed in IDEAS as well.) 


Consider yourself warned.  Expect a lot of questions from me about SSP, along with the appropriate amount of bitching about the things I don't like.