How Weight Data Actually Gets Into the System: NX Mass Properties and Advanced Weight Management

Siemens' Weight and Balance blog post (wb-siemens-blog-weight-balance-overview.md) describes the Teamcenter-side reporting/tracking experience but says almost nothing about the mechanics of how mass values are actually calculated and asserted at the CAD level. This file covers that lower layer, sourced from a Siemens design-tooling blog and community-forum search snippets (full forum page content was not fetchable — see caveat below).

Primary source: NX Tips and Tricks blog

"Mass Property Management" Author: Jimmy Costello, Associate Technical Product Manager, Siemens Digital Industries Software Published: February 13, 2026 URL: https://blogs.sw.siemens.com/designcenter/nx-tips-and-tricks-mass-properties/

Key points:

• Framed as NX's "digital scale and balance" for 3D models/assemblies — calculating weight, density, volume, center of gravity, and moments of inertia directly from geometry and assigned materials, before any physical prototype exists.
• Configuration lives under Gateway > Customer Defaults > Materials/Mass. A Roll-Up attributes tab lets an admin check "Create Attribute" for specific mass properties, which automates writing those values out as attributes directly onto part/assembly files — this is presumably the mechanism that feeds structured weight data up into Teamcenter's BOM rather than leaving it trapped inside NX part files.
• The tool tracks and lets a user compare multiple parallel value columns for the same property: asserted, actual, estimated, and budget — i.e., the "target vs. estimate vs. as-weighed" distinction from the Teamcenter blog post is visible even at the NX authoring level, not just in Teamcenter's reporting layer.
• Positioned as turning weight management from reactive to proactive by surfacing reduction opportunities and material-impact trade-offs during design, not after.

This article does not itself describe the Teamcenter integration/rollup mechanism — that connective tissue is inferred, not confirmed, from the "Roll-Up attributes" terminology.

Community forum findings (title/snippet-level only — see caveat)

Search snippets (not full page fetches — see caveat below) surfaced a consistent, recognizable practitioner pain-point pattern around the older "Advanced Weight Management" command in NX, which appears to be the direct predecessor/component of what the 2026 blog post above calls "Mass Property Management":

• Command relocation confusion: a community question titled "Where is Assembly-'Advanced Weight Management' command in NX 1899, I cannot find it anymore" — indicates the feature was renamed, moved, or restructured around the NX 1899 release, causing user confusion. (Full thread content not retrievable — see caveat.)
• Asserted mass showing zero: multiple distinct threads describe mass/volume/center-of-mass values showing as zero after running Advanced Weight Management, or asserted values not propagating correctly into upper-level assemblies — a recurring class of bug/gotcha where assertion doesn't take effect as expected.
• Motion/simulation disconnect: a thread titled "NX-Motion and Link to components with asserted mass properties do not work" — suggests asserted mass values set via Advanced Weight Management are not automatically honored by NX Motion/simulation, meaning a user has to be deliberate about where in the toolchain an asserted value is actually being read.
• Removal mechanism: per an eng-tips.com community answer, assertions are removed via Analysis > Advanced Mass Properties > Advanced Weight Management > Work Part > Remove Assertions — a specific, verifiable menu path, useful as a concrete fact even without the full thread text.
• Import/STEP interaction: a thread describes mass properties appearing correct for individually-imported STEP files but summing to zero once placed into an assembly set to use "as Asserted" properties, if the part file itself lacks asserted values — a data-completeness trap for anyone assembling mixed-source (native + imported) geometry.

Caveat: community.sw.siemens.com is not reliably fetchable

Consistent with prior research passes in this KB (see rm- and other _agent-*-community-index.md files), community.sw.siemens.com and community.plm.automation.siemens.com pages returned only page chrome / a CSS-error placeholder to WebFetch, not actual thread content. Everything in the "Community forum findings" section above is reconstructed from search-result snippets only (titles plus a short excerpt), not from reading the full threads, answers, dates, or usernames. Treat these as directionally real (the thread titles and topic pattern are consistent and specific enough to be credible) but not verified in full — do not attribute specific dates, resolution steps beyond what's quoted, or usernames, since none were actually visible in the retrieved content.

Assessment

The real mechanical story is: NX's Mass Property Management / Advanced Weight Management is where mass gets calculated and "asserted" (i.e., manually overridden or locked, e.g., for a purchased/standard part whose real weight differs from raw-geometry-times-density), and a Roll-Up attributes mechanism appears to be the bridge that exposes those values as structured attributes Teamcenter can then track, budget against, and report on. The community forum evidence, even at snippet level, shows this is a real, actively-used feature with a real practitioner support burden (renamed commands, zero-value bugs, assembly propagation gaps) — a level of organic community activity that the Weight and Balance BOM-reporting layer itself does not appear to generate (no comparable Teamcenter-side community threads about the W&B reporting feature were found in this pass).