2026-11-17 14:13:12Motor / Webasto / Raildelivery Group

I. Responsibility Determination Is the Precondition for Recovery to Work
The consensus in industry discussions is that the effectiveness of a recovery mechanism depends on confidence in the root-cause determination. When suppliers push responsibility back to the manufacturer, question the test methods, or do not accept the analysis results, recovery often becomes a lengthy negotiation rather than a data-based decision. Differing test methods, uneven levels of engineering support, and inconsistent documentation standards all delay recovery decisions.
Contract wording alone cannot prevent disputes. The people who negotiate supply contracts are often not the same people who handle recovery years later; suppliers also usually do not truly grasp the real impact of provisions such as dealer labor rates and handling fees until claims have accumulated. Clear test requirements, engineering involvement, and consistent analysis standards are therefore seen as ways to reduce disputes.
II. Differences in Recovery Models and Points of Dispute
The following summarizes several recovery models that came up in the discussions.
| Model | Approach |
| Default ratio or technical factor | While returned-part analysis is under way, an initial recovery ratio is applied first; once enough samples have accumulated, a technical factor is determined and applied to subsequent claims |
| Pre-agreed sharing ratio | The supplier's share is agreed in advance according to the type of warranty coverage |
| Deferred recovery | Recovery is made only after detailed analysis confirms technical responsibility |
Billing frequency also differs: some organizations bill monthly and rely on highly automated systems; others bill quarterly and rely more on manual review and negotiation.
The most contested situation is secondary damage. Suppliers are usually willing to take responsibility for the failed part, but when the failure of a low-priced part involves a high-value system such as the engine, transmission, or battery, the dispute shifts from whether the part failed to whether the supplier should bear the entire financial impact. The definition of recoverable cost is also a point of contention: some organizations calculate the full amount of the warranty claim, including parts, labor, and dealer handling fees; others deduct part of the margin and add costs that do not appear on the claim ledger.
III. Why Can't the Fault Be Found
Another difficulty in responsibility determination is that the supplier finds no fault after testing. Practical guidance from the rail vehicle industry notes that such cases consume the limited time and resources of multiple companies yet often yield no conclusion about the cause of failure, and because of how data is collected, their impact on operations is hard to quantify. The following summarizes causes and recommendations according to that guidance.
| Cause Type | Description | Recommended Practice |
| Behavior and process | After preventive replacement, parts are sent back without verifying whether there was actually a fault; mutual distrust makes parties unwilling to fully share failure information | Isolate the suspect part first and see whether the fault recurs before sending it back; hold regular technical and commercial meetings |
| Information flow | Failure symptoms and diagnostic records are lost in the return process, so the supplier cannot diagnose | Agree a minimum standard for returned-part information, and update claim document templates |
| Traceability | Parts have no serial number, or the serial number is changed by the supplier without the user's knowledge, making repeat failures hard to identify | Mark parts with a unique and durable serial number, and establish control over serial number changes |
| Test conditions | The supplier performs only electrical tests without reproducing the actual operating environment; the test process may erase asset history data | Agree test specifications in advance, simulate the field environment using vibration, climatic chambers, etc., and back up data before testing |
Another recommendation is that the two sides agree test specifications first, carry out a joint investigation when necessary, and fold what is learned from the investigation into everyday practice.
IV. Reducing Disputes with Explicit Rules: One Automotive Parts Supplier's Approach
The supplier guideline (2020 edition) of an automotive parts company shows how to write these issues into rules. It requires suppliers to:
The guideline also lists the conditions for initiating the NTF process, for example an NTF rate above 20% (at least 10 cases per part number per half-year), the production ramp-up period (within 6 months after start of production), customer request, downtime events, rising trends, or product safety involvement. This is one company's requirement for its own suppliers, not a general industry standard.
Conclusion
Disputes over responsibility determination mostly arise from data and rules, not the technology itself: whether information reaches the supplier completely, whether testing is close to field conditions, and whether time limits and costs are made clear in advance. Writing these into processes and contracts allows recovery to shift from negotiation to data-based decisions.
Sources:
Declare:The sources of contents are from Internet,Please『 Contact Us 』 immediately if any infringement caused