master data management (mdm) & plm in context of enterprise product management
TRANSCRIPT
1 Copyright © 2013 Tata Consultancy Services Limited
Master Data Management (MDM) & PLM – Enterprise Product Management
2
Table of Contents
1 Key trends in Product Development, reshaping product data
2 Current MDM practices, Need for product master data in MDM
3 Understanding Product Master Data - Ontology & Approach
4 PLM and MDM relationship
5 Customer Case Reference
6 Benefits & Takeaways
3
Engineering Systems Manufacturing Systems Sales & Marketing Systems
Component Supplier
MfgPlant
Engineering Data Mfg
Data
SalesData
SalesData
ContractManufacturer
MfgPlant
Mfg Data
SalesData
MfgPlant
Engineering Data
Mfg Data Engineering
Data
Acquisition
Engineering Data
Mfg Data
Mfg Data
Engineering Data
Designer
Designer
Part Engineer
Part Engineer
MfgPlant
Mfg Data
Mfg Data
Globalization, Innovation, Cost competitiveness and Sustainability bringing increased focus on Product data
Mergers, Acquisitions and Divestitures
Continuous and ongoing activity of Product Data synchronization .Understanding of “What Product Data is” is different across organizations
Globalization and localization of Products
“Product Data” mutates to meet local business and IT needs
Evolving Biz needs increasing the scope of product data elements
Continuously evolving business needs on “Product Data”.
Multidisciplinary View of Products
Constant increase in complexity of information needed to comprehensively understand product data.
Future proof IT at lower TCO
Scalable robust IT infrastructure built on new gen IT strategies . Standardization and Harmonization of IT systems and services
4
Organizations are constantly thriving to address their challenges in managing and sharing Product Data
Complex Product data, fragmented across the organization
Looking beyond CAD & Documents and tackling the Complex Part/BoM /Change relationshipsIncreased software intensity in productsExpanding functional footprint (Simulation, Digital Mfg Data, Compliance and Quality Data)
Product Data, today is federated and exists in disconnected multiple systems resulting in data ownership, governance and security issues
Lack of Data / process synchronization leading to Usage of old and duplicate product data Long cycle times for data reconciliation
Ever increasing mergers & acquisitions leading to growing complexity in product data diversity and relationships
Available Product Data is not trustworthy for decision making
“A need exists for a system to store released product information available as a System of Record, defined as Product Master Data which can be referred across the organization”
Are Today’s MDM practices able to
establish a product Master to address
these challenges ??
5
Data Analytics & BI
Current established practices of MDM should enrich the scope and boundaries of Product Data
CRM ERP MES MRO LegacyCRMCRM ERPERP LegacyPDMMES
MDM
EAI/P2P/SOA
Customer Master
data
Product Master
data
SupplierMaster
data
Enterprise Data Warehouse
ETL Engine
EmpMaster
data
Data Integrity
Data Accountability
Data Accuracy
Data Stewardship Semantic consistencyData Ownership
Today, Product Master data under MDM is catering mainly to the Sales and Marketing needs of the organization (Product Catalog, pricing, availability , etc..)
Data Quality Data Reuse
Data MartData Mart
Data Mart
Data Accountability
6
Multiple R&D Systems
across BUs
Derivable views for MTS, CTO, ETO etc
Product Master Data
Understanding Product Master Data in the Context of Master Data Management
Parts Data
Docs/Specification Configuration Data
Design Data
Prod Quality Data Product Compliance Data
Product Service Data
Sales
Mfg
Supply Chain
Service
Sales
SalesProduct CatalogSales ConfigurationsQuotes & OrdersMat’l safety data sheets
Mfg
MfgPlant BoMsPlant routingsWork instructionsTest plans and procedures
Service
ServiceInstalled BaseSpare Parts CatalogService Bulletins
Supply Chain
Supply ChainMaterial Sourcing
MDMCustomer Master
data
Product Master
data
SupplierMaster
data
EmpMaster
data
BOMs& Routings
Work Instructions
PDM
ALM
PDMPLM(BU1)
ALMALM(BU1)
LegacyLegacyLegacy(BU1)
ALMALMAcquisitions
Enterprise Integration LayerEAI/P2P//SOA
1
2 3 4
7
Ontology of Product Master Data
Product Master Data
Parts / Components
Mechanical
Electrical / Electronic
Software
Documents
Visual Representation
2D
3D
PDF / Word
Product Structure
BOM
Relationships
Rules
Product Planning Info
Product Quality Data
Product Re-use Info
Classification
Characteristics
Product History / Change
Product Compliance Data
Routings
Process Instructions
Product Service Data
Product Technical Information
Service Parts Attributes
8
A Closer look at the Data elements and interrelationships- Ontology of the Product Master Data (But not limited to..)
Employee
Organization
Business Unit
RegionLocation
Department
Workflow
Workflow Task
Eng. Change
Issue
PartProduct Part Family
Features Master BoM
Substitute Part
AlternatePart
Spare Part
Product Configuration
Mechanical
Hardware
Software
Part
DrawingSpecification Model
Design Spec
Tech. Spec
Material SpecTest Spec
JTPDF
Documents
Substance
Material
Supplier
Cost
Routings
Work Instructions
Tech. Manuals
BoMs
Images
9
PLM Systems will complement the creation of Product Master Data systems
PLM MDM
PLM is the Source for Work in Progress (WIP) Product Data
MDM is the source for Released Product Data aggregated to a Product Master
Authoring Space for Product Data Gate Keeper of Product Master Data for different consumers
Focus on Multidisciplinary engineering functions (Hardware/ Mechanics/Software)
Focus on Product Master Data needed for enterprise level transactions
Process centric approach to creation of Product Data
System of Record for establishing the single source of truth
Structured feed of data elements which can constitute the Product Master data
Leveraging the MDM infrastructure to feed different consumers like Sales, Supply Chain, Analytics etc
PLM and Product Master data Systems are complementary and not redundant
10
Data Migration Setup
Systemic View of the PLM MDM setup with other cross functional enterprise systems
Compliance
PDM/PLM
ALM
PDM/PLM
Authoring Tools
MDM/PLM
Product Data from Engineering/ R&D
Product Data needed by other functions (maintained in MDM)
Product Master
Customer Master
Sales
ConfiguratorPricingWarrantyOrders
Service
Service BOMSpares
Maintenance Schedule
ERP
Plant Specific ChangesPlanning
Production OrdersLocalization
MES
SchedulingTesting / Quality
SerializationAs Built BOM
Simulation
Supplier Master
Multiple SourcesExtract
Staging(Cleanse/transform)
Target Systems(Load)
Employee Master
Integration Data Load
11
Enabling integration between the Engineering/ R&D systems, MDM and cross functional systems
1
PLM
Engineering Business Processes
MDM
Maturity
Lifecycle
Change Product Master
2
3Sales
Mfg
Service
Supply Chain
Response
Request
Changes
Cross functional integration
12
Closed Loop Engineering Change Process
• Process definition for Engineering release to Product Master
• Mechanism to inform Product Master stakeholders regarding the change
• Change Number format harmonization in all Engineering Systems
Integration between engineering (R&D)systems and Product Data master system
• Transform engineering system data to Product Master schema
• Data validations before transfer• Development mechanism
identification for source and destination systems
• Queuing, Scheduling and Monitoring mechanism
Key Use Cases and solution scenarios
On Demand Trigger for data migration
• Establishing the triggers from Engineering systems
• Identify additional attributes for transfer
Automated ContinuousData Migration Mechanism
• Automatic transfer situations from Engineering (R&D) systems to Product Master data system
• Identify triggering mechanisms (synchronous / asynchronous)
• Workflow modifications / status change triggers modification for data transfer
Standard Based Meta Model Definition
• Meta model definition of the Product Master
• Standards based metal model for structure, relationships and information exchange
Data Ownership Identification & TransferMechanism
• Identify ownership mechanism in various Engineering Systems
• Ownership definition in Product Master system
• Role & Access Control setup in Product Master System
• Engineering attribute & Product Master attribute identification
1 2 3
5 64
13
Benefits for Globalization, Innovation, Cost competitiveness and Sustainability
Data Governance,
Risk & Compliance
Process Simplification & Standardization
Scalable and Simplified IT Landscape
• Standardized & uniform product data in Product Master system across the organization• Single source for truth for Sales, Mfg, Supply chain & Service• Ease in making Product Ownership changes• Increased data quality for decision making
• Improved change management : Control on Global/Local changes• Ease in engineering/mfg change analysis and implementation• mproved business agility & speed to customer response• Improved traceability of product data, helping in compliance & Issue
identification
• Reduced number of interfaces (Low AMS costs)• High Scalability due to standard practices and established models
14
6 Key Learnings for Product Master Data fitment into Overall MDM Strategy
1
2
3
4
5
Business Unit / Product Division level variations in Product Data will lead to more time for interfaces harmonization
No standard data ownership identification mechanism. Organization specific rules need to be developed to classify ownership
Data conflicts identification & resolution is time consuming (especially for legacy data)
Historical data migration, could lead to development of complex migration mechanisms
Changes in upstream & downstream systems calls for lot of co-ordination among different organization functions
6Standards driven Meta Model definition and data exchange like JT2Go, STEP, PLCS etc should be evaluated and established
15
Recommended reading
Open Methodology Solution on MDM (http://mike2.openmethodology.org/wiki/Master_Data_Management_Solution_Offering).
Microsoft Definition on MDM (http://msdn.microsoft.com/en-us/library/bb190163.aspx)
David Butler. Master Data Management, an Oracle White Paper, 2011.
Dr Rob Bodington, Patrick Houbaux. What is PLCS – STEP AP239, 2011.
