IBM InfoSphere Master Data Management Version Overview SC

Transcription

1 IBM InfoSphere Master Data Management Version 11.4 Oeriew SC

2

3 IBM InfoSphere Master Data Management Version 11.4 Oeriew SC

4 Note Before using this information and the product that it supports, read the information in Notices and trademarks. Edition Notice This edition applies to ersion 11.4 of IBM InfoSphere Master Data Management and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2011, US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Tables InfoSphere MDM product oeriew... 1 Scenarios for InfoSphere MDM User roles for MDM InfoSphere MDM technologies Comparison of irtual, physical, and hybrid MDM capabilities Virtual MDM Physical MDM Hybrid MDM InfoSphere MDM Collaboration Serer InfoSphere MDM technologies by edition Architecture and concepts for InfoSphere MDM.. 13 Key concepts: Entity, attribute, and entity type. 16 Data management in hybrid MDM Components for InfoSphere MDM InfoSphere MDM Application Toolkit oeriew 18 InfoSphere MDM Custom Domain Hub oeriew 19 InfoSphere MDM for Healthcare oeriew IBM Stewardship Center oeriew InfoSphere MDM Policy Management oeriew 20 InfoSphere MDM Reference Data Management Hub oeriew Notices Index Contacting IBM Copyright IBM Corp. 2011, 2014 iii

6 i InfoSphere MDM Oeriew

7 Tables 1. Implementation and Operations roles Goernance (Data Stewardship) roles Enterprise Use of Master Data roles MDM-Powered Applications roles Capabilities Client applications IBM resources Proiding feedback to IBM Copyright IBM Corp. 2011, 2014

8 i InfoSphere MDM Oeriew

9 InfoSphere MDM product oeriew InfoSphere MDM is a comprehensie suite of products and capabilities that you can use to manage the master data in your organization. Introduction to master data and master data management Companies frequently hae difficulty achieing an accurate iew of the key facts that affect the organization in non-customer-facing enironments such as operations and finance because data about customers, locations, accounts, suppliers, and products can often be fragmented, incomplete, or inconsistent across organizations. InfoSphere MDM proides the features and flexibility needed to sole these issues. Master data is a subset of all enterprise data. Master data is the high-alue, core information used to support critical business processes across the enterprise. Master data is at the heart of eery business transaction, application, and decision. Master data management is a discipline that proides a consistent understanding of master data entities (for example, subscriber, policy, and so forth). It is a set of functionality that proides mechanisms and goernance for the consistent use of master data across the organization. It is designed to accommodate, control, and manage change. InfoSphere MDM addresses issues of fragmented, incomplete and inconsistent data with a central repository to store master data across the organization. InfoSphere MDM proides a consolidated, central iew of an organization's key business facts and also proides the ability to manage master data throughout its lifecycle by integrating with each organization's specific business rules and processes for creating, erifying, maintaining, and deleting master data from the repository. InfoSphere MDM helps organizations realize the full benefit of their inestments in customer relationship management (CRM), enterprise resource planning (ERP), and business intelligence (BI) systems, as well as integration tools and data warehouses. Lifecycle of information InfoSphere MDM is in the midst of the lifecycle of information, as shown in the following diagram: Copyright IBM Corp. 2011,

10 Optimizing the business with right-time information Customer self serice Customer serice and care Maximizing customer satisfaction and reenue opportunities Tools Enrich Billing Marketing and sales interactions Authoring Security End-to-end master data management Hierarchies Operational Financial planning Back office systems Search Stewardship Fraud aoidance Ensuring all systems hae consistent and complete information in real time Understanding the choices and planning with accurate information Regulatory compliance New product introduction Unified iew The following diagram shows how InfoSphere MDM pulls together information into a unified iew across business processes, transactional systems, and analytical systems. InfoSphere MDM addresses key data issues such as goernance, quality, and consistency. The MDM goals are as follows: Manage To manage your data. InfoSphere MDM manages your data from source systems such as business applications, databases, and content sources. Goern To proide data stewardship tools that help ensure quality and security. Data stewardship is essential for your MDM implementation. Deelop and integrate To create custom applications and business processes. Each MDM implementation has different requirements; InfoSphere MDM proides the deelopment tools to create custom applications and business processes. Analyze To analyze your data. Business intelligence applications help you to monitor and assess your master data and how it affects your business goals. 2 InfoSphere MDM Oeriew

11 Custom Applications and Business Processes Deelop and Integrate Analyze Reports & Dashboards Business Intelligence Applications MDM Manage CRM Business Applications Transactional Business Applications Database Infrastructure Content Goern Data Quality Security Lifecycle Management The editions InfoSphere MDM includes both transaction-oriented MDM and collaboratie authoring and workflow capabilities to handle multiple domains, implementation styles, and use cases across arious industries. To proide you with optimal coerage of their MDM solution requirements, InfoSphere MDM is offered in these editions: Enterprise Edition addresses your MDM needs with a single, comprehensie solution. Adanced Edition helps you to transform your organization through improed business processes and applications. Standard Edition deliers business alue for MDM projects with a quick time to alue. Collaboratie Edition streamlines workflow actiities across users who are inoled in authoring and defining information. Related information: Video: InfoSphere MDM in action Scenarios for InfoSphere MDM Scenarios show how you might use the arious editions of InfoSphere MDM to master data and improe data goernance. The following examples list only a few of the ways that you might take adantage of the different editions of InfoSphere MDM. Which edition and features you use typically depends on your requirements and enironment. The scenarios describe options for meeting requirements for particular enironments. But because InfoSphere MDM is flexible and configurable, you might use a different edition or different features to achiee similar business or organizational goals. These scenarios consider a few key industries as examples, howeer it is not possible to list specific information for all the industries and domains that can benefit from InfoSphere MDM. Generally, if you obtain InfoSphere Master Data Management Standard Edition, you deploy MDM as a registry implementation. If you obtain InfoSphere Master Data Management Adanced Edition or InfoSphere Master Data Management InfoSphere MDM product oeriew 3

