IBM InfoSphere Master Data Management, Version 11.3In many organizations, efficiency and accuracy depend on understanding the household relationship between individuals that are managed within the enterprise. The MDM operational server can establish household relationships that are based on the comparison and match of a physical location.
The MDM operational server manages entities that are based on whether an entity type is configured to be transitive or non-transitive. As a reminder:
The householding feature is built on non-transitive entity processing. All records in the entity must match above the auto-link threshold with every other record in the set, and members can belong to only one household entity at a time. Household addresses must be an exact match to link. It is important to understand that the single entity membership rule applies only within an entity type. If you are a member of a household entity, you can also be a member of an identity entity.
Both the Entity Linker and Relationship Linker processes come into play for householding. The Entity Linker process initially forms a household entity after comparison of the address and other attributes result in records that score above the auto-link threshold. Entity rules are not created for household entities. The Relationship Linker then processes the records by using the defined relationship rules and establishes an implicit relationship (that is, the relationship exists by common membership) between identity and household entities. In the InfoSphere® MDM Inspector application, the household relationship would be noted by the relationship type of “lives in.” Initial links and relationships are created in batch-mode, while subsequent maintenance is handled in real time.
Tasks are not created for household entities. Manual linking and unlinking of household entities is not supported.
The following components are used to implement and use the householding feature: