This replicates container structure in the JACE station from the “network downwards”, that is, below the network (but including the device). Using the following station slot path value (for both PxViewTags and PointTags) can provide consistent results.

slot:points/%networkFolderPath%

For example, consider a JACE station with a BacnetNetwork that has an architecture like this:

The JACE station has a PxView on the device component “EastWing”—a Px view that you are exporting. If you add a PxViewTag on EastWing, and set its slot path to:

slot:points/%networkFolderPath%

Upon a Join, this results in the following folder structure under the Supervisor’s NiagaraNetwork:

Assuming this slot path did not already exist because of other PointTags, or by previous manual definiton via the “profile.bog” file in the JACE, the EastWing component created in the Supervisor is a standard “folder” component. As a result, it not visible in the Supervisor’s Niagara Point Manager view.

To improve this, it is recommended to use a PointTag on at least one proxy point of the device with the PxViewTag. In this case, the EastWing folder (above) is deleted in the Supervisor station.

Then in the JACE station, a PointTag is added to the “RetAir” point under the “AHU2” points folder, with its “Station Slot Path” property configured as: slot:points/%networkFolderPath%

Following another Join, because of the PointTag, all folders used to replicate the container structure are Niagara Point Folders, including the “EastWing” container with the SubstitutePxView, as shown above. Everything is now visible in the Niagara Point Manager view. Note this also allows you to manually add more proxy points at a later time, if ever desired.

If all PxViewTags and PointTags use a Station Slot Path “slot:points/%networkFolderPath%” value, this can keep everything exported to the Supervisor in the same (or at least similar) hierarchy as it is in the JACE station. It also can save export tag editing time when duplicating a “template” device to create all of the devices in the station.

This replicates container structure in the JACE station from the “device downwards”, that is, below the device component (but not including the device). For example, with the same station example described in the previous “%networkFolderPath%” section, if you added the following station slot path to both the PxViewTag on the BACnet “EastWing” device and also on a PointTag for one of its proxy points:

slot:points/%deviceFolderPath%

This results in the following folder structure under the Supervisor’s NiagaraNetwork:

This is typically less desirable than using the “%networkFolderPath%” variable appended to “slot:points/”, because all device-level Px views get “stacked” onto the NiagaraStation’s Points device extension. However, if devices are engineered in the JACE using many point folders, perhaps with PxViews on those point folders (instead of on device components), this may be a useful alternative.

See %networkFolderPath% for a more universal example.

This BFormat entry applies more to PxViewTag usage outside of any “points context”, as it creates a folder named the same as the parent of the export tag. For example, if the JACE station has a folder “Setpoints” with a PxViewTag added and configured with the following Station Slot Path:

slot:%parent.name%

or

slot:%parent.name%/this/that

where this and that are manually-entered slot paths, this is equivalent to entering

slot:Setpoints

or

slot:Setpoints/this/that

depending on the structure of the system. In this case, the “Setpoints” folder (with SubstitutePxView) will be created in the root of the NiagaraStation component that represents this JACE station.