• About
    • Who We Are
    • Partners & Providers
    • News & Events
    • The ESRD Blog
    • Careers
    • Contact Us
  • Applications
    • What We Solve
    • Detailed Stress
    • Composites
    • Fracture Mechanics
    • Residual Stress
    • Sim Apps
  • Products
    • What We Develop
    • StressCheck Professional
      • StressCheck Core
      • Solvers
      • Advanced Modules
      • Utilities
      • Academic Licensing
    • StressCheck Apps
      • CAE Handbook
      • StressCheck Tool Box
    • Product Updates
  • Support
    • How We Can Help
    • Training
    • Webinars
    • Quick Start Guide
    • Help Documentation
    • Software FAQ’s
  • Simulation
    • How We Simulate
    • Benchmarks
    • Simulation Governance
    • History of FEA
    • Dictionary & Terms
  • Resources
    • Browse Our Resource Library
    • White Papers
    • Case Studies
    • Product Demos
    • StressCheck Tutorials
Serving the Numerical Simulation community since 1989
  • Contact Us
  • Register
Login
Forgot Password?
Join Us
ESRDESRD
ESRDESRD
  • About
    • Who We Are
    • Partners & Providers
    • News & Events
    • The ESRD Blog
    • Careers
    • Contact Us
  • Applications
    • What We Solve
    • Detailed Stress
    • Composites
    • Fracture Mechanics
    • Residual Stress
    • Sim Apps
  • Products
    • What We Develop
    • StressCheck Professional
      • StressCheck Core
      • Solvers
      • Advanced Modules
      • Utilities
      • Academic Licensing
    • StressCheck Apps
      • CAE Handbook
      • StressCheck Tool Box
    • Product Updates
  • Support
    • How We Can Help
    • Training
    • Webinars
    • Quick Start Guide
    • Help Documentation
    • Software FAQ’s
  • Simulation
    • How We Simulate
    • Benchmarks
    • Simulation Governance
    • History of FEA
    • Dictionary & Terms
  • Resources
    • Browse Our Resource Library
    • White Papers
    • Case Studies
    • Product Demos
    • StressCheck Tutorials

Variational Crimes and Refloating the Costa Concordia

Home The ESRD BlogVariational Crimes and Refloating the Costa Concordia

Variational Crimes and Refloating the Costa Concordia

March 25, 2025 The ESRD Blog

By Dr. Barna Szabó
Engineering Software Research and Development, Inc.
St. Louis, Missouri USA


In one of my conference presentations, I discussed variational crimes, noting that using point forces and point constraints in finite element analysis serves as examples of such crimes. In the question-and-answer session, I was asked: “If using point constraints is a variational crime, then how is it possible that the structure designed to refloat the Costa Concordia was full of those crimes and yet it worked just fine.” The Costa Concordia was a cruise ship that hit a rock and sank off the coast of Giglio Island in the Mediterranean in January 2012 and was refloated in July 2014. Refloating this vessel, weighing over 114,000 tons, was a major engineering feat. The entire salvage operation cost approximately 2 billion US dollars.

The refloating of the Costa Concordia.

This question presented an opportunity for me to explain that finite element modeling (FEM) and finite element analysis (FEA) are complementary methods when analysts correctly understand their respective domains of application and use them accordingly. However, problems arise when FEM is used outside its scope, which is an all too frequent error.

FEM is an art where engineers are called upon to balance two qualitatively different errors. In contrast, FEA is a scientific method for approximating the solutions of partial differential equations cast in variational form. The objectives and scope of FEM are very different from those of FEA.

The Art of Finite Element Modeling

In the 1950s, engineers began using computers to solve the equations arising from the analysis of structural trusses and frames by the matrix method. This was a great relief from the burden of hand calculations, which were time-consuming and prone to error. By harnessing the power of early computing technology, they could perform complex structural analyses more efficiently and accurately.

In the analysis of trusses and frames, all errors reside in the assumptions incorporated in the classical beam-column theory and the idealizations of the connections between structural elements, which are typically considered either rigid or hinged. The numerical error is just the round-off error which, in the age of computers, is negligibly small. All errors are errors of idealization.

In 1956, it was proposed that matrix methods could be extended to find stress distributions in thin shells, such as the fuselage of an aircraft, and thus the finite element method was born. The idea was that a shell could be divided into smaller, discrete elements connected at nodes. Each element has a stiffness matrix that relates the nodal forces to the nodal displacements. By assembling these element stiffness matrices into a global stiffness matrix, the response of the entire structure can be calculated. This was a significant departure from the naturally discrete systems of trusses and frames. As a consequence, two types of errors occurred: (a) conceptual errors stemming from the use of nodal forces and displacements, and (b) discretization errors arising from the choice of elements and refinement of the finite element mesh.