12 Enterprise Edition, you deploy MDM either as a registry implementation or as a centralized implementation. In Adanced and Enterprise Editions, you can hae both registry and centralized implementations by using hybrid MDM in this scenario: You want to maintain source systems as your system of record for master data, by using irtual MDM capabilities to match and merge. You also use physical MDM capabilities to persist and augment a defined enterprise iew with more centrally managed information. Patient data from multiple clinics With InfoSphere Master Data Management Standard Edition, a regional healthcare organization allows its indiidual clinics to maintain diagnostic and treatment information locally. While the organization maintains a centrally located index (or "registry") of the distributed data. The organization chooses this registry implementation style because goernment regulations do not allow healthcare organizations to modify the data that is proided by clinics. Therefore, the organization cannot consolidate source records into a single physical record that happens with a centralized implementation style. The registry style proides a complete iew of a patient across all clinics. At the same time, this implementation enables 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 MDM enironment as a registry implementation. 2. The MDM architect and data steward use the InfoSphere MDM Workbench to run processes that clean and de-duplicate the data. Then InfoSphere MDM stores a consolidated irtual iew of each patient. 3. Customer serice representaties and clinic staff use InfoSphere MDM Inspector, flexible search, and InfoSphere MDM Enterprise Viewer to perform data stewardship actiities. 4. Application deelopers create custom business process flows for business analysts to analyze and improe patient data. At the same time, the organization continues to integrate data from newly acquired clinics. Customer centralization for insurance policies Using InfoSphere Master Data Management Adanced Edition, a property and casualty insurance company centralizes insurance-policy data for faster and more accurate actuarial analysis. The centralization works well for information that is complex but relatiely static (for example, coerage under multiple policies). As the company loads customer data from different sources into the central system, InfoSphere MDM standardizes the party information and merges duplicate customer records. This action is based on predefined business rules for suriorship. The company expects to integrate new data sources gradually oer time. How it works: 1. The MDM architect starts with the default party domain to model the insurance customers and to set up the MDM enironment in a centralized implementation style. 2. The MDM architect and data steward can augment the built-in capabilities by deeloping extensions and additions. For example, the company might deelop an extension to populate a new field that contains only the last 4 digits of a 4 InfoSphere MDM Oeriew

13 customer's Social Security Number. Administrators might allow an application that is used by call-center agents to access the new field, while the administrators prohibit access to the full Social Security Number. 3. Local agents and call-center agents access a single iew of a customer with the Data Stewardship UI so they can improe cross- and up-sell opportunities. 4. Business analysts reiew customers coerage under multiple policies by using IBM Cognos reports. Single iew of citizens for goernment agencies With InfoSphere Master Data Management Adanced Edition, a goernment agency creates a single iew of "persons of interest" that is built from multiple data sources. By using a centralized implementation, the agency can easily augment the data model with more attributes such as multiple alias fields and last known location. How it works: 1. The MDM architect starts with the party domain to build a model of persons of interest and to set up the MDM enironment in a centralized implementation style. 2. The MDM architect and data steward can augment the built-in capabilities by deeloping extensions and additions. 3. The MDM architect generates a feed into an InfoSphere Identity Insight system for party actions, such as updates, additions, and deletions. 4. Application deelopers create custom user interfaces with the InfoSphere MDM Application Toolkit so that goernment employees can iew the person data. Consistent product information for the retail industry With InfoSphere Master Data Management Collaboratie Edition, a retail business has consistent product information both for its customers and for internal operations. The customer can see the same product information from mobile applications, websites, or at a physical store. For internal operations, consistent product information streamlines interactions with endors, manufacturers, and internal teams, such as sales and marketing. How it works: 1. The MDM architect starts by creating the data model and business-process objects for product information management. 2. The MDM architect simplifies the addition of new products to the product line by setting up global data synchronization with existing endor and manufacturing systems. 3. The business users create and update product packages with shared workflows. Customer-centric initiatie for financial serices With InfoSphere Master Data Management Enterprise Edition, a financial serices company recently added new products. The company wants to offer them to customers of its recent acquisition, a regional bank. How it works: 1. The MDM architect consolidates the company's existing customers with its new regional bank s customers, while the architect allows the regional bank to InfoSphere MDM product oeriew 5

14 User roles for MDM maintain its customer records. The architect implements a hybrid MDM model, where some data is stored centrally in its complete form. At the same time, the architect centrally stores pointers to data that is maintained regionally in a registry implementation. 2. Data stewards and business analysts ensure compliance with regulations such as priacy 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, the company can send certain product offerings only to eligible customers. 4. With collaboratie authoring of bundled offerings, business users centrally manage bundles, check eligibility or pricing, make updates, and detect iolations of terms and conditions. Related information: Video: Banking solutions Video: Goernment solutions Video: Healthcare solutions Video: Insurance solutions Video: Product solutions Video: Telecommunications solutions To offer some clarity about which members of your organization might complete particular MDM tasks, the InfoSphere MDM documentation employs a set of specific user roles. The roles that are outlined here are descriptie. They do not correspond to product capabilities. In particular, the user roles do not determine which features users can use. These roles are examples of the type of roles that you might hae in your organization. Your organization might call these roles by other names. Table 1. Implementation and Operations roles Role Architect Database Administrator Description The goals of the Architect are the oerall implementation of MDM into the enterprise. The Architect also sets up the infrastructure and connections to other enterprise information systems. In your organization, you might call this role an MDM Designer, Solution Architect, or Enterprise Architect. The Database Administrator (DBA) ensures the performance of data-related components, including the security of data and the aailability of databases. Your organization might refer to this role as the Lead Operations DBA, Enterprise DBA, or Data Warehouse DBA. 6 InfoSphere MDM Oeriew

