An intertwining and complex network of relationships can be difficult to work with. To simplify this process, the data should be filtered according to specific business concerns and organized by relationships, and data components should be placed in context to each other. In the following example, the data has been filtered and structured to display the sphere of influence of John Lewis, the father in the family whose data is shown in the previous section.

With

HM

you can do the sorting, filtering, and managing that results in this kind of easily accessed, comprehensive data arrangement. From the new data arrangement John Lewis’ relationships are more clearly discerned. These relationships are enclosed within the red line and are summarized in red type in the figure above. John has a relationship with his wife (Alice) and his daughter (Amy Miller). He has three types of accounts: DDA, credit card, and mutual fund. He is associated with two organizations: Heart Association of America, and John’s Sporting Goods, where he is also employed.

The data depicted in "Challenges of Managing Data in Enterprise Systems" could be viewed according to different business interests. Each business interest (for example, mutual funds company) could have their own customer view, their own applications, and their own data stores. This type of arrangement requires different hierarchies. The following examples show possible business unit hierarchies that capture important customer relationships, and that can be created in HM:

Territory (Geographic-to-Account)
Profitability (Product-to-Client)
Contracts (Division-to-Client)
Purchasing (Organization-to-Organization)