Index | Prev | Next

Setting up a hierarchy definition

This procedure demonstrates the steps to define a hierarchy to easily navigate to Air Handler Units in a specific building in order to monitor child points and performance.
Prerequisites:
  • The hierarchy and tagdictionary modules must be installed on your system.
  • The hierarchy palette is open in the side bar.
  • All devices, points and other components are already tagged and any necessary relations already added.
  • A plan for the desired navigation hierarchy already determined during preliminary preparations. For more details see the section, Preliminary preparations.
Shown here is the modelled site structure (left) and the resulting navigation hierarchy (right).
Image
Perform the following steps:
  1. Navigate to the station’s Config > Services node in the Nav tree and double-click the HierarchyService.
    The Hierarchy Service Property Sheet displays in the right pane.
  2. Drag and drop the Hierarchy component from the palette side bar to the Hierarchy Service Property Sheet (or to HierarchyService node in the Nav tree), and in the Name dialog enter the hierarchy name: “AHU Points” and click OK.
    The new hierarchy definition appears in the Hierarchy Service Property Sheet and under the HierarchyService in the Nav tree.
  3. In the right pane, click on AHU Points to open it’s property sheet.
  4. Click to expand the Scope and Station properties and enter the following Scope ORD: station:|slot:/Model/Westerre/W1.

    This Scope ORD causes the query to search only this specific location within the station. An alternative to limiting the scope is to use additional LevelDefs.

  5. Click and drag a QueryLevelDef component from the hierarchy palette to the AHU Points Property Sheet and in the Name dialog enter “Device” and click OK.
  6. In the property sheet, click to expand the new Device level definition and perform the following action:
    Property name Action
    Query Enter: n:device and nBld:ahu to return any objects tagged with n:device and nBld:ahu.
     NOTE: Typically, you identify the tags applied to AHUs in the station and make note of them, by examining tags on one or more of these devices during preliminary preparations. Without prior knowledge, you need to examine the devices to determine how they are tagged or to apply tags. 
  7. Click and drag a RelationLevelDef component from the hierarchy palette to the AHU Points Property Sheet and in the Name dialog enter “Points” and click OK.
  8. In the property sheet, click to expand the new Points level definition and perform the following actions:
    Property name Action
    Outbound Relation Ids Enter: n:childPoint to return any child point components.
    Filter Expression Enter additional tags to filter results: hs:air or nBld:temp to return any objects tagged with either hs:air or nBld:temp.
    Repeat Relation Select: true
  9. Click Save.
  10. In the Nav tree, right-click the Hierarchy space, select Refresh Tree Node, and expand the nodes to view the resulting AHU Points hierarchy.

Example: AHU Points hierarchy definition

Image
 NOTE: In Niagara 4.3 and later, there is added support for multiple relation IDs on a single relation level definition. You can enter more than one comma separated tagID in the Inbound Relation Ids or Outbound Relation Ids properties. The results for any of these relation IDs display in the hierarchy. 

Related Links

  • Common hierarchy tasks (Parent Topic)

    • Index | Prev | Next