Hierarchy Manager addresses the challenges of managing data in enterprise systems through a reliable source of unified views that capture the many relationships between customers and related entities across and within business units.

Hierarchy Manager builds on Informatica MDM and the repository managed by the MDM Hub, so that it can leverage MDM metadata management capabilities, such as history or lineage. Hierarchy Manager delivers reliable and consolidated customer relationship views, enabling businesses to view, navigate, analyze, and manage relationships across multiple hierarchies, and across disparate applications and data sources. Hierarchy Manager defines the relationships, affiliations, and hierarchies among various entities (such as individual to organization, organization to organization, or individuals within households). In addition, Hierarchy Manager allow you to create new relationships between the existing entities, as business conditions change.

The way that Hierarchy Manager approaches relationship data consolidation makes it easy for you to add relationship data from new sources without the need for additional programming. The consolidated relationship data can be used by downstream applications or written back to other sources. The Hierarchy Manager console provides a user interface that allows relationship stewards (data stewards tasked with managing relationships and hierarchies) to navigate among multiple entities and hierarchies, at several levels of abstraction. Multiple

cross-application

hierarchies (such as Oracle) can be combined and reflected in one place, giving Hierarchy Manager the ability to produce the only unifying repository of hierarchy data.

Hierarchy Manager defines and manipulates both transactional data and master data during its transactions.

Transactional data

Typically representing actions of one application, transactional data is usually maintained in one system, and includes (for example) banking actions involved in withdrawals, deposits, and transfers of funds

Master data (also known as reference data)

Typically composed of common, core entities and their attributes and values, master data is usually maintained in two or more system that might not communicate with one another.

For example, information about a person who opens a checking account and savings account at different times might be kept in two different systems, making it more difficult to manage customer information across the entire bank system.