NX Routing vs. Siemens Capital: Which Tool Does What

A recurring point of confusion for readers of this knowledge base: NX has its own electrical routing/harness capability (NX Routing Electrical), and Siemens separately sells Capital, an ECAD/electrical-systems-design product line that also does harness design. This note clarifies the boundary, drawn from Siemens' own Capital team blog and forum discussion, since Siemens does not appear to publish a single crisp "use this one, not that one" statement — the reality is genuine overlap plus formal integration.

The core division of labor

• Capital is the electrical-systems-of-record tool: schematic/logical design (signal connectivity), physical wire/splice/multicore definition, and electrical documentation. Capital Logic Designer specifically supports authoring both logical designs (signal connectivity flows) and physical designs (the actual wires, splices, and multicores that implement those signals) — described as functioning as "more than a schematic design tool," spanning "from logical concept design through to harness design." (Source: Master logical and physical wiring systems design with Capital Logic Designer)
• NX Routing (Electrical) is the 3D-mechanical realization tool: it takes electrical connectivity/harness definitions and routes them as real 3D geometry through the actual product assembly, checking clearances, bend radius, and physical fit against surrounding mechanical structure, and produces flattened formboard manufacturing drawings.

How they're actually connected

Siemens' own description of the Capital↔NX relationship: "electrical harness designs created in Capital can be visualized and routed directly within NX, while spatial and packaging constraints from NX inform the electrical topology." In other words, this is explicitly not a competing/either-or choice for the electrical-harness use case — Capital owns the electrical logic and documentation of record, NX Routing owns the literal 3D packaging and routing of that harness through the mechanical assembly, and data is meant to flow both directions. (Source: The origins and impact of Siemens Capital integrations)

Maturity levels of the integration (per Siemens' own framing)

Siemens describes the Capital↔MCAD integration as having evolved through four stages, useful context for readers evaluating how tightly coupled a given deployment might be:

1. Crawl — file-based export only, one direction, no live link.
2. Walk — bidirectional data push/pull between the two systems, but not live/real-time.
3. Run — real-time, API-connected synchronization with some automation.
4. Fly — seamless, high-performance, collaborative real-time workflows.

Where a given customer's Capital-NX deployment sits on that scale matters a lot for how much manual reconciliation designers should expect day to day — a "crawl" or "walk"-stage deployment still requires real design discipline around when data is exported/imported, whereas a "run"/"fly" deployment behaves closer to a single connected model. (Source: The origins and impact of Siemens Capital integrations)

Guidance for readers deciding "which tool do I need"

• If the question is "what does the electrical circuit look like, what wires/splices/connectors exist, and what is the documentation of record for the electrical system" — that's Capital.
• If the question is "will this harness physically fit through the airframe/chassis/enclosure, what's its bend radius and bundle diameter, and what does the flattened formboard for the manufacturing floor look like" — that's NX Routing Electrical.
• For an all-mechanical routed system (pipes, tubes, HVAC ducting — no electrical signal content at all), there is no Capital equivalent; that is NX Routing Mechanical's exclusive domain, with no overlap question to resolve.
• Expect data exchange between the two, not a hard wall — teams already using both should ask their PLM/CAD admin which integration "stage" (crawl/walk/run/fly, per Siemens' own framing above) their environment is actually configured at, since that materially changes daily workflow expectations.

Sources:

• The origins and impact of Siemens Capital integrations, Siemens EE Systems Blog
• Master logical and physical wiring systems design with Capital Logic Designer, Siemens EE Systems Blog