For purposes of this discussion, the term portability means reusability. In other words, being able to use the same Px View
in different stations without having to edit the ORD properties for bindings and hyperlinks. Another example of portability,
is being able to use the same Px view in a controller station and a
The floor plan graphic shown below has a bound label configured with a hyperlink to a detailed graphic for a specific device. You can see that both the ord binding and hyperlink properties use an absolute ord, meaning the value specifies the entire station slot path.

If you wanted to use the same floor plan graphic in the
station:|slot:/Drivers/NiagaraNetwork/VA/Richmond/myController/points/FirstFloor/AHU1
station:|slot:/Drivers/LonNetwork/FirstFloor/points/FirstFloor/SpaceTemp
Here, you have the same scenario but in this case using relative ORDs instead of absolute ORDs.

The same relative ORDs can be used in both the JACE and the
The following example, the user has hyperlinked from the floor plan graphic to a more detailed graphic of the air handling unit (AHU). This detailed AHU graphic includes a button that is a hyperlink back to the floor plan graphic (FirstFloor). The button hyperlink is configured with an absolute ORD.

In order to use the above graphic in the Supervisor station, you must use NiagaraNetwork proxy points and assign a Px view or by using a Px view export tag.
The absolute ORD to the First Floor graphic in the JACE is different from that in the
station:|slot:/Drivers/LonNetwork/FirstFloor
station:|slot:/Drivers/NiagaraNetwork/VA/Richmond/myController/points/FirstFloor
Using relative ORD properties, it is possible to navigate back up the tree by entering two periods in the path, similar to how directories can be navigated in a DOS command window.
..”.

slot:..
station:|slot:/Drivers/LonNetwork/FirstFloor/AHU1
station:|slot:/Drivers/NiagaraNetwork/VA/Richmond/myController/points/FirstFloor/AHU1