Vendor to Vendor Migrations - PROSTEP INC.webinarsbyprostep.com/.../07/Vendor-to-Vendor-Migrations.pdf · - The importance of using neutral software in vendor to vendor migrations
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
PROSTEP Inc • 300 Park st. • Birmingham MI 48009 • www.prostep.com
Webinar
February 25 th 2016No part of this presentation may be reproduced or transmitted in any form for any purpose without the express written permission of PROSTEP, Inc. The information contained in this presentation may be subject to change without prior notice. The statements made in this presentation do not represent any kind of offer or warranty. Portions of this presentation are pre-recorded.
PROSTEP, Inc. 300 Park Street Suite 410, Birmingham, MI 48009US Toll Free : 8-PROSTEP-01 Direct: +1-248-247-1007 [email protected] / www.prostep.com
Is the PLM Grass Greener with a New System?- The importance of using neutral software in vendor to vendor migrations -
Page 2
Practice Question
Welcome
Brian SchoutenSales Executive – PROSTEP, [email protected]+1-248-247-1007
Since its foundation in 1993, PROSTEP has become a leading provider of turn-key solutions for engineering processes in the areas of product data integration, data migration and supply chain communication for manufacturers and suppliers.
We provide leading manufacturing companies worldwide with the support they require for designing, implementing and optimizing their internal and cross-enterprise development processes.
�This Webinar Will Cover the Following Topics:� Different strategies for handling PLM migrations � The risks and challenges in migrating vendor to vendor
PLM or CAD data� The best ways to align your strategy and goals to
assure project completion
�This Webinar also Includes:� PROSTEP Integration products� Insights to integration architecture� Integration best practices� Question & Answer� Audience surveys
> Over 22 years of Experience> 250 PLM Experts> 500 Customers
11 Locations
� Since its foundation in 1993, PROSTEP has become a leading
provider of turn-key solutions for engineering processes in the areas of product data integration, data migration and supply
chain communication for manufacturers and suppliers.
� We provide leading manufacturing companies worldwide with the support they require for designing, implementing and
optimizing their internal and cross-enterprise development processes.
Page 6
PROSTEP Alliances and Partnerships
PROSTEP technology partnersSynergies bundle knowledge. And Knowledge provides solutions. In order to
provide our customers with the best possible solutions, we have long maintained open and productive relationships with all leading IT system
vendors.
Strategic partnersOur strategic partners include leading PLM providers.
These are in details
Technology Partnerships
Name of Company Partner Status Since Focus of Partners hip
Siemens PLM Software & Technology Partner Since 2003 Teamcenter Data Exchange Solutions
SAP Software Partner Since 2002 SAP PLM Data Exchange Solutions
Dassault Systèmes
Software Partner Since 2002 ENOVIA and CATIA Data Exchange Solutions
Oracle Solution Partner Since 1996 Data Management SystemsAdobe Silver Solution Partner Since 2005 3D-PDF SolutionsIBM Business Partner Since 2006 PDM Migration Projects
MSC Software Partner Since 2007 Integration of Simulation Data Management
PTC Silver Partner Since 2000 Windchill Data Exchange Solutions
Ansys Software Partner Since 2009 Integration of Simulation Data Management
Some Strategic Requirements to assist in Vendor to Vendor Migration
� Differentiate the requirements for decommissioning your legacy PLM from the requirements for introducing the new PLM
� For Legacy PLM� What is the required data that needs to be extracted?� What version / iteration requirements? All history? Just released?� How to handle “other” system data like tasks, workflow history, etc.
that may not map to new PLM?
� For New PLM� Define what is needed to be operational in your new PLM system?� Is all the CAD history required or maybe just the top 20 programs
CAD data?� Do you have an alternative archiving strategy for unused legacy
� Migration Timing� Calculate expected downtime vs. migration performance� Weekends? Merry Christmas here’s the new PLM?� Incremental migrations can take too long and enable bad behavior
in the transition
� Data Disaster Risks� First migration to empty system shouldn’t ever corrupt production
data with proper testing� Adding a large volume of data to existing production PLM requires
practiced disaster recovery plan.
� Vendor to Vendor migration without planning tend to “de-scope” data to better fit the new data model� Know at your strategy phase what is able and realistic to be moved
� ETL (Extract, Transform, Load)� Extract: Export the data from the source system to a staging
database� Transform: Map data to the target system format & fix data issues� Load: Import complete staging database to the production system� Define initial load and delta update for extraction to staging
database� Define initial load and delta update for import to new PLM
� Transactional� Define packages from dependencies to migrate� Export, map and import a small data package within a transaction� Define insert / update import strategy for new PLM
� The Benefits� Ability to modify data and correct issues in the staging database� Good performance for large volume of data� Lends itself to good repeatable testing scenarios� High quality results for a one-time first go-live of new PLM
� The Risks� Staging database gets out of sync quickly� Intermediate database means export / import is done twice� Modification of data does not always sync up to legacy PLM or 3rd
� The Benefits� Enables staged migration of data� Staged migration allows for easier PLM adoption strategies� Errors are more easily controlled and corrected� Enables migration to move at the pace of business
� The Risks� Garbage in, Garbage out� Order of import operations is not always transparent� Performance is not as good� Testing can be cumbersome
� Bulk “Big Bang” Migration carries large risks such as:� Disaster & corruption of production data� Business training and acceptance of the new system� Issues with the new system are not addressed over time with small
volume of users
� Co-existence integration approach mitigates risks:� Data can be synchronized an migrated over time� Program by program or functional role can be adopted from source
to target system� Training, system acceptance and critical fixes can be established
over a reasonable time-frame� 3rd party integrations have time to be established in the new
system and not immediately required to be functional
� Connectivity to Engineering systems, including software solutions for the hard-to-implement features without shortcuts
� Mapping functionality, best by adding visual functionalities� Workflow support, for complex business requirements� Ability to be deployed in a clustered environment� Sophisticated approaches to parse and export complex product
structures (top-down, bottom-up) to meet different customer requirements
� Filter and Split mechanisms (vertical or horizontal), to reduce the data volume to the really required information
� Packaging mechanisms that are able to transfer only subsets of data, but still keeping all relevant relationships
� Import conflict management to enable conistent import processes to databases that already contain information
Requirements for Vendor to Vendor Migration Software
Page 32
Vendor Technical Considerations- For Teamcenter
� Tools for interfacing with Teamcenter:�Teamcenter Portal Client API (Legacy ITK)�Teamcenter SOA API� IPS CSV loading tool for metadata�PLM XML for metadata and document export /
import� CAD Import For Teamcenter
�UGClone for NX data export / import�TCIC bulk spreadsheet for export / import for
CATIA�Creo IPEM Command line for export / import
� PROSTEP has comprehensive Metadata and CAD import tools that include all this technology
� Data creation performance in Teamcenter may require alternative methods for loading
� CAD and Parts are historically built on the same BOM in Teamcenter meaning that your CAD must align to the EBOM!
Page 33
Vendor Technical Considerations- For Windchill
� Tools for interfacing with Windchill � RMI API for integration export /
import� Windchill Bulk Migrator for Creo,
Metadata & Document� Work Group Manager Batch Import
for other CAD� Pro/Toolkit + JLink
� PROSTEP has comprehensive connectors for interfacing with Windchill API’s and tools
Page 34
Vendor Technical Considerations- For Enovia V6
� RMI API for V6 and CATIA (V5) API for export / import to Enovia provides sufficient functionality for many tasks
� PROSTEP has an XPDM adapter is needed for VPM Central CATIA V6 data
� Modern V6 has a lot of object model dependencies! Test your UI for everything!
� Understand the object models in the database
� Can support relatively fast export / import
Page 35
Vendor Technical Considerations- For Enovia V4 VPM
� For Parts, BOM & Documents you could go to the database to get the information, but not all of it is readily available
� Need Dictionaries, Effectivities & Configurations and some other more complicated data? Be prepared to use the VPM API on AIX
� CATIA is exploded in the VPM database so no direct export -� Leverage CAA process for generating CATProducts and healthy
dependency relationships on export (load in CATIA and Save As)
� Want original CATIA release levels and environments? Be prepared to load data in that CATIA in that release level and environment to save out. (This normally is multiple release levels per assembly)
� CATIA Reconciliation or CAA process for import� SetPDMProperties API to replicate the 3DCOM save process� PROSTEP has great solutions for this!
Page 36
Technical Considerations- For File Based CAD Import
� CAD Data does not have enough information to import on it’s own. PLM data should be added to the process
� Unmanaged data is generally “dirtier” with considerably more issues than PLM managed data
� Recommended Process Steps –� Scan directories with CAD interrogation tool (CAA, etc) and get
all data attributes and dependencies� Move all data to staging database or Excel file(s) with attributes
and:� Determine which file is the master between multiple instances
� Transform metadata into import packages� Execute bulk import with appropriate PLM interface tool
Page 37
A Note On The Use of Neutral Formats
� PROSTEP iViP leads the definition of many engineering neutral formats and processes� ISO STEP 10303 AP 214, 239, 242� PLM Services� Open JT, LOTAR, other working groups
� Neutral Formats are beneficial for more than one party that agree on the standard (for partner collaboration)� Exchanging standards based data give good definition to all
parties
� Neutral formats may complicate migrations where a strong independent semantic definition is not needed� Point to point solutions generally do not require neutral formats� Neutral formats add a layer of transformation� Maybe useful for more than two interfaced systems
OpenPDM – The PLM Integration PlatformOne Solution for all Integration Tasks
Dat
a fo
rmat
sIn
terf
aces
CAx
TDM, PDM, PLM, …
SD
M
Others…
MSC
SIMMANAGER
ANSYS
EKM
DASSAULT
ENOVIA V6
DASSAULT
VPM V4
PTC
WINDCHILL
DASSAULT
SMARTEAM
SIEMENS
TEAMCENTER
SIEMENS
TEAMCENTERENTERPRISE
SAP
SAP PLM
ORACLE
AGILEePLM
STEP
XML
ASCII
WEBSERVICES
DATABASES
DASSAULT
CATIA V6(XPDM)
YOUR
LEGACY SYSTEM…
DASSAULT
CATIA V5
SIEMENS
NX
PTC
PRO/ECREO
…
…
…
…
ER
P
Page 43
Standard Functionality of OpenPDM Connectors
� Import/Export of PDM Meta Data� Parts, Part Versions (incl. attributes)� Documents (incl. physical files and attributes)� Assembly Structures / BOMs� Configuration data (150%BOMs incl. configuration options, effectivities, …)� Change data� Roles & Rights management
� Import prognosis / dry run� Calculate import result before starting a real import
� Calculate differences between import data and actual data base content
� PDM-system import logic is in place� Check for missing mandatory attributes
� Check for write access to all touched PDM objects
� Highly configurable import logic� Control “Insert/Update“ on each object depending on use case� Control ID generation � Control handling of structure updates (managing relationship updates)
PROSTEP Inc • 300 Park st. • Birmingham MI 48009 • www.prostep.com
No part of this presentation may be reproduced or transmitted in any form for any purpose without the express written permission of PROSTEP, Inc. The information contained in this presentation may be subject to change without prior notice. The statements made in this presentation do not represent any kind of offer or warranty. Portions of this presentation are pre-recorded.