Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
#PLMConX
3 Keys to a Successful PLM MigrationBrian Schouten, PROSTEP@prostep_inc
#PLMConX
Company Overview
Shareholders
Over 25 years experiencewith engineering interoperability, migration, intelligent documents, benchmarking, more
Approximately 250 employees and consultantsbased from international locations throughout Europe and in North America
More than 500 Customersthat are leading companies across most industries
A vendor neutral / independent engineering services and software company since 1993
[email protected] / 8-PROSTEP01
#PLMConX
PROSTEP – 100% PLM
Strategy Concepts & Solution Architecture Implementation of IT & Process
PLM Implementation
Strategy
PLM Architecture & Processes PLM Migration & Integration − PLM System Selection− PLM Implementation− PLM Process Optimization
Benchmark & ROI-Analysis
PLM Landscape & Complexity Management
Product Structure and Variant Management PLM Realization and Roll-out
Bill of Material & Change Management
Variant & Configuration Management
Digital Master / Digital TwinPLM for Digital Transformation
PLM for IoT/I 4.0 Solutions− Digitalization− Industry 4.0− IoT
Digital Master / Digital Twin
Model Based Enterprise Technical Data Package3D Master / Systems-Engineering Paper-less Processes
PLM for Collaboration
Cross-company PLM PLM Collaboration − Merger & Acquisitions− Joint Venture− Project Consortia
PLM for Merger & Acquisitions
PLM for Joint Ventures
Partner & Supply Chain Integration
Automated PLM Data Supply
PDM & CAx Data Exchange
Consulting and Solution Portfolio
#PLMConX
PROSTEP Technology Partners
#PLMConX
PLM Migration Roadmap
PLM ArchitecturePLM Information Flow and CapabilitiesChallenges and DiscontinuitiesCompare to MarketStatistics (Data, Performance, Usage)
Pilot / Proof of Concept RFPAssessmentContractingHW/SW ProcurementSolution Partner SelectionMigration Project Planning
UATEnd User TrainingAdmin TrainingMigration Dry-runsRollout Scheduling
Business Strategy Definition / Future TopicsMajor PLM ConceptsBusiness Processes RealignmentReference Customers and Best PracticesVendor PresentationsBusiness & IT Requirements SpecMigration Strategy Selection
IT Project ManagementDetailed SpecificationSystem Configuration and CustomizationData Conversion and Migration Business Processes ImplementationSystem Interfaces ImplementationValidation & Verification
RolloutDelta MigrationIT SupportOn-site End User Support
AS-ISANALYSIS GO-LIVETO-BE
DEFINITIONSYSTEM
SELECTION IMPLEMENTATION GO-LIVE PREPARATION
#PLMConX
3 Keys to a Successful PLM Migration
1. Make sure your user base is well informed. Enterprise Public Relations Campaign is vital for any PLM Introduction and Migration. Bring stakeholders in early and teach them what they will benefit from using the system.
2. Think of migration requirements as what do you need to use the new system and what is required to decommission the old system. Utilize or develop an archiving or other alternative strategies.
3. Find a migration process strategy (One time or Co-existance) that aligns best with your business needs.
#PLMConX
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?
#PLMConX
Archiving Strategy – Put data where it needs to be!
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 (link 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!
#PLMConX
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
PLMTransactional• 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
SourcePDM System
TargetPDM System
User and Data
Migration User and Data
MigrationUser and
Data Migration
25% User Base
50% User Base
75% User Base
Complete User Base
Complete User Base
#PLMConX
Migration Strategy – Generally Aligned with Migration Methods (ETL or Transactional)
Longer period of coexistenceLegacy system productive
Legacy system productive
Migrate data and users in one step• Aligns well with ETL
Migrate data and users: Move business over
time Aligns well with
Transactional
New system productive
“Big
Ban
g”m
igra
tion
Fixed period of time
WeekendWeek
YearsMonths
New system productive
Incr
emen
tal
mig
ratio
n
#PLMConX
ETL vs. Transactional Benefits and Risks
ETL 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
ETL 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
Transactional 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
Transactional Risks• Garbage in, Garbage out• Order of import operations is not always
transparent• Performance is not as good• Testing can be cumbersome
#PLMConX
Advise 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• Production Migration
For Incremental 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.
#PLMConX
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 utilize 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!
#PLMConX
A Note on Neutral Formats in Migrations
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 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
#PLMConX
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
161.26.2017, Schouten
#PLMConX
Questions?
#PLMConX
PROSTEP INC300 Park Street Suite 410Birmingham, MI 48009US Company Voice: 8-PROSTEP-01 (877-678-3701)US Company Fax: 8-PROSTEP-02 (877-678-3702
THANKYOU!