# 6 things all engineers should know before using FEA6 things all engineers should know before using FEA

December 18, 2000

Engineers in every industry are integrating finite element analysis (FEA) into the design cycle to ensure that their products are safe, cost-effective, and fast to market. But, analysis is not as simple as putting a CAD model into any FEA package.

There are more software options today than ever before. For many years, engineers were limited to using linear static stress analysis. More recently, finite element packages have been extended to include nonlinear static stress, dynamic stress (vibration), fluid flow, heat transfer, electrostatic, and FEA-based stress and motion analysis capabilities. These capabilities are frequently combined to perform analyses that consider multiple physical phenomena, and are tightly integrated within a CAD interface.

This article will briefly discuss some FEA basics and then outline what engineers need to know when they decide to use FEA.

1. FEA basics. A finite element model is a discrete representation of the continuous, physical part being analyzed. This representation is created using nodes, which are connected together to form elements. The nodes are the discrete points on the physical part where the analysis will predict the response of the part due to applied loading. This response is defined in terms of nodal degrees of freedom (DOF). For stress analysis, up to six degrees of freedom are possible at each node (three components of translation and three components of rotation), depending on the element type selected (e.g., beam, plate, 2D, and 3D elements).

The grid of connecting elements at common nodes comprises the mesh. When adjacent elements share nodes, the displacement field is continuous across the shared element boundary and loads can be transferred between the elements.

2. Design criteria. In any analysis, an engineer first needs to determine the significant physical phenomena and environmental conditions to which the part will be exposed, and also the desired design objective. For example, one of the most common concerns for engineers involves maximizing the part's durability.

The first step in an analysis is to determine whether the design will be subject to static or dynamic conditions. In its real-world application, is the part fixed in space, subject to vibration, or does it move relative to other parts in the assembly? What happens when you run the entire product through its motion cycle? For years, engineers faced with expensive computing resources have simplified the problem by using static FEA software to calculate stresses at a single instant in time. This method works only if the design does not experience impact, motion, or changes in applied loads over time.

3. Multiphysics. In addition to considering a part's ability to withstand mechanical stresses, FEA software often enables engineers to predict other real-world stresses, such as: the effects of extreme temperatures or temperature change (heat transfer analysis), the flow of fluids through and around objects (fluid flow analysis), or voltage distributions over the surface or throughout the volume of an object (electrostatic analysis).

Often these effects work in unison, so it is important that the FEA program can consider their effects on one another. For instance, a computer chip may be heating up over time, cooled down by airflow from a fan, vibrated against other parts, and electrically charged. A typical approach might be to isolate and calculate each variable, then feed the results into the FEA program one at a time. Yet each variable could also affect all the others, so either a coupled analysis or tools for relating results is often necessary.

4. Motion simulation. With today's cheaper, faster computers, a growing trend in FEA is the simulation of large-scale motion using finite element models. In the past, the design process demanded specialists who could build models for different uses: design, machining, or analysis. But with more computing power at their fingertips, today's engineers can use the same model for all three demands, and even perform a motion analysis from their desktops. There are three common methods:

Motion Load Transfer requires engineers to use two applications: a kinematics package is used to obtain approximate loads, which are then input to an FEA program for analysis. This approach does not simulate the motion of a finite element model, just many approximate static points. It's faster than calculating stresses by hand, but it uses a rigid-body motion program, so the engineer must accept certain assumptions. For instance, parts like gaskets are flexible, but a rigid-body program can't calculate that.

The Explicit Timestep Method does simulate a model's actual motion, using a huge number of short time intervals. It determines a solution by "marching" along in time, extrapolating from the solution of the prior timestep. This method is fast for a given time interval, but it can take too long for an entire scenario. For example, if you're simulating a car crashing into a telephone pole, it would be impractical with this approach to consider more than the actual moment of impact.

