2. Regulatory and consumer rating landscape

An occupant safety program does not operate against a single specification. It operates against a portfolio of mandatory regulations and voluntary consumer rating programs, each with its own test matrix, injury criteria, thresholds, and — critically — its own timing relative to vehicle development. The program manager's job is not merely to know these requirements exist, but to place each one on the milestone timeline so that hardware, sled bucks, and full vehicles are available when the relevant test must be run. Late discovery of a rating requirement is one of the most expensive failure modes in body structure and restraint development.

The Two Families: Regulation and Rating

FMVSS (Federal Motor Vehicle Safety Standards) and ECE regulations (United Nations Economic Commission for Europe, often cited through UN R-numbers) are mandatory. A vehicle cannot be sold in the respective market without demonstrating compliance, typically through self-certification (FMVSS) or type approval (ECE). NCAP programs — Euro NCAP, C-NCAP (China), and the U.S. NCAP — plus IIHS are voluntary consumer information programs. They do not block sales, but a poor star rating or a "Poor" IIHS rating directly damages market position, insurance cost, and brand equity. In practice, most global programs treat top NCAP and IIHS performance as a hard internal requirement even though it is legally voluntary.

The distinction matters for milestone planning because the two families have different test objects, different lead times, and different tolerance for design change. A regulation test is usually a pass/fail gate with a defined compliance path. A rating test is a scored continuum where a few millimeters of intrusion or a slightly high chest deflection can drop a star, so it demands more iteration and more prototype vehicles.

Requirement-to-Milestone Mapping

The core planning instrument is a matrix that places each requirement against the program's gate structure. A typical passenger-car program runs through concept, A-surface freeze, body-in-white (BIW) design freeze, mule build, prototype build phases (often P1, P2, P3), tooling kickoff, and start of production (SOP). The table below shows a representative mapping; exact gate names vary by OEM, but the logic is stable.

Two patterns emerge from this mapping. First, structural requirements (side impact, roof strength) must be resolved earlier than restraint requirements, because body structure is locked at BIW freeze and changes after that are extremely costly. Second, rating programs generally require more vehicles and later confirmation than regulations, because their scoring is finer and their protocols are revised more frequently.

Why the Test Object Determines the Schedule

A frequent planning error is to assume all requirements can be validated on the same prototype build. They cannot. Sled tests for restraint tuning need a body buck and a sled pulse, not a running vehicle, and can start as early as the mule phase. Full-vehicle frontal and side tests need a complete, representative vehicle with production-intent structure, airbags, and seat belts. IIHS roof strength and side tests need specific hardware configurations that may not exist until P2. Euro NCAP's moving progressive deformable barrier (MPDB) test requires a compatible barrier and a vehicle mass representative of production.

The practical consequence is that the program must reserve prototype vehicles by requirement, not by phase. A common approach is to allocate a fixed number of vehicles per gate per requirement family, with a contingency pool for retests. If a side impact test at P1 shows excessive B-pillar intrusion, the fix must be designed, built, and retested before BIW freeze — which means the contingency vehicle must be available within weeks, not months.

Injury Criteria and Thresholds as Design Targets

Each requirement defines injury criteria that become engineering targets. For frontal impact, the Head Injury Criterion (HIC), chest deflection, and femur load are typical. For side impact, the key metrics are rib deflection, abdominal force, and pelvic force, often expressed through the WorldSID or ES-2re dummy. Euro NCAP and C-NCAP add scoring bands, so the design target is not merely "below the limit" but "in the top band."

For example, FMVSS 208 sets a HIC limit of 700 for the 50th percentile male in a belted frontal test. Euro NCAP awards full points only when HIC is well below that, and penalizes higher values progressively. A program targeting five stars therefore designs to a HIC target of roughly 500–600, not 700. This margin is not optional; it absorbs production variation, dummy positioning tolerance, and test-to-test repeatability.

Regional Differences That Affect the Plan

FMVSS and ECE differ in dummy selection, test speed, and barrier design. FMVSS 208 includes an unbelted test condition that ECE R94 does not, which forces restraint systems to manage an occupant without belt load — a significant design constraint. ECE R94 uses a 40% offset deformable barrier at 56 km/h, while Euro NCAP's frontal MPDB runs at 50 km/h with a progressive barrier and a mobile deformable element, producing different loading paths. C-NCAP has historically aligned more closely with Euro NCAP but maintains its own scoring weights and has introduced far-side occupant protection requirements.

IIHS is distinct in two ways: its moderate overlap test uses a 40% overlap at 64 km/h, and its side test uses a heavier moving deformable barrier (1,500 kg) at 50 km/h, which is more severe than FMVSS 214's barrier. IIHS also introduced the updated side test with a higher barrier and a different strike point, which has driven significant B-pillar and door trim redesign across the industry.

For a global program, the practical approach is to identify the most severe requirement in each load case and design to that, then verify compliance with the less severe regional variants. This "worst-case envelope" strategy reduces the number of unique hardware configurations, though it can add mass if not managed carefully.

Building the Compliance and Rating Plan

The deliverable that ties this together is a compliance and rating plan, owned by the safety program manager and reviewed at each gate. It should contain, at minimum:

• Requirement register: every applicable FMVSS, ECE, NCAP, and IIHS test, with the market it applies to and the responsible engineer.
• Test object definition: sled buck, mule, P1/P2/P3 vehicle, or production vehicle, with the configuration (dummy, restraint variant, mass).
• Milestone alignment: the gate by which each test must be completed, and the gate by which any required design change must be frozen.
• Vehicle allocation: number of vehicles per test per gate, plus contingency.
• Target values: not just pass/fail limits but the design targets that provide margin for production variation.
• Risk log: requirements with uncertain protocols, pending regulatory changes, or tight timing.

Common Failure Modes and How to Avoid Them

The most common program-level failures are not technical but scheduling-related. A side impact requirement discovered after BIW freeze forces either a mass-adding reinforcement or a late structural change, both of which cascade into other attributes. A rating test scheduled too close to SOP leaves no time for a retest if the first result misses the target band. A regional variant that was assumed to be covered by the global design turns out to have a unique barrier or dummy requirement.

The mitigation is early and explicit mapping. Before the first mule is built, the program should be able to state, for every applicable requirement, which test object will be used, at which gate, and what the design target is. If any of those three cannot be answered, the requirement is a risk and should be escalated. This discipline is what separates a program that passes its safety gates on schedule from one that spends its final year in reactive retesting.