How an Electric Vehicle Is Designed — From Vehicle Targets to Production

An EV Is a Coupled Engineering System

An electric vehicle is not simply a conventional vehicle with an electric motor substituted for an engine. Battery mass changes the structural concept, packaging changes occupant and crash geometry, power demand changes cooling and electrical architecture, regenerative braking changes brake blending, and software becomes a major part of vehicle behaviour. A credible development process therefore treats performance, range, mass, crash, thermal behaviour, durability, controls, cost and manufacture as coupled design variables from the beginning.

The Development Chain

1. Define customer use cases, regulatory obligations and measurable vehicle targets.
2. Select the vehicle architecture, driven wheels, voltage class, battery concept and principal hardpoints.
3. Close first-order mass, performance, energy and thermal budgets.
4. Develop packaging, structural load paths, crash zones and battery protection together.
5. Size the motor, inverter, gearing, battery and thermal systems against the full operating envelope.
6. Develop suspension, steering, brakes and control functions around the chosen mass distribution and tyre capability.
7. Build prototype and analytical models, then correlate road, rig, thermal, crash and electrical tests.
8. Mature the design for production, manufacturing variation, serviceability, cost and compliance.

Targets Must Close Together

A range target cannot be separated from mass, drag, rolling resistance, usable battery energy and auxiliary demand. Acceleration cannot be separated from tyre traction, motor torque, inverter current, battery power and thermal limits. Crash performance cannot be separated from battery packaging and body structure. Early development should therefore maintain linked engineering budgets rather than independent headline targets.

A Useful Set of Early Budgets

Models Should Mature With the Vehicle

Early models should be fast enough to explore architecture. Spreadsheet and 1D models are often more useful than detailed FEA before geometry and load paths are stable. As the design matures, CAD packaging, multibody vehicle dynamics, thermal networks, electromagnetic models, CFD, structural FEA, crash simulation and controls-in-the-loop models add fidelity where decisions justify it. Detail should follow design maturity rather than precede it.

Engineering Principle

The best EV architecture is rarely the design that maximises one metric. It is the design that closes the complete vehicle simultaneously: range, performance, crash, durability, thermal behaviour, manufacturability, cost and customer use.

Design Inputs, Assumptions & Requirement Control

For How an Electric Vehicle Is Designed — From Vehicle Targets to Production, the analysis should begin with a controlled set of inputs rather than a geometry-first model. The key inputs include the requirement set, failure consequence, design maturity, configuration status, verification method, manufacturing variation, service environment and the evidence needed for release or operation. Each value should carry a source, units, reference condition, uncertainty and revision status. Requirements, measured data, supplier limits and engineering assumptions should remain distinguishable because they have different levels of authority. In a Electric Vehicles programme the disciplines evolve in parallel, so an assumption that is acceptable during concept selection can become non-conservative after mass, stiffness, software or operating conditions change. A useful design record therefore captures the baseline, the reason for every important simplification and the sensitivity of the conclusion to uncertain inputs. This prevents an early placeholder from becoming an invisible design requirement later in the programme.

Engineering Analysis & Design Workflow

A strong workflow for this topic is based on risk-based verification planning, FMEA/FTA or equivalent failure analysis, progressive prototype and qualification testing, controlled model correlation and closure of non-conformities against the released configuration. Start with the simplest model that exposes the governing physics and use it to identify dominant parameters, limits and trade directions. Increase fidelity only when the additional detail can change a requirement, load, margin or architecture decision. At every level, preserve equilibrium, energy/power balance and interface consistency so the higher-fidelity model can be checked against an independent lower-order result. The output should not be a single number: useful engineering evidence includes trends, sensitivity, governing cases and the mechanism that creates the limit. This is especially important when optimisation is involved, because a numerical optimum at one assumed condition may disappear once uncertainty, manufacturing tolerance or another subsystem is included.

Governing Failure Modes, Limits & Sensitivities

The credible limits for How an Electric Vehicle Is Designed — From Vehicle Targets to Production include untested interfaces, latent common-cause failures, evidence produced on the wrong configuration, manufacturing variation outside analysed assumptions, inadequate safe-state behaviour or verification gaps discovered only at final acceptance. These mechanisms should be listed before detailed analysis so that the model is built to calculate the quantities that actually govern acceptance. Sensitivity should focus on parameters that can switch the governing mode: stiffness, damping, friction, preload, material modulus, temperature, timing, aerodynamic condition, battery state, tyre condition or manufacturing tolerance as relevant. If a small plausible change causes a large movement in margin, the engineering response should normally be to improve the evidence or make the design more robust rather than simply report the nominal result with greater numerical precision. Failure-mode thinking also helps distinguish a real design reserve from apparent margin created by a modelling assumption.

