Scenarios show how you might use the various editions of InfoSphere® MDM to
master data and improve data governance.
The following examples list only a few of the ways that you might
take advantage of the different editions of InfoSphere MDM.
Which edition and features you use typically depends on your requirements
and environment. The scenarios describe options for meeting requirements
for particular environments. But because InfoSphere MDM is
flexible and configurable, you might use a different edition or different
features to achieve similar business or organizational goals. These
scenarios consider a few key industries as examples, however 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 Advanced Edition or
InfoSphere Master
Data Management Enterprise Edition,
you deploy MDM either as a registry implementation or as a centralized
implementation. In Advanced and Enterprise Editions, you can have
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 virtual MDM capabilities to match and merge.
- You also use physical MDM capabilities to persist and augment
a defined enterprise view with more centrally managed information.
Patient data from multiple clinics
With
InfoSphere Master
Data Management Standard Edition,
a regional healthcare organization allows its individual 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 government regulations do not allow healthcare organizations
to modify the data that is provided by clinics. Therefore, the organization
cannot consolidate source records into a single physical record that
happens with a centralized implementation style. The registry style
provides a complete view 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:
- The MDM architect uses the Patient Hub to quickly
set up an MDM environment as a registry implementation.
- 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 virtual view of each patient.
- Customer service representatives and clinic staff use InfoSphere MDM Inspector, InfoSphere MDM Flexible Search,
and InfoSphere MDM Enterprise Viewer to
perform data stewardship activities.
- Application developers create custom business process flows for
business analysts to analyze and improve 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 Advanced 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 relatively static (for
example, coverage 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 survivorship. The
company expects to integrate new data sources gradually over time.
How
it works:
- The MDM architect starts with the default party domain to model
the insurance customers and to set up the MDM environment in a centralized
implementation style.
- The MDM architect and data steward can augment the built-in capabilities
by developing extensions and additions.
For example, the company might develop an extension to populate a
new field that contains only the last 4 digits of a 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.
- Local agents and call-center agents access a single view of a
customer with the Data Stewardship UI so
they can improve cross- and up-sell opportunities.
- Business analysts review customers’ coverage under multiple
policies by using IBM® Cognos® reports.
Single view of citizens for government agencies
With
InfoSphere Master
Data Management Advanced Edition,
a government agency creates a single view 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:
- The MDM architect starts with the party domain to build
a model of persons of interest and to set up the MDM environment in
a centralized implementation style.
- The MDM architect and data steward can augment the built-in capabilities
by developing extensions and additions.
- The MDM architect generates a feed into an InfoSphere Identity Insight system
for party actions, such as updates, additions, and deletions.
- Application developers create custom user interfaces with the InfoSphere MDM Application Toolkit so
that government employees can view the person data.
Consistent product information for the retail industry
With
InfoSphere Master
Data Management Collaborative 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 vendors, manufacturers, and internal teams, such
as sales and marketing.
Customer-centric initiative for financial services
With
InfoSphere Master
Data Management Enterprise Edition,
a financial services company recently added new products. The company
wants to offer them to customers of its recent acquisition, a regional
bank.
How it works:
- The MDM architect consolidates the company's existing customers
with its new regional bank’s customers, while the architect
allows the regional bank to 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.
- Data stewards and business analysts ensure compliance with regulations
such as privacy controls, Basel
accords, and tax compliance.
- 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.
- With collaborative authoring of
bundled offerings, business users centrally manage bundles, check
eligibility or pricing, make updates, and detect violations of terms
and conditions.
IBM InfoSphere Master Data Management, Version 11.3