COMPDM Efficient Data Exchange · Module TCU Module CATIA Module NXVPM Module STEP Module TFE...
Transcript of COMPDM Efficient Data Exchange · Module TCU Module CATIA Module NXVPM Module STEP Module TFE...
COMPDM Efficient Data Exchange PLM Europe Theatre Session, Wednesday October 31st, 2018
Basics of COMPDM
T-Systems SC PLM / COMPDM - Efficient Data Exchange 2
COMPDM Overview Integration of PLM, CAD and STEP
Exchange of product structure data
Conversion between multiple formats and systems
Client/Server architecture
Rich client (web client on roadmap)
Clients do not require a CAD/PLM installation
Aras Module
TCU Module
CATIA Module
NX Module
STEP Module
TFE Module
VPM Module
EnoviaV6 Module
Current Release 2.3 since June 2018
T-Systems / COMPDM - Efficient Data Exchange 3
COMPDM Efficient data exchange
Basic Concepts of COMPDM Easy to configure and to adapt to individual data models, mappings, transformation
methods and import/export processes
Based on automatic analysis of new data; system suggests mapping
Adaptations to business logic can be performed by customers, even if complex or very specific; customer’s IP is thus protected
Preconfigured for major PLM and CAD systems
Very sophisticated reconciliation capabilities before data is imported into PLM system
Optional tagging of data exchange information in PLM system
Designed to handle large amounts of data (data storage, performance)
Integration with data exchange monitor TRUfusion Enterprise™ by Rocket Software for seamless end-to-end data exchange
T-Systems / COMPDM - Efficient Data Exchange 4
COMPDM One of the best STEP AP 242 Processors Participation in AFNeT & ProSTEP iViP STEP AP242
benchmark (2017)
Seven worldwide active vendors of data exchange applications in the race including PLM system vendors
Assessment of functionality, quality of imported/exported data and compliance with STEP AP242 standard (especially relevant for Automotive and Aerospace)
Standard important for automotive and aerospace OEMs to communicate with their suppliers
Scope AP242 Business Object Model: PDM, kinematics, composites, long-term archiving, Product Manufacturing Information (PMI), Requirements Management etc.
For more details on benchmark see http://benchmark.ap242.org
Participation in next benchmark planned for 2019
T-Systems / COMPDM - Efficient Data Exchange 5
COMPDM Dedicated Use Cases
T-Systems SC PLM / COMPDM - Efficient Data Exchange 6
Prime Use Case Supplier dex in multi-oem environment
Supplier PLM Teamcenter, Aras Innovator, ENOVIA VPM V4, 3DEXPERIENCE (ENOVIA V6)
COMPDM
Create assembly files if necessary
Apply customer naming rules
Map properties Remove IP properties
Update PLM structure & docs
Convert to local file naming rules
Map properties Analyze contained properties and
compare Easy installation Installer Auto-recognition
of CATIA/NX data model Supplier
Network
Exchange to partner: geometry positioning structure PLM properties also within CAD system configuration effectivities
Trigger export by event in PLM
CAD and non-CAD documents CATIA V5, NX; other geometry formats: JT; Neutral product structure formats: STEP AP214, STEP AP242 XML
Easy to configure GUI based driven by PLM
customization
T-Systems / COMPDM - Efficient Data Exchange 7
Handling of special use cases
T-Systems SC PLM / COMPDM - Efficient Data Exchange 8
Use case: handling daimler legacy data
The issue
Daimler sends former CATIA legacy data as JT, i.e. structure consists of mixed NX and JT data
When loading to NX for each JT files an additional PRT objects gets created
If data is to be sent back to Daimler, they will get PRT files instead of JT
The solution
COMPDM prevents NX wrapper parts to be exported
JT objects get directly connected to their former parent parts
Teamcenter
9
NX PRT
JT
NX PRT
JT
NX PRT
JT
Import Export
Use case for renaming CAD files
The issue
Part numbering for partner may differ from inhouse part numbering
Assemblies sent by partner contain partner numbering and should be imported correctly
In many cases CAD files need to obey different numbering schemas internally and externally
The solution
Part recognition according to customer part number and/or internal part number
Renaming of files according to internal or partner numbering rules
Use customizable file naming templates for renaming procedure (available in version 2019)
10
USE CASE: PART RECOgNITION LOGIC EXAMPLE
Property My_ItemID
in CAD?
Start
When exporting, part number is
stored in this CAD property
yes (our data)
Part with part number = My_ItemID
in PLM?
Latest release valid
for revise ?
yes
Error!
no
Create new
revision yes
Ok
Partner‘s part number gets stored
in this PLM property when
importing
one match
Ok
no match
Create new part in PLM with new internal part number;
store original part number in customer_number
Issue warning that lists matching
part numbers
multiple matches
Search PLM for parts whose customer_number
equals incoming part identifier
no
no
Use case: handling daimler modified data
The issue Multiple modified partial assemblies are sent from Daimler to
a supplier
During export @Daimler all partial assemblies get connected to a dummy root node (named ARR…)
Additionally two STEP files are created and sent with the package:
_smaragd.stp contains whole assembly structure with parts at leaf level and no intermediate nodes
_sam.stp file contains intermediate nodes explicitly and creates them as PRT files
Both do not have a connection to the virtual root
node
Dummy ARR node should not be imported to Teamcenter (always the same prt name but does not represent a real part number)
Handling of STEP files generally difficult for suppliers
The solution COMPDM can read STEP files and thus ignore ARR node
automatically
When reading the _sam.stp file, intermediate prt files are imported to Teamcenter, thus the structure is immediately valid for the TC/NX integration.
In the end assembly structure gets imported without issues
Daimler JTs can be imported as DirectModels and could be re-exported in JT format (in case Daimler requests it).
12
Working with COMPDM Highlights
T-Systems SC PLM / COMPDM - Efficient Data Exchange 13
Configuring data exchanges Two simple steps to perform
Create data representation(s) for relevant objects & properties (for each PLM/CAD involved)
Connect representations with a mapping
T-Systems / COMPDM - Efficient Data Exchange 14
Configuring data exchanges Creating representations
Create data representation(s) for relevant objects & properties (for each PLM/CAD involved)
CAD: Optionally scan sample data
for properties
PLM: Pick objects and properties
directly from customization
Connect representations with a mapping
T-Systems / COMPDM - Efficient Data Exchange 15
Configuring data exchanges Creating Mappings
Create data representation(s) for relevant objects & properties (for each PLM/CAD involved)
define property mappings
connect representations
Connect representations with a mapping to form a data exchange method
T-Systems / COMPDM - Efficient Data Exchange 16
Executing data exchange processes Utilizing comprehensive client gui
Powerful GUI for administrator to configure exchange processes
Easy to use GUI for end user to execute and monitor exchange processes
Stores exchange information in PLM System
optionally linked to exported/imported parts or root part
Main window shows all processes and their status access logs, traces, or a review of product structure
T-Systems / COMPDM - Efficient Data Exchange 17
Executing data exchange processes Integration with TRUfusion enterprise (option)
Enabling an end-to-end data exchange process
For customers having Teamcenter, the TRUfusion Enterprise ™ (TFE) plugin is used to select data, specify receivers and trigger extraction by COMPDM, all directly from within the Teamcenter client.
For all other customers, the COMPDM client allows selecting a receiver from TFE’s partner database and automatically transfers exported data to the TFE server for further processing (e.g. quality check) and sending
When receiving files, TFE automatically launches a COMPDM import process for them
TFE Job number is referenced in COMPDM process list
See also: http://www.rocketsoftware.com/products/rocket-b2b-supply-chain-integration/rocket-trufusion-enterprise
T-Systems / COMPDM - Efficient Data Exchange 18
COMPDM Roadmap
T-Systems / COMPDM - Efficient Data Exchange 19
Version 2.2
PLM Modules for Teamcenter, Aras Innovator, VPM V4
CAD Modules for CATIA V5, NX
Version 2.3 ENOVIA V6/
3DX Module
Interactive Mappings
Version 2019
Filename mapping templates
Web Client (end user view)
Version 2019R2
Windchill Module
12.2017 06.2018 12.2018 06.2019
References
T-Systems SC PLM / COMPDM - Efficient Data Exchange 20
References Overview (excerpt)
Migrate CAD data from Enovia VPM V4 to Teamcenter
Handle references contained in CATIA V5 Multi-Model Links
No intermediate format
Project ongoing till YE 2018
Yanfeng Automotive Interiors (China), IAC Group (USA), SMP (Germany), Lisa Dräxlmaier (Germany)
Tier-1 suppliers, Teamcenter based File based data exchange (CATIA, NX) with many (up to 50) OEMs and Tier-2
suppliers
Introduction of Aras Innovator as central PLM backbone for all product lines Synchronization (delta): multiple VPM V4 (master) to Aras (slave) based on
COMPDM In work: Data migration from 3DEXPERIENCE to Aras Planned: File based supplier integration to Aras (CATIA)
Tier-1 supplier of Ford using Aras Innovator
CATIA file based data exchange with Ford and suppliers
Productive use of COMPDM since early 2017
T-Systems / COMPDM - Efficient Data Exchange 21
References Overview (excerpt)
Mass CATIA V5 data import to Aras Innovator in preparation of a PLM migration
PoC ongoing until November 2018
T-Systems / COMPDM - Efficient Data Exchange 22
“London Taxi” successor, purchased by Geely Automotive
Migrate CAD data and product structure from 3DExperience to Teamcenter
Intermediate format: STEP AP242
Successful PoC in 12/2017 and 01/2018
Contact Martin Frenzel (product management) [email protected] +49 711 999 7052
Oliver Quak (Sales management) [email protected] +49 40 30600 5542
23 T-Systems SC PLM / COMPDM - Efficient Data Exchange