Confidence in this method greatly increased when it was discovered that the nodal forces acting on any element, or group of elements, calculated from the finite element solution, satisfied the equilibrium equations. However, this is not an indicator of the quality of the finite element solution: It is related to the rank deficiency of the unconstrained stiffness matrices. An explanation is available in reference [1].

It was found that reasonably accurate force-displacement relationships in shells and other continuous structures can be predicted when the elements are suitably defined and the mesh is properly configured. This motivated the development of the legacy finite element modeling codes still widely used to support engineering decision-making processes. The development of those codes started in the mid-1960s when the knowledge base of finite element analysis was a very small fraction of what it is today.

Finite element models are useful for finding load distributions in large structures such as airframes, and the structure fabricated for the refloating of the Costa Concordia. Finite element models are also used when large deformations occur, such as in automotive crash dynamics. The conceptual errors associated with using nodal forces and displacements are compensated for by offsetting approximation errors [1]. This compensation is achieved through artful selection of finite elements from a finite element library and mesh design.

Finite Element Analysis

Finite element analysis has the following objectives:

  1. Given a well-posed mathematical problem in variational form, find an approximate solution such that the error of approximation is minimum in the energy norm. The approximate solution is characterized by a partition of the solution domain into finite elements (the mesh), the polynomial degrees assigned to the elements, and a corresponding set of mapping functions.
  2. Extract the quantities of interest (QoI) from the approximate solution and show that the relative error in the numerically computed QoI is smaller than a prescribed value.

The Differences Between FEM and FEA

The differences between FEM and FEA can be summarized as follows:

  1. Goals: FEM was designed for solving structural problems, such as determining load-displacement relationships, natural frequencies, and buckling loads. On the other hand, FEA focuses on strength-related problems, such as calculating stresses, strains, stress intensity factors, and similar quantities. This involves solving mathematical problems in continuum mechanics, extracting quantities of interest (QoI), and estimating their relative errors.
  2. Existence of an exact solution: In FEA, an exact solution must exist, while in the FEM, an exact solution may not exist—and usually does not. The numerical problem stands on its own. As a consequence, data inadmissible in FEA are admissible in FEM. 
  3. Calibration vs tuning: The material properties and other parameters in the mathematical model and the quantities of interest in FEA are determined by calibration. Calibration is an experimental process in which the loads and corresponding displacements are known, and the values of the parameters are inferred from that information. In contrast, tuning is used in FEM: It is a trial-and-error process by which the properties of the elements and the mesh are adjusted until the observed outcome matches the outcome predicted by the model. It is by artful tuning that errors in discretization offset errors caused by variational crimes. This is why finite element models can still produce useful results even when laden with variational crimes. In many cases, experienced engineers can create reasonably good finite element models, bypassing the trial-and-error process. Some engineering organizations have established rules for the construction of finite element models.
  4. The domain of calibration: The set of intervals on which the model parameters have been calibrated is called the domain of calibration (DoC). A model is considered validated when all parameters are within the DoC [2]. An important objective of model development is to ensure that the DoC is sufficiently large to encompass all intended applications of the model. Tuned finite element models also have an analogous domain, the domain of tuning (DoT), but this domain is not well defined.
  5. Implementation: In FEM, the model definition and polynomial degrees are mixed in large element libraries. Variational crimes, such as reduced integration, are incorporated in some elements. In FEA, on the other hand, the definition of elements is strictly consistent with the formulation, and the model definition is distinct from the polynomial degrees, enabling the construction of sequences of hierarchical models and hierarchical finite element spaces [1]. In other words, the implementation of FEM is element-centric, whereas the implementation of FEA is model-centric.
  6. Solution verification: In FEM, the exact solution is not defined, hence solution verification is not possible. Instead, confidence is gained by tuning and rule-based model construction. By contrast, one of the key objectives of Finite Element Analysis (FEA) is to estimate the relative error in the quantities of interest.
  7. Integration with AI: Artificial intelligence (AI) can assist in navigating the operations of both FEM and FEA. However, FEA is far better suited to support explainable AI (XAI), offering insights into how predictions are made and highlighting caveats to consider.

The Main Points

FEM is not only useful in numerical simulation but also indispensable in certain applications. FEM and FEA are complementary tools: In engineering mechanics, FEM is useful for structural calculations, such as finding the load distribution in statically indeterminate systems, such as airframes and the structure designed to refloat the Costa Concordia, whereas FEA is used for strength, durability and damage tolerance calculations. This distinction is often overlooked, and FEM is used for both structural and strength calculations. The typical consequences are project delays, cost overruns, and increased maintenance costs. See, for example, reference [3].


References

[1] Szabó, B. and Babuška, I. Finite Element Analysis. Method, Verification and Validation. John Wiley & Sons Inc. Hoboken, NJ, 2021.

