Transcription

IBM InfoSphere Master Data ManagementVersion 11 Release 5OverviewIBMSC27-6718-01

IBM InfoSphere Master Data ManagementVersion 11 Release 5OverviewIBMSC27-6718-01

NoteBefore using this information and the product that it supports, read the information in Notices and trademarks.Edition NoticeThis edition applies to version 11.5 of IBM InfoSphere Master Data Management and to all subsequent releases andmodifications until otherwise indicated in new editions. Copyright IBM Corporation 2011, 2015.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

ContentsTables . . . . . . . . . . . . . .vInfoSphere MDM product overview . .1Scenarios for InfoSphere MDM . . . . . . .3User roles for MDM . . . . . . . . . . .6InfoSphere MDM technologies . . . . . . .8Comparison of virtual, physical, and hybrid MDMcapabilities . . . . . . . . . . . . .9Virtual MDM . . . . . . . . . . . .10Physical MDM . . . . . . . . . . .11Hybrid MDM. . . . . . . . . . . .11InfoSphere MDM Collaboration Server . . .12InfoSphere MDM technologies by edition . .13 Copyright IBM Corp. 2011, 2015Architecture and concepts for InfoSphere MDM .Key concepts: Entity, attribute, and entity type .Data management in hybrid MDM . . . .Components for InfoSphere MDM . . . . . .InfoSphere MDM Application Toolkit overviewInfoSphere MDM Custom Domain Hub overviewInfoSphere MDM for Healthcare overview . .IBM Stewardship Center overview. . . . .InfoSphere MDM Policy Management overviewInfoSphere MDM Reference Data ManagementHub overview . . . . . . . . . . .Index . . . . . . . . . . . . . .1317191919202021212225iii

ivInfoSphere MDM Overview

Tables1.2.3.Implementation and Operations roles .Governance (Data Stewardship) roles .Enterprise Use of Master Data roles . . Copyright IBM Corp. 2011, 2015.6784.5.6.MDM-Powered Applications roles . . . .Capabilities . . . . . . . . . . .Client applications . . . . . . . . .81015v

viInfoSphere MDM Overview

InfoSphere MDM product overviewInfoSphere MDM is a comprehensive suite of products and capabilities that youcan use to manage the master data in your organization.Introduction to master data and master data managementCompanies frequently have difficulty achieving an accurate view of the key factsthat affect the organization in non-customer-facing environments such asoperations and finance because data about customers, locations, accounts,suppliers, and products can often be fragmented, incomplete, or inconsistent acrossorganizations. InfoSphere MDM provides the features and flexibility needed tosolve these issues.v Master data is a subset of all enterprise data. Master data is the high-value, coreinformation used to support critical business processes across the enterprise.Master data is at the heart of every business transaction, application, anddecision.v Master data management is a discipline that provides a consistent understandingof master data entities (for example, subscriber, policy, and so forth). It is a set offunctionality that provides mechanisms and governance for the consistent use ofmaster data across the organization. It is designed to accommodate, control, andmanage change.InfoSphere MDM addresses issues of fragmented, incomplete and inconsistent datawith a central repository to store master data across the organization. InfoSphereMDM provides a consolidated, central view of an organization's key business factsand also provides the ability to manage master data throughout its lifecycle byintegrating with each organization's specific business rules and processes forcreating, verifying, maintaining, and deleting master data from the repository.InfoSphere MDM helps organizations realize the full benefit of their investments incustomer relationship management (CRM), enterprise resource planning (ERP), andbusiness intelligence (BI) systems, as well as integration tools and data warehouses.Lifecycle of informationInfoSphere MDM is in the midst of the lifecycle of information, as shown in thefollowing diagram: Copyright IBM Corp. 2011, 20151