15 Table 1. Implementation and Operations roles (continued) Role Description System Administrator The System Administrator manages and maintains the IT enironment for MDM and its operations management tools, including system administration, networking, and backup. The System Administrator also typically maintains arious components and frameworks for reuse within other solutions. In your organization, this role might correspond to the IT Administrator or Metadata Administrator. Solution Deeloper The Solution Deeloper uses specifications that are created by Architects to build the MDM system. In your organization, you might call this role a Senior Consultant or Deelopment Manager. Table 2. Goernance (Data Stewardship) roles Role Description Basic Data Steward The Basic Data Steward manages information quality for one or more subject areas of the business. This role typically resoles data issues for such things as company names and addresses by alidating alues against third-party sources. In your organization, the Data Steward role might correspond to an Agent or a Customer Serice Representatie. Adanced Data Steward The Adanced Data Steward resoles identity resolution issues, such as deduplication, maintains hierarchies, and deelops business rules. This role typically inestigates data questions and analyzes the data to identify trends and to improe business processes. This role coordinates access authorization and planning for the subject area data. In your organization, you might call this role a Business Analyst, Data Analyst, or Line-of-Business User. This role sometimes oerlaps with the Enterprise Use of Master Data roles. Data Steward Manager The Data Steward Manager manages a team of Basic and Adanced Data Stewards to ensure that quality goals are met for the organization. This role reiews data quality reports and deelops standard operating procedures for the team. This role might deelop business rules and perform data stewardship tasks also. InfoSphere MDM product oeriew 7

16 Table 2. Goernance (Data Stewardship) roles (continued) Role Description Master Data Goernance Council The Council is a cross-functional, multi-layer team that collectiely owns master data. The council steers master data management initiaties at the program leel. In your organization, they might include the Director of Goernance Quality Board, the Data Standards Program Lead, and other business roles. Table 3. Enterprise Use of Master Data roles Role Business Analyst Business User Description The Business Analyst proides the analysis to enable the business integration of the MDM application into the enterprise. The Business Analyst understands customer and business needs and identifies areas where business processes can be optimized to better sere those needs. In your organization, you might call this role a Data Analyst, Subject Matter Expert, or Information Analyst. The Business User uses the content of enterprise information to achiee business goals. Your organization might refer to the Business User as an Information User, Report User, or Application User. Table 4. MDM-Powered Applications roles Role Application Deeloper Description The Application Deeloper augments MDM to meet the requirements of the business with additions, extensions, and so forth. The Application Deeloper performs deelopment tasks to integrate MDM into the enterprise. In your organization, this role might correspond to a Software Engineer, Software Programmer, or Data Integration Deeloper. InfoSphere MDM technologies The InfoSphere MDM portfolio includes distinct technologies. Comparison of irtual, physical, and hybrid MDM capabilities The technical capabilities of irtual, physical, and hybrid MDM help you to manage your master data, whether you store that data in a distributed fashion, in a centralized repository, or in a combination of both. The following definitions show the differences and the relationships among the technical capabilities: 8 InfoSphere MDM Oeriew

17 Virtual MDM The management of master data where master data is created in a distributed fashion on source systems and remains fragmented across those systems with a central "indexing" serice. Physical MDM The management of master data where master data is created in (or loaded into), stored in, and accessed from a central system. Hybrid MDM The management of master data where a coexistence implementation style combines physical and irtual technologies. Relatie to your master data goals, you might require the technical capabilities of irtual MDM, physical MDM, or hybrid MDM. These capabilities are not implementation styles, but instead they are means by which you might achiee your goals for a particular implementation style. Where and how you choose to store a golden record is reflected by the implementation style for your MDM solution. The distinction between product capabilities and implementation styles is as follows: You can achiee a registry implementation style by installing the Standard Edition and by using the irtual MDM capabilities. You can achiee a centralized implementation style by installing the Adanced Edition and by using the physical MDM capabilities. You can achiee a coexistence implementation style by installing the Adanced or Enterprise Edition and by using the hybrid MDM capabilities. The following diagram shows the interrelationships of physical and irtual MDM capabilities as they relate to the editions: InfoSphere MDM MDM operational serer MDM collaboration serer Virtual MDM Physical MDM Collaboratie MDM Legend: MDM Editions are groupings of capabilities Enterprise Adanced Standard Collaboratie = Virtual, Physical, Collaboratie = Virtual, Physical = Virtual = Collaboratie In preious releases, you might hae used the following products to achiee equialent results with each capability: InfoSphere MDM product oeriew 9

