best practices in engineering...

© PROSTEP AG 2016 | Alle Rechte vorbehalten / All Rights reserved

BEST PRACTICES IN ENGINEERING MIGRATIONS Online Workshop Schouten – 1/26/2017

1.26.2017, Schouten


Workshop Overview

Best Practices for handling even the most complex PLM Migrations

The most common risks and challenges you'll face in migrating from vendor to vendor PLM or CAD data

The proven ways to strategically align your goals to assure project success

PROSTEP tools and customer experiences with Engineering Migrations

Best Practices in Engineering Migrations to Start the New Year. This workshop will cover the following topics:

2 1.26.2017, Schouten


Company Overview

Shareholders

Over 22 years experience

with engineering interoperability, migration, intelligent documents, benchmarking, more

Approximately 250 employees and consultants

based from international locations throughout Europe and in North America

More than 500 Customers

that are leading companies across most industries

A vendor neutral / independent engineering services and software company since 1993

[email protected] / 8-PROSTEP01


PROSTEP Technology Partners

4 1.26.2017, Schouten


Agenda Overview

5 1.26.2017, Schouten

Challenges in PLM Migration

Finding the Optimal Migration Strategy

Advice on PLM Migration Planning

PROSTEP Migration Tools and Customer Experiences


PLM System Migration 10,000 Foot View Questions

ARCHITECTURE VIEW

Replace or realign current PLM system?

Setup a brand new target system or migrate into an existing one?

Which interfaces to other systems?

ORGANIZATION VIEW

Time frame / Deadline?

Internal and external resources / budget?

Switch over at once or per project / per business unit?

Where to continue ongoing projects?

PROCESS VIEW

Which processes to be implemented?

Which cross-system processes to be implemented?

Which data is shared between old and new system?

DATA VIEW

Which data to be provided, and how much?

Quality of meta data and CAD data?

Migrate whole history? Quality of historical data?

How to transform old data to fit to new processes?

1.26.2017, Schouten


Migration Requirements

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 data?

7 1.26.2017, Schouten


Migration Planning

If migration is to a newly introduced PLM be prepared for Parallel development

− Remember that there is a strong dependency on the PLM introduction

− Sometime this is a moving target during the development affecting data conditions, mapping and process

− Bugs in the system result in bugs in the migration

− Migration is incredibly performance intensive and new systems do not always perform well

− Release schedules are inter-twined

− New vendor systems are not always well understood by customers, they need to learn how to use it!

− Any business case ROI from migration is in the new system

8 1.26.2017, Schouten


Migration Risks

Migration Timing

− Calculate expected downtime vs. migration performance

− Weekends? Merry Christmas here’s the new PLM?

− Coexistence 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.

PLM 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

9 1.26.2017, Schouten


Migration Acceptance

Migration Planning

− How long does it take to steer the enterprise to the new PLM?

− Is your business capable of handling a one time event to switch to a new PLM?

− Is your ERP / MRP / 3rd party integration capable of a cut over?

− Is the training and support for the new PLM in place and comprehensive?

− Will the solution be comprehensive and bug free day one?

− Have you done a good job with public relations and PLM change acceptance?

− New system acceptance is critical to any migration project!

10 1.26.2017, Schouten


Survey #1 What PLM system are you migrating TO?

11 1.26.2017, Schouten

Siemens (Teamcenter etc)

Dassault (VPM / LCA / Matrix / Enovia / SmarTeam)

PTC (Windchill / Pro Intralink)

ARAS

Other / Unknown


Survey #2 What PLM system are you migrating FROM?

12 1.26.2017, Schouten

Siemens (Teamcenter etc)

Dassault (VPM / LCA / Matrix / Enovia / SmarTeam)

PTC (Windchill / Pro Intralink)

ARAS

Other / Flat Files / Spreadsheets / Etc


Survey #3 Why are you migrating to a new PLM system?

13 1.26.2017, Schouten

Old system / Out of maintenance

Merger / Acquisition / Divestiture

System Stability / Performance / Issues

Operating / License Cost

Vendor or Service Provider Issues


Workshop Discussion: What leads to a successful migration project?

14 1.26.2017, Schouten

Requirements

Planning

Risks

Acceptance


Agenda Overview

15 1.26.2017, Schouten






Migration to PLM Roadmap From As-Is Analysis To System Go-Live

PLM Architecture PLM Information Flow and Capabilities Challenges and Discontinuities Compare to Market Statistics (Data, Performance, Usage)

Pilot / Proof of Concept RFP Assessment Contracting HW/SW Procurement Solution Partner Selection Migration Project Planning

UAT End User Training Admin Training Migration Dry-runs Rollout Scheduling

