Upload
embarcadero-technologies
View
222
Download
2
Tags:
Embed Size (px)
Citation preview
Model Confidence for Master Data
2015-05-14
David Loshin
Knowledge Integrity, Inc.
© 2015 Knowledge Integrity, Inc [email protected] (301) 754-6350 1
What is Master Data?
• Master data encompasses the models representing the core business entity objects used in the different applications across the organization, along with their associated metadata, attributes, definitions, semantics, roles, connections, and taxonomies.
• Examples include:
– Customers
– Products
– Parts
– Vendors
– Employees
– Suppliers
– Locations
• Master entity domains are identified in relation to the business context
© 2015 Knowledge Integrity, [email protected](301) 754-6350
2
The Master Data Environment
• A Master Data Environment provides a set of services enabling data consumers with accessibility to a composite view of uniquely identifiable entities
• Requirements are solicited from data producers and data consumers for providing or using master data: – Collecting source information about entities
– Resolving entity identities
– Indexing entity data
– Establishing connections among source data records associated with uniquely identified entities
– Ingesting data from the sources into the master data environment
– Project planning for consuming applications
© 2015 Knowledge Integrity, [email protected](301) 754-6350
3
The Myth of the Golden Record
• Typical pitches for master data management use platitudes to motivate adoption: – “Golden record”
– “360° view of the customer”
– “Single source of truth”
• These concepts are somewhat misleading:– Integration into a single “golden” record implies transformations that
may be inconsistent with operational use
– MDM, by its very nature, cannot be a “source” except under very constrained circumstances
– “Truth,” from a business process and application perspective, is malleable
– Dependencies on structure, intent, semantics, and context cannot be ignored
© 2015 Knowledge Integrity, [email protected](301) 754-6350
4
Master Data Models
© 2015 Knowledge Integrity, [email protected](301) 754-6350
5
• MDM tools often provide data models for common entity types– Person
– Organization
– Item
• A unique entity may participate in different roles across different domains
• Representing the same entity in different master domain repositories may lead to inadvertent duplication!
Patient Provider
and
Vendor-Provided Master Models
• Prepackaged:– Provided by vendor as core part
of MDM product
– Consolidated and filtered views accumulated from previous experiences
– May be “robust” in terms of attribution
– May carry bias of earlier implementations
– Catalog of services “built-in”
© 2015 Knowledge Integrity, [email protected](301) 754-6350
6
The Dimensional Attitude
• We often center attention on a single master data domain at a time
• However, few business processes employ a single master domain
• Most transactions, operations, and analyses touch multiple entity types– Customer buys a product
– Employee is assigned an office location
– Vendor sells a part
– Sales are reported by customer type, product type, region, time frame
• Business processes need access to multiple master domains at the same time
• Therefore, an organization must consider the domains to be incorporated within the master data environment
© 2015 Knowledge Integrity, [email protected](301) 754-6350
7
A Business Data Consumption Approach
© 2015 Knowledge Integrity, [email protected](301) 754-6350
8
Human ResourcesSales
Customer Support
Marketing
Purchasing/Materials
Manufacturing Fulfillment
Accounting/Finance
R & D
Forecasting
IT
Business Functions
Customers Vendors Suppliers Employees Parts Products
Business Entities
Revisiting the Master Entity Model
• Identify potential consumers of master data first
– Assess their data requirements
– Consolidate their data availability, usability, quality expectations
• Business Process Mapping
– Understand cross-functional business processes
– Note touch points for common shared data concepts
– Identify existing models
• Consolidation vs. Consumption?
– Are the uses of shared master data independent of creation? or
– Do the consumers require structurally and semantically aligned models?
• Migration
– Ensure that master models support data and functional interoperability
– Ensure that services support cross-functional processes and enable functional migration
© 2015 Knowledge Integrity, [email protected](301) 754-6350
9
Master Entity Alignment
Customer Product Supplier Vendor Credit Profile Employee
Customer
Read X X X
Product
X
Supplier
Create
Read
Update
X
Vendor
Create
Read
Update
Read
UpdateX
Credit Profile
X
Employee
Create
Read
Update
Create
Read
Update
Create
Read
Update
© 2015 Knowledge Integrity, [email protected](301) 754-6350
10
Modeling Considerations
• Business Model-Driven:
– Begin with your own organization’s concepts and models or
– Guides development of canonical models
– Intended to align with business process architecture
• Achieve enterprise alignment in terms of structural and semantic metadata:
– Data element name
– Data type
– Length/size
– Definition
– Usage scenarios
– Presentation rules
© 2015 Knowledge Integrity, [email protected](301) 754-6350
11
Questions & Suggestions
• www.knowledge-integrity.com
• www.dataqualitybook.com
• www.decisionworx.com
• If you have questions, comments, or suggestions, please contact me
David Loshin
301-754-6350
© 2015 Knowledge Integrity, [email protected](301) 754-6350
12
EMBARCADERO TECHNOLOGIESEMBARCADERO TECHNOLOGIES
ER/Studio XE7 Introduction
Improve Agility and Collaboration in
Your Data Architecture
EMBARCADERO TECHNOLOGIES
Business-Driven Data Architecture
• Improve visibility and collaboration with ER/Studio
• Enable more efficient and automated data modeling
• Share models and metadata across the organization
• Establish business glossaries with consistent terms and definitions
• Build a solid foundation for compliance, data governance, and master data management
14
EMBARCADERO TECHNOLOGIES
Introducing ER/Studio XE7
• Innovation– Agile Change Management
Tasks and UI
• Team Server Enhancements– Glossary Hierarchies with
Inheritance– Detailed Audit Trail for
Glossaries and Terms– Improved CSV Import– Improved Advanced Search
• Increased ER/Studio Platform Interoperability– Glossary Integration to
Data Architect– Data Source Mapping and
Impact Analysis
• Usability improvements – Data Architect Welcome
Page – Automated Naming
Standards– Multi-version Licenses
16
EMBARCADERO TECHNOLOGIES
Glossary Inheritance
• Similar to ER/Studio submodels• Child glossaries inherit a subset
of parent terms• May have one or more
parent glossaries• No limit to hierarchy level
20
EMBARCADERO TECHNOLOGIES
Glossary Integration
• Associate ER/Studio Data Architect objects to Team Server glossary terms
– Model, submodel
– Entity, Table
– Attribute, Column
– Domain
– View
• Push terms to glossary
21
EMBARCADERO TECHNOLOGIES
Additional Glossary Enhancements
• Change history / audit trail
• Export/Import
– To/from workbooks
22
EMBARCADERO TECHNOLOGIES
Advanced Search
• Available in Team Server / Enterprise Team Edition• Improved search criteria for data objects, data sources, glossaries,
and terms
22
EMBARCADERO TECHNOLOGIES
Agile Change Management
• Enable “Agile Data Modeler”
– Incremental rather than waterfall
• Need more granularity than named versions of a model or submodel
• Change numbers assigned at Repository check-in (or check-out)
– Can be associated to user stories, tasks
24
EMBARCADERO TECHNOLOGIES
Thank you for your interest!
• Learn more about the ER/Studio product family: http://www.embarcadero.com/data-modeling
• Trial Downloads: http://www.embarcadero.com/downloads
• To arrange a demo, please contact Embarcadero Sales: [email protected], (888) 233-2224
29