Hierarchies are based on the tags and relations associated with each object (device, point and component). Tags tell the system,
for example, that a specific device is located in a specific building and that a specific point belongs to a specific piece
of equipment. The HierarchyService uses this contextual information to set up the structure for individual hierarchies.
All types of tags may be used to structure hierarchies, including implied (default) tags, such as n:device and n:point as well as Haystack dictionary tags (tags that begin with hs:), custom-built dictionary tags, and Ad Hoc tags that you might create when tagging components in the station. You do not
have to create a custom tag dictionary to use Ad Hoc tags, they can be created as needed. Although, using tags in a tag dictionary
ensures consistency which typically yields better results.
Before creating one or more hierarchies, configure your devices with the tags that will yield the hierarchies that you need.
NOTE: As a convenience, you can fine tune a hierarchy by editing the tags on a component where it appears in the Hierarchy space,
rather than navigating to the component in the station logic. Whether your changes are made in the station logic or in the
Hierarchy space, they are applied to the same component.