Business Strategy Definition / Future Topics Major PLM Concepts Business Processes Realignment Reference Customers and Best Practices Vendor Presentations Business & IT Requirements Spec Migration Strategy Selection

IT Project Management Detailed Specification System Configuration and Customization Data Conversion and Migration Business Processes Implementation System Interfaces Implementation Validation & Verification

Rollout Delta Migration IT Support On-site End User Support

AS-IS ANALYSIS GO-LIVE TO-BE

DEFINITION SYSTEM

DEFINITION IMPLEMENTATION GO-LIVE PREPARATION

1.26.2017, Schouten


Migration Methods

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

17 1.26.2017, Schouten

Source PDM System

Target PDM System

User and Data

Migration User and Data

Migration User and

Data Migration

25% User Base

50% User Base

75% User Base

Complete User Base

Complete User Base


Migration Methods One Time vs Coexistence Migration

1.26.2017, Schouten

Longer period of coexistence Legacy system productive

Legacy system productive

Migrate data and users in one step

Migrate data and users: Project by project per application … as your needs dictate

New system productive

“Big

Ban

g”

mig

ratio

n

Fixed period of time

Weekend Week

Years Months


Incr

emen

tal

mig

ratio

n


Comparing ETL and Transactional Migrations

ETL Benefits and Risks

− 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 party integrations

Coexistence Benefits and Risks

− 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

19 1.26.2017, Schouten


Migration Strategy Options

One Time Migration

− Export and Import over a weekend

− ETL or Transactional

Update until Go-Live One Time Migration

− One time, test & delta update production until go-live

− ETL or Transactional

Staged Migration

− Move in Program by Program

− Transactional

Co-existence

− Flexible to move in data over time

− Flexible to give time to develop Old PLM functionality like ERP integrations in the new PLM

− Transactional

20 1.26.2017, Schouten


Survey #4 What phase are you in your PLM migration project?

21 1.26.2017, Schouten

Planning / Strategy / Research

Just Started / Early Phases

In Progress / Some Issues

In Progress / No Issues

In Progress / Major Issues (now or foreseen)


Survey #5 What methods and strategy are you using or considering in your migration?

22 1.26.2017, Schouten

ETL / One Time Migration (Bulk Load)

ETL / Coexistence Migration (Mini Bulk Load)

Transactional / One Time Migration (Trans Bulk)

Transactional / Coexistence Migration (Program)

Unknown / Not Decided


Survey #6 What do you see as the largest business risks for your migration?

23 1.26.2017, Schouten

Timing to complete (not enough time)

Reconciling system differences (conflict management)

Large user community (training, acceptance)

In House Technical Skills or Resources

Budget Constraints


Workshop Discussion: When is it appropriate to use an ETL migration? When would it be appropriate to use a incremental migration?

24 1.26.2017, Schouten

Migration Methods: − ETL

− Transactional

Migration Strategy − One Time

− Coexistence


Agenda Overview

25 1.26.2017, Schouten






Migration Strategy Recommendations

One Time Migration

− Exact preparation

− Long test phase

− Emergency plan to go back

− Unidirectional

Staged Migration

− Process oriented

− Focus on semantic group of data

− Controlled Replication

Coexistence Migration

− Transfer of small data packages

− Controllable in going step by step

− Bidirectional

26 Datum, Autor

Migration KPIs:

Risk Acceptance Success-Rate

Cost Time Data Master

Smaller PLM

Projects

Larger PLM

Projects


One Time Migration Risks

Short Execution Timeframe

− Be prepared for disaster recovery

− Backup system & execute migration

The new system must support the complete functionality from the start

− All users and processes

− User acceptance is critical

− All technical interfaces

− Complex technical dependencies can make the project fail

Continuity of resources is important

− Migration developers should be testing and executing the production migration if possible

27 1.26.2017, Schouten

Target System

User

Files

Meta Data

Source system in productive use

Target system in productive use Migrate


Coexistence Migration Risks

Long Execution Timeframe

− Hold to the plan timeline, execute in under a year

− Delay means more updates & maintenance with new system

Transactional Data Risks

− Not all data is tested like in a migration rehearsal

− Run the data twice –

− Perform transactions with the same data in the test environment before production until comfortable with the solution performance

28 1.26.2017, Schouten

Target System

User

Files

Meta Data

Source system in productive use

Target system in productive use


Advice on Project Planning

For One Time Migrations - Target complete migration development, testing and execution

− Strategy and Requirements workshop resulting requirements and implementation plan

− Implementation of migration use cases with basic system testing

− Execute “Migration Rehearsals” that include: − Limited data (10%) to test requirements

− Full data (100%) to test migration data success and performance

− Production Migration

