9. Approaches to MDM Matches and physically stores a consolidated view of master data Updated after the event and not guaranteed up-to date. Authoring remains distributed No publish and subscribe. Not used for transactions, but could be used for Reference For Reporting, Analysis and Central Reference Consolidation Registry Coexistence Transaction Matches and links to create a "skeleton" system of record Physically stores the global ID, links to data in source systems and transformations Virtual consolidated view is assembled dynamically and is often read-only. Authoring remains distributed Registry Mainly for Real-Time Central Reference Matches and physically stores consolidated view of master data Updated after the event and not guaranteed up to date. Authoring remains distributed Publishes the consolidated view. Not usually used for transactions, but could be used for reference Coexistence For Harmonization Across Databases and for Central Reference Matches and physically stores the up-to-date consolidated view of master data Supports transactional applications directly — both new and legacy — typically through service oriented architecture interfaces Central authoring of master data Transaction Acts as System of Record to Support Transactional Activity
10.
11. MDM Location in Enterprise Architecture Business Process Layer ODS Customer Profile Data Mart Business Intelligence MRD Authoring instance Application & Data Service Channels Billing System Campaign Management 3 rd Party Data CDW UI for MRD Integration Layer Information Integration Infrastructure Data Quality ETL Staging Area Source system Interface Layer Business Rules Operational Data Store Staging area for transformation and consolidation Self Service Customer Portal Reports / Dashboards Inbound Contact channels Agent App IVR Master Data Hub Business Events UI / Access Manager MRD Transaction instance Customer Hub Service Layer Business services Business Process Composition Business Process Orchestration Data services EAI EII Governance and Security Metadata
12. MDM Reference Architecture Data Rules Engine Rules of Visibility Security Business Services Matching Engine Rules for suspect processing Validation Engines Transaction Audit Log Data Standardiza tion tools Workflow Management Engine Central Hub Interface for Configuration both real time and batch Data Warehouses & BI applications External marketing database Key Operation Systems: CRM, SFA etc . Data Stewards
13.
14.
15.
16.
17.
18.
19.
20.
21.
22. Customer Master Profile - Reference Data Customer-centric Cross reference keys History/Audit Data base Account Cross Reference Keys Last Update Date & User Source System Data Transaction Audit Log Data Decay Meta Data Effectivity Dating Application Meta Data
23. WebSphere Customer Center - Multiple Input, Multiple Output Design Input key = Contract key Request – inbound message Add New Contract (Account) Contract ABC Data Contract component data Party profile Location Data Identifier Data Contract 12345 Contract Component A Contract Component B Role: Account Owner Home Address Identifier Party: Jane Smith Example – Build a party-centric master with account-centric processes
25. Business Service Interface – Overview Interface Layer XML Interface Web Services Java Object Batch Transaction Processor Event Manager / Evergreen IBM WBI WebSphere Customer Center XML File Formats Real-time Batch WebSphere Customer Center Central Transaction Server WebSphere Customer Center Fast Track Transaction Server COBOL Adapter CICS Interface Messaging Adapter Composite Transaction Framework XML COBOL Copybook Flat File Customer Parser Custom Constructor Adapters / Interfaces Message Queue Notification Framework Request Response
26.
27.
28.
29.
30.
Editor's Notes
Please Note: This .pot file has been created in PowerPoint 2002 and is a Design Template which provides you the “look” of the presentation Applying the template to your existing presentation: You apply a .pot file by opening the Task Pane with View > Task Pane and select Slide Design – Design Templates. Click on the word Browse… at bottom of Task Pane and navigate to where you stored the template then click Apply. Starting with a Blank Presentation and switching to the desired Design Template: Start a new presentation as Blank Presentation You can switch to the desired template by opening the Task Pane with View > Task Pane and select Slide Design – Design Templates. Click on the word Browse… at bottom of Task Pane and navigate to where you stored the template and click Apply. Changing background color of your existing presentation: You can switch between black and white backgrounds in your presentation by navigating to that .pot file and click Apply. Changing templates 1. You can switch templates from within this file by opening the Task Pane, select Slide Design – Design Templates and selecting the other master that is used in this presentation. Printing your presentation on a black and white printer Send file to print in "Grayscale" mode – which is the default setting in the print dialogue box Analyze printout. If some text is not readable due to being on a gray background, switch "Grayscale" to "Pure Black and White" and reprint. This would solve 80% of your print problem. Analyze printout again and if specific image areas are still not printing properly, select View / Color / Pure Black and White / and click on the problem image object. On the floating Grayscale toolbar, under Setting, select the appropriate choice for correct printing. This would solve the other 20% of your print problem.
![Objectives ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)