Documentation
A surrogate model is a fast approximation of an expensive simulation. It’s trained on the inputs and outputs of solved cases, then predicts the result for a new design in seconds instead of hours.
Engineers reach for one when a single CFD or FEA run takes hours and the design question needs hundreds of answers. At Convion, a solver-driven optimization of one ejector “easily takes weeks,” in the words of its thermofluids lead. With a trained surrogate in the loop, the same optimization ran in minutes.
A surrogate model (also called a metamodel, response surface model or emulator) approximates the input-output behavior of a high-fidelity simulation. It’s trained on a set of solved simulation cases and predicts the response for new inputs without solving the governing equations again.
$$ \hat{y} = \hat{f}(\mathbf{x}) \approx f(\mathbf{x}) \tag{1} $$
Here \(\mathbf{x}\) is the vector of design inputs (geometry parameters, boundary conditions, operating points), \(f\) is the simulation and \(\hat{f}\) is the surrogate, trained on \(N\) solved samples \((\mathbf{x}_i, f(\mathbf{x}_i))\).
The output can be a few scalars, such as pressure drop, drag coefficient or peak temperature. It can also be a full field, such as pressure and velocity on every surface of the part. Field surrogates are what most engineers mean by an AI surrogate model for CFD.
Two meanings of “surrogate model”
In machine learning interpretability, a surrogate model is a simple model, such as a decision tree, trained to explain the predictions of a black-box model [5]. This article covers the engineering meaning: a fast stand-in for a physics simulation.
A physics solver computes each case from first principles. A surrogate model learns from cases the solver has already computed. That difference sets where each one belongs.
| Criterion | Physics solver (CFD, FEA) | Surrogate model |
| How it gets the answer | Solves the governing equations on a mesh | Maps inputs to outputs learned from solved cases |
| Time per new design | Minutes to hours | Milliseconds to seconds |
| Up-front cost | Setup and meshing per case | Tens to hundreds of solver runs, plus training |
| Valid range | Any case the physics models cover | Only inside the design space it was trained on |
| Accuracy depends on | Mesh, physics models, numerics | Quality and coverage of the training data |
| Best for | New physics, one-off cases, final validation | Design space exploration, optimization, sensitivity studies, real-time use |
In practice the two work together. The surrogate screens thousands of variants, and the solver confirms the shortlist. For more on that hybrid pattern, see AI simulation explained.
Pick the type by the number of inputs, the number of solver runs you can afford and whether you need scalars or full fields [1].
| Type | How it works | Fits when |
| Polynomial response surface | Fits a low-order polynomial by least squares | Few inputs, smooth response, small run budget |
| Kriging / Gaussian process | Interpolates between samples using their spatial correlation; returns an uncertainty estimate | Expensive runs, tens to low hundreds of samples, you need error bars |
| Radial basis functions | Sums distance-weighted basis functions centered on the samples | Scattered samples, moderate number of inputs |
| Polynomial chaos expansion | Expands the output in orthogonal polynomials of random inputs | Uncertainty quantification |
| Neural networks | Learns a layered nonlinear mapping from data | Many inputs, strongly nonlinear physics, full 3D field outputs, larger data sets |
The classic methods fit smooth, low-dimensional problems well. They struggle when the physics turns sharply nonlinear. Convion learned this firsthand: its earlier attempts with traditional surrogate modeling “proved insufficient to capture the extreme non-linear behavior present in this regime,” so the team moved to neural network models trained on 3D CFD (Convion case study).
These three terms overlap in search results, but they build the fast model in different ways.
| Approach | How it’s built | What it needs | Trade-off |
| Surrogate model (data-driven) | Learns from solver outputs; treats the solver as a black box | Solved cases from any solver | Simple to build from existing runs; valid only inside the training range |
| Reduced-order model (ROM) | Projects the governing equations onto a small set of dominant modes, for example by proper orthogonal decomposition (POD) [4] | Solution snapshots plus access to the equations or operators | Keeps more of the physics; harder to build around commercial solvers |
| Physics-informed machine learning (for example PINNs) | Trains a neural network whose loss penalizes violations of the governing equations [3] | The equations, with little or no solver data | Physics built into training; training is often slow for complex 3D flows |
The boundaries are blurring. Many current AI surrogates for CFD learn from solver data and add physics constraints during training, which is why the press often calls them physics-informed.
Training a surrogate is a six-step loop. Most of the effort goes into the first three.
Training data comes from a DoE, which needs far fewer runs than a solver-driven optimization. An optimizer walks the design space step by step and can need thousands of evaluations. A DoE covers the space once, up front, in hundreds.
“When we’re training or doing CFD simulations for training a Physics AI, we’re not doing optimization,” said Armin Narimanzadeh, Thermofluids & Simulations team lead at Convion. “It’s a DoE problem, and you could do less with a DoE problem.”
Where the DoE starts matters too. Convion runs 0D and 1D calculations first to find the promising region, then spends its 3D CFD budget there.
There’s no universal number, but three reference points help.
The Convion test is the method to copy. Train on growing subsets of your data and stop adding runs when the validation error stops falling. Data quality in the regions that drive the result counts for more than raw run count.
Neural network surrogates train over a set number of epochs, one epoch being one pass through the training data. Too few and the model underfits. Too many and it memorizes the training runs and generalizes poorly. In SimScale you set the number of epochs and a target confidence score before training starts, then review how the model performed across the epochs before releasing it to your team.
Check these before you trust a surrogate:
Convion designs solid oxide fuel cell and electrolyzer systems. One component, an ejector that recovers high-temperature process gas, had coupled, competing performance targets and a highly nonlinear design space. Finding the best configuration with simulation-driven optimization “would have taken months,” according to Armin.
The team replaced the solver inside the optimization loop with a surrogate:
The design that came out met every performance target in 50% less physical volume. And because the validated model is reusable, a new component for changed boundary conditions is now “half a day maximum away,” down from weeks.
Most surrogate-based optimizations are multi-objective, as Convion’s was. Querying a surrogate in milliseconds is what makes mapping a full Pareto front affordable.
A surrogate is the wrong tool in these cases:
SimScale runs the whole loop in the browser. You can generate the DoE with parametric studies or have the Engineering AI agent set it up, run every case in parallel in the cloud, then train a model on the results. In a live demo at Agentic Unlocks, a drone model’s training job was submitted in about a minute and ready in about 40 minutes on cloud GPUs. The trained model then returned field predictions in seconds, shown side by side with the CFD result.
Because the surrogate and the solver share the same setup, you can switch from a prediction to a full CFD or FEA run of the same design in a few clicks.
A surrogate model learns the input-output relationship from solved simulation cases and treats the solver as a black box. A reduced-order model projects the governing equations onto a small number of dominant modes, so it needs access to the equations or solver internals. Both give fast answers; the surrogate is simpler to build from existing runs.
A common starting point is about 10 runs per input variable for Gaussian process models, and SimScale’s AI model training needs at least 20 runs. Neural network surrogates that predict full 3D fields usually need hundreds. Convion found 256 runs gave nearly the same result as 512, and 128 were enough with a fine mesh in the critical region.
Accuracy depends on the training data and on staying inside the trained design space, so check it on validation runs with metrics such as R² and mean absolute error. In Convion’s ejector case, the model predicted performance within 5% of high-fidelity CFD. Always confirm the final design with a solver run.
They’re different methods. A standard surrogate model learns only from simulation data. A physics-informed neural network (PINN) builds the governing equations into its training loss and can learn with little or no simulation data. Many current AI surrogates for CFD combine the two, using solver data with added physics constraints.
It can’t. A surrogate is trained on simulation results and is only valid inside the range of those results. Engineers use it to explore design options and run optimizations quickly, then validate the final candidates with a full CFD or FEA run.
Some are. Polynomial response surfaces, kriging and radial basis functions are classical statistical methods. Neural network surrogates, which can predict full 3D flow and stress fields, are machine learning models and are usually what people mean by an AI surrogate model.
References
Last updated: October 28th, 2026
We appreciate and value your feedback.
Subscribe to our newsletter
By subscribing you agree to with our Privacy Policy
Product
Solutions
Resources
Sign up for SimScale
and start simulating now