As a Tier 1 supplier, the validation requirements are led by the OEM. The key is to align on the test plan and report requirements in advance, so nothing is returned for a format or condition mismatch.
Characteristics of OEM validation
- OEM-led: the test plan is set by the OEM specification or technical agreement, and the supplier executes it as required.
- Report acceptance: confirm whether the OEM accepts third-party laboratory reports, and check the approved list.
- Witnessing: some OEMs require on-site witnessing for key items.
- Format requirements: report format, language and signatures may be specified.
Common problems and how to handle them
- Standard version mismatch: the customer requires the new version, testing was run to the old one, and rework follows. Confirm the version number at the planning stage.
- Sample state mismatch: the vehicle state the customer requires differs from what was actually supplied. Define the sample state in advance.
- Report format mismatch: the OEM has a template requirement. Request the template in advance.
- Missing test conditions: some items have special conditions in the customer corporate standard. Check the technical agreement clause by clause.
Examples of differences between OEMs
- German OEMs: usually cite LV 124, with severity above the national standard.
- Japanese OEMs: have their own requirements on top of the JASO system.
- Domestic brands: mostly use national standards, with their own corporate standards layered on.
- The technical agreement of the target OEM governs.
Service notes
Our laboratory holds both CMA and CNAS accreditation, covers about 10,000 m2 and runs more than 500 sets of equipment. All testing is carried out in our own laboratories — nothing is subcontracted. Plant visits and on-site witnessed testing are welcome.
Scheduling follows the actual project pipeline. You can state your preferred lead time when you submit samples; we will confirm a feasible plan against current capacity and keep you updated at each milestone.
Test plan alignment checklist
What goes wrong in Tier 1 validation is rarely the testing itself; it is misalignment of information between the two sides. Confirm item by item before submission: the standard version number, since OEM specifications often cite a custom corporate version; condition levels and acceptance criteria, including whether functional status is defined in the same version; sample quantity and delivery milestones; report format, language and signature requirements; witnessing requirements and the form of data delivery, including whether raw data accompanies the report. Agreeing the checklist before scheduling significantly reduces rework.
Supporting witnessed testing
For items the OEM requires to be witnessed, the laboratory locks the test window in advance and prepares raw-record templates; on the day, the setup drawing, monitoring points and data acquisition can be reviewed together. Where attendance is not possible, photographic records and a process data package can be arranged, with the form confirmed with the OEM beforehand.
Handling failed items
A failed validation does not end the project: locating the root cause, which can lead into failure analysis, verifying the corrective action, and resubmitting is the standard path. Whether a corrective plan or a concession release is accepted is the OEM decision; the laboratory role is to supply data that supports that decision — failure evidence, boundary conditions and re-test comparison all go into the report.
