📄 Extracted Text (21,583 words)
SOFTWARE HOUSE
From Tyco Security Products
C•CURE 9000
Version 2.50
UM-297 CO
EFTA01225852
C•CURE and Software House are registered trademarks of Tyco Security Products.
The trademarks, logos, and service marks displayed on this document are registered in the United States [or
other countries]. Any misuse of the trademarks is strictly prohibited and Tyco Security Products will aggressively
enforce its intellectual property rights to the fullest extent of the law, including pursuit of criminal prosecution
wherever necessary. MI trademarks not owned by Tyco Security Products are the property of their respective
owners, and are used with permission or allowed under applicable laws.
Product offerings and specifications are subject to change without notice. Actual products may vary from photos.
Not all products include all features. Availability varies by region; contact your regional sales manager.
Software version: 250
Document Number: UM-297
Revision Number: CO
Release Date: December 2015
This manual is proprietary information of Software House. Unauthorized reproduction of any portion of this
manual is prohibited. The material in this manual is for information purposes only. It is subject to change
without notice. Software House assumes no responsibility for incorrect information this manual may contain.
O 2015 Tyco Security Products.
MI rights reserved.
EFTA01225853
Table of Contents
Preface 5
How to Use this Manual 6
Finding More Information 7
Conventions 8
Software House Customer Support Center 9
Chapter 1 - Guard Tour Overview 11
Guard Tour Introduction 12
Sequential Tours 12
Random Tours 12
Guard Tours in an Enterprise Environment 12
Guard Tour Activation 13
Tour Stop Considerations 14
Rules for Guards 15
Guard Tour Capacity Limitations 16
Guard Tour Scheduling and Time Zones 17
Scheduling Guard Tours 17
Time Zones 17
Using Guard Tours 18
Manual Guard Tours 18
Scheduled Guard Tours 19
Automatically Started Guard Tours 27
Guard Tour Error Handling, Triggers, and Event Activation 23
Error Handling 23
Triggers 23
Chapter 2 - Configuring a Guard Tour 25
Guard Tour Configuration Steps 26
Guard Tour Basic Tasks 28
Viewing a List of Guard Tours 29
Using the Guard Tour List Context Menu 30
Viewing Guard Tour Details 32
C•CURE 9000 Guard Tours Guide 3
EFTA01225854
Guard Tour Details Dialog Box Definitions 32
Tour Stops Tab 33
Documents Tab 36
Logging a Message for a Guard Tour 37
Chapter 3 - Guard Tour Editor 39
Guard Tour Editor 40
Accessing the Guard Tour Editor 40
Guard Tour Editor Buttons/Fields Definitions 41
Guard Tour Stops Tab 43
Guard Tour Stops Tab Definitions 43
Guard Tour Stops Tab Tasks 46
Guard Tour Stop Triggers Dialog Box 49
Guard Tour Stop Triggers Dialog Box Definitions 49
Guard Tour Stop Triggers Dialog Box Tasks 51
Guard Tour Options Tab 53
Guard Tour Options Tab Definitions 53
Guard Tour Options Tab Tasks 54
Guard Tour Triggers Tab 56
Guard Tour Triggers Tab Definitions 57
Guard Tour Triggers Tab Tasks 59
Guard Tour Guards Tab 64
Guard Tour Guards Tab Definitions 64
Guard Tour Guards Tab Tasks 65
Guard Tour Predefined Log Messages Tab 67
Guard Tour Predefined Log Messages Tab Definitions 68
Guard Tour Predefined Log Messages Tab Tasks 68
Guard Tour Documents Tab 69
Guard Tour Documents Tab Definitions 69
Guard Tour Documents Tab Tasks 70
Guard Tour State Images Tab 72
Guard Tour State Images Tab Definitions 72
Guard Tour State Images Tab Tasks 74
Chapter 4 - Guard Tour Scheduling Editor 75
Guard Tour Scheduling Editor 76
Accessing the Guard Tour Scheduling Editor 76
Guard Tour Scheduling Editor Definitions 77
Guard Tour Scheduling Editor Task 78
Viewing a List of Guard Tour Schedules 79
4 C•CURE 9000 Guard Tours Guide
EFTA01225855
Preface
The C•CURE 9000 Guard Tours Guide is for new and experienced security system users who want to learn to use
this product for the C•CURE 9000 Security Management System.
In this preface
How to Use this Manual 6
Finding More Information 7
Conventions 8
Software House Customer Support Center 9
C•CURE 9000 Guard Tours Guide Preface 5
EFTA01225856
How to Use this Manual
How to Use this Manual
this manual contains chapters that provide the following information about the C•CURE 9000 Guard Tour.
Chapter 1: Guard Tour Overview
Provides introductory information about the C•CURE 9000 Guard Tour functionality.
Chapter 2: Configuring a Guard Tour
Outlines the steps involved in configuring Guard Tours and provide information on performing basic Guard Tour
tasks.
Chapter 3: Guard Tour Editor
Provides information about the Guard Tour Editor, its various tabs, and how to use them to configure a Guard Tour.
Chapter 4: Guard Tour Scheduling Editor
Provides information about the Guard Tour Scheduling Editor and how to use it to configure scheduling for a Guard
Tour.
6 Preface C•CURE 9000 Guard Tours Guide
EFTA01225857
Finding More Information
Finding More Information
You can access C•CURE 900(1 manuals and online Help for more information about C•CURE 9000.
Manuals
C•CURE 9000 software manuals are available in Adobe PDF format on the C•CURE 9000 DVD.
You can access the manuals if you copy the appropriate PDF files from the C•CURE 9000 Installation DVD
English \ Manuals folder.
The available C•CURE 9000 and Software House manuals are listed in the C• CURE 9000 Installation and Upgrade
Guide, and appear as hyperlinks in the online.pdf file on the C•CURE 9000 DVD English \ Manuals folder.
These manuals are also available from the Software House Member Center website
Online Help
You can access C•CURE 9000 Help by pressing Fl or clicking Help from the menu bar in the
Administration/Monitoring Station applications.
C•CURE 9000 Guard Tours Guide Preface 7
EFTA01225858
COnveribonS
Conventions
Ibis manual uses the following text formats and symbols.
Convention Meaning
Bold T his font indicates screen elements, and also ind tales w hen you should take a direct action in a procedure.
Bold font describesone of the following items:
• A command or character to type, or
• A button or option on the screen to press, or
• A key on the keyboard to press
• A screen element or name
blue color text Indicates a hyperlink toa URL, or a cross-reference toa figure, table, or section in this guide.
Regular keit font Indicates a new term.
<text> Indicatesa variable.
The following items are used to indicate important information.
Indicates a note. Notes call attention to any item of information that may be of special importance.
NOTE
Indicates an alternate method of performing a task.
TIP
0 Indicates a caution. A caution contains information essential to avoid damage to the system. A
caution can pertain to hardware or software.
Indicates a warning. A warning contains information that advises users that failure to avoid a
specific action could result in physical harm to the user or to the hardware.
MCP Indicates a danger. A danger contains information that users must know to avoid death or serious
injury.
8 Preface C•CURE 9000 Guard Tours Guide
EFTA01225859
Software House Customer Support Center
Software House Customer Support Center
Telephone Technical Support
During the period of the Agreement, the following guidelines apply:
• Software House accepts service calls only from employees of the Systems integrator of Record for the installation
associated with the support inquiry.
Before Calling
Ensure that you:
• Are the Dealer of record for this account.
• Are certified by Software House for this product.
• Have a valid license and current Software Support Agreement (SSA) for the system.
• Have your system serial number available.
• Have your certification number available.
Hours Normal Support Hours Monday through F riday. 8:00 to 8:00 , EST. Except holidays.
Emergency Support Hours 24 hours/day, seven days a week, 365 days/year.
Requires Enhanced SSA"7 x2r Standby Telephone Support
(emergency) provided to Certified Technicians.
For another customers. billable on time and materials basis.
Minimum charges appty - See MSRP.
Phone For telephone support contact numbers for all regions. see
C•CURE 9000 Guard Touts Guide Preface 9
EFTA01225860
Software House Customer Support Center
10 C•CURE 9000 Guard Tours Guide
EFTA01225861
1
Guard Tour Overview
This chapter introduces the Guard Tour configuration components of the C•CURE 9000 Security and Event
Management System. C•CURE 9000 Guard Tour provides the tools needed to configure a Guard Tour and its related
Stops, Triggers, Guards, Predefined Log Messages, Documents, State Images, and Recurring Schedules.
In this chapter:
Guard Tour Introduction 12
Tour Stop Considerations 14
Rules for Guards 15
Guard Tour Capacity Limitations 16
Guard Tour Scheduling and Time Zones 17
Using Guard Tours 18
Guard Tour Error Handling, Triggers, and Event Activation 23
C•CURE 9000 Guard Tours Guide Chapter1 11
EFTA01225862
Guard Tour Introduction
Guard Tour Introduction
A Guard Tour consists of a series of Stops where a Guard checks in during security rounds. Each Guard Tour Stop is
monitored by a reader or by a security input that allows check-in by the Guard. To complete a Tour, a Guard must
check in at each specified Stop. Stops can consist of any combination of Doors, Elevators, and Inputs.
There are two types of Guard Tours:
■ Sequential. The Guard must check in at the Stops in the Guard Tour in sequence, according to the order
configured on the Guard Tour Editor Stops tab (StopIt).
■ Random. The Guard can check in at the Stops in the Guard Tour in any order.
For either type Guard Tour:
■ The Guard must check in at all the Tour Stops before the Tour is considered completed—unless the Tour is
canceled, either due to errors or by an Event Action or a Manual Action. (A canceled Tour is not considered
'completed')
■ The Tour has a minimum and maximum time of completion: a Guard must spend at least the minimum
amount of time walking the Tour, but no more than the maximum amount of time.
Sequential Tours
MI tour stops in a sequential tour require the configuration of minimum and maximum amounts of time that a
guard can take between stops. In addition, the minimum and maximum time for the first stop is used to determine if
a tour started early, late, or on time.
■ When a guard checks in at the first stop before the minimum stop time expires, this stop was reached early and
the tour was started early.
■ When a guard checks in at the first stop after the maximum time expires, this stop was reached late and the tour
was started late.
■ When the maximum stop time expires, but a guard has not yet checked in, the stop will indicate that it was not
reached on time.
Random Tours
Four stops in a random tour also require configuration of minimum and maximum amounts of time that the guard
can take between stops, but the settings apply to all the stops. The system still uses the minimum and maximum
time for the first stop to determine if the tour started early, late, or on time —as detailed in the preceding section on
sequential Tours.
Guard Tours in an Enterprise Environment
Guard Fours are 'local' objects. Consequently, in an Enterprise Environment, Tours can only be associated with a
particular SAS server. Along with other local objects, they can be edited and viewed on that SAS.
Guard Tours can be viewed on the MAS server, and if the associated SAS is online, they can also be edited on the
MAS.
12 Chapter 1 C•CURE 9000 Guard Tours Guide
EFTA01225863
Guard Tour Introduction
Guard Tour Activation
Guard Tours can be activated (started) by:
• Operator Action.
• Configured Event.
• Guard swiping at the Reader/Keypad of the Door or Elevator at the first Tour Stop.
Guard Tours can have any of the following statuses resulting from an Operator Action/Event Action:
• Activated- A Guard has been assigned to the tour and it has started.
• Suspended - An 'Active' Tour has been temporarily stopped.
• Resumed - A Suspended Tour has been re-activated.
• Canceled- An 'Active' Tour has been requested to stop. (An Active Tour that is 'disabled' is considered
'Canceled'.
Guard Tours cannot be edited while they are 'Enabled'.
NOTE
CCURE 9000 Guard Tours Guide Chapter! 13
EFTA01225864
Tour Stop Consderations
Tour Stop Considerations
■ A Tour Stop can be configured to use a Door, Elevator, or Input as the monitoring device for the Stop.
Clearance for the Door or Elevator is not required unless the Guard
NOTE
is expected to use the Door/Elevator. (For more detail, see Rules
for Guards on Page 15.)
• Either In or Out type Doors can be specified. (The 'In'/'Out' designation indicates which Reader on the Door
is used —if the Door has two readers. A single Reader can be on either the 'In' or the 'Out' side.)
• A swipe at an unlocked Door is treated as though it was a valid swipe at a locked Door —on Controllers that
support this. (Currently only iSTARs with 6.1.0 firmware or higher support this feature.)
• An Elevator can be used with/without a corresponding Floor.
Only iSTAR and apC Doors/Elevators are supported as Tour
NOTE
Stops.
■ The same Door, Elevator, or Input can be used to monitor multiple Stops in the same Tour.
■ If Tour Stops are monitored by Doors or Elevators, those Stops can be assigned to multiple Guard Tours.
However, Doors or Elevators that initiate Guard Tours cannot be assigned as Tour Stops to other Guard Tours.
■ If Tour Stops are monitored by Inputs, those Stops cannot be assigned to multiple Guard Tours.
The Inputs must be enabled and also armed.
■ A Stop visited out of order in a sequential Tour is considered an error. (The next valid Stop in a sequential Tour
that has gotten out of order must be the Stop configured to follow the last valid Stop. In addition, the Stop visited
out of order must be re-visited in its correct order for the Tour to be considered 'Completed'.
For more information about Tour Stops, see How Stop Statuses Work for Random Tours on Page 36.
Duress Situations
Dual Inputs, Readers with a keypad, and Mag Stripe Readers (these Readers include Doors and Elevators) can be
configured to monitor for Duress.
■ For Inputs: Duress is indicated by another nearby Input.
■ For a Reader with a keypad: Duress is indicated by the Personnel PIN number plus one.
■ For a Mag Stripe Reader: Duress is indicated by a reverse swipe.
14 Chapter 1 C•CURE 9000 Guard Touts Guide
EFTA01225865
Rubs for Guards
Rules for Guards
■ To be assigned to a Tour as a Guard, a person must have a Personnel record in C•CURE 9000 and have the Can
Perform Guard Tour option selected. (For information, see the "Personnel General Tab" section in the "Personnel"
chapter in the C• CURE 9000 Personnel Configuration Guide.)
■ A Guard must have the requisite Clearance to access (enter/exit) Doors/Elevators configured as part of the Tour.
■ Some Stops, such as Door (In), Door (Out), Elevator, Input, and Input (Duress) that do
NOTE not require 'usage', do not require Clearances.
■ Other Stops that do require 'usage', such as Door (In Used), Door (Out Used), and
Elevator (Used), do require Clearances.
■ An individual Guard Tour can only be run by Personnel who not only have the Can Perform Guard Tour
option selected in their Personnel record, but are also listed on the Guard Tour Editor Guards tab. (For
information, see the Guard Tour Guards Tab on Page 64.)
If no Guards are listed on the preceding tab, the Tour cannot be run.
NOTE
C•CURE 9000 Guard Tours Guide Chapter 1 15
EFTA01225866
Guard Tour Capacity Limitations
Guard Tour Capacity Limitations
The following limitations apply to C•CURE 9000 Guard Tours:
■ The maximum number of 'enabled' Guard Tours allowed in a C•CURE 9000 system is 200, while the maximum
number of Stops per Tour allowed is 100. The system displays a message when either limit has been reached.
■ The maximum number of simultaneous 'running' Guard Tours allowed is 50. Once that number has been
reached, no further Tours are permitted to start. The system notifies users that the limit has been reached in the
following ways, depending on how the Tour was being initiated.
If started:
• From a Dynamic View via the Start command, a message displays.
• By a Scheduled Event or a Guard's Card swipe at an initiating Reader, a message is logged.
■ 23 Hours, 59 Minutes is the maximum amount of time:
• A Guard Tour can take to complete.
• Between Guard Tours Stops.
• A Guard Tour can be suspended.
■ There is no limit to the number of Personnel who can be configured to act as Guards.
■ A maximum of 10 documents can be assigned to a Guard Tour.
18 Chapter1 C•CURE 9000 Guard Tours Guide
EFTA01225867
Guard Tour Scheduling and Time Zones
Guard Tour Scheduling and Time Zones
Scheduling Guard Tours
Scheduling a Guard Tour means that:
■ A Tour is expected to start and end within a schedule. It does not mean a Tour will start on a schedule. (If you
want a Tour to start on a particular schedule, you can create an Event with the 'Guard Tour Start' Action that
activates on that schedule.)
■ One Guard is assigned to run the Tour within this particular schedule. (This Guard can only be someone listed
for that Tour on the Guards tab of the Guard Tour Editor —someone who has a Personnel record in C•CURE
9000 and the Can Perform Guard Tour option selected on the Personnel Editor General tab. For information, see
the "Personnel General Tab" section in the "Personnel" chapter in the C• CURE 9000 Personnel Configuration Guide.
The Guard Tour Scheduling Editor information is used to notify Guards when their selected Tours should run.The
scheduling does not prevent the assigned Guards from running Tours at other times.
• Their card swipe at the 1st stop can start the Tours outside the Schedule.
• In addition, Guards not assigned to a Tour on the Scheduling Editor can still run the tour.
The system checks once an hour to see which Schedules associated with inactive Tours are about to become active in
the next hour. Email notifications are then sent to the Guards —if the Notify Guard... option is selected —and to the
Additional Notifications group of personnel —if any is specified. The email includes the time frame in which the
Tour is expected to be run (the schedule start and end times), as well as any documents attached to the Tour.
When a Schedule associated with one or more Guard Tours becomes active, the system logs a Journal Message
indicating that each Tour on that Schedule is due to be run. The message also indicates when the Tour must be
completed (the end date/time of the Schedule). The message appears on the Monitoring Station Activity Viewer as
well.
When a Schedule associated with one or more Guard Tours becomes inactive, the system marks any Tours that
failed to start with the "Failed to Start"status and logs a Journal Message for each tour that has not completed. (You
can also configure an Event on the Guard Tour triggers tab to activate when a Tour "Fails to start".) The system also
marks any Tours that are running as "Not Completed On Time.
Time Zones
Guard Tours do not have assigned Time Zones. However, they do have Tour Stops which are constructed of
devices —such as Doors, Elevators, and Inputs —that have related Time Zones. Consequently, the Schedules used by
Guard Tours, either when a Guard's card swipe at a Reader at a Door or Elevator starts a Schedule, or when Guards
are scheduled to run tours, should be respected in the Time Zone of the devices.
The Time Zone of the device at the first Stop is the Time Zone used for Schedules related to the Tour. When Tour
Stops whose Time Zone does not match the Time Zone of the first Stop are added to the Tour, the Schedule uses the
Time Zone of the first Stop. (The system displays a warning message.)
C•CURE 9000 Guard Tours Guide Chapter! 17
EFTA01225868
Using Guard Tours
Using Guard Tours
Guard Tour functionality is flexible and consequently can be utilized in several different ways. You can use Guard
Tours in the way best suited to your company or institution's needs.
This section presents three example scenarios for using the Guard Tour feature. You can use any combination of
these scenarios, as well as others appropriate for your site. You do not need to configure each of your Tours in the
same way.
1. An entirely manual usage - Manual Guard Tours on Page 18.
2. Configuring Tours so Guards are expected to run them at specific times and Reports can be generated to check
Tour status - Scheduled Guard Tours on Page 19.
3. A fully automatic setup where Tours are started automatically by the system and Reports are used to document
the status of those Tours - see Automatically Started Guard Tours on Page 21.
In addition, different ways of tracking Tour issues are detailed in a section on Guard Tour Error handling - see
Guard Tour Error Handling, Triggers, and Event Activation on Page 23.
Manual Guard Tours
In the 'Manual' method —the least common, but the easiest to configure, system Operators tell Guards when they
should run Guard Tours.
Configuring Manual Guard Tours
You will probably configure most Manual Tours to be run sequentially—the Guard has to visit each Stop in the
specified order. However, you have two other options. You could also configure the Tour as:
■ A random Tour - the Guard can visit the Stops in any sequence he/she prefers.
■ A sequential Tour - but configured so certain Guards can visit the Stops in any sequence (like a random Tour).
Since you are starting these Tours manually, configure the first Stop's minimum time as zero (0). (This will prevent
the Tour from getting a "Started Early" error.)
On the other hand, if you plan to start a Tour and tell the Guard to run it while expecting he/she to perform a Tour-
related and time-consuming task before reaching the first Stop, configure a minimum time for the first Stop.
Example:
If the Tour involves a five-minute walk at the start that is not covered by an actual Stop, specify a five-minute
minimum time for the first Stop. If the Guard then takes fewer than five minutes, the Tour will enter the "Started
Early" state. This might require a discussion with the Guard about the reason for the status. Did the five-minute
walk not take place? Why? Or did the walk take less time than expected?
For information on how to configure Guard Tours, see Chapter 2, Configuring a Guard Tour and Chapter 3, Guard
Tour Editor. You do not need to use the Guard Tour Scheduling dialog box to configure Guard Tours manually.
18 Chapter1 C•CURE 9000 Guard Tours Guide
EFTA01225869
Using Guard Tours
Running Manual Guard Tours
You have two options for running these Tours:
■ Start the Tour manually from the Guard Tour Dynamic View. (See Using the Guard Tour List Context Menu on
Page 30.)
■ Configure a card swipe at the first Stop to start the Tour, so the system initiates the Tour when the Guard visits
that first Stop. (See Guard Tour Stops Tab on Page 43.)
However the Tour is started, the system creates a journal record and displays it on the Monitoring Station Activity
viewer.
Reporting for Manual Guard Tours
You can run the pre-defined Guard Tour Reports to check which Tours ran, their current status, and whether or not
they had errors, etc. (For information on these Reports, see "Appendix A, Pre-defined Reports, Queries, and Views" in
the C•CURE 9000 Data Views Guide.)
Scheduled Guard Tours
In the Scheduled' method, a Tour is configured to be run at some appointed time. You can configure Guard Tour
Schedules to tightly restrict a Guard's time allowance for the Tour or alternatively to allow a greater span of time for
a Guard to use during the Tour. In addition, you can control the Tour by combining the following factors in different
ways:
■ When the Tour starts.
■ How quickly a Guard must reach specific Stops and how much time can be spent at each Stop (Min Time/Max
Time).
■ How much time the entire Tour can take.
■ How long the Tour can remain suspended at any point in time.
Configuring Scheduled Guard Tours
As with Manual Guard Tours, you will configure most Scheduled Tours to be run sequentially—the Guard has to
visit each Stop in the specified order. However, you have two other options. You could also configure the Tour as:
■ A random Tour—the Guard can visit the Stops in any sequence he/she prefers.
■ A sequential Tour- but configured so certain Guards can visit the Stops in any sequence (like a random Tour).
Most Scheduled Tours will probably be started when a Guard visits the first Stop of the Tour. Therefore,
configure the first Stop's minimum time as zero (0) to prevent the Tour from getting a "Started Early" error.
It is not a requirement that Scheduled Tours be started in the preceding manner. You can
NOTE
still start such Tours manually from the Guard Tour Dynamic View. (See Using the
Guard Tour List Context Menu on Page 30.)
Be aware, however, that a Tour that is started manually outside the configured Schedule
does not count towards the scheduled expectation of running this Tour.
C•CURE 9000 Guard Tours Guide Chapter 1 19
EFTA01225870
Using Guard Tours
■ You must also use the Guard Tour Scheduling dialog box to complete the configuration of scheduled Guard
Tours.
For information on how to configure Guard Tours, see Chapter 2, Configuring a Guard Tour, Chapter 3, Guard Tour
Editor, and Chapter 4, Guard Tour Scheduling Editor.
Notifications for Scheduled Guard Tours
The system includes several notification options for Scheduled Guard Tours. Once an hour, the system looks ahead
an hour and makes note of any Tours expected to start in that time period.
When the system first starts up, it performs the look-ahead and notifications for the next
NOTE
hour at start time—even if it is not currently the top of the hour.
For each Tour expected to start, the system sends an email to the Guard assigned to run that Tour ( if the Notify
Guard of Scheduled Tour option is selected), and optionally to the Group of Personnel specified in the Additional
Notifications field. (See Guard Tour Scheduling Editor on Page 76.)
For email notification to work, the Guard and any additional personnel listed must have valid Email addresses on
their Personnel records; in addition, the system must be properly configured to connect to an Email server. For
information, see:
■ "Personnel General Tab" and "Setting an Email Address" in the Personnel chapter in the C•CURE 9000 Personnel
Configuration Guide.
■ "Setting Up Email for C•CURE 9000" in the C•CURE 9000 System Maintenance Guide.
The email specifies that the Guard is expected to run the named Tour between the time the Schedule activates and
the time it goes inactive—presented as Start and Stop times.
Example:
The email might read: Guard Tour 'Front' is scheduled to be run between 6:00 PM and 7:00 PM for Guard: John
Smith.
The subject of the email would display: Guard Tour 'Front' should start in the next hour.
The email would include any documents configured as attachments for this Guard Tour.
You can also specify that a Guard listed on a Tour Schedule not be sent email. (Maybe the
NOTE
Guard gets notified of the Tour in another way and does not want extra email.)
Other Notifications for Scheduled Guard Tours
For various reasons, you might want notifications, outside of the Guard Tour functionality, sent to entirely different
Personnel. You can do this by creating an Event that sends an email or emails a Report, and then scheduling that
Event to run periodically.
20 Chapter1 C•CURE 9000 Guard Tours Guide
EFTA01225871
Using Guard Tours
Running Scheduled Guard Tours
You have the following options for running these Tours:
■ Start the Tour manually from the Guard Tour Dynamic View. (See Using the Guard Tour List Context Menu on
Page 30.)
Or -
• Configure a card swipe at the first Stop to start the Tour, so the system initiates the Tour when the Guard visits
that first Stop. (See Guard Tour Stops Tab on Page 43.)
■ Additionally, schedule an Event to start a Tour. (For information, see Automatically Started Guard Tours on Page
21.)
However the Tour is started, it must be started while the Schedule for the Tour is active—or it will not count towards
the Scheduling record.. It must also be completed before the Schedule goes inactive. Consequently, with Scheduled
Guard Tours, both the Activation time of a schedule as well as the subsequent Inactivation time are most important.
Guard Tour Scheduling Results
When Guard Tours are scheduled in this manner, the system performs some extra operations to help track the Tours.
Whenever a Schedule for one or more Tours goes active, the system 'initializes' the Tour, resetting the various Tour
statuses. It does not do this, however, if the Tour is currently running.
More importantly, when such a Schedule goes inactive, the system checks every Tour. Any such Tours still running
have their state changed to "Not Completed On Time" —which is entered in the Journal.
This is not considered a Guard Tour error, and consequently does not cancel the Tour —
NOTE
even if the Cancel Guard Tour on Error option is configured.
Any of these Tours that did not start in the scheduled time have their state changed to "Failed To Start" —also
entered in the Journal.
The preceding operations enable the running of Reports that indicate which Tours ran as scheduled, which did not
run, and which ran, but failed to complete on time.
Reporting for Scheduled Guard Tours
You can run the pre-defined Guard Tour Reports to check which Tours ran, their current status,and whether or not
they had errors, etc. (For information on these Reports, see "Appendix A, Pre-defined Reports Queries, and Views" in
the C• CURE 9000 Data Views Guide.)
Automatically Started Guard Tours
In the 'Automatically Started' method, a Tour is started on a Schedule using Event Scheduling. The Tours always
start on time (when the Event activates), and the timing begins instantly. This might be the best method to use if you
cannot start your Tours by a card swipe at a Reader (the first Stop does not have a Reader).
C•CURE 9000 Guard Tours Guide Chapter! 21
EFTA01225872
Using Guard Tours
Configuring Automatically Started Guard Tours
To create automatically started Tours, you configure scheduled Events with the Guard Tour Start Action. (See "Event
Editor" in the C•CURE 9000 Software Configuration Guide.)
The system will refuse to start a Guard Tour if the:
NOTE
■ Tour is already running.
• tour configuration is no longer valid.
■ Specified Guard is no longer valid.
You can optionally configure Guard Tour Scheduling for Automatically Started Guard Tours.
For information on how to configure Guard Tours, see Chapter 2, Configuring a Guard Tour, Chapter 3, Guard Tour
Editor, and Chapter 4, Guard Tour Scheduling Editor.
Notifications for Automatically Started Guard Tours
When a Tour is started automatically by the Event becoming active, the Event is entered in the Journal, as usual.
Without using the Guard Tour Scheduling Editor there is no automated notification to the Guard, but an Operator
looking at the Activity Viewer or Guard Tours Dynamic View can see that the Tour has been started.
If you did configure Guard Tour Scheduling for your Automatically Started Guard Tours, you benefit from the
functionality described in Scheduled Guard Tours on Page 19 such as notifications and Journal entries.
In addition, even without having scheduling configured, you can still create separate Events to send notifications.
You can also track Tours that fail to complete on time by checking for Tours "Completed Late" in the Journal or the
Activity Viewer.
Reporting for Automatically Started Guard Tours
You can run the pre-defined Guard Tour Reports to check which Tours ran, their current status,and whether or not
they had errors, etc. If you configured Guard Tour Scheduling, you can also run Reports indicating which Tours ran
as scheduled, which did not, and which ran, but failed to complete on time. If you did not configure Guard Tour
Scheduling, you can still find that information by running Report on Tours that time out (equivalent to Tours "Not
Completed On Time") and Tours whose first Stop times out (roughly equivalent to "Failed to Start").
(For information on these Reports, see "Appendix A, Pre-defined Reports Queries, and Views" in the C•CURE 9000
Data Views Guide.)
22 Chapter1 C•CURE 9000 Guard Tours Guide
EFTA01225873
Guard Tour Error Handling. Triggers. and Event Activation
Guard Tour Error Handling, Triggers, and Event Activation
You can configure Guard Tours to include:
■ Error handling that immediately cancels the Tour if any errors occur during execution of the Thur.
■ Triggers that activate or pulse Events, send Emails, or run Reports.
Error Handling
Global Error handling is set by selecting the Cancel Guard Tour on error option. (See the Guard Tour Options Tab
on Page 53. For information on handling specific errors separately, see Triggers on Page 23.)
When such an error occurs, the Tour's Monitoring State is set to "Canceled Due to Error", and the Tour's "Error
Occurred" property is set to 'true'. You could configure either of these to be used with a trigger that causes additional
activity to occur :
Example:
Emailing the Guard.
Activating an Event Action that sets off an alarm.
There are several possible errors that can occur during the execution of a Guard Tour:
■ A Stop was reached out of sequence in a sequential Tour.
■ A Stop was reached before the minimum amount of time for that Stop elapsed.
• If this is the first Stop in the Tour, the error is the Tour "Started Early".
• For any other Stop, the error is the Stop "Checked in Early".
■ A Stop was reached after the maximum amount of time for that Stop elapsed.
• If this is the first Stop in the Tour, the error is the Tour "Started Late".
• For any other Stop, the error is the Stop "Checked in Late.
■ A Tour was "Suspended Too Long".
■ The Tour "Completed Early" (before the minimum Tour time elapsed).
■ The Tour "Completed Late (after the Tour timed out).
Triggers
Canceling the Guard Tours on the occurrence of any and all errors may be too extreme for your company's situation.
You may want to customize what the system does, depending on the type of error. You can achieve this by
configuring Triggers for the Guard Tour and/or its Tour Stops.
Triggers can activate Events, send emails, or run Reports:
■ If a sequential Tour is taken out of sequence; any Tour is Completed sooner or later than configured (a Guard
Tour error), started late, suspended for too long a time, or in 'duress' (a Stop encountered a duress situation); or a
Tour Stop is reached sooner or later than configured (a Guard Tour error).
■ When a Tour completes.
(See Guard Tour Stop Triggers Dialog Box on Page 49 and Guard Tour Triggers Tab on Page 56.)
C•CURE 9000 Guard Tours Guide Chapter! 23
EFTA01225874
Guard Tour Error Handling, Triggers, and Event Activation
These two types of Trigger give you great control over error handling, including the ability to cancel the Guard Tour
only for certain errors. Triggers also give you the ability to handle initialization and post-tour functionality.
Example:
You can configure Triggers to arm all of your Inputs at the start of the Tour ("Tour Running" property= true) and
disarm the Inputs at the end ("Tour Running" property=false).
24 Chapter 1 C•CURE 9000 Guard Tours Guide
EFTA01225875
2
Configuring a Guard Tour
This chapter outlines the steps required to configure a Guard Tour in C•CURE 9000 and provides information on
Guard Tour basic tasks.
In this chapter
Guard Tour Configuration Steps 26
Guard Tour Basic Tasks 28
Viewing a List of Guard Tours 29
Viewing Guard Tour Details 32
C•CURE 9000 Guard Tours Guide Chapter 2 25
EFTA01225876
Guard Tour Configuration Steps
Guard Tour Configuration Steps
Table 1 on Page 26 shows the C•CURE 9000 Editors and activities that create C•CURE 9000 Guard Tours.
Table 1: Creating Guard Tours
Task C•CURE 9000 Configuration Notes Additional Information
Editor
Configure Personnel>Personnel> Enables specific Personnel to run Guard Tours by See 'Personnel General Tab', "Setting
Personnel allowed New>Personnel selecting the Can Perform Guard Tour option in Options', and 'Setting an Email
to run Guard Editor>General tab the Options box. Addresse in the Personnelchapter in the
Tours and -or- Creates an Email address for a Personnel Record C•CURE 9000PersonnelConfiguration
Personnel Email so the person can receive Email notification if: Guide.
Address Edit an existing
Personnel Record • Assigned as a Guard to run a Tour on the
Guard Tour Scheduling Editor and the See Guard Tour Scheduling Editor on
Notify Guard of Scheduled Tour option is Page 76 and Guard Tour Guards Tab on
selected. Page 64.
• A member of a Personnel Group configured
on the Guard Tour Guards tabor Guard
Tour Scheduling Editor to receive email
notification of Tour scheduling.
Configure a Configuration>Group> Creates a Personnel Group which can then be See the Groups chapter in the C•CURE
Personnel Group New>Group Editor selected on the Guard Tour Guards tab/Guard 9000 Software Configuration Guide.
(optional) - or - Tour Scheduling Editor so its members receive See Guard Tour Scheduling Editor on
email notification of Tour scheduling. Page 76 and Guard Tour Guards Tab on
Edit an existing
Personnel Group Page 64.
Configure the Personnel>Guard Creates a Guard Tour. See Guard Tour Basic Tasks on Page 28
Gua
ℹ️ Document Details
SHA-256
776b05ffcef620fafdd6b57e8cd714e58041ef24f981a39ecd3922b5fa1832b1
Bates Number
EFTA01225852
Dataset
DataSet-9
Document Type
document
Pages
80
Comments 0