MBSE Organizational Adoption: The 'Transplant' Framing and Simcenter/HEEDS Workflow Integration

Source 1: Adopting MBSE Into an Existing Organization

"System Engineering Process from Inside-out" — Siemens Teamcenter blog, Mark Sampson, January 20, 2020. https://blogs.sw.siemens.com/teamcenter/system-engineering-process-from-inside-out/

Sampson's core argument: most real-world engineering work is improving an existing product, not starting a clean-sheet design — so any honest MBSE adoption plan has to deal with legacy systems, legacy process, and legacy organizational habits, not just pick a modeling tool.

His framing is an analogy to organ transplantation:

"Replacing existing critical legacy organization systems with models/tools is a transplant-like experience" — requiring coordinated change across process definition, organizational buy-in, training, financial planning, and management support, not a tool swap.

He explicitly names three dimensions that must change together for MBSE to succeed: people, process, and tools. Tool selection alone is treated as insufficient and likely to fail without the other two.

The post references Siemens Healthcare as an example of MBSE adoption succeeding inside a regulated industry with legacy-system conflicts (a real Siemens business unit, though the blog post does not go into implementation specifics — no numbers, timeline, or named systems are given, so this should be read as an illustrative internal reference rather than a documented case study).

Source 2: Simcenter/HEEDS Workflow Integration

"Leveraging an integrated MBSE workflow to deliver better designs" — Siemens Teamcenter blog, Alexandre Poisson and Alex Graham, February 8, 2023. https://blogs.sw.siemens.com/teamcenter/leverage-better-designs-with-mbse/

This post describes a specific cross-tool workflow rather than adoption philosophy:

• System engineers define architecture/requirements in an MBSE authoring tool (the post names System Modeling Workbench (SMW), Rhapsody, and Catia Magic as interchangeable options at this layer).
• Simulation specialists then build domain-specific models in Simcenter (the post names Amesim, STAR-CCM+, and unspecified "3D" simulation tools).
• Requirements become constraints in optimization studies run through HEEDS (Siemens' design-space-exploration/optimization tool), closing the loop between systems requirements and simulation-driven design exploration.
• Teamcenter sits underneath as the PLM backbone holding the traceable links.

Claimed benefit: engineers can re-run optimization when requirements change without extensive rework, because "everything he needs is already there" (direct quote from the post, referring to a hypothetical engineer in the article's illustrative scenario — not a named real engineer).

A separate, related YouTube video — "Fully integrated MBSE workflow with Teamcenter and Simcenter #HowToTeamcenter" (Feb 2023, https://www.youtube.com/watch?v=xwXw7BAZt3Q) — appears (per its title/search-snippet metadata only) to cover the same closed-loop MDAO (multidisciplinary design analysis & optimization) workflow, available as of Teamcenter 14.2 / Active Workspace 6.2 / HEEDS 2210. See mbse-video-tutorials.md for why the actual video content could not be verified.

Honest Note

Both sources are Siemens blog posts with named individual authors (a positive for traceability) but are still vendor content, not independent case studies. The "Siemens Healthcare" reference in Source 1 is a real internal example but was not corroborated with any independent source, external press release, or technical detail in this research pass — it should not be cited as a verified case study, only as "Siemens' own blog references this internally."