An FEA result that has not been validated is a number. It may be accurate, or it may be wrong by a factor of two, or it may be capturing the wrong failure mode entirely. Without validation, the engineer has no basis for knowing which of these is true. The model ran. The solver converged. The stress map looks reasonable. None of these facts confirm that the result is correct.
Validation is what separates a credible analysis from an exercise in sophisticated guesswork. It is the process of confirming that the FEA model represents the physical system it is intended to represent, with a quantified level of confidence appropriate to the consequence of being wrong. For a concept design optimization, a modest confidence level may be adequate. For a pressure vessel that will operate near a nuclear reactor, or a structural implant that will be inside a human body for thirty years, the validation standard is considerably more demanding.
This article covers the complete FEA validation framework: the formal distinction between verification and validation, the hierarchy of validation methods from basic sanity checks through full experimental correlation, the error metrics that quantify how well FEA matches test data, the specific validation requirements in regulated industries, and the practical V&V documentation framework that supports both engineering defense and regulatory submission.
Verification vs Validation: The Distinction Every FEA Engineer Must Own
The terms verification and validation are routinely conflated in engineering practice, even by experienced analysts. They are not synonyms. They answer different questions, they require different methods, and responsibility for each falls on different parties. Confusing them produces validation plans that verify the wrong things and leave critical questions about model accuracy unanswered.
The definitions from ASME V&V 10-2006, the primary standard for verification and validation in computational solid mechanics, are the clearest and most widely cited:
Verification: the process of determining that a computational model accurately represents the underlying mathematical model and its solution. Verification asks: are we solving the equations correctly? It is concerned with numerical accuracy, mathematical correctness, and the absence of coding or implementation errors in the solver and the model.
Validation: the process of determining the degree to which a model is an accurate representation of the real world from the perspective of the intended uses of the model. Validation asks: are we solving the correct equations? It is concerned with whether the physics represented in the mathematical model accurately captures the physical behavior of the real system.
The critical implication of this distinction is that verification is largely the software developer’s responsibility, while validation is the analyst’s responsibility on every analysis. When you use Ansys, Abaqus, Nastran, or any other commercial FEA solver, you inherit the solver verification that the software vendor has performed. You do not re-verify the solver from first principles. What you must do, on every analysis, is validate your model of the specific physical system you are analyzing.
Solution Verification: The Analyst’s Verification Responsibility
While code-level verification is the software vendor’s domain, solution verification is the analyst’s responsibility. Solution verification confirms that the numerical solution computed by the solver is sufficiently accurate for the mathematical model that was formulated. The primary tool for solution verification is the mesh convergence study covered in the previous article in this series: demonstrating that the discretization (mesh) is fine enough that further refinement does not change the result meaningfully.
Solution verification also includes checking the patch test for the element types used. The patch test is the fundamental test of whether a finite element formulation can exactly reproduce a state of constant stress. Any element formulation that fails the patch test is mathematically deficient and should not be used. Commercial software elements are tested for patch test compliance during development, but analysts working with custom elements or unconventional formulations must verify patch test performance before relying on the results.
| What is the difference between FEA verification and validation? Verification confirms that the numerical solver correctly implements the mathematical model (solving the equations correctly). Validation confirms that the mathematical model represents the physical system accurately (solving the correct equations). In practice: the software vendor is responsible for code verification; the analyst is responsible for solution verification (mesh convergence) and model validation (comparison to analytical solutions or experimental data) on every analysis. |
The Validation Hierarchy: Ten Methods from Least to Most Rigorous
FEA validation is not a single activity but a spectrum of methods with different costs, confidence levels, and applicability. The appropriate method for any given analysis depends on the consequence of error, the available resources, and the regulatory context. Every analyst should understand all ten methods and know when to apply each.
| Validation Method | When to Apply | Cost/Effort | Confidence Level | Limitations | Regulatory Acceptance |
| Analytical solution comparison | Always – for simplified models matching real physics | Low – analytical derivation only | High for matched cases | Limited to simple geometry and loading | Universal – highest credibility |
| NAFEMS benchmark comparison | Software selection and new problem types | Low – run benchmark models | High for matched benchmark | Only validates solver capability not model | Universal – well-documented benchmarks |
| Mesh convergence study | Every analysis with stress gradients | Medium – multiple mesh runs | High – demonstrates numerical convergence | Confirms numerical accuracy, not physics accuracy | Universal – required by most codes |
| Symmetry and equilibrium checks | Every analysis – basic sanity check | Very low – post-processing only | Medium – eliminates gross errors | Does not confirm stress magnitude accuracy | Universal – expected as minimum due diligence |
| Sensitivity analysis | Complex models with uncertain inputs | Medium – multiple parameter runs | Medium – shows influence of uncertainty | Does not confirm accuracy, only influence | Growing acceptance in FDA, EU MDR submissions |
| Classical mechanics cross-check | Simple structural cases | Low – hand calculation | High if problem is well-matched | Approximate for complex geometry | Universal – engineers must be able to sanity-check |
| Physical test correlation | High-consequence, regulated applications | High – test setup, instrumentation, specimen costs | Very high if properly correlated | Expensive; test conditions must closely match model | Required by FDA, FAA, ASME, NRC for safety-critical |
| Strain gauge correlation | Structural stress validation | High – instrumented test article | Very high for measured locations | Only validates accessible surface locations | Required by ASME Sec VIII Div 2 for pressure vessels |
| Digital image correlation (DIC) | Full-field surface strain validation | High – optical setup required | Extremely high – full field data | Surface only; no internal strain | Accepted by FDA, aerospace certification bodies |
| Historical data and expert review | All analyses lacking better alternatives | Very low – engineering time only | Low-Medium – subjective | No quantitative error bound | Minimum acceptable for non-safety-critical work |
The methods in this table are ordered from least rigorous (historical data and expert review) to most rigorous (physical test correlation with DIC). More rigorous is not always better: the appropriate validation level is the minimum that provides adequate confidence for the engineering decision being supported, given the consequences of error. Applying full physical test correlation to a bracket supporting a light fixture is over-engineering the validation. Applying only historical data review to a pressure vessel component near a nuclear reactor is under-engineering it.
Level 1 Validation: Sanity Checks That Every Analysis Must Pass
The first level of FEA validation requires no test data, no benchmark comparisons, and no additional computational work. It uses the analysis results themselves, combined with basic engineering knowledge, to confirm that the model has not produced results that are physically impossible or obviously incorrect. These checks catch gross errors that would otherwise propagate forward into a credible-looking but fundamentally wrong analysis.
Equilibrium Check: Does the Model Sum Forces and Moments Correctly?
Every FEA model must satisfy global equilibrium: the sum of all reaction forces at the boundary conditions must equal the applied loads, and the sum of reaction moments must equal the applied moments. Most FEA solvers compute and report these equilibrium checks automatically in the output file. A reaction force sum that does not match the applied load within numerical precision (typically 0.1% or less) indicates a fundamental problem with the model: either loads or constraints have been incorrectly defined, or the model has numerical errors severe enough to violate equilibrium.
Symmetry Check: Does the Model Respect the Expected Symmetry?
If the geometry, loading, and boundary conditions are symmetric about a plane, the solution must also be symmetric about that plane. Any asymmetry in the results of a symmetric analysis indicates a modeling error: an incorrectly applied asymmetric load, an asymmetric material property assignment, or an incorrectly positioned boundary condition. This check is particularly effective at catching subtle errors in load direction or constraint application that produce results that look reasonable but are systematically wrong across the symmetry plane.
Deformation Mode Check: Does the Structure Deform as Physics Predicts?
Before examining any stress result, examine the deformed shape of the structure and ask: is this the deformation mode I expected? A cantilever beam under a tip load should show maximum deflection at the tip and zero deflection at the fixed end. A pressure vessel under internal pressure should show outward bulging. A column under compressive load should show axial shortening, not lateral displacement. Any deformation mode that contradicts the expected physical response indicates a modeling error that must be corrected before any stress result is meaningful
Load Path Check: Does the Model Transfer Load as Expected?
Plot the stress distribution and trace the load path from the applied forces to the reactions. The stress should be highest in the members that carry the most load and decrease as the load is distributed toward the supports. Any region showing unexpectedly high or low stress should be examined for modeling errors: incorrect material properties, missing connections, or erroneously applied constraints.
| Minimum Validation Standard Every FEA analysis, regardless of its intended use or consequence level, should at minimum pass the four Level 1 sanity checks: equilibrium check (reactions equal applied loads), symmetry check (results respect model symmetry), deformation mode check (structure deforms physically), and load path check (stress distribution follows expected load path). Any analysis that fails one of these checks has a modeling error that must be corrected before proceeding to any further validation or result interpretation. |
Level 2 Validation: Analytical Solution Comparison
Comparison to analytical (closed-form) solutions is the most credible validation method available when the analytical solution exists and the model geometry and loading match the analytical assumptions well enough. An FEA result that agrees with a known exact solution within the expected discretization error is a validated result for that class of problem. The confidence in the analytical comparison transfers to the full model when the simplified problem and the full model share the critical physics that govern the structural response.
Building the Validation Model: Matching FEA to Analytical Assumptions
The most common mistake in analytical comparison is applying an analytical solution to a problem whose assumptions it does not satisfy. The Euler-Bernoulli beam bending formula (sigma = M*y/I) assumes a long, thin beam with a uniform cross-section under pure bending, with no shear deformation, no geometric nonlinearity, and loads applied far from the measurement point. Applying this formula to validate FEA of a short, deep beam with a complex cross-section and concentrated loads will produce disagreement that tells you nothing meaningful about the accuracy of the FEA, because the analytical solution does not apply to the problem.
The correct procedure is to create a validation sub-model: a simplified version of the full FEA model that does match the analytical assumptions (same or simplified geometry, same loading type, same material model, same boundary conditions). Run the FEA on this validation sub-model. Compare to the analytical solution. If they agree within expected discretization error (typically less than 5% for a well-converged mesh), confidence in the FEA implementation is established. Then return to the full model, recognizing that the physics that were validated in the sub-model also operate in the full model.
Useful Analytical Solutions for Structural FEA Validation
- Beam bending (Euler-Bernoulli or Timoshenko): deflection, slope, and stress along a beam under specified loading and boundary conditions. Valid for aspect ratios L/h > 10 for Euler-Bernoulli, L/h > 3 for Timoshenko with shear correction.
- Hertz contact: contact pressure distribution, contact radius, and subsurface stresses for two elastic spheres or cylinders in contact. Validates contact nonlinearity implementation.
- Lame equations for thick-walled cylinders: radial and hoop stress distribution through a pressurized thick-walled cylinder. Validates axisymmetric element and pressure loading accuracy.
- Plate bending (Kirchhoff or Mindlin-Reissner): deflection and stress in a plate under uniform pressure for various boundary conditions. Validates shell element formulation.
- Hertzian beam on elastic foundation: beam deflection and bending moment along a beam on a Winkler elastic foundation. Validates spring support boundary conditions.
- Buckling load (Euler column): critical buckling load for a slender column under axial compression. Validates linear buckling eigenvalue analysis.
Level 3 Validation: NAFEMS Benchmark Problems
NAFEMS (the National Agency for Finite Element Methods and Standards, now operating as an international association) has published an extensive library of benchmark problems with reference solutions for a wide range of structural, thermal, fluid, and coupled physics analysis types. These benchmarks serve a different purpose from analytical comparison: they validate the solver’s implementation for problem types that have no exact analytical solution but have highly accurate reference numerical solutions computed by multiple independent methods.
The most widely used structural benchmark series is the NAFEMS Linear Static Benchmarks, which includes tests for 2D plane stress and plane strain elements, 3D solid elements, shell elements, beam elements, and various boundary condition types. Each benchmark provides: the problem geometry and loading, the reference solution for key result quantities (displacement, stress, natural frequency), and the expected accuracy range for a correctly implemented solver with a specified mesh density. A FEA model that matches NAFEMS benchmark results within the stated accuracy confirms that the solver implementation is correct for that element type and analysis type.
How to Use NAFEMS Benchmarks in Practice
The intended use of NAFEMS benchmarks is before starting a new type of analysis with an unfamiliar element type, solver setting, or problem configuration. If you are running your first large-displacement nonlinear analysis, run the NAFEMS nonlinear benchmark for that analysis type before the production analysis. If you are using a new contact formulation for the first time, run the NAFEMS contact benchmark. The benchmark confirms that your solver setup for this problem type is correct before you commit engineering resources to analyzing the actual structure.
NAFEMS benchmarks are available to NAFEMS members and through academic institutions. Several benchmark problems are also available in published form through NAFEMS conference proceedings and educational resources. Most major commercial FEA software vendors provide worked examples of their software running the NAFEMS benchmarks as part of their validation documentation, which can be used as secondary references if direct NAFEMS membership is not available.
Level 4 Validation: Experimental Correlation
Experimental correlation is the most expensive and most credible FEA validation method. It involves comparing FEA predictions against measurements taken on a physical test article under controlled loading, demonstrating that the simulation matches the measured physical behavior to within a quantified uncertainty band. For safety-critical applications, many regulatory bodies explicitly require experimental correlation as part of the design substantiation package, and the specific correlation methods, measurement techniques, and acceptance criteria are defined in the applicable code or standard.
The Experimental Validation Hierarchy: From Coupon to System
Experimental validation in aerospace, medical device, and nuclear industries follows a building-block approach: validation evidence is collected at progressively higher levels of structural complexity, from simple material test specimens through components, sub-assemblies, and ultimately the complete system. Each level builds on the confidence established at the level below.
Coupon level: simple specimens of the exact material, in the same manufacturing condition as the production component, tested under simple loading (tension, compression, bending) to establish material model parameters and validate material behavior. Material properties used in FEA must be traceable to coupon test data for the specific material and manufacturing process used in the production component.
Component level: single structural components (a bracket, a fastener, a weld joint) tested under representative loading to validate the FEA prediction of that component’s response. Component tests are where most FEA validation in product development occurs: strain gauges or DIC measurements on the component under measured loads, compared to FEA predictions at the same locations.
Sub-assembly level: groups of interconnected components under combined loading, validating the FEA model of assembly interactions including contact behavior, load transfer through fasteners, and joint stiffness. Sub-assembly validation is particularly important for bolted connections and press-fit assemblies where the individual component FEA is well-validated but the assembly behavior depends on interface conditions that are less certain.
System level: the complete product or structure under full operational loading, providing the highest-confidence validation but at the highest cost. System-level testing is typically limited to critical safety programs and regulatory demonstrations, not routine product development.
Strain Gauge Correlation: The Most Common Experimental Validation Method
Resistance strain gauges are the most widely used experimental measurement tool for FEA validation of structural components. They measure the surface strain at specific locations, which can be directly compared to the FEA-predicted strain at those locations. The correlation workflow involves applying gauges at locations where the FEA predicts significant strain (peak stress locations, load introduction points, strain concentration features), loading the test article to a measured load level, recording the gauge outputs, and comparing to the FEA predictions at the corresponding nodes and load level.
The correlation is expressed as a percent error at each gauge location: (FEA strain – measured strain) / measured strain x 100%. Acceptable correlation thresholds depend on the application: 5% or less is expected at well-characterized, accessible locations in structural steel components. 10 to 15% may be acceptable at locations with significant manufacturing variability (welds, castings) or where the gauge placement was not precisely at the FEA node location. Discrepancies greater than 15% at critical locations require investigation to determine whether the error source is in the FEA model, the test setup, or the measurement system.
Digital Image Correlation: Full-Field Validation
Digital Image Correlation (DIC) is an optical measurement technique that computes the full two-dimensional or three-dimensional surface strain field over a region of interest by tracking the deformation of a speckle pattern applied to the test article surface. Unlike strain gauges, which provide point measurements at pre-selected locations, DIC provides continuous full-field strain maps that can be directly compared to FEA contour plots over the entire measured region.
DIC validation is particularly powerful for identifying unexpected strain concentration locations that were not anticipated during the strain gauge placement plan: the DIC map reveals where the actual peak strains occur, even if those locations were not gauged. This is the most direct evidence that the FEA model correctly predicts not just the magnitude but also the spatial distribution of the strain field, which is the true measure of model quality for structural analysis.
Quantifying Correlation: Error Metrics for FEA Validation
Saying that FEA and test results agree well is not a quantitative validation statement. Professional FEA validation requires quantitative error metrics that express the degree of agreement between simulation and measurement in reproducible, comparable terms. The following metrics are used in published validation studies, regulatory submissions, and engineering design reviews.
| Metric | Formula | Acceptable Threshold | What It Measures | When to Use |
| Percent error (single point) | |(FEA – Test)| / Test x 100% | <5% critical features; <10% secondary | Point-to-point deviation at specific location | Comparing FEA vs test at individual measurement points |
| Root Mean Square Error (RMSE) | sqrt(mean((FEA_i – Test_i)^2)) | Application-specific; typically <10% of range | Overall scatter in FEA vs test across all measurement points | Full-field correlation quality across strain gauge array or DIC field |
| Correlation Coefficient (R^2) | 1 – sum((FEA-Test)^2)/sum((Test-mean)^2) | R^2 > 0.95 for high confidence | How well FEA tracks test trends (not absolute accuracy) | Modal analysis correlation; full-field strain correlation |
| MAC (Modal Assurance Criterion) | (phi_FEA . phi_Test)^2 / ((phi_FEA.phi_FEA)(phi_Test.phi_Test)) | MAC > 0.9 for same mode pair | Similarity between FEA and test mode shapes | Vibration/NVH correlation – modal analysis validation |
| Normalized Error Norm | ||FEA – Test|| / ||Test|| | <0.1 (10%) for engineering confidence | Global normalized error across all comparison points | Global quality metric for full-field comparison |
| Frequency error (modal) | |(f_FEA – f_Test)| / f_Test x 100% | <5% for well-correlated modes | Natural frequency prediction accuracy | Modal analysis validation for dynamic analysis |
Interpreting the Metrics: Beyond the Numbers
No single error metric tells the complete validation story. A model with excellent percent error at one location may have poor correlation at another. A model with high R-squared correlation coefficient may have a systematic bias (consistently over- or under-predicting by a constant factor). A model with good overall RMSE may have poor correlation at the specific location that governs the safety decision.
The engineering approach is to report multiple metrics and investigate discrepancies rather than to report the best-looking metric and declare validation success. A validation that reports both the best-correlated and worst-correlated locations, with specific explanation of why the worst locations show more error, demonstrates far more analytical rigor and engineering credibility than a validation that only shows the cases where FEA and test agree well.
Sensitivity Analysis: Validation Through Input Variation
Sensitivity analysis is a validation-adjacent method that, while not a direct comparison to experimental data, provides critical information about the robustness of the FEA result to uncertainties in the model inputs. It asks: how much does the result change if the input parameters vary within their realistic uncertainty ranges? A result that changes dramatically with small input variations is inherently less credible than a result that is stable across the uncertainty range of its inputs.
What to Vary and What to Measure
The inputs to vary in a sensitivity analysis are those that carry meaningful uncertainty in the specific analysis: material modulus (typically well-characterized in metals but highly variable in polymers and composites), material yield strength (significant lot-to-lot variability in some materials), applied load magnitude and direction, boundary condition stiffness (especially for spring supports representing adjacent structure), friction coefficient at contact interfaces, and geometric dimensions within manufacturing tolerances.
For each varied input, compute the change in the critical result (peak stress, maximum deflection, natural frequency) as a percentage of the baseline value. Inputs that produce a 10% or greater change in the critical result are high-sensitivity inputs that deserve careful attention: their uncertainty must be well-characterized, and the conservative direction of their variation must be identified for the safety case. Inputs that produce less than 1% change in the critical result are low-sensitivity and can be treated as nominal in the final analysis.
Sensitivity Analysis in Regulatory Submissions
Regulatory bodies in medical device (FDA, EU MDR), aerospace (FAA, EASA), and nuclear (NRC) applications have increasingly recognized sensitivity analysis as a component of a complete V&V package. The FDA’s guidance on the use of computational modeling in medical device submissions (2016 and 2023 updates) explicitly discusses the role of sensitivity analysis in demonstrating that the FEA result is robust and that the conclusions drawn from the model hold across the realistic range of input uncertainty.
The practical benefit for regulated product development is that sensitivity analysis performed and documented during design validation creates an asset that directly supports regulatory submission, rather than requiring additional analysis during the submission review process.
Regulatory V&V Requirements by Industry
Regulated industries have specific, binding requirements for FEA validation that go beyond engineering best practice. Performing FEA without understanding the applicable regulatory V&V requirements is a significant compliance risk: a well-executed analysis that is documented in the wrong format or that does not include the required validation methods may be rejected by regulators, requiring expensive retrospective validation work or design modifications.
Medical Devices: FDA and EU MDR Requirements
The FDA’s guidance document ‘Reporting of Computational Modeling Studies in Medical Device Submissions’ (2016) establishes expectations for computational modeling V&V in device submissions. The guidance requires: documentation of model assumptions and their justification, verification evidence (mesh convergence, benchmark comparisons), validation evidence appropriate to the model’s intended use and the consequence of error, uncertainty analysis, and clear communication of model limitations.
The FDA uses a risk-based approach to determine the required validation rigor: the higher the risk of the device and the more central the computational model is to the safety and effectiveness evidence, the more extensive the validation evidence required. A low-risk dental implant using FEA as supporting evidence for a well-established design may require only analytical comparison and basic experimental correlation. A high-risk cardiac implant where FEA is the primary structural evidence may require extensive coupon-through-system validation with quantified uncertainty bounds.
Aerospace: FAA and MIL-STD Requirements
Aerospace structural analysis validation is governed by the AC 20-107B (Advisory Circular for Composite Aircraft Structure) for composite structures, and by structural substantiation requirements in the applicable aircraft certification basis (FAR Part 23, 25, 27, 29) for metallic structures. The primary validation method for aerospace FEA is the building-block test program, which provides experimental validation at each level of the structural hierarchy from coupon through full-scale component.
The DOD-HDBK-6870 (Probabilistic Failure Analysis Handbook) and the Department of Defense V&V framework provide additional guidance for defense system structural analysis. These frameworks require that computational models used for structural adequacy demonstration be validated against representative test data before being used for design decisions or certification evidence.
Pressure Vessels and Piping: ASME V&V 10
ASME has published ASME V&V 10-2006 (Guide for Verification and Validation in Computational Solid Mechanics) and ASME V&V 10.1-2012 (Example for Verification and Validation in Computational Solid Mechanics) as the primary V&V standards for pressure equipment FEA. These standards establish the formal framework for verification activities (patch tests, mesh convergence, code verification benchmarks) and validation activities (comparison to analytical solutions, experimental correlation at various structural levels) for FEA used in ASME Boiler and Pressure Vessel Code design submissions.
Engineers using FEA under ASME Section VIII Division 2 Design by Analysis methods are expected to follow the V&V 10 framework. The Division 2 Annex 5B explicitly requires that the analyst document the validation basis for the FEA model, including the analytical or experimental evidence that the model correctly captures the relevant physics. Without this documentation, the FEA-based design analysis is not substantiated under Division 2 regardless of how technically correct the underlying simulation may be.
The V&V Documentation Framework: Creating a Defensible Validation Record
A technically excellent validation that is poorly documented is nearly as problematic as a poorly executed validation. The validation record is the artifact that survives the analysis project: it is what engineers review when the design is questioned years later, what regulatory reviewers examine when evaluating a submission, and what legal counsel relies on when defending the engineering team. A complete validation record makes the analysis credible, defensible, and reusable.
FEA Validation Documentation Package Structure |
Frequently Asked Questions
Q: What is the difference between FEA verification and validation?
Verification asks ‘are we solving the equations correctly?’ and confirms that the computational model accurately implements the mathematical model. Validation asks ‘are we solving the correct equations?’ and confirms that the mathematical model represents the physical system. In practice: the FEA software vendor is responsible for code verification (ensuring the solver correctly implements finite element formulations); the analyst is responsible for solution verification (mesh convergence study proving numerical accuracy) and model validation (comparison to analytical solutions or experimental data proving physical accuracy) on every analysis.
Q: What is a patch test in FEA and why does it matter?
The patch test is the fundamental test of a finite element formulation’s mathematical completeness. It verifies that a mesh of elements in a general distorted configuration can exactly reproduce a state of constant stress and corresponding linear displacement field when subjected to appropriate boundary conditions. An element that fails the patch test cannot exactly represent constant stress states, which means it introduces systematic errors in all problems where the true stress approaches constant. Commercial software elements pass the patch test by design, but analysts using custom elements or unusual formulations must verify patch test performance before trusting the results.
Q: When is experimental validation required for FEA?
Experimental validation is required whenever FEA results are used as primary evidence for safety-critical design decisions in regulated industries. The FDA requires experimental correlation for medical device FEA used in submissions for high-risk devices. The FAA requires building-block test programs for aerospace structural certification. ASME requires documented validation evidence for FEA used in Division 2 Design by Analysis of pressure vessels. For non-regulated applications, experimental validation is best practice when the consequences of an incorrect FEA result are significant (personnel safety, major financial exposure) and when other validation methods do not provide adequate confidence in the model’s physical accuracy.
Q: What error tolerance is acceptable between FEA and experimental results?
Acceptable error depends on the application and the location of comparison. For structural stress validation at well-characterized, accessible locations in metallic components: less than 5% error is expected for high-confidence validation. Less than 10% is generally acceptable for engineering design validation. Less than 15% may be acceptable at locations with high manufacturing variability or uncertain gauge placement. Errors above 15% at critical locations require investigation to determine whether the error source is in the FEA model, the test setup, the measurement system, or the material property data. For modal analysis, natural frequency errors below 5% and MAC values above 0.9 for matched modes are the standard acceptance criteria.
Q: What is the NAFEMS benchmark and how do I use it for FEA validation?
NAFEMS (the National Agency for Finite Element Methods and Standards) has published an extensive library of benchmark problems with reference solutions for a wide range of structural, thermal, fluid, and coupled physics analysis types. Engineers use NAFEMS benchmarks to verify that their solver setup produces correct results for a specific element type and analysis type before running the production analysis. The workflow is: identify the NAFEMS benchmark that most closely matches your analysis type, build the benchmark model in your FEA software, run the analysis, compare your result to the NAFEMS reference solution, and proceed with the production analysis only if the benchmark comparison is within the expected accuracy range.
Q: What must a V&V documentation package include for a regulatory submission?
A complete V&V documentation package for regulatory submission should include: (1) Analysis scope and objectives, including intended use and consequence of error; (2) Model description and assumptions with justification for all simplifications; (3) Verification evidence including mesh convergence study results, equilibrium checks, and benchmark comparisons; (4) Validation evidence appropriate to the application risk level, which may range from analytical comparison for low-risk to full experimental correlation for high-risk; (5) Sensitivity analysis showing how the critical result responds to input uncertainty; (6) Uncertainty quantification establishing confidence bounds on the critical result; and (7) Conclusions including the limits of applicability of the model. The specific required content and format varies by regulatory body (FDA, FAA, ASME, NRC) and submission type.
Conclusion:
The engineer who runs an FEA, checks that it converged, and delivers the peak stress number without any validation has performed a sophisticated calculation and made an unquantified assumption that it is correct. That assumption may be valid. But the engineer cannot know that it is, and more importantly, no one reviewing the work can know it either.
Validation is what converts a calculation into evidence. It is the technical discipline of establishing, through structured comparison to known-correct solutions or physical measurements, that the FEA model represents the physical system it claims to represent, with a quantified degree of confidence appropriate to the engineering decision it supports. This is a higher standard than most engineering teams routinely meet, and meeting it requires effort, documentation, and in some cases physical testing. But it is the standard that the engineering profession owes to the people who use the products, infrastructure, and equipment that FEA analysis is used to design.
Start with the minimum: run every analysis through the four Level 1 sanity checks. Add analytical comparison for the class of problem the analysis represents. Document both. Add a mesh convergence study demonstrating numerical accuracy. Document it. For safety-critical applications, add the experimental correlation that the application demands. Document everything in a format that a reviewer can independently assess. That is the professional standard. This article has given you the framework and the specific methods to meet it.
Continue building your FEA expertise with our guides on when to use linear vs nonlinear FEA, mesh quality and its impact on accuracy, and the CAD modeling practices that create simulation-ready geometry.