IBM Analytics White paper
IBM Industry Models and IBM Master Data Management
Positioning and Deployment Patterns 2 IBM Industry Models and IBM Master Data Management
Introduction Although the value of implementing Master Data Management (MDM) • The Joint Value Proposition summarizes the scenarios in which solutions is widely acknowledged, it is challenging for organizations IBM Industry Models and MDM accelerate projects and bring to realize the promised value. While there are many reasons for this, value. ranging from organizational alignment to siloed system architecture, • Positioning of IBM MDM and IBM Industry Models explains, by certain patterns have been proven to dramatically increase the success using the IBM reference architecture, where each product brings rates of successful projects. value, and how they work together. • IBM Industry Models and MDM deployment options describes The first of these patterns, which is not unique to MDM projects, is the different reasons for which IBM Industry Models are that the most successful projects are tightly aligned with a clear, concise implemented, and how IBM Industry Models are used together business value. Beyond this, MDM projects create challenges to an with IBM MDM in implementing a solution. organization along several lines. • A comparison of IBM Industry Models and MDM discusses the similarities and differences in structure and content of IBM • MDM is a business application that acts like infrastructure. Industry Models and IBM MDM. Organizations need to learn what this means to them and how they are going to adapt to it. This document is intended for any staff involved in planning for or • Although MDM projects might not start with data governance, implementing a joint IBM Industry Models and MDM initiative within they quickly encounter it. MDM projects provide focus on their organization, including IT Architects, Enterprise Architects and what aspects of governance are required for the project’s value Business Analysts. proposition. • Mastering data implies that there are business processes concerned with establishing and maintaining the quality of that data. • For MDM programs to be truly successful, they need to use a service-oriented architecture.
IBM’s experience is that industry-specific models can help organizations with the last three points, once they have identified the specific value proposition to be delivered by the project. This white paper explains what MDM is, what IBM® Industry Models are, and how the combination of the two can significantly improve the targeted value realization and can reduce project durations and overall costs.
This document contains the following:
Figure 1. MDM strategic components IBM Analytics 3
IBM Master Data Management Overview By providing a single view of people, products, services and more, IBM InfoSphere® Master Data Management is the most complete, MDM enhances strategic decision making across an organization. The proven and powerful MDM solution with collaborative and operational quality of that data shapes the decisions that are made and ultimately capabilities. affects everything from customer relationships and regulatory compliance to business agility and competitiveness. Master data is the information about customers, products, materials, accounts and other entities that is critical to the operation of the • Service-oriented architecture delivers functionality through business. But companies hold pieces of master data in many different intelligent, pre-packaged web services that can be used to applications, such as enterprise resource planning (ERP) and customer seamlessly integrate MDM into existing business processes and relationship management (CRM) systems. Each of those source systems technical architectures. creates and holds the data in its own unique way. As a result, information • Pre-built and extensible data models for any domain are does not match from one system to the next. Critical data elements optimized for MDM; an organization can import existing data might be missing, duplicated or inconsistent. Furthermore, each models or build data models from scratch. department can operate only from within its own compartmentalized • Collaborative tasks allow workflows to be set up that reflect view. existing and new business processes, delivering a system that closely aligns with business practices. IBM InfoSphere MDM software manages the creation, maintenance, • Business process management capabilities enable the delivery and use of master data, both to ensure that it is consistent and implementation of policies and coordinate multi-step / multi-role trustworthy, and to make it possible to see the data in an organization- workflows for data stewardship and data governance on-premises, wide context. in the cloud, and bridging between on-premises and cloud. • Policy management ensures high quality master data using a quantitative, probabilistic approach to monitoring and enforcing policies. • InfoSphere Governance Center allows business users, data stewards, and IT teams to collaboratively improve master data quality by resolving data quality tasks and creating master data in compliance with corporate governance policies. • InfoSphere MDM Application Toolkit delivers business value rapidly with governance applications through pre-built blueprints and widgets for embedding within existing applications. • Common matching and search engine employs advanced statistical techniques to automatically resolve and manage data quality issues using probabilistic or deterministic options.
Figure 2. Logical view of the MDM Hub 4 IBM Industry Models and IBM Master Data Management
IBM InfoSphere MDM Standard and Advanced Editions (MDM IBM Industry Models Overview Operational Server) deliver single, trusted and complete versions of IBM Industry Models provide predefined data model industry content critical data assets and their relationships to applications and users to for banking, financial markets, telecommunications, healthcare, support efficient operational business processes and strategic decision insurance, retail and energy & utilities. The main components of the making. MDM helps clients in many industries share information data model are: across multiple systems to improve the services they provide to patients, citizens and customers. Business Terms Business terms define industry concepts in plain business language, with IBM InfoSphere MDM Collaborative Edition (MDM Collaboration no modeling or abstraction involved. Business terms have a standard set Server) manages master product data to maintain a single view of of properties and are organized by business category. Clearly defined product information for use throughout an organization and as part of a business terms help standardization and communication within an comprehensive MDM strategy. organization.
IBM InfoSphere MDM Reference Data Management Hub (RDM) is a Supportive Content robust MDM solution for centralized management and distribution of Supportive Content represents data elements in the language of a given reference data across the enterprise. (Reference data is static data, such source requirement. For example, requirements such as Health Level as code tables, used to classify business entities – for example, salutation, 7 (HL7), which is the standard series of predefined data formats for gender, country code). It provides the governance, process, security and packaging and exchanging healthcare data in the form of messages that audit control for managing reference data as an enterprise standard, are transmitted between disparate IT systems, or BASEL, which defines resulting in fewer errors, reduced business risk and cost savings. the capital requirements for banks.
IBM InfoSphere Big Match for Hadoop helps analyze large volumes of Analytical Requirements structured and unstructured data to derive deeper customer insight on a Analytical Requirements reflect the most common queries and analyses Big Data platform. for business performance measurement and reporting. They help with the rapid scoping and prototyping of data marts, which provide a subject-specific analytical layer in a data warehouse solution. IBM Analytics 5
Business Data Model (BDM) Dimensional Warehouse Model (DWM) The Business Data Model is the first point at which the various The Dimensional Warehouse Model is a logical model that is derived business requirements are brought together and modeled in an entity from the BDM and is an optimized data repository for supporting relationship format. It helps organizations to perform the initial analytical queries. This repository holds data to meet the needs of modeling of their business requirements and understand the various business-user-required analyses. constraints, relationships and structures that can be implied in their business requirements.
Atomic Warehouse Model (AWM) The Atomic Warehouse Model is a logical, specialized model that is derived from the BDM. It is optimized as a data repository, which can hold long-term history, usually across the entire enterprise in a flexible manner.
Figure 3. IBM Industry Model components 6 IBM Industry Models and IBM Master Data Management
In the case of Banking, Financial Markets and Insurance, IBM Industry Analysis Process Model (APM) Process and Services Models are also available. This extended landscape The Analysis Process Model provides the initial Business specification consists of the following model components: of processes, which is used to underpin the initial analysis activities in determining the optimum subset of processes for a Project, from a Business Object Model (BOM) business perspective. The Business Object Model is the first point at which the various business requirements are brought together and modeled in UML. The Orchestration Process Model (OPM) BOM is essentially the UML equivalent of the BDM and performs the The Orchestration Process Model Provides the design level technical same role and provides technology independent class models that enable specification of processes, which forms the basis for any downstream traceability between automated business process requirements and implementation of executable processes. downstream SOA IT analysis representation. In all industries, the Business Vocabulary provides a common semantic Interface Design Model (IDM) reference point across the different Data, Process and Services domains. The Interface Design Model provides a design for the development All of the models in these three different technical domains (analytical, of components, types, interfaces, and data transfer objects for an process and service) are mapped to the equivalent business terms in the enterprise-wide business services-based architecture. Business Vocabulary.
Services Design Model (SDM) The Services Design Model provides a design for the development of participants, service interfaces, and messages appropriate for an enterprise-wide business services-based architecture.
Figure 4. How IBM Industry Model components relate to each other in an analytics landscape IBM Analytics 7
Joint Value Proposition
The provision of a broader enterprise context is a fundamental overall The Business Terms that are provided by IBM Industry Models provide value proposition for using the IBM Industry Models with IBM a canonical set of data elements that are expressed in the language that is MDM. This wide cross-LOB scope of IBM Industry Models providing commonly used by business users. With the Business Terms as a starting semantic and structural consistency is complementary to the deep point, all of the information elements in the organization (whether focus that MDM applications provide to specific subject areas such as owned by MDM or other systems) can be understood, related to other Customer and Product. elements, and managed.
As mentioned earlier, the IBM Industry Models help MDM projects Industry Models also help accelerate the focus of a project. When along three strategic lines: delivering an analytics project, for example, the Analytical Requirements provide the requirements for a set of KPIs that will be used to measure • Although MDM projects might not start with data governance, progress towards achieving business value. The Analytical Requirements they quickly encounter it. MDM projects provide focus on identify the business objects required, which can then be traced down what aspects of governance are required for the project’s value to the critical attributes within logical and physical systems. Specific proposition – the area of Data Governance. data governance rules can be created based on the importance of each • Mastering data implies that there are business processes around attribute having one of a defined set of values. establishing and maintaining the quality of that data – the area of Business Processes. IBM Industry Models also provide a logical data structure of the objects • For master data programs to be truly successful, they need to use in scope for a project. The result is that the project team obtains a a service-oriented architecture more complete description of what will be involved in delivering the business value, with a logical data model helping them organize how Addressing the Main Business Issues these objects are related, and complete definitions with examples to Let’s dive down more deeply into each of the 3 main MDM project ensure that there is a common and accurate definition of the objects issues that are mentioned above, and the benefits that a well thought out themselves. and exercised model brings: The benefits of using IBM Industry Models to help drive the data Data Governance governance process are: While there is a common understanding of the need for data governance, most companies encounter challenges figuring out where • A business-led understanding of the information within the to start. In an MDM project, the value proposition of the first project organization, bringing together a semantic map of all information helps bring focus from a broad topic with thousands of attributes to a elements within the organization, whatever their role in the much more focused and manageable set. Some of these attributes might organization. be owned by MDM and some by other systems or the Enterprise Data • Significantly reduced time to describe the required business Warehouse (EDW). objects and underlying attributes. 8 IBM Industry Models and IBM Master Data Management
• Complete definitions of both what it takes to deliver business A key factor underpinning successful SOA is a common, enterprise- value, as well as the supporting objects, provide focus on what wide description of business concepts and processes of interest to a is important, further reducing both high-level design as well as financial institution. Without this common language, any attempt to testing. support a consistent and flexible architecture will more than likely fail. IBM Industry Services Models provide this common language and • Complete definitions also reduce or eliminate discovery – which also support a complete and unambiguous description of the business can often happen late during the testing process, and which can services that are required to support the organization. The Service add months to a project. Models enable the efficient and accurate gathering of requirements, and • The ability to generate both the supporting EDW structures as guarantees the consistency of definitions with a single integration effort well as specific star configurations required for a focused set of or across multiple projects. analytics.
The Service Models are tightly coupled with the Process Models, Business Process describing the underlying services that support these processes at run One of the keys to understanding and mastering data is knowing time. Using the Service Models, business concepts can be traced from exactly what the business processes are which create and change that analysis level through design level refinements to actual component and information – in other words, optimized business processes that support message definitions that provide a quick start for the specification of the complete lifecycle of the information within an organization. common services within the organization. IBM Industry Process Models provide ready-made processes and services that are constructed with customer focus, without the need to To summarize, the synergies between IBM Industry Models and reinvent from scratch. The integration and consistency of the business InfoSphere MDM are: processes provide extensive re-usability of activities and processes, and translate into less process maintenance and reduced training costs, • IBM Industry Models provide a set of business terms which while enabling flexibility in the workforce. The customizable generic provide a business context for the information that is mastered by process templates enable an organization to meet its specific project InfoSphere MDM. requirements. • Analytical Requirements provide the business requirements for Service Oriented Architecture areas of analysis for which the business community requires A Service-oriented architecture (SOA), as a common basis for support. Each element in these templates is related to elements integration and as a means of structuring large-scale software in an EDW or data lake/reservoir design, and can be related architectures, is rapidly becoming the backbone of the modern financial to elements of information that are mastered by using IBM institution. An SOA can increase the speed of business changes, improve InfoSphere MDM. business efficiency and performance, as well as protect the privacy and • IBM Industry Process Models provide a business context for the security of critical information assets. An SOA enables IT to align more information that is created and updated by business operations, tightly with business strategies in a cost-effective manner and in a secure and is maintained by IBM InfoSphere MDM. and managed integration environment. • IBM Industry Services Models provide a linkage from business processes that are defined in the process models, to the underlying services that can be provided by IBM InfoSphere MDM –allowing a translation of the “to-be” best practice business processes into implemented SOA-based services for master data. IBM Analytics 9
Positioning in an Analytics Landscape
The IBM Analytics Landscape The specific positioning of these MDM capabilities are shown in Figure Figure 5 shows the relevant subset of a possible overall Analytics 6, using a subset of the standard components in the IBM Data Reservoir Landscape. This landscape will be used to frame the relative placement Logical Architecture. of the various IBM MDM and IBM Industry Model components that are described in this document, and is known as the IBM Data Reservoir The Virtual MDM capability is considered part of the Information Reference Architecture. You can find additional information on IBM Views. The Information Definitions of simplified subsets of Data Reservoir in the IBM Redbook Designing and Operating a Data information that is stored in the data reservoir repositories. These views Reservoir. are created with the information consumer in mind.
IBM MDM Positioning The Physical MDM capability is part of the Asset Hub, which is defined There are three main IBM MDM components that need to be as slowly changing operational master data (information assets) such as positioned with the IBM Industry Models in the context of a typical customer profiles, product definitions and contracts. The Asset Hub Data Reservoir landscape. These three components are: provides authoritative operational master data for the service interfaces, real-time analytics and for data validation in data ingestion. It is a • Virtual MDM reference repository of the operational MDM systems but can also be • Physical MDM extended with new attributes that are maintained by the reservoir. • MDM services The MDM Services are positioned within the Services Interfaces component and they provide a standard programmable interface for accessing the data that is stored in the MDM Asset Hub.
Figure 5. IBM Analytics Landscape 10 IBM Industry Models and IBM Master Data Management
Figure 6. Positioning on IBM MDM in the IBM Analytics Landscape
Figure 7. Deployment paths for IBM Industry Models IBM Analytics 11
IBM Industry Models Positioning IBM Industry Models and IBM MDM Mappings Typically IBM Industry Models are design-time artifacts and are used IBM provides a series of predefined attribute level mappings between to underpin the related development activities. In general, a number of the relevant components of IBM Industry Models, the MDM physical IBM Industry Model components deploy into this physical landscape. data model and the MDM Services Layer. These mappings provide an Figure 7 outlines the main deployment paths for IBM Industry Models indication of where the same or equivalent data and services elements exist between IBM Industry Models and IBM MDM. Shown in Figure 1 The Business Vocabulary content, usually stored in InfoSphere 8. Information Governance Catalog are deployed into the Catalog component. The three different types of mappings are shown in the above diagram. 2 The Atomic Warehouse Model provides a key design point for These mappings are intended to provide an accelerator to clients the overall logical data warehouse and so deploys to a number of wanting to have a combined deployment of IBM MDM and runtime components. artifacts that are derived from IBM Industry Models. The three types of - The traditional relational Information Warehouse component. mappings are: - The usually Hadoop-based Deep Data component - Potentially used to deploy Operational History 1 Mapping between Business Terms and the MDM physical 3 The Dimensional Warehouse Models would provide much of the data model. This mapping would be useful in establishing an design content for the Reporting Data Marts. In addition, where overall information governance based on a common glossary or a client is looking to deploy a Kimball dimensional warehouse taxonomy of business terms that includes linkage to the physical they might also use the Dimensional Warehouse Models to MDM components, in addition to possibly other components. deploy a dimensional variant of the information warehouse. 2 Mapping between the Atomic Warehouse Model and the MDM 4 The Service Design Model provides the basis for enforcing a physical data model. This mapping is intended to provide common standardized basis for the deployment of the Services guidance to clients wanting to establish an overall ETL layer that are used by the Real-time Interfaces. that includes IBM MDM and an IBM Industry Models-derived Information Warehouse as target data structures. 3 Mapping between the Service Design Model and the MDM services layer. This mapping is intended to provide guidance on possible linkage between IBM Industry Models-derived runtime services and the MDM Services layer. 12 IBM Industry Models and IBM Master Data Management
Figure 8. Mappings between IBM Industry Models and IBM MDM IBM Analytics 13
Deployment Options
This chapter explains some typical use cases in which IBM Industry A significant advantage of this tool is that this is used as the source Models and IBM MDM are deployed – and why those use cases are of of business terms both at design time and run time. The Business benefit. Vocabulary can be mapped to the various physical assets and be used to underpin data lineage activities. IBM Industry Models Deployment Options Optionally, the Business, Atomic and Dimensional models can also be Business Vocabulary loaded into the Catalog to provide further context or lineage. In this scenario, the customer uses part or all of the Business Vocabulary component of IBM Industry Models to provide the central semantic Data Warehouse Deployment reference point for multiple projects. In addition, customers might turn For many customers, this is a core deployment use case of IBM industry to using the Business Vocabulary in the face of the growing and more data warehouse models. It relates to the use of the data warehouse diverse nature of the overall runtime landscape. design models (Atomic Warehouse and Dimensional Warehouse) to deploy the required runtime data warehouse artifacts. In this case, some or all of the Business Vocabulary is deployed in the Catalog component, usually in the IBM InfoSphere Governance In this deployment scenario, a client can choose to adopt either an Catalog tool. Inmon relational approach in which case they will focus their attention on the Atomic Warehouse Model. They can also use the Dimensional Warehouse Model to provide a downstream layer to support any user interaction.
Alternatively the client might choose to adopt a Kimball approach and center their development on the Dimensional Warehouse Model and deploy a single dimensional warehouse layer. This has the advantage of being a simpler deployment option but might sacrifice some of the flexibility of the Inmon approach
Another consideration that might guide deployment choice is the advent of Hadoop based Deep Data structures being used to augment traditional the Information Warehouse. Currently, the Atomic Warehouse Model is validated for deployment to the IBM BigInsights Hadoop solution.
This data warehouse deployment option can also be used with the Business Vocabulary deployment option.
Figure 9. Business Vocabulary deployment 14 IBM Industry Models and IBM Master Data Management
Combined IBM Industry Models and IBM MDM Deployment Options The possible combined deployment of the IBM Industry Models and IBM MDM on this overall landscape can be described by the following:
• Integrated Data Governance • Integrated Services deployment
Combined Governance of MDM and IBM Industry Models derived components Both IBM Industry Models and IBM MDM products are key to providing some of the core components of the centralized set of data reservoir repositories. With that in mind, the ability to enforce a workable approach to the overall governance of these assets is critical to the ongoing long-term exploitation of these assets.
Exploiting the pre-built integration between IBM Industry Models and Figure 10. Data Warehouse deployment IBM MDM is important in ensuring that a combined approach to this overall information governance landscape is achieved. Services Deployment
The third deployment option that is relevant to IBM MDM is the Figure 12 outlines how the main components of IBM MDM and those deployment of SOA Services. Traditionally this deployment option derived from IBM Industry Models can be considered as part of an occurs where the UML interface Services Design Model in a tool like integrated set of governed assets. IBM Rational Software Architect is used as the basis for the generation of the relevant services run-time artifacts such as XSD, WSDL, etc. The core to this is the Catalog, the location in which all of the metadata that is needed to describe the various repository components is stored. The catalog can provide a single viewpoint of all of the components.
1 The Catalog itself can store a layer of Business Terms, where the overall environment is described in the language of the business and in a means that is independent from the specific technologies. The catalog will also store detailed metadata that describes each of the relevant data reservoir components and how they relate to each other. 2 The linkages between the Catalog elements and the MDM Asset Hub. This would be heavily influenced by the mappings between the Business Terms and the MDM physical model.
Figure 11. Services deployment IBM Analytics 15
Figure 12. IBM MDM and Industry Model components as part of an integrated set of governed assets.
Model example: Implementing a Business Intelligence solution for 3 In this landscape, where the Information Warehouse and any Customer Profiling associated Reporting Data Marts are derived from the IBM Industry Models, then such physical artifacts would also inherit As part of their customer intelligence solution, Bank ABC wants to any linkages that existed between their equivalent logical models understand their customer base. and the Business Terms in the Catalog. The business analyst consults the content of the Analytical 4 Potentially some deep data. In some cases such stores can be Requirements. Under the focus area “Relationship Marketing”, they derived from IBM Industry Models, in which case these artifacts find the Analytical Requirement “Individual customer profile”. might also be included in the overall set of components subject to such an information governance approach.
In addition to providing the metadata of the components, the catalog should also provide a view of any relationships that exist between the various components.
This linkage between the Business Term, the Data Warehouse Model(s) and the MDM physical model enables a common information governance approach to be built out including IBM Industry Model derived assets and IBM MDM components.
Figure 13. Example - Individual Customer Profile 16 IBM Industry Models and IBM Master Data Management
The Analytical Requirement Individual Customer Profile includes The mappings to the Atomic Warehouse show where in the EDW a number of measures and dimensions that are used to analyze the design support for Gender can be found: demographics of the financial institution’s customer base:
Figure 16. Example - Gender
The corresponding MDM attribute can be found by consulting the Figure 14. Example - Measures and Dimensions MDM/Industry Data Model for Banking (Banking Data Warehouse) mapping spreadsheet, which is available to licensed customers of both MDM and IBM Industry Model products: This provides a starting point for designing a data mart to support analysis: To summarize, this use case shows:
• Banking Data Warehouse models a source of analytics design. • The ability to find (and customize if required) the logical structure to support the analytics. • The ability to determine how to support elements of the analysis in an EDW. • The ability to find the master data that will provide the source for the analysis, by using the MDM/Banking Data Warehouse model mappings.
Figure 15. Example - Designing a data mart
Let’s take an example of Gender to see where this can be mastered.
Figure 17. Example - MDM mappings IBM Analytics 17
Combined MDM and IBM Industry Models services deployment The approach of using Adaptive Service Interface (ASI) for adapting The IBM MDM product also includes a services layer that provides MDM interfaces to adhere to IBM Industry Model definitions can a standard interface to enable a consistent and robust access to the provide some performance benefits over the approach of using an ESB MDM data by other applications. Given that IBM Industry Models for to perform the same mapping in cases when several sequential calls to Insurance and Banking include models that would be used to enable the MDM is required for full business function. Solution developers can generation of a services layer typically for use by Systems of Record and create composite transactions using MDM business proxy capabilities. Systems of engagement, then a services-related deployment pattern is possible. Model Example : Implementing a Business Process using the IBM Industry Models Process and Service Model and MDM services As part of their commitment to enterprise process engineering, and with a focus that is driven by new regulatory requirements in this area, Fund Manager Company XYZ has decided to examine their customer onboarding procedures.
In order to find the relevant processes to examine, the Value Chains are reviewed. The Value Chains present Line of Business functions that are supported by a set of long-running business processes.
In this case, KYC and Account Opening is the most relevant:
Figure 18. Example - Services deployment
IBM Service Design Models can provide the basis for the services layer both for the Systems of Record and Systems of Engagement (item (1) in the diagram) as well as providing the services layer for certain data artifacts in the System of Insight (2).
The MDM Services Layer and any services that are generated from IBM Industry Models can be used to together as part of an overall ESB environment.
Alternatively, IBM MDM Services could be adapted to use service layer definitions from IBM Industry Models using MDM Adaptive Service Interface functionality. MDM provides the ability to map externally defined service interfaces to internal MDM service and business object Figure 19. Example - Value Chains definitions. In essence, MDM could be “taught” to “speak” the language of the Service Design Model for subset of services that are used in MDM deployment. 18 IBM Industry Models and IBM Master Data Management
Figure 20. Example - Process
This provides the context for the process modeler to home in on relevant processes, including “Administer IP Onboarding”. The process modeler opens the Analysis Process Model in Rational System Architect (RSA), for example, and examines the process:
For each of the activities in the process workflow diagram, the model provides an understanding of the data inputs and outputs, and the end to end process flow. The company can choose to customize the process elements, reviewing their granularity and potentially introducing new process activities or subprocesses.
A key element of analyzing the business processes in the APM is determining which activities are service candidates, i.e. are candidates for automation – these are the process steps that can ultimately be supported by a set of common services, such as provided by IBM InfoSphere MDM. Figure 21. Example - Retrieve Full Customer Details For Service Candidate activities, the next step is to identify the relevant Service Capability Operation in the Business Object Model (BOM), which is the analysis-level services model.
Taking “Retrieve Full Customer Details” as an example, the corresponding BOM Service Capability Operation, of the same name, is found in the “Involved Party Management” Capability:
And, examining the Relationships that the “Retrieve Full Customer Details” Operation has, shows the association in the design-level Service Design Model (SDM): Figure 22. Example - Service Design Model IBM Analytics 19
Figure 23. Example - MDM Mappings
Following the link from the BOM Operation leads to the To summarize, this use case shows: “retrieveFullCustomerDetails” SDM Service Operation, under the “IInvolvedPartyManagement” ServiceInterface: • IBM Industry Model for Banking as a source of process and service analysis The corresponding MDM attribute can be found by consulting the • The ability to find (and customize if required) the relevant model MDM/BPS mapping spreadsheet. elements in scope • The ability to find the master data that will provide the source for Model Example: Mapping the Service Design Model to MDM the analysis, by using the MDM/IBM Industry Model mappings services Building further on the example that is mentioned in previous section, solution developers can use MDM Adaptive Service Interface feature to map “recordInvolvedParty” service interface that is defined by IBM Industry Models to addParty MDM service. An example of such mapping is provided as part of MDM distribution package.
Figure 24. Example - Service Operation Figure 25. Example - Service Design Model mapping 20 IBM Industry Models and IBM Master Data Management
A Comparison of IBM Industry Models and IBM MDM
Scope of the MDM and IBM Industry Models The main difference in domain coverage is in the breadth of coverage of The IBM InfoSphere MDM data model represents the persistence IBM Industry Models. The scope of IBM Industry Models is to provide store on which MDM services operate, retrieving data through services an enterprise-wide view of all of the information in the organization, and updating this data through services. It is structured to meet MDM and thus to integrate the potentially many operational master systems needs, which are best provided through the identification of information that exist in a given organization. There might be a different master for domains. MDM defines three major domains of Party, Product and ledger information, and both of these sources are integrated by using Account, which are represented in the DOMAIN model. IBM Industry Models. On the other hand, MDM masters only aspects The following shows the main entities that are included in the Party of Party, Agreement and Product that are common across multiple Domain: business processes in organization.
Both the banking and insurance IBM Industry Models support the three Another difference in IBM Industry Models is the approach to data domains of MDM. In the case of insurance, since the development quality. of MDM was highly influenced by the IMB Industry Models for Insurance, the naming of concepts are largely similar. In the case of MDM ensures information about the same party that is updated banking, there is also a high level of overlap in these domains, although simultaneously from potentially a large number of consuming the names might differ – for example, IBM Industry Models for Banking applications will be cleansed and de-duplicated inside MDM using uses “Involved Party” for MDM’s “Party”. sophisticated probabilistic matching engine, therefore always ensuring the best quality.
As a data warehouse model, IBM Industry Models assume a level of cleansing before data is accepted into the warehouse database, so there is, by design, any inbuilt tolerance of duplication.
Data Model Similarities and Differences MDM represents both a logical and a physical model; the physical model needs to be stable and predetermined as a basis for data retrieval through services, optimized for operational access pattern. IBM Industry Models are purely logical models, which are open to customization, and Figure 26. Main entities in the Party domain can be implemented on a variety of both traditional DBMSs and less traditional environments, such as Hadoop. IBM Analytics 21
One difference that ensues from this is the approach to customizations MDM Package IIW Package to the model. In the case of MDM, there are two main approaches – Product Product hard persistence involves changes to the model and underlying database, Account Agreement with potential changes being required to associated services. The soft
Some of the MDM elements are internal application administration and
IBM MDM provides a solution for ensuring that the critical core data that is referenced and updated by multiple systems within an © Copyright IBM Corporation 2015 organization is appropriately governed. It provides persistence structures and services to allow these core elements to be managed centrally and IBM Corporation effectively. IBM Analytics Route 100 Somers, NY 10589 IBM Industry Models provide a context of this core information within a logical map of all of the concepts that an organization must manage. Produced in the United States of America They also provide an analytical reason for the use of the information September 2015 that is managed by IBM MDM. IBM Industry Process and Service Models provide the business context for the need for IBM MDM IBM, InfoSphere and the IBM logo are trademarks of International Business services. Machines Corporation in the United States, other countries, or both.
Other company, product or service names may be trademarks or service marks of Together IBM MDM and IBM Industry Models provide analysis and others. A current list of IBM trademarks is available on the web at “Copyright and implementation of both core operational information and the analytical trademark information” at. ibm.com/legal/copytrade/shtml. structures that will allow the business to be managed. This document is current as of the initial date of publication and may be changed by IBM at any time. Not all offerings are available in every country in which IBM operates.
THE INFORMATION IN THIS DOCUMENT IS PROVIDED “AS-IS” WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT. IBM products are warranted according to the terms and conditions of the agreements under which they are provided.
The client is responsible for ensuring compliance with laws and regulations applicable to it. IBM does not provide legal advice or represent or warrant its services or products will ensure that the client is in compliance with any law or regulation.
Please Recycle
IMW14850-USEN-00