2. Regulatory and consumer rating landscape

A DVP&R plan is only as good as the requirement set it is built against. For crashworthiness and occupant restraint systems, that requirement set is not a single document but a layered landscape: legally mandated regulations that define the minimum acceptable performance, and consumer rating programs that define the competitive target. The two layers differ in legal force, test protocol, injury criteria, and — most importantly for planning — in how much freedom they leave the OEM to choose its own test matrix. A restraint engineer who treats "passing FMVSS" and "achieving 5-star Euro NCAP" as the same kind of requirement will build a plan that is either over-constrained in the wrong places or dangerously thin in others.

Two layers with fundamentally different logic

Regulations (FMVSS in the United States, UN ECE Regulations under the 1958 Agreement in Europe and most other markets) are pass/fail. They specify a fixed test configuration, a fixed dummy, fixed injury criteria, and a fixed threshold. The OEM has no choice about the test: a frontal impact is performed at the regulated speed, with the regulated barrier, and the regulated dummy. The DVP&R implication is that regulatory tests are non-negotiable, fully specified, and identical for every competitor. They belong in the plan as mandatory verification items with a binary acceptance criterion, and they must be scheduled early enough that a failure can still be corrected before type approval or self-certification.

Consumer rating programs (Euro NCAP, C-NCAP, IIHS, and the U.S. NCAP under NHTSA) are voluntary but commercially decisive. They publish star ratings or awards that directly influence purchase behavior, fleet procurement, and insurance grouping. Their protocols are revised on a roughly three-year cycle, they add new test configurations faster than regulations do, and they increasingly reward active safety and post-crash performance alongside structural performance. The DVP&R implication is the opposite of the regulatory case: the OEM must decide which rating to target, in which market, at which protocol revision, and then translate that target into a set of internal test configurations that may be stricter than the published protocol.

The principal programs and what each one actually tests

The table below summarizes the programs most relevant to a global restraint DVP&R. Speeds and criteria are indicative of current protocol generations and must always be confirmed against the latest published revision before being written into a plan.

Where the programs diverge — and why it matters to the plan

Three divergences drive most of the planning complexity. First, barrier and overlap geometry: FMVSS 208 uses a full rigid barrier and a 40% offset deformable barrier, IIHS adds a 25% small overlap against a rigid pole-like barrier, and Euro NCAP's frontal assessment is built around the mobile progressive deformable barrier. A body structure tuned only for the 40% ODB can pass regulation and still fail the IIHS small overlap, because the load path through the wheelhouse and A-pillar is completely different. The DVP&R must therefore contain separate structural load cases for each overlap geometry, not a single "frontal" line item.

Second, dummy and injury criteria. FMVSS 208 frontal assessment still relies heavily on the Hybrid III family, while Euro NCAP has migrated frontal assessment toward the THOR dummy and side assessment toward WorldSID. THOR measures different channels — for example, more detailed chest deflection and abdominal pressure — and its biofidelity changes the pass/fail boundary for the same physical event. A restraint system calibrated to Hybrid III responses may need re-tuning before it can be scored under THOR. The plan must specify the dummy model per test, because "frontal impact, 56 km/h" is not a complete test definition.

Third, scope beyond crash. Euro NCAP and C-NCAP now allocate a substantial share of the score to active safety (AEB, lane support), vulnerable road user protection, and post-crash rescue information. IIHS awards require front crash prevention ratings. These items are not restraint-system tests in the classical sense, but they consume DVP&R budget and schedule, and they interact with restraint calibration — an AEB intervention changes the impact speed and therefore the restraint firing strategy. The plan should treat them as a separate verification stream with its own owners, not as an afterthought appended to the crash matrix.

Translating the landscape into DVP&R line items

The practical work is to convert each program into test lines that carry enough information to be executed and judged. A well-formed line item for a crash test contains at minimum: the program and protocol revision, the test configuration (barrier type, overlap, impact speed, impact angle), the dummy model and seating position, the restraint state (belted/unbelted, airbag enabled/disabled), the acceptance criterion with its threshold and margin, the facility, and the evidence to be retained. A line that says only "frontal crash — pass" is not verifiable and will not survive a design review.

Consider a concrete example. A program targeting both Euro NCAP and C-NCAP for a mid-size SUV would generate, among others, the following distinct lines for the frontal event alone:

DVP-208-F1  FMVSS 208  Full rigid barrier, 56 km/h, Hybrid III 50th, driver belted
            Criterion: HIC15 <= 700, chest defl <= 63 mm, Nij <= 1.0
            Facility: FMVSS-conformant sled/buck + full vehicle
            Evidence: high-speed video, filtered accel channels, dummy cert

DVP-208-F2  FMVSS 208  Full rigid barrier, 56 km/h, Hybrid III 50th, driver UNBELTED
            Criterion: same thresholds, plus occupant excursion envelope
            Note: unbelted case drives airbag venting and knee-bolster design

DVP-EN-F1   Euro NCAP  MPDB 50% overlap, 50 km/h, THOR 50th, driver + passenger
            Criterion: scored; target chest deflection margin >= 15% below 5-star cut
            Facility: Euro NCAP accredited lab
            Evidence: THOR channel set per protocol annex

DVP-CN-F1   C-NCAP     Full rigid barrier, 50 km/h, Hybrid III 50th, driver
            Criterion: HIC15 <= 650, chest defl <= 55 mm (per current C-NCAP)
            Note: separate calibration from FMVSS 208 due to speed and criteria

DVP-IIHS-F1 IIHS      25% small overlap, 64 km/h, Hybrid III 50th, driver
            Criterion: structural intrusion <= 150 mm at lower hinge pillar;
                       HIC15 <= 700; femur <= 4 kN
            Note: load path through wheelhouse and A-pillar; not covered by FMVSS

Two observations follow from this fragment. First, the same physical event — a frontal impact — produces five lines with different speeds, dummies, and criteria. They cannot be collapsed into one test, and a single restraint calibration will not satisfy all of them without compromise; the plan must therefore include calibration iterations as explicit activities, not just final verification tests. Second, the IIHS small-overlap line has no regulatory counterpart, which means it will be dropped from the plan unless someone deliberately adds it. That is the most common failure mode in restraint DVP&R: the plan mirrors the regulation because the regulation is written down, and silently omits the consumer tests that are not.

Protocol revision control

Consumer programs revise their protocols on a published cadence, and a vehicle certified to one revision may be re-rated under the next. The DVP&R must therefore pin the protocol revision for every scored line and record the date of the published document. When a revision is announced mid-program, the change control question is not "does the vehicle still pass?" but "which lines change, which calibration activities are invalidated, and what is the schedule impact?" A revision that adds a far-side occupant test, for example, invalidates any calibration done without a far-side airbag and adds a new structural and restraint load case. Building a small revision-impact table into the plan — program, revision, affected lines, re-test required — keeps this manageable.

What the plan should look like at the end of this step

By the close of the requirement-definition phase, the DVP&R should contain three clearly separated streams: mandatory verification lines with binary criteria and fixed configurations; scored target lines with pinned protocol revisions and explicit margins; and market-specific structural lines covering geometries that no regulation requires. Each line should name its dummy, its restraint state, its facility, and its evidence. The next planning step — allocating these lines to buck tests, sled tests, full-vehicle tests, and CAE correlates — depends entirely on this separation being clean, because a mandatory line and a scored line have different tolerances for schedule slip and different consequences when they fail.