Tag-Based Graphics in Niagara 4.9+ (Haystack)

Problem

Graphics tied to absolute ORDs break when devices are moved or renamed. Need a more portable, semantic approach.

Solution

1. Leverage Haystack Tags for Dynamic Bindings

• Instead of binding to >jace:niagara:~/floor3/Room_305/damper, bind using tags
• Example: Bind damper graphic to any object tagged with vav + damper + zone tags
• When you move the device or rename the folder, the graphic still works

2. Use Niagara 4.9+ Tag-Based Expressions

In PX binding, use query strings that find points based on tags:

^find( tag("vav") && tag("damper") )

Returns any damper under the parent that's part of a VAV. No path-specific references needed.

3. Set Up Auto-Tagging via Point Naming

• Configure Tag Rules so points named vav_xyz_damper automatically receive vav, damper tags
• Graphics work across multiple systems without manual intervention

4. Create a Tag-Based Graphic Template

• Design one "generic VAV" graphic that works for all VAVs
• Bindings use semantic queries instead of ORDs
• Deploy to every location—graphics auto-adapt based on tags

Benefits

• Graphics are truly portable and vendor-agnostic
• Renaming/moving devices doesn't break graphics
• Faster on-site deployment: copy template, tag new devices, graphics appear