Guard Tours

1. Guard Tours

1.1. The ISMS shall support multiple guard tours between check points.

1.1.1. There shall be no imposed limit on the number of guard tours that can be
configured.

1.2. Check points shall be card readers, inputs, or outputs.

1.2.1. There shall be no imposed limit on the number of check points.

1.3. Multiple guard tours must be able to run concurrently.

1.4. The guard tour shall allow for flexible and configurable timing between check points
which shall have (but not be limited to) the following:

1.4.1. transition time;

1.4.1.1. the time period that it should take the guard to move from the
last check point to the next check point,

1.4.1.2. this shall be configurable in hours, minutes and seconds,

1.4.1.3. the time shall be uniquely configurable for each check point,

1.4.2. deviation;

1.4.2.1. the time allowed for the guard to be early or late at the check
point,

1.4.2.2. this shall be configurable in hours, minutes and seconds,

1.4.2.3. the time shall be uniquely configurable for each check point,

1.4.3. late;

1.4.3.1. the time period that has elapsed since the guard was expected
at the check point wherein they are now considered as late to
the check point,

1.4.3.2. this shall be configurable in hours, minutes and seconds,

1.4.3.3. the time shall be uniquely configurable for each check point.

1.5. The alarm priority for the guard tour events must be configurable.

1.6. User configurable instructions shall be available to assist operators when a guard tour
alarm occurs.

<SpecDate> Page 1
 Guard Tours

1.7. The ISMS shall have an option to determine whether the guard must badge and open a
door for a guard tour check point, or just present their card at the check point and not
enter.

1.8. The ISMS shall be able to send an email and/or SMS alert to selected personnel based
on guard tour events:

1.8.1. it shall be possible to configure which events send alerts,

1.8.2. it shall be possible to schedule when these alerts are sent.

1.9. The guard tour shall display in real-time the following information:

1.9.1. the name of the guard,

1.9.2. the list of check points,

1.9.3. the time the guard is expected at each check point. This time shall display
the deviation to indicate the time period the guard has to arrive at the check
point.

1.9.3.1. This time period should update dynamically depending on the

time the guard arrived at each check point.

1.9.4. The time the guard arrives at the check point.

1.9.5. The guard tour status should indicate (but not be limited to) the following:

1.9.5.1. not due,

1.9.5.2. due,

1.9.5.3. early,

1.9.5.4. overdue.

1.10. The guard tour shall stop if the guard arrives at an incorrect check point and an alarm
shall be raised to indicate this.

1.11. The ISMS shall be configurable to restrict the individual guard tours that an operator
can view.

1.12. The ISMS shall be configurable to determine whether an operator can view, edit or
delete selected guard tours.

1.13. It shall be possible to display the real-time status of guard tours on a site map.

1.14. The guard tours shall be able to be started and stopped from the site map.

1.15. A site map showing the route of the guard tour shall be displayed.

1.16. It shall be possible to print a guard tour report directly from the site map.

<SpecDate> Page 2
 Guard Tours

1.17. The reports shall be configurable to filter based on the following criteria:

1.17.1. date/time,

1.17.2. guard tour,

1.17.3. guard.

<SpecDate> Page 3