Appendix A. BACnet AWS and OWS Supervisors

Table of Contents

A.. BACnet OWS and AWS Supervisors overview
- AWS and OWS Supervisor module and license requirements
  - BACnet AWS Supervisor requirements
  - BACnet OWS Supervisor requirements
A.. BACnet AWS Supervisor features
A.. BACnet OWS Supervisor features
- Bacnet Ows Device Manager
  - Event Information
  - Enrollment Summary
- Additional BACnet OWS Supervisor features
A.. Converting to a BACnet AWS or OWS Supervisor station
- Converting from a BACnet Supervisor (BacnetWsNetwork)
  - Notes on a converted BACnet Supervisor station
- Converting from a BACnet OWS Supervisor to a BACnet AWS Supervisor
  - Notes on a converted BACnet OWS Supervisor station

Concurrent with this document update in the AX-3.6 timeframe, and starting in a maintenance release of AX-3.6, there are now two BTL^[1]-certified BACnet Supervisor products:

BACnet AWS Supervisor — A specially licensed Supervisor that provides client supervisory access and control of BACnet devices, as a BACnet “Advanced Operator Workstation” (B-AWS).
BACnet OWS Supervisor — A specially licensed Supervisor that provides client access and control of BACnet devices, as a BACnet “Operator Workstation” (B-OWS).

A BACnet AWS Supervisor or BACnet OWS Supervisor lets you interact with BACnet devices from a supervisory standpoint, as described in the BACnet Specification for the B-AWS or B-OWS device profiles. Each Supervisor includes most of the same functionality as the regular NiagaraAX BACnet driver, as described in other sections of this document.

At the time of this document, one exception is that neither the BACnet AWS or BACnet OWS Supervisor is licensed for “server side” (BACnet export) of objects, unlike the regular NiagaraAX BACnet driver that runs on a JACE, or the previous “BACnet Supervisor” product. Typically this is not an issue, as a BACnet workstation’s purpose is to be the ultimate “authoritative client” to all other BACnet devices.

Note that each product above requires a Windows PC platform running AX-3.6 or later, and uses a different licensing scheme (and Niagara modules) than the previous BACnet Supervisor product, described in another appendix. That previous BACnet Supervisor (based on the now-deprecated bacnetws module), adheres to the B-OWS device profile—however, it is not BTL-certified.

Because of the new bacnetAws and bacnetOws module scheme, an existing BACnet Supervisor station database (using the BacnetWsNetwork from the bacnetws module) is not directly upgradable to run as a BACnet AWS Supervisor or BACnet OWS Supervisor. However, an “offline conversion utility” is provided in the bacnetAws and bacnetOws modules. This utility converts the saved station database (config.bog) of a previous BACnet Supervisor to one compatible with one of the new Supervisor types. See Converting to a BACnet AWS or OWS Supervisor station, and also the leading Note in the appendix about the BACnet Supervisor.

This appendix describes the additional features and functionality specific to a BACnet AWS Supervisor and BACnet OWS Supervisor, and has the following main sections:

^[1]BTL is BACnet Testing Laboratories, where BTL certification means the product/device was tested by an official BACnet Testing Laboratory to certify its BACnet PICS (Protocol Implementation Conformance Statement).