Home / Blog
Guide — components
Wiring harness design: specs buyers must confirm before ordering
A wiring harness is a drawing made physical, which means every harness dispute is a specification that was never written down. The catalogue's harness platform is unusually explicit — a shared specification envelope behind nine harness records — and it doubles as a checklist of what a buyer must confirm before ordering. Work through these seven items and a harness order becomes boring, which is the goal.
1. Wire gauge range and standard
The platform envelope runs from 10 AWG to 32 AWG — vehicle-class power leads at one end, signal wiring at the other. Confirm the gauge per circuit, not per harness, and name the wire standard: the record lists UL-listed types (UL1007, UL1015, UL1061, UL1430, UL1571, UL2464, UL2468 and others) or VDE equivalents. A harness quoted "to UL wire" without type numbers is a harness waiting to be re-quoted.
2. Jacket and shielding construction
Three constructions are recorded: normal PVC wire, spiral or braid shield, and halogen-free. Shielding is an EMC decision (braid for coverage, spiral for flex life); halogen-free is an installation-environment decision (enclosed public spaces, transport). Confirm per harness family — mixed constructions in one programme are normal.
3. Connector families — and the word "equivalent"
The record names AMP, MOLEX, JST, PHR, FCI and Berg connectors "or the equivalent", fitted per customer requirements. That phrase is where programmes succeed or drift: if your mating side is a genuine branded connector, say so and spec the genuine part or a named equivalent with a mating test; if it is a commodity interface, equivalents save real money. Either way, write the decision down.
4. Strain relief and mechanical protection
On patch-cord-class assemblies the record specifies insert-moulded strain relief giving 360-degree protection against mechanical strain. For equipment harnesses, the equivalent conversation is bend points, grommets and clamp positions on the drawing. Mechanical failure, not electrical failure, ends most harness lives.
5. Application environment
The recorded application fields span network and communication devices, automatic control, home appliances and office equipment, and automobile, motorcycle and electric vehicles — a useful reminder that the same platform serves a bench appliance and an ATV, with the environment (heat, vibration, moisture, UV) driving the construction choices in items 2 and 4. The named variants — ATV, home appliance, magnet ring and refrigeration — exist because environments differ.
6. Compliance expectations
RoHS compliance is recorded for the platform. Anything beyond that — specific test reports, material declarations — belongs in the enquiry, confirmed against the exact build.
7. The approval procedure
Finally, confirm the process itself. The published customised-service procedure runs: buyer supplies drawings, samples or pictures with specifications; quick prototypes are made for initial approval; design-for-manufacturability feedback follows; final samples and specifications are approved before mass production. Do not skip the prototype loop on a new harness — it is where gauge, connector and routing mistakes are still cheap.
The platform and variants are documented on the custom wiring harnesses and automotive & appliance harnesses pages. Harnesses terminate in the blocks covered by terminal block selection, and pair with the PCBA service for assembled programmes.
Cost drivers buyers actually control
Harness pricing surprises usually trace to four buyer-side choices. Connector selection is the largest: a genuine branded connector set can cost more than the wire it terminates, which is why the equivalent decision deserves its own line in the enquiry rather than a default. Shielding construction is second — braid coverage is labour, and specifying it where the EMC environment does not need it buys nothing. Third is variety: every additional gauge-and-colour combination in one harness is a setup the line must make, so consolidating wire types where the design allows pays directly. Fourth is the approval loop itself — programmes that approve the prototype promptly and freeze the specification start production weeks earlier than programmes that treat the sample as a suggestion box. None of these require design compromise; they require deciding early the things that will be decided eventually anyway.
Testing expectations to state up front
The confirmation list should end with verification: what will be checked, on what share of production, before the harness ships. Continuity is the baseline expectation for any harness; beyond it, programmes differ — hi-pot testing where the application demands it, pull-force checks on crimped terminations, and mating verification against the actual counterpart connector where equivalents were approved. Stating the expectation in the enquiry costs one sentence; discovering its absence at incoming inspection costs a programme its schedule. The catalogue's procedure — prototype approval, DFM feedback, final sample sign-off — is the framework these expectations attach to, and a buyer who names them early will find they are priced into the quotation rather than argued about afterwards.
Documentation: the eighth confirmation
One more confirmation closes the list, and it is the one that pays out for years: agree what documentation ships with the programme and where it lives. The drawing revision, the wire and connector decisions, the approved sample reference and the test expectations should exist as one file that both sides can produce on demand. Programmes with that file reorder in a thread; programmes without it re-litigate every decision at every reorder, with staff turnover quietly editing the specification each time. The catalogue's procedure generates most of the file as a by-product — drawings in, prototypes out, approvals recorded — so the buyer's task is simply to keep it, name it, and send it back with the next order.
The cheapest sentence in sourcing
Every item in this guide compresses into a habit: write it down before the order, not after the delivery. The harness industry runs on artefacts — drawings, records, approved samples — because a harness is an artefact: copper and polymer arranged exactly as specified, with no opinion of its own. Programmes that treat specification as paperwork discover its real function at the first dispute, the first reorder, the first staff change. Programmes that treat it as the product's second half find that harness buying becomes the calmest line in their sourcing portfolio. The seven confirmations and the documentation habit are that second half, itemised.
One closing observation from the sourcing desk: harness enquiries that follow this checklist are answered faster, and the speed is diagnostic. A quotation that returns quickly against a complete specification is a supplier telling you the job is understood; a slow, question-heavy return against the same specification is information of a different kind. Either way, the checklist has done its work before a single sample exists — it has made the programme legible to everyone who has to price, build, inspect or reorder it.