Adjacent Capability: Weight Data Feeding Teamcenter Product Cost Management

Why this is in the Weight and Balance research pass

This is a genuine adjacent finding, not the core module, but worth capturing because it shows weight data has a second consumer inside Teamcenter beyond the Weight and Balance BOM reports themselves — relevant to anyone mapping out where mass data flows once it exists in the system.

What was found

Siemens Teamcenter blog content on Product Cost Management (multiple posts under blogs.sw.siemens.com/teamcenter, including "What's new in Teamcenter Product Cost Management?" dated June 10, 2025, and version-specific "What's New in 2406" posts) describes:

• Fraction bars in cost breakdown sheets showing the weight of different cost sources within a part's final net sales price, and separately, the weight of different carbon-footprint sources — i.e., "weight" here is used in the statistical/proportional sense (share of total cost) as well as literal mass, and the two usages should not be confused when reading Siemens material.
• Automatic transport-weight calculation: transport cost tooling can automatically calculate transport weight based on part weight plus package weight — a direct, literal-mass use case, implying part mass data (potentially originating from the same NX/Advanced Weight Management assertion pipeline described in wb-nx-mass-properties-mechanics.md) is reused for logistics costing, not just engineering weight-target tracking.
• Transport Cost and Carbon Calculator: users can enter transport quantity or transport weight, which is exported via a cloud service to Siemens Digital Logistics, where cost and carbon footprint are calculated externally and returned.

Assessment

This is a real but secondary finding: it confirms that "weight" as a data element in Teamcenter is not siloed to the Weight and Balance Management module alone — it's reused downstream for logistics/transport cost and carbon-footprint estimation in Product Cost Management. No direct architectural documentation was found describing whether these two capabilities (Weight and Balance vs. Product Cost Management's transport-weight field) actually share the same underlying attribute/rollup, or are independently maintained — that connection is plausible but not confirmed, and should be treated as an open question rather than a verified integration.