Figuring out a reality-based return on investment for technology is never easy. But, unlike other tools that assist product development, the ROI for simulation is pretty solid. As I’ve written before in a post over at the NAFEMS blog, in general, there are Four ROIs of Simulation. However, for the most part, it is about avoiding multiple rounds of prototyping and testing with hard savings behind it.
As I started developing my plans for the 2013 Simulation Driven Design study, I contemplated the same question for simulation in the concept design phase. The findings came as a bit of a surprise to me. The value from simulation in concept design is markedly different from that in detailed design. That’s what I explain in this post.
Activities Driving Value
Before we jump into the ROI or value proposition, it is important to understand what activities lead to value.
In detailed design, simulations can drive design decisions to refine the sizing of a single existing design. But in concept design, the purpose is to compare and contrast many, sometimes radically, different design ideas. The difference is macro versus micro in scope.
A bigger difference, however, lies in the design constraints themselves. In detailed design, you use simulation to conform to existing requirements. But in concept design, you can actually use simulations as a means to define or shape the constraints.
For detailed designs, because the objective is to refine something that already exists, simulation tools that drive parametric changes are a good fit. These include associativity between CAD and CAE applications, where modifications are made to the 3D model and the simulation model is updated. It also includes parametric sensitivities and optimizations.
The applicable capabilities for concept design, are quite different. With the purpose of exploring many different concepts quickly, unstructured modifications such as direct modeling against 2D and 3D geometry is important. In this case, you don’t want to be constrained by parametric features. Furthermore, technology like topology optimization, which suggests design geometry based on simulations, is a great fit.
Differences in Value
So what is the value for simulation in the concept and detailed design phases? The answer, per the 1,005 respondents from the 2013 Simulation Driven Design study, were very clear.
- The top two business objective for simulation in detailed design was to meet product requirements (76%) and avoid development costs and delays (65%), with everything else below 50%.
- The top business object if for simulation in concept design was to avoid development costs and delays (71%), with everything else below 50%.
And that’s the part that surprised me. You see, I think these responses should be different. Addressing product requirements should be the tip-top objectives of concept design.
Why? It gets back to design constraints. The job during concept design isn’t to conform to to constraints, it is to define them. Avoiding failures is the purpose of simulation the detailed design phase. Trying to shoehorn concept simulation into that job is a lost opportunity to set the development project up for success. This, in turn, should translate into lower product costs, higher product performance and other desirable product traits.
Recap and Questions
- In detailed design, simulations are used to refine an existing design. In concept design, it is used to compare different design concepts.
- Critical capabilities for simulation in detailed design include CAD-CAE associativity and parametric optimizations. Those for simulation in concept design include direct modeling, for 2D and 3D, as well as topology optimization.
- Respondents to the 2013 Simulation Driven Design study cited that meeting product requirements and avoiding development costs and delays as the business objective for simulation in detailed design. For concept design, they cited avoiding development costs and delays as the top priority.
- This last finding is where I object. Simulation in concept design is where design constraints can be defined, not conformed to. The focus should, instead, be on shaping those requirements.
I’m said my piece. Now its your turn. What do you think the objective for simulation driven design in the concept phase should be? Sound off and let us know what you think.
Take care. Talk soon. And thanks for reading.
This blog post has been licensed for hosting by PTC. The concepts, ideas and positions of this post have been developed independently by Industry Analyst Chad Jackson of Lifecycle Insights. 2013-2014 © LC Insights LLC