Transcript John McAllister -- [email protected] Group Program Manager Microsoft Session Code: BIN205 Session Overview What is Master Data and Master Data Management? Introducing Microsoft Master Data.

John McAllister -- [email protected]
Group Program Manager
Microsoft
Session Code: BIN205
Session Overview
What is Master Data and Master Data Management?
Introducing Microsoft Master Data Services (MDS)
Planning MDS Projects
Implementing MDS Projects
What is Master Data and MDM?
Master Data – Key nouns of the business – slow changing – shared across
systems – key to transactional and analytic systems
PEOPLE
• Customers
• Vendors
• Sales people
• Employees
• Partners
• Patients
THINGS
• Products
• Organizational
units
• Recipes
• Parts
• Storage bins
• Documents
PLACES
• Stores
• Wells
• Power lines
• Geographical
areas
ABSTRACT
• Contracts
• Warrantees
• Time
• Metrics
Master Data Management – Software and Processes for creating and
maintaining an authoritative view of master data including policies and
procedures for access, update, modification, and viewing -- between systems
and across the enterprise
Why do you need MDM?
•Add 15 attributes to product xrb019
•Information workers can’t edit dimensions
Warehouse or
Analytic App
ERP - USA
•Resolve XYZ Corp’s Address
•Does product xrb019 = fft019?
•Difficulty coordinating multiple systems
•Difficulty managing dimensions
ERP - Europe
•Or both
Data Platform Vision
Services
Enterprise Data Platform
Reporting
Analysis
Platform For All Data
Dynamic Development
Query
Mobile and
Desktop
Integration
Master Data
FILE
RDBMS
OLAP
XML
Datacenter
Sync
Search
Cloud
Storage
Pervasive Insight
Enabling customers of all sizes to derive value from
ALL data, birth through archival
Introducing Master Data Services
Part of SQL Server 2008 R2
CTP and TAP in second half of 2009
More information at
http://www.microsoft.com/mdm
Introducing Master Data Services
MDS Management & Stewardship Interface
LOB Application
Master Data Services - WCF
Custom Application
WF Workflows
Change Notification
Service Broker
Email Notification
SQL Mail
Bulk Operations
Staging &
Subscriptions
SQL Server 2008 R2
Any application can contribute, any application can consume, process is key
Master Data Services - Features
Demoed Features Other Features
Master Data Portal
Attributes
Hierarchies
Versioning
Model Metadata
Notifications
Workflow
Business Rules
Model Deployment
SharePoint Integration
Integration
Security
Master Data Methodology
Your methodology variant will probably work as well for
MDM as it does for other projects
Pick the right thing to solve
Master Data Management software is only part
of the solution. MDM implementations must
accompany changes in processes, procedures
and policies – this usually can’t happen
overnight
Select a domain and problem set that adds
value and can be leveraged in future phases
MDM Project Drivers
Number of:
Domains (Models)
Entities
Attributes
Hierarchies
Subscribing Systems
Security Profiles
Number and Complexity of Workflow Scenarios
Source Systems
MDM Project Governing Principles
Start small – especially when you are learning
Solve a real problem owned by a sponsor
Scan the horizon, drive to your destination
Engage strong technical resources
Engage knowledgeable business resources
Process is more important than technology
MDM Analysis & Discovery
Environment & Stakeholders
Business drivers
Required integrations
Process – current and desired
Enumerate out-of-scope and nice-to-haves
Common Evolution Pattern
1
1
Master Data
Services
2
LOB App(s)
3
3
Analytic App
3
1. Critical dimension loaded from LOB Apps to MDS and MDS to analytic apps.
Users manage hierarchies and “homeless” attributes in MDS portal
2. Organization recognizes benefits of MDS and begins pushing MDS back to
LOB App.
3. Organization integrates more LOB apps and/or other domains, and more
analytic apps
Deployment & Integration
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should
not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,
IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.