Date: Fri, 29 Mar 2024 09:40:53 +0100 (CET) Message-ID: <400406598.1752.1711701653936@nm-docs> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1751_1237982451.1711701653936" ------=_Part_1751_1237982451.1711701653936 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Teamcenter Integration plugin is disco= ntinued
Starting with version 2022x, the Teamcenter Integration plugin is no lon= ger available. You may continue to use your perpetual license of the produc= t in accordance with the terms of your license agreement. The support for t= he product will be provided until the end of your current maintenance suppo= rt subscription.
The Teamcenter Integration plugin complements Teamcenter =E2=80=93 Siemens Product Lifecycle Management (PLM)= software =E2=80=93 with UML/SysML modeling capabilities provid= ed by No Magic modeling tools. This state-of-the-art integration is the res= ult of collaboration between Siemens PLM and No Magic, Inc.
The Teamcenter Integration plugin =
allows you to expose PLM operations, such as saving, updating and revising,=
within No Magic modeling tools. You can manage and reuse UML/SysML models =
by storing model files as modeling baselines. It is also possible
The plugin integrates the Active Workspace Client into No Magic modelin= g tools. This allows you to browse Teamcenter data, including exported SysM= L elements and diagrams, without leaving the modeling tool environment.&nbs= p;You can import/export= items or model elements as bill of materials (BOM) to/from No Magic modeli= ng tools, and synchronize changes from a modeling tool to Siemens Team= center and vice versa. The Teamcenter Integration plugin comes with a compl= ete mapping scheme that is available out-of-the-box. The mapping scheme is = based on the best fit between SysML and RFLP (Requirements, Functional, Log= ical and Physical approach). Additionally, the default mapping is customiza= ble on a single property level.
The Teamcenter Integration plugin = gives you the benefit of using SysML functional behavior modeling to comple= ment the Teamcenter multi-domain system modeling with the model driven func= tion allocation and system interface definition. You can also enable model = driven requirement engineering using No Magic modeling tools. This all= ows you to take advantage of model driven requirement analysis and val= idation.