18 Table 5. Capabilities Technical capability Preious product name irtual MDM Initiate Master Data Serice physical MDM InfoSphere MDM Serer hybrid MDM InfoSphere MDM Serer Initiate Master Data Serice collaboratie MDM InfoSphere MDM Serer for Product Information Management (PIM) Virtual MDM The technical capabilities of irtual MDM assemble a irtual iew of master data from existing systems, deliering tailored iews wheneer and whereer they are needed. Virtual MDM can help organizations improe customer serice, lower costs, and reduce risks, while it meets current and future business needs. Virtual MDM proides these capabilities: A irtual master registry that improes existing foundational processes and applications. Views of trusted information that are deliered in real time and tailored to indiidual users or groups. Data stewardship and data goernance capabilities to help resole differences between source systems and maintain data integrity. Powerful relationship and hierarchy management capabilities that proide significant alue in managing both household and business-to-business relationships. An assembled "single iew" of key data such as Customer, Patient, Product, Account, and Location information, and their relationships. Accuracy, performance, and scalability to grow from departmental implementations to multinational enterprises, with deployments across a dozen industries. Exceptional time-to-alue for registry implementations. Physical MDM The technical capabilities of physical MDM include a physical master repository that deliers a single ersion of truth of an organization s critical data entries. Examples of data entries are customer, product, and supplier. The technical capabilities help an organization to make better decisions and achiee better business outcomes. Physical MDM includes these capabilities: Multidomain MDM Prebuilt party, account, and product domains, along with deelopment tools to simplify customization for industry-specific requirements. Serice-oriented architecture (SOA) A complete SOA library of prepackaged business serices that organizations use to define how users access master data. The SOA library integrates into current architectures and business processes. 10 InfoSphere MDM Oeriew

19 Eent management The ability to proactiely respond to data eents and trigger business processes (such as up-selling, cross-selling, retention campaigns, and priacy). Then, you can react to business opportunities and lower oerall risk. Performance An MDM transaction hub for high olume system of record implementations, which results in less downtime and high reliability. Flexibility The ability to extend and define prebuilt data domains, business serices, and user interfaces. This ability saes time and cost during implementation while your implementation can scale to meet growing business demands. Data stewardship and user interfaces Role-based, domain drien hierarchy management user interfaces, as well as tools for deterministic or probabilistic party matching and physical party collapses. Hybrid MDM Hybrid MDM combines the technical capabilities of irtual MDM and physical MDM. The capabilities allow for the seamless moement and management of a master data entity between its irtual MDM and physical MDM representations. Mappings create correspondences between irtual MDM attributes and physical MDM attributes. Most of the mappings that you need are defined already and proided with InfoSphere MDM Adanced Edition. Use the InfoSphere MDM Workbench and begin with the default mapping for your hybrid MDM solution. Choose a single iew of the irtual MDM person or organization entities that you want to persist in the physical MDM domain. InfoSphere MDM Collaboration Serer With InfoSphere MDM Collaboration Serer (Collaboratie Edition), companies can create a single, up-to-date repository of product information. That repository then can be used throughout the organization for strategic initiaties. InfoSphere MDM Collaboration Serer proides the following benefits: A flexible data model Includes product, category, hierarchy, taxonomy, location, and extensible modeling capabilities that help you to build models that eole as your organization eoles. Data aggregation and syndication Supports importing and exporting data oer seeral standard protocols and flexible data formats to minimize impact on interfacing systems. Collaboratie workflows Enables organizations to set up workflows to reflect existing and new business processes and rules, ensuring that the system closely aligns with your practices. User experience for business users Proides user interfaces for data authoring and for searches. Those user InfoSphere MDM product oeriew 11

20 interfaces include single-edit screens; mass update screens; category-mapping; faster and simpler searching capabilities; single sign-on (SSO); and web style content through a rich text editor. Link to unstructured content Integrates with content management applications. Reporting Includes adanced auditing and reporting capabilities with configurable history tracking. Integration Has a built-in integration with other IBM InfoSphere products. Business uses for InfoSphere MDM Collaboration Serer As an example, InfoSphere MDM Collaboration Serer fulfills the following needs: Creation and management of product catalogs Business-process workflows for data goernance Adanced business-focused tools for product-hierarchy management and multiple product hierarchies Data model where business users can make changes without IT inolement Role-based security down to the attribute leel that is enforced through the user interfaces Other master data management for product-like domains, such as asset or project domains You can address more complementary, product-data needs by using Adanced Edition with Collaboratie Edition: Operational multidomain needs and relationships between products and other entity types: customers, accounts, suppliers, endors, employees, and so forth. Publication of product-rule combinations from Collaboratie Edition to Adanced Edition for execution in a multidomain context. This implementation takes adantage of these integration points: Collaboratie Edition with IBM Operational Decision Management for rule authoring. Adanced Edition with IBM Operational Decision Management for rule execution. A single, enterprise multidomain implementation where both editions are already in use separately. InfoSphere MDM technologies by edition Some technologies are aailable only in particular editions. Edition Physical MDM Virtual MDM Collaboratie MDM Enterprise Edition Yes Yes Yes Adanced Edition Yes Yes No Standard Edition No Yes No Collaboratie Edition No No Yes 12 InfoSphere MDM Oeriew

21 Architecture and concepts for InfoSphere MDM InfoSphere MDM proides a unified architecture that works with arious types of master data. Common serices, a unified workbench, and customizable applications are at the core of the architecture. Standard and Adanced Editions The following deployment diagram shows how the clients, the application serer, the MDM operational serer, and the database serer can be deployed in your enironment. To start, the data that you want to master is stored in source systems. You perform most of your master data tasks within the clients, such as the Workbench, InfoSphere MDM Inspector, or your own custom-built clients. Those clients connect to the application serer that hosts the operational serer, where most MDM processing occurs. Finally, the application serer uses a database serer to host the MDM database and other databases that are applicable to optional components. Clients Data stewardship clients Workbench Custom-built clients Application toolkit Application serer Database serer MDM operational serer Serices Physical, irtual, & hybrid domains Core components MDM database Reference data management database Source systems Policy management database Data sources The primary components are defined as follows: Operational serer The software that proides serices for managing and taking action on master data. The operational serer includes the data models, business rules, and functions that support entity management, security, auditing, and eent detection capabilities. Examples of functions that support entity InfoSphere MDM product oeriew 13

