Raising the Value of your Product Data MCAD & PLM Integration and Legacy PDM Data Migration May 18, Tom Makoski VP PLM Integration Business 5303 DuPont Circle Milford. Ohio 45150 513-576-3826
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. -2 -
Outline ITI TranscenData Background Understanding MCAD & PLM Integration Value Proposition Key Terminology Abstract Data Model Lifecycle Process Synchronization Challenges Direct MCAD & PLM vs. PDM/MCAD & PLM Integration Legacy PDM/MCAD to PLM Data Migration 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... -3 -
ITI TranscenData Business Focus Engineering is hard... PLM Integration MCAD & PLM Integration Legacy PDM to PLM Migration PLM & ERP Integration C3 Interoperability CAD Translation CAD Model Quality & Validation OEM & Supplier Exchange Sharing your product data should be easy! -5 -
ITI PLM Integration > Vendor Partners & Integrations Dassault Systemes / Enovia Direct MCAD ProENGINEER, UG NX & CATIA V4 MCAD/WIP DM ProIntralink & Team Data Manager ERP Oracle Mfg., JD Edwards & QAD Siemens PLM Direct MCAD ProENGINEER & SolidWorks ERP Oracle Mfg. -6 -
Understanding MCAD & PLM Integration > Value Proposition > Key Terminology > Abstract Data Model > Lifecycle Process Synchronization > Challenges -7 -
Understanding MCAD & PLM Integration > Value Proposition Access Control & Security MCAD file vaulting and team/role based data access control Configuration Control & Change Management MCAD lifecycle design, review, and release process management Version and revision management As-stored, latest released, and latest WIP configuration management Global Team Design Collaboration Check-in / check-out / check for updates across the wide area network Multi-site file replication -8 -
Understanding MCAD & PLM Integration > Value Proposition (Cont d) Data Visibility, Sharing & Re-use Common access/use to enterprise shared / library parts Controlled enterprise visibility to MCAD attributes and viewables ECR / ECO, Part & MCAD Lifecycle Integration ECR / ECO driven workflow through to MCAD design Customer & Supplier Data Exchange Automated derived output and/or data exchange file generation Supply chain management data access and prep -9 -
Understanding MCAD & PLM Integration > Key Terminology Metadata Files Items Part Item MCAD Item Document Item ECR / ECO Other Relationships E-BoM MCAD Structure Specification Other Attributes Revisions Versions Lifecycle & States Trigger Derived Output Drawings -.pdf,.tiff, etc. Assembly/Part -.cgr,.jt, etc. Exchange -.step,.iges, etc. Store (Database) Vault Multi-site Replication - 10 -
Understanding MCAD & PLM Integration > Abstract Data Model Engineering Change Mgt. ECR ECO Affected Part(s) Part (Revision C) MCAD Data Mgt. Specification Document Mgt. MCAD Part (Revision K) MCAD Drawing (Revision M) Document (Revision T) Version of MCAD Part (Version 1) MCAD Drawing (Version 1) Document (Version 1) CAD Model MCAD Part (Version 2) File of CAD Model Derived File File Document (Version 2) CAD Model File File - 11 -
Understanding MCAD & PLM Integration > Lifecycle Process Synchronization Create ECR In Work Review Approval Released ECR/ECO Lifecycle In Work Review Approval Released Part Lifecycle Revise Create New Design Assign MCAD Work Early Visibility E-BoM Synch Release to enterprise entails the synchronization of either CAD objects/models or derived MCAD objects/files Release to Enterprise E-BoM Synch PLM & MCAD Lifecycle Interface Points Collaborate Work WIP In Work Review Approval Released Demote Revise Mechanical Design Lifecycle - 12 -
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 replication Establishing and managing a process of automated MCAD derivative file generation Integration of ECR/ECO process with MCAD design process Supplier access/exchange for native MCAD data - 13 -
Direct MCAD & PLM vs. PDM/MCAD & PLM Integration - 14 -
Direct MCAD & PLM Integration PLM System PLM Vaulted File(s) https & ftp Communications Server Side MCAD Integration Client Side MCAD Integration MCAD Integration Extension MCAD API Local In-work File(s) MCAD Application - 15 -
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 -
PDM/MCAD & PLM Integration Vault (Files) PLM Adapter PLM API PLM System Vault (Files) Web Services (XML Exchange) PDM WIP DM API PDM Adapter Inwork File(s) MCAD Integration MCAD Application PDM/MCAD & PLM Integration - 17 -
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 PLM Revise from PLM Package and export to PLM View metadata and MCAD files from PLM - 18 -
Legacy PDM/MCAD to PLM Data Migration - 19 -
Legacy PDM to PLM Migration Managed-Migration Philosophy Migration 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 data Provide automated fixes where applicable Provide reports/diagnostics for problems that need manual fixing Validate before you import to PLM - 20 -
Legacy PDM to PLM Migration (Cont d) Managed-Migration Project Approach Assess Validate Via PoC Engineer Migration Solution Test Production Migration Proof of concept is an optional phase, based on the overall migration project complexity - 21 -
Legacy PDM to PLM Migration (Cont d) Managed-Migration Tool-set Legacy PDM Exporter Driver (Rationalization) Importer PLM Managed-Migration Project Execution o Consulting Services Assessment, Engineer, Migration Test Support o Software Use - SaaS Delivery Model - 22 -
Legacy PDM to PLM Migration > Export Export Factors oexport *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 API o 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) Exporter EFS The EFS (Export File Set) is an ITI defined file format designed specifically to support PDM/PLM data migration. - 23 -
Legacy PDM to PLM Migration > Rationalization Rationalization Factors othe 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 Reports Automated Fix Scope Filtering Dependency Management Metadata Mapping File Migration Validation Archive Export Rationalization Module Rationalization Module Rationalization Module Migration Driver (Customer Specific) Rationalization Module - 24 -
Legacy PDM to PLM Migration > Import Import Factors odata creation (items and relationships) in the PLM system is at the database level. We do not use rely on the application API Primarily 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. Import File Importer Target PLM (Metadata) Legacy PDM Vault File Migration PLM Vault - 25 -
Legacy PDM to PLM Migration > Archive Archive Factors oweb-browser based interface to the legacy PDM data. osimple data storage approach with minimal system infrastructure requirements. ofunctional Scope: Search Navigation up or down within structures Query of item properties Copy-out of files - 26 -
Legacy PDM to PLM Migration > PLM Migration Center (PMC) Legacy PDM Vault File Migration PLM Vault Legacy PDM (Metadata) Exporter EFS Import File Importer Target PLM (Metadata) 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. Customer ITI 3. After the migration driver executes, the Import File is retrieved by the customer. Reports Migration Driver (Customer Specific) PLM Migration Center Archive - 27 -