Structural modeling software: expressing your needs

We have sought to illustrate the methodology for choosing software for finite element modeling of mechanical structures, by presenting two essential points of view in separate articles:

• expression of need ;

• offer quality and analysis.

The aim is to present the various stages in the process, emphasizing several aspects that are neglected by a purely commercial approach, but in no way to provide infallible recipes. It should be noted that the certifiers of the corporate quality approach have identified numerous shortcomings in the practice of software selection.

This first article deals with the analysis of needs to answer the question: what modeling results are sought by the user? by addressing two complementary points of view.

• When does numerical simulation using finite elements come into play?

  Not all stages in the design cycle or, more generally, in the life cycle of a mechanical component or system, are amenable to numerical simulation using finite elements. In particular, we'll look at the skills required and the considerations that need to be made before implementing such a numerical approach.

  Remember that this simulation brings together a chain of complementary tools: the 3D modeler, mechanical analysis pre-processing, the finite element solver itself, post-processing to format the results, and visualization tools. Here, we will only deal specifically with the part dedicated to calculation: mechanical pre-processing, solver, formatting of results.

• What modeling objectives: from design to research?

  To help the reader analyze his modeling needs and prepare his own specifications, we have chosen to present in general terms the functionalities of finite-element mechanical analysis software, from two angles:

  • the possibilities available for the main fields of application and forms of analysis;

  • sensitive points linked to the way they are implemented in software, as some implementations are not suitable for high-quality industrial use.

  This presentation aims to contribute to :

  • a good reading of the documentation and the preparation of a grid of necessary functionalities;

  • evaluation of the learning effort required.

  To conclude this first article, we'd like to say that the customer needs to be able to step back from fashionable ideas and vocabulary. They must take...