22 management include data loads, cleansing, linkage, and de-duplication. Preiously referred to as master data engine in Initiate Master Data Serice and MDM Hub or MDM Serer in InfoSphere MDM Serer. Application serer A serer program in a distributed network that proides the execution enironment for an application program. Database serer or DBMS A software program that uses a database manager to proide database serices to other software programs or computers. Clients Software programs that request serices from the operational serer. The following clients proide entry points to your key MDM actiities. Table 6. Client applications MDM actiities Clients Configuration and customization of your MDM solution Data goernance and stewardship Administration Deelopment InfoSphere MDM blueprints in InfoSphere Blueprint Director InfoSphere MDM Workbench IBM Cognos reports InfoSphere MDM Data Stewardship UI InfoSphere MDM Enterprise Viewer Flexible search InfoSphere MDM Inspector InfoSphere MDM Pair Manager InfoSphere MDM Product Maintenance UI InfoSphere MDM Reference Data Management Hub InfoSphere MDM Unstructured Text Correlation InfoSphere MDM Web Reports Some stewardship actiities are configured in InfoSphere MDM Workbench. InfoSphere MDM Administration UI WebSphere Administratie Console InfoSphere MDM Application Toolkit InfoSphere MDM Batch Console (sample) InfoSphere MDM for IBM Business Process Manager InfoSphere MDM Workbench SDKs, APIs Primary users Architect, Solution Deeloper, Data Steward Lead Data Steward, Business Analyst, Business User, Application User System Administrator, Database Administrator Solution Deeloper, Application Deeloper For a more detailed look at the architecture, the following diagram shows the components that form the whole architecture: 14 InfoSphere MDM Oeriew

23 Clients Data stewardship clients Workbench APIs, SDKs Custom-built clients Application Toolkit Application Serer MDM operational serer Serices Request framework Adaptie serice interface Connectiity (WD, RMI, JMS) Virtual MDM serices APIs Database serer Composite business proxy Business eent manager Notification CEI Parsers & constructors Authorization & access Task management Security Logging Client-specific serices esoa serices Reporting Auditing & monitoring MDM database (physical and irtual MDM) Composite iews with irtual MDM Physical MDM tables Other MDM artifacts Core components Data loads Policy hub Standardization External rules engine Configuration management BPM serer Message broker suite Probabilistic matching engine Batch processor Domains Physical domains Hybrid domains Virtual domains Party Product Account Hybrid Party Common serices Person Organization Proider Extensions Custom Extensions Extensions Custom Collaboratie Edition For the Collaboratie Edition, a component-based architecture can consist of a two-tier or three-tier configuration. The Collaboratie Edition has these components: core components, integration components, and collaboration components. The core components are as follows: An API layer A business object layer An infrastructure layer A storage layer The integration components are as follows: Custom tools Import-export Portal framework Web serices The collaboration components are as follows: InfoSphere MDM product oeriew 15

24 Data authoring UI Import-export Workflow engine Key concepts: Entity, attribute, and entity type Depending on your implementation style, the concepts of entity, attribute, and entity type reflect the technical capabilities of irtual and physical MDM. The term golden record is often used to describe the goal of proiding a 360-degree iew of your master data. While that term is sufficient in high-leel conersations, the following definitions for the deeper concepts illuminate how those concepts work within InfoSphere MDM: Entity A single unique object in the real world that is being mastered. Examples of an entity are a single person, single product, or single organization. Entity type A person, organization, object type, or concept about which information is stored. Describes the type of the information that is being mastered. An entity type typically corresponds to one or seeral related tables in database. Attribute A characteristic or trait of an entity type that describes the entity, for example, the Person entity type has the Date of Birth attribute. Record The storage representation of a row of data. Member record The representation of the entity as it is stored in indiidual source systems. Information for each member record is stored as a single record or a group of records across related database tables. Other related terms are as follows: Golden record: primarily for general, nontechnical use Aggregate record: specific use in physical MDM Party: specific use in physical MDM Various IDs: enterprise ID, entity ID, record ID, account ID, and product ID For example, an entity in irtual MDM is assembled dynamically based on the member records by using linkages and then is stored in the MDM database. Conersely, an entity in physical MDM is based on matching records from the source systems that are merged to form the single entity. The following diagrams are isual representations of the MDM concepts. The diagrams show how the concepts relate to the registry and centralized implementation styles. Virtual MDM In irtual MDM, a member record with its attributes exists in a source system. Those member records are assembled dynamically by irtual MDM to form a single entity in a composite iew (entity 1 in the following diagram). That single entity represents the golden record for that person, organization, object, or so on. After the initial configuration, business users continue to change data on the source 16 InfoSphere MDM Oeriew

25 systems. Based on configurable rules, the changes to the source system data are reflected in the entity composite iew that is stored in the MDM database. Assembled dynamically Member record 1a Member record 1c Attributes Source Source Attributes entity 1 in irtual MDM Member record 1b Member record 1d Attributes Source Source Attributes Physical MDM In physical MDM, an entity with its attributes starts in a source system. Those entities (1a, 1b, 1c, and 1d in the following diagram) are centralized by physical MDM to form a single record in the MDM database. That single record represents the golden record for that person, organization, object, or so on, where entity type 1 in the diagram represents the type of the information that is being mastered. After data from the source systems is consolidated within the MDM database, business users directly change the data in the MDM database rather than in source systems. That is in physical MDM, the MDM database is the system of record for master data. InfoSphere MDM product oeriew 17

