Configuring Coordinated Control

Configuring Coordinated Control


An admin user selects one or more Trigger Groups (group of occupancy sensors) to control one or more Coordination Nodes (occupancy-sensing or not). For more, please review the Coordinated Control Overview article.
Info
Coordinated Control is only available to Admin level users.

Create a new Coordinated Control

  1. Open the Administration Console, and click on Coordinated Control
  2. Click New to create a new Coordinated Control
  3. Enter a descriptive Name for the new Coordinated Control
  4. Create at least one Trigger Group of occupancy sensing nodes:
    1. Select one or more Trigger Nodes (occupancy sensing) on the map preview
    2. Define the Trigger Criteria - the threshold number of Trigger Nodes that must be in the active occupancy state for the Trigger Group to be active

  5. If desired, click the + button to create additional Trigger Groups
    1. If using multiple Trigger Groups, select whether Any one trigger group or All  trigger groups must be active for the Coordination Nodes to be activated
  6. Select the desired Coordination Nodes
    1. Coordination Nodes may contain occupancy-sensing and non-occupancy-sensing nodes


  7. Add an optional Timeout - The Timeout parameter is the amount of time for which the Coordination Nodes remain active after the Trigger Groups are inactive (below Trigger Criteria) - this time is in addition to the timeout of the Trigger Node’s existing Task Tune settings. The Coordinated Control timeout overrides the Task Tune timeout when nodes enter the active state due to Coordinated Control.
  8. Click Save

Notes
The Trigger Criteria tooltip provides a brief explanation of the Coordinated Control behavior.
Info
Coordination Nodes will time out to their Inactive Task Tune and Automatic Setback levels based on their Trigger Nodes’ SiteWorx Tune settings and the Coordinated Control timeout
Info
Trigger Nodes switch between the active and inactive occupancy states based upon the occupancy events detected by the motion sensor as well as the timeout of the Trigger Node’s existing Task Tune settings. For example if a Trigger Group consists of an aisle and all sensors in the aisle have a 5 minute timeout in Task Tune settings, if someone walks down the aisle each node will remain active occupancy state for 5 minutes after occupancy is detected. Thus if the person walks through the aisle and exits in less than the Task Tune timeout of 5 minutes, then all sensors in the aisle would simultaneously be in the active occupancy state for a period of time until the 5 minute Task Tune timeout expires on each individual ligh