Teamcenter NX Integration: The Short Version
Teamcenter NX integration is the managed connection that stores NX parts as Teamcenter datasets, with check-in and check-out, instead of native files on a share. inteliScience sets this up for DACH manufacturers before any copilot or BOM job. One checked-in UGMASTER dataset is the proof it works.
The Problem: Copilots and BOM Jobs on Unmanaged Parts
If NX still writes parts to a share, Teamcenter does not own the CAD master. Search, revision, access control, and later BOM extract all guess. That is a missing Teamcenter Integration for NX, not a weak Teamcenter install.
A built-in PLM assistant is useless until this integration holds.
Our recommendation: stand up managed NX before you fund a copilot or an ERP connector. IT installs NX and a rich client, someone saves locally “just this week,” and months later nobody can say which .prt is released.
Siemens is still shipping into that path. June 2025 NX added NX Properties on the NX dataset (forms plus files and named references). On 5 August 2026 Designcenter documented managed Work Offline (New Workspace, Go Offline, then Go Online). On 17 September 2026 Siemens described Teamcenter 2606 cloning structures with up to one million parts. None of it helps if the first save never created UGMASTER.
Managed NX Versus Native Files
Managed NX (NX Manager in most plants) is the Teamcenter Integration for NX session: the part is bound to an item revision. Native NX is the same modeller with a filesystem master. Both are valid NX. Only managed mode is this integration.
Native scratch parts are fine. Official part numbers belong in managed mode.
What managed mode actually is
Siemens names the product Teamcenter Integration for NX in the tcint documentation. The session gets Teamcenter search, check-in and check-out, and structure work against the vault. June 2025 managed-mode notes also cover Teamcenter inside NX and NX Properties on the dataset.
What native NX still is
Native NX is not a lesser product. If you launch the desktop shortcut and save to disk, you are testing NX, not the integration. Treat that save as a failed proof.
What Has to Be True in Teamcenter First
The CAD client cannot invent a legal item. Item types, dataset types, and the NX dataset have to exist in Teamcenter before the first managed save. That work is BMIDE and TEM, not a designer preference dialog, and skipping it creates the wrong object or a failed save.
Item types
Pick the item type that will own design masters. We’d advise against going live on generic Item “until BMIDE is ready.” The first check-in should already use the type you intend to keep.
Dataset types and the NX dataset
The model lands as an NX dataset on the item revision. Siemens still names that dataset UGMASTER in Support Center articles from 2412 onward. If UGMASTER is missing or swapped for an unmapped custom type, save has nowhere to put the part file. Drawings map under the UGPART section of the attribute file. Confirm both.
Attribute mapping before the first save
Properties move through the mapping file, imported with import_attr_mappings. Siemens documents extra definitions when display values and database values diverge. Official topic: Teamcenter Integration for NX.
KB000215723 (published 28 August 2026) states that on Teamcenter 2506.0004 with NX 2306, owning user, Item Type, and Last mod user can show the wrong value unless you split display type from database revision type.
Siemens’ published example (their item type name):
{ Item type="KR5_Design"
"Type" : ItemRevision.object_type /master=iman /description="Display Type"
"DB_REV_TYPE" : ItemRevision.object_type /master=iman /description="Revision Type"
}Export with export_attr_mappings. Import with -test, then set TC_USE_TEST_ATTR_MAPPINGS on an administrator session only. We’d advise against a production import until NX and the item revision show the same properties.
Setup Sequence We Use
TEM click paths change by release, so we do not invent them. Server gets the Teamcenter Integration for NX data model; each CAD seat gets NX rich-client integration bound to that NX directory. Use the Siemens guide for your Teamcenter drop.
Sequence:
- Freeze the item type and UGMASTER (NX dataset) in the Teamcenter data model.
- Install Teamcenter Integration for NX on the server so the dataset model exists.
- On each CAD client, install NX, then the NX rich-client integration via TEM, pointed at that NX directory.
- For the proof part, start NX only as managed NX from Teamcenter (NX Manager), never from a native shortcut.
- Create a new part on the intended item type and save so Teamcenter creates the NX dataset on the revision.
- Check in. Open the NX dataset. Use NX Properties (June 2025 managed-mode docs): forms table and files/named references both populated.
- Repeat from a second client. One seat only means a client install, not a data-model win.
NX 2506 TcIN added dialog sizing and related-file export (Siemens Community, 26 November 2025). Usability, not a substitute for steps 1-7.
The First Save and Check-In That Proves It
The proof is not “NX opened.” It is an item revision whose NX dataset holds the part file, is checked in, and opens from a second managed session. Until that loop closes, you do not have Teamcenter NX integration. If save creates an item with no UGMASTER, stop modelling and fix the dataset model.
NX Properties on the dataset
Open the NX dataset, open NX Properties, confirm attached forms, then attached files and named references. An empty files table means the part was not vaulted, even if the item ID looks right.
# Managed check-in proof (one item type, two clients)
# A. Launch managed NX from Teamcenter Integration for NX.
# B. Create a part on the intended Item type. Save.
# C. Confirm UGMASTER exists on the new ItemRevision.
# D. Check in. Dataset must not stay checked out to user one.
# E. NX Properties: forms table + files/named refs.
# F. Second client: open the same revision in managed NX.
# Fail if any of C-F is missing. Do not proceed to BOM or AI.Active Workspace is not the proof
On 10 October 2025 Siemens published that in Teamcenter 2412 the Named Reference tab on UGMASTER is restricted in Active Workspace on purpose. Downloading NX files that way is not supported. The documented AW path is Export NX Assembly. “I cannot download the .prt from AW” tests a designed client limit, not a broken vault. Rich Client still shows named references when an admin must see the files.
Check-in just worked. Production still fails when item types, mapping, and sites stay undefined. A copilot on the wrong dataset will quote the wrong revision with perfect confidence. We close that production gap on your Teamcenter data: Teamcenter AI on a governed NX dataset.
Failure Modes to Check Before You Scale
Most tickets are dataset, mapping, or client mismatches, not a broken NX licence. Check the row that matches what you see, then fix that layer only. Do not open a Siemens IR until UGMASTER, mapping, and launch path have been ruled out.
| Failure mode | What you see | What to check |
|---|---|---|
| Wrong or missing NX dataset | Item exists, no UGMASTER, or a custom dataset with no part file | Data model: NX dataset on that item type; first save in managed mode |
| Attribute mapping drift | NX and Teamcenter properties disagree (type, owner, last mod) | export_attr_mappings; KB000215723 display vs DB_REV_TYPE; -test import |
| AW vs rich client | Named Reference download missing in AW on UGMASTER (2412+) | Designed AW block; Export NX Assembly; inspect files in NX Properties or RAC |
| Native session used for the proof | .prt on disk, Teamcenter item unchanged | Launch managed NX / NX Manager, not the native shortcut |
| Client integration missing | Teamcenter cannot start NX, or NX never sees Teamcenter | TEM NX rich-client integration, NX directory bound |
| One site maps, another does not | Check-in works in HQ, fails at a second site | Same item type, mapping file, and dataset type |
Multi-site mapping
inteliScience (nearshore from Romania, Siemens NX and Teamcenter work for DACH) will not bless a multi-site rollout until the table is green on two clients and two item IDs. Teamcenter 2606 can clone huge structures. Cloning a broken dataset model only multiplies it.
Once that proof holds, the rollout becomes a project of its own. We plan templates, standards and the switch-over site by site as part of our Siemens NX rollout service, so design work keeps running.
For users who are new to Teamcenter, our Teamcenter training covers items, revisions, datasets and opening and saving NX parts from Teamcenter.
Frequently Asked Questions
These five questions are the ones engineering and IT leads ask before they fund a copilot or a BOM job. Answers assume Siemens NX (Designcenter from the June 2026 rename) plus Teamcenter Integration for NX, not a generic file vault.
How do you set up Teamcenter NX integration for an engineering org?
Make the item type and UGMASTER legal first, install Teamcenter Integration for NX on the server and the NX rich-client integration on each CAD seat, then launch managed NX only. Done means one part saves, checks in, and opens from a second client with named references on the dataset.
What is the difference between managed NX and native NX?
Managed NX (NX Manager) binds the session to Teamcenter so save and check-in vault an NX dataset on an item revision. Native NX writes a filesystem .prt. Same modeller, different master. Only managed NX is Teamcenter NX integration.
How much does a Teamcenter NX integration project cost?
Cost follows the dataset model, the size of attribute mapping (custom item types and LOVs), and the number of sites that must share the same TEM and mapping. Licence list price is not the driver. A focused pilot on one item type and two clients is the shape of the work. Mapping and sites stretch calendar and budget.
Teamcenter Integration for NX vs NX Manager: which name is right?
Teamcenter Integration for NX is the product and documentation name. NX Manager is the managed-mode session people still launch.
Active Workspace or rich client: which one proves check-in?
Neither client is the vault. Proof is the NX dataset on the item revision. From Teamcenter 2412 on, AW will not give a UGMASTER named-reference download; use Export NX Assembly. Inspect files with NX Properties or rich client.
Next Step
If NX parts still live beside Teamcenter instead of inside it, inteliScience should look at the dataset model and the first check-in with you.