26 entity 1a entity 1c Attributes Source Source Attributes entity 1 in physical MDM entity 1b entity 1d Attributes Source Source Attributes Data management in hybrid MDM You can maintain master data simultaneously, by using a combination of distributed data sources (aggregated through the irtual MDM) and a single, "golden record" data source (maintained in the physical MDM). This dual implementation style is often called "hybrid." Note: Hybrid MDM combines the capabilities of the irtual MDM and physical MDM. A hybrid implementation assumes that you are using the Adanced or Enterprise Edition of the InfoSphere MDM product. The Standard Edition does not include the physical MDM. Hybrid MDM uses both registry and centralized styles of managing master data. With Hybrid MDM, administrators "persist" data, meaning that they create (and then update) representations of irtual MDM person or organization entities in the physical MDM. In other words, data aggregated from the source systems of the irtual MDM are "persisted" within the centralized database of the physical MDM. Components for InfoSphere MDM In addition to the operational serer, MDM database, clients, and other parts of the primary architecture, you can use other components to achiee your MDM goals. InfoSphere MDM Application Toolkit oeriew Optimize business performance by proiding decision makers with better insight through trusted, accurate master data. Decisions are only as good as the information aailable at the time the decisions are made. When decision makers hae trust in the master data their decisions are smarter, resulting in fewer errors and better business performance. Use the InfoSphere MDM Application Toolkit for BPM to bring trusted master data into enterprise processes that run on IBM Business Process Manager. 18 InfoSphere MDM Oeriew

27 For example, you can enhance your customer onboarding process by using IBM Process Designer to display master data hierarchies to sales representaties. You can look up existing accounts to gain a comprehensie iew of your customers. With this 360-degree customer iew, you can achiee these goals: Improe customer serice Improe risk management Increase up-sell and cross-sell reenue by proiding more releant offerings The MDM Application Toolkit proides a comprehensie set of MDM-specific building blocks, including prebuilt integration serices and MDM-specific user interface controls. You can use these building blocks within the IBM Process Designer to enrich your business processes with master data. With the building blocks, the MDM Application Toolkit facilitates the rapid construction of these business processes while it remoes the integration complexity. Using the combination of the IBM Process Designer and the MDM Application Toolkit, deelopers can minimize the time that they spend working with the data. Deelopers can instead focus their time on building a robust, efficient process for use by the lines of business. The following table details whether the MDM Application Toolkit is aailable for each of the InfoSphere MDM technologies: Technology Hybrid MDM Physical MDM Virtual MDM Collaboratie MDM MDM Application Toolkit Yes Yes Yes No InfoSphere MDM Custom Domain Hub oeriew IBM InfoSphere Master Data Management Custom Domain Hub proides the tools and runtime platform to create purpose-built domains of operational master information. The hub also manages that information within a runtime serer, which is referred to as a hub instance. A hub instance role is to act as a consolidation and distribution point for shared operational data. The hub instance offers a wide range of mechanisms for receiing and sending information. Data can be sent and receied in a batch mode, trickle feed mode, or online transaction processing mode. For more information about the latest release of InfoSphere MDM Custom Domain Hub, see its documentation. InfoSphere MDM for Healthcare oeriew InfoSphere MDM for Healthcare supports patient and proider implementations in both standard and adanced editions. These prepackaged projects contain a number of artifacts (such as attributes and algorithms) for you to reuse. InfoSphere MDM product oeriew 19

28 InfoSphere MDM for Patient InfoSphere MDM for Patient is aailable in both the standard and adanced editions: Patient Standard Edition proides an optimized prebuilt configuration (attributes, algorithms, and bundled eents for the most common patent actions) to support patient data. Patient Standard Edition integrates with existing healthcare applications and is designed for ease of administration and maintenance. Patient Adanced Edition expands upon the Standard Edition where you can author and persist data attributes for adanced solutions. For example, the solutions proide patient registries for an entire health system or sere data to a health information exchange that is solely owned and managed by Patient Adanced Edition. It further shares trusted patient identities and their relationship with proiders or other members of their household with clinical and business intelligence warehouses. That intelligence can drie more accurate analytics that are required for population health cost and quality improement initiaties. InfoSphere MDM for Proider InfoSphere MDM for Proider is aailable in both the standard and adanced editions: Proider Standard Edition is an optimized prebuilt configuration for proider data. The Standard Edition supports the creation of a master irtual repository for proider data, adance relationship management, data stewardship, and enterprise data goernance. Proider Adanced Edition builds on the Standard Edition and further includes the Proider Direct user interface, adanced workflows, and supports intelligent system updates. IBM Stewardship Center oeriew Organizations can optimize their data integrity and business performance by using IBM Stewardship Center. IBM Stewardship Center proides consistent isibility, collaboration, and goernance of your master data by combining the strengths of IBM Business Process Manager and InfoSphere MDM Application Toolkit. IBM Stewardship Center includes a set of built-in process applications that are ready for immediate use to sole your data stewardship requirements. IBM Stewardship Center also includes performance metrics to monitoring how many tasks are oerdue, the task turnoer rate, among other metrics. With IBM Stewardship Center, business owners hae the assurance that master data is a trusted asset that is ready for use in their own business processes. InfoSphere MDM Policy Management oeriew With policy management, you can set, monitor, and enforce polices for quality thresholds that you want to achiee for your master data. Your master data becomes a trusted asset for consuming applications. With policy management, MDM data sources are inoled in a continuous data quality improement process. 20 InfoSphere MDM Oeriew

