Master Data Management

Transcription

1 Master Data Management Patrice Latinne ULB 30/3/2010

2 Agenda Master Data Management case study Who & services roadmap definition data How What Why technology styles business 29/03/2010 2

3 Why Master Data Management Investments Who How What Why Loans Deposits Cross-Line of Business - Different Regulatory requirements - Different Controls 29/03/2010 3

4 Why Master Data Management Investments Who How What Why Loans Deposits Partner Internet Branch Cross-Line of Business Cross-Channel - Different complexities - Different treatments - Different locations 29/03/2010 4

5 Why Master Data Management Investments Who How What Why Loans Deposits Case history Contact preference Party Partner Internet Branch Cross-Line of Business Cross-Channel Cross-Business Subdomain - Different scopes (of interest, of biz information) - Different subsets 29/03/2010 5

6 Why Master Data Management Investments Who How What Why Loans Deposits Case history Contact preference Party Partner Internet Branch Cross-Line of Business Cross-Channel Cross-Business Subdomain Cross-Application - Different packages (CRM, ERP, SCM, ) - Different technologies (SAP, IBM, Oracle, ) - Different representations 29/03/2010 6

7 Why Master Data Management Organization A Organization B Who How What Why Cross-Line of Business Cross-Channel Cross-Business Subdomain Cross-Application Mergers & Acquisitions - The worse of all inputs 29/03/2010 7

8 Why A big Shift in Enterprise Information Architectures where will play a significant role Who How What Why US Intelligence Community Information Sharing Strategy, produced by the Office of the Director of National Intelligence (DNI), published in February of /03/2010 8

9 IT Both Business Why Strategy Components Provide a Foundation for a Business-IT Partnership Who How What Why Governance/Ownership Business and IT Alignment Business Processes Privacy and Compliance Roadmap/Plan Data Quality Data Stewardship Methodologies Architecture Internal Standards What are we trying to achieve How can the data be used How do we define the data What gets prioritized How do we make data usable for everyone What data can be shared and with whom What data will be addressed when How do we make sure Quality data is available How do we manage our data projects What are the roles and responsibilities What new skills will be necessary What tools/technologies will be necessary How should we organize the data How do we interact with the business 29/03/2010 9

10 IT Both Business Why Technical challenges Who How What Why Governance/Ownership Business and IT Alignment A Proliferation of Data, Stored in Business Processes Privacy and Compliance Roadmap/Plan Data Quality A Proliferation of Databases, Containing A Proliferation of Definitions, Satisfying A Proliferation of Requirements, Accessed by Data Stewardship Methodologies Architecture Internal Standards A Proliferation of Applications, Enabled by A Proliferation of Tools, Yielding A Proliferation of Answers 29/03/

11 Why Summary Who How What Why Web Site Contact Center Enterprise Data Systems Warehouse Root Cause Application functionality and business processes are not designed to manage data for use beyond its own sphere, affecting data integrity, quality and governance Symptom Data is out-of-synch, incomplete, and inaccurate in your applications Business Processes Operational Functions Collaboration Analytics Customer Location Supplier Order Cust. Ship-to Product Business Processes Operational Functions Collaboration Analytics Customer Location Order Business Processes Operational Functions Collaboration Analytics Cust. Ship-to Location Account Order Business Processes Operational Functions Collaboration Analytics Customer Product Product Product Location Supplier Order Analytic/Insight Analytic/Insight Analytic/Insight Analytic/Insight 29/03/

12 Agenda Master Data Management case study Who & services roadmap definition data How What Why technology styles business 29/03/

13 What is Master Data Who How What Why Master Data IS NOT All the data within the enterprise - such as transaction data, billing data, sales data, inventory data, etc. Application-unique data Master Data IS The key facts describing your core business entities: customers, partners, employees, products, bill of materials, list of accounts and locations and the relationships between them The high value information an organization uses repeatedly across many business processes 29/03/

14 position within Information Management Who How What Why Operational / Transactional Applications Decision- Support Systems - BI / CPM - Management Information system 29/03/

15 position within Information Management Who How What Why 29/03/

16 position within Information Management high-level idea Who How What Why Operational / Transactional Applications other data Decision- Support Systems / Management Information system 29/03/

17 How to define a system or discipline Method of Use How are we going to use master data (collaborative, operational, analytical ) Implementation Style How do we architect the solution (registry, coexistence, transaction ) Who How What Why System Domains What master data do we need to manage (customer, product, account ) 29/03/

18 What a question of Style Consolidation Registry Co-existence Transaction Who How What Why Database Function Collaborate Create and Define Data Domain Master Data Management Operationalize Real-time business services Analyze Insight and Analysis Party Product Account Location 29/03/

