4. Barrier compliance criteria

In the Euro NCAP MPDB (Mobile Progressive Deformable Barrier) test, the barrier is not a passive prop but a calibrated measuring instrument. Every result — occupant deceleration, structural intrusion, compatibility scoring — is only meaningful if the barrier itself conforms to its reference specification at the moment of impact. Compliance therefore rests on three pillars: geometric accuracy (dimensional tolerances), inertial accuracy (mass distribution), and mechanical accuracy (static stiffness). This section explains what each criterion requires, how it is verified in practice, and how to interpret the verification data.

Why the Barrier Must Be Treated as a Calibrated Instrument

The MPDB barrier is a deformable aluminium honeycomb cartridge mounted on a moving trolley. Its face geometry defines the contact patch with the test vehicle; its mass properties define the momentum transferred during the 50 km/h impact; and its stiffness defines the force–deformation characteristic that the vehicle "sees." A deviation in any of these three domains shifts the crash pulse and can change star ratings by a meaningful margin. Consequently, compliance verification is performed at defined intervals — typically before each test campaign and after any barrier repair or cartridge replacement — and the results are recorded in the test facility's calibration log.

Dimensional Tolerances

Dimensional verification confirms that the barrier face presents the correct frontal geometry and that the cartridge is correctly seated on the trolley. The key controlled dimensions are the overall barrier width and height, the flatness of the impact face, the perpendicularity of the face to the trolley's longitudinal axis, and the ground clearance of the lower edge. The face flatness check is the most sensitive: a honeycomb cartridge that has been previously crushed or unevenly loaded may show local depressions that alter the contact onset time across the vehicle's front end.

In practice, flatness is checked with a straightedge and feeler gauge, or with a laser displacement sensor on a bridge across the face. A representative acceptance criterion used in many facilities is a maximum local deviation of ±2 mm from the reference plane across the central impact region, with the straightedge placed at several heights and lateral positions. Width and height are verified with a calibrated tape or laser distance meter against the nominal drawing dimensions, and perpendicularity is checked by measuring the distance from the face to a reference datum on the trolley at the top and bottom of the barrier; equal readings confirm the face is vertical.

Mass Distribution

Mass verification has two components: total mass and centre-of-gravity (CoG) location. The total mass of the trolley-plus-barrier assembly determines the momentum at impact speed, while the CoG position — particularly its height and longitudinal offset — determines the pitch moment applied to the test vehicle. A barrier that is correct in total mass but has its CoG too high will produce excessive vehicle pitch and can distort the compatibility assessment.

Total mass is measured by weighing the complete assembly on a calibrated platform scale, with the result compared to the nominal value and its tolerance band. CoG location is determined either by a dedicated CoG rig that supports the assembly on load cells at known positions, or by the classic four-point weighing method: the assembly is placed on four load cells arranged in a rectangle, and the CoG coordinates are computed from the reaction forces. For a rectangular arrangement with load cells at positions (x₁, y₁) … (x₄, y₄) and measured reactions W₁ … W₄, the longitudinal CoG is:

x_cog = (W1·x1 + W2·x2 + W3·x3 + W4·x4) / (W1 + W2 + W3 + W4)
y_cog = (W1·y1 + W2·y2 + W3·y3 + W4·y4) / (W1 + W2 + W3 + W4)

As a worked example, suppose the four load cells read 312 kg, 298 kg, 305 kg and 285 kg at positions forming a 1.2 m × 0.8 m rectangle. The total is 1200 kg, and the longitudinal CoG offset from the rectangle centre is computed directly from the weighted sum. If the result falls outside the drawing tolerance — commonly a few millimetres in each axis — the cause is usually ballast placement or a cartridge seated off its locating pins, and the assembly must be re-ballasted before the test.

Static Stiffness Verification

Static stiffness verification characterises the force–deformation behaviour of the deformable face. The barrier is loaded quasi-statically through a rigid indenter at a controlled rate, and the force is plotted against displacement. The resulting curve is compared with the reference characteristic for the barrier type. Two features matter most: the initial plateau force (the force at which the honeycomb begins to crush) and the energy absorbed up to a defined deformation, typically 150–200 mm.

A practical procedure is as follows. Mount the barrier rigidly against a reaction wall, align the indenter with the barrier centre, and apply displacement at a slow rate — on the order of 10–50 mm/min — while logging force and displacement at 100 Hz or better. Crush the face to the specified depth, then unload. Compute the absorbed energy as the area under the loading curve using trapezoidal integration, and compare both the plateau force and the energy against the acceptance band. A plateau force that is too high indicates an over-dense or aged cartridge; a plateau that is too low, or a curve with an early collapse, indicates a damaged or previously crushed cartridge that must be replaced.

Reading the Verification Record

The three verification domains are not independent. A cartridge that passes dimensional flatness but fails stiffness has likely been loaded in a previous test; a barrier that passes stiffness but shows a CoG shift has a ballast or seating problem. The verification record should therefore be read as a whole, with each result cross-checked against the others before the barrier is released for testing.

The diagram above shows how the three verification domains converge on a single release decision, and why a failure in one domain should prompt a cross-check of the others rather than an isolated re-test. In the next section, we move from verifying the barrier to preparing the test vehicle and trolley for the impact itself.