[2] Szabó, B. and Actis, R. The demarcation problem in the applied sciences.  Computers and Mathematics with Applications. Vol. 162, pp. 206–214, 2024. 

[3] Szabó, B. and Actis, R. Planning for simulation governance and management. Ensuring simulation is an asset, not a liability.  Benchmark, a NAFEMS Publication, July 2021.


Related Blogs:

  • Where Do You Get the Courage to Sign the Blueprint?
  • A Memo from the 5th Century BC
  • Obstacles to Progress
  • Why Finite Element Modeling is Not Numerical Simulation?
  • XAI Will Force Clear Thinking About the Nature of Mathematical Models
  • The Story of the P-version in a Nutshell
  • Why Worry About Singularities?
  • Questions About Singularities
  • A Low-Hanging Fruit: Smart Engineering Simulation Applications
  • The Demarcation Problem in the Engineering Sciences
  • Model Development in the Engineering Sciences
  • Certification by Analysis (CbA) – Are We There Yet?
  • Not All Models Are Wrong
  • Digital Twins
  • Digital Transformation
  • Simulation Governance
  • Variational Crimes
  • The Kuhn Cycle in the Engineering Sciences
  • Finite Element Libraries: Mixing the “What” with the “How”
  • A Critique of the World Wide Failure Exercise
  • Meshless Methods
  • Isogeometric Analysis (IGA)
  • Chaos in the Brickyard Revisited
  • Why Is Solution Verification Necessary?
Tags: Errors of ApproximationFinite Element AnalysisFinite Element ModelingMechanical DesignTechnical Requirements
3

You also might be interested in

Obstacles to Progress
Obstacles to Progress

Obstacles to Progress

Oct 24, 2023

The development of the finite element method (FEM) consists of two main branches: the art of finite element modeling and the science of finite element analysis. Learn why in this blog.

Honored in the Breach

Honored in the Breach

Feb 6, 2026

I am often asked to comment on how it is possible that, although everybody agrees simulation governance is a good idea, it is not being practiced — or, as Shakespeare would put it more elegantly, “more honour’d in the breach than the observance.” — The short answer is that changing minds and habits is hard.  A more detailed explanation follows.

Why Is Solution Verification Necessary?

Why Is Solution Verification Necessary?

Feb 24, 2025

We at ESRD preach and practice solution verification. We believe that reporting data computed by an approximate method is incomplete without providing an estimate of the size of the relative error. This simple and self-evident statement tends to trigger fierce resistance from those who were schooled in the use of legacy finite element modeling tools. But why?

Leave a Reply

We appreciate your feedback!
Cancel Reply

You must be logged in to post a comment.

Looking for Resources?

Interested in a Demo, Evaluation or Purchase?

Have a Software Question, Issue or Feature Request?

Recent News & Events

  • Trustworthiness in Simulation: Credibility or Decision-grade Reliability?
  • Beyond the Black Box: Explainable AI Requires Explainable Simulation
  • Turtle Shells and Legacy Finite Element Codes: Evolutionary Constraints in the Age of Explainable AI

Quick Links

  • Quick Start Guide
  • Documentation
  • Software FAQs
  • Software Demos

Testimonials

  • “Of the three FEA products we use, StressCheck gives me the most confidence when it comes to performing post-processing quality checks on multi-body contact analysis results.  StressCheck has the capability to extract any data of interest and convergence information for that data at any location in the model domain; the other two FEA products do not.  And when it comes to interference fit multi-body contact solutions, I haven’t found any software to outperform StressCheck.”

    In Service Support Center Engineer
    Navy Fleet Readiness Center-East

Testimonials

“A screening of existent commercial and non-commercial tools was carried out in respect to their fracture mechanics capabilities, their design abilities, implementation as well as their complexity. Although, there are many software possibilities, only those within the reach of the author were evaluated. This resulted in the selection of the commercial tool StressCheck. The assessment of crack propagation on compact tension and two stringer specimens governed by the Paris and Forman regimes was satisfactory compared with experimental results using the material data from simple standard specimens.”

Lloren Llopart Prieto (EADS) , Doctoral Thesis, "Modelling and analysis of crack turning on aeronautical structures"

Member Portal

  • Member Registration
  • Member Login

Contact Us

© 2026 · Engineering Software Research & Development, Inc. | Terms & Conditions | Privacy & Cookie Policy | Software License Agreement | Software Maintenance and Technical Support Policy

Prev Next

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits, as outlined in our Cookie Policy. You may adjust your cookie preferences within .

ESRD
Powered by  GDPR Cookie Compliance
Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.

Strictly Necessary Cookies

Strictly Necessary Cookies should be enabled at all times so that we can save your preferences for cookie settings.