19 ACCOUNT to LOCATION Relationship CUSTOMER to PRODUCT Relationship What Master Data domains Party can reflect any legal entity, whether individual or organization PARTY PRODUCT Who How What Why Product encompasses both physical goods as well as services Account includes terms and conditions, and associated relationships Agent Customer Employee Prospect Supplier CUSTOMER to ACCOUNT Relationship ACCOUNT Part Product Product Bundle Item/SKU Service Terms & Conditions PRODUCT to LOCATION Relationship LOCATION Location may serve as a primary or secondary domain...not only must these domains be managed but also the relationships among them... Contract Agreement Transaction Reward Program Financial Account Location Address Contact Method Geography/Region 29/03/

20 Who Collaborative How What Why Collaborative Function of : Manages the process of Creating, Defining, and Verifying master data Focused on the definition of Master Data that can be synchronized with Operational and Analytical Systems Function Collaborate Create and Define Master Data Management Operationalize Real-time business services Analyze Insight and Analysis Data Domain Party Product Account Location 29/03/

21 Who Operational Operational Function of : How What Why Use and Maintenance of Master Data occurs within Operational process/applications Master Data is consumed by other systems via real-time accessible SOA Services Function Collaborate Create and Define Master Data Management Operationalize Real-time business services Analyze Insight and Analysis Data Domain Party Product Account Location 29/03/

22 Who Analytical How What Why Analytical Function of : Integration with existing data warehouse & analytics environment to provide master data Inject insight from analytic systems into operational business processes Function Collaborate Create and Define Master Data Management Operationalize Real-time business services Analyze Insight and Analysis Data Domain Party Product Account Location 29/03/

23 Who Consolidation style How What Why Consolidation Consolidation Full data model across multiple data domains Batch import capabilities + Information Server integration Data stewardship and governance functionality Batch export to target systems 29/03/

24 Who Registry style How What Why Registry Registry Index (cross-reference) capabilities for any data entity and attribute Search and inquiry services Capabilities for virtual consolidated view via database server capabilities (federated queries) Data stewardship and matching 29/03/

25 Who Co-existence style How What Why Co-existence Co-existence Full data model across multiple data domains Cross-reference keys, subscription management, and message notification capabilities Search and inquiry SOA services 29/03/

26 Who Transactional style How What Why Transactional 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 29/03/

27 Remember, a question of Style Consolidation Registry Co-existence Transaction Who How What Why Database Function Collaborate Create and Define Master Data Management Operationalize Real-time business services Analyze Insight and Analysis Data Domain Party Product Account Location 29/03/

28 Agenda Master Data Management case study Who & services roadmap definition data How What Why technology styles business 29/03/

29 Who How to implement How What Why roadmap 29/03/

30 Who Programme: Data Maturity Model How What Why 29/03/

31 Who technology: Forrester s analysis How What Why 29/03/

32 Who technology: Gartner s analysis How What Why 29/03/

33 Example of technology IBM WebSphere Information Server Who How What Why Information Server Unified Service Deployment Discover, model, and govern information quality and structure Standardize, merge, and correct information Transform, enrich, place, and synchronize information Virtualize access to disparate information Unified Metadata Management 29/03/

34 Example of technology IBM WebSphere Information Server Information Server Who How What Why Data Administrators DataStage Implementers Architects Subject Matter Experts, Data Stewards Development Data Data Modeling Architect Data Stewardship QualityStage Business Glossary Data Analysts Source System Information Analysis Analyzer Database application and transformation development Metadata and datadriven data modeling and management Business context mapped to information technology assets Data-driven analysis, reporting, monitoring, data rule & integration specification Metadata Server Simplify integration Facilitate change management & reuse Increase compliance to standards Increase trust and confidence in information 29/03/

35 Agenda Master Data Management case study Who & services roadmap definition data How What Why technology styles business 29/03/

36 Case Study of FOD/SPF Economie Who How What Why Energy Consumers Competition Statistics SMEs External competitiveness «Create the conditions for a competitive, sustainable and balanced functioning of the goods and services market in Belgium» Information society Economic prospects Goods and services market Regulations Market surveillance Innovation 29/03/

37 Case Study of FOD/SPF Economie Who How What Why Geography Gender KBO/DBRIS Citizen Enterprise National Registry Legal Form Company type Economic Activity Diverse Reference Data 29/03/

38 Case Study of FOD/SPF Economie: initial state Operational Analytical Who How What Why Queries NIS/INS Survey Data Reference Data Survey Data Reference Data Results Results Queries Survey Data Reference Data Survey Data Reference Data Results Results Survey Data NIS/INS Reference Data Results 29/03/

39 Case Study of FOD/SPF Economie: final situation Who How What Why 29/03/