Fast Configured Structure Traversal

Siemens PLM Software

Siemens AG 2012. All Rights Reserved.

Fast Configured Structure Traversal

Reiner Kaiser, PhD Consultant

1 http://plmworld.org/ Siemens AG 2012. All Rights Reserved.



Page 2


Agenda

PLMXML based Traversal

TCXML based Traversal

Configured Traversal in TCXML

Performance Characteristics

Synchronization/Import logic

Solution Matrix

HD User Experience

Intelligently Integrated

Information

Future-proof Architecture



Page 3


PLMXML Based Traversal

Before Teamcenter 9.0, XML based

Configured Structure Traversal was

exclusively PLMXML :

Traversal logic derived from BOM traversal and codeful

interpretation of closure rules

Best case performance based on closure rules / property sets:

~ 700,000/hour



Page 4

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



Page 5

More Aspects 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 PLMXML between two sites connected by Multi-Site, if the same objects are to be replicated later via CMS or GMS

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 often used to identify all Configured ItemRevs in a BOM



Page 6

TCXML Based Data Transfer

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

TCXML 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 TCXML with high level of data model coverage (close to 100% of Teamcenter data model

in the Teamcenter 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)



Page 7

TCXML Based Data Transfer

Data model equivalence between similar but different data model constructs, using powerful mapping tool ( Teamcenter Mapping

Designer based on Altova Mapforce)

Used for TeamcenterTeamcenter or TeamcenterTeamcenter Enterprise exchange of data

Object UIDs are preserved during exchange process (Teamcenter Teamcenter)

Also, Site ownership of objects is maintained



Page 8

TCXML: very close to Teamcenter data model, used for federation-internal data transfer with or without data mapping, and briefcase / supplier integration

PLMXML: object model independent, basis of rich interoperability pipeline connecting

SIEMENS Software products and 3rd party adopters

TCXML vs. PLMXML Schema



Page 9

New in Teamcenter 9.x

Configured TCXML Based Traversal

Runtime objects are represented in the TCXML (example: BOMLines)

~Order of Magnitude performance gain compared to PLMXML

Full expand of BOMWindow not necessary

XML contains all persisted objects required to re-generate configured structure

Scalable and Parallelizable Import: Many processes can run in parallel Well-defined rollback for given island of data Import performance same as bulk loader (up to 500,000 objs/hour)



Page 10

Performance Numbers (export)

Sample Structure on 6GB Machine

BOM

size

(x1k)

TCXML

Export (s) PLMXML

Export (s)

TCXML

thru-put

(obj/h)

PLMXML thru-

put (obj/h)

10 96.2 426.353 3101613 699831

20 197.42 772.693 3033303 774997

50 650.293 3110.805 2298450 480475

100 1206.559 9605.283 2476792 311120

200 2524.877 2367178

300 5692.18 1575008

TCXML based configured export can handle much larger structures (PLMXML running out of memory sooner..)

export throughput is up to 8 times faster than equivalent PLMXML throughput

Mild nonlinearity for larger structures due to scalable architecture and set based logic

0

500000

1000000

1500000

2000000

2500000

3000000

3500000

0 50 100 150 200 250 300 350

TC XML Exportthru-put (obj/h)

PLMXML thru-put (obj/h)



Page 11

Fast Configured Synchronization

Traversal-free Identification of Structure Updates

Synchronization performance is proportional to number of changes, not overall size of the structure

Approach works best for small number of changes, i.e. Synchronization performed in regular intervals (hourly/daily)

Typical performance for several hundred changed lines is within the order of a few minutes for any size BOM

Configuration parameters (Revision rule, Variant rule) are assumed stable

New patented

technology!



Page 12

New Configured Structure Import Approach

Configured TCXML also contains persisted objects needed to re-generate the configured structure at the importing site

No BOMWindow is needed to perform these imports, performance is equivalent to TCXML bulk loader performance (~500k/hour)

Import processes are scalable and parallelizable, with minimum memory overhead required

Partial rollback supported



Page 13

PLMXML and TCXML at a Glance

Requirement TCXML PLMXML(AI)

Require export of configured

structure yes yes

Require replica concept

Yes Replica import not supported

Unmanaged processing and

markup of XML

More difficult, no SDK available,

GSIdentities difficult to generate

Easy due to existence of SDK

generate updates for re-import All Update Scenarios supported delta import, utilized by several

customers, however some

update Scenarios unsupported

Require simple/complex

mapping of XML to destination

XML

Easy to do with sophisticated

Mapping tool, GSIdentity

concept allows repeated data

sharing and coexistence

Hard, must generate XSLTs

style sheets manually, must be

created as a ImanFile object.

Co-existence and re-replication

of product data

Design supports this use case

explicitly by use of GSIdentity,

site referential Integrity and

replica concepts

Not possible, all objects are

owned at their respective sites



Page 14

New Configured Structure Traversal Approach

TCXML based Traversal is faster and more scalable

Traversal Free Updates, Highly scalable imports

Performs substantially faster and can handle much

bigger Structures

Teamcenter 9.x Fast Configured Traversal Summary



Page 15

Patents Pending

SIEMENS has Two Patents Pending as result of R&D for this

Project:

DOCKET NO. : 2012P03414 UGSC01-05212

(Traversal Free Updates in large data Structures)

DOCKET NO. 2012P03416 UGSC01-05213

(Bulk Traversal of Large Data Structures)



Page 16

Related Sessions

494 Bulk Loader Success Stories

Thursday / 8:45AM



Page 17

Related Materials

Products & Solutions overview

http://www.plm.automation.siemens.com/en_us/products/teamcenter/index.shtml

http://www.plm.automation.siemens.com/en_us/industries/index.shtml

Collateral Library

http://www.plm.automation.siemens.com/en_us/products/teamcenter/library.shtml

Customer Success Videos

http://www.plm.automation.siemens.com/en_us/products/teamcenter/video/feature_video.shtml

Contact for obtaining additional materials

Reiner Kaiser, PhD Consultant, Siemens PLM

[email protected]

Documents

Fast Configured Structure Traversal