Two ways a programme starts
The first is selection: we propose the closest published model and modify it — circuit count, connectors, CAN / J1939 role, sealing class, housing and mounting. That covers most enquiries and it is the fastest route to a sample, so it is what our four product families and RFQ checklist are built around.
The second is design: no platform fits, so we design the part from your requirement and carry design responsibility for it. Buyers usually call that ODM. IATF 16949 calls it being design-responsible. They describe the same arrangement, and this page is about that second path — what we can commit to, how the project runs, and what we need from you before it can be quoted.
The catalogue is the portfolio
The clearest evidence that we can design a new part is the catalogue itself. There are 91 models with published detail pages across power distribution, control modules, switches and sensors, and displays and HUD, plus catalogue variants that are not individually published. Those platforms are our own designs — we own the schematic, the PCB, the housing and the firmware.
That covers software as well as hardware. Firmware for our switch, power-distribution and instrument platforms is written by our own engineering team, and that firmware is registered on China's national software copyright register in the company's own name — central-console switch control, fireproof and smart power-distribution-box monitoring and control, TPMS receiver and transmitter, CAN-bus test and control, and CAN-bus cluster simulation and display. A registration is a copyright record rather than a patent; eight of the certificates are shown on the quality page, and the current list with full PDFs goes out during supplier qualification.
On the hardware side the same team handles schematic and PCB design, enclosure and sealing design, and the connector and harness interface. Reverse and concurrent engineering, 3D modelling, virtual assembly and motion simulation are part of how development runs; the engineering clip on the about page shows that side of the floor.
What “design-responsible” says on the certificate
Our IATF 16949:2016 registration is not scoped to assembly only. The certified scope reads: the design and manufacture of electrical switches and controller assemblies, and the manufacture of printed circuit board assemblies. NQA certificate T195990, IATF certificate 0537625, IATF Unique Site Identifier 6PE2KE, valid through 12 August 2027 — you can confirm it is live in the IATF Customer Portal using the certificate number or the USI, and the IATF page reproduces the certificate itself.
Read the boundary as it is written. Design sits inside the scope for switches and controller assemblies; printed circuit board assemblies are in scope as manufacture. In practice that shapes who owns which risk document: where we are design-responsible, DFMEA is ours; where you own the design and we build it, you keep DFMEA and we own PFMEA. The OEM sourcing guide works through that split, along with APQP and PPAP levels.
How a new-design programme runs
- Requirement intake. Function, electrical interfaces and loads, network role, environment, mechanical envelope, target volume and SOP date. Drawings are welcome but not required — if you have none, a written requirement is enough to start.
- Feasibility and concept. We come back with what can be reused from an existing platform, what has to be new, the risks we can already see, and development cost and timing. Both are quoted per programme.
- Design. Schematic and PCB, enclosure and sealing, connector and harness interface, firmware. DFMEA and design reviews at the gates agreed at kick-off.
- Prototype and bench validation. Engineering samples, then environmental testing and EMC pre-compliance in our own laboratory. Formal EMC and type-approval testing is performed at third-party accredited laboratories when the programme requires it — see environmental and EMC testing.
- Design validation and PPAP. Submitted at the level agreed in your customer-specific requirements, not one fixed package on every programme.
- Production and change control. SMT and THT lines, in-process inspection, end-of-line functional test, traceable batch records. Later changes go back through the same gates the design came through.
What we need from you to quote it
The six information groups in the RFQ checklist are what engineering works from, and they apply to a new design as much as to a selection. For a new design the ones that decide feasibility are the function description, the electrical interfaces and loads, the network role, the environment the part lives in — temperature range, sealing class, vibration — the mechanical envelope and mounting, and the volume and timing you are planning against.
If you already have a complete drawing package and want it built as drawn, say so in the first message. That is a different quote: build-to-print, with design ownership staying with you.
Scope, and what we will not claim
We look at any commercial-vehicle or machinery electronics requirement rather than a fixed list of categories. Power distribution, control modules, switching, sensing, clusters and displays are where our platforms already are, but the first question we answer is whether we can build what your vehicle needs — not whether it fits a family page.
What we will not do is claim ground we have not covered. If a requirement needs something we have not built in production, we say so at the feasibility stage and tell you what would have to be developed, what it adds to cost and schedule, and what risk that carries. Market approvals — UNECE type approval and e-Mark where applicable, SASO for Saudi Arabia, FCC equipment authorisation — are supported per programme rather than claimed as blanket certification on the standard catalogue.
Commercial terms
Development is quoted per programme. Ownership of drawings, tooling and firmware is agreed in the contract. An NDA is available on request, and we would rather settle all three in the first commercial exchange than after a prototype exists.
Common questions
Do you take ODM projects, or only build to our drawings?
Both. If you send drawings and want them built as drawn, we quote build-to-print and you keep design ownership. If you send a requirement instead, we design the part and take design responsibility for it — the path most buyers call ODM.
Who owns the design, the tooling and the firmware?
It is agreed in the contract for each programme. We do not publish one fixed rule, because it depends on who funds the development and the tooling. Raise it in the first commercial exchange rather than after the prototype.
Can you design a part outside your four published product families?
We will look at any commercial-vehicle or machinery electronics requirement. Feasibility comes first: we tell you which parts of it we have already built in production and which parts would be new development, with the cost and schedule that adds.
Start a design enquiry
Send the requirement — or the drawings, if you have them — to [email protected] or message us on WhatsApp. Typical reply within one business day. If you would rather check the existing platforms first, the four product families and the buyer guides are the place to start, and the contact page has the rest of the routes in.