You can add these tags directly to station components and set their value manually to the ID of the entity to which they refer. If the ID of that referenced entity changes, the values of these ref tags must be manually updated. Alternatively, Niagara relations can be used. For ref def subtypes except for ID, a relation is added to the dictionary. These relations are exported by the nhaystack service as ref tags with their value set to the ID of the relation endpoint.

The Niagara configuration file also defines tag rules that imply smart equipRef, spaceRef, and siteRef relations. The smart equipRef relation works exactly as the Haystack 3 version, which is that an outbound relation is implied from non-null proxy points to a component ancestor with the equip tag and inbound relations are implied from that ancestor back to the points.

Unlike Tridium’s Haystack 3 tag dictionary, the equip tag is not implied on all BDevices, so it needs to be added where appropriate.

If an equip component has a spaceRef relation to a space component, the smart spaceRef relation will imply outbound spaceRef relations from that equip’s points to that space and will imply inbound relations from the space component back to those points.

If an equip or space component has a siteRef relation to a site component, the smart siteRef relation will imply outbound siteRef relations from the sub-equips, sub-spaces, and equip points to that site and will imply inbound relations from the site component back to those items. The following figure shows an automatically generated hierarchy based upon these implied smart relations.