User Manual

Graphics Builder
Overview
5
A6V11604297_en--_e
63 | 196
Binding query
Type of binding
Description
baUniqueId
Fixed for a specific application on a specific system
device.
● Query stays constant within a device unless the
application structure is changed.
● Useful for one-time solutions.
semantic tags
Can be reused with similar applications and other
system devices.
Query can be used across systems and is extensible
by individual libraries.
shortName
Can be reused with similar applications and other
system devices.
Query is proprietary to a system.
navName
Fixed for a specific application on a specific system
device.
Query can be engineered to be reused.
Table 15: Types of GRAPHIC ON binding queries.
Occasionally, you may want to add additional tags to the GRAPHIC ON query so that the graphic is recognized
in more locations of the building hierarchy. For example, when you view the GRAPHIC ON query for a plant,
you find that it only contains the equip tag. This tag alone is insufficient to identify a specific data point in the
database.
● Manually adjusting the GRAPHIC ON query maintains the relative data point binding.
● You may need to add tags that are not automatically used for this query, such as navName.
● You may need to add an engineering notation that uniquely identifies the data point.
Engineering notations [➙ 52]
Using Relative by navName binding
Depending on the structure of an application for a BACnet/IP system, it may be possible to create graphics with
Relative by navName binding that can be reused. In this case, navName is the point or equip name that
displays in the Desigo Control Point List view and Plant view. You can verify the navName by displaying
the magic bubbles for an object. For more information, see the Verifying relative binding queries [➙ 67] section.
Note
The discussion in this section assumes the following:
● Data points are not structured according to a building hierarchy. That is, all points may belong directly to a
site object, or many points may belong to just a few equip objects.
● Your application consistently uses a naming convention that allows an equip or point to be uniquely
identified. The naming convention may be applied consistently from Plant-to-Plant on the same device, or in
the application structure shared from device-to-device.
Workflow Step
1
Configuring the binding options
2
Verifying the object binding
Prerequisites
● The procedure Discover and assign devices [➙ 15] is complete.
● A graphic has been created according to the procedure Adding a graphic [➙ 36].
● The graphic has been saved at the point in the building hierarchy where it will be opened for viewing. For
example, a room segment graphic has been created and saved at a room segment in the building hierarchy.