Customerservice andcareMaximizing customersatisfaction andrevenue opportunitiesCustomerself serviceOptimizing thebusiness withright-timeinformationToolsMarketingand -to-endmaster ingSearchStewardshipFraud avoidanceBack officesystemsUnderstanding thechoices and planningwith accurateinformationRegulatorycomplianceEnsuring allsystems haveconsistent andcompleteinformationin real timeNew productintroductionUnified viewThe following diagram shows how InfoSphere MDM pulls together informationinto a unified view across business processes, transactional systems, and analyticalsystems. InfoSphere MDM addresses key data issues such as governance, quality,and consistency. The MDM goals are as follows:ManageTo manage your data. InfoSphere MDM manages your data from sourcesystems such as business applications, databases, and content sources.GovernTo provide data stewardship tools that help ensure quality and security.Data stewardship is essential for your MDM implementation.Develop and integrateTo create custom applications and business processes. Each MDMimplementation has different requirements; InfoSphere MDM provides thedevelopment tools to create custom applications and business processes.AnalyzeTo analyze your data. Business intelligence applications help you tomonitor and assess your master data and how it affects your businessgoals.2InfoSphere MDM Overview

The editionsInfoSphere MDM includes both transaction-oriented MDM and collaborativeauthoring and workflow capabilities to handle multiple domains, implementationstyles, and use cases across various industries. To provide you with optimalcoverage of their MDM solution requirements, InfoSphere MDM is offered in theseeditions:v Enterprise Edition addresses your MDM needs with a single, comprehensivesolution.v Advanced Edition helps you to transform your organization through improvedbusiness processes and applications.v Standard Edition delivers business value for MDM projects with a quick time tovalue.v Collaborative Edition streamlines workflow activities across users who areinvolved in authoring and defining information.Related information:Video: InfoSphere MDM in actionScenarios for InfoSphere MDMScenarios show how you might use the various editions of InfoSphere MDM tomaster data and improve data governance.The following examples list only a few of the ways that you might take advantageof the different editions of InfoSphere MDM. Which edition and features you usetypically depends on your requirements and environment. The scenarios describeoptions for meeting requirements for particular environments. But becauseInfoSphere MDM is flexible and configurable, you might use a different edition ordifferent features to achieve similar business or organizational goals. TheseInfoSphere MDM product overview3

scenarios consider a few key industries as examples, however it is not possible tolist specific information for all the industries and domains that can benefit fromInfoSphere MDM.Generally, if you obtain InfoSphere Master Data Management Standard Edition,you deploy MDM as a registry implementation. If you obtain InfoSphere MasterData Management Advanced Edition or InfoSphere Master Data ManagementEnterprise Edition, you deploy MDM either as a registry implementation or as acentralized implementation. In Advanced and Enterprise Editions, you can haveboth registry and centralized implementations by using hybrid MDM in thisscenario:v You want to maintain source systems as your system of record for master data,by using virtual MDM capabilities to match and merge.v You also use physical MDM capabilities to persist and augment a definedenterprise view with more centrally managed information.Patient data from multiple clinicsWith InfoSphere Master Data Management Standard Edition, a regional healthcareorganization allows its individual clinics to maintain diagnostic and treatmentinformation locally. While the organization maintains a centrally located index (or"registry") of the distributed data. The organization chooses this registryimplementation style because government regulations do not allow healthcareorganizations to modify the data that is provided by clinics. Therefore, theorganization cannot consolidate source records into a single physical record thathappens with a centralized implementation style. The registry style provides acomplete view of a patient across all clinics. At the same time, this implementationenables newly acquired clinics to be integrated quickly into the organization.How it works:1. The MDM architect uses the Patient Hub to quickly set up an MDMenvironment as a registry implementation.2. The MDM architect and data steward use the InfoSphere MDM Workbench torun processes that clean and de-duplicate the data. Then InfoSphere MDMstores a consolidated virtual view of each patient.3. Customer service representatives and clinic staff use InfoSphere MDMInspector and InfoSphere MDM Enterprise Viewer to perform data stewardshipactivities.4. Application developers create custom business process flows for businessanalysts to analyze and improve patient data. At the same time, theorganization continues to integrate data from newly acquired clinics.Customer centralization for insurance policiesUsing InfoSphere Master Data Management Advanced Edition, a property andcasualty insurance company centralizes insurance-policy data for faster and moreaccurate actuarial analysis. The centralization works well for information that iscomplex but relatively static (for example, coverage under multiple policies). Asthe company loads customer data from different sources into the central system,InfoSphere MDM standardizes the party information and merges duplicatecustomer records. This action is based on predefined business rules forsurvivorship. The company expects to integrate new data sources gradually overtime.4InfoSphere MDM Overview

