CHeKT is proud to announce the public release of the Automation Rules. When this function is enabled, the integrator is granted access to a wide range of new site-level functions that can create a unique, custom experience for their client. Need the customer's gate to close any time the system is armed? What about trigger talk down when an alarm is detected on a specific camera? All of these combinations (and many more) are now available. The conditions can even be set dependent on the arming status of the bridge or time of day. Below, we have included an example of configuring the bridge to Automate Talkdown based on a camera trigger as an example, but this is only one of the many functions that can be programmed.

Access to the Automation Rules in the CHeKT Portal is a premium feature, and requires that the respective Dealer Account be upgraded to one of the CHeKT Premier Plans. Contact your Central Station or CHeKT Sales Representative for upgrade inquiries.

Enabling Automation Rules

1. Camera Triggered: rule will be initiated when the selected camera channel is activated. This activation could by way of a DI alarm, Analytic Event Message or local API Call. 
   
2. Time Triggered: rule will be activated at a programmed start time
   
3. System State Changes: Used to initiate a rule on a given event.
   
1. When site is armed: Rule will be initiated by arming the system.
   
2. When site is disarmed: Rule will be initiated by disarming system.
   
3. When Site Entry Delay Begins: Rule will be initiated at the start of the Site Entry Timer (normally initiated by opening an entry / exit zone while armed).
   
4. When Site Exit Delay Begins: Rule will be initiated at the start of the Site Exit Timer (normally initiated when a system with an entry/exit zone is armed).
   
5. When Site System Alarm Begins: Rule will be initiated when the site enters an alarm condition (such as violating an instant zone when armed, or allowing an entry timer to expire without a disarm).
   
4. System Status: Rule will follow a status constantly, as opposed to just on initiation.
1. While Site is armed: As long as the site is armed, the rule is activated.
   
2. While site is disarmed: As long as the site is disarmed, the rule is activated. 
   
3. During System Entry Delay: As long as the site entry timer is active, the rule will be activated. 
   
1. Example: If the entry delay on a site is programmed for 60s, the user can expect the rule to activate from the moment they violate the entry zone until the disarm comes in or the 60 second timer ends,  whichever comes first)
   
4. During System Exit: As long as the site Exit timer is active, the rule will be activated
   
5. While Site in Alarm: As long as the site is in alarm condition (the time defined under bell timer), the rule will be active.
   
5. Monitoring Portal
   
1. Opened: Will initiate the rule at the time the monitoring portal is opened.
   
2. While open: Rule will be active as long as the monitoring portal remains open.

Camera Triggered alarm source can be Digital Input or Analytic Event Topics. Local API Alarms will also work to initiate the rule.

Select the Camera(s) that will initiate the rule. 

Once the Cameras are selected, hit Next.

Step 2 is where the Action is defined. The action is what will take place when the Source Event takes place and the rule is activated.

Actions:

1. Talkdown: Initiate an audio broadcast. 
   
1. Users can choose a message from the pre-defined site options to play out of any or all speakers a selected number of times.
   
2. IP Speakers and Bridge Audio Outputs are listed individually
   
2. Record Video (20s) : Generate a 20s non-alarm video clip from a selected camera or cameras.
   
3. 2-minute Pre Recording : Generate a 2-minute non-alarm video clip from the selected camera or cameras. 
   
1. The clip will be the two minutes up to the moment the request is made
   

CHeKT will already create the 20s MP4 video clip in the event of an alarm condition before automated rules are in play. Keep this is mind when setting up automated rules to create video clips; additional video data uploaded can make the operator response less efficient.

1. Relay: Activate the hardware relay on the Bridge 
   
1. Relays must be enabled to be used in automated rules
   
2. For source events such as camera triggered and status changes, the relay can be set to engage a momentary trigger defined in configuration wizard
   
3. For events such as System Status since the condition is designed to follow, latch is the only programming option. 
   
2. HTTP Request: Create a local web request to another device on the network. 
   
1.  Click here for more information on HTTP Requests
   
2. Ensure the device you are making the request to is on the same Local Area Network as your Bridge.

For our example rule, we will select Talkdown:

After selecting Talkdown as the action, select the message this rule will play, choose the speaker and define the number of repetitions:

In Automation Bridge Speaker are speakers connected to the Bridge Hardware via the audio input jack. IP speakers hold their own identity and will be listed as with the label used when they were mounted to a Bridge.

1. Time: Users can configure a time-frame for the rule to activate. The rule will only initiate if the source event occurs during the programmed time frame.
   
2. System Status: 
   
1. While Armed: Rule will only initiate if the source event occurs while the system is armed
   
2.  While Disarmed: Rule will only initiate if the source event occurs while the system is disarmed
   
3. During System Entry: Rule will only initiate if source event occurs while the System Entry Timer is active
   
4. During System Exit: Rule will only initiate if source event occurs while the System Exit Timer is active
   
5. While in Alarm: Rule will only initiate if source event occurs while the System Bell Timer is active.
   
6. AI Operator: 
   
1. This new feature will allow the user to define whether the rule should wait for the AI determination from the selected Provider.
   

Note that when AI Operator is enabled, the rules will take an extra ~5-10 seconds to activate while awaiting the AI determination. 

Click Next:

Users will see a green success message on successful rule creation

Always test newly added rules for proper and expected function.