Do You Need a Wire Harness Prototype Before Production?

When a prototype is worth requesting

A prototype is most useful when it can answer a project question that a drawing review cannot settle by itself. Examples include a new connector interface, a branched route with tight clearances, a first installation in the target equipment, a changed supplier or component, or a design whose service conditions are not yet fully represented in the documentation.

It is not a universal requirement for every order. If a released design is unchanged and its interfaces and acceptance plan are already understood, another sample may add little. Decide based on design risk, the cost of a late change, and what remains uncertain—not on a fixed rule that every harness needs the same sample process.

Clarify what the sample represents

The word sample can describe different things: an early engineering build, a design-validation unit, a first article made against a released drawing, or a production-representative assembly. These are not automatically equivalent. Before work starts, state the drawing revision, bill of materials, connector and wire references, quantity, and any temporary substitutions or open items. Ask the supplier to identify deviations instead of treating an undocumented difference as approved.

NASA's systems-engineering guidance distinguishes prototype or engineering-unit evaluations from planned verification and validation activities, and recommends documenting what each test article represents. That is a useful discipline for a harness project too: name the sample's purpose and limits so its results are interpreted correctly.

Evaluate the sample in its intended installation

First check whether the assembly matches its controlled references: connector identity and keying, cavity assignments, wire identification, branch positions, protective parts, labels, and any dimensions designated for acceptance. Use the drawing's stated measurement points and inspection conditions. If a requirement is missing or ambiguous, resolve it before recording a pass or fail.

Then install the sample in the equipment or a representative fixture. Confirm that connectors mate as intended, the harness follows the planned route, clips and mounting points align, branches reach their destinations, and the assembly can be installed and serviced in the specified sequence. Observe clearances, movement, strain relief, and contact with nearby parts under the conditions that matter to the application. A loose bench check cannot answer an installation question that only appears in the machine.

Electrical and other performance checks should come from the product requirements and agreed test plan. Define the circuits, conditions, limits, instrumentation, and records that matter for the project. IPC/WHMA-A-620 describes process and acceptance requirements for cable and wire harness assemblies, but it does not select a universal test plan or sample quantity for every application. State the standard, revision, class, and any additional customer requirements when they apply.

Agree on acceptance evidence before the sample arrives

Write down what will be reviewed and who makes the approval decision. A concise record can identify each characteristic, its drawing or requirement reference, the check method, acceptance condition, result, and any supporting photo or test record. Include the intended installation check and any project-specific electrical or environmental evaluation. If a test can damage the sample, decide in advance whether a separate unit is needed.

Avoid vague sign-off such as “looks good.” Record objective observations and mark up the controlled drawing when a dimension, route, orientation, or component reference needs clarification. Separate an acceptable concession from a permanent design change, and identify who may authorize either one.

Record approval against a controlled revision

An approval should point to the exact sample configuration reviewed: part number, drawing revision, bill of materials revision, sample identifier if used, and the agreed results. If the sample leads to a change, update the controlled documents and decide which checks must be repeated. Keep the approved reference available to purchasing, engineering, quality, and the supplier so a repeat order does not depend on memory or an email attachment with no revision.

Know what sample approval does—and does not—prove

A passing sample can show that the reviewed unit met the checks and installation conditions that were actually applied. By itself, it does not demonstrate that every future unit will be identical, that untested operating conditions are safe, or that a production process is controlled. Those questions need the applicable production controls, inspection plan, acceptance criteria, and any required qualification evidence to be defined separately.

Likewise, a reference to an industry standard is not a substitute for an agreed requirement. Identify which standard and revision apply, what acceptance class or customer-specific criteria are required, and what records are expected. IPC notes that IPC/WHMA-A-620 does not set the inspection frequency for every product; project documents should close that gap where frequency matters.

When buyers ask whether they need a prototype

**Do I always need one?** No. Request one when it reduces a meaningful design, fit, interface, or process uncertainty. The project team can document why an existing approved configuration does not need another sample.

**How many should I request?** There is no universal number. Consider the number of configurations, installation locations, planned checks, destructive tests, and whether retained or comparison units are needed. Agree on quantity with the supplier and project team before ordering.

**Can I approve a sample from photos?** Photos can help review visible features, but they cannot establish every dimension, mating condition, electrical behavior, or fit in the equipment. Use them only for the characteristics they can show, and arrange physical or instrumented checks for the rest.

The most useful prototype approval is a small, controlled decision: a known configuration, checks tied to project requirements, recorded results, and a clear next revision or production-release status.

References

NASA guidance distinguishes prototype or engineering-unit evaluation from planned verification and validation, and recommends defining what each test article represents. IPC/WHMA-A-620 describes cable and wire harness process and acceptance requirements; its applicability, revision, class, inspection frequency, and additional criteria must be specified for the project. Neither source defines one universal sample quantity or approval checklist for every harness.

NASA Systems Engineering Handbook Appendix: Verification and Validation Plan Outline

IPC/WHMA-A-620 Requirements and Acceptance for Cable and Wire Harness Assemblies

Contact HPC