ONCE Meeting Dallas Texas October 2005

1
ONCE MeetingDallas Texas October 2005
Master Data Management
2
Topics for Discussion

• Introduction
• Definitions The Tower of Babylon
• Sizing the opportunity
• Where can Marketplaces add value?
• Pain Points
• ERP Positioning
• Emerging Standards
• A Model for MDM
• Target business processes for MDM
• RFID MDM Discussion
• MDM Providers Who is out there?
• Conclusion Where can marketplaces / ONCE add
  value?

3
Introduction
4
Definitions The tower of Babylon

• MDM Master Data Management
• PIM Product Information Management
• GDSN Global Data Synchronization Network
• GS1 UCC EAN Barcode authorities
• RFID Radio Frequency Identification
• EPC Electronic Product Code

5
Sizing the opportunity
6
Where can Marketplaces add value?

• Building Supplier value
• Payment settlement solutions
• Data Synchronisation Services

7
Pain Points with data synchronisation

• Buyers
• Keeping Supplier data up to date
• Increasing compliance costs SOX, Minority owned
  etc
• Part and price updates
• Suppliers
• Visibility into buyer processes
• Multiple connections, standards
• Increasing compliance costs
• Marketplaces
• Standards
• ERP capabilities
• Business models

8
ERP Positioning on MDM
Reality
Marketing

• Strategies
• External
• Supply Chain
• RFID
• Inventory
• Logistics
• Collaborative design
• Internal
• Consolidation of multiple ERPs
• Portal technologies
• Central to SOA concepts
• Touch points

9
Emerging Standards

• Trading Partner numbering
• GDSN / GS1
• DUNS
• eOTD
• Catalogues / Content
• Classification UNSPSC / eCl_at_ss
• Codification eOTD
• Item identification EPC, GDSN
• XML
• RosettaNet, ebXML

10
Emerging Standards

• There are numerous initiatives however they also
  roll up to a very similar choreography
• Choreography
• Publish
• Update
• Notify
• Subscribe
• Few processes are attempting to be synchronous,
  most are asynchronous

11
Emerging Standards GS1
12
An emerging model for MDM

• Trading Partner Data
• Core, Extended, Relationship specific
• Catalogue / Content
• Base, Technical Attributes / Values
• Commercial
• Core, Complex
• Logistical
• Core, Complex
• Other
• Production, Maintenance, Sales

13
A simple use case
Core Content / Commercial Data
Technical Data
Logistics Data
14
Trading Partner data

• Core
• Company name
• Address, phone, fax, email
• Contacts
• Extended
• XML Header style data
• Remit to, Ship from etc.
• Tax number etc
• Relationship specific
• Buyer spend categories
• Local jurisdiction fields

15
Catalogue / Content

• Base
• Short description
• Unit of measure
• List price
• Part Number (supplier / manufacturer
• Technical Attribute values
• Structured description (e.g. noun modifier)
• Standard set of attributes (often with valid
  values)
• Descriptive patterns etc

16
Commercial

• Core
• Lead time
• Price effective dates
• Classification
• Price (list)
• Contract number
• Complex
• Volume / discount
• Attribute based pricing (distance, weight,
  volume)
• Caps, floors etc

17
Logistical

• Core
• Height
• Width
• Depth
• Weight
• Classification
• Complex
• Pack sizes
• Lots
• QA

18
MDM data Complexity verses change
Frequency of Change
Infrequent
Constant
Complex
Catalogue Technical
TP Relationship Specific
Catalogue Core
Complexity of Data
Commercial / Logistical (Core Complex)
TP Extended
TP Core
Simple
19
Target Business Processes for MDM

• Inventory
• Vendor managed, Kanban
• Inventory sharing
• Inventory update (parts
• Logistics
• 3PLs
• JIT
• Procurement
• Supplier discovery and sourcing
• Invoicing
• Pricing
• Compliance
• Contract Management
• Contract Compliance

20
RFID MDM

• There is a land rush for RFID standards
  (technology and standards management)
• Barcoding is the underlying enabler to RFID
  deployment
• Master Data Management is the underlying enabler
  to cross trading partner Barcode implementation
• Retail Industries seem to be the leaders in the
  space
• WALMART etc

21
MDM Providers Who is out there?
22
(No Transcript)
23
Conclusion Where can Marketplaces add value

• Open discussion