3. Engineering Change Request (ECR) initiation

An Engineering Change Request is the formal entry point into the change management process. For restraint systems — airbags, seat belts, pretensioners, retractors, buckle assemblies, anchors, and the associated control electronics — an ECR is not merely an administrative form. It is the first structured risk gate, and the quality of information captured at initiation determines whether downstream activities (DFMEA updates, validation planning, PPAP impact assessment, regulatory re-certification) proceed efficiently or collapse into rework. This chapter focuses on how to initiate an ECR correctly: what requirements to capture, how to justify the change, how to identify affected parts, and how to perform a preliminary risk evaluation before the request enters formal review.

When an ECR Is Required

Not every modification needs a full ECR. A drawing note correction that does not alter form, fit, function, or regulatory compliance may be handled as a documentation change. However, an ECR is mandatory when any of the following apply to a restraint component:

• Change to a safety-critical characteristic (e.g., tear seam geometry, webbing elongation, retractor locking threshold, inflator output).
• Change of material, supplier, or manufacturing process for a component that affects deployment performance.
• Change to an interface dimension that affects assembly into the vehicle or mating with another restraint part.
• Change driven by a field issue, warranty trend, regulatory update, or customer requirement.
• Any change that could invalidate a previously completed FMVSS 208, FMVSS 209, FMVSS 225, or equivalent homologation test.

The trigger may originate from design engineering, manufacturing, quality, supplier, or the customer. Regardless of source, the ECR initiator owns the responsibility to capture the request with enough precision that reviewers can make an informed disposition decision.

Capturing the Requirement

The requirement statement must be specific, measurable, and traceable. Vague statements such as "improve airbag performance" are not actionable. A well-formed requirement identifies the parameter, the current value, the target value, and the source of the requirement. For example:

Requirement ID: ECR-2024-0317-R1
Component: Driver-side airbag module, P/N 62810-XXXX
Parameter: Tear seam opening force at -35°C
Current: 420 N ± 40 N
Target: 360 N ± 30 N
Source: Field return trend, cold-weather non-deployment (3 incidents, MY2022-2023)
Verification method: Component-level cold deployment test per internal spec ES-8821

Each requirement should be linked to its origin — a customer specification, an internal standard, a regulatory clause, or a field data reference. This traceability is essential when the change later undergoes verification and when auditors review the change history.

Justification and Business Case

Justification answers the question "why now?" It should address the driving factor, the consequence of not changing, and the expected benefit. Common justification categories for restraint components include:

• Safety/regulatory: Non-compliance with FMVSS or customer safety requirements.
• Field performance: Warranty data, incident reports, or customer complaints indicating a performance gap.
• Manufacturing: Process capability (Cpk) below target, excessive scrap, or assembly difficulty.
• Cost/availability: Obsolete components, supplier exit, or cost reduction targets.
• Vehicle integration: Interface changes driven by a vehicle-level design change.

The justification should include quantified evidence where available. For a field-driven change, cite the incident rate, population size, and severity. For a manufacturing-driven change, cite the Cpk value, scrap rate, or defect Pareto. This evidence forms the basis for prioritization and resource allocation.

Identifying Affected Parts

Restraint systems are highly integrated. A change to one component frequently propagates to mating parts, assemblies, and vehicle-level interfaces. The initiator must perform a structured impact scan across the following dimensions:

The output of this scan is a preliminary affected-parts list with part numbers, revision levels, and the nature of the impact. This list will be refined during the detailed impact assessment, but it must be sufficiently complete at initiation to scope the change.

Preliminary Risk Evaluation

Before the ECR enters formal review, the initiator performs a preliminary risk evaluation. This is not a full DFMEA — it is a rapid screening to identify high-risk changes that require escalated review or additional validation. A practical approach uses three factors:

1. Safety impact: Does the change affect occupant protection performance? (High/Medium/Low)
2. Regulatory impact: Does the change affect compliance with a regulated standard? (Yes/No)
3. Implementation complexity: How many parts, processes, or suppliers are affected? (High/Medium/Low)

A change with high safety impact and regulatory impact automatically triggers a full DFMEA review and validation plan update. A change with low safety impact and no regulatory impact may follow a streamlined path. The preliminary risk rating also determines the approval authority level required.

ECR Initiation Workflow

The following diagram illustrates the initiation workflow and the key decision points that determine whether an ECR proceeds to formal review or is redirected.

Practical Example: Seat Belt Retractor Locking Threshold Change

Consider a Tier 1 supplier receiving a field complaint that a retractor locks too early during normal driving on rough roads, causing occupant discomfort. The initiator captures the following:

• Requirement: Increase locking threshold from 0.45 g to 0.55 g vehicle deceleration at the retractor mounting point.
• Justification: 12 warranty claims per 10,000 vehicles; customer satisfaction metric below target; no safety non-compliance identified.
• Affected parts: Retractor assembly P/N 73210-XXXX, mounting bracket, and the vehicle-level anchor point (interface check required).
• Preliminary risk: Safety impact — Medium (locking threshold affects restraint performance); Regulatory impact — Yes (FMVSS 209 compliance must be re-verified); Complexity — Medium (one supplier, one assembly line).

Because regulatory impact is flagged, the ECR is routed to escalated review. The validation plan must include re-testing per FMVSS 209 and a confirmation that the new threshold does not compromise locking performance in emergency conditions. The initiator attaches the field data summary, the proposed threshold curve, and a preliminary test matrix.

Quality Criteria for ECR Initiation

A well-initiated ECR satisfies the following criteria:

• Completeness: All required fields are populated; no "TBD" in critical fields.
• Traceability: Each requirement links to a source document or data set.
• Scoping accuracy: Affected parts list is neither over-inclusive nor under-inclusive.
• Risk transparency: Preliminary risk rating is justified with reasoning, not just a label.
• Actionability: A reviewer can determine the next step without requesting additional information.

With the ECR properly initiated, the change enters the formal review and disposition phase, where cross-functional teams evaluate feasibility, cost, timing, and validation requirements. The quality of the initiation package directly determines how smoothly that phase proceeds.