Named Customer Case Studies Touching Teamcenter Requirements Management

Genuinely named, attributable case studies specific to Teamcenter Requirements Management (as opposed to Teamcenter PLM generally) are scarce in public material — consistent with the pattern already observed for Schedule Manager/Program Planning in this KB. Two real, named data points were found.

Teradyne (electronics/semiconductor test equipment, Siemens case study)

Teradyne is a ~2,900-employee manufacturer of automatic test equipment for consumer, automotive, computing, telecom, aerospace, and defense electronics, headquartered in North Reading, Massachusetts. Per Siemens' own case study ("Engineering change-order cycle cut by 84 percent, $2 million saved yearly"):

• Teradyne consolidated six disparate design-center applications (East Coast and West Coast) into one standardized Teamcenter-based process, and unified six different part-revision schemas and ~300 part-number prefixes into single alphabetical/unified schemes.
• Product and project information — requirements, parts, specifications, changes, BOMs, documentation — was centralized into Teamcenter paired with Microsoft Office SharePoint Server, replacing manual/paper-based engineering-change workflows and email-based document review.
• Cited metrics: engineering change-order cycle time reduced from 90 days to 14 days (84% reduction); change-order rejection rate fell from 70% to 26%; change-order implementation costs down 60%; project slip rate improved from 7.5% late to 4% early; $2 million in annual savings; a further $500,000 in potential Oracle maintenance savings cited as an ancillary benefit.
• Quotes attributed by name: Bill Duggan (Engineering Manager) — "We're not just meeting our promised delivery dates – we're beating them." Chuck Ciali (CIO) — on now collecting both engineering and unstructured data in one place.
• Caveat: this case study is about the broader Teamcenter-plus-SharePoint change/requirements-consolidation initiative, not a narrowly-scoped "we deployed Teamcenter Requirements Management module X" story — requirements management is one thread in a larger PDM/change-management transformation.

Siemens Healthcare (MBSE adoption, referenced in a Siemens blog, not a formal case study)

Mark Sampson's Siemens Teamcenter blog post "System Engineering Process from Inside-Out" (January 20, 2020) references Siemens Healthcare as an example of successful Model-Based Systems Engineering (MBSE) adoption specifically in a regulated industry facing legacy-process conflicts. This is a passing reference inside a broader change-management/analogy-driven blog post (the post's central device is comparing MBSE rollout to a hospital organ-transplant program), not a dedicated, metrics-bearing case study — no specific numbers, dates, or named individuals from Siemens Healthcare are given. Treat this as a named-but-thin data point, not a substantiated case study.

What was not found

No named aerospace/defense or automotive customer case study specifically calling out Teamcenter Requirements Management (the RM module, as distinct from Teamcenter PLM broadly or Teamcenter for Systems Engineering broadly) was found with verifiable metrics in this research pass. Generic references to "an aerospace and defense enterprise" or "a diesel engineering division" using Teamcenter's RM/systems-engineering capabilities appear in search-result summaries but were not traceable to a specific, named, fetchable source — they are not included here to avoid presenting unverified generic marketing claims as case studies.