TeamcenterKnowledge

Community Knowledge > MBSE

System Modeling Workbench: Teamcenter + Capella/ARCADIA Integration

What This Is

System Modeling Workbench (SMW) is a joint Siemens + Obeo product — Obeo is the French software company that stewards Capella, the open-source MBSE tool built around the ARCADIA methodology (Architecture Analysis & Design Integrated Approach). ARCADIA was originally developed inside Thales starting around 2000, as Thales evolved from an equipment supplier to an integrated-systems supplier and found SysML (as it existed at the time) insufficient — Thales built ARCADIA in-house specifically so all stakeholders (not just modeling experts) could share one methodology and one model. Capella/ARCADIA is now an Eclipse Foundation open-source project with an industry consortium that includes Thales and Obeo.

Sources:

How SMW Actually Connects to Teamcenter (per Obeo's own page)

  • Architecture designed in SMW is transformed into coarse-grained RFLP data for Teamcenter's Common Architecture Information Model — i.e., Capella models don't live natively as Teamcenter objects; they get published/mapped into Teamcenter's RFLP structure.
  • Requirements traceability is bidirectional between Teamcenter Requirements and SMW models.
  • Parameter management is two-way linked with Teamcenter Parameter for design values.
  • Product configurator support: SMW-authored variability is tied to Teamcenter Product Configurator variants.
  • SMW is described as "natively based on Capella" — i.e., it isn't a from-scratch tool, it's Capella wrapped/extended with Teamcenter connectivity.

Origin Story (2018 Announcement)

Siemens PLM Software announced the Obeo partnership on June 4, 2018 at Siemens PLM Connection Americas in Phoenix, AZ. Named quotes from that announcement:

  • Etienne Juliot, Obeo VP/co-founder: "Managing the system, software and hardware architecture characteristics in an integrated repository that is 'single source of truth' uniquely enables a digital thread."
  • Tony Hemmelgarn, then-Siemens PLM Software CEO: "Siemens' System Driven Product Development solutions are unique to the market in the way that we are able to integrate MBSE throughout the entire product life cycle."

The stated goal was multi-domain digital twin support spanning Teamcenter, Simcenter, Capital (electrical), NX, and Polarion.

Real Practitioner Q&A: What SMW Actually Does and Doesn't Do

This is the most valuable and concrete find of this research pass — an actual practitioner exchange on the Eclipse Capella community forum, thread "System Modeling Workbench: How do Capella and Teamcenter interact?" (https://forum.mbse-capella.org/t/system-modeling-workbench-how-do-capella-and-teamcenter-interact/6340).

User "Epictetus" (May 8, 2023) asked four concrete integration questions that anyone evaluating SMW would actually need answered:

  1. Does Teamcenter become the source of truth for system parameters, requiring manual import/export via PVMT (Parameter and Variable Management Tool)?
  2. Do requirements stay synchronized across both tools, or is there one master?
  3. Is SMW's view inside Teamcenter Active Workspace read-only (like an XHTML render), or can you actually build models there?
  4. Does Teamcenter replace Git/"Team for Capella" for model collaboration, or do you need all three (Teamcenter + Git + Team for Capella)?

"LaurentDelaigue" answered (May 9, 2023), and the answers are specific and slightly less rosy than the marketing pages imply:

  • Parameters: "Teamcenter is the source of truth," synchronized as PropertyValueGroups — but no PVMT integration exists (as of that date).
  • Requirements: Teamcenter owns requirements outright; Capella can only edit the links between requirements and model elements, not the requirements themselves.
  • Editing: Capella is the sole authoring tool for Capella models — once an architecture is published into Teamcenter as RFLP, it becomes read-only there. This confirms SMW/Teamcenter is not a place to edit architecture; it's a place to consume and trace it.
  • Collaboration: Both "Team for Capella" (Capella's own collaborative model-versioning add-on) and Git remain necessary alongside SMW/Teamcenter — SMW does not replace either. So a full SMW deployment realistically means three tools in play (Capella + Team for Capella/Git + Teamcenter), not a single consolidated one.

A follow-up post from another user on November 8, 2023 asked for the promised workflow-documentation slides referenced earlier in the thread — which, as of that post, had not been provided. This is a small but telling practitioner-level signal: even six months after a detailed technical Q&A, requested follow-up documentation from the vendor/community side hadn't materialized.

Scaled Agile Angle

The Wickers blog (April 2024) makes the case that SMW/Capella's capability decomposition maps cleanly onto SAFe: capabilities in the model "typically span multiple Agile Release Trains," functional chains/requirements translate directly into features for Program Increment planning, and full traceability lets teams organize work breakdown for design/dev/test. Illustrated with a Netflix-style streaming service example (illustrative, not a real customer).

Honest Note

The forum thread is the single most credible, non-marketing source found in this entire MBSE research pass — it's a real named (if pseudonymous) practitioner asking pointed questions and getting specific, sometimes unflattering answers (no PVMT integration; three tools still required; promised docs undelivered after six months). Treat the vendor blogs' framing of "single source of truth" and "seamless" with that forum thread's more granular caveats in mind. No named aerospace/defense customer specifically using SMW (as opposed to Capella alone, which Thales/Thales Alenia Space do use — see mbse-aerospace-defense-notes.md) was found.

Source: https://www.obeosoft.com/en/products/smw/ · retrieved 2026-07-10