Problem

Building individual graphics for each device is time-consuming and hard to maintain when hundreds of similar devices exist.

Solution

1. Use Relative ORD Bindings (Not Absolute)

• Instead of hardcoding >jace:niagara:~/folder/AHU_01/supplyTemp, use relative bindings
• Bind to parent object properties (e.g., ^ for parent, .. for grandparent)
• This allows the same graphic to be copied and used for AHU_02, AHU_03, etc., automatically

2. Create PX Includes for Reusable Components

• Build a library of common widgets: setpoint adjuster, status indicator, command button
• Reference these includes in multiple graphics instead of recreating them
• Update the include once and all references update automatically

3. Use the Batch Editor for Mass Deployment

• After creating a template graphic, use the Batch Editor to copy it to all matching devices
• Bind the copies to the correct folder ORDs with one action
• Reduces manual work from hours to minutes

4. Enforce Consistent Point Naming

• All AHUs should have identical point names: supplyTemp, returnTemp, damperPos, etc.
• This allows smart, pattern-based bindings across your entire site
• Use Haystack tagging to enforce naming standards automatically

5. Organize Graphics by Folder Hierarchy

• Store folder-tied graphics (tied to a location folder) rather than individual device graphics
• A single "AHU" graphic can serve all 50 AHUs if properly parameterized
• New devices automatically inherit folder graphics

6. Example Workflow

• Create one master "AHU.px" graphic bound to >supplyTemp, >returnTemp, etc.
• Tie this graphic to the generic AHU folder template
• When new AHUs are added to the system, they automatically show the correct graphic with correct bindings