PLM XML and Teamcenter XML

Download as pdf or txt
Download as pdf or txt
You are on page 1of 22
At a glance
Powered by AI
PLM XML and TC XML are two XML formats used for data sharing and integration in Teamcenter. PLM XML is used for integration with external applications while TC XML is used internally within Teamcenter.

PLM XML provides a lightweight format for transporting product data over the internet to connect Siemens PLM products and third party applications. TC XML schema closely matches the Teamcenter data model and is used for federated data sharing within Teamcenter.

PLM XML does not support the replica concept and imported data is locally owned. TC XML supports referential integrity and replication of data between sites. PLM XML is easier to process and map while TC XML graphical mapping is possible.

PLM XML and Teamcenter XML

Comparison, in-depth Technical


analysis and best practices for
deployment

Reiner Kaiser, PhD


Siemens PLM

http://plmworld.org/ 1
Platform Extensibility Services

© Siemens AG 2011. All Rights Reserved.


Page 2 May-11 Siemens PLM Software
Platform Extensibility Services
PLM XML and Teamcenter XML

 Features, Performance
Characteristics and use cases
of each XML flavor

 Solution Spaces and best


practices

 performance and scalability


considerations

 side by side “at a glance”


Comparison

© Siemens AG 2011. All Rights Reserved.


Page 3 May-11 Siemens PLM Software
PLM XML

PLM XML provides a lightweight, extensible and flexible mechanism for


transporting high-content product data over the Internet, and aims to form
the basis of a rich interoperability pipeline connecting Siemens PLM
Software products and third party adopter applications

 Language definition serving as interface to Teamcenter PLM data


(configured and unconfigured)

 widely used by customers and partners


(solves “n squared problem”)

 accessible via published SDK

© Siemens AG 2011. All Rights Reserved.


Page 4 May-11 Siemens PLM Software
More Key Features of PLM XML:
No Replica Concept (imported data is locally owned, exported data
does not have Export Records and there is never any Ownership
Transfer)

No Site Referential Integrity (Imported Data can be deleted without


impacting the original objects)

 Do not share data using PLM XML between two sites connected by
Multi-Site, if the same objects are to be replicated later via CMS or GMS.

 Supports Delta Import

“appRef” concept to establish stable identity for update use cases, also
valid for BOMLines (XML contains both instance graph and ProductView)

 BOMWriter is based on PLMXML export logic and is the fastest and


easiest way of identifying Configured ItemRevs in a BOM
© Siemens AG 2011. All Rights Reserved.
Page 5 May-11 Siemens PLM Software
PLM XML in Tc 8.3

Teamcenter

RAC P
L 3rd Party
Web M System
Teamcenter X
Cmd M
L
Workflow Tecnomatix

Visualization

© Siemens AG 2011. All Rights Reserved.


Page 6 May-11 Siemens PLM Software
PLM XML Import Export Framework – Export Scenario

PLM XML
Framework
Inputs
A set of tags Transfer Mode
(could be CC object) PLM XML
Context of export -Closure Rules file
-Filter Rules
-Property Sets
-Action Rules

© Siemens AG 2011. All Rights Reserved.


Page 7 May-11 Siemens PLM Software
PLM XML Import Export Framework – Import Scenario

PLM XML
Framework

Transfer Mode Teamcenter objects


PLM XML
get created
File
Context for Import -Closure Rules
-Filter Rules
-Property Sets
-Action Rules

© Siemens AG 2011. All Rights Reserved.


Page 8 May-11 Siemens PLM Software
PLM XML performance considerations / limitations

 Memory/performance overhead of configured structure traversal limits


maximum size of configured assemblies

 Structures of up to 500000 lines have been processed successfully.


However:

 Focus should be on optimization of closure rules, property sets, BOM


configuration to minimize amount of data processed. Traversal of
smaller substructures where possible

 Maximize address space (/3GB switch on Windows etc.)

 Oracle performance tuning: cache settings and missing indices


db_cache_size = 4 - 5 GB, sga_max_size = 4 - 5 GB
index_verifier –u=<uname> –p=<pwd> > missing_indices.txt

© Siemens AG 2011. All Rights Reserved.


Page 9 May-11 Siemens PLM Software
TC XML based Data Transfer:

new flavour of XML, very close to persisted Teamcenter Data Model


TC XML payload has the following characteristics:

high flexibility providing open mapping between dissimilar data models,


allowing customization of data model and simplifying data model upgrades
(bi-directional)

Teamcenter can produce/ consume TC XML with high level of


data model coverage (close to 100% of TC data model
in the TC 8.3 time frame)

Customizable data scoping to address individual customer needs on a


business process level, customization interface tightly integrated
with business modeler application (Transfer Modes, Closure Rules,
Property Sets and Option Sets)

© Siemens AG 2011. All Rights Reserved.


Page 10 May-11 Siemens PLM Software
TC XML based Data Transfer (2):

Data model equivalence between “similar but different” data model


constructs, using powerful mapping tool ( Teamcenter Mapping Designer
based on Altova Mapforce).

Used for Teamcenter<->Teamcenter or


Teamcenter<->TC Enterprise exchange of data

Object UIDs are preserved during exchange process (TC<->TC)


Also, Site ownership of objects is maintained

Only supports un-configured structures

© Siemens AG 2011. All Rights Reserved.


