Siemens NX Open, Teamcenter, Large Assemblies, and Troubleshooting Complete Guide

NX · NX Open · Teamcenter · Troubleshooting

Overview

The value of Siemens NX comes not only from its CAD/CAM/CAE functionality, but also from automation with the NX Open API, PLM-wide process management with Teamcenter, and stable operation of assemblies with tens to hundreds of thousands of components.

This page covers the automation section — Knowledge Fusion, NX Open (Python/C#/C++/Java), UDF, and Reuse Library — the Teamcenter managed environment and Active Workspace, large-assembly performance optimization (Reference Set, Lightweight, Partial Loading), field troubleshooting, best practices, and industry-specific tips.

Finally it summarizes NX 2406/2412 new features (Adaptive UI, AI features, XR, Generative Design). For basic UI and Navigators see 01-shortcuts-ui.md, and for assemblies and WAVE see 03-assembly-wave.md.

Knowledge Fusion (KF)

The Knowledge-Based Engineering language built into NX. It extends parametrics by rules atop the Design Freedom Architecture (DFA).

LISP-family declarative syntax
Stored as .dfa files
Used for Rules, Constraints, Derived Properties, and UDF extension
Typical application: when a bolt size changes, the washer, nut, and assembly clearance all auto-cascade

> Tip: KF has a learning curve, but when building a company standard library where "if the dimension changes, the related standard parts follow automatically", the return on investment is high.

NX Open API

NX's official programming interface. Supported languages:

Language	Characteristics
C++	Highest performance, complex plugins and real-time UI
C# / VB.NET	Windows platform, easy dialog authoring
Java	Cross-platform
Python	Officially supported since NX 10, lowest learning curve

Journal (Macro Recording)

Menu → Tools → Journal → Record records UI actions and emits them as a Python or VB script.

Editing the recording to extend it with for loops and variables is the standard entry point to NX Open. Set the recording language to Python in File → Preferences → User Interface → Journal Language.

Python NX Open Example

import NXOpen

def main():
    theSession = NXOpen.Session.GetSession()
    workPart = theSession.Parts.Work

    # List every feature by name
    for feat in workPart.Features:
        print(feat.GetFeatureName())

if __name__ == '__main__':
    main()

Key Uses of NX Open

Batch processing: bulk save and format-convert hundreds of parts (STEP/JT Export)
Create custom Features
Integrate with Teamcenter / PLM systems via REST API
Automate checklists like missing-dimension detection and BOM consistency verification

Block UI Styler

Menu → Resource Bar → Block UI Styler lets you drag in widgets like textboxes, sliders, and lists, and auto-generates the XML and code.

Since you can author complex dialogs without hand-coding, it has become the de facto standard for deploying in-house automation tools.

NX Open Field Tips

Iterate fast with Python Journal, and when stabilized, port to C# or C++ for performance.
For in-house distribution, build a set of company.men (menu) + company.btn (button) + company.py (script) to standardize a custom ribbon and toolbar.
API deprecations happen at NX upgrades, so regular regression testing is essential.
With Teamcenter–NX Open integration, Item creation → Part creation → BOM registration can be handled from a single script.

> Note: Always validate NX Open scripts on a duplicate file before running them on the original .prt. Incidents where a wrong Feature-name pattern match caused mass deletion of features are common.

UDF (User Defined Feature) & Reuse Library

UDF Concept

A capability that saves a recurring combination of features as a reusable custom feature. It takes input parameters (dimensions, positions) and can be called from many parts to produce the same shape.

UDF Creation Workflow

Build the reference part (e.g., T-slot pocket).
Menu → Tools → User Defined Features → Create.
Pick the features to export.
Promote Expression Variables to input parameters.
Set UDF name, icon, and category.
Save as a .udf file.

UDF Library Configuration

Managed with udf_index.dat (index) + udf_def.txt (definitions)
Share on a network drive + environment variable UGII_UDF_DIR
Register the library at Menu → Tools → User Defined Feature → Configure Library

Reuse Library

The Reuse Library tab on the right of the ribbon stores UDFs, part templates, Custom Symbols, and Institutional Parts by category, and supports drag and drop like a parts catalog.

Typical UDF examples: T-slots, dovetails, keyways, a bolt hole + counterbore + tap combination, bracket mounting hole patterns, and joint blend groups.

Teamcenter Integration

What is Teamcenter?

Siemens' PLM platform. It is most deeply integrated with NX, and stores part numbers, Revisions, BOMs, workflows, and all CAD files in the Teamcenter Vault.

Managed vs Native

Mode	Characteristics
Native NX	Saves .prt directly to the file system. For individuals and SMBs
Managed NX (Teamcenter integration)	Logs into the Teamcenter server at NX start; all files reside in the Vault, governed by Item ID and Revision

Main Features

Check-Out / Check-In: edit lock + version commit
Revision: A, B, C... or 01, 02, 03 schemes
Where-Used: reverse-trace which higher-level assemblies use a part
What's Changed: compare changes versus the previous revision
Workflow: automate design review → approval → Release
ECN/ECO: handle Engineering Change Orders
BOM Management: manage EBOM/MBOM/SBOM separately in Structure Manager
Multi-site: access the same data from multiple locations

Active Workspace

The Teamcenter web client. You can do model view, BOM editing, and workflow processing in the browser, and inside NX you can also open the Active Workspace panel to browse the Vault.

NX–TC Integration Field Tips

Auto-generate Item IDs per the organization's rules (e.g., 000001-000, 000002-000). Human-readable rules are preferred over UUIDs.
Save with the correct Dataset Type: distinguish NX Part Dataset, CAD Dataset, and DirectModel (JT) Dataset.
Release Status stages: Working → In Review → Approved → Released. After Release, any edit must issue a new Revision.
Use Load Options to control load time among Latest/Working/Baseline.
For external supplier handoff, export via PLMXML to deliver BOM + geometry together.
Use Teamcenter Share (2406+) to share CAM programs via cloud with external partners.

> Note: In a Teamcenter environment, renaming or moving files at the OS level breaks references. All naming and moves must be done inside the Teamcenter UI or NX.

Large-Assembly Performance Management

Reference Set

A Reference Set (RS) is a "partial representation" of a part. It selects which objects the assembly will load and display.

Automatic Reference Sets:

Empty: loads only structure, no objects
Entire Part: all objects
Model: solids and sheets only (excludes drawings and sketches)
Simplified: simplified body

Common user-defined Reference Sets in practice:

MATE — only assembly reference faces and axes
SIMPLE — only the outer bounding box body
DRAFT — only objects needed for drawings
LIGHTWEIGHT — lightweight JT representation

Partial Loading / Lightweight

Partial Loading: load only the components you need
Lightweight Representation: lightweight JT + outer-boundary representation, reducing memory by up to 90%
Enable Use Lightweight Representations / Use Partial Loading in File → Preferences → Assembly Load Options

Open by Proximity

Assemblies → Component → Open by Proximity. Fully loads only components inside a sphere or box region, keeping the rest in a lightweight state.

For local work inside hundred-thousand-part assemblies like full vehicles, this is an essential feature.

Linked Exteriors

Links only the outer geometry of a sub-assembly to the parent, replacing thousands of internal parts. Parent-assembly performance improves dramatically.

Performance Optimization Checks

Standardize Reference Set on MODEL (avoid Entire Part)
Minimize the number of Datum Planes; prefer Sketch references instead
Clean up unnecessary Constraints to prevent over-constraint
Create Interpart Links (WAVE) only when truly needed
Suppress variable or not-yet-designed features
On save, use "Save Work Part" only, not "Save All as Displayed"
Unify Assembly Load Options as a team standard

Performance Benchmarks

Component Count	Normal Load Time
1,000	< 30 s (Lightweight)
10,000	< 2 min
100,000+ (full vehicle)	Not feasible without Lightweight + Partial Loading

Troubleshooting

Update Error

Symptom: a yellow warning triangle in the Part Navigator, "Error during Update".

Causes: parent object deleted or suppressed, WAVE source deleted, circular reference, or bad Expression reference.

Resolution:

Right-click the feature → Edit Feature or Edit with Rollback → identify the missing object
Use Find References to select broken references
Use Replace Reference to swap in a valid object
In the worst case, Suppress the feature and regenerate downstream features to restore the tree

Broken Link

Causes: OS-level rename, files moved outside Teamcenter, or WAVE source part deletion.

Resolution:

Use Menu → Assemblies → WAVE → General WAVE Relinker to bulk-reconnect broken WAVE links
Use File → Clone Assembly for a proper duplication that reconnects WAVE automatically
Rename files only inside NX and forbid OS-level renames

Tangled Reference Set

Symptom: a component is shown as empty, or downstream features disappear.

Resolution: right-click the component → Replace Reference Set → choose Model. When the number of Reference Set members exceeds 32,767, rare data corruption can occur — reconstruct in Format → Reference Sets.

License Issues

Symptom: "License unavailable" or specific Features shown grayed out.

Resolution:

Verify the environment variable UGS_LICENSE_SERVER (e.g., 28000@licserver01)
Check the ugslmd or lmgrd service status
Query per-feature checkout status in the License Manager
If a colleague holds the same Feature, send a returnRequest
Check the ugnx.lic expiration date

Crash / Freeze

Check ugs_crash_report in the TEMP folder
Can occur when the Undo stack accumulates too much → save and restart
For display driver issues, update to the latest NVIDIA Quadro driver
Enable OpenGL performance optimizations in Preferences

Other Common Issues

Hidden Datum not visible: Ctrl+Shift+U (Show All) + Layer ON
Sketch will not activate: Reattach Sketch with a new plane
Body empty after Feature Rollback: Suppress the offending feature → regenerate upstream features
Edge not selectable: enable Edge in the Selection Filter (Ctrl+Shift+J)

> Note: In a Teamcenter environment, after resolving a broken link, always Check-In to push it to the server. If you only fix the local cache, other users will pull the broken state again.

Best Practices Summary

Part Structure

Prefer one primary solid body per part
With multiple bodies, name them (BODY_MAIN, BODY_RIB, BODY_TRIM)
Keep Datum/Sketch at the top of the feature tree
Place auxiliary features at the bottom

Expression Naming

Do not keep the default p0, p1…
Convention: {function}_{dimension} — e.g., L_Shaft, D_Bore, T_Wall
Prefix interpart-reference expressions with IP_ (e.g., IP_Housing_L)
Organize by function with Group Expression

Reference Set Policy

MODEL — for assembly reference
MATE — assembly reference faces and axes
SIMPLE — outer bounding box (large-assembly LOD)
DRAFT — for drawings

Company Standard Template

Place a master_template.prt in UGII_TEMPLATE_DIR that contains default Datum CSYS, company Material Library, default Expression groups, standard Reference Sets, and PMI View templates, so the entire organization starts from the same baseline.

Filename & Item ID Rules

Forbid spaces, Korean characters, and special characters
Linux is case-sensitive, so do not rely on case
Keep paths within 256 characters
Example: PRJ001_ASM001_PART001_RevA.prt

Example Layer Usage

Range	Purpose
1	Solid Model
10–20	Sketches
21–30	Datum Planes/Axes
41–50	Reference Curves
61–80	Work Surfaces
100+	User-defined

Industry-Specific Tips

Automotive

Bodyshop: body panels = Sheet Metal + Variational Flange + welding symbols. Customize OEM Bend Tables (Toyota, Hyundai specifications).
Class A Surface: G2/G3 continuity with Studio Surface. Zebra + Reflection are required checks. It is common to import from Alias and do additional work in NX.
Powertrain: casting parts rely mainly on Synchronous Modeling + Draft Angle analysis.
Electrical: Routing Electrical + Capital Harness integration, extending into production harness jig design.
OEM standards: presets for GM-APE, Ford-C3P, VW/Audi-KPM, Toyota-TPSA, and Hyundai-HKMC.

Aerospace

Primary Structure: Frames, Ribs, Spars = mix of Aero Sheet Metal + Machined Parts. Heavy use of Canted Flanges and Joggles.
Skin: curved panels. Manage tens of thousands of rivet holes with Pattern Features.
Composite Layup: Fibersim for NX integration, covering Ply Layup, Rosette, Darts, and Producibility Simulation.
Assembly: with hundreds of thousands of parts, Partial Loading + Open by Proximity are mandatory. Integrate with Teamcenter MRO.
PMI/MBD mandatory: per FAA/EASA regulations, under ASME Y14.41.
Fastener Library: built-in libraries for NAS, MS, and AN standard fasteners.

Tooling

Injection molds: full use of Mold Wizard. Hasco/Misumi Mold Base + automated cooling.
Progressive dies: PDW. Target 70%+ material utilization via Strip Layout optimization.
Large press dies: Class A-based Die Face design + Springback Compensation (AutoForm integration).
Electrode Design: under Mold Wizard, auto-electrode + WEDM integration.
Machining integration: Mold Wizard output flows naturally into CAM via the Master Model.

NX 2406 / 2412 New Features

NX 2406

Selection Filter for Tools and Devices (CAM): pick tools directly in the Graphics window
Advanced Chip Control (CAM turning): optimized chip breaking, extended tool life
Rules-based Automation for Hole-making: auto machining strategy based on hole-diameter range
Concept Modeling (Realize Shape, Push/Pull) enhancements
Aerodynamic Surface Analysis improvements

NX 2412

Immersive Engineering: Sony XR HMD integration, VR-based model editing
Concepteur CFD: FloEFD-based CFD fully integrated into the CAD environment
Value-Based Licensing: per-feature and usage-based billing
AI Features: Predictive Modeling Assistant, improved Automated Feature Recognition, Natural Language Commands (beta)
Generative Design: Topology Optimization + Lattice Structure auto-generation
NX X (SaaS): fully browser-based CAD

AI / XR / Sustainability

Adaptive UI: learns usage patterns → auto-arranges frequently used commands on the ribbon
AI Design Assistant: modeling instructions through a chat interface (beta)
Inspection Automation: auto-generate CMM programs from PMI
HoloLens integration: model overlay on the manufacturing floor
WebGL JT Viewer: lightweight viewer based on Teamcenter Share
Sustainability Dashboard: tracks per-material carbon emissions, recyclability, and Product Carbon Footprint

Field Checklist

Refactor Journal recordings into parameterized, reusable functions
Before an NX version upgrade, run regression tests on in-house NX Open scripts
Confirm the Teamcenter Item ID scheme is human-readable
After Release, branch to a new Revision for any change
Standardize assembly Reference Set on MODEL
Default large assemblies to Partial Loading + Open by Proximity
After fixing Update Errors, re-check for circular references in the WAVE Relations Browser
No spaces, Korean, or special characters in filenames or Item IDs
Apply industry standard presets (OEM Bend Table, ASME Y14.41, Mold Base Library)
Validate NX 2412 AI/XR features in a pilot project before rolling out company-wide