Convergence-Data PLM World Presentation - FINAL (009) - CLEAN

Confidential Convergence Data Services, Inc. // © 2016 Convergence Data Services, Inc. Richard Turner - Presenter

Siemens PLM Connection 2016

Orlando, FL • May 16-19

www.plmworld.org #PLMCONX

Convergence Data: Case StudyTitle: Effectively Migrating Data to Teamcenter Classification

Panzacola F-4 - Time Slot: Tuesday May 17th (01:15 PM - 02:15 PM)


Todays Presentation – Case Study – ACME Products

• Scope project: • 3 legacy systems to migrate to 1 Teamcenter PLM• 150k parts in 6 months• 1 Nervous Project Manager at ACME Products• 1 Demanding Boss

• Data Challenges: • Different levels of quality• 4 different data models• Different suppliers for same part• Similar parts with different pricing• Missing attribute data to find parts

Project Manager

Boss

Convergence Team

2


Value of High Quality Part Data

Prevent Part Duplication Increase Parts Reuse Reduce Direct Material SpendReduce Compliance and

Lifecycle Risk

Nearly 20% of your parts can be duplicatesConvergence Data – 15 years experience

“…re-usable elements can constitute up to 85% of new design content.” ~ Jim Dehmlow

(Teamcenter Blog)

Reduce material spend on similar items and spot buys.

Mitigate costly material compliance issues

Don’t put dirty or partial data into Teamcenter!!

3


ACME Data

ABB S201-K6 MiniCircuit Breaker s200 1PK6A.277VAC

TEC

HN

ICA

L D

ATA

PR

OV

IDED

DA

TA

Data cleansing is critical for an optimal PLM/ERP experience!

Data cleansing needs to include data harvesting, de-duping and normalization of data.

STA

ND

AR

D D

ATA

TEC

HN

ICA

L D

ATA

PR

OV

IDED

DA

TAST

AN

DA

RD

DA

TA

CUSTOMER PART NUMBER 34-056497-00

CUSTOMER PART DESCRIPTION CB,6A,1P,DIN,MNT

MANUFACTURER NAME ABB CNTRL

MANUFACTURER PART NUMBER A-S201-K6

Cleansed PART DESCRIPTIONCIRCUIT BREAKER, 6KA @ 240/277VAC, 10KA @ 120VAC, 10KA @ 60VDC INTERRUPT RATING, DIN RAIL MOUNTING, 1 POLES, 6A RATED CURRENT, 480Y/277VAC RATED VOLTAGE, SCREW TERMINAL, MINIATURE

CORRECTED MFG NAME ABB CONTROL, INC

CORRECTED MFG PART NUMBER S201-K6

PART STATUS ACTIVE

NOUN BREAKER

MODIFIER CIRCUIT

UNSPSC CODE 39121603 MINIATURE CIRCUIT BREAKERS

INTERRUPT RATING 6KA @ 240/277VAC, 10KA @ 120VAC, 10KA @ 60VDC

MOUNTING DIN RAIL

NUMBER OF POSITIONS 1

RATED CURRENT 6A

RATED VOLTAGE 480Y/277VAC

TERMINAL TYPE SCREW

TYPE MINIATURE

TEC

HN

ICA

L D

ATA

PR

OV

IDED

DA

TAST

AN

DA

RD

DA

TA

4


Todays Presentation – ACME Case Study

• Presentation Today:• The process followed to execute the project• Classification methodology• Project resources and timeline• Tools and Teamcenter integration• Benefits achieved

5


ACME Project Structure

Convergence Team ACME Team

Project Owner

Project Manager

Category SME

Procurement

ITData

Approvers

Account Manager

Project Manager

Data Services

Classification SME

Harvesting Team

Mechanical SME Electrical SME

Healthcare SMELife Sciences

SME

Data QC

Team

Support

Training

Technical

Engineering

Software Developers

Software QA

6


87654321

Harvesting / Normalizing / Cleansing / De-Duping / QC

