Principal MDM Components and Capabilities

Transcription

1 Principal MDM Components and Capabilities David Loshin Knowledge Integrity, Inc. 1

2 Agenda Introduction to master data management The MDM Component Layer Model MDM Maturity MDM Functional Services Summary 2

3 The MDM Component Layer Model Business Process Integration Business Rules MDM Business Component Layer Business Process Management Application Integration and Synchronization Service Layer MDM Component Service Layer Integration Record Linkage Identity Search and Resolution Merging and Consolidation Identification Migration Plan Hierarchy Management Identity Management Administration/Configuration Management Data Standards Metadata Management Data Quality Data Stewardship Governance Master Data Model MDM Service Layer Architecture MDM System Architecture Architecture 3

4 Mixing It Up Order of review: 1. Identification 2. Business Process Management 3. Management 4. Governance 5. Integration 6. Architecture 4

5 Identification Every object subject to mastering is managed using a unique representation within the master repository Any time data intended to refer to that object is seen by an application, its unique representation must be found, verified, and presented back to the application by the MDM platform Identity Search and Resolution Record Linkage Merging and Consolidation Identification 5

6 Identity Search and Resolution David Howard Loshin Howard David Loshin Loshin, Howard Objective: Provide the services that will seek the matching record in the master index that represents the queried object 6

7 Record Linkage Parsing and Standardization Parsing Identifying and tagging pieces of each data value within a semantic context Standardization Correcting terms based on defined rules Assembling components into recognized patterns Transformation Rule-based modifications into target canonical representations Transformation into target format Loshin, Howard D First Howard Middle D Last Loshin Howard D Loshin 7

8 Merging and Consolidation Knowledge Integrity, Inc David Loshin David Lotion 1163 Kersey Rd Howard David Loshin Knowledge Integrity Knowledge Integrity Incorporated

9 Business Process Management Business Process Modeling Business Process Integration Business Rules Business Component Layer Business Process Integration Business Rules Business Process Management MDM Business Component Layer 9

10 Mapping to the Business Processes Business Policy Terms Business Objectives Business Policy Business Policy Facts Execution Model Application Application Application Application Application Application Business Policy Business Logic 10

11 Business Rules Business Policy Business rules contribute to the business process model, and can be isolated and managed as enterprise content 11

12 Business Component Layer Services reflecting business process needs create new customer locate matching products find purchase order remove supplier modify vendor status Business layer built on top of business and component object services Business process models document the expected ways in which the business operates The business process model exposes candidate master data objects and the components that use them Business rules traditionally embedded within application code can be extracted and managed as master content as well 12

13 Management Administration/Configuration Hierarchy Management Identity Management Migration Migration Plan Hierarchy Management Identity Management Management Administration/Configuration 13

14 Management Issues Configuration, administration, and ongoing maintenance Identity management: For any object, enough identifying information must be managed to determine that A record exists and no more than one record for the object, or No record exists and one can be created that can be uniquely distinguished from all others Hierarchy management both historical and connectivity Migration management Application MDM 14

15 Governance Data Standards Metadata Management Data Quality Data Stewardship Data Standards Metadata Management Data Quality Data Stewardship Governance 15

16 Master Object Resolution Resolution of candidate master data types requires a compete view of what composes the information architecture This entails cataloging data sets, their attributes, data domains, definitions, contexts, and semantics This view must facilitate the resolution of: Format at the element level, Structure at the instance level, and Semantics across all levels This introduces three challenges: Collecting and analyzing master metadata Resolving similarity in structure Understanding and unifying master data semantics 16

17 Operationalizing Data Governance Actualization of data governance activities enables: The identification of explicit and hidden risks associated with data expectations The actualization of the implementation of business policy Oversight of the definition of critical data elements Monitoring and auditing information quality rule compliance Managing enterprise data ownership and stewardship Coordination and oversight of enterprise data quality In general, data governance provides management oversight for organizational observance of different kinds of information policies 17

18 Stewardship: Remediation and Manual Intervention Issues with addressing data quality events: Immediate remediation of flawed data does this imply data correction? Not all data flaws can be captured via automated processes this implies manual reviews Accuracy may only be measured by comparing values directly Carefully integrate manual intervention when necessary in a controlled manner 18

19 Integration Application integration Synchronization Component services Application Integration and Synchronization Service Layer Integration MDM Component Service Layer 19

20 Application Transition Phase 1 Phase 2 Phase 3 Business Application Business Application Business Application Functional Interface Wrapper Facade Functional Interface Wrapper Facade Service Layer Data Data MDM Repository 20

21 Synchronization and Coherence Federated Issues to consider: Frequency of updates to master object attributes Performance impacts Bottlenecks Attribute overlap Consolidated EAI/EII Master Repository 21

22 Component Service Object Locate Master Index Object Locate Object Factory 22

23 Architecture Master data model MDM system framework Service layer architecture MDM Service Layer Architecture Master Data Model MDM System Architecture Architecture 23

24 Master Data Model Limited universe of common master objects Party, customer, product, part, supplier, claim, instrument Universal models may be suitable as starting points Challenges: Resolution of metadata in a consistent manner Creating a model that accommodates all applications properly CUST First Middle Last Address1 Address2 City State ZIP VARCHAR(15) VARCHAR(15) VARCHAR(21) VARCHAR(45) VARCHAR(45) VARCHAR(30) CHAR(2) CHAR(9) Last VARCHAR(21) Nightingale-Patterson CUSTOMER FirstName MiddleName LastName TelNum VARCHAR(14) VARCHAR(14) VARCHAR(20) NUMERIC(10) LastName VARCHAR(20) Nightingale-Patterso 24

25 Central Master/Coexistence 25

26 Registry 26

27 Transaction Hub 27

28 Architecture - Summary Architecture decisions rely on the requirements identified during the analysis of: Business processes Data requirements Operational processing requirements Levels of coherence and synchronization Governance protocols Component and application services 28

29 Questions? If you have questions, comments, or suggestions, please contact me David Loshin