Hierarchy modules
A hierarchy is an organization of records that are connected to each other in a special way. One record is chosen to be the root of the hierarchy. Other records are connected directly to the root. Other records may be connected to those. The following figure is an example of a hierarchy organization.

There are a few points about the hierarchy that is shown in the figure that are important to notice.
- The hierarchy contains more than one kind of record, but all records must be from the same module. This is common. However, it is not necessary for a hierarchy to contain more than one kind of record.
- A record can appear in only one place in a hierarchy. The same record cannot appear in more than one place in a hierarchy.
- Except for the record at the root of a hierarchy, every record in a hierarchy has exactly one parent. The record at the root of the hierarchy has no parent.
- A record in a hierarchy can have any number of children.
- It may be possible for two records in the hierarchy to have the same name, but records with the same parent cannot have the same name. The hierarchy in the figure has a country that is named Georgia and a state that is named Georgia. They are represented in the hierarchy by two different kinds of records with two different parents that have the same name.
Figure 1 explains what a hierarchy is. IBM® Maximo® Real Estate and Facilities does not display a hierarchy that way. The following figure shows how the platform displays a hierarchy.

To improve the performance in hierarchy trees with many children, only the first 1000 children display along with an informational message 1000 results displayed. Use Manager Queries to view more. Child records to the nodes that are not displayed in the hierarchy tree can be added by opening the record from the Master/Detail Query and using the Includes tab. The Includes tab displays the tree from the record being shown.