29 Policy management consists of these key components: policy monitoring and policy enforcement. Policy monitoring uses metrics to track the policies and determine whether the master data is in compliance with quality thresholds that you established. A set of built-in, key performance indicators (KPIs) is used to calculate data quality compliance. Built-in KPIs include completeness, consistency, uniqueness, and the rates of false positie and false negatie records. Executies, business analysts, and data stewards can use the built-in IBM Cognos reports to monitor the data quality and facilitate quality improements. You can use or extend the built-in KPIs and reports, or create KPIs and reports for your specific requirements. Policy enforcement proides the tools that are necessary to resole data quality issues that are policy iolations. Effectie data resolution often requires input from data stewards and indiiduals who know the information best, such as sales representaties and account managers. Policy enforcement proides the collaboratie capabilities that are necessary to coordinate multiple actiities across multiple roles. Policy enforcement includes a set of built-in samples for the key data stewardship tasks. You can use the built-in samples or customize the samples for your unique requirements. Use the Critical Data Change Sample to alidate new or changed data that originates from a different data source. Use the Suspected Duplicate Processing Sample to persist duplicate records or to collapse multiple records into a single entity. Use the Policy Remediation Sample to set up processes for the remediation of records that do not meet the policies for your organization. Use the Party Maintenance Sample to search for and update the attributes for a specific party. From the search results you can update and add attribute alues, and process any suspected duplicates that are associated with the party. InfoSphere MDM Reference Data Management Hub oeriew IBM InfoSphere MDM Reference Data Management Hub solution proides a single point of management and goernance for enterprise reference data. InfoSphere MDM Reference Data Management Hub proides centralized management, stewardship, and distribution of enterprise reference data. It supports defining and managing reference data as an enterprise standard. It also supports maintaining mappings between the different application-specific representations of reference data that are used within the enterprise. InfoSphere MDM Reference Data Management Hub supports formal goernance of reference data: Putting management of the reference data in the hands of the business users Reducing the burden on IT Improing the oerall quality of data that is used across the organization Key functions of InfoSphere MDM Reference Data Management Hub are as follows: Role-based user interface with security and access control Management of reference data sets and alues Management of mappings between reference data sets Import and export of reference data by using CSV and XML formats Versioning support for reference data sets and maps Change process that is controlled through configurable lifecycle management InfoSphere MDM product oeriew 21

30 Hierarchy management oer sets of reference data InfoSphere MDM Reference Data Management Hub also integrates with and complements IBM InfoSphere Business Glossary and the broader portfolio of IBM Information Management products. Definition of reference data Reference data is any data that is used to categorize other data within the enterprise. Reference data is commonly stored in the form of code tables or lookup tables, such as country codes, state codes, and gender codes. Reference data is used within eery enterprise application, from backend systems through front-end commerce applications to the data warehouse. Business users recognize reference data as code choices within the pick-lists of their business application user interfaces. 22 InfoSphere MDM Oeriew

31 Notices This information was deeloped for products and serices offered in the U.S.A. Notices This information was deeloped for products and serices offered in the U.S.A. This material may be aailable from IBM in other languages. Howeer, you may be required to own a copy of the product or product ersion in that language in order to access it. IBM may not offer the products, serices, or features discussed in this document in other countries. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user's responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drie Armonk, NY U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd , Nihonbashi-Hakozakicho, Chuo-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such proisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be Copyright IBM Corp. 2011,

32 incorporated in new editions of the publication. IBM may make improements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are proided for conenience only and do not in any manner sere as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it beliees appropriate without incurring any obligation to you. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Aenue San Jose, CA U.S.A. Such information may be aailable, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material aailable for it are proided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurements may hae been estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly aailable sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objecties only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: 24 InfoSphere MDM Oeriew

33 This information contains sample application programs in source language, which illustrate programming techniques on arious operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of deeloping, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, or function of these programs. The sample programs are proided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Each copy or any portion of these sample programs or any deriatie work, must include a copyright notice as follows: (your company name) (year). Portions of this code are deried from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights resered. If you are iewing this information softcopy, the photographs and color illustrations may not appear. Priacy Policy Considerations IBM Software products, including software as a serice solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improe the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering s use of cookies is set forth below. Depending upon the configurations deployed, this Software Offering may use session and persistent cookies that collect each user s name, user name, password, profile name, or other personally identifiable information for purposes of session management, authentication, enhanced user usability, single sign-on configuration, or web page identification that the user tried to load prior to login. These cookies can be disabled, but disabling them will also likely eliminate the functionality they enable. If the configurations deployed for this Software Offering proide you as customer the ability to collect personally identifiable information from end users ia cookies and other technologies, you should seek your own legal adice about any laws applicable to such data collection, including any requirements for notice and consent. For more information about the use of arious technologies, including cookies, for these purposes, see IBM s Priacy Policy at and IBM s Online Priacy Statement at the section entitled "Cookies, Web Beacons and Other Technologies" and the "IBM Software Products and Software-as-a-Serice Priacy Statement" at product-priacy. Notices 25