The Implicit Timestep Method and automatic timestepping scheme of FEA-based stress and motion analysis allows for the simulation of a model's motion cycle by running at larger timesteps for periods of relative inactivity, such as a constant acceleration or deceleration, and then automatically reduces the timestep size to capture periods of critical activity, like surface-to-surface contact, local buckling, or impact. Therefore, an accurate solution for the motion, deformation and stresses of a part becomes practical. However, as always, there's some tradeoff of speed for accuracy-since this approach calculates results for every point in time.

5. Modeling. After determining the type of analysis required and the characteristics of the operating environment, the engineer must produce a finite element model with appropriate analysis parameters, such as loads, constraints, and a suitable mesh. The three available methods of CAD/FEA interoperability can vary widely in terms of ease-of-use, accuracy, and functionality:

The CAD universal file format method requires an engineer to export the CAD solid model to a neutral file format, such as IGES, ACIS or Parasolid, and then import the neutral file into the FEA system for setup and analysis. Although this method usually enables engineers to take full advantage of an FEA program, it can also result in the loss of CAD geometry data as the model is translated. So it's not an ideal method, since it sometimes involves using a simplified version of the problem.

The "one window" CAD/FEA method requires no file translation, since the FEA vendor builds analysis capabilities into a CAD solid modeler. Users choose this option for its ease-of-use, as they can access FEA capabilities from a pull-down menu in a single application. However, FEA providers often simplify their one-window versions due to space and interface limitations. In addition, it can also be limited since FEA companies must tailor their product to each CAD vendor's software in order to integrate the two products. So this CAD/FEA interoperability method may require the engineer to purchase and learn other software if he or she is working in a multi-CAD environment or with moderate to advanced analysis capabilities.

The "one window away" CAD/FEA method also requires no file translation, but it has the additional abilities to perform FEA analysis on a different computer from the CAD solid modeler, and to use a single interface for multiple CAD packages. The primary difference is that the FEA runs in a separate application, so an FEA vendor can supply a more complete version (such as including more element types, meshing, and analysis options) without requiring the need for other analysis software. One possible drawback to this approach is that the engineer must learn both the CAD and FEA software.

6. Results interpretation. Once an engineer gets analysis results, he or she inevitably asks, "How do I know my answers are correct?" So FEA software must provide result verification or validation tools. Ideally, these tools would not only include displacement, stress, or other result contours, but also precision contours that provide qualitative and quantitative verification.

Often, the analysis and modeling choices that an engineer makes will determine how easy it is to interpret results. For example, if a linear static stress analysis was performed, only contours at a single instant in time will be available. The stresses displayed will need to be interpreted in some way, such as comparing the values to the yield stress of the material used in the analysis. In addition, the engineer has assumed that the one instant analyzed in the linear static stress analysis represents the worst case scenario.

If, on the other hand, an FEA-based stress and motion analysis was performed on a solid assembly, interpreting the results will be much easier because the model can be seen to move, flex, bend, and even break over time. These time-dependent results can be recorded in an animation file, such as the Windows .avi format.

In addition to animation capabilities, engineers should expect the FEA software to have a fast, easy-to-use visualization tool for reviewing and presenting results for all analysis types with other integrated presentation options, such as automatic options to generate image files of result contours and plots, VRML files, and HTML reports. These tools can be used to prepare a presentation of results to other engineers and even managers and clients.

Carefully considering the analysis, modeling and results interpretation issues discussed here will help engineers to present their designs with more confidence in the validity of their FEA results.

About Bob Williams

Bob Williams is the Product Development Coordinator of Algor Inc., a maker of FEA and FEA-based stress and motion analysis software for mechanical engineers. He holds a bachelor's degree in mechanical engineering from Youngstown State University in Ohio. He previously worked within the Application Engineering department at Algor, which provides technical support and training for Algor's 20,000 customers in 60 countries, and quality assurance testing for all Algor products.

## About the Author(s)

You May Also Like