Warranty

Organize Data files

ACME Project Schedule (150k parts)

Kick off

Identify Attributes

Production

Data Harvesting/Cleansing

MobilizationTaxonomy

Review

Taxonomy LoadTrainingServer Setup

Identify Harvest SourceDefine Key Attributes

Ongoing Part Support

Data Integration

Batch (40k)Batch (40k)Batch (40k) Batch (30k)

Collaborative Quality Review

Month

AnalysisReporting

Teamcenter

7


ACME - PLM Part Data Sourcing Process

2

1

3 Analysis & Search

PLM

/ E

RP

Dat

a So

urc

es

Gather Disparate

Data

Harvesting and Enriching Data

Content

Classifying Data

Integrate into Unified PLM, &

ERP

Teamcenter

Modeling & cleansing system “DFR”

SAP

8


• Identified/prioritized source data, agree on objectives, extract source data

• Data Loading*: Load existing part data, MFG info, Supplier, codes, categories

*Doesn’t need to bel clean

Data Preparation1

• Created/Refined the data model

• Categories, attributes, properties

Data Modeling2

• Cleansed the data: classify to categories, assign attribute values, descriptions, codes, etc.

• Validated and Published: validate, approve and publish data

Part Optimization & Delivery

3

• Reporting & Analytics: graphs and dashboards

• New Parts: creation and approval of new parts

• Search: looking up and finding similar parts

Part Management & Reporting

4

4 Key Stages of the Data Classification Process - ACME

9


Step 1 – Data Preparation - ACME

• Prioritized source data, agree on objectives (150k parts)

• Collected: existing part data, MFG part info, supplier part info commodity codes, categories

Data Preparation1

ExistingData

• Determined criteria for data cleansing –• 2 year order history• Inventory status – active only • Item Types – parts only

• Worked out how to manage duplicates• Duplicate MFG part number• Duplicate by attributes

• Obtained requirements for target system –Teamcenter rules – data and model

• Rationalize commodity codes – different between legacy systems

Migration Strategy

10


Step 2 – Data Modeling - ACME

• Created/Refined the data model

• Categories, attributes, properties.

• Data governance –who is allowed to make/approve changes

Data Modeling2

• Industry Standard Codes – ECCMA, UNSPSC, FSC

• CDS provided a majority of the data model – approved by ACME

• Determined how many descriptions –format, length, abbreviations, UOMs, etc.

Identify Attributes & Categories

• Data model needed to be maintainable and flexible to changes

• Aligned category and attribute properties to ERP / PLM

• The data model properties drove many things – search, validations, analytics, etc.

Create/Refine Data Model

11


Step 3 – Part Optimization & Delivery - ACME

• Cleansed the data: classify to categories

• Validated and Published: validate, approve and publish data

Part Optimization & Delivery

3• We harvested data from

websites, documents, internal and external databases

• In some cases we contacted suppliers to obtain missing data

Harvest & Cleanse

• Data needed to pass validation and fill rate reports

• Harvested data was normalized against our data model

Normalize & Validate

• Approved data is locked down

• Select fields can be exported to target systems e.g. Teamcenter, SAP

Approve & Deliver

ConvergenceData

Services

12


Teamcenter Integration - ACME

• Classification • Uploaded TC Classification into DFR

• Created new Classification into TC from DFR

• Use DFR to extend categories lower for reporting/analysis

• DFR and Teamcenter – Classification Synergies• DFR – batch data cleansing workflow, cleansing

and validation tools, agnostic

• Teamcenter – attribute based search and new part creation

Modeling & cleansing system

“DFR”

Teamcenter

Analysis & Search

Part Data

Classification

13


Dashboard used to track progress

14


Step 4 – Part ManagementSearch & Reporting

• Reports: dashboards to manage ongoing work

• Analytics: graphical analysis of the data

• New Parts: creation and approval of new parts

• Search: access to lookup and find like parts

Part Management & Reporting

4

