Electric Vehicle Architecture & Platform Trade Studies

Architecture Decisions Create Long-Term Constraints

The earliest vehicle architecture choices determine wheelbase, occupant position, battery envelope, crash zones, suspension hardpoints, luggage volume, electrical distribution and manufacturing strategy. Once body tooling and battery geometry mature, architecture changes become disproportionately expensive. Early trade studies should therefore compare complete vehicle consequences rather than isolated subsystem efficiency.

Core Architecture Choices

• Single-motor front-, rear- or all-wheel-drive arrangements.
• Dual-motor or multi-motor torque distribution architectures.
• Flat underfloor battery, structural battery, split packs or application-specific pack placement.
• Dedicated EV platform versus conversion/shared multi-energy platform.
• Nominal HV voltage class and charging architecture.
• Integrated e-axle versus separated motor, inverter and gearbox.
• Conventional body-in-white, skateboard chassis or highly integrated cast/structural concepts.

Trade at Vehicle Level

Architecture Should Be Compared With Common Assumptions

Trade studies are easily distorted when one concept is mature and another is represented by optimistic assumptions. Candidate architectures should use consistent payload, range, cell technology, tyre assumptions, thermal conditions, crash requirements and manufacturing volume. Otherwise the trade becomes a comparison of modelling maturity rather than architecture quality.

First-Order Architecture Metrics

Specific vehicle power:
P_spec = P_peak / m_vehicle

Battery mass fraction:
f_batt = m_batt / m_vehicle

Packaging utilisation:
η_pack = V_useful / V_vehicle_envelope

These metrics are useful for comparison but should not replace detailed range, thermal, crash and structural checks.

Architecture Freeze Is Not Geometry Freeze

A good architecture freeze establishes interfaces, envelopes, hardpoints and performance allocations while retaining local design freedom. Freezing detailed geometry too early can lock in poor load paths or manufacturing assumptions; freezing too little leaves every subsystem moving. The objective is controlled maturity, not premature certainty.

Design Inputs, Assumptions & Requirement Control

For Electric Vehicle Architecture & Platform Trade Studies, the analysis should begin with a controlled set of inputs rather than a geometry-first model. The key inputs include energy and peak-power duty, voltage/current limits, cell or source characteristics, conversion efficiency, temperature, degradation, reserve policy, protection thresholds and wiring/bus distribution losses. 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 time-domain energy integration and electrical network modelling, linked to thermal and degradation models so peak power, usable energy and lifetime are evaluated together. 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 Electric Vehicle Architecture & Platform Trade Studies include voltage collapse, overcurrent, thermal runaway or excessive temperature, capacity fade, imbalance, isolation loss, protection nuisance trips, inadequate eclipse/reserve energy or underestimated distribution loss. 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 time-domain energy integration and electrical network modelling, linked to thermal and degradation models so peak power, usable energy and lifetime are evaluated together. 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 cell/source characterisation, pack or power-system cycling, insulation and protection tests, load-bank tests and end-to-end duty-cycle correlation at representative temperature. 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 Electric Vehicle Architecture & Platform Trade Studies is that energy capacity should not be treated independently from power, temperature and ageing; nominal stored energy can be misleading when voltage, current or thermal limits make part of it unusable. 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.

Architecture Review Checklist

• All concepts satisfy the same vehicle-level requirements and mission assumptions.
• Occupant, battery, crash and suspension envelopes are represented simultaneously.
• Mass and thermal penalties are included, not only nominal efficiency.
• Service, assembly and repair implications have been considered.
• High-voltage architecture and charging route are compatible with the target market.
• Key interfaces can be configuration-controlled before detailed design.