Raising the Value of your

Product Data

MCAD & PLM Integrationand Legacy PDM Data Migration

May 18, 2009

Tom Makoski

VP PLM Integration Business

5303 DuPont Circle

Milford. Ohio 45150

513-576-3826

2009

- 2 -

Is’t ptrety esay fro a pseorn to gte hte yek piosnt of a lsopyp or grabeld ocmumniactino, but for enterprise

system integration or data migration the information must be clear and accurate.

2009

Outline

ITI TranscenData BackgroundUnderstanding MCAD & PLM Integration

Value PropositionKey TerminologyAbstract Data ModelLifecycle Process SynchronizationChallenges

Direct MCAD & PLM vs. PDM/MCAD & PLM IntegrationLegacy PDM/MCAD to PLM Data Migration

- 3 -

Presentation Objective•To provide a baseline understanding of the value proposition for MCAD & PLM integration, how a direct MCAD & PLM and a PDM/MCAD & PLM integration differ, and what represents the best in class PDM to PLM data migration technical solution and project approach. . .

2009

- 5 -

ITI TranscenData Business Focus

Engineering is hard . . .

Sharing your product data should be easy!

PLM Integration• MCAD & PLM Integration

• Legacy PDM to PLM Migration

• PLM & ERP Integration

C3 Interoperability• CAD Translation• CAD Model Quality & Validation• OEM & Supplier Exchange

2009

ITI PLM Integration> Vendor Partners & Integrations

Dassault Systemes / EnoviaDirect MCAD – ProENGINEER, UG NX & CATIA V4

MCAD/WIP DM – ProIntralink & Team Data Manager

ERP – Oracle Mfg., JD Edwards & QAD

Siemens PLMDirect MCAD – ProENGINEER & SolidWorks

ERP – Oracle Mfg.

- 6 -

2009

- 7 -

Understanding MCAD & PLM Integration> Value Proposition> Key Terminology> Abstract Data Model> Lifecycle Process Synchronization> Challenges

2009

Understanding MCAD & PLM Integration> Value Proposition

Access Control & SecurityMCAD file vaulting and team/role based data access control

Configuration Control & Change ManagementMCAD lifecycle design, review, and release process management

Version and revision management

As-stored, latest released, and latest WIP configuration management

Global Team Design CollaborationCheck-in / check-out / check for updates across the wide area network

Multi-site file replication

- 8 -

2009

Understanding MCAD & PLM Integration> Value Proposition (Cont’d)

Data Visibility, Sharing & Re-useCommon access/use to enterprise shared / library parts

Controlled enterprise visibility to MCAD attributes and viewables

ECR / ECO, Part & MCAD Lifecycle IntegrationECR / ECO driven workflow through to MCAD design

Customer & Supplier Data ExchangeAutomated derived output and/or data exchange file generation

Supply chain management data access and prep

- 9 -

2009

Understanding MCAD & PLM Integration> Key Terminology

MetadataItems

Part ItemMCAD ItemDocument ItemECR / ECOOther

RelationshipsE-BoMMCAD StructureSpecificationOther

Attributes

Files

Revisions

Versions

Lifecycle & States

Trigger

Derived OutputDrawings - .pdf, .tiff, etc.

Assembly/Part - .cgr, .jt, etc.

Exchange - .step, .iges, etc.

Store (Database)

Vault

Multi-site Replication

- 10 -

2009

Understanding MCAD & PLM Integration> Abstract Data Model

- 11 -

Part(Revision C)

ECR ECO

MCAD Part(Revision K)

Document(Revision T)

MCAD Drawing(Revision M)

MCAD Part(Version 1)

MCAD Part(Version 2)

MCAD Drawing(Version 1)

Document(Version 1)

Document(Version 2)

Derived FileCADModel

CADModel

CADModel

File

File

File

Affected Part(s)

Version of

Specification

File of

MCAD Data Mgt. Document Mgt.

EngineeringChange Mgt.

2009

Understanding MCAD & PLM Integration> Lifecycle Process Synchronization

- 12 -

Mechanical Design

Lifecycle

ECR/ECO Lifecycle

PartLifecycle

Assign MCAD Work

In Work Review Approval Released

Work

Collaborate

Early Visibility E-BoM Synch

Release to Enterprise

E-BoM Synch

Revise

PLM & MCAD Lifecycle Interface Points

In Work Review Approval Released

In Work Review Approval Released

WIP

Create New

Design

DemoteRevise

Release to enterprise entails the synchronization of either

CAD objects/models or derived MCAD objects/files

Create ECR

2009

Understanding MCAD & PLM Integration> Challenges

Transition from MCAD drawing centric data management to managing the review, release and revision of parts, assemblies and drawings Reconciliation and consolidation of division specific MCAD data management processes Bulk loading / migration of legacy MCAD data

Big bang or incremental migration by program/division

MCAD file check-in/out performance across the WAN vs. multi-site replicationEstablishing and managing a process of automated MCAD derivative file generationIntegration of ECR/ECO process with MCAD design processSupplier access/exchange for native MCAD data

- 13 -

2009

- 14 -

Direct MCAD & PLMvs.

PDM/MCAD & PLM Integration

2009

Direct MCAD & PLM Integration

- 15 -

LocalIn-workFile(s)

MCAD IntegrationExtension

MCADApplication

PLM SystemPLM

VaultedFile(s)

Server SideMCAD Integration

Client SideMCAD Integration

MCAD API

https & ftpCommunications

