In order to use the virtual MDM module and physical MDM
module together in a hybrid MDM implementation, certain expectations
exist for the data and interactions.
In a hybrid MDM implementation:
- Data quality is a key factor in dictating whether you fully persist
customer profiles. For more information this topic, see the link to Preparing
data for hybrid MDM at the end of this topic.
- Data ownership matters. You are combining two fundamentally different
styles of master data management. As a step in combining those styles
you must decide whether the source system or the master data management
system should be the system of record for an attribute. It cannot
be both at the same time. For more information on data ownership and
the management of supplemental attributes, please see the link to Accounting
for supplemental attributes at the end of this topic.
Other important notes:
- The hybrid MDM implementation supports a hybrid model for the
Person and Organization business objects as defined in the physical
MDM schemas. However, by default hybrid MDM does not provide support
for maintaining relationships in virtual MDM and subsequently persisting
them to physical MDM. Relationships include party-to-party, party-to-contract/party-to-account,
party-to-product, hierarchies, and groupings.
- Data stewardship for a hybrid MDM solution currently requires
the use of two tools:
- The InfoSphere® MDM
Inspector manages virtual MDM attributes.
- The Data Stewardship UI (DSUI) manages physical MDM attributes.
There is not currently a single data stewardship user interface
that manages both virtual MDM and physical MDM attributes.
- The hybrid MDM implementation requires some customization to support
the data survivorship processing of supplemental attributes.
- And finally, the InfoSphere MDM Workbench does not currently provide
a tool to convert a virtual MDM project into a hybrid MDM project.
IBM InfoSphere Master Data Management, Version 11.3