How it works:1. The MDM architect starts with the default party domain to model the insurancecustomers and to set up the MDM environment in a centralizedimplementation style.2. The MDM architect and data steward can augment the built-in capabilities bydeveloping extensions and additions. For example, the company might developan extension to populate a new field that contains only the last 4 digits of acustomer's Social Security Number. Administrators might allow an applicationthat is used by call-center agents to access the new field, while theadministrators prohibit access to the full Social Security Number.3. Local agents and call-center agents access a single view of a customer with theData Stewardship UI so they can improve cross- and up-sell opportunities.4. Business analysts review customers’ coverage under multiple policies by usingIBM Cognos reports.Single view of citizens for government agenciesWith InfoSphere Master Data Management Advanced Edition, a governmentagency creates a single view of "persons of interest" that is built from multiple datasources. By using a centralized implementation, the agency can easily augment thedata model with more attributes such as multiple alias fields and last knownlocation.How it works:1. The MDM architect starts with the party domain to build a model of persons ofinterest and to set up the MDM environment in a centralized implementationstyle.2. The MDM architect and data steward can augment the built-in capabilities bydeveloping extensions and additions.3. The MDM architect generates a feed into an InfoSphere Identity Insight systemfor party actions, such as updates, additions, and deletions.4. Application developers create custom user interfaces with the InfoSphere MDMApplication Toolkit so that government employees can view the person data.Consistent product information for the retail industryWith InfoSphere Master Data Management Collaborative Edition, a retail businesshas consistent product information both for its customers and for internaloperations. The customer can see the same product information from mobileapplications, websites, or at a physical store. For internal operations, consistentproduct information streamlines interactions with vendors, manufacturers, andinternal teams, such as sales and marketing.How it works:1. The MDM architect starts by creating the data model and business-processobjects for product information management.2. The MDM architect simplifies the addition of new products to the product lineby setting up global data synchronization with existing vendor andmanufacturing systems.3. The business users create and update product packages with shared workflows.InfoSphere MDM product overview5

Customer-centric initiative for financial servicesWith InfoSphere Master Data Management Enterprise Edition, a financial servicescompany recently added new products. The company wants to offer them tocustomers of its recent acquisition, a regional bank.How it works:1. The MDM architect consolidates the company's existing customers with its newregional bank’s customers, while the architect allows the regional bank tomaintain its customer records. The architect implements a hybrid MDM model,where some data is stored centrally in its complete form. At the same time, thearchitect centrally stores pointers to data that is maintained regionally in aregistry implementation.2. Data stewards and business analysts ensure compliance with regulations suchas privacy controls, Basel accords, and tax compliance.3. Data stewards define and manage reference data (for example, country codes,gender codes, and customer types) for the company’s customers. Then, thecompany can send certain product offerings only to eligible customers.4. With collaborative authoring of bundled offerings, business users centrallymanage bundles, check eligibility or pricing, make updates, and detectviolations of terms and conditions.Related information:Video: Banking solutionsVideo: Government solutionsVideo: Healthcare solutionsVideo: Insurance solutionsVideo: Product solutionsVideo: Telecommunications solutionsUser roles for MDMTo offer some clarity about which members of your organization might completeparticular MDM tasks, the InfoSphere MDM documentation employs a set ofspecific user roles.The roles that are outlined here are descriptive. They do not correspond to productcapabilities. In particular, the user roles do not determine which features users canuse.These roles are examples of the type of roles that you might have in yourorganization. Your organization might call these roles by other names.Table 1. Implementation and Operations roles6RoleDescriptionArchitectThe goals of the Architect are the overallimplementation of MDM into the enterprise.The Architect also sets up the infrastructureand connections to other enterpriseinformation systems. In your organization,you might call this role an MDM Designer,Solution Architect, or Enterprise Architect.InfoSphere MDM Overview

