NX WAVE vs NXOpen: The Short Version
NX WAVE vs NXOpen is the methods choice for variants: part families, interpart links, or code. inteliScience picks that stack with the people who own reference sets, not from a mate-constraint clip. Designcenter 2606 (June 2026) added Live Share on the same assembly. Collaboration is not a variant engine. WAVE, part families, and NXOpen are the actual decision.
| Part family | WAVE | NXOpen | |
|---|---|---|---|
| What it is | Table-driven members from a template part | Associative interpart geometry / PMI links | API that reads specs and builds or edits NX |
| Who maintains it | Designer + a spreadsheet | Methods (link policy) | Software + methods |
| Breaks when | Table and 3D diverge | Parent dump, load options, license | NX major release, unsigned journals, tribal rules |
| Best for | Fastener-like members, few rules | Skeleton driving many parts | Rules that a table cannot hold |
| Teamcenter | Member as item, if you designed it | Revisions on both ends of the link | Same, plus a signed library |
| Live Share 2606 | Still a family | Still a link | Still code |
The Problem: The Assembly Tutorial Stops at Mate
“Siemens NX assembly” is how you fix the first component and assemble the second. This page assumes you already can. The question is how the hundredth similar cover, tank, or winding appears.
Clone-and-hope is a process. It is a bad one. Part families look cheap until the table has columns nobody understands. WAVE looks magical until someone suppresses a parent. NXOpen looks expensive until the quote cycle is three days and the rules live in one engineer’s head.
A generator for order engineering (spec in, geometry and BOM out) is a use of NXOpen, not a third CAD module. If you already know you need that class of tool, the energy-OEM pattern is written up as NX Open transformer automation. This article is the step before that: which of the three mechanisms should own the variant at all.
Part families: when the table is the product
Use a part family when members differ by a short list of expressions (length, hole count, a catalog material) and you can name every column. Fasteners, simple brackets, busbars with three lengths.
The mechanics are simple. A template part carries the expressions, the family table (a spreadsheet inside the part) lists the members, and NX generates each member part on demand into a family directory. Members show up in the Reuse Library and in Teamcenter as items if you set that up before the first member exists, not after.
Do not use a family when the next order adds a rule (“if voltage then this boss, else a cutout”). Tables rot. We advise against hiding if/then logic in spreadsheet cells that NX will not test.
Three signs a family has outgrown itself:
- The table has more than a dozen columns and a “notes” column that explains which combinations are legal.
- Someone maintains a second spreadsheet outside NX to generate the family table.
- Members get edited by hand after generation. That member is no longer a member. It is a clone with a misleading name.
WAVE: when the skeleton should drive
WAVE (interpart) is NX at its strongest: a layout or skeleton owns the interfaces, children extract faces and datums, PMI can follow (WAVE PMI Linker is the older, non-AI version of that idea). Load options, reference sets, and who may create an interpart expression are the real work.
Live Share in 2606 lets several people edit one assembly, including PMI. That is concurrent design. It does not replace a WAVE policy. Two users dragging the same linked face without an agreed update rule is a quality topic, not a collaboration feature.
Our clear recommendation: WAVE over clone when interfaces are shared. NX plus a written link standard, not “WAVE is banned because it broke in 2018.”
A usable WAVE standard fits on one page:
- Direction. Links flow from the skeleton down. No child links back up, no sibling links sideways.
- What may be linked. Faces and datums from a named reference set, never raw solid bodies from a working part.
- Load options. Partial loading and reference sets defined per project, checked into the customer defaults, not left to each seat.
- Who may break a link. Breaking a WAVE link is a release decision. It gets a reason in the Teamcenter change, not a quiet “Break” in the feature tree.
NXOpen: when the rule is the product
Code wins when the variant is a configuration (options, BOM, drawing set) rather than a row. Journals are fine to learn. Production needs a signed library and a version that still runs after the June and December releases. Journals run unsigned on the author’s seat. Signed add-ins ship to other seats; that packaging difference is its own article: NX Journal vs NXOpen. Python vs C# is a later choice.
Designcenter Copilot will not write your WAVE graph. It answers questions about commands. Finding the alternate part in the catalog is reuse, a different product again.
# After an assembly is the work part: count components (NXOpen, NX 2606).
import NXOpen
import NXOpen.Assemblies
session = NXOpen.Session.GetSession()
work = session.Parts.Work
print("work part:", work.Name)
root = work.ComponentAssembly.RootComponent
if root is None:
print("piece part, no components")
else:
print("components:", len(root.GetChildren()))If this is a piece part, you are not in the variant problem yet. Open the assembly that actually ships.
What NXOpen adds that neither table nor link can: the rule lives in reviewed code, it can read the order spec (ERP, Excel, a web form), it can build the assembly, the drawing set, and the BOM in one run, and it fails loudly in a test before the shop sees it. What it costs: a developer, an NX Open Author license on the build machine, and someone who owns the library after the next release.
How the three fail in production
| Symptom | Usually means |
|---|---|
| “The member looks right but the drawing is wrong” | Family member edited by hand, or the template drawing was never parameterised |
| Update takes minutes and half the tree goes red | WAVE parent replaced or a reference set renamed; load options differ between seats |
| Two variants, same part number | Family table generated twice into different directories, or a clone kept the name |
| The journal works on one seat only | Unsigned NXOpen pulling an Author license that other seats do not have |
| “We cannot change the rule, only Klaus knows it” | The rule was never in NX at all; it lived in a person |
How we would choose in a workshop
- List how a variant is born today (clone, family, WAVE, Excel, NXOpen, prayer).
- Name the rule that last caused scrap.
- If the rule fits a table, family. If it is an interface, WAVE. If it is a sentence with “when / unless,” NXOpen.
- Write load options and reference-set policy before adding more WAVE.
- Sign the code. “It ran on my seat” is not a release.
When the answer is the third column, NXOpen custom tool development is the job. This article is the pick; the API craft comes after it.
Frequently Asked Questions
What is NX WAVE vs NXOpen in one line?
WAVE links geometry between parts. NXOpen is code that can create, edit, or check those parts. Part families are a table in front of a template. You can use two of the three. You should not use all three on the same dimension without a rule.
Part family vs WAVE for a housing line?
Family if the housings are catalog lengths. WAVE if a skeleton owns the connector face and every housing must follow. Mixing both on the same parameter is how updates double-fire.
Does Live Share replace WAVE?
No. Live Share (Designcenter 2606) is concurrent editing. WAVE is associative ownership. You can have both. You still need a policy.
How much does an NXOpen variant tool cost?
A signed add-in is a software project, not a seat upgrade. Families and WAVE are cheaper to start and more expensive to unwind if you picked wrong. We would rather spend a day on the choice than a quarter on the wrong graph.
NX WAVE vs NXOpen vs Knowledge Fusion?
Knowledge Fusion is a fourth, older rule language still in NX. We compare it separately in NXOpen vs Knowledge Fusion. For new variant work in 2026 we start with WAVE or NXOpen, not a new KF stack, unless you already own one.
Next Step
Want a 60-minute map of clone vs family vs WAVE vs code on your assemblies? Book a free strategy call. Book a strategy call about NX WAVE vs NXOpen