Modelling, FEA & Computational Fidelity

The numerical strategy should reflect the physics of the problem. For this topic, the natural starting point is risk-based verification planning, FMEA/FTA or equivalent failure analysis, progressive prototype and qualification testing, controlled model correlation and closure of non-conformities against the released configuration. Where structural FEA is required, boundary conditions should preserve the real interface stiffness and load path, and mesh convergence should be assessed on the response used for the decision rather than on contour smoothness. Where controls, aerodynamics, thermal behaviour, electrical networks or multibody dynamics dominate, the corresponding system model should remain the master source of loads and states; detailed FEA should not invent a disconnected design condition. Submodelling is often preferable to making a complete vehicle, aircraft or spacecraft model excessively detailed. The objective is a hierarchy of models whose assumptions are visible and whose results can be cross-checked, not a single opaque model that is difficult to verify.

Interfaces & System-Level Consequences

This subject cannot be closed independently from the rest of the system. The most important interfaces include battery mass and stiffness, high-voltage power, thermal loops, body load paths, suspension hardpoints, braking/regen control, tyres and occupant packaging. A design change should therefore be propagated through the adjacent budgets and models before it is accepted. For example, a stiffness increase can add mass and shift a mode; a larger actuator can increase power and thermal demand; a more conservative protective structure can alter packaging and centre of gravity; and a software change can alter the loads used for mechanical sizing. Interface reviews are most effective when they exchange quantitative quantities—forces, moments, stiffness, voltage, current, heat, latency, geometry and tolerances—rather than general statements of compatibility. Many expensive late changes are the result of locally valid designs whose interface assumptions were never reconciled.

Verification, Test Correlation & Model Updating

Confidence should be built through a planned hierarchy of inspection, analysis, component/subsystem test and full-system demonstration, with each item linked to an acceptance criterion and a configuration-controlled requirement. Test and analysis need to compare equivalent quantities: the same coordinate system, operating condition, filtering, configuration and measurement location. A strain gauge should be compared with strain in its actual direction; a thermal measurement should use the same heat input and ambient state; a dynamic response needs compatible bandwidth and boundary conditions. When disagreement appears, the first task is to identify whether the source is load, stiffness, damping, material data, sensor error, software logic or boundary condition. Model parameters should be updated only when a physical reason exists. Correlation is strongest when one justified model change improves several independent observations rather than forcing one trace to match.

Standards, Evidence & Configuration Traceability

The governing evidence for this topic should remain linked to target-market legislation and type-approval requirements, the vehicle programme DVP&R, OEM design standards, supplier specifications and applicable functional-safety, electrical and EMC requirements. Those documents define the project-specific context; this article should not be read as prescribing universal factors, margins or pass/fail values. The analysis record should identify the model revision, software version, material or supplier data, load-case source, safety/design factors, configuration and acceptance criterion used. Where requirements evolve, the impact on previous evidence should be assessed explicitly rather than assuming the old result remains valid. This traceability is particularly important when test, analysis and supplier evidence are combined, because all three can be individually correct yet refer to subtly different configurations. A reviewer should be able to move from requirement to input to model to result to verification evidence without reconstructing the engineering history from memory.

Engineering Judgement & Common Traps

The central judgement for How an Electric Vehicle Is Designed — From Vehicle Targets to Production is that verification is not a final project phase; it should shape architecture from the beginning so important requirements can be demonstrated without heroic or ambiguous end-of-programme testing. Common traps include accepting a positive margin without confirming that the governing physical mode is represented, using independently enveloped loads that cannot occur simultaneously, applying supplier catalogue limits as exact boundary conditions, or increasing model fidelity before uncertainty in the inputs has been reduced. Another recurring problem is optimising a subsystem after its neighbours have effectively frozen the interfaces; this can produce impressive local results with little system value. A good technical review should ask three questions: what assumption could reverse the conclusion, what measurement would most reduce the remaining uncertainty, and whether the recommended change still makes sense when viewed across battery, high-voltage system, powertrain, body structure, crash system, chassis, thermal management, controls, low-voltage electrical system and occupant/package interfaces.

Programme Health Check

• Vehicle targets are measurable and linked to a defined use case.
• Mass, energy, power and thermal budgets reconcile to the same vehicle configuration.
• Battery, crash structure and occupant package are being developed together.
• Peak and continuous performance are distinguished.
• Manufacturing and service requirements are represented before detailed design freeze.
• Analytical predictions are tied to a staged physical verification plan.