NAFEMS UK Conference 2026

Formula One teams rely heavily on advanced engineering software—CAD, CFD, FEA, and multi-physics simulation—to deliver performance gains measured in thousandths of a second. Unlike most engineering domains, however, Formula One operates under explicitly defined regulatory constraints that limit how simulation tools may be used. FIA regulations impose strict caps on aerodynamic testing, including limits on wind-tunnel hours, restricted CFD activity, and total allowable computational effort within fixed Aerodynamic Testing Periods. In parallel, a season-wide financial cost cap governs all relevant development expenditure, including software licensing, compute infrastructure, and engineering labor. Within this environment, engineering performance is no longer driven by who can run the most simulations, but by who can extract the greatest insight from a finite and regulated simulation budget. As a result, visibility into how engineering software is actually used becomes a competitive requirement rather than an administrative exercise. This presentation explores how granular reporting of simulation and license usage enables Formula One teams to operate effectively within these constraints. Rather than focusing on individual tools or solvers, the discussion examines how usage data—covering CFD execution, geometry iteration, solver configuration, and license consumption—can be structured to support informed decision-making across the aerodynamic development process. The emphasis is on understanding where regulated resources are consumed, when they are most valuable, and how they align with performance objectives. A key challenge lies in managing scarcity. Regulatory limits on CFD compute, geometry iterations, and wind-tunnel activity force teams to make deliberate choices about model fidelity, simulation frequency, and development focus. Without structured reporting, these decisions are often made reactively, increasing the risk of wasted regulatory allowance, duplicated effort, or reduced aerodynamic return. Reporting frameworks introduce transparency by linking simulation activity to design intent and regulated limits, allowing teams to prioritize high-impact analyses while deferring lower-value work. The session also considers the role of license and compute visibility in a cost-constrained environment. Understanding concurrency, idle capacity, and feature utilization supports better alignment between engineering demand and available resources, particularly when all usage contributes to regulated budgets. When combined with time-based views of activity across Aerodynamic Testing Periods, reporting enables forward planning rather than retrospective correction. While grounded in the specific context of Formula One, the principles discussed extend far beyond motorsport. Many engineering organizations now face similar constraints driven by compute availability, sustainability objectives, regulatory oversight, or fixed R&D budgets. In these environments, the ability to govern simulation usage without slowing innovation is increasingly critical. By reframing reporting as an enabler of engineering effectiveness, rather than a compliance obligation, constrained environments can turn limitation into advantage—on the grid and beyond.