Test plans organised by the stage and scenario our clients are in. The same laboratory capability is applied in completely different ways depending on the stage.
Choose by stage
Development stage → R&D scoping tests: the goal is to find problems while the cost of a change is still low.
Choose by scenario
Exporting to the EU → export certification: the CE / ECE R10 test package.
Why the stage matters
At the development stage the job is to find problems; a scoping test is enough and the cost of being wrong is low.
Service notes
The laboratory holds both CMA and CNAS accreditations, with approximately 10,000 m² of space and 500+ instruments. All testing is completed in our own laboratories — no subcontracting. On-site visits and witnessed testing are supported.
Testing is scheduled per project. When submitting samples, tell us your expected timeline; we will confirm a feasible plan against current availability and keep you updated at each milestone.
What each of the five plans solves
R&D scoping tests (DV/PV) — find problems at the design stage, absorbing risk while a board respin is still cheap; Sample submission and third-party testing — independent third-party data to support customer acceptance and supply-chain audits; Export certification — test data and certification files prepared for the destination market; Tier-1 / OEM validation — validation against the OEM technical agreement, with the report format aligned; Mass-production QA — ongoing verification of production batches to catch process drift. All five share the same laboratory capability; only the way the plan is organised differs.
Positioning the plan by target market
Exporting to the EU → export certification (ECE R10 / CE test package, see ECE R10); a domestic vehicle platform → environmental and electrical tests organised per GB/T 28046 / ISO 16750; a German supply chain → conditions per LV 124; electronic components going into a vehicle → AEC-Q reliability qualification. The target market decides the standard family, and the standard family decides the test matrix.
Not sure which type to start with
Three things are enough: what stage the product is at (schematic, prototype, mass production), where it will be sold (China / EU / elsewhere), and whether a standard or a customer agreement is already specified. Engineers match the plan from those three inputs and can give the test matrix and a cost framework in the first conversation.
How a plan becomes a project
Each plan page describes the typical approach and the common problems at that stage. Before execution there are still three steps: engineers confirm the test matrix and sample requirements and issue a written test plan; both sides confirm scheduling and sample delivery; testing runs with data shared at each milestone. The written plan can be used directly as the basis for internal project approval and budget requests. If the applicable standard is already known, you can go straight from the corresponding standard page to the list of test items.