Page 11 May-11 Siemens PLM Software
TC XML is currently utilized in the following
Applications:

Global Multi-Site:
Multi-siting of data between sites in the Teamcenter federation (TCUA, TCE)
utilizing Global Services Framework

PDX integration:
Import/export is facilitated via XSLT translation between TC XML and PDX.
Used to facilitate communication with ERP systems

Briefcase:
Focus on packaging up all data (structured and bulk) required to work with
PDM data offline. Site check-out concept facilitates
update of offline transferred data

© Siemens AG 2011. All Rights Reserved.


Page 12 May-11 Siemens PLM Software
TC XML is currently utilized in the following
Applications: (2)

Interspec Integration:
GMS based integration between Interspec
(a SIEMENS Product Data Management application
focusing on recipe related BOMs)

Excel-BOM integration:
GMS based Import of excel spreadsheet data into Teamcenter

© Siemens AG 2011. All Rights Reserved.


Page 13 May-11 Siemens PLM Software
Architecture

© Siemens AG 2011. All Rights Reserved.


Page 14 May-11 Siemens PLM Software
Evolution and Teamcenter investment in GMS:
Siemens has invested several hundred Person Months of development in GMS

Several large OEMs (Automotive, Aerospace etc) are using GMS in production for their
Data Transfer/Coexistence/Data Migration needs w.r.t. TCEnterprise  TCUA

Tc8.3 saw substantial improvements in Performance, Scalability, parallel execution of


data transfer processes, “Flip-the Switch” feature (rapid ownership transfer) and
drpvoements ing of data between sites in the Teamcenter federation (TCUA, TCE)
utilizing Global Services Framework and 100% support of complete TCUA data model
in Tc8.3, including all COTS Templates (~3000 Classes)

TC XML (GMS) is the strategic go-forward, best-practice solution for Data Transfer,
Data Migration and Data Coexistence of TCEnt to TCUA data transfer within a
Teamcenter Federation

© Siemens AG 2011. All Rights Reserved.


Page 15 May-11 Siemens PLM Software
TC XML Briefcase:

Using TC XML for metadata transport, and compressed set of bulk files

Supports non-networked Teamcenter to Teamcenter data sharing


Supports variability of data models on both ends, meta-data, JT, and NX
Reference only transfer but site check-out allows data updates on import

Can co-exist with Classic Multi-site connectivity


Briefcase can operate inside and outside a Global Services Infrastructure

© Siemens AG 2011. All Rights Reserved.


Page 16 May-11 Siemens PLM Software
TC XML vs. PLM XML schema
TC XML: very close to Teamcenter data model, used for “federation-internal”
data transfer with or without data mapping, and briefcase / supplier integration

<Item item_id="NML00000026" last_mod_date="2008-05-08" object_name="test"


revision_list="#id8" revision_number="0" uom_tag="">
<GSIdentity elemId="id1" label="xXPhiwm1AAgcRD"/>
</Item>

PLM XML: object model independent, basis of rich interoperability pipeline connecting
SIEMENS Software products and 3rd party adopters

<ProductRevision id="id12" name="asm"accessRefs="#id5"masterRef="#id20"


revision="A">
<UserData id="id15">
<UserValue value="02-Dec-2003 12:37" title="last_mod_date"/>
</UserData>
</ProductRevision>

© Siemens AG 2011. All Rights Reserved.


Page 17 May-11 Siemens PLM Software
PLM XML and TC XML Solution Space
PLM XML:
Canonical Model,
used to solve “n squared”
integration problem

 Applies to Configured
Structure

Data Sharing with External


Applications in a object-
model neutral format

 TC XML:
Payload of choice for data
sharing within SIEMENS

Supported in briefcase

Schema is very close


To Teamcenter data model

Graphical Mapping possible

© Siemens AG 2011. All Rights Reserved.


Page 18 May-11 Siemens PLM Software
PLM XML and TC XML: at a glance

Requirement TC XML PLM XML(AI)


Require export of configured N/A yes
structure
Require replica concept Yes Replica import not supported

Unmanaged processing and More difficult, no SDK available, Easy due to existence of SDK
markup of XML GSIdentities difficult to generate

generate updates for re-import All Update Scenarios supported delta import, utilized by several
customers, however some
update Scenarios unsupported
Require simple/complex Easy to do with sophisticated Hard, must generate XSLTs
mapping of XML to destination Mapping tool, GSIdentity style sheets manually, must be
XML concept allows repeated data created as a ImanFile object.
sharing and coexistence

Co-existence and re-replication Design supports this use case Not possible, all objects are
of product data explicitly by use of GSIdentity, owned at their respective sites
site referential Integrity and
replica concepts

© Siemens AG 2011. All Rights Reserved.


Page 19 May-11 Siemens PLM Software
Related Sessions

Bulk Loader and Legacy Platform Migration Best Practices


 Wednesday 9:30

© Siemens AG 2011. All Rights Reserved.


Page 20 May-11 Siemens PLM Software
Related Material

 Best Practices Guides

 Contact for obtaining additional material


Reiner Kaiser, PhD – Architect, Teamcenter Distributed Services
[email protected]
Office – (714) 952-6604

© Siemens AG 2011. All Rights Reserved.


Page 21 May-11 Siemens PLM Software
Thank You!

Siemens PLM Connection 2011


Las Vegas, NV
May 2-5

http://plmworld.org/ 22

You might also like