SCREENSHOT OFADVANCED SEARCH TOOL?

• Search tools leverage the new data model – find parts vs. creating parts

• New parts must be classified and cleansed to maintain higher data standards

• Data governance setup to approve new part requests

Ongoing Data Maintenance

15


Attribute Name Value Item Count Percentage

Head Type Double Hexagon 1299 44.71

Head Type Hexagon 1201 41.06

Head Type Flat 229 7.94

Head Type Pan 64 1.08

Step 4 – Part Management & Reporting

Bar Graph of Screw Head Types

• 30 Similar Bolts Clustered• $.05 to $150 price variance

16


Results – ACME Products

• Identified duplicates and near duplicates

• Establish governance for new part introduction process

• 20% less new parts – easier to find parts (2,000 parts)

• Define preferred parts

• Improve search efficiency

• Avoid new part creation costs ($5,000 to $20,000/part)

• 2,000 parts x $10k = $20M annual savings for new part requests

• Rationalize parts

• Enable strategic sourcing - One preferred supplier per part

• Enable spend analysis – more granular level (cluster)

• Estimate 5% reduction in $100M spend = $5M Direct Material Savings

• Monitor risks for obsolescence and counterfeit parts

• Ensure export and environmental compliance (e.g. RoHS, REACH, etc.)

• Mitigate fines, recalls

Prevent Part Duplication Increase Parts Reuse Reduce Direct Material SpendReduce Compliance and

Lifecycle Risk

17


Project Lessons: avoid road blocks

• Let the data drive the category structure• Let the data drive normalization• Identify Key attributes up front• Decide on UOM values and standards up front

• Plan ahead: different countries may need different UOMs, Fractions vs. decimals (or both)

• Manage Policies for exporting data• Use Reports to help QA that data• Map duplicate internal parts to 1 preferred part for

ERP – avoid rationalizing BOMs (1 to many)• 2 years purchasing history for short life products• Use abbreviated codes for ERP – classification for

elongated codes (spend rollups)

Lessons Learned

18


Our Company

Data from disparate sources (Purchased parts, MRO, design parts, etc.)

Data for migrations:ERP, PLM, MDM, PIM

Parts re-useinitiatives, mitigate parts

proliferation

Analytics supporting cost reductions &

classification search

Our MissionHelp our customers extract more value out of their enterprise systems with improved part data.

Providing services to• Aerospace/Defense• Electronics• Automotive/Industrial• Consumer/White Goods• Oil/ Gas

15 Years Experience

Cleanse & Normalize Prepare Support Provide

19


Richard [email protected]

Alison [email protected]

Visit us in the Solution Center (near booth 321 in the back)

20


Thank You!

Your feedback is important.

Use the PLM World mobile app to fill out the Session Survey.

• Locate the session in the app

• Select “Take Survey”

21


Our Relationships

Customers Partners

22


Design for Retrieval (DFR)

DFR Administration Client• Windows Azure cloud-based architecture

Back-End Administrators

Creation and maintenance of the category structure by adding / editing attributes to a category, submitting category for approval and using the description generator.

DFR OnlineFront-End Web users

Classification Manager

Attribute Manager

Item Loader

Data Developer

Allowed Values Manager

Enables the user to create attributes, relationship attributes, image attributes and groups of attributes to set up in the category tree.

Used to load data in batches and populate items with attribute and relationship values. Attribute data can be added or updated with additional items.

Allows the assigned user to check, modify or verify the attribute values for each data item assigned to him/her.

Allows users to cleanse data, impose rules for creating new data. Users can request an attribute value and workflow for approval/denial of values.

SOA / API layer - Framework to integrate with your ERP, PLM, PIM

Exports categories, category attributes, allowed values and

Items.

Direct access to the catalog configurations via the UI.

Manages Data rules

ExportManager

Options Manager

PolicyManager Administrative User Mgmt. &

Permissions

23

Documents

Convergence-Data PLM World Presentation - FINAL (009) - CLEAN