NX Routing Tutorial: The Short Version
This NX routing tutorial covers a first project in Siemens NX Routing Electrical and Routing Mechanical: pick the application and discipline, set up specifications and the part library, place equipment, create paths, assign stock and run design rules. inteliScience builds routing libraries and trains NX teams, so the first harness becomes a repeatable process.
The Problem: First Routing Projects Fail at the Library, Not at the Path
In a demo, NX Routing looks like sketching: draw a path, drop stock on it, done. In a real first project the path is the easy part. What stops teams is everything that has to exist before the first path: a discipline that filters the library, a specification that decides which elbow fits which tube, connectors that carry ports, and one shared place where generated parts are saved.
The pattern repeats. One designer gets a routing license, opens a sample assembly and routes a hose in an afternoon. The project plan then assumes the production assembly takes a week. Three weeks later the harness exists, but half the connectors are plain solids without ports, the elbows came from the wrong family, and nobody can produce a length list the shop floor trusts.
A naming note before we start. Siemens now sells NX under the Designcenter name, and the current release is 2606 from June 2026 (as of September 2026). The routing applications, the documentation and most job ads still say NX Routing, and so does this tutorial. Siemens also ships two generations of routing tools side by side, which is the first decision you have to make.
Which NX Routing Application Do You Start In?
Start in the electrical tools for wires, cables and harnesses, and in the mechanical tools for pipes, tubes, conduit and HVAC. Then pick the generation: traditional Routing or Routed System Designer (RSD). For a new project without legacy routing data, we evaluate RSD first, because moving from traditional Routing to RSD later is a one-way step.
| Application | What it routes | Typical first project | Worth knowing |
|---|---|---|---|
| Routing Electrical (traditional) | Wires, cables, harnesses, driven by a connection list and a component list | Harness between connectors in a machine assembly | Formboard drawing flattens the 3D harness |
| Routing Mechanical (traditional) | Pipes, tubes, conduit | Hydraulic tube run from pump to manifold | Design rules: minimum bend radius, minimum straight length, connection compatibility |
| Mechanical Routed System Designer | Industrial piping with runs and spools, tubing, HVAC, 3D cableways | Plant piping or cable tray network | Table-driven bulk resize and replace of connected parts |
| Electrical Routed System Designer | Signal and power distribution, cabling, wiring harness assemblies | Harness built from an imported route list | Many tools need the Electrical specialty application |
Both generations share the same library concepts: part and stock definitions, ports, disciplines and specifications. Traditional assemblies move to RSD with the command Advance to Routed System Designer, and the Siemens documentation is plain about the limits. After conversion you cannot run traditional routing operations on the assembly, you cannot convert it back, and there is no associative link to the original. Runs and spools from traditional Routing are removed; noncircular PTS or raceway stocks are deleted while their paths are converted.
We’d advise against converting in the middle of a project. Convert a copy, check it against the original, then decide.
Check licenses before you plan. Routing needs NX plus Assemblies, drawings need a Drafting license, and interference checks use Clearance Analysis from NX Advanced Assemblies. The NX Open routing functions list the license keys routing_electrical, routing_mechanical and routing_combined, which tells you what your seat must carry.
Before the First Path: Discipline, Specification and Part Library
Three settings decide what NX lets you place: the active discipline, the active routing specification and the content of the Routing Part Library. Set them up before anyone routes. Teams that skip this step route fast in week one and spend week three replacing parts that came from the wrong family.
Disciplines
A discipline tailors a routing application to one kind of work, such as piping versus tubing, or high-pressure piping versus gravity-fed drainage. Disciplines are defined in Application View (APV) XML files that ship in metric and inch variants, for example ugroute_mech_metric.xml for Routing Mechanical and ugroute_elec_metric.xml for Routing Electrical. Each discipline names a default specification, the start nodes for parts and stock in the library, and the required and optional characteristics.
Only one discipline is active at a time, and the default per application comes from customer defaults. Setting the discipline to None switches library filtering off, and you cannot create a specification while it is None.
Routing specifications
A specification narrows the library further, using part attributes from the part family table (PTB) file: material, size and other physical values. Each specification is stored in its own XML file in the folders set in Customer Defaults (Routed System Designer, Part Library, Specification Folders tab). Besides part compatibility, a specification can hold connection and branch compatibility, companion parts and secondary placement rules. The Siemens example for the last one: mating flanges with matching NPS values are placed automatically when a gate valve goes in.
The Routing Part Library
The library holds family-based parts qualified for routing. NX distinguishes equipment parts, which stay put when paths change (pumps, motors, tanks), from routing parts, which move with the path (inline valves, flanges, elbows). A part becomes routing-aware only through Qualify Part, the one dialog that creates ports, anchors, terminals, built-in paths and cross-section curves. It works within the work part only, so you qualify the part file itself, never a component inside an assembly.
Ports are where most first-project problems start:
| Port type | What it does | Example |
|---|---|---|
| Fitting port | Connection point; the alignment vectors of two mating ports point toward each other, an optional rotation vector clocks the part | Flange face, tube fitting |
| Fixture port | Lets a path run through a component without splitting the stock | Clamp, hanger, holder |
| Multiport | One connection point that holds many terminals, placed or virtual | Connector with pins |
| Stock port | Created automatically at both ends of a path when stock is assigned | Tube end |
One setting saves a lot of cleanup. Routing part family members are saved to the folder in UGII_ROUTING_MEMBER_SAVE_DIR. If that variable is not set, they go to a local default: the Siemens documentation names %UGII_BASE_DIR%\ugii inside the NX installation for Routed System Designer and the folder NX was started from for traditional Routing. Set it on every seat before the first project. Because library parts are part families, the mechanics of templates and family tables are worth knowing too.
Your First NX Routing Project, Step by Step
The sequence below follows the routing workflow Siemens documents: place devices, create paths, assign stock, add fittings, fix rule violations, check clearances, then produce drawings and the bill of materials. Run it on one real subassembly with a prepared library, not on the full product.
- Prepare the assembly. Make the parent assembly the work part, set the discipline (for example Tubing) and activate the specification you want to route with.
- Place equipment and devices. Use Place Part from the library, or Add Component for equipment. Place stationary equipment first, because routing parts follow the paths that connect it.
- Create paths. Create Linear Path builds route control points (RCPs), line segments, default corners and elbows, and NX applies assembly constraints as the path is created. Spline Path is meant for flexible runs such as brake lines and harnesses and shows the total spline length and the location of the minimum radius. Start and end paths on ports, not on free points.
- Assign stock. Drag stock from the Reuse Library onto a segment, or use the Stock dialog. You can also assign stock while creating the path.
- Add fittings with Place Part. Not with Add Component: Siemens notes that Add Component does not update existing routing paths to accommodate the new part.
- Run the design rules. Routing Mechanical checks minimum bend radius, minimum straight length and connection compatibility. In electrical routing, the curve bend radius is a ratio to the bundle diameter, set by CURVE_MIN_BEND_RADIUS_COEFF in the APV file; without a value, the ratio is 1.
- Check interference. Clearance Analysis (NX Advanced Assemblies) finds collisions with the surrounding structure.
- Produce output. Define fabrications if needed, create drawings and generate the routing BOM. With Teamcenter, the routing BOM can create items for stock in a BOM view, driven by the DB_PART_NO characteristic.
Before anyone trusts a length list, compare it with the model. This NX Open Python journal uses only standard API calls and lists every stock in the work part with its diameter and routed path length:
# List routing stock in the work part with diameter and routed path length.
# Make the routing assembly the work part, then File > Execute > NX Open (Ctrl+U).
# Stock modeled as components lives in child parts: run the journal there too.
import NXOpen
def main():
session = NXOpen.Session.GetSession()
work_part = session.Parts.Work
lw = session.ListingWindow
lw.Open()
if work_part is None:
lw.WriteLine("No work part loaded.")
return
total = 0.0
count = 0
for stock in work_part.RouteManager.Stocks:
# Path length of all segments the stock sits on (no cut extensions).
length = sum(seg.GetLength() for seg in stock.GetSegments())
name = stock.GetStockData().Name or "(unnamed stock data)"
lw.WriteLine(f"{name:<32} D={stock.Diameter:8.2f} L={length:10.1f}")
total += length
count += 1
lw.WriteLine(f"{count} stocks, total routed length {total:.1f} (part units)")
if __name__ == "__main__":
main()
Path length is not cut length. Connector extensions and cutback lengths come on top, which is exactly what the electrical tools add.
Electrical extras: connection list, auto route, formboard
The electrical side adds connectivity. The Electrical Connection Navigator keeps one entry per wire in the work part and needs a Unique ID for every referenced component; routing a wire uses the fields from_comp, from_conn, from_port, to_comp, to_conn and to_port. Auto Route then calculates lengths and assigns stock, but the lengths are only accurate if the connection list carries enough data to determine the wire outer diameter. Route lists in PLMXML format can be imported to update a harness, and component IDs have to match the imported data.
Bundles are computed, not drawn. NX derives the bundle diameter from the average wire diameter and a bundle factor based on NASA MSC-16378, and a custom plugin can replace that calculation. For manufacturing, Formboard flattens the 3D harness into a 2D drawing, and Update Formboard compares the harness with an existing formboard and reports the differences.
Siemens keeps extending this area: the December 2025 release added multi-tray placement on electrical topology paths and an override for power, control and instrumentation segregation rules, as the Siemens electro-mechanical routing update describes. Where the wire list itself should come from, and where EPLAN ends, is a separate question that we answer in NX Routing vs EPLAN.
One routed subassembly is a pilot. Production routing needs more: a qualified part library with ports, specifications per discipline, one shared member save folder, Teamcenter item rules for stock, and a connection list that maps to your connector IDs. Our NX routing services set that up with your designers, from library to formboard drawing.
Typical Mistakes in a First NX Routing Project
Almost every mistake we see in first projects comes from routing before the library is ready. None of them is a missing command. Each one is cheaper to prevent with a setting or a short rule than to repair in a finished assembly.
| Mistake | What happens | Prevention |
|---|---|---|
| Routing with discipline None | The library is unfiltered, wrong sizes get placed, specifications cannot be created | Set a default discipline per application in customer defaults |
| Connectors modeled but never qualified | Paths cannot snap to ports, auto route finds no endpoints | Qualify every connector and fitting before it enters the library |
| Fittings placed with Add Component | Existing paths do not adjust to the new part | Place routing parts with Place Part |
| No member save folder | Generated members land in the NX installation or start folder, seats see different files | Set UGII_ROUTING_MEMBER_SAVE_DIR on every seat |
| Component IDs differ from the wire list | Imported connections have no endpoints in the model | Agree the ID rule with the electrical team before import |
| Converting to RSD mid-project | No way back, runs and spools removed | Convert a copy and compare first |
| Trusting nominal lengths | Cut list does not match the harness | Provide outer diameter data and check lengths before release |
In practice, the second and fifth rows cost the most time. Both are naming and data problems, and both surface only when the first real connection list arrives.
How to Learn NX Routing Without Stalling a Project
Learn routing on your own parts, and use any NX routing tutorial, this one included, as a map rather than a course. A sample hose in a demo assembly teaches commands; your own connectors, tube sizes and wire list teach the library, which is where the work is. Our clear recommendation: the person who will own the library is trained first, and designers follow once the library holds the first real parts.
A sensible order is library basics (qualify a part, build a family, write one specification), then paths and stock on one subassembly, then electrical connectivity and formboard if harnesses are in scope. We follow that order in our NX routing training, on your own parts and in small groups.
When routing repeats on every order, for example the same harness on a new variant of a machine, the next step is automation with NX Open. How that looks in a real project is described in our NX electrical routing automation case study. At inteliScience, an NX engineering company based in Cluj-Napoca, we usually reach that point after the library and the ID rules are stable, not before.
Frequently Asked Questions
What is the difference between NX Routing Electrical and NX Routing Mechanical?
Routing Electrical models wires, cables and harnesses and works with a connection list, a component list, auto routing and formboard drawings. Routing Mechanical models pipes, tubes and conduit and checks design rules such as minimum bend radius, minimum straight length and connection compatibility. Both share the same concepts of paths, stock, ports and part library, so a team that learns one already knows most of the other.
What is Routed System Designer in Siemens NX?
Routed System Designer is the newer generation of NX routing tools for industrial piping, tubing, HVAC, cableways and electrical cabling, with piping runs and spools, table-driven bulk replacement and integration with NX Diagramming. Traditional routing assemblies can be converted with Advance to Routed System Designer, but the conversion is one-way and keeps no associative link to the original. For new projects without legacy routing data, we evaluate it first.
How do you create a routing part library in Siemens NX?
You build part families for connectors, fittings and stock, qualify each template with the Qualify Part command (ports, anchors, terminals, cross sections) and add the families to the Routing Part Library under the right discipline. Routing specifications then filter the library by attributes such as material and size. Set UGII_ROUTING_MEMBER_SAVE_DIR first, otherwise generated members are saved to a local default folder (the NX installation or the folder NX was started from).
Can Siemens NX import a wire list for harness routing?
Yes. The Electrical Connection Navigator imports connection and component data, including PLMXML route lists, and Auto Route then calculates lengths and assigns stock along the paths. It only works when every referenced component carries a Unique ID that matches the list and the list holds enough data to determine the wire outer diameter. Siemens also lists netlist import from ECAD systems on its wire harness design page.
How much effort does a first NX Routing project take?
Most of the effort goes into the library, not into routing. Placing parts and drawing paths in a prepared assembly is quick; qualifying connectors and fittings, writing specifications and agreeing component IDs with the electrical team decide the schedule. We size a first project by the number of distinct parts that need ports, not by the number of paths, which is why this NX routing tutorial starts with the library.
Next Step
If your first routing project has a date, the most useful hour is one that sorts the library question: which parts need ports, which disciplines and specifications you need, and where the wire list comes from. inteliScience NX engineers go through that with you and tell you plainly what to set up first.

