3DXML is often the only practical handoff available when a wire harness leaves its original CATIA or 3DEXPERIENCE environment. The file may contain rich assembly structure and routing data, but “opens successfully” is not the same as “ready for engineering.” A dependable import workflow must distinguish geometry, product structure, physical harness semantics, and electrical connectivity.
What a wire harness import should recover
The objective is an editable harness model, not a collection of meshes. At minimum, the importer should attempt to identify connectors, branch points, protections, fixings, routed segments, centre-lines, and the relationships between them. When conductor routes or bundle membership are present, those relationships should remain traceable to the source records.
| Source evidence | Useful imported result | Qualification question |
|---|---|---|
| Product structure | Stable component identity and assembly hierarchy | Were duplicate, generated, or missing identifiers resolved explicitly? |
| Curves and centre-lines | Editable harness segments and branch topology | Are endpoints joined, ordered, and measured consistently? |
| Fixings and protections | Placed engineering entities with source attribution | Were classifications inferred, supplied, or left unknown? |
| Conductor routes | Wire-to-segment routing relationships | Is the electrical definition complete enough to trust? |
| Configuration data | Variant or effectivity scope | Does the imported harness represent one buildable configuration? |
Why a companion wirelist still matters
Physical routing and electrical connectivity are related, but they are not interchangeable. A 3DXML package can describe where a bundle runs while omitting wire endpoints, circuits, gauges, colors, terminal assignments, or splice logic. A wirelist or another electrical source can supply those facts.
Reconciliation should not silently overwrite one source with another. It should match conductors and cavities using stable identifiers where possible, report ambiguous candidates, preserve unmatched records, and show which fields came from which source. That evidence is essential when the physical and electrical exports were created at different revision levels.
Never promote inferred connectivity to source truth. Keep supplied, derived, matched, and unresolved data distinguishable through review and export.
A safer import workflow
- Inventory the package. Identify the root product, available representations, configuration records, conductor-route data, and any companion wirelists or spreadsheets.
- Recover structure before appearance. Build component identity and parent-child relationships before using geometry to solve topology.
- Normalize the physical network. Join curves, resolve branch points, calculate lengths, and retain source references for every derived segment.
- Reconcile electrical evidence. Match connectors, cavities, wires, terminals, and routes while surfacing collisions and unresolved candidates.
- Run readiness checks. Detect missing identities, disconnected topology, configuration ambiguity, incomplete routing, and export blockers.
- Release with an import report. Record what was preserved, inferred, repaired, omitted, or still requires downstream validation.
Questions to ask before approving the result
- Can every important imported entity be traced back to the 3DXML package or a named companion source?
- Are physical lengths based on recovered centre-lines rather than visual bounding boxes?
- Are configuration and effectivity assumptions explicit?
- Do unmatched wires, connectors, or route fragments remain visible?
- Does the target export state what it can and cannot preserve?
Harness Studio treats 3DXML recovery as an engineering evidence problem. It builds an inspectable neutral harness, supports optional wirelist reconciliation, and produces readiness findings so teams can repair the result before translating it into KBL, VEC, HX2ML, or another downstream workflow.