Академический Документы
Профессиональный Документы
Культура Документы
Agenda
Master Data Management Market Update
IBM Multiform MDM Strategy Keep it simple
Introduction to IBM MDM Server v8
Key Supported Features
Implementation Styles
Packaging and Pricing
CDI Entry Level Concept
Case Studies
Revenue
700
140%
Growth
600
120%
500
100%
400
80%
300
60%
200
40%
100
20%
0%
2003
2004
2005
2006
2007
2008
2009
2010
Source: Magic Quadrant for Product Information Management, 2Q07, Gartner, Inc.
(IDC)
Source: Gartner, Inc. Magic Quadrant for Customer Data Integration Hubs,
2Q06 by John Radcliffe. May 26, 2006. This Magic Quadrant graphic was
published by Gartner, Inc. as part of a larger research note and should be
evaluated in the context of the entire report. The Gartner report is available
upon request from IBM.
Agenda
Master Data Management Market Update
IBM Multiform MDM Strategy Keep it simple
Introduction to IBM MDM Server v8
Key Supported Features
Implementation Styles
Packaging and Pricing
CDI Entry Level Concept
Case Studies
Data and
Functionality
unique to each
application
CRM
Billing
ERP
Application-unique
Functionality & Data
Application-unique
Functionality & Data
Application-unique
Functionality & Data
Common
Functionality & Data
Common
Functionality & Data
Common
Functionality & Data
Symptom
Data is inaccurate, incomplete
and conflicts with other systems
10
Root Cause
Common data and data
function is siloed
Contain configurable functionality to maintain and be the system of truth for master data
11
Operationalize
Create and
Define
Real-time
business services
12
Analyze
Insight and
Analysis
13
Party, Product,
Account, Location
Party
PRODUCT
Agent
Customer
Employee
Prospect
Supplier
Part
Product
Product Bundle
Item/SKU
Service
Terms & Conditions
ACCOUNT
LOCATION
Contract
Agreement
Transaction
Reward Program
Financial Account
Location
Address
Contact Method
Geography/Region
Party
Account
Product
Location
14
Multi-domain Relationship
Management
An MDM Application must
manage complex relationships
among data domains to gain
understanding of master data
Op
Co
lla
al
n
io
t
a
er
Data
Lifecycle
Management
bo
ra
tive
Analytical
15
Application-unique
Functionality & Data
Application-unique
Functionality & Data
Application-unique
Functionality & Data
Common
Functionality & Data
Common
Functionality & Data
Common
Functionality & Data
Common
Functionality & Data
Operational
Data Usage
Collaborative
Data Usage
Operationalize
Analyze
Analytical
Data Usage
Common
Functionality & Data
16
Data
Warehouses
Reporting &
Analytics
Analyze
master data
Operationalize
Create and
Define
Real-time
business services
Analyze
Insight and
Analysis
17
Consolidation
Registry
Co-existence
Transaction
Consolidation
Registry
Co-existence
Transaction
Consolidation
Full data model across multiple
data domains
Batch import capabilities +
Information Server integration
Data stewardship and
governance functionality
Batch export to target systems
Batch Import
MDM Database
Full Data Model
Matching
Governance
Batch Export
18
Consolidation
Registry
Co-existence
Transaction
Registry
Index (cross-reference) capabilities
for any data entity and attribute in
the IBM MDM Server database
Search and inquiry services
Capabilities for virtual consolidated
view via Information Server
capabilities (federated queries)
Data stewardship and matching
19
Source
Source
MDM Database
Index
Virtual View
Consolidation
Registry
Co-existence
Transaction
Batch Import
Co-existence
Full data model across multiple data
domains
MDM Database
Full Data Model
Matching
Governance
Application
Application
Application
20
Registry
Co-existence
Transaction
Application
Application
Transaction
System of record add and update SOA
transactions, with full business logic
Transaction audit logging and database
change logging and auditing
Authorization an the data attribute level
rules of visibility to control data access
Transaction processing capabilities
transactional integrity across all business
services and ability to participate in
enterprise (cross application) transactions
21
MDM Database
Full Data Model
Matching
Governance
Application
Application
Application
Registry
Co-existence
Transaction
22
Action
Maintains single
record
MDM business
services
Data
Governance
Rules of visibility
Services interface
Intelligence
Business rules to
manage events
Leverage
Interaction
Business rules to
manage events
Aggregate and
syndicate data
IBM MDM Server and IBM WebSphere Product Center deliver Multiform MDM capabilities
Operationalize
Create and
Define
Real-time
business services
Analyze
Insight and
Analysis
23
Consolidation
Registry
Co-existence
Transaction
Index
Reference System of
Data Record Data
Operationalize
Analyze
25
26
Cross-domain capabilities
Manage Risk & Compliance
Master Data Lifecycle Support
Manage Information Complexity
Optimized Infrastructure
WPC
Collaborative Prod
Cambridge
Collab
Party
Collaborative Prod
Hollywood
Collab
nt
e
09
em
20
g
na
a
aM
Operational
Party
Glendale
Acct
Prod
Multiform Phase II
Auckland
Operational
Operational
27
Party
Acct
Prod
Multiform Phase I
Party
Prod
Bordeaux
Collaborative Prod
WCC
Acct
Multiform Phase III
WPC
Customers
WCC
Customers
Analytical
WPC
Customers
WPC
WPC
Operational
08
20
M
IB
r
e
v
r
Se
at
D
r
e
t
s
Business Benefits
Revenue Enhancement
Ma
Customer Care
Thread and Fraud
Services Optimization
Operational Efficiency
10
20
Agenda
Master Data Management Market Update
IBM Multiform MDM Strategy Keep it simple
Introduction to IBM MDM Server v8
Key Supported Features
Implementation Styles
Packaging and Pricing
CDI Entry Level Concept
Case Studies
28
Operationalize
Create and
Define
Real-time
business services
29
Analyze
Insight and
Analysis
Improved and
differentiated customer
service
Regulatory compliance
30
Operationalize
Real-time
business services
Analyze
Insight and
Analysis
Action
Data Governance
Rules of visibility
Services interface
Integrity
Intelligence
Business rules to
manage events
31
Action
100% service oriented every function is a business service to maintain the master customer profile
More than 700 large and fine grain business services
Integrity
Data quality components are integrated with MDM business services
Detection of duplicate parties, data validation rules
Data stewardship UI managing data and data quality within MDM Server customer master profile
Intelligence
Business rules event detection and notification
Critical data change management
Data Governance
Privacy, data security & governance manage user/role access to data at a granular level
Knowledge
Party-centric model with complex hierarchies
Contains operational database and history/audit trail database to maintain master data audit trail
Note: all information represents IBM's current intent, is subject to change or withdrawal, and represents only goals and
32
Action
Name
Address
Add
Customer
Search
Person
Check for
Duplicates
Add
Customer
Contact Method
Identification
Relationship
Financial Profile
Intelligence
Check User
Authorization
Integrity
Duplicate Suspect
Processing
Knowledge
Action
MDM business services
Data Governance
Rules of visibility
Services interface
Integrity
Maintains single record
Intelligence
Business rules to
manage events
Flexibility
Easily extend or build new services from existing services
33
Action
MDM business services
Data Governance
Rules of visibility
Services interface
Integrity
Maintains single record
Intelligence
Business rules to
manage events
Party Demographic
Services
Roles-related Services
Account Services
Product Services
Party
Basic Demographics
Definable Demographics
Party Names
Party Values
Party Search
Delete Party
Delete Party History
Interaction History
Campaigns
Privacy
Customer Preferences
Party Values (Value Profile)
Notes/Alerts
Data Stewardship
Services
Party Relationship
Services
Location Services
Contract
Contract Component
Contract Party Role
Contract Details
Contract Location
Contract Terms & Conditions
Contract T&C Override
Contract-Product Relationships
Contract Note/Alert
Contract Search
Contract Relationship
Value Package Management
Party Relationships
Party Grouping
Hierarchy Management
Role Relationships
Line of Business
Address
Contact Method
Household
Location Group
Role Location
Address Standardization
Address Demographics
Product
Product Type Hierarchy
Product Values
Product Search
Product Terms & Conditions
Product Relationship T&C
Product Category Hierarchy
Product Identification
Product Equivalency ID
Product Content Mgmt Ref
Product Relationships
Category Hierarchy Equivalency
Category Hierarchy Search
Category Hierarchy Values
Terms & Conditions
Terms & Conditions Parameters
Bank Account
Credit Cards
Payroll Deduction
Income Source
Party Events
Events
Customer Value Profile
Corruption Management
Needs Analysis
KYC Questionnaire
35
Contract Services
Contract
Contract Component
Contract Party Role
Contract Location
Billing
Rebate/Claim
Contract Note/Alert
Contract Search
Contract Relationship
Holding
Action
MDM business services
Data Governance
Rules of visibility
Services interface
Integrity
Maintains single record
Intelligence
Business rules to
manage events
36
Data Stewardship
Application enhancements
Task management
Party management
capabilities
Data decay and recency
Hierarchy management
Grouping and relationship
management
Action
MDM business services
Data Governance
Rules of visibility
Services interface
Integrity
Maintains single record
Intelligence
Business rules to
manage events
37
Action
MDM business services
Data Governance
Rules of visibility
Services interface
Integrity
Maintains single record
Intelligence
Business rules to
manage events
Flexibility
Federated Deployments
Performance
Metadata management
Performance optimization
38
Integrity
Maintains single
record
Action
MDM business
services
Intelligence
Data
Governance
Services interface
Replication of data in
siloed projects
Requirements grow over
time and require different
POVs
Single view of
Single view of
CUSTOMER
PRODUCT
Agent
Customer
Employee
Prospect
Supplier
Part
Product
Product Bundle
Item/SKU
Service
Terms & Conditions
Master
Single view of
ACCOUNT
record
Contract
Agreement
Transaction
Reward Program
Financial Account
39
LOCATION
Location
Address
Contact Method
Geography/Region
Action
MDM business
services
Intelligence
Data
Governance
40
Services interface
Hierarchy
Party
Identification
Product
Roles
Relationships
& Groups
Account
Interactions
Location
Intelligence
Action
MDM business
services
Data
Governance
Location
Services interface
KYC Compliance
Demographics
Interaction
Relationships
Privacy
Roles
Party
Contract
and Product
Financial
Profile
Events
and Insight
41
Data
Identification Stewardship
Intelligence
Action
MDM business
services
Data
Governance
Services interface
Base Contract
Relationships to Party
Relationships to Product
Contract Services
Account
Relationships
Agreement
Account
Account to
Party Role
Account
Components
Account
42
Account
Alerts
Contract
Agreement
Transaction
Reward Program
Financial Account
The Account domain would be used to manage the Contract between a Retailer and Vendor (Supplier)
The Account domain would be used to manage the Contract (Store Card Account) between a Retailer &
Customer
43
MDM Account
MDM Account provides a single source of truth of
accounts and relationships among accounts.
Consolidated Statements
Consolidated Billing & Payments
Account Sweeps
Rewards Points across accounts
MDM Account
Value Package X
(Managed Account)
Cheque
Account
(Ref Account)
Savings
Account
(Ref Account)
Credit
Account
(Ref Account)
Cheque
Account
Savings
Account
Credit
Account
Cheque System
Savings System
Credit System
Account Details
Account Services
Contract
Contract Party Role
Contract Details
Contract Location
Contract Terms & Conditions
Contract T&C Override
Contract-Product Relationships
Contract Note/Alert
Contract Search
Contract Relationship
Value Package Management
46
Product
Checking
Account
(Ref Account)
47
Savings
Account
(Ref Account)
Party
Credit
Account
(Ref Account)
Checking
Account
Savings
Account
Credit
Account
Cheque System
Savings System
Credit System
Action
MDM business
services
Intelligence
Data
Governance
Services interface
Good
Category
Service
Hierarchy
Product
Terms and
Conditions
48
Crossreference
Keys
Features
Base Product
Product Dynamicity
Category Hierarchy
Localization
Product Services
Product model with
support for different
Party Roles
Part
Product
Product Bundle
Item/SKU
Service
Terms & Conditions
Product Domain
Support for large, complex product implementations
Validation framework
Standards based
Inheritance
49
MDM Product
MDM Product provides a single source of truth for product information.
50
Card Product
Product Details
Product Services
Product
Product Type Hierarchy
Product Values
Product Search
Product Terms & Conditions
Product Relationship T&C
Product Category Hierarchy
Product Identification
Product Equivalency ID
Product Content Mgmt Ref
Product Relationships
Product History Audit Trail
Category Hierarchy Equivalency
Category Hierarchy Search
Category Hierarchy Values
Terms & Conditions
Terms & Conditions Parameters
51
Loan Product
Credit Facility
Deposit Prod
52
AddProductInstance
AddProductType
UpdateProductInstance
UpdateProductType
GetProductInstance
GetProductType
SearchProductInstance
GetAllProductTypes
AddProductAdminSysKey
AddProductTypeSpecUse
UpdateProductAdminSysKey
UpdateProductTypeSpecUse
GetProductTypeSpecUse
GetAllProductTypeSpecUsages
GetAllProductSpecs
CategorizeProduct
CategorizeProducts
GetProductAdminSysKey
GetProductAdminSysKeyByProductId
GetProductAdminSysKeyByIdPK
GetAllProductAdminSysKeys
AddProductIdentifier
UpdateProductIdentifier
UpdateProductCategoryAssociation
RecategorizeProduct
GetProductIdentifier
GetAllProductCategoryAssociations
GetAllProductIdentifiers
GetProductCategoryAssociation
AddProductInstanceRelationship
GetAllProductsInCategory
UpdateProductInstanceRelationship
GetProductInstanceRelationship
GetAllProductInstanceRelationships
(bordeaux)
(bordeaux)
(bordeaux)
Account Data
Starving Student
Bundle Shell
(managed account)
iPod
(reference account)
(reference account)
Discount = 5%
Free iPod if accounts in good
standing after three months
The accounts within the bundle
must be in a valid status
Status = Active
Status = Credits Only
53
Discount = 7%
Implementation Approaches
Consolidation
Registry
Co-existence
Transaction
54
Geographies
Action
MDM business services
Data Governance
Rules of visibility
Consolidation
Registry
Co-existence
Transaction
55
Services interface
Integrity
Maintains single record
Intelligence
Business rules to
manage events
Action
MDM business services
Data Governance
Rules of visibility
Consolidation
Registry
Co-existence
Transaction
Services interface
Integrity
Maintains single record
Intelligence
Business rules to
manage events
Action
MDM business services
Data Governance
Rules of visibility
Consolidation
Registry
Co-existence
Transaction
57
Services interface
Integrity
Maintains single record
Intelligence
Business rules to
manage events
Action
MDM business services
Data Governance
Rules of visibility
Services interface
Integrity
Maintains single record
Intelligence
Business rules to
manage events
Consolidation
Registry
Co-existence
Transaction
System of record add and update SOA transactions, with full business logic
Transaction audit logging and database change logging and auditing
Authorization an the data attribute level rules of visibility to control data
access
Transaction processing capabilities transactional integrity across all business
services and ability to participate in enterprise (cross application) transactions
58
59
Web Site
Contact Center
Store
Name:
Address: 437
Easy Street
Address
Address: 123
Main Street
High value
customer 10% off
Sales History
Product: 1234, 5748
Jane Smith
Is a high value web customer
60
Preferences
Customer Value:
High
Sales History
Product: 6574
Contact Center
Store
Jane Smith
MDM Server business services provide
every customer interaction point with the
complete view of the customer
Jane is now viewed and treated equally
across channels
And Service Improves
Yes I do see the order you placed on 2/2.
Did you know you qualify for a discount
promotion?
Would you like me to send that to your
home address?
61
getParty Service
Address:
Home - 123 Main St
Billing 437 Easy St
Interaction History:
Service Issue 4/23/06
Web Order 2/2/06
Store Order 1/5/06
Relationships
Household:
Daughter Jenny
Husband John
Employer IBM
Privacy Preferences:
Solicitation - No
Identifier IDs
Demographics:
Income - $100,000
Interests - Running
Age - 41
Life Events:
Daughters Birthday
Wedding Anniversary
Operational Inefficiencies
Problem: Inability to sell and service bundled product
Web Site
Product Sys 1
Product A:
Address: 437
Easy Street
Product B
Discounted
Product Sys 2
Jane Smith
The marketing department wants to
offer this ideal customer bundled
products to increase revenue and
drive customer loyalty
Operational systems are not
capable of managing bundles,
which are relationships among
existing products
The result is significant manual
effort and cost to create the illusion
of a bundle (e.g., manually
discounting a product in multiple
systems) and no way to manage or
track the bundle over time
62
Product 3345 67
High value
customer 10% off
Product C
Sales History
Product: B, 2234 68
Customer Value:
High
Product 2234 68
Discounted
Web Site
Product Sys 1
Product Sys 2
Jane Smith
Address:
Home - 123 Main St
Billing 437 Easy St
Interaction History:
Service Issue 4/23/06
Web Order 2/2/06
Store Order 1/5/06
Relationships
Household:
Daughter Jenny
Husband John
Employer IBM
Privacy Preferences:
Solicitation - No
Identifier IDs
Demographics:
Income - $100,000
Interests - Running
Age - 41
Life Events:
Daughters Birthday
Wedding Anniversary
Agenda
Master Data Management Market Update
IBM Multiform MDM Strategy Keep it simple
Introduction to IBM MDM Server v8
Key Supported Features
Implementation Styles
Packaging and Pricing
CDI Entry Level Concept
Case Studies
64
5 choices align with IBM Sectors (i.e. COMM, DIST, FSS, IND, PUBLIC)
Industry: XYZ
Functional
Usage Styles
Foundation
Transaction Hub
66
Types of Records
Party: Individual
Party: Organization
Account
Product
Communications
Sector
Distribution
Sector
Financial
Services Sector
Industrial Sector
Telecommunications
Retail Industry
Banks
Automotive
Government
Media&
Entertainment
Consumer
Products
Financial Markets
Electronics
Education
Insurance
Health
Utilities
Travel &
Transportation
Aerospace &
Defense
Chemical &
Petroleum
Industrial Products
67
Public Sector
Life Sciences
Types of Records
Party: Individual
Party: Organization
Account
Product
68
MDM Server team plans to install ITLM compliance switches for second release of MDM Server
Functional Usage Styles
69
Foundation
The Foundation functional usage style describes when the MDM Server is
used to store and use party data as an Index, Operational Data Store, or
referential system.
Transaction Hub
The Transaction Hub functional usage style describes when the MDM Server is
used as a system of record in a transactional manner. The Transaction Hub
functional usage style pre-requisites the Platform functional usage style for any
given category of Record.
Types of Records
PARTY
ACCOUNT
PRODUCT
Functional Usage
Styles
Foundation
Transactional Hub
70
Account relationships
Value package management (all
relationship services)
Agenda
Master Data Management Market Update
IBM Multiform MDM Strategy Keep it simple
Introduction to IBM MDM Server v8
Key Supported Features
Implementation Styles
Packaging and Pricing
CDI Entry Level Concept MDM CoreAdvantage
Case Studies
71
72
73
Types of Records
PARTY
ACCOUNT
PRODUCT
Functional Usage
Styles
MDM CoreAdvantage
Foundation
Transactional Hub
74
Account relationships
Value package management (all
relationship services)
75
Information Management
76
Information Management
77
SOLUTION
Phase 1
Phase 2
Phase 3
Implementation
Registry
Registry, Co-existence,
Transaction hub
Transaction hub,
Registry, Co-existence
Function
Operational
Operational,
Collaborative
Operational,
Collaborative
Data
Guest, reservation
Guest, reservation,
preferences
Guest (deep),
reservation, preferences
77
78
Information Management
79
Appendix
Case studies
79
Client Example
80
Phase 1
Phase 2
Phase 3
Implementation
Consolidation
Consolidation, Coexistence
Transaction hub,
Registry, Coexistence
Usage Style
Operational
Operational,
Collaborative
Operational,
Collaborative
Data
Party(Person,
Organization);
D&B data
Party, Account,
D&B data
Party, Account,
D&B data
BUSINESS PROBLEM
SOLUTION
81
Phase 1
Phase 2
Phase 3
Implementation
Registry
Registry, Coexistence,
Transaction hub
Transaction hub,
Registry, Coexistence
Function
Operational
Operational,
Collaborative
Operational,
Collaborative
Data
Guest, reservation
Guest, reservation,
preferences
Guest (deep),
reservation,
preferences
BUSINESS PROBLEM
Phase 2
Implementation
Registry
Function
Operational,
Collaborative
Operational,
Collaborative
Operational,
Collaborative
Data
Person customer,
name, address, ID,
account, data
stewardship
+ privacy
preferences (SOR)
+ Person customer
(deep), account
(reference data),
privacy preferences
82
Phase 3
BUSINESS PROBLEM
Client data fragmented across multiple systems inability to deliver a consolidated view of the customer
Inability to effectively cross sell to customer base
Inability to introduce service differentiation and efficiencies
83
Phase 1
Phase 2
Phase 3
Implementation
Transaction - Retail
Transaction Institutional
Transaction,
consolidation
Function
Operational,
Collaborative
Operational,
Collaborative
Operational,
analytical
Data
Party (deep),
location, account &
claims (reference),
Party (deep),
location, account &
claims (reference),
Party (deep),
location, account &
claims, insight value
scores
BUSINESS PROBLEM
In the process of implementing new web-based ATMs across the entire banking company. Their existing CIF system didnt have the ability to store ATM customer preferences without significant costs for changes
Need to eventually replace core CIF
Integrate with the Banking Data Warehouse for Basel II compliance
Phase 1
Phase 2
Phase 3
Registry,
Consolidation,
registry
Transaction,
consolidation, registry
Operational, analytical,
collaborative
Transaction
Function
Operational
Operational,
collaborative,
Analytical
Data
84
BUSINESS PROBLEM
Customer and policy information scattered across multiple applications and lines of business
Needed to shift operational focus from product-centric to customer-centric
Inefficiencies in sales and back-office systems due to redundant processes
Phase 2
Phase 3
Implementation
Transaction Additional
LOB 50+ apps integrated
where IBM is system of
record
Function
Operational
Operational, Collaboration
Operational,
Collaboration
Data
Party (deep),
account (policy),
product, location
85
BUSINESS PROBLEM
Customer and policy information scattered across multiple applications and business units
Lacked consistent practices for data cleansing and matching with application-independent rules and processes
Need single customer view for web-based account management, privacy management, and improved compliance and cross-selling
86
Phase 1
Phase 2
Phase 3
Implementation
Transaction (new
business)
Transaction, Coexistence
Transaction, Coexistence
Function
Operational,
Collaborative
Operational,
Collaborative
Operational,
Collaborative
Data
Customer (location,
Customer (location,
privacy); Mutual Fund privacy), Org; Mutual
(account)
Fund, Policy
Customer (location,
privacy), Org; Mutual
Fund, Policy
Customer
Success
Business Value
Operational
Customer
Party
Account
Co-existence
Transactional
Account/policy
Operational
Product
Collaborative
Customer
Party
Registry
Transactional
Operational
Guest
Location
Party
Location
Registry
Product
Co-existence
Operational
Collaborative
Customer
Supplier
Hierarchy
Consolidation
Location
Co-existence
Operational
Collaborative
Customer
Account
Party
Registry
Transaction
Collaborative
Product
Location
Supplier
87
Co-existence
Consolidation