Introduction
This rule checks to see if a track has moved from Area 1 to Area 2. There is no time associated with this check and it relies on the track Id being maintained between the areas. Typically this is a very effective way to check where a track has entered a site. You can specify that if a track has come through an area and moved into a secure area that it was either an unauthorised or authorised route and raise an alarm as required.
Contents
Configuration
Nodes
Input
Track Sighting Input https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/1874853893/Rule+Inputs#Track-Sighting-Input
Checks
Area Check 1 https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/1866498140/Rule+Checks#Area-Check
We use the AnyTime option on this area check which means this check will evaluate to true if the track has at any time passed through this area, it does not need to be in the area at the time of the check.
Area Check 2
This check is Now, which means the track must be in this area at the point this check evaluated.
Link
Boolean Link: And https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/1866498140/Rule+Checks#Boolean-Link
Actions
Alarm https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/1874854150/Rule+Actions#Alarm
Camera https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/1874854150/Rule+Actions#Camera
PPI Example
However, if the a track only enters one Area, then no alarm is raised:
Related Information
-
Sections (Witness 4.0)
-
Lanes (Witness 4.0)
-
Rule Areas (Witness 4.0)
-
Alarm Areas (Witness 4.0)
-
Alarms (Witness 4.0)
-
Rule Nodes (Witness 4.0)
-
Rules (Witness 4.0)
-
Creating a Rule (Witness 4.0)
-
Static Sensor (Witness 4.0)
-
Rule Schedules (Witness 4.0)
-
Breach Lines (Witness 4.0)
-
Entity Timeouts (Witness 4.0)
-
Camera Controllers (Witness 4.0)
-
AdvanceGuardĀ® Configuration (Witness 4.0)
-
Adding Cameras (Witness 4.0)