The document discusses master data management (MDM) as a critical component for creating a unified view of master data across systems within organizations. It highlights the challenges of inconsistent data, lack of stewardship, and the cost implications of poor data quality, while proposing a master data platform as the solution. The document also outlines the architecture and benefits of using SQL Server MDS for effective data management and processes.

1. Introduction & Overview

2. Mission Critical Platform
CloudServer & Datacenter
Empowered IT Pervasive Insight Dynamic Development
Desktop & Mobile
Information Platform Vision

3. Definitions
• Master Data – Slowly changing reference data shared across systems
• Master Data Management – An application for creating and maintaining an
authoritative view of master data including policies and procedures for access,
update, modification, viewing between systems across the enterprise
People
• Customers
• Vendors
• Sales people
• Employees
• Partners
• Patients
Things
• Products
• Organizational
units
• Recipes
• Parts
• Storage bins
• Documents
Places
• Stores
• Wells
• Power lines
• Geo areas
• Warehouses
Abstract
• Contracts
• Warranties
• Time
• Metrics
• Securities

4. No single, trusted source of the truth
No dimension maintenance capability
Conflicting views of product, customer location, etc
No system to maintain attributes
Multiple stakeholders for the same record
Inability to enforce data stewardship processes
Inconsistencies cost – mistakes, incorrect reports, etc.
Master Data Challenges

5. ERP - USA
ERP - Europe
Warehouse or
analytic app
Operational MDM – Difficulty coordinating multiple systems
Analytic MDM – Difficulty managing dimensions
• Which is the real XYZ Corp?
• Resolve XYZ Corp’s address
• Does product xrb019 = fft019?
• Add 15 attributes to product xrb019
• Information workers can’t edit dimensions
Analytic And Operational MDM
SQL Server MDS – solving for both

6. Align to a single
authoritative source
Master Data Hub
Master Data Platform
Integrate Information
with people and
systems
Stewardship Portal
Stewardship Process

7. Master Data
Platform
Master Data
Hub
Stewardship
Portal
Stewardship
Process
Master Data
Hub
Hierarchy and
attribute
management
Versioning
Transaction
logging
Data quality
and cleansing
Stewardship
Portal
Master data
maintenance
Modeling
Model
documentation
Import and
export
Stewardship
Process
Workflow
Notifications
Business rules
Validation
Master Data
Platform
API support for
all operations
Any domain
Model
deployment
Security
Capabilities

8. Aligning Systems With MDS
MDM
HubMatching
Versioning
Workflow
Role-based Security
Hierarchy Mgmt
Boeing
Master Data
Stewardship
Business Rules
Purchasing
DB
Asset MgmtHR Doc
Boeing Boeing Inc Boeing
(Renton)
Aut_Boeing Boein’

9. MDM Challenges
Where is the real Boeing?
Purchasing
DB
Asset MgmtHR Doc
Boeing Boeing Inc Boeing
(Renton)
Aut_Boeing Boein’

10. MDM Scenarios
MDM
Boeing
Merge/Match
Versioning
Workflow Approval
Role Security
Hierarchy Mgmt
Master Data
Stewardship
Purchasing
DB
Asset MgmtHR Doc
Boeing Boeing Inc Boeing
(Renton)
Aut_Boeing Boein’

11. • An authoritative source
• Central storage and services
– SQL Server database
– WCF API
• May serve as system of entry, system of record, or both
• Any Domain
• Features to support stewardship and integration
Hub

12. Versioning
– Defaults
– Validations
– Actions
Versioning
Transactions
– Data changes
– Annotations
Optimistic member creation
Data quality rules
Hub Capabilities

13. VS Integration
Model
Definition
– APIs for pre-built content
– Model definition and data
Any domain
Model deployment
– Beyond canned domains
– Support unique requirements
APIs for custom interfaces
– Domain specific UIs
– Application integrations
Platform

14. Stewardship Portal
• Master data management
• Model management
• Model documentation

15. Change notification
Bulk extract
Notification
Approval request
MDS
Master Data
Services Layer
Stewardship Portal
Create or change
Data
Warehouse
Master Data
DB Layer
Example Stewardship Process
SharePoint
ERP

16. Case Study: Major Regional Bank
Challenge:
Cumbersome business process to manage
cost centers and accounts impacting
> 10 systems
• Excel-based maintenance
• Point-to-point update flows
• Process based in e-mail
• Expensive and prone to error
Solution:
• Single point of
maintenance (+EDM)
• Process changed to central management
from point-to-point
• Feeds built from MDM to
subscribing systems
Results:
• Consistent dimensions across systems
• 30 person days effort reduced to 2
• Staff reduced from 5 to 3

17. MDS Logical Architecture
Win32 API .NET Framework 3.5
Data Access
Business Logic Business
Entities
Translators (Business Entities ↔ Data Contracts)
Data
Contracts
Service and Message Contracts
Service Adapter
HTTPServer
Logging&
Tracing
Security
WCF Service Implementation
Public WCF Endpoint
Win32
API
.NET
Framework 3.5
Configuration Manager
Configuration Logic
Configuration Library
PowerShell cmdlets
Stewardship UI
Master
Pages
Common
Controls
Code Behinds
ServiceMgmt SharePoint
Server
LOBi Shim
Legend
External Infrastructure
Infrastructure
Business Logic
API
UI
SQL Server 2008 R2
SprocsUDFs
SQL CLR
Subscription Views
Staging Tables
SQLMail
Notifications
Service Broker
Master data
Model metadata
Security data
Audit history

18. © 2014 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.