2009

Direct MCAD & PLM Integration> Key Factors

Application-based and application-driven integration.Client side integration is API-based

Operators are embedded/Immersed in the MCAD application

Invoked through menu overrides and extensions

MCAD files (WIP & released) are vaulted in the PLM system.

Interaction with PLM server is based on secure https & ftp communications.

PLM distributed infrastructure and multi-site replication model is leveraged to support MCAD design collaboration & management

MCAD lifecycle process can be independent or integrated with the ECR/ECO and Part lifecycles.

- 16 -

2009

PDM/MCAD & PLM Integration

- 17 -

In-work

File(s)

MCAD Integration

MCADApplication

PDM

Vault(Files)

WIP

DM

API

PLM System

Vault(Files)

PLM

API

PLMAdapter

PDMAdapter

PDM/MCAD & PLMIntegration

Web Services(XML Exchange)

2009

PDM/MCAD & PLM Integration> Key Factors

MCAD & PLM lifecycle-driven, process centric integration.MCAD items are locked/unlocked, based on a PLM release/revise.

MCAD files (WIP & released) are vaulted in the WIP DM system.MCAD items, attributes, and derived files are “published”, and stored in the PLM system.

MCAD files can be packaged & transferred to PLM for supplier exchange.Key process interface points are:

Part number fetch (for starting a design)Publish items & derivative files to PLMRevise from PLMPackage and export to PLMView metadata and MCAD files from PLM

- 18 -

2009

- 19 -

Legacy PDM/MCADto

PLM Data Migration

2009

Legacy PDM to PLM Migration

“Managed-Migration” PhilosophyMigration project is a joint customer/vendor project.

Division of responsibility and labor is key to success

Implementation, migration, and deployment plans need to be well aligned.Scope of migration should be carefully scrutinized.

Migrate what is *needed*, archive all the data for potential future reference

Architect migration solution with clear lines of delineation.Export, rationalization (transformations), and import

Architect migration solution to enable many (up to 100) test iterations.Don’t allow for the migration of “bad” data.

Detect problematic source dataProvide automated fixes where applicableProvide reports/diagnostics for problems that need manual fixing

Validate before you import to PLM

- 20 -

2009

Legacy PDM to PLM Migration (Cont’d)

- 21 -

“Managed-Migration” Project Approach

AssessEngineerMigrationSolution

Test ProductionMigration

ValidateViaPoC

Proof of concept is an optional phase, based on the overall migration project complexity

2009

Legacy PDM to PLM Migration (Cont’d)

- 22 -

“Managed-Migration” Project Executiono Consulting Services – Assessment, Engineer, Migration Test Support

o Software Use - SaaS Delivery Model

“Managed-Migration” Tool-set

ExporterLegacyPDM

Driver(Rationalization) Importer PLM

2009

- 23 -

Legacy PDM to PLM Migration> Export

Export FactorsoExport *all* metadata into the EFS – no physical file export.

The EFS is a simple, structured ASCII file – easy to transfer from customer to vendor, to support remote analysis, development, etc.

oAccess to the legacy PDM data is at the database level.o We do not rely on the application APIo The APIs are typically slow and not always sufficient

oExport has minimal data manipulation or validation.oExport has high performance – fast execution time.oExport is intended to be run against the production database.

Legacy PDM(Metadata)

Expo

rter

EFS

The EFS (Export File Set) is an ITI defined file format designed specifically to support PDM/PLM data migration.

2009

- 24 -

Legacy PDM to PLM Migration> Rationalization

Rationalization FactorsoThe data rationalization solution represents a set of discrete modules.oThe rationalization modules work with the migration data set in a memory-based, page to disk, working form architecture.oThe rationalization solution is extensible.oCurrent set of OOTB modules include:

Clean-up ReportsAutomated FixScope FilteringDependency ManagementMetadata MappingFile MigrationValidationArchive Export

Migration Driver(Customer Specific)

Rat

iona

lizat

ion

Mod

ule

Rat

iona

lizat

ion

Mod

ule

Rat

iona

lizat

ion

Mod

ule

Rat

iona

lizat

ion

Mod

ule

2009

- 25 -

Legacy PDM to PLM Migration> Import

Import FactorsoData creation (items and relationships) in the PLM system is at the database level.

We do not use rely on the application APIPrimarily due to performance reasons

oImport has minimal data manipulation or validation.oCopy the physical file once, from vault to vault.oImport is high performance – fast execution time.

Target PLM(Metadata)

Impo

rter

ImportFile

File

Mig

ratio

n

LegacyPDM Vault

PLMVault

2009

Legacy PDM to PLM Migration> Archive

- 26 -

Archive FactorsoWeb-browser based interface to the legacy PDM data.oSimple data storage approach with minimal system infrastructure requirements.oFunctional Scope:

SearchNavigation up or down within structuresQuery of item propertiesCopy-out of files

2009

- 27 -

Legacy PDM to PLM Migration> PLM Migration Center (PMC)

Legacy PDM(Metadata)

Expo

rter

EFSTarget PLM(Metadata)

Impo

rter

ImportFile

Migration Driver(Customer Specific)

PLM Migration Center

1. Customer executes the legacy PDM export, and submits the EFS to the PMC for processing.

2. Data summary and clean-up reports are sent back to the customer.

Reports

3. After the migration driver executes, the Import File is retrieved by the customer.

Customer

ITI

File

Mig

ratio

n

LegacyPDM Vault

PLMVault

Archive

2009