Introduction

The page discusses the creation of a security rule, and an action if that rule is broken by the tracks.

Contents

Overview

Rules stipulate the parameters of acceptable track behaviours, and are critical to the creation of Alarms. Once the Radar data has been processed through the tracker channels and shaped by the tracking parameters, the resulting interpreted output is fed into the Rules Engine. It is here that decisions are made according to a series of rule definitions that separate potential incidents.

Rules consist of basic conditions, such as:

• ‘If a target enters this area then sound an alarm’, or

• ‘If a target is moving faster than 4 metres per second then follow it with a camera’.

Further details on Rules are available here: Rules.

Creating a New Security Rule

To create a Security Rule:

1. Enable the Config Function, then select an entity - for instance, the Rules folder.
   
   

   Open

   

    

2. In the Configuration Panel, select New, and then Rule.
   
   

   Open

   

    

3. The Security Rule Wizard will appear in a new window. Name the Security Rule, and choose a Rule Type - a Custom or a Defined Rule.
   
   

   Open

   

    

4. In this example, a defined rule is selected. These rules are pre-populated, with an existing template, and are therefore a simpler choice for a first rule. Select Next.
   
   

   Open

   

    

5. Given this rule requires assignation to an area, either an existing area can selected or a New Area created for the rule. If New Area is selected, an area with the same name as the rule will immediately appear on the PPI Map ready for further configuration.
   
   

   Open

   

    

6. Now you can define further properties to the rule. The basic Area Movement Rule would be broken if a track entered the specified Area. But additional parameters can be set - for instance, a speed limit must also be surpassed within the area to break the rule. Configure the options, then select Next.
   
   

   Open

   

    

7. Finally, the Break Allowance, Priority and Severity must be set:
   
   

   Open

   

    

   Break Allowance: Defines how many times a track must break a rule before an action is triggered.

   Priority: Allows you to optionally apply a ‘weighting’ to any rules that invoke an action using comparative values.

   Severity: Defines how a target should be marked when it breaks a rule. Such markings allow a target to be easily differentiated. A Threat severity triggers both 'Alarm' and 'Camera Follows' actions.
   
   

8. Select Finish. The new rule will appear in the Configuration Tree:
   
   

   Open

   

Related Information