34 General statement regarding product security IBM systems and products are designed to be implemented as part of a comprehensie security approach that might require the use of other systems, products, or serices to be most effectie. A comprehensie security approach must be reiewed wheneer systems and products are added to your enironment. No IT system or product can be made completely secure, and no single product or security measure can be completely effectie in preenting improper access. IT system security inoles protecting systems and information through preention, detection, and response to improper access from within and outside your enterprise. Improper access can result in information that is altered, destroyed, or misappropriated, or can result in misuse of your systems to attack others. IBM does not warrant that systems and products are immune from the malicious or illegal conduct of any party. IBM does not beliee that any single process can be completely effectie in helping identify and address security ulnerabilities. IBM has a multilayered approach: An ongoing, internal initiatie promotes consistent adoption of security practices in deelopment of products and serices, with the goal of continually improing the quality and security characteristics of all IBM products and serices. This initiatie is described in the IBM Redguide Security in Deelopment: The IBM Secure Engineering Framework, which contains public information about software deelopment practices from IBM. Tests and scans of IBM products use arious IBM technologies to proactiely identify and remediate defects and ulnerabilities, including high or greater criticality ulnerabilities. Remediation takes place within IBM-defined response target timeframes for analysis, impact assessment, and fix deliery. The IBM Product Security Incident Response Team (PSIRT) manages the receipt, inestigation, and internal coordination of security ulnerability information that is related to IBM offerings. The IBM PSIRT team acts as a focal point that security researchers, industry groups, goernment organizations, endors, and customers can contact through the IBM PSIRT portal to report potential IBM product security ulnerabilities. This team coordinates with IBM product and solutions teams to inestigate and identify the appropriate response plan. A global supply-chain integrity program and framework proide buyers of IT products with a choice of accredited technology partners and endors in the Open Group Trusted Technology Forum (OTTF). Because security of computer systems and computer software is a ery complex issue, IBM does not proide information about deelopment practices for indiidual products other than what is found in standard product documentation or as published though IBM's public actiities. Public information about software deelopment practices recommended by IBM is documented in the IBM Secure Engineering Framework. This information is a compilation of practices from across IBM business units and deelopment teams. In most cases, published ulnerabilities are documented at timely interals through IBM Security Bulletins that include the associated Common Vulnerability Scoring System (CVSS) base score. In some cases, IBM might contact customers directly and discreetly regarding specific ulnerabilities. 26 InfoSphere MDM Oeriew

35 Customers who want to further alidate the ulnerability of IBM Software beyond the assessments that are performed internally by IBM are welcome to conduct their own scans against licensed software. They may use the tool of their choice within the existing software licensing terms. For example, scanning is acceptable, but reerse compiling or reerse engineering IBM Software is not authorized except as expressly permitted by law without the possibility of contractual waier. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and serice names might be trademarks of IBM or other companies. A current list of IBM trademarks is aailable on the web at "Copyright and trademark information" at The following terms are trademarks or registered trademarks of other companies: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Goernment Commerce. Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of Linus Toralds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Jaa and all Jaa-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. ITIL is a registered trademark, and a registered community trademark of The Minister for the Cabinet Office, and is registered in the U.S. Patent and Trademark Office. UNIX is a registered trademark of The Open Group in the United States and other countries. Notices 27

36 28 InfoSphere MDM Oeriew

37 Index A attributes 16 C case studies 3 concepts 16 customer support contacting 31 E entities 16 entity types 16 examples 3 H hybrid MDM 8 I InfoSphere MDM for Healthcare oeriew 20 InfoSphere MDM for Patient 20 InfoSphere MDM for Proider 20 InfoSphere MDM Reference Data Management Hub oeriew 21 S scenarios 3 software serices contacting 31 support customer 31 T technical capabilities 8 trademarks list of 23 U use cases 3 user roles 6 user stories 3 V irtual MDM 8 L legal notices 23 M master data definition 1 MDM definition 1 O oeriew master data 1 MDM 1 P personas 6 physical MDM 8 policy management 21 R RDM oeriew 21 reference data oeriew 21 roles 6 Copyright IBM Corp. 2011,

38 30 InfoSphere MDM Oeriew

39 Contacting IBM You can contact IBM for customer support, software serices, product information, and general information. You also can proide feedback to IBM about products and documentation. The following table lists resources for customer support, software serices, training, and product and solutions information. Table 7. IBM resources Resource Description and location Product documentation for InfoSphere MDM You can search and browse across the InfoSphere MDM documents at knowledgecenter/sswsr9_ Product documentation for InfoSphere MDM Custom Domain Hub, including InfoSphere MDM Reference Data Management IBM Support Portal Software serices My IBM Training and certification IBM representaties You can search and browse across the InfoSphere MDM Custom Domain Hub documents at support/knowledgecenter/sslsqh_ You can customize support information by choosing the products and the topics that interest you at You can find information about software, IT, and business consulting serices, on the solutions site at businesssolutions/. You can manage links to IBM web sites and information that meet your specific technical support needs by creating an account on the My IBM site at You can learn about technical training and education serices designed for indiiduals, companies, and public organizations to acquire, maintain, and optimize their IT skills at You can contact an IBM representatie to learn about solutions at Proiding feedback The following table describes how to proide feedback to IBM about products and product documentation. Table 8. Proiding feedback to IBM Type of feedback Product feedback Action You can proide general product feedback through the Consumability Surey at studies/consumabilitywebform.htm. Copyright IBM Corp. 2011,

40 Table 8. Proiding feedback to IBM (continued) Type of feedback Action Documentation feedback To comment on the product documentation: Click Add Comment on the topic in IBM Knowledge Center Click the Feedback link on the topic in IBM Knowledge Center Use the online reader comment form: Send an 32 InfoSphere MDM Oeriew

41

42 Printed in USA SC