Case Study: Piper Aircraft M600 Wing — NX and Teamcenter Under Strict Weight Constraints

Source: "Aircraft manufacturer uses NX CAD and Teamcenter to develop wing that increases fuel payload by 35 percent" URL: https://resources.sw.siemens.com/en-US/case-study-piper/ Named subject: Mike Rushworth, Lead Engineer, Structures Group, Piper Aircraft Inc. (Vero Beach, Florida)

What this case study actually is

This is a named, quoted Siemens customer case study — the strongest sourcing tier found in this research pass, since it has a real person, title, and company attached to direct quotes. However, it is important to be precise about scope: it is a case study about clean-sheet wing design under weight constraints, told through NX CAD and general Teamcenter part-tracking, not a case study of the Weight and Balance Management BOM capability described in wb-siemens-blog-weight-balance-overview.md. No mass-rollup, CG-envelope, or weight-target-tracking workflow specific to that named module is described. This distinction matters — do not conflate "Piper used Teamcenter while also caring a lot about weight" with "Piper is a documented Weight and Balance Management customer."

What Piper actually did, per Rushworth's quotes

• The M600 wing was a clean-sheet design evolved from the M500: "We did the initial structural wing layout in NX, positioning ribs, spars, flaps, etc. From the initial layout we developed detailed models."
• The central engineering constraint was weight headroom: "The main technical challenge we faced was meeting weight requirements because there wasn't a lot of extra weight allowance from the M500 to the M600."
• NX CAD's mass-property/design-exploration capability was credited generally for surfacing weight-saving opportunities and, by extension, cost: "NX CAD allows you to identify weight savings" and helped take cost out of the aircraft.
• Teamcenter's documented role in the case study is part and configuration tracking — knowing exactly where each part was in the design process (layout vs. finished detail) so manufacturing could see what was coming, and so Piper could always reconstruct the original configuration of a given aircraft (relevant since Piper builds many unique/customized aircraft). This is standard PLM/BOM configuration management, not the weight-rollup/target-tracking feature set.

Quantitative results (aircraft-level, not weight-tool-level)

• Fuel capacity: 260 gallons (M600) vs. 170 gallons (M500) — a 35% increase
• Useful load: 2,400 lb (M600) vs. 1,698 lb (M500) — a 29% increase
• Range: 1,658 NM (M600) vs. 1,000 NM (M500) — a 40% increase

These are real, named, quoted figures from the case study as fetched — not estimated or inferred.

Assessment / honest gap

No independently-verified Siemens or third-party case study was found in this pass that names a specific customer using the Weight and Balance Management BOM module (mass-target tracking, CG envelope, as-weighed vs. estimate reconciliation) end-to-end with quoted results. The Piper case study is the best adjacent evidence — a real aerospace OEM, a named structures engineer, and a direct quote establishing that weight was the single hardest constraint on the program — but it documents NX-level mass-property design work and general Teamcenter BOM/configuration tracking, not the specific weight-and-balance reporting capability. This gap is also noted in the index file.