Building control integration
By associating an integration ID with the access right exercised by a person when they enter an access zone, the system can automatically turn on lights and the building’s HVAC system.
Integration IDs link an access right to the building’s control logic. As an option for any access right, an administrator creates a unique integration ID (name and integer value) and assigns it to an access right. When a person exercises the access right to enter the building, the integration ID integer value is available to the building control logic. The integration ID value may be used, along with a valid badge value to initiate HVAC and lighting controls for the areas appropriate to the person or group that is represented by the integration ID.
true or false state that defaults to false until an authorized, active badge is swiped at an appropriate reader. When this occurs, the property status changes to true momentarily (2 seconds by default). This property is only available in
An access right may contain only one integration ID. Since many persons may share an access right, they also share the access right integration ID. Therefore, access rights with integration IDs are typically defined and named in terms of the common physical location that persons occupy.
For example, two access rights: Acme West and Acme East might relate to two sides of a single floor in the Acme building. Persons with different access rights may enter the building through a common door and actually have the same overall access to the building. However, if the different access rights contain unique integration IDs, they can trigger building controls to turn on lighting in the west side offices for the west side occupants and the east offices for east side occupants, as appropriate.
Figure 15. Niagara Integration ID
ValidBadge=True and IntegrationID=AcmeWest[1] property values from the system (possibly over a BACnet network) and the building control logic triggers a boolean control
to turn on the west-side office lights.