Download

1,634 views
1,529 views

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,634
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
119
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Most people can easily identify the symptom – data is fragmented across business applications – it’s inaccurate, incomplete, and in conflict with data in other systems It’s not as easy to identify the root cause – but it is the functionality of the applications themselves that cause this problem. No one application is aware of how other applications consume the data it uses – it doesn’t have the business logic and function to manage data at an enterprise level. Therefore it adds and updates data profiles based on its narrow set of rules, and does share data with other applications – and that is why data gets out of synch and is inaccurate.
  • In order to solve this problem you cannot address the data alone – you must address the functionality that corrupts the data in the first place in order to completely solve the MDM problem.
  • MetLife – Case Study A Major Retailer – Source, “How to Sell Business Value in Master Data Management” – Dan Vanhammond Telco - BellCan Case Study
  • Uniform MDM - -Single Style-Single Domain-Supporting Reference data for primary domain Uniform MDM Suite - -Collection of Uniform MDM Solutions without integration Multiform MDM Stg I - -Multiple and separate platforms for A/C/O MDM Multiform MDM Stg II -- -Common/ Integrated Platform for A/C/O MDM-Function in at least one style across domains-Function between styles
  • Key points for this slide Logo, and Market Growth Slide. Market Graph to be replaced by Forrester’s recent study when available (Released March 6 th ) Based on the Market growth in the MDM space, IBM is making large investments in the area of Information, with $1.5B in acquistions thus far.
  • Story – MDM is a biz strategy with IT deliverables, and many clients begin in different points to end up at the same end-state – different usage and domains Point – These clients have been highly successful precisely because they qualifiedwhere to begin and delivered short-term, high profile projects Benefit – There is a proven and successful implementation methodology that ties MDM deliverables to your business case – e.g., you may start with privacy because it is a pressing issue that results in cost avoidance, and customer satisfaction increase Key points for this slide Clients often begin with one dominant usage style and grow the number of data domains from one primary to one or more primaries and multiple secondaries. Next step is to introduce multiple usage styles – some clients have reached that stage already. Many clients are “doing MDM” today and no one is doing exactly the same thing – some start with one domain, one style, some have multiple styles and 1 or 2 domains, some have one style and several domains – the deployment of MDM is unique to your business requirements and your business case, but you want a vendor that is capable of addressing the entire MDM requirement set because you will grow into additional usage over time – if you start with the wrong vendor you will not be able to leverage it later across a broader MDM deployment – and that is where the greatest value is realized (relationships across domains, linkage of usage styles to trigger actions)
  • http://www.dmreview.com/article_sub.cfm?articleId=1068002 http://www.cioinsight.com/article2/0,1540,1965749,00.asp
  • http://www.dmreview.com/article_sub.cfm?articleId=1068002 http://www.cioinsight.com/article2/0,1540,1965749,00.asp
  • Download

    1. 1. Master Data Management An Introduction Igor G Gonchar, Executive IT Architect InfoSphere Acceleration Team IBM Software Group WW Sales Office: +1-215-396-2893 Mobile phone: +1-215-681-6053 e-mail: igonchar@us.ibm.com
    2. 2. IBM Multiform Master Data Management The Application Process and Function Problem Symptom Data is inaccurate, incomplete and conflicts with other systems Root Cause Common data and data function is siloed Data and data functionality common to applications: Customer, Account, Product CRM Billing ERP Data and Functionality unique to each application Application-unique Functionality & Data Common Functionality & Data Application-unique Functionality & Data Common Functionality & Data Application-unique Functionality & Data Common Functionality & Data
    3. 3. IBM Multiform Master Data Management The Application Process and Function Problem CRM Billing ERP eBusiness Application Common Data = Master Data Common Functionality & Data Master File Application-unique Functionality & Data Common Functionality & Data Application-unique Functionality & Data Common Functionality & Data Application-unique Functionality & Data Common Functionality & Data Application-unique Functionality & Data
    4. 4. IBM Master Data Management Industry Models & Assets Collaborate Operationalize Analyze Party (Customer, citizen, prospect, organization, supplier, distributor, etc.) Product (good, service, product bundle, catalogue, product component, etc.) Account (Agreement, financial account, reward program, etc.) <ul><li>Multiform MDM is: </li></ul><ul><ul><li>Multi-Style: Collaborative, Operational, Analytical </li></ul></ul><ul><ul><li>Multi-Domain: Product, Customer, Account </li></ul></ul><ul><li>Multiform Value Delivered Through: </li></ul><ul><ul><li>Matching Styles to Consumer Usage </li></ul></ul><ul><ul><li>Linkage of Data Domains </li></ul></ul><ul><li>Multiform MDM Functionality: </li></ul><ul><li>Manages domains that have a significant impact on business processes </li></ul><ul><li>Realizes the promise of SOA </li></ul><ul><li>Configurable Functionality Out-of-the-Box </li></ul><ul><li>Manages the complete Data Lifecycle </li></ul>Define, create and synchronize Master Information Deliver Master Information as a Service for business operations Drive real time business insight Common Function = MDM Style Common Data = Master Data IBM Multiform Master Data Management The Broad Functionality across master data domains
    5. 5. Focused On Critical Information Intensive Business Problems IBM Master Data Management Solutions Banking Insurance Government Healthcare Retail Telco IBM Master Data Management Collaborate Operationalize Analyze Party (Customer, citizen, prospect, organization, supplier, distributor, etc.) Product (good, service, product bundle, catalogue, product component, etc.) Account (Agreement, financial account, reward program, etc.) Define, create and synchronize Master Information Deliver Master Information as a Service for business operations Drive real time business insight Common Function = MDM Style Common Data = Master Data Industry Models & Assets
    6. 6. IBM Multiform Master Data Management Multiform MDM manages data domains critical to business processes Multiform MDM leverages merged, cleansed and standardized data via the Information Server Industry Models & Assets Understand Cleanse Transform Deliver Discover, model, and govern information structure and content Standardize, merge, and correct information Combine and restructure information for new uses Synchronize, virtualize and move information for in-line delivery Unified Deployment IBM Information Server Unified Metadata Management Parallel Processing Rich Connectivity to Applications, Data, and Content IBM Master Data Management Collaborate Operationalize Analyze Party, Product, Account Define, create and synchronize Master Information Deliver Master Information as a Service for business operations Drive real time business insight
    7. 7. IBM Multiform Master Data Management Multiform MDM manages data domains critical to business processes Multiform MDM leverages merged, cleansed and standardized data via the Information Server Focused on critical information intensive business problems Understand Cleanse Transform Deliver Unified Deployment IBM Information Server Unified Metadata Management Parallel Processing Rich Connectivity to Applications, Data, and Content IBM Master Data Management Banking Insurance Government Healthcare Retail Telco Industry Models & Assets IBM Master Data Management Collaborate Operationalize Analyze Party, Product, Account
    8. 8. Business value of MDM <ul><li>Multiform MDM delivers the functionality to manage key business facts that have a significant impact on the most important business processes, allowing the organization to: </li></ul><ul><li>Increase Revenue and Customer Retention </li></ul><ul><li>Leverage cross-sell and Up-Sell opportunities </li></ul><ul><li>Identify the most valuable customers to provide differentiated service </li></ul><ul><li>Cost Reduction and Avoidance </li></ul><ul><li>Introduce New Products more quickly reducing time to market </li></ul><ul><li>Streamline and automate business processes for greater effieciency </li></ul><ul><li>Increase Flexibility to Support Existing and new Business Strategy </li></ul><ul><li>Meet the dynamic requirements of the buisness with an SOA architecture </li></ul><ul><li>Support New Strategic initiatives such as M&A with an integrated framework </li></ul><ul><li>Meet Compliance Requirments and Reduce Risk Exposure </li></ul><ul><li>Capture and manage net new elements such as Privacy Preferences </li></ul><ul><li>Proactivley uncover and action fraud risk </li></ul>
    9. 9. A Large North American Telco... A Major US Health Plan... <ul><li>Identified 2,328 Instances of SSNs associated with multiple DOBs, names and/or genders </li></ul><ul><li>186,725 Instances where a member number was shared by multiple individuals </li></ul><ul><li>Calculated Cumulative Benefits of $62.8M: </li></ul><ul><li>Enhanced Customer Insight incremental revenues and retention totalling over $47M </li></ul><ul><li>Channel, Communication and Billing savings totalling over $14M </li></ul>A Major US Retailer... <ul><li>Has added a true multi-channel capability increasing customer acquisition rates, conversion rates, repeat sales and basket size </li></ul><ul><li>Conservative estimates of total impact is a 5 year net benefit of $37M </li></ul>Value Realized Through MDM Deployments A Leading Financial Services Company... <ul><li>Integrated over 50 applications leading to: </li></ul><ul><li>Increased Sales Opportunity, Improvements in Customer Service, Differentiation in Client Management and reduction in IT costs </li></ul><ul><li>Leading to over $40M in benefit quantification </li></ul>
    10. 10. Top-5 US Credit Card Issuer... Major Pharmaceutical Company... <ul><li>$8.4M+ in Annual Direct Labor Cost Savings across Operations, Sales, Finance and Distribution </li></ul><ul><li>$1.7M in Other IT Related Cost Savings Annually </li></ul><ul><li>Expects $7.34M in recovered Revenues </li></ul><ul><li>Calculated 473% ROI based on Computing and Operations Efficenciencies </li></ul><ul><li>Yielded payback in under 12 Months </li></ul>A Leading Electronics Manufacturer... <ul><li>Has reduced time for creating and maintaining Product Information by 10% and reduced errors by 5%, resulting in savings of £ 5M per annum </li></ul><ul><li>Increased speed to market resulting in a 3.5% increase in Revenue </li></ul>Major Technology Manufacturer... <ul><li>Funded an independent study confirming expected revenue growth of $40M due to: </li></ul><ul><li>Identification of net new opportunities, improved win rates </li></ul><ul><li>Ability to develop strategic pricing activties and increase customer focus </li></ul>Value Realized Through MDM Deployments (cont’d)
    11. 11. Evolution of MDM Applications MDM Functional Maturity Evolution of Complete Multiform MDM Offering Multiform MDM II Multiform MDM I Uniform MDM Suite Uniform MDM Index Multi-Domain Index Single Domain 1 Style 1 Domain Fully integrated multi-domain, multi-style Platform for single style that supports multiple domains +1 Uniform Solns Reference1+ Domain Reference1 Domain Reference Single Domain Reference Multi-Domain Data-Centric Approach Function-Centric Approach MDM Application MDM Tool Evolution Chasm Evolution Chasm
    12. 12. Evolution of MDM Applications MDM Functional Maturity Evolution of Complete Multiform MDM Offering Data-Centric Approach Function-Centric Approach MDM Application MDM Tool Evolution Chasm Multiform MDM Uniform MDM Reference MDM Index MDM Multi Domain Index Multi Domain Reference Multi Domain Uniform Integrated Platform Single Domain Index Single Domain Reference Single Domain Uniform Multiple Separate Platforms
    13. 13. Analyst Validation Gartner Magic Quadrant For PIM 2005 Forrester Wave for CDI Gartner Magic Quadrant For Data Integration Tools 2006 Gartner Magic Quadrant for CDI Hubs 2006 Source: Gartner, Inc. “Magic Quadrant for Customer Data Integration Hubs, 2Q06” by John Radcliffe. May 26, 2006. This Magic Quadrant graphic was published by Gartner, Inc. as part of a larger research note and should be evaluated in the context of the entire report. The Gartner report is available upon request from IBM. The Magic Quadrant is copyrighted May 2006 by Gartner, Inc, and is reused with permission. The Magic Quadrant is a graphical representation of a marketplace at and for a specific time period. It depicts Gartner’s analysis of how certain vendors measure against criteria for that marketplace, as defined by Gartner. Gartner does not endorse any vendor, product, or service depicted in the Magic Quadrant, and does not advise technology users to select only those vendors placed in the “Leaders” quadrant. The Magic Quadrant is intended solely as a research tool, and is not meant to be a specific guide to action. Gartner disclaims all warranties, express or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. <ul><ul><ul><li>Source: “Magic Quadrant for Product Information Management, 2005” Gartner ID: G00139227, Andrew White, Published on 16 May 2006 </li></ul></ul></ul><ul><ul><ul><li>Source:”Magic Quadrant fo rData Integration Tools, 2006 Gartner ID: G00141484 </li></ul></ul></ul>
    14. 14. IBM Master Data Management Forrester - Global Adoption of MDM by Region
    15. 15. Forrester: A new view on the players converging on master data management solutions Infrastructure players End-user focused solutions Intelligent consumption Transactional maintenance Enterprise Apps Data management BI/action frameworks * Oracle * SAP * Oracle – Siebel * IBM * Siperian * Initiate Trusted data sources * Purisma * D&B * VisionWare * Acxiom * SAS (DataFlux) * Sun (See Beyond) Master data hub * Cordys * InfoUSA * GoldenSource * Hyperion * Business Objects * Cognos * i2 * Lexis-Nexis * Tibco * Amdocs * Kalido * Trillium * Group 1 * GXS * FullTilt
    16. 16. What We Provide for Our Customers Initial MDM Deployment Business Value Business Driver Customer Success Usage Domain New product introduction Customer Care Enhanced new product introduction and supplier management Customer care Location Product Enhanced customer service across all channels, integration of customer profile within account opening process Customer Care Hierarchy Location Enhanced sales and executive planning via complete relationship understanding of customers and suppliers Customer care Operational Customer Party Account/policy Product Streamline new business process to increase revenue and retention New product introduction Collaborative Product Item Supplier Vendor Customer Enhanced new product introduction and item maintenance process to increase revenue Integrated Content Mgmt Collaborative Operational Product Supplier Operational Customer Account Collaborative Operational Customer Supplier Threat and Fraud Analytical Traveler Location Crew Member Significant improvement in accuracy of matching names resulting in improved security
    17. 17. Business Value, defined by Analysts “ <MDM’s> alignment of technology, process, and governance allows information and knowledge management professionals to get to that elusive goal of creating a trusted version of critical enterprise data.” – Forrester, Demand for Master Data Management Software is Timid but Growing Steadily Through 2010, March 2007 <ul><li>83% of organizations suffer from poor Master Data – TDWI, November 2006 </li></ul><ul><li>Master Data...problems have contributed to poor customer service and inefficient marketing – TDWI, November 2006 </li></ul>“ Without a single view of ... customers, organizations are in the dark and cannot effectively retain customers, cross-sell to them, deliver the right customer experience to them or manage the risk associated with them.” – Gartner, Market Share and Forecast: CDI Hub Software, December 2006 Master Data Management “is yeilding a 25 percent improvement in top and bottom line benefits for the enterprises.” – Yankee Group , 2005
    18. 18. Business Value, defined by Customers <ul><li>“ Time-to-market has been significantly improved, and the amount of time required for creating and maintaining product information has been reduced by 50 percent.” – Case Study: Panasonic Searches the Master Data for the Single Version of the Truth, May 2006 </li></ul><ul><li>“ Panasonic Europe expects to save a million euros a year as a result <of IBM’s MDM>. The group also projects a 3.5 percent increase in sales, thanks to that faster time-to-market.” – Case Study: Panasonic Searches the Master Data for the Single Version of the Truth, May 2006 </li></ul><ul><li>“ We’re also able to ensure the security and privacy of client information. Our service oriented architecture has enabled us to migrate to a layered architecture, for flexibility, ease of maintenance and reduced development time. This helps us continue to derive benefits well into the future.” </li></ul><ul><li>– Case Study: The Cooperators Group share revenue, savings with IBM’s WebSphere Customer Center, May 2007 </li></ul><ul><li>“ We expect to remove one week of processing time for adding a new item because we are moving from a linear process....to a process in which information flows to multiple groups at one time.” </li></ul><ul><li>– Case Study: West Marine, November 2005 </li></ul><ul><li>“ As part of the implementation, we had to look at more than eight major databases and over 60 process functions, ....Having those systems talk to one single system instead of each other puts us years ahead of where the system was.” </li></ul><ul><li>– Case Study: West Marine, November 2005 </li></ul><ul><li>“ Even though we have fewer customers than large consumer-facing organizations, these customers are large complex companies with many locations and branches, and we needed a product that could handle this complexity,” – Business Intelligence Network, Master Data Management Research Report, 2006 </li></ul>
    19. 19. Selected MDM Customers Insurance & Financial Services Banking & Financial Services
    20. 20. Selected MDM Customers Retailers & Distributors Manufacturers & Service Providers Boulanger
    21. 21. <ul><li>Architectural Decisions: </li></ul><ul><li>The LOB system that receives the new Customer Data will first apply it’s business logic and persist the data to its transactional database before invoking MDM services. </li></ul><ul><ul><li>The Level of Effort may be too high to change the existing application business logic to invoke MDM services as part of a business transaction (logical unit of work) prior to committing the results to its database. </li></ul></ul><ul><li>WebSphere QualityStage will provide name and address standardization and probabilistic matching for WCC. </li></ul><ul><ul><li>In Scenario 1A WebSphere QualityStage will standardize and cleanse the name and address information and perform probabilistic matching to determine if the customer is unique or an existing customer. </li></ul></ul><ul><ul><li>The scenario shows using the WCC-QS Adapter invoking the QSRT Client API to communicate with the QualityStage Server </li></ul></ul><ul><li>In Scenario 1B WebSphere QualityStage will call GNR NameParser to standardize the name information as part of the Data Quality Management process for WCC. </li></ul><ul><ul><li>When performing the initial load of WCC, the ETL process must then call GNR NameParser to utilize the same name standardization logic. </li></ul></ul>Deployment Scenario 1: Add New Customer with Cross-Sell
    22. 22. <ul><li>Architectural Decisions: </li></ul><ul><li>The LOB system that processed the original update will receive a cleansed and standardized version of the same Master Data for processing. </li></ul><ul><ul><li>Implement logic so as to not create a continuous loop between the originating system and the Master Data Management Services. </li></ul></ul><ul><ul><li>There will need to be a compensation process to resolve duplicate customers in the originating system if this happens to be an existing customer. </li></ul></ul><ul><li>The use of messaging provides a mechanism to support both synchronous and asynchronous processing to receive updates by WCC and distribute updates to subscribing systems. </li></ul><ul><ul><li>The use of messaging provides the ability for a LOB system to process the updates based upon its latency requirements such as immediate upon publication or on a scheduled basis and to not loose information when unavailable during a planned or unplanned outage. </li></ul></ul>Deployment Scenario 1: Add New Customer with Cross-Sell
    23. 23. <ul><li>A LOB user updates new customer life insurance policy information through a portal user interface to a LOB system. The LOB system validates the data, applies any business logic and persists the data to its transaction database. </li></ul><ul><li>The LOB system creates a WCC XML request/response message with the customer and policy information to request a WCC add party transaction. The LOB system posts the request message to a MQ message queue. </li></ul><ul><li>WCC retrieves the MQ message and invokes the WCC service to process the new customer data and policy information. </li></ul><ul><li>WCC formats the business object and invokes a WebSphere QualityStage service via the QSRT Client Real-Time Interface (RTI) for the QualityStage Server that performs customer name and address cleansing and standardization. </li></ul><ul><li>WebSphere QualityStage cleanses and standardizes the name and address information. </li></ul>4 3 1 2 Scenario 1A : Add New Customer with Cross-Sell 5 Transaction Data LOB Systems Data Rules Services Business Process Data Policy Data User Registry Policy Data User Registry Rules WebSphere Enterprise Service Bus Database Server Transaction Data Database Server LOB Systems Firewall Metadata WebSphere Customer Center Customer Master Data Reference Data DB2 UDB Server Customer History Data DMZ WAS for ND Firewall eNetwork Dispatchers Firewall Tivoli Access Manager WebSeal TAM (Master) TAM (Read-Only) External Data Providers LOB Browser U.I. IBM HTTP Server w/Redirector Plug-in WebSphere Portal HTTPS HTTPS WebSphere Services Registry & Repository WebSphere Process Server 3 MQ / JMS / XML JDBC MQ (Subscribe) SOAP/ HTTPS aznAPI aznAPI MQ/ JMS / XML (Publish) Transaction Data WebSphere QualityStage 1 5 SOAP / HTTPS 2 MQ / XML 11 13 12 10 10 8 11 16 LOB Systems 1 4 7 6 9 Telemarketing System 14 Database Server Transaction Data 15 MQ MQ / JMS / XML 17 18 19 1 10 11 SOAP/ HTTPS 11 WCC-QS Adapter QSRT (RTI) Data Stewardship U.I. QSRT (RTI) HTTPS
    24. 24. <ul><li>WebSphere QualityStage returns the standardized name and address results to WCC. </li></ul><ul><li>WCC receives the standardized name and address from QualityStage. WCC queries the WCC Database to retrieve candidate names, creates the business object and invokes a QS probabilistic matching service via the QSRT Client. </li></ul><ul><li>WebSphere QualityStage performs probabilistic matching against the candidate names received in the request from WCC. </li></ul><ul><li>QualityStage returns the scoring results to WCC which indicates that this is a new customer. </li></ul><ul><li>WCC creates and submits a web service request/response to an external data provider for data enrichment. </li></ul><ul><li>The External Data Provider receives the query request and performs the query request. The External Data Provider returns the results to WCC. </li></ul>Scenario 1A : Add New Customer with Cross-Sell 6 7 8 9 10 11 Transaction Data LOB Systems Data Rules Services Business Process Data Policy Data User Registry Policy Data User Registry Rules WebSphere Enterprise Service Bus Database Server Transaction Data Database Server LOB Systems Firewall Metadata WebSphere Customer Center Customer Master Data Reference Data DB2 UDB Server Customer History Data DMZ WAS for ND Firewall eNetwork Dispatchers Firewall Tivoli Access Manager WebSeal TAM (Master) TAM (Read-Only) External Data Providers LOB Browser U.I. IBM HTTP Server w/Redirector Plug-in WebSphere Portal HTTPS HTTPS WebSphere Services Registry & Repository WebSphere Process Server 3 MQ / JMS / XML JDBC MQ (Subscribe) SOAP/ HTTPS aznAPI aznAPI MQ/ JMS / XML (Publish) Transaction Data WebSphere QualityStage 1 5 SOAP / HTTPS 2 MQ / XML 11 13 12 10 10 8 11 16 LOB Systems 1 4 7 6 9 Telemarketing System 14 Database Server Transaction Data 15 MQ MQ / JMS / XML 17 18 19 1 10 11 SOAP/ HTTPS 11 WCC-QS Adapter QSRT (RTI) Data Stewardship U.I. QSRT (RTI) HTTPS
    25. 25. <ul><li>WCC assigns a unique PartyId, enriches the data with data from the External Data Provider and persists the customer and policy data to the WCC database. </li></ul><ul><li>Based upon the customer’s privacy preference, WCC queries marketing campaign information in the WCC database and determines that the customer meets the income criteria for a marketing campaign and can be contacted. </li></ul><ul><li>WCC generates a XML message and posts the XML message via JMS to a MQ message queue. WebSphere Enterprise Service Bus translates the XML message based upon message transformation rules to the format recognized by the Telemarketing System. </li></ul><ul><li>The Telemarketing System MQ listener retrieves the message and performs any logic such as notification, scheduling etc. </li></ul>Scenario 1A : Add New Customer with Cross-Sell 12 13 14 15 Transaction Data LOB Systems Data Rules Services Business Process Data Policy Data User Registry Policy Data User Registry Rules WebSphere Enterprise Service Bus Database Server Transaction Data Database Server LOB Systems Firewall Metadata WebSphere Customer Center Customer Master Data Reference Data DB2 UDB Server Customer History Data DMZ WAS for ND Firewall eNetwork Dispatchers Firewall Tivoli Access Manager WebSeal TAM (Master) TAM (Read-Only) External Data Providers LOB Browser U.I. IBM HTTP Server w/Redirector Plug-in WebSphere Portal HTTPS HTTPS WebSphere Services Registry & Repository WebSphere Process Server 3 MQ / JMS / XML JDBC MQ (Subscribe) SOAP/ HTTPS aznAPI aznAPI MQ/ JMS / XML (Publish) Transaction Data WebSphere QualityStage 1 5 SOAP / HTTPS 2 MQ / XML 11 13 12 10 10 8 11 16 LOB Systems 1 4 7 6 9 Telemarketing System 14 Database Server Transaction Data 15 MQ MQ / JMS / XML 17 18 19 1 10 11 SOAP/ HTTPS 11 WCC-QS Adapter QSRT (RTI) Data Stewardship U.I. QSRT (RTI) HTTPS
    26. 26. <ul><li>WCC creates the XML transaction response message and posts the results indicating that this new customer was processed successfully to a MQ queue for the originating LOB system to retrieve from the queue. </li></ul><ul><li>The originating LOB system retrieves the MQ message in the XML response format and based upon its business logic, updates the customer information in its database from the results contained in the WCC response. </li></ul><ul><li>WCC constructs a XML message with the new customer information and posts the message to an MQ Queue for publishing the new customer data. WebSphere ESB converts the XML message to the specific message format required for each LOB system and routes it to each LOB system MQ queue that matches the subscription topic. </li></ul><ul><li>LOB systems retrieve the message with the new customer and account information and process it according to the business rules for updating their transactional database. </li></ul>Scenario 1A : Add New Customer with Cross-Sell 16 17 18 19 Transaction Data LOB Systems Data Rules Services Business Process Data Policy Data User Registry Policy Data User Registry Rules WebSphere Enterprise Service Bus Database Server Transaction Data Database Server LOB Systems Firewall Metadata WebSphere Customer Center Customer Master Data Reference Data DB2 UDB Server Customer History Data DMZ WAS for ND Firewall eNetwork Dispatchers Firewall Tivoli Access Manager WebSeal TAM (Master) TAM (Read-Only) External Data Providers LOB Browser U.I. IBM HTTP Server w/Redirector Plug-in WebSphere Portal HTTPS HTTPS WebSphere Services Registry & Repository WebSphere Process Server 3 MQ / JMS / XML JDBC MQ (Subscribe) SOAP/ HTTPS aznAPI aznAPI MQ/ JMS / XML (Publish) Transaction Data WebSphere QualityStage 1 5 SOAP / HTTPS 2 MQ / XML 11 13 12 10 10 8 11 16 LOB Systems 1 4 7 6 9 Telemarketing System 14 Database Server Transaction Data 15 MQ MQ / JMS / XML 17 18 19 1 10 11 SOAP/ HTTPS 11 WCC-QS Adapter QSRT (RTI) Data Stewardship U.I. QSRT (RTI) HTTPS
    27. 27. <ul><li>A LOB user updates new customer life insurance policy information through a portal user interface to a LOB system. The LOB system validates the data, applies any business logic and persists the data to its transaction database. </li></ul><ul><li>The LOB system creates a XML message in the WCC XML request format containing the customer and policy information to request a WCC add party transaction. The LOB system posts the request message to a MQ message queue. </li></ul><ul><li>WCC retrieves the MQ message and invokes the WCC service to process the new customer data and policy information. </li></ul><ul><li>WCC formats the business object and invokes a WebSphere QualityStage service via the QSRT Client Real-Time Interface (RTI) for the QS Server that performs customer name and address cleansing and standardization. </li></ul><ul><li>WebSphere QualityStage cleanses and standardizes the non-name information such as address and telephone number. </li></ul>4 3 1 2 Scenario 1B : Add New Customer with Cross-Sell (GNR) 5 Metadata Data Rules Business Process Data Policy Data User Registry Policy Data User Registry Rules WebSphere Enterprise Service Bus Firewall WebSphere Customer Center Customer Master Data Reference Data DB2 UDB Server Customer History Data DMZ WAS for ND & WebSphere MQ Firewall eNetwork Dispatchers Firewall Tivoli Access Manager WebSeal TAM (Master) TAM (Read-Only) External Data Providers IBM HTTP Server w/Redirector Plug-in WebSphere Portal HTTPS WebSphere Services Registry & Repository WebSphere Process Server 3 MQ / JMS / XML JDBC SOAP/ HTTPS aznAPI aznAPI MQ/ JMS / XML (Publish) SOAP / HTTPS 11 13 12 WebSphere QualityStage 5 8 11 4 14 Telemarketing System Database Server Transaction Data 15 MQ MQ / JMS / XML 2 Database Server Transaction Data MQ / XML LOB System 1 17 18 Transaction Data LOB Systems Database Server Transaction Data LOB Systems MQ (Subscribe) 19 1 10 11 12 QSRT (RTI) WCC Data Stewardship U.I. Global Name Recognition 7 9 1 Name Knowledge Services MQ LOB Browser U.I. 6 8 12 16 20 1 HTTPS 8
    28. 28. <ul><li>WebSphere QualityStage calls GNR NameParser which returns the standardized name results (parsed name & score). </li></ul><ul><li>WebSphere QualityStage logic determines the best standardized name and returns the standardized name, address and telephone number results to WCC. </li></ul><ul><li>WCC receives the standardized name and address from QualityStage. WCC queries the WCC Database to retrieve candidate names, creates the business object and invokes a QS probabilistic matching service via the QSRT Client. </li></ul><ul><li>WebSphere QualityStage performs probabilistic matching against the candidate names received in the request from WCC. </li></ul>Scenario 1B : Add New Customer with Cross-Sell (GNR) 6 7 8 9 Metadata Data Rules Business Process Data Policy Data User Registry Policy Data User Registry Rules WebSphere Enterprise Service Bus Firewall WebSphere Customer Center Customer Master Data Reference Data DB2 UDB Server Customer History Data DMZ WAS for ND & WebSphere MQ Firewall eNetwork Dispatchers Firewall Tivoli Access Manager WebSeal TAM (Master) TAM (Read-Only) External Data Providers IBM HTTP Server w/Redirector Plug-in WebSphere Portal HTTPS WebSphere Services Registry & Repository WebSphere Process Server 3 MQ / JMS / XML JDBC SOAP/ HTTPS aznAPI aznAPI MQ/ JMS / XML (Publish) SOAP / HTTPS 11 13 12 WebSphere QualityStage 5 8 11 4 14 Telemarketing System Database Server Transaction Data 15 MQ MQ / JMS / XML 2 Database Server Transaction Data MQ / XML LOB System 1 17 18 Transaction Data LOB Systems Database Server Transaction Data LOB Systems MQ (Subscribe) 19 1 10 11 12 QSRT (RTI) WCC Data Stewardship U.I. Global Name Recognition 7 9 1 Name Knowledge Services MQ LOB Browser U.I. 6 8 12 16 20 1 HTTPS 8
    29. 29. <ul><li>WebSphere QualityStage returns the results to WCC which indicates that this is a new customer based upon the score. </li></ul><ul><li>WCC creates and submits a web service request/response to an external data provider for data enrichment. </li></ul><ul><li>The External Data Provider receives the query request, submits the query and returns the results to WCC. </li></ul><ul><li>WCC assigns a unique PartyId, enriches the party record with data received from the External Data Provider and persists the customer and policy data to the WCC database. </li></ul><ul><li>Based upon the customer’s privacy preference, WCC queries marketing campaign information in the WCC database and determines that the customer meets the income criteria for a marketing campaign and can be contacted. </li></ul>Scenario 1B : Add New Customer with Cross-Sell (GNR) 12 13 14 10 11 Metadata Data Rules Business Process Data Policy Data User Registry Policy Data User Registry Rules WebSphere Enterprise Service Bus Firewall WebSphere Customer Center Customer Master Data Reference Data DB2 UDB Server Customer History Data DMZ WAS for ND & WebSphere MQ Firewall eNetwork Dispatchers Firewall Tivoli Access Manager WebSeal TAM (Master) TAM (Read-Only) External Data Providers IBM HTTP Server w/Redirector Plug-in WebSphere Portal HTTPS WebSphere Services Registry & Repository WebSphere Process Server 3 MQ / JMS / XML JDBC SOAP/ HTTPS aznAPI aznAPI MQ/ JMS / XML (Publish) SOAP / HTTPS 11 13 12 WebSphere QualityStage 5 8 11 4 14 Telemarketing System Database Server Transaction Data 15 MQ MQ / JMS / XML 2 Database Server Transaction Data MQ / XML LOB System 1 17 18 Transaction Data LOB Systems Database Server Transaction Data LOB Systems MQ (Subscribe) 19 1 10 11 12 QSRT (RTI) WCC Data Stewardship U.I. Global Name Recognition 7 9 1 Name Knowledge Services MQ LOB Browser U.I. 6 8 12 16 20 1 HTTPS 8
    30. 30. <ul><li>WCC generates a XML message and posts the XML message via JMS to a MQ message queue. WebSphere Enterprise Service Bus translates the XML message based upon message transformation rules to the format recognized by the Telemarketing System. </li></ul><ul><li>The Telemarketing System MQ listener retrieves the message and performs any logic such as notification, scheduling etc. </li></ul><ul><li>WCC creates the XML transaction response message and posts the results indicating that this new customer was processed successfully to a MQ queue for the originating LOB system to retrieve from the queue. </li></ul><ul><li>The originating LOB system retrieves the MQ message in the XML response format and based upon its business logic, updates the customer information in its database from the results contained in the WCC response. </li></ul>Scenario 1B : Add New Customer with Cross-Sell (GNR) 16 17 18 15 Metadata Data Rules Business Process Data Policy Data User Registry Policy Data User Registry Rules WebSphere Enterprise Service Bus Firewall WebSphere Customer Center Customer Master Data Reference Data DB2 UDB Server Customer History Data DMZ WAS for ND & WebSphere MQ Firewall eNetwork Dispatchers Firewall Tivoli Access Manager WebSeal TAM (Master) TAM (Read-Only) External Data Providers IBM HTTP Server w/Redirector Plug-in WebSphere Portal HTTPS WebSphere Services Registry & Repository WebSphere Process Server 3 MQ / JMS / XML JDBC SOAP/ HTTPS aznAPI aznAPI MQ/ JMS / XML (Publish) SOAP / HTTPS 11 13 12 WebSphere QualityStage 5 8 11 4 14 Telemarketing System Database Server Transaction Data 15 MQ MQ / JMS / XML 2 Database Server Transaction Data MQ / XML LOB System 1 17 18 Transaction Data LOB Systems Database Server Transaction Data LOB Systems MQ (Subscribe) 19 1 10 11 12 QSRT (RTI) WCC Data Stewardship U.I. Global Name Recognition 7 9 1 Name Knowledge Services MQ LOB Browser U.I. 6 8 12 16 20 1 HTTPS 8
    31. 31. <ul><li>WCC constructs a XML message with the new customer information and posts the message to an MQ Queue for publishing the new customer data. WebSphere ESB converts the XML message to the specific message format required for each LOB system and routes it to each LOB system MQ queue that matches the subscription topic. </li></ul><ul><li>LOB systems retrieve the message with the new customer and account information and process it according to the business rules for updating their transactional database. </li></ul>Scenario 1B : Add New Customer with Cross-Sell (GNR) 20 19 Metadata Data Rules Business Process Data Policy Data User Registry Policy Data User Registry Rules WebSphere Enterprise Service Bus Firewall WebSphere Customer Center Customer Master Data Reference Data DB2 UDB Server Customer History Data DMZ WAS for ND & WebSphere MQ Firewall eNetwork Dispatchers Firewall Tivoli Access Manager WebSeal TAM (Master) TAM (Read-Only) External Data Providers IBM HTTP Server w/Redirector Plug-in WebSphere Portal HTTPS WebSphere Services Registry & Repository WebSphere Process Server 3 MQ / JMS / XML JDBC SOAP/ HTTPS aznAPI aznAPI MQ/ JMS / XML (Publish) SOAP / HTTPS 11 13 12 WebSphere QualityStage 5 8 11 4 14 Telemarketing System Database Server Transaction Data 15 MQ MQ / JMS / XML 2 Database Server Transaction Data MQ / XML LOB System 1 17 18 Transaction Data LOB Systems Database Server Transaction Data LOB Systems MQ (Subscribe) 19 1 10 11 12 QSRT (RTI) WCC Data Stewardship U.I. Global Name Recognition 7 9 1 Name Knowledge Services MQ LOB Browser U.I. 6 8 12 16 20 1 HTTPS 8

    ×