| Vincent Saluzzi |
Does the TC variant integration have any correlation to the ‘Pure Variants’ connecter? |
Teamcenter Variant integration does not rely on the ‘Pure Variants’ connector from PTC. Instead, Teamcenter uses Siemens’ native Product Configurator for managing system and product variability. |
| Adil Yilmaz |
Is there a unified approach for suppliers using different versions or types of modeling tools (e.g., SWM, Cameo, CAD tools)? |
OEM and suppliers should be on same version of SMW as whence the project is migrated to new version it can’t be opened in previous ones. Some interoperability with SysML v1.4 is possible via an import/export feature built in SMW. This can be extended to adapt to specific needs on demand, as a service. The main supported mappings are described on this page: https://www.obeosoft.com/en/products/sysml-bridge-for-capella |
| Vincent Saluzzi |
How will an SMW model immediately and visually update the Architect that simulation results presented architecture non-compliances? |
System model parameters optimized by simulation are synced back in SMW system architecture automatically on the next project load or sync operations. Architecture changes recommended as an outcome of verification / simulation goes through a change process. |
| Vincent Saluzzi |
How does SMW address roles and accesses within a given project/model? Whereby not all users have the same access to all aspects of the architecture? How is that coherence maintained across the S2S model transition? |
Access control is managed at the project level. When multiple groups or teams collaborate on the same system, best practice is to break down the project model into subsystem projects or libraries, each with its own access control. |
| Vincent Saluzzi |
Where can Siemens provide a comparative between SMW/Capella and the Siemens SysML v2 proposition? |
SysML v2 and SMW (Capella/Arcadia) serve different but complementary roles in MBSE. SysML v2 is a general-purpose, formally defined modeling language designed for flexibility, precision, and strong automation support, making it suitable for complex, multi-domain systems. In contrast, SMW, based on the Arcadia method, offers a mature, guided, and user-friendly approach focused on system engineering processes with a strong emphasis on usability and consistency. While SysML v2 targets broad adaptability and digital engineering integration, SMW excels in structured, top-down systems analysis with robust tooling already in place. |
| Uday Chandra Gollapalli |
The exchange of MBSE models across companies for collaboration is a challenge. Are there any model exchange portability limitations of these system models from one machine to another ? |
Leveraging Teamcenter supplier collaboration, project models can be shared with partners in secured and seamless manner. You can define which projects to be shared and by whom partners contact. You can also define a timebox a project can be accessible. A partner contact with rights access to a SMW project model can download, edit and upload it back. OEM and Partner should be on the same SMW version or agree to migrate the design to a newer SMW version. |
| Adil Yilmaz |
How do you measure and ensure the performance and responsiveness of the system when managing large interconnected datasets? |
Recommendation is to breakdown the system into subsystem project/libraries to enhance the performance while improving the collaboration. |
| Eric Wines |
Does new Tc SMW install ask what Tc server to connect to? don’t want to edit multiple config files to try to make a Tc connection from SMW |
SMW-2406 provides a Teamcenter preferences UI to define the connectivity parameters. |
| Adil Yilmaz |
MBSE success strongly depends on high-quality data and committed stakeholder involvement. How do you ensure data quality across the multidisciplinary teams involved? |
Data quality across multidisciplinary teams should first be ensured through standardized modeling practices, clear data governance policies, continuous validation processes, controlled vocabularies, enforce version control and traceability. Equally important, stakeholders should be engaged through regular reviews, cross-functional collaboration, and role-based access to ensure everyone contributes accurate, consistent data throughout the system lifecycle. |
| Adil Yilmaz |
What is your opinion on this; should companies dealing with complex systems with multi domains have specific System Modelers on top system architects, or system architects should also wear system modeler hat? |
Having separate System Modelers and System Architects is often beneficial for complex, multi-domain systems. Architects focus on high-level design and stakeholder alignment, while modelers specialize in precise, tool-based modeling. This division ensures depth in both strategy and execution. However, in smaller or less complex projects, one person could effectively wear both hats. |
| Karthik Nageshwara Rao |
Is Team Center product Configurator integrated with other System Modelling Tools besides SMW? |
SMW is currently the only system modeling tool integrated with Teamcenter Product Configurator, with Cameo and Rhapsody integration planned for upcoming releases. |
| Mark Walter |
Can requirements be written and managed in SMW or does this have to happen in TC? If it can happen in SMW, do they synchronize with TC? |
System Modeling Workbench (SMW) provides a tight integration with Teamcenter Requirements Management, allowing engineers to link requirements to system model elements. However, the authoring and primary management of product requirements happen in Teamcenter, not in SMW. |
| Hans-Günter Thonemann |
In which way may SysON play a role for your SYSML 2.0 strategy? |
Our strategy remains consistent in supporting a multi-tool, multi-vendor approach and opened to partnership. Anyone can implement an integration using our APIs and if a customer requires integration of SysON with our MBSE solution, we are open to implementing it. The same applies to any other third-party tools. |
| Hans-Günter Thonemann |
In which way are you incorporating generative AI and machine learning into your SMW/Teamcenter strategy? |
We are exploring AI to enhance MBSE by automating routine tasks, improving model quality, and accelerating development through intelligent assistance and reuse. Key applications include using NLP for requirement analysis and traceability, generating and transforming models from text or legacy data, exploring design alternatives through optimization algorithms, detecting anomalies and supporting formal verification, enabling pattern reuse and intelligent recommendations, and improving simulations and predictions with AI-driven analysis and learning techniques. |
| Naresh Kumar |
Does TC MBSE has integration with CATIA Magic? |
Cameo (Catia Magic) can be integrated with Teamcenter by a connector owned and sold by our partner HCL |
| Naresh Kumar |
Is MBSE supporting Arcadia / capella only? Is there any support for SysML 2.0? |
Teamcenter MBSE supports both Capella and SysML v1 models, with SysML v2 support coming soon |
| Eric Dano |
How are the parameters defined in SMW objects to match the myriad of domain parameters ( e.g. ME thermal, production, sustainability, etc.)? |
SMW metamodel can be extended using Property Value Groups (PVGs) to define domain-specific properties for different disciplines. |
| Anbarasu Mullainathan |
Multi-domain verification needs “Tc Simulation Process Mgmt” module/license in addition to System Lifecycle Mgmt package right? |
Correct |
| Eric Dano |
How are 3rd party/proprietary Apps added into team center for use in architecture alternative selection, etc. |
Sorry Eric, I don’t understand the question. |
| Anbarasu Mullainathan |
Are we getting rid of “SYSML_BHM_INT_DEF_FILE” for mapping mechanism and use AWC interface to define & update the mapping between SMW & Tc objects? If yes, from which Version, we can expect that? Thanks |
The integration mappings can be edited in the new Teamcenter Active Workspace IDF Editor location. The editor has been added in Teamcenter 2312. |