4. Load case definition for restraint optimization

Restraint system optimization is only as meaningful as the load cases it is evaluated against. A restraint system that performs well in a 56 km/h frontal barrier test but allows excessive chest deflection in a 32 km/h oblique pole impact is not optimized — it is overfitted to a single event. This chapter defines how to construct a complete, defensible load case matrix covering frontal, side, rear, and rollover scenarios, how to select the crash pulse that drives each simulation, and how to specify boundary conditions so that results are comparable across design iterations.

Why Load Case Definition Precedes Optimization

In an optimization loop, the objective function and constraints are derived directly from occupant injury criteria evaluated under specific load cases. If the load case set is incomplete or the pulses are inconsistent between baseline and candidate designs, the optimizer will exploit the gap — for example, by softening a restraint to reduce frontal chest acceleration while silently degrading side impact performance. A rigorous load case definition therefore serves three purposes: it bounds the design space, it ensures regulatory and consumer-rating coverage, and it provides a stable reference for comparing restraint variants.

A practical load case matrix for a passenger vehicle typically includes the following categories:

Frontal Load Cases: Pulse Selection and Boundary Conditions

Frontal pulses are the most mature part of the load case library, but they are also the most frequently misapplied. The two dominant inputs are the rigid barrier pulse (a vehicle-level deceleration history measured at the B-pillar or rocker) and the sled pulse (a simplified acceleration profile applied to a sled fixture). For restraint optimization, the sled pulse is preferred because it decouples the restraint performance from body structure deformation, allowing rapid iteration.

When selecting a frontal pulse, three parameters matter most:

• Delta-v (Δv): The velocity change the pulse must produce. For a 56 km/h full frontal, Δv ≈ 56 km/h; for a 64 km/h ODB, Δv is typically 60–64 km/h depending on vehicle mass and barrier engagement.
• Peak acceleration and time to peak: A stiffer vehicle produces a higher peak (e.g., 40–50 g) with a shorter rise time (30–50 ms). A softer front end produces a lower peak (25–35 g) with a longer duration.
• Pulse shape: Square, half-sine, and trapezoidal pulses produce different occupant kinematics. The trapezoidal pulse with a controlled rise is generally recommended for restraint tuning because it avoids unrealistic jerk at onset.

Boundary conditions for a frontal sled model include seat position (fore-aft and recline angle), belt anchorage locations, steering column angle and collapse force, and knee bolster stiffness. These must be held constant across all restraint variants; otherwise, the optimization will attribute structural differences to the restraint design.

Side Load Cases: Barrier Face and Door Intrusion

Side impact load cases are fundamentally different from frontal cases because the restraint system (side airbag, curtain airbag, seat-mounted thorax bag) interacts with a deforming door and a moving barrier. The two primary inputs are the moving deformable barrier (MDB) force-deflection characteristic and the door intrusion velocity profile.

For a 50 km/h MDB test (ECE R95 / FMVSS 214), the barrier face is modeled with a honeycomb material that produces a specific force-deflection curve. The door intrusion profile is extracted from a full-vehicle simulation or test and applied as a prescribed motion to the inner door panel in the sled model. The restraint optimization then focuses on:

• Airbag deployment timing relative to door intrusion onset.
• Bag pressure and venting to balance chest deflection against head containment.
• Seat-mounted side airbag coverage relative to the occupant's rib cage and pelvis.

For the 32 km/h oblique pole test, the boundary conditions include vehicle yaw rate and lateral acceleration, which cause the occupant to move forward and laterally into the pole. The pole is rigid, so the restraint must absorb energy without relying on door deformation.

Rear and Rollover Load Cases

Rear impact load cases are dominated by seatback strength and head restraint geometry. The pulse is typically a moving barrier rear impact at 50 km/h, producing a Δv of 30–40 km/h on the struck vehicle. The key injury metric is neck injury criterion (NIC) and seatback moment. For restraint optimization, the rear case is often used to verify that the seatbelt pretensioner and load limiter do not cause excessive forward excursion of the head into the seatback.

Rollover load cases are the least standardized. The FMVSS 208 dolly rollover applies a lateral acceleration pulse followed by a vertical drop, while the roof crush test (FMVSS 216) applies a quasi-static load to the roof. For restraint optimization, the rollover case is primarily used to evaluate curtain airbag deployment and occupant ejection mitigation. The boundary conditions include the vehicle's roll angle, roll rate, and the timing of curtain airbag deployment relative to the occupant's head trajectory.

Integrating Load Cases into the Optimization Workflow

The load case matrix should be defined before any restraint parameter is varied. A practical workflow is:

1. Select the regulatory and consumer-rating load cases that apply to the vehicle's target markets.
2. For each load case, define the pulse, boundary conditions, and injury metrics with tolerances.
3. Run a baseline simulation with the current restraint design and record all metrics.
4. Define the optimization objective as a weighted sum of normalized injury metrics across all load cases.
5. Constrain the optimization so that no load case exceeds its regulatory limit.
6. Iterate restraint parameters (belt force limit, airbag pressure, vent size, deployment timing) and re-evaluate all load cases simultaneously.

The SVG below illustrates the load case matrix and the flow of inputs into the restraint optimization loop.

Key Takeaways

• Load case definition must precede restraint optimization; otherwise the optimizer will exploit gaps in coverage.
• Frontal pulses are defined by Δv, peak acceleration, rise time, and shape; boundary conditions must be held constant across variants.
• Side impact requires both barrier face characteristics and door intrusion profiles; oblique pole adds yaw and lateral acceleration.
• Rear and rollover cases are often overlooked but are critical for seatback strength, head restraint geometry, and ejection mitigation.
• The optimization loop must evaluate all load cases simultaneously, with constraints derived from regulatory and consumer-rating limits.