Frequently asked questions

We use CFD and related analysis for aerodynamic performance, high-speed and re-entry aerothermodynamics, heat flux, fluid–structure interaction, and specialist problems such as biofluid dynamics, pumps, rail, and civil flows. The right method depends on the engineering question and available evidence.

Our work includes aerospace and spaceflight, transport, energy and industrial equipment, civil flows, and biofluid research. If your application is not listed, describe the system and decision you need to make; we can assess fit during an initial discussion.

Share the engineering question, available geometry or model, operating conditions, and any target date or constraints. Existing test or simulation data and known assumptions are useful too. You do not need a complete package to start a conversation; we can identify missing inputs while agreeing the scope.

Validation depends on the case and intended use. It can include checking inputs and boundary conditions, mesh or time-step sensitivity, convergence and conservation, and comparison with experiments, benchmark cases, or trusted reference data where available. We agree the relevant evidence and acceptance criteria for each project; no single check proves every result accurate.

Yes. We can use a private or on-premises cluster if it has the required software, capacity, and access controls. We agree on execution, data transfers, and responsibilities before setup.

Deliverables are agreed for the project and may include CFD results or flow-field data, engineering quantities such as coefficients, loads or heat flux, comparisons between defined cases, and a concise record of methods, assumptions, validation evidence, and limitations. CFS Engineering has its own database format, and clients can choose their preferred export format. File formats, level of detail, and any reports are agreed in the project scope.

CFD is a model, not a measurement. Accuracy is affected by geometry and input quality, boundary conditions, mesh and numerical choices, physical models, and the amount and relevance of validation data. Some uncertainty remains even after checks; we document material assumptions and limits, and results should be used within their agreed scope.

There is no standard duration. Timing depends on the scope, geometry and input readiness, number of operating cases, modelling and validation needs, compute access, and review cycles. We estimate the schedule after reviewing the request and agree milestones before work starts.

We prepare a project-specific estimate after clarifying the scope. Cost depends on the engineering question, input readiness, modelling and mesh effort, number and fidelity of cases, validation work, compute or software needs, and requested deliverables. Share any budget constraint early so the proposed scope can be discussed against it.

No. The currency you pay in is not important, so please don’t worry about it. We can agree the payment details when we scope the project.

CFS focuses on CFD and connected engineering analysis, with experience across aerospace, high-speed flows, fluid–structure interaction, and specialist applications. We can bring modelling, meshing, simulation, and interpretation together, including work with our NSMB solver where it fits. Whether that is a better fit than another provider or your in-house team depends on your skills, tools, workload, and project needs.

The work is carried out by CFS engineers and specialists selected for the technical needs of the project. The relevant people, roles, and any collaborators are identified during scoping or in the proposal, so you can discuss the team before work begins.

Discuss confidentiality terms, approved transfer methods, access, working environment, storage, and retention before sending sensitive files. We agree how data is handled for each project. The contact form opens your email application and does not send or store your details; agree an approved channel before sharing sensitive data.

We review your engineering question and available inputs, then discuss fit, missing information, scope, deliverables, validation approach, security needs, schedule, and estimate. If we agree to proceed, these points are confirmed in a proposal before technical work starts. The contact form opens your email application; your message is sent only if you choose to send that email.