I strongly believe that it is wise to know what you are getting into!
This is why it is worth considering, what is Finite Element Analysis for. Especially when you are new to the field!
To do that let’s go through the basics together!
Finite Element Analysis (FEA) is a tool
FEA is used mostly by engineers to solve engineering problems. As a tool, it helps us to solve problems faster and with less effort. Just as any other tool you need to have practice and experience in using it. At the beginning, it will be frustrating without a doubt, but trust me – there is a great potential ahead just waiting for you!
To discuss these further let’s take a look at what are engineering problems and how they can be solved at all
How engineering problems are solved
Most if not all engineering problems require a model in order to solve them. You simply “model” the reality to see how the object of your interest behaves in certain conditions.
Let’s assume that we want to cross a river. Building a bridge seems reasonable, but it is simpler to cut a tree and simply walk across the river on its trunk. To me, that would be a nice engineering approach. However, that is not all – as an engineer, you will also have to decide how thick tree to cut. Cutting down a smaller tree is less work, but if it breaks you get wet.
And this brings us to who problems in engineering can be solved.
Apart from simply trying (risky, requires all work up front, may fail), you can make a model of our “bridge” and check what will happen. In general, there are 3 models for a problem:
In the physical model, we try to do a test to see what the outcomes would be. Trying our “bridge” over the river would be tricky, but we could make a test on a similar tree on the ground (by putting them on two stones slightly above the ground). This way be can see if a similar tree will hold our weight, and if not we won’t get wet.
This is a nice approach, but it is not perfect. Tests are costly – you had to cut down the second tree just to see if this will work. Usually, one test is much too little… some testing setups go in thousands of samples tested! It also requires a lab to do a test in (nowadays) – a tricky thing to pull off sometimes.
There are good sides to tests as well. I.e. you don’t have to understand something to test it. It’s irrelevant if you know the wood properties, understand the nuance of wood structure and have basic knowledge of static. Just cut the tree and stand on it… the rest will be done by itself!
Note that this absolutely doesn’t mean you don’t have to have specific skills to run tests. Far from it – tests are tricky to do correctly in more advanced problems. This is, however, a completely different topic…
This is a second type of the models for engineering problems. Since tests are expensive and time consuming another way had to be found. That way was in mathematics. By observing the world we can see the rules that govern it. With repeating tests of similar problems we can observe relations between various inputs and the final outcome. This means that we can describe reality in a mathematical way.
Thanks to this model we did not have to cut the “test tree” to be sure that our tree passing will be safe. All we had to do is to learn some design rules and follow them. Mostly this is what codes are for. We saw the relation between various phenomenon and we have described them. Now if you want to design an element you take the code (like Eurocode) and you simply search for mathematic rules that govern this case.
The thing is… those tend to be more and more complicated. We want our outcomes to be more specific, touch the problem with several different disciplines in mind. We want to take into account new factors that we learn about etc.
The mathematical model can always be solved with pencil and paper. But nowadays engineering problems are so complex that often there is not enough paper in the office to solve a problem (not to mention the workload). We analyze more and more complicated problems, and we want the outcomes as fast as possible.
This is why we created the third kind of the model…
With the complexity of math problems calculating everything by hand required enormous effort. But computers came around and they started to do math operations in speed that is currently unmatched. There was a problem, however – we had to describe to the computer what problem do we wish to solve. We have to tell what is the issue, and what outcomes we are interested in.
This is how several approaches to implementing engineering problems were developed. Simply out of the need to show computer what to calculate. Finite Element Method is one of those approaches – currently the most popular one. It allows us to implement the problem as a numerical model, so we don’t have to solve it by ourselves.
Of course such implementing (as any programming in general) is governed by a lot of rules. You need to know what to model and how. Which parts are important, what can be done and what cannot etc. This makes FEA somewhat hard to learn at the beginning – simply because it can be overwhelming at the start. However, if you dig deep enough there is literally no limit to what you can solve with this method 🙂
To sum it up
Knowing that there are 3 models for each problem reason for FEA becomes quite clear. You don’t have to run tests a lot of the times. There is no need for complex mathematics and time-consuming hand calculations. When you implement an engineering problem with Finite Elements computer will solve it for you.
Note however that FEA is not the “ultimate” answer. Each of the models has its uses:
Respect the math!
There is no point in solving something in FEA when you have a simple math rule that gives specific, correct outcome.In such cases modeling is a pure waste of time. Be aware, as this is a very tempting possibility. I suspect that a lot of analysis performed now are completely unnecessary – outcomes could be obtained from simple math rules in a fraction of cost and effort. FEA makes some people lazy – since it can answer almost any engineering question people tend to forget about other models that are available… and often waste time and resources!
Physical tests are needed.
It is really easy to say, that with FEA you don’t need them at all. This is not the case however. Sure, if you want to optimize a structure, than doing a lot of physical tests rarely makes sense. Also if you are doing a model with materials and uses that are well known, FEA is your friend. Be aware however that most of the information you include in FEA (material models / parameters values etc.) are strongly based on physical tests.
You can’t “discover” Young Modulus with FEA – it needs to be tested and then implemented. Also if there is a new phenomenon to be discovered (like bizarre material property in high temperature), FEA is almost defenseless! First you should discover the phenomenon, and then create the model or set of parameters that will make it possible to take that into account in FEA. This means that if you are doing something “new” with new materials or conditions, physical tests most likely will be needed!
Tying it all together makes it perfect!
This is why I think it is worth understanding this. FEA is tricky to use and requires enormous experience. In many cases it is used with physical tests to “calibrate” the model. You make a limited amount of testing and reproduce the tests outcomes with FEA. When everything matches between numerical and physical tests you know that the method you are using works and that the assumptions you made in FEA work properly.
Now instead of making enormous amounts of lab tests you can make additional numerical calculations. Usually numerical models are faster and cheaper than laboratory tests. At that stage (with all the numerical models done) you have so much information, that you can build a mathematical model. This way in future for similar problems you won’t have to do FEA – simple math will do (assuming that simple math model can be made of course). Such use is the power behind understanding what each of the model is for!
Without a doubt, FEA is a great tool and it is very often used nowadays. I’m very fond of this method because the knowledge about it literally changed my career! I foresee that FEA will be even more popular in future until we figure out a different way to model our problems or a completely different approach.
This is a part of our Getting started with FEA course.