📚 Course ContentsChapter 4 Test configuration definition

4. Test configuration definition

Before a single ballast block is bolted into a body-in-white, the test configuration must be frozen. Configuration definition is the translation layer between a regulatory or consumer-protocol requirement and the physical state of the vehicle on the day of the test. Get it wrong, and a perfectly executed impact produces a result that cannot be homologated, compared, or defended. This chapter covers three linked decisions: which crash mode to run, what mass and inertia targets apply, and how the chosen standard becomes a written preparation specification that the workshop can execute without interpretation.

Selecting the crash mode

Crash mode selection is driven by the certification or rating program the vehicle must satisfy, not by preference. A European passenger car typically faces a portfolio spanning frontal offset (UN R94 / Euro NCAP MPDB), side impact (UN R95 / AE-MDB), rear impact (UN R34), and pedestrian protection (UN R127 / GTR 9). Each mode imposes different preparation consequences, and those consequences are what the preparation engineer must extract.

The critical distinction is between full-vehicle barrier tests and sled or component tests. A frontal offset test requires the complete vehicle at its certified test mass with restraint systems live; a pedestrian test requires the vehicle at its normal ride height with a specific front-end geometry and no ballast that would alter the bonnet leading edge. A rear impact test per UN R34 uses a moving barrier and evaluates fuel system integrity, so the preparation emphasis shifts to fuel tank condition and filler neck integrity rather than occupant restraint calibration.

Mode selection also determines the impact reference frame. For frontal tests, the longitudinal axis (X) is the primary load path and the vehicle is aligned to the barrier within a stated tolerance. For side impact, the lateral axis (Y) dominates and the struck-side door, sill, and B-pillar become the critical preparation surfaces. For pedestrian tests, the vertical axis (Z) and the bonnet surface geometry govern. Establishing the coordinate convention early — X forward, Y left, Z up, origin at the vehicle datum — prevents the alignment and ballast-placement errors that plague poorly specified programs.

Target mass and inertia requirements

Every protocol defines a test mass, and that mass is rarely the kerb mass. UN R94 specifies the mass in running order plus a defined occupant and luggage allowance; Euro NCAP frontal testing uses the vehicle mass in running order plus 100 kg of ballast distributed to represent occupants. The preparation engineer must convert the protocol's mass definition into a measurable target with a tolerance, typically ±1% or a stated absolute value.

Mass alone is insufficient. Inertia — particularly the yaw moment of inertia about the vertical axis and the pitch moment about the lateral axis — governs how the vehicle rotates during impact and therefore how the restraint system and structure load. A vehicle that meets the mass target but has ballast concentrated at the rear will pitch differently from one with ballast distributed at the occupant positions. The specification must therefore state both the total mass and the ballast distribution, usually expressed as masses at defined longitudinal and lateral stations.

A practical approach is to build a mass budget before the vehicle is weighed. The budget lists kerb mass, fuel load (typically a defined fill level, often 90% or a specified volume), coolant and lubricants at service fill, occupant ballast at each seating position, and luggage ballast in the boot. The sum must land within tolerance of the protocol target. If the kerb mass is already above target — common with heavy battery-electric vehicles — the specification must state how the excess is handled, for example by removing optional equipment or by accepting the protocol's higher mass band.

Record the mass budget and the as-tested mass on the same form, with the scale identification and calibration date. A mass figure without traceability to a calibrated scale is not evidence.

Translating the standard into a preparation specification

The preparation specification is the document the workshop works from. It should be written so that a technician who has never read the regulation can still produce a conforming vehicle. The specification typically contains: the applicable protocol and clause references; the crash mode and impact configuration; the target mass with tolerance and the ballast schedule; the fuel and fluid state; the tyre specification and inflation pressure; the restraint and safety-system state (live, disabled, or replaced with dummy loads); the instrumentation and sensor mounting provisions; and the acceptance checks to be performed before release.

Consider a worked example. A mid-size sedan is prepared for a Euro NCAP frontal offset test. The protocol requires the vehicle mass in running order plus 100 kg ballast. The measured kerb mass is 1,485 kg with a 90% fuel fill. The mass budget allocates 75 kg to the driver position, 15 kg to the front passenger position, and 10 kg to the rear seat, giving a target of 1,585 kg ± 1% (1,569–1,601 kg). The workshop weighs the vehicle after ballast installation and records 1,592 kg — within tolerance. The specification then requires a four-wheel alignment check, tyre pressures set to the protocol value, and a restraint-system continuity check before the vehicle is released to the test cell.

The specification must also capture the as-built deviations. If a component was removed to meet the mass target, or if a sensor was relocated to clear a ballast block, that deviation is recorded with its justification. Undocumented deviations are the most common cause of a test being rejected at the data-review stage, because the test house cannot demonstrate that the vehicle matched the certified configuration.

Common failure modes and how to catch them

Three configuration errors account for most rejected or invalid tests. First, mass target mismatch: the vehicle is weighed before the fuel fill is finalized, or the ballast is installed but not re-weighed. Symptom: as-tested mass outside the ±1% band, or a mass that matches but with ballast in the wrong stations. Fix: weigh after every ballast change and record the scale reading, not the calculated value.

Second, mode-specific preparation leakage: a pedestrian test vehicle is prepared with the ride height lowered for a frontal test, or a side-impact vehicle carries ballast that intrudes into the struck-side door cavity. Symptom: geometry or clearance check fails at the test cell. Fix: the specification should list mode-specific prohibitions explicitly, not just the positive requirements.

Third, undocumented deviation: a sensor bracket is relocated, a trim panel is removed for clearance, and the change is not recorded. Symptom: data review cannot reconcile the as-tested configuration with the certified build. Fix: a deviation log with a mandatory justification field, reviewed and signed before release.

A configuration that is internally consistent but not traceable to the protocol clause is not a valid test configuration. Every mass figure, ballast position, and deviation must point back to a specific requirement.

Closing the loop

Configuration definition ends when the preparation specification is signed and the vehicle passes its pre-release checks. The specification should be treated as a controlled document: versioned, linked to the protocol revision, and updated when the protocol changes. The mass budget, the as-tested mass record, and the deviation log travel with the vehicle into the test cell and become part of the test report. When the impact data is reviewed weeks later, those three documents are what allow the engineer to state, with confidence, that the vehicle on the barrier was the vehicle the standard intended.