FEAI uses a language model to help you build and set up analyses, but the model never computes the answer itself. Geometry is created by a solid-modeling kernel, meshes are generated explicitly, and finite element solvers calculate the response.
A language model can understand a request like “fix this face and apply a 1 kN load here,” but understanding the request is not the same as solving the structure. Finite element analysis depends on geometry, material properties, boundary conditions, meshing, matrix assembly, and numerical solution. Those steps need to be explicit and reproducible. In FEAI, the assistant helps translate what you mean into those engineering operations. The geometry kernel and solver do the actual computation.
02/ The pipeline
Every analysis follows the same six stages.
The assistant turns your request into supported actions; the geometry kernel, mesher, and solver handle everything after that. Scroll to see where the language model's job ends and the engineering system's job begins.
01 / 06
01/language
02/feature actions
03/B-rep kernel
04/mesh
05/solver
06/results
01/
language
You describe what you want in plain English. FEAI also passes along useful context from the viewport: selected faces, edges, bodies, existing materials, loads, constraints, and analysis settings.
02/
feature actions
The assistant converts that request into structured operations that FEAI already knows how to execute. That includes actions such as create sketch, extrude, revolve, fillet, assign material, constrain face, apply force. The model does not write arbitrary geometry code or directly modify the scene. It chooses from defined operations and fills in their parameters.
03/
B-rep kernel
Geometry operations are executed by the CAD kernel as boundary-representation solids. Faces, edges, vertices, shells, and solids remain real geometric entities rather than being reduced to a triangle mesh. That means operations such as booleans, fillets, selections, and mass-property calculations work on the underlying CAD model. The resulting model also remains editable through the feature tree.
04/
mesh
The solid is discretized into finite elements before solving. FEAI can generate tetrahedral or hexahedral meshes from the CAD geometry and checks basic mesh quality before analysis. The mesh stores the nodes, element connectivity, material regions, and the geometric surfaces used to transfer loads and constraints from the CAD model into the finite element model.
05/
solver
The finite element solver computes the response. For a linear static analysis, FEAI assembles the global system Ku = f where K is the stiffness matrix, u is the displacement vector, and f contains the applied loads. Boundary conditions modify the system, the solver computes nodal displacements, and element quantities are recovered afterward, including strain and stress. The language model is not involved in this calculation.
06/
results
Results are mapped back onto the model for inspection. You can view quantities such as displacement, strain, stress, or von Mises stress. The underlying numerical data can also be exported for independent analysis or visualization.
03/
The assistant
The assistant is an interface to the engineering system, not a replacement for it. It can interpret requests, identify selected geometry, choose supported operations, fill in parameters, and explain what FEAI did. For example, if you write: “Use steel, fix these mounting holes, and put 2 kN on this face”, the assistant might translate that into: material → structural steel; constraint → fixed, selected faces 14–17; load → 2000 N, selected face 23, −Z direction. Those actions are then executed by the same geometry and simulation systems that would run if you created them manually. Everything appears in the model normally, so you can inspect it, edit it, or remove it afterward.
04/
Grounding
FEAI does not let the language model invent commands and hope they work. Each operation has a defined schema: the action name, required parameters, valid units, supported geometry references, and allowed values. A load action, for example, needs an actual model entity, a magnitude, and a direction. A material assignment needs a valid body and material definition. Geometry operations need the parameters expected by the CAD kernel. If a request cannot be represented by one of those operations, FEAI rejects it or asks for more information. That creates a simple boundary: the model decides what operation you probably want; the engineering system decides what operations are actually possible.
05/
Validation
A simulation is much more useful when you can inspect what went into it. FEAI keeps the analysis inputs visible: geometry, mesh, material properties, loads, constraints, and solver settings. Meshes and numerical results can also be exported in standard formats such as VTU and CSV. That makes it possible to inspect the mesh in another viewer, process results in Python, or compare the same problem against another FEA package. For validation, we use problems with known or independently computed solutions and compare quantities such as displacement, reaction force, stress, and mesh convergence. The goal is not simply to produce a contour plot. It is to make it possible to understand where the result came from.
