Routes are what guards follow when they patrol sites. Every route is defined for a single site (it cannot cover more than one site). There are two ways you can open a route list:
In both lists, you can create a new route and edit or remove an existing one.
Every route has the following properties:
There are two types of routes:
Simple route is a set of checkpoints. A guard has a defined amount of time to pass all of them, without any particular order. See Patrol failed alarms below, for details on patrol completion and failure.
Simple route’s definition consists of:
Below the checkpoints list, there are options to clear the list and to add new checkpoints. Choosing the latter opens a list of all checkpoints connected with the site. You can select one or more (using ctrl and shift keys) and then choose Select to add them to the route.
NOTE: Saving a route definition (checkpoints list) does not mean it is stored in the database. You have to save the whole route to make any changes permanent.
Advanced route is a list of checkpoints. A guard has to pass each of them at a defined point in time. See Patrol failed alarms below, for details on patrol completion and failure.
Advanced route’s definition consists of a list of checkpoints. For every checkpoint there are the following fields and options:
Below the checkpoints list, there are the same Clear and Add new options as in the simple route definition panel (see above).
The Tag Missed event type applies to the unrepeated tag. It does not cause an alarm.
SLA is a percentage threshold of passed checkpoints. This feature allows you to specify how many percent of tags can be omitted from the path for the patrol to complete. It is valid only for advanced routes.
The Failed to Start alarm event determines how many minutes after the start of the route until the first tag is not reflected, the route will receive the FAILED_TO_START status.
There are two types of route schedules:
All times in a schedule are expressed in the site time zone (see Sites for more information on site time zone).
The Every X days schedule has the following fields:
In the bottom left corner of the panel, there is an option to clear Hours and Hours after midnight fields.
Above the schedule fields, there is an automatic times generator. You set time when you want patrols to start (Time from), time when you want them to end (Time to) and how often you want a patrol (every … minutes). After you choose Generate, generated times are appended to Hours and Hours after midnight fields. The latter is used when Time from is later then Time to.
The Days of the week schedule has a times list for every day of the week (semicolon-separated, expressed in a 24-hour clock, like Hours in the Every X days schedule).
The clear option at the bottom and the automatic times generator at the top are also available.
In the times generator, you can choose days of the week for which the generated times will be appended. If Time from is later then Time to, times after midnight are appended to the next day of the week.
ActiveView generates a patrol failed alarm if a guard does not pass a checkpoint he/she is supposed to. When exactly a guard should pass a checkpoint depends on the route type, definition (checkpoints list) and schedule.
For a simple route, every time a patrol starts according to schedule, a guard has the “overall route time” to pass all the checkpoints. If he/she passes them before that time, the patrol is considered completed. If he/she does not, a patrol failed alarm is generated after the “overall route time” from the patrol’s start.
For an advanced route, every time a patrol starts according to schedule, a guard has to pass all the checkpoints at defined times.
If he/she passes the first checkpoint after checkpoint time minus time tolerance, but before checkpoint time plus time tolerance from the patrol’s start, nothing happens. If he/she does not, a patrol failed alarm is generated (after checkpoint time plus time tolerance from the patrol’s start).
The same goes for all the checkpoints of the route. Every checkpoint not passed on time generates an alarm.
Right after a guard passes the last checkpoint on time (in checkpoint time +/- time tolerance), the patrol is considered completed.
When a route is removed, all future patrols resulting from its schedule are cancelled. However, patrols which have already started, continue (i.e. will result in alarms if checkpoints are not passed on time).