Table 1. Implementation and Operations roles (continued)RoleDescriptionDatabase AdministratorThe Database Administrator (DBA) ensuresthe performance of data-related components,including the security of data and theavailability of databases. Your organizationmight refer to this role as the LeadOperations DBA, Enterprise DBA, or DataWarehouse DBA.System AdministratorThe System Administrator manages andmaintains the IT environment for MDM andits operations management tools, includingsystem administration, networking, andbackup. The System Administrator alsotypically maintains various components andframeworks for reuse within other solutions.In your organization, this role mightcorrespond to the IT Administrator orMetadata Administrator.Solution DeveloperThe Solution Developer uses specificationsthat are created by Architects to build theMDM system. In your organization, youmight call this role a Senior Consultant orDevelopment Manager.Table 2. Governance (Data Stewardship) rolesRoleDescriptionBasic Data StewardThe Basic Data Steward managesinformation quality for one or more subjectareas of the business. This role typicallyresolves data issues for such things ascompany names and addresses by validatingvalues against third-party sources. In yourorganization, the Data Steward role mightcorrespond to an Agent or a CustomerService Representative.Advanced Data StewardThe Advanced Data Steward resolvesidentity resolution issues, such asdeduplication, maintains hierarchies, anddevelops business rules. This role typicallyinvestigates data questions and analyzes thedata to identify trends and to improvebusiness processes. This role coordinatesaccess authorization and planning for thesubject area data. In your organization, youmight call this role a Business Analyst, DataAnalyst, or Line-of-Business User. This rolesometimes overlaps with the Enterprise Useof Master Data roles.InfoSphere MDM product overview7

Table 2. Governance (Data Stewardship) roles (continued)RoleDescriptionData Steward ManagerThe Data Steward Manager manages a teamof Basic and Advanced Data Stewards toensure that quality goals are met for theorganization. This role reviews data qualityreports and develops standard operatingprocedures for the team. This role mightdevelop business rules and perform datastewardship tasks also.Master Data Governance CouncilThe Council is a cross-functional, multi-layerteam that collectively owns master data. Thecouncil steers master data managementinitiatives at the program level. In yourorganization, they might include theDirector of Governance Quality Board, theData Standards Program Lead, and otherbusiness roles.Table 3. Enterprise Use of Master Data rolesRoleDescriptionBusiness AnalystThe Business Analyst provides the analysisto enable the business integration of theMDM application into the enterprise. TheBusiness Analyst understands customer andbusiness needs and identifies areas wherebusiness processes can be optimized tobetter serve those needs. In yourorganization, you might call this role a DataAnalyst, Subject Matter Expert, orInformation Analyst.Business UserThe Business User uses the content ofenterprise information to achieve businessgoals. Your organization might refer to theBusiness User as an Information User,Report User, or Application User.Table 4. MDM-Powered Applications rolesRoleDescriptionApplication DeveloperThe Application Developer augments MDMto meet the requirements of the businesswith additions, extensions, and so forth. TheApplication Developer performsdevelopment tasks to integrate MDM intothe enterprise. In your organization, this rolemight correspond to a Software Engineer,Software Programmer, or Data IntegrationDeveloper.InfoSphere MDM technologiesThe InfoSphere MDM portfolio includes distinct technologies.8InfoSphere MDM Overview

Comparison of virtual, physical, and hybrid MDM capabilitiesThe technical capabilities of virtual, physical, and hybrid MDM help you tomanage your master data, whether you store that data in a distributed fashion, ina centralized repository, or in a combination of both.The following definitions show the differences and the relationships among thetechnical capabilities:Virtual MDMThe management of master data where master data is created in adistributed fashion on source systems and remains fragmented across thosesystems with a central "indexing" service.Physical MDMThe management of master data where master data is created in (or loadedinto), stored in, and accessed from a central system.Hybrid MDMThe management of master data where a coexistence implementation stylecombines physical and virtual technologies.Relative to your master data goals, you might require the technical capabilities ofvirtual MDM, physical MDM, or hybrid MDM. These capabilities are notimplementation styles, but instead they ar