An appliance wire-harness connector change needs a documented baseline, connector delta, harness impact, evidence boundary, and approval owner. A similar appearance is not a change approval.

Contents

• Part 1. Establish the released baseline
• Part 2. Describe the connector delta
• Part 3. Check harness and appliance impacts
• Part 4. Define evidence and approval boundary
• Part 5. Build a change-control RFQ

Part 1. Establish the released baseline

Record the connector, mating part, terminals, housing, harness route, appliance context, drawings, and revision before describing a proposed swap.

Part 2. Describe the connector delta

State what changes and what remains unchanged: keying, terminal population, housing, mating interface, routing, support, or supplier reference.

Important: A visually similar connector cannot approve a harness change. Source: IPC.

Part 3. Check harness and appliance impacts

Review routing, bend space, support, enclosure, access, environment, assembly work, service documentation, and any appliance-specific condition affected by the delta.

Part 4. Define evidence and approval boundary

Identify the evidence requested, configuration it covers, open questions, and organization responsible for approval. A supplier response is not automatically a released engineering change.

Part 5. Build a change-control RFQ

Change field	Provide	Purpose
Baseline	Released drawings, route, revision	Establish the reference
Delta	Proposed connector and harness differences	Make change explicit
Impact	Appliance, assembly, service, environment	Identify review scope
Evidence	Samples, records, open questions, owner	Keep approval bounded
## Part 6. Use ZUCH inquiry routes
Start a family discussion at the ZUCH appliance solution route, then send the baseline and delta through the sample request route. The shared appliance RFQ checklist provides a complementary procurement record.
## FAQ
### What should a swap record contain?
Baseline drawings, proposed delta, harness and appliance impacts, revision, evidence request, open questions, and approval owner.
### Can a similar connector be substituted?
Not without the responsible program’s controlled review and evidence.
### Why retain the harness layout?
It shows routing, support, access, and assembly impacts that a component photo cannot show.
### Does a supplier response approve the change?
No. Approval belongs to the responsible engineering and change-control process.
### When should the record be revised?
Revise it after any connector, harness, appliance, requirement, or evidence change.
### What belongs in the RFQ?
Send baseline and proposed drawings, harness layout, change reason, impacts, sample objective, requested evidence, approval owner, and revision controls.
## References
– IPC: interconnection documentation context.
– IEC: application-evaluation context.