For Coexistence Migrations - Target 3-5 migration use cases per development period and iterate in a standard software development pattern. Sprints should be between 2 to 4 weeks.

− Strategy and Requirements Workshop for each sprint

− Implementation of migration use cases with unit tests and system integration tests

− Execute user acceptance for incremental functionality

− Migration execution utilizing group that includes migration tool developers

Utilize the same development and business team to build understanding and core competence.

29 1.26.2017, Schouten


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 might need to align to the EBOM

30 1.26.2017, Schouten


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

31 1.26.2017, Schouten


Technical Considerations for 3D Experience Enovia

RMI API for V6 and CATIA (V5) API for export / import to Enovia provides sufficient functionality for many tasks

MQL scripting performs well for metadata (over RMI)

Newer CAD integrations have new API’s not covered in MQL

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

32 1.26.2017, Schouten


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

− Add PLM metadata (owner, group, projects, status, etc)

− Transform metadata into import packages

− Execute bulk import with appropriate PLM interface tool

33 1.26.2017, Schouten


Using 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

Lightweight Formats can assist in short term co-existence as they are easier to integrate

Neutral formats for non-CAD data 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 34 1.26.2017, Schouten


Archiving Strategy Not all your old data will be used in your new system

LOTAR – (LO)ng (T)erm (A)rchiving and (R)etrieval

− Many industries require CAD data for 50+ years (think Boeing 747). This is growing.

− CAD and PDM formats and versions cannot be supported indefinitely.

− Your data in those formats needs to be accessible forever

− Using standards-based CAD Formats (3DPDF / STEP 242) and repository you can archive this data

− This partitioning of old data and archiving is natural at migration when you may not want to carry over all data

− Aerospace and Automotive have standard practices for archiving widely used

− Manage your data so that you don’t need to keep every all versions of CAD that you have used (ever) with unsupported software and hardware!

35 1.26.2017, Schouten


Survey #7 What do you see as your largest technical challenges for your migration?

36 1.26.2017, Schouten

Many sources of data

Handling dirty or not well managed data

System complexity / vendor schemas

Large Volume of Data

Handling CAD (Native or Translated)


Survey #8 What is you plan for dealing with legacy data

37 1.26.2017, Schouten

Migrate all versions and all history (native format)

Migrate all released data without history

Migrate just some of the data as needed

Archive legacy data and migrate current programs

Undecided


Survey #9 What archiving or neutral formats are you utilizing in PLM and migration?

38 1.26.2017, Schouten

3DPDF

STEP (any format)

JT

3DXML

Other


Survey #10 How are you handling CAD Translation Needs

39 1.26.2017, Schouten

Manage “Foreign” Native CAD in new system (eg CATIA in Teamcenter)

Convert all Legacy CAD to a Neutral Format such as STEP

Convert all Legacy CAD to new Native Format (eg Creo to NX)

Only Convert Current Programs to Native CAD, and translate the rest as needed.

Remaster or Convert upon request


Workshop Discussion: What are large technical challenges that should be planned for?

40 1.26.2017, Schouten

PLM Data

CAD Transfer

CAD Conversion

PLM Schema Differences


Agenda Overview

41 1.26.2017, Schouten






DIY Benefits

Just like a home improvement project you may be able to save time and money doing much of the migration on your own. Some elements for success might include the following;

NON Technical (Engineering)

− Clean / Heal your legacy Data before the Migration

− Document existing customizations in Legacy Environment

− Map Legacy Properties to Future Properties

− Archive as much as you can ahead of time

Technical (IT Related)

− Optimize Technical environment for test labs, snap shot backups, quick restoration of test systems

− Programming Scripts and data mapping

− Project Management

42 1.26.2017, Schouten


DIY Risks

Just because you think you can, does not mean you really can

Does your team have the skills?

− PLM Source and Target Expertise

− Complete Understanding and Access to Systems API’s for complex workflow

− Check In, Check Out, Insert Update, Conflict Management, Effectivity Mapping

− Java, C++, SOAP, REST, SOA, XML, XSLT……..

Does your team have the time ?

− This is a full time job for x people and y months.

− This should be planned and worked on throughout PLM deployment not just the last few weeks.

− Does the rest of the company have time for repeated testing?

43 1.26.2017, Schouten


DIY Final Thoughts

Many companies have successfully worked on their own PLM migrations with varying degrees of success.

− Allocate enough time

− Allocate enough resources

− Do what you can, but know when to get extra help

− Plan Hard

− Test Hard

− Document Success Criteria

− Over Communicate with Everyone

− Use commercial tools where available instead of reinventing the wheel each time

44 1.26.2017, Schouten


OpenPDM MIGRATE The PLM System Migration Framework

WOULD YOU LIKE TO REPLACE YOUR PLM SYSTEM? With OpenPDM MIGRATE, you can migrate your existing data either as a "Big Bang" or "incrementally"

Analysis tools for checking the source data (volume, type, etc.)

Flexible structuring of the data to be migrated (project, product, etc.)

High level of performance and error tolerance thanks to packing and parallelization

Transfer of CAD models and structures

Bidirectional synchronization for incremental migration

Migration from multiple data sources (systems and files)

Process monitoring using migration cockpit

Master your migration with OpenPDM MIGRATE!

1.26.2017, Schouten


OpenPDM Connectivity Connectors to migrate your PLM

46 1.26.2017, Schouten

Dassault

Smarteam

Dassault ENOVIA 3DX/V6

Dassault

VPM V4

Siemens TeamcenterEnterprise

PTC

Windchill

Siemens

Teamcenter

Oracle

Agile ePLM

Ansys

EKM

Dassault CATIA

3DX/V6

STEP

XML

ASCII

Web Services

Dassault

CATIA V5

Siemens

NX

PTC

Creo

PROSTEP OpenDXM

GlobalX ….

Your Legacy System

MSC Sim

Manager

SAP

SAP PLM

…

ILC

4PEP

Autodesk

Vault

Aras Aras

Innovator

OSLC

PROSTEP

PDFGen3D

Data Bases

PDM / PLM

CAx Others…

ERP SD

M

Dat

a fo

rmat

s In

terf

aces


OpenPDM MIGRATE Features and Benefits

KEY PERFORMANCE FEATURES

Tried-and-tested procedural model Processing of large amounts of data Parallel process handling Data analysis Quality assurance through validation Graphical monitoring "Soft stop" functions Modularity based on building block principle Framework for non standard systems Optional CAD data conversion Concept for temporary use

BENEFITS

Project success Manageable data migration High level of performance Calculable project High level of data quality in target system Optimum process monitoring Possibility of intervention at runtime Individualized solutions Anything can be migrated PLM and CAD system switch High level of economic efficiency

1.26.2017, Schouten


Due to the strategy program wise

Objects in the right order to get consistency in the target system

With regards to the business logic

Objects in the right order to get consistency in the target system

Quality checked Performance managed

OpenPDM MIGRATE – Architecture High Level Visualization

1.26.2017, Schouten

Export Import Transformation

Server

As Designed

As Planned

As Build

As Designed

As Planned

As Build

AS-IS Source System TO-BE Target System

Migration Process engine Business Logic Data Model Mapping Monitoring

O

penP

DM C

onne

ctor

Ope

nPDM

Con

nect

or

CAD Structure Documents

Libraries Standard Parts

Engineering standards


OpenPDM MIGRATE – Functional Principle Controlled migration of large data amounts

FUNCTIONAL PRINCIPLE

Data structures are split into small packages

Packages can be processed independently and in parallel

Sub-processes can be monitored and controlled via migration cockpit

ADVANTAGES AND BENEFITS

Processing and transfer of large data amounts become controllable

Parallel processes increase the performance extensively

Integrated report functions

High flexibility due to OpenPDM modularity

1.26.2017, Schouten

1

6

2 3

4 5

7 2

1

2 3

6

4 5

7

3

4 5

Export

Export

Export

Export

Mapping

Mapping

Mapping

Import

Import


OpenPDM MIGRATE – Migration Strategy One Time and Coexistence Migration

1.26.2017, Schouten

Longer period of coexistence Legacy system productive

Legacy system productive

Migrate data and users in one step

Migrate data and users: Project by project per application … as your needs dictate


“Big

Ban

g”

mig

ratio

n

Fixed period of time

Weekend Week

Years Months


Incr

emen

tal

mig

ratio

n


PROSTEP is Here to Help

100’s of skilled PLM and CAD consultants More than 20 years of experience since

1993 Global Reach Part of the ProSTEP iViP non profit

consortium Standards based software Best in class processes methodologies

Field Tested Commercial grade Software Flexible Rental or Purchase Options Certified and Maintained Connectors to

most popular systems

51 1.26.2017, Schouten


OpenPDM Customers

52 1.26.2017, Schouten

http://www.3m.com/


Workshop Discussion: Any final questions?

53 1.26.2017, Schouten

Products

Services

Expertise


PROSTEP Inc. PROSTEP Inc.

300 Park Street Suite 410

Birmingham, MI 48009

US Toll Free Company Voice: 8-PROSTEP-01 (877-678-3701)

US Toll Free Company Fax: 8-PROSTEP-02 (877-678-3702)

THANK YOU!

1.26.2017, Schouten 54