Beruflich Dokumente
Kultur Dokumente
Overview ............................................................................................................................. 3
Software Components ................................................................................................... 4
TourTrax Server .................................................................................................................. 4
TourTrax Client .................................................................................................................. 4
Download Guardian ............................................................................................................ 4
Database .............................................................................................................................. 4
Hardware Components ................................................................................................ 5
Data Probe ........................................................................................................................... 6
Incident Wallet .................................................................................................................... 7
Officer ID Button ................................................................................................................ 7
Checkpoints & Mounts ....................................................................................................... 7
Tour Start Buttons ............................................................................................................... 8
Download-i Desktop Downloader ...................................................................................... 8
Remote-i Downloaders ....................................................................................................... 8
USB Cable-Style Downloaders........................................................................................... 9
PES Downloaders ............................................................................................................... 9
System Setup and Configuration ..................................................................................... 10
Software Installation................................................................................................... 11
Stand-alone Installation .................................................................................................... 11
Networked Installation ...................................................................................................... 13
TourTrax Server Configuration ................................................................................ 13
Installing and Changing a Database .................................................................................. 14
The Client Configuration ........................................................................................... 17
Programming..................................................................................................................... 20
How to Add Data Probes .................................................................................................. 20
Adding Incident Wallets (PES and Guardus Desktop Downloaders) ............................... 22
Adding Incident Wallets (ActiveGuard, BluCard, Guardus Cable-Style Downloaders).. 26
How to Add an Event Set.................................................................................................. 29
Creating Events for use with Incident Wallets ................................................................. 30
Creating Single Button Events .......................................................................................... 31
Using Memorized Filters .................................................................................................. 34
The Client Information. .................................................................................................... 36
Adding The Client Level .................................................................................................. 37
Adding The Facility Level ................................................................................................ 37
Adding the Site Level ....................................................................................................... 38
Overview
Software Components
The TourTrax System is comprised of the following software components:
• TourTrax Server
• TourTrax Client
• Download Guardian
• Database
TourTrax Server
The TourTrax Server is the component that interfaces directly to the Database, and deals
with processing, storing, removing, and transferring data. All software components that
access the database connect to this program. As such, the Server must be running for the
TourTrax Client and the Download Guardian components to function properly.
TourTrax Client
The TourTrax Client is where you will spend the majority of your time. In this
application, you will be able to set up all Guard Tour configuration, including checkpoint
locations, Officers, Tours, and individual user accounts. Additionally, you will be able
generate and view reports detailing tour data recorded from your officer’s patrols.
Download Guardian
Unlike the previous two components, the Download Guardian only has one function- to
communicate with downloader hardware and transfer information from your data probes
to the TourTrax Server. There are two Download Guardian applications: The Guardus
DG (with a blue shield icon ), and the TourTrax DG (with a green shield icon ).
Each are used independently of each other, and are used with different hardware
platforms. The Download Guardian is an unattended application, designed to run in the
background and retrieve information from data probes as they are placed on hardware
downloader components.
Database
This is single-handedly the most important component of the TourTrax system. This file
contains all configuration information that is stored in TourTrax, such as your
programmed Data Probes, Checkpoints, and other tour information. Additionally, it also
Digital Security Concepts,Inc V.011008 www.GuardTourSystems.com 4
stores all patrol data that is transferred from your Data Probes to TourTrax. Other than for
initial set-up purposes, no further user interaction with the database is typically required.
Important: Due to the critical nature of this file, it is important on installation that you
plan for and implement a strategy to back it up as much as needed. Not doing so may
result in total loss of your data!
TourTrax is designed to support any database that uses Microsoft Active Data Objects
(ADO) connectivity. By default, TourTrax uses an included Microsoft Access database,
however, other database formats are also supported . Contact your software supplier for
more details.
Hardware Components
ActiveGuard- These probes are large, grey, and operate without use
of a downloader. Instead, they use the GSM-GPRS cellular network to transmit their data,
and have a variety of features, such as two-way voice communication, and a universal
Panic Button. These probes utilize RFID technology.
See Page 20 of this Guide for details on how to add a Data Probe to your TourTrax
system.
See Page 22-26 of this Guide for details on how to add &
use the Incident Wallet.
Officer ID Button
See Page 49-51 of this Guide for details on how to add an Officer ID
Button to your TourTrax system.
See page 39-47 of this Guide for details on how to add Checkpoints to TourTrax.
They are typically mounted on a board in the Security Office, installed in the field as the
first button read on the Tour, or fixed to a card carried by a Security Officer performing
Tours.
See page 39-47, 53-56 in this Guide for details on adding these buttons to the software
and creating Tours from them.
Remote-i Downloaders
The Remote-i downloaders allow downloading of the data probes without the use of a
PC. This allows probes to be downloaded in remote locations using either phone lines or
dedicated Internet access. There are 3 main types of Remote-i Downloaders. They are:
Remote-i Modem – This downloader has a modem built into it and uses a power
source and phone line to download, and as such can be used anywhere these resources
are available. On the receiving end, you must have an active internet connection on
the PC.
Remote-i ISP – This downloader also uses a phone line and power source to
download the data, but it differs in that it will make a dial-up internet connection and
transfer the data across the internet to the receiving PC. The receiving PC must have
a dedicated broadband Internet Connection, such as with DSL or Cable.
PES Downloaders
Enter Product
Add Data Probes
Registration Code
Configure initial
server settings
Add Officers
Create Tours
System is ready
for basic usage
Stand-alone Installation
The installation is simple and straightforward. First locate the unique TourTrax Serial
Number provided when you purchased or downloaded your copy of TourTrax.
1. To begin installing the software, insert the TourTrax CD in your CD ROM drive.
Next, access your CD ROM drive by double clicking the “My Computer” icon and your
corresponding CD drive letter. Start the installation by double-clicking the TourTrax
setup icon.
2. Click the next button until you are prompted for the Serial Number as shown below.
Type in the provided Serial Number and click the Next button to continue.
3. Click “Next” to continue through the install process. When you are prompted for the
Install Type, click on the plus button to expand and display your options and to install the
components required for your implementation.
When finished, click on the Next button to proceed with the next portion of the install.
The next screen will prompt you for the directory to install TourTrax to (Default:
C:\Program Files\TourTrax\). In most cases, you do not need to change this option.
Click on Next to continue, then Install to start installing your software. Afterwards, click
Finish to complete the installation.
Once you have determined what PC will be your server you will need to find out what the
IP Address of the computer is. It is best that the Server IP address be set up so that it
does not change. Contact your IT department for more information on how to obtain the
IP address and how to make sure your IP address is “Static”. Alternatively to avoid IP
address changes, you can also configure the system by using the server’s hostname, as
well.
We recommend that you do a Full Install of TourTrax on the Server PC, so you will have
all components available in case you need to do any troubleshooting. Follow the stand-
alone installation procedures to do a Full Install on the Server.
Once you have completed the installation you will need to ensure that your server is set
up to use your “static” IP address. To do this, start the TourTrax Server. Once the server
is started, double click on the Server Icon in the system tray (it should be blue and black,
and say ‘’server’’ when your mouse cursor passes over it.). This will open the Server
window. Click on the Properties Tab and then click on the “Stop Server” button. In the
Server Socket Configuration area you will see the IP Address. If this does not correspond
to your “static” IP address then change it to the new IP address. Once this is set, click on
the “Start Server” button to start the Server again.
You can now go to the client computers and install the TourTrax Client and/or Download
Guardian components on those PCs. Once you are done the installation, you will need to
go into Windows Control Panel, click on the TourTrax Setting icon and then set the IP
address in the appropriate area.
By default, the TourTrax server is pre-configured to run as a windows service, and will
run in the background automatically on computer startup. No user interaction is required
unless it is necessary to change the database to a previously backed up file.
To view the current status and connection information, log on to the machine and Right
click on the TourTrax Server icon and select Properties from the pop up menu. You’ll
see an open window as follows.
Before you setup another database connection or make any changes to the server
configuration, you have to stop the server by first clicking on the Properties tab and then
clicking on Stop Server button as shown above on previous page. The window will be
displayed as below:
Select “Microsoft Jet 4.0 OLE DB Provider” as shown above and click the ‘Next >>’
button.
Use the “Select Database” screen to navigate to the directory the new database is in. Once
you have selected the Database, click the ‘Open’ button on the dialog box. You will be
returned back to the previous window (Data Link Properties). Click on the ‘OK’
button at the bottom of the screen, to close the window.
Then there should be only the TourTrax Server window displayed. The Server is active
again and connected to the database you selected. Click on X on the top right of the
window will minimize the TourTrax Server to the bottom of the screen.
This will open the TourTrax Settings window and allow you to configure the default
connection settings for the Client. In the Client area type in either the IP address or the
Host name of the computer that has the TourTrax Server program installed on. If you are
using Hostnames then you must ensure that they are addressable (resolved) by your DNS
servers. If you are running the client program on the same computer as the server then
you should use the “Loop Back Address” which is 127.0.0.1, or the host name of
“LocalHost”. If you are installing across a network, and are unsure what the IP address of
After setting this information you can close the window by clicking on the X in the top
right corner of the window. Now you are ready to launch the client program.
To launch the client program, double click on the ‘TourTrax Client’ shortcut on your
desktop.
After the Client loads you will be prompted for a username and password. The master
account defaults are:
Username: master
Password: qwerty
A. The Menu Toolbar- this portion of the TourTrax Client allows you to make
configuration changes, to probes and checkpoint information, as well as to
unlock the more advanced reporting features in the software.
B. The Download List- this pane, located on the left side of the Main Window,
contains all downloaded tour information that has been processed by the server.
Whenever a wand is “downloaded”, a new entry is created, at the top of the list.
This entry shows the name of the Data probe, the date and time it was
transferred, and other features specific to your hardware, such as the specified
data probe’s battery life.
C. The Main Reporting Area- This area is where the report data is generated, for
easy viewing.
D. The Reporting Toolbar- This toolbar allows easy access to the five basic
report types used by users of TourTrax- the Summary Report, Full Report,
Exception Report, Event Report, and Missed Report. Also available here are
options to save, print, or email the reports, as well as to re-adjust the zoom if the
data is displayed too small to read.
3. You are now ready to configure your site in TourTrax. Click on Data ->
Programming to begin.
1. Click on the “Data Probes” Tab in the Programming area. On this tab you will see 3
buttons along the bottom. Click the ‘Add’ Button to add all of your Data Probes into the
system.
3. Enter the name you want to assign to a given Data Probe in the “Description” blank
field.
4. Select the type of Data Probe you are using. If you are using a Guardus wand, for
example, select Guardus from the Type drop-down menu.
5. If you are using multiple branches, then select the branch name that this data probe
belongs to from the drop down box.
Before you do this, you will have to download data from the wand in question at least
once prior to checking for this information, from at least 3 checkpoints, or loose
unassigned buttons you may have around. After doing so, go back to the Data Probes list,
select the probe you wish to check, and click on “Edit”. If you correctly set the Type to
PES, you will see the number of points registered on the probe so far next to that field,
and if you click on the AV button, it will show you what has been done to the Probe (e.g.,
attempts to electrocute it).
The first thing you will need to do is to create a name for your Incident Wallet. This will
help you keep them organized, if you have more then one. To do this, click the “Add”
button and fill in the “Incident Wallet Name”. Once you have entered a name,
click on the checkmark button to save it.
Before you begin, you will need to first click on the “Edit Incident Wallet” button. This
will now unlock the button areas, and allow you to make changes. Place the number 1
button from your Incident wallet on your downloader and then click the circular button 1
on screen. This will automatically read in the serial number for you. Continue this same
process to read in all the other buttons. Once you have them all entered into the form,
click the “Save Incident Wallet” button and the data will be saved.
Since the buttons on an Incident Wallet are fairly close together it can be difficult to read
them in using the downloader. So we created a more automated method of adding them in
using the Date Probe.
To use the Data Probe you first must ensure that it is empty. For Guardus hardware users,
You can do this by going to the Information tab, and clicking on the “Clear Wand”
button. For other hardware platforms, you will need to perform a download before using.
Once you are sure the probe is clear you can touch the 12 buttons that make up the
Incident Wallet.
You MUST follow a certain order when touching the buttons so that they will be entered
in properly. The order is as follows. Start at the top left of the Incident Wallet (Button
1) and go across the top row touching all the buttons. Then move down to the second
row, and start on the left and touch all of those buttons. Continue adding in each row,
starting at the left side going to the right side. You should hit the buttons in this order:
“1”, “2”, “3”, “4”, “5”, “6”, “7”, “8”, “9”, “C”, “0”, “E”.
Once you have all 12 buttons read into the data probe click on the “Read Data Probe”
button and place the Data Probe on the downloader. All 12 buttons will be added into the
system and it will be automatically saved for you.
You can continue this process to add all of your Incident Wallets.
1. Before you begin the first thing you will need to do, is to take an empty probe, and
read all the RFID buttons on your incident wallet. This MUST be done in order of
sequence, starting from 1,2,3,4,5,6…. And ending in …C,0,E.
When you are finished, download the probe. (Note to ActiveGuard users: If you are
using this hardware platform, you will just need to read the buttons, as the data is
transmitted as you do so.)
2. In the Programming area, click on the “Numeric Buttons” tab. This is where all the
Incident wallets are added into the system. As you can see it looks a lot like an Incident
Wallet layout.
The first thing you will need to do is to create a name for your Incident Wallet. This will
help you keep them organized, if you have more then one. To do this, click the “Add”
button and fill in the “Incident Wallet Name”. Once you have entered a name, click
on the checkmark button to save it.
(Note: Learn Mode organizes checkpoints read in ascending order. The first button you
read (1) will be at the top of the list, while the last (E) will be at the bottom.
5. The serial number should now populate the 1 field. Repeat this process, for all 11 other
buttons, taking care to match each serial number with it’s corresponding button. As you
add them, the entries will disappear from Learn Mode. When you are finished, your
wallet will look like this:
An Event set is a grouping of event descriptions, and numerical codes, that can be used
to report incidents that a Security Officer may encounter during the course of their
patrols.
In most cases, a single event set is all that is needed to use this functionality. However
you can create as many as you require. For example, in some scenarios, you may have
two or more separate site locations that share similar events, but use different codes to
report them. In others, you may have completely different events to report altogether. In
these cases, individual event sets and codes can be created for the sites.
To begin, we will need to access the Events area. Go to Data, Programming, and select
the Events tab.
Click on the plus button (+) to add a new Event Set. Choose a name for the event set by
filling in the Description field, then click on the checkmark button (“√ ”). to save your
changes. Once you have the Event Set created, you are now ready to begin adding events
to it.
Before you can use the event set you created, you must add events to it.
Events are by definition occurrences that a Security Officer encounters within the
duration of a given tour. Some typical events can range from an unlocked door, to a
broken window, to a fire extinguisher check, and vary with the needs and uses of the site
being protected.
1. Click on the plus button (“+”) to begin adding a new event. Under the
“Description” field, type in the name of the new event you are adding. Remember
to be as descriptive as possible- what you type in this field will be what is shown
in your reports later on.
2. Next, you will need to assign your event an Event Code. This will be the number
that the Security Officer enters on the incident wallet to “report” it. The event
code can be any value up to 5 digits in length, but can NOT start with 0.
3. When you are finished, click on the Checkmark (“√ ”) button to save.
If you require a secondary level of information with your events, you can configure your
events to use and display these alongside the event descriptions in the reports. There are
two additional options you can use for this, depending on your requirements: Boolean
values, and Reference values.
Reference values are numerical values that can be entered in the incident wallet after the
associated event code has been read by the wand. They can be useful in instances such as
to report the number of a door that is unlocked, the temperature of a refrigeration unit, the
pressure of a boiler, etc. To make the reference value more meaningful on the reports,
you can use the Suffix and Prefix fields to add additional information.
For example, let’s say that one of the event descriptions is that of “unlocked door”, and
has been configured to use a reference. Additionally, “Door#” is in the prefix field. When
the security officer next reports the Unlocked Door event, and enters in the required
reference value of “101”. When the report is later reviewed, the report will show up as
“Unlocked Door- Door# 101 .
Alternatively, the other second-level entry option you can choose, is a “Boolean
Reference” value. Unlike the reference value option, this does not allow the Security
Officer to choose numerical values to enter after the associated Event Code is reported-
instead, it gives them two choices to enter: “Yes” or “No”.
This value is appended to the end of the displayed Event as it shows up in reports, to
indicate the status of the event. While not often used, where this becomes particularly
useful is on Safety Equipment or Maintenance checks. In such scenarios, events can be
used with a “yes” or “no” value indicating if the equipment is in serviceable condition.
Not only does TourTrax support incident wallets, but it also supports single button
events. Unlike incident wallets where you only need 12 buttons to make an unlimited
number of events, with single button events each button you configure uniquely
represents an event to report.
2.) Use one of your Data Probes to register the iButtons or RFID tags you wish to
enter as your event buttons.
When you are finished, download the report. (ActiveGuard users: your data will
already be stored in TourTrax). On successful transfer, every button you read will
show up in a full report as an “unknown checkpoint” like so:
3.) From the menu at the top left of your screen, go to Data, Programming. Select
the Events tab.
4.) If you do not currently have an event set, you will need to create a new one. If you
have already done so, select the Set.
5.) Click on the plus button in the Event Properties area to add a new record.
6. Next, right click on the Event Code field, and Select Add From Learn mode.
The Serial number of the ibutton/RFID tag has now been assigned to the system.
Click on the checkmark button to save.
To add more events to the event set, repeat this process. When you are finished,
your Event List should look something similar to this:
Your events are now ready to use. It is recommended after you are finished to run a test
tour, using the events you just created to make sure there are no inconsistencies.
Operation of single events in tours is simplistic. To report an incident, the officer must
first read the checkpoint associated with the area he/she is in, then the iButton/RFID Tag
associated with the event he/she is reporting.
Memorized filters allow you to save commonly used filters as presets eliminating the
need to recreate them over and over again. They are also used with the AutoGen add-on
for TourTrax, to filter out data such as time and date ranges in automated reports emailed
to recipients.
To begin creating a Memorized filter for use, first click on the Plus button (‘+’), and type
a name under the “Name” field. You can then configure the other options in the list as
required. To add a filter option, you must first enable it by selecting the checkbox next to
it, then use its associated dropdown menu to select the necessary criteria. The filter
options to choose from are as follows:
Branch- filters so that only data entered from the specified branch is shown
Client- Filters so that only data from the Clients selected is shown.
Facility- Filters so that only data from the specified Facilities are shown. Useful if
you are working with multiple facilities.
Site- Filters data so that only data from the specified site(s) are shown.
Officer- Filters so that only tour data from the selected officer(s) are shown.
Event- filters the data, so that only the specified events are shown.
Start Time/End Time- Allows you to set that starting and ending time and date
range of what you want to see in your reports (Ie, if you only want to look at a
specific shift, such as 7am-7pm the previous day, and contain 24 hours worth of
data in a single download). The time is in 12-hour format, and the general syntax
is MM/DD/YYYY Hr/Min/Seconds (am/pm).
Apply Date/Time filter to Tour Details- This option allows you to filter out all
data from tours, except from within the specified range. Any tour data entered
slightly before the Start Time, or after the End Time will be cut out of the viewed
report.
Maintain Date Range- Automatically updates the Start and End time and date
ranges in the given filter. This is especially useful if you want relatively low
maintenance out of a given filter. For example, let’s say you are off-duty
weekends, and want to check your officer’s progress during your absence with a
Memorized Filter, every Monday. Keeping the Maintain Date Range option
selected will ensure that you will not need to change the time and date range
every single time you use this filter for this purpose.
Note: this option adjusts the date range in relation to your current date at the time
of usage. Going by the above example, if you were to use the said Memorized
filter on Tuesday, it would adjust to show data from Sunday-Monday. If you were
to view it on Wednesday, it would view the data from Monday-Tuesday, and so
forth.
To use the saved filters you need to open the filter pane by going to the File menu and
selecting “Filters”. When they are loaded you will see at the bottom of the panel a combo
box that list off all the Memorized Filters. To use any of them, just select the one you
would like to use and then click on the “Set” button. This will set all of the filter
parameters they are contained in the selected Memorized filter record. If you would like
to clear the filters then you just need to click on the “Clear” button.
The Client Information Area is the central area where both checkpoints and internal (non-
reported) site information is stored. It organizes this information in an easy-to-use, easy-
to-update 3-tier structure, called the CFS (Client, Facility, Site) tree. The tree progesses
as follows:
- The Client Level. This is considered the top level of a CFS tree, and can be
named to represent either the name of the Security Company or the name of the
Client that is being protected.
- The Facility Level. This is the secondary level of the CFS tree, or one “Under”
the client level. The facility level is often used to describe the name of a particular
property or building on a property monitored by TourTrax.
- The Site Level. This is the third and lowest level in the CFS tree, or one “under”
the Facility level. This is commonly used to break down what falls under the
Facility level into “zones”, or groupings. For example, some Facilities may have
multiple floors to monitor. In such instances, multiple site levels may need to be
created for each of these areas(using names such as First Floor, Second Floor,
etc). It is under the Site level that checkpoints can be added and organized.
This Hierarchal system can be particularly useful in scenarios where multiple properties
or numerous quantities of checkpoints are used, as it allows the TourTrax Administrator
to organize them into groups for easier and faster searching/checkpoint maintenance.
To add a Client, start by right clicking on the white area on the left side of the Client
information area. Under Client Name, choose the name you will call the new entry.
Under the Branches field, select the Branch this Client will belong to (if applicable).
When finished, click on the Checkmark button on the upper right-hand side to save.
Repeat the process until you have finished adding all desired Clients.
Now that you have added your Client level, the next thing you will need to do is assign at
least one Facility level to it.
To do this, left-click on the desired Client to select it, then Right-click on it and choose
Add Facility. Type a name for the Facility under the Facility Name field, then from the
Branch dropdown menu, choose the associated Branch the entry will belong to (if
applicable). When finished, click on the Checkmark button to save. To add more facilities
as required, repeat this process.
In the following example, “HQ”, “R&D Lab”, and “Warehouse” are the three facilities
assigned to the Client “RhinoRugged Security”.
Last, but not least, we will need to set up at least one Site level under the Facility(s) you
created. It is in these sites that your checkpoints will be entered into TourTrax.
To add a Site, first click on the desired Facility to add it to, to select it. Then, right-click
on it, and choose “Add Site”. Under the “Site Name” area, fill out the name of the Site
you are adding. From the Branch dropdown menu, select the Branch that will be assigned
to this site (If applicable). After you are finished, click on the Checkmark button to save
the record. To add more site records, repeat the process.
In the following example, ‘1 Basement’, ‘2 First Floor’, and ‘3 2nd Floor’ are three Sites
in the ‘R&D Lab’ Facility.
This method is especially useful for when your checkpoints have not been mounted, or if
you need to make a minor change, such as to add or edit one or two more checkpoints to
an existing installation.
1. Select a site in the Client Information window as shown below. Click on the
Checkpoints tab.
3. Place the button on the Downloader, and press the button with the 3 dots (‘…’).
Note: For each Tour you want to create, you MUST have one button marked as a Start
button.
Learn Mode is designed to minimize the data entry requirement, and help automate the
task of adding a large number of checkpoints to your TourTrax installation. This is
especially useful if your checkpoints are already mounted and they can not be easily
brought to the downloader. If you use RFID-based hardware, it is also the primary
method in which you can add checkpoints.
It is important to take steps to ensure that you accurately read in the checkpoint
information. The best way to do this is to make a list of the description of each
checkpoint you are going to touch (Use a chart similar to the one depicted below).
Checkpoint Description
1 Main Entrance1
2 Main Lobby
3 Emergency Exit
4 Administration
5 Executive Offices
6 Computer Lab
Once you have created a chart, you can then, using an empty Data Probe, read each
checkpoint with the Data Probe, carefully following the order in which you have
listed each checkpoint in your description chart.
NOTE: All data that is in the “Learn Mode” window must be assigned to a Site
before the Client program is closed. Any remaining data in the “Learn Mode”
windows will be lost once the Client program is closed and you will need to enter it in
again.
1. While in the Site Level, first click on Checkpoints tab and then click on “Learn”
button.
3. Receive the Data from the Data Probe by placing it on the downloader, and
clicking on “Receive Data” button and selecting “From Data Probe” option.
Note that each checkpoint will be listed in the order it was read i.e.: Checkpoint
001 will be the first, Checkpoint 002 will be the second etc
5. Once all checkpoints are selected, click on “Add to List”. The selected
checkpoints will be appended to the Checkpoints list on the site record.
6. Proceed with editing the description to match the description you have assigned
by selecting a checkpoint, then clicking on “Edit” and then fill in a description.
1. Before you begin, It is important to take steps to ensure that you accurately read in the
checkpoint information. The best way to do this, would be to create a list of each RFID
tag you will be adding. Number the list, as below:
Checkpoint Description
1 Main Entrance1
2 Main Lobby
3 Emergency Exit
4 Administration
5 Executive Offices
6 Computer Lab
2. Once you have created the chart, use an empty wand to read each of the checkpoints in
sequence, starting from checkpoint #1.
When you are finished, download the wand. (Note to ActiveGuard users: As the Data
Probe transmits data the moment it receives it, you will just need to read the RFID tags).
3. Now we are ready to start adding checkpoints. Let’s start with the first one. Select a
site by clicking on a site in the Client Information window as shown below. Then click
on the Checkpoints tab.
4. Click the ‘Add’ button. This will open up the Checkpoint Properties window.
Right-click in the white Serial Number field, and select Add from Learn Mode, shown
as below:
6. Next, type in a description for the checkpoint you added, and specify whether or not it
should be used as a start button.
Note: Learn Mode organizes your checkpoints in Ascending order, as they are read. The
first checkpoint you read will be at the top of the list, while as the last will be at the
bottom. As you add checkpoints, their corresponding checkpoints will be removed from
Learn Mode, shortening the list.
Reassigning checkpoints allows you to move checkpoints from one Site level in Client
information to another, making it easy re-order your checkpoint assignments with out
having to type in any new information. You can do this one checkpoint at a time or in
bulk, by selecting multiple checkpoints.
1. From Client Information, click on the site that you are moving checkpoints
from.
2. On the Checkpoints Tab, highlight the checkpoint(s) you want to reassign by
holding down the <ctrl> key and clicking on them.
3. Next click on “Reassign”. This brings up a window alerting you that you should
also go into the Tour Builder and modify your tours if needed. Clicking “OK”
removes the highlighted checkpoints from the Site and sends them to the “Learn
Area”.
4. Now, click on the Site level you will be adding the checkpoints to. Click on
Learn, to bring up the Learn Mode area. In this area you will see all checkpoints
that are currently not assigned to any sites.
First, begin by accessing the Officer ID Properties area. Click on Data, Officer.
1. Click on the plus button (+) to add a record. Under the name field, add the
name of the officer.
2. Place the button you are assigning to the Officer on the downloader, engraved
side down, and click on the button with the 3 dots (…) Fill out additional
information as required, and click on the Checkmark button when you are
finished to save.
Another way to add Officer Buttons is to mass add them, using the Data Probe. To do
this, you need to first have a clear Data Probe, as everything that has been entered into it
will be imported into the database.
1.) Organize your buttons. Make a note of them, and what officers will be assigned to
each. The easiest way to do this would be to line them up in a row on a sheet of paper,
and write the names down of each officer each next to a button.
2.) Use the Data Probe to read each of the buttons, from the beginning of the row to the
end, not breaking the sequence. (This is important, to keep order of which button is
which).
4.) From the Officer Properties window, click on the “Mass Add” option, and select
“Export Data”.
5.) You will be presented with a prompt asking if you want to clear the Data Probe after
the data downloads to the computer. Since you will not need the data in the probe
afterwards, click on “Yes”.
7) Choose a name to save the file as. (It may be a good idea afterwards to save the file
itself, as it would eliminate the need for organizing and entering the buttons you just
worked with).
8) Now, from the Officer Properties window, click on Mass Add, and choose “Import
Data. Navigate to the folder you saved the file, Select it, and click on Open.
9) The new officer buttons are now added to the officer list, labeled as “checkpoints”, and
with numerical values starting with “001”, in the order you entered your officers. List the
Officer names corresponding to the buttons they are assigned to, and close the window
when you are done.
To avoid confusion, we recommend you enter your officers into the system one by one.
2.) Using the Data Probe, read the RFID tag of the officer you will be entering into
the system. When you are finished, transfer the information to TourTrax by
placing it on the downloader. (Note to Activeguard Users- your information is
automatically downloaded on button read).
3.) Click on the “+” button to add a new record. Fill out the officer’s name.
4.) Right-click on the ID field, and choose “Add from Learn mode”.
5.) Select the serial number entry you wish to add, then click on Add From List.
The ID will now appear in the officer record. Click on the checkmark button to save.
Note: When adding multiple officers at once, it may be more convenient to mass-add all
of their associated tags at once, and add them to the officer list afterwards. When you do
so, they will be listed in Learn Mode, in ascending order. The first tag you read will be at
the top of the list, the last at the bottom, and so forth. As you add officers using this
information their corresponding entries will be removed from the Learn Mode area.
Tour Builder is the section of the TourTrax client that deals with your tour behavior, and
organizes your checkpoint data in reports. How your tours look depend on how you
configure this section. In this area, you can assign what start buttons and checkpoints to
use with a given tour, as well as additional information such as the maximum tour
duration, time allowed between checkpoints, etc.
1. From the main window of TourTrax Client, click on ‘Data’ from the menu, and
then select ‘Tour Builder’.
2. A window will be opened as follows. To build a new tour, click on Add button(“+”).
The rest of the options below, with the exception of adding checkpoints to your
Tour Details area, are optional:
If you want the tour to be ‘Sequential’, select that option by just clicking on the box
ahead of ‘Sequential’. If you want it to be timed, select the ‘Timed’ option by clicking
on the box ahead of ‘Timed’. To save your information, click on the Checkmark
button.
Sequential Tour allows you to set the order in which checkpoints must be hit on a given
tour, the first button being on the top of the list, and the last being on the bottom. Leaving
this option unchecked will enable the officers to visit checkpoints in any order they
choose as long as they are within the tour schedule specified. They are still required to
register the start button of a given tour before visiting any checkpoints in said tour.
Tour Duration- This option allows you to set the maximum duration of a given tour.
When you have finished creating your tour information, click on the Checkmark button to
save the record.
4. Now that you have created your baseline Tour information, you will need to add
checkpoints to it. To do this, make sure the Tour you are working on is selected in the
Tour List, and move down to the Tour Details area. Click on the Multi-Add button.
The Multi-Add window will now appear. Use the Client, Facility, And Site dropdown
menus to select the area in Client information you will be adding checkpoints from.
Now, click on the checkpoint you are adding to the tour. To add multiple checkpoints at
once, hold down on the CTRL button on your keyboard, and click on each of the
checkpoints until you have made your selection.
The checkpoints are now added, and the Multi-Add Checkpoints list can be closed. To
add more checkpoints, adjust the Client Information filters accordingly, and repeat the
process.
Note: there are actually two Download Guardian programs- one for Guardus systems
(Blue Shield), and one for the other hardware platforms (Green Shield.)
To begin, first run the Download Guardian shortcut located on your Desktop, or in the
Start menu. Double-click on the Download Guardian icon in the windows system tray
(shown below).
Click on the Setup button. The configuration screen will appear as below:
In some cases, it may be necessary to disable the Guardus Download Guardian, such as
when using a hardware type unsupported by this module (such as Activeguard or PES).
In these cases, to do this:
1. Double-click on the Download Guardian System Tray icon, and select the
Download Guardian Setup icon.
Downloader Status (middle)- informs you whether or not Download Guardian was able
to connect to your Downloader hardware.
To Install:
The Command Prompt window should appear. Use it to navigate to the folder you
installed the TourTrax software to, using the “CD” command. (By default, the program,
and all its files, are installed to C:\Program Files\TourTrax, so you would type the
following command to get to it as illustrated below:
2.) To Uninstall the TourTrax Download Guardian as a Service (if you remove the
software)
As with installing the Service, navigate to the DG folder located within the program
folder you installed the software to, using Command Prompt. Type TTXDGSVC
/uninstall , and press Enter. A message should appear confirming the service to be
uninstalled:
So to summarize:
If an Officer is signed in he can be signed out in one of 2 ways
- touching his ID button again (then it is Unknown who is signed in)
- touching another Officer Button (signs in new officer)
If an Officer is signed in and a Supervisor Button is touched the current Officer is NOT
signed out.
- A Supervisor Check is logged.
If a Supervisor is relieving an assigned Officer, the Officer must sign off. Likewise, if an
Office is relieving an assigned Supervisor, the Supervisor must sign off.
While tour operation in TourTrax has been designed with ease of use in mind, there is a
key sequence you must follow while using your Data Probes in the field.
1.) Begin of Tour- Start the patrol by signing in using an officer button. Touch the
wand to the button to start the tour.
2.) Start Of Tour- Start the desired tour, by touching the wand to it’s corresponding
Start Button.
3.) Perform the Tour- use the wand during the course of your tour, making sure that
all of the buttons mounted in the areas you have been in have been registered.
(Note: any checkpoints you have not registered will show up as “missed” in later
reports)
4.) Come back to the start of the tour. If you have finished your tours, you can choose
whether or not you want to repeat the tour, perform another configured tour, hand
the probe to another officer to perform a tour, or download. Please note that each
time you start a tour, whether it is the same tour or a different one, you must read
it’s corresponding start button first. This is critical, as it tells the PC in later
reports of your intentions to start a new tour.
Recording Events
8 Vehicle Check
In addition to recording the date, time, 9 First Aid Box
location and type of Incident/Event and who
the reporting officer is TourTrax provides full 10 Fire Phone
narrative and categorization of Incidents. See the input forms available to authorized
TourTrax Users and depicted below.
Note: while registering a numeric event, you can, at any time before hitting
ENTER, register a button stamped as CLEAR to restart entry of the numeric
event information.
For example, to register events 4 and 10, the following steps should be taken:
Remember the button identified by CLEAR performs input correction. For example, if
you wish to enter event 4, and start out touching button 5, by mistake, this situation can
be corrected this way:
If the event being registered requires a numeric reference, you can enter it just as the
event code, right after the ENTER corresponding to the code.
First, generate a TourTrax Event Report by selecting your criteria and clicking on
Events, then the incident you want to edit.
The Edit Incident window that opens up, as shown below, opens allowing an authorized
user to add narrative and other information to the event.
Incident Number
Reporting Officer
Client
Facility
Site
Incident Date/Time
Description
Category
Report Date/Time
Narrative
2. A Tour Builder window is opened as shown below. Use the Tour Description list
to select the desired Tour to edit.
4. Click on the Minus button ( - ) above the list of checkpoints to delete the checkpoint
from the Tour.
5. A confirmation window will appear, asking you to confirm whether or not to delete the
record. Click on OK to continue.
1. Click on the Data menu option from the TourTrax Client main screen, and then select
Client Information.
2. Navigate through the Client, Facility, and Site records until you locate the desired
checkpoint to change. When you have found it, select it and click on Edit.
Note: If you need to make changes to a Start Button, remove it from Tour
Builder first! Failure to do this may cause problems with the Tour it is associated
with.
4. Although you have made modifications to the checkpoint in Client Information, these
changes will not be reflected in Tour Builder. You will have to change it in the Tour
For instance, there are five checkpoints except Start Button in the Tour of “night patrol”
as shown below. The current record in the area of Tour Detail is “Administration”
In the Tour Information area, the current record is “HQ Exterior Tour”. You can use ,
, , to change the Tour from “Tour 1” to the first Tour, the last Tour, prior
Tour, and next Tour.
: Insert new record (See Tour Information and Tour Details under Tour Builder.)
For instance, if someone used another computer to change the content of a record via
network, this button can be used to update the content of the record on your computer
If you want to have a look at the detailed information of the actual tour, you can simply
click on the Tour Name that corresponds to the Tour of your choice, and a full report of
the download will pop up displaying all the information regarding the tour.
A TourTrax Full Report provides you with a checkpoint-by checkpoint detailed listing of
each performed Tour. It describes the date/time the tour was performed, the tour name,
who performed the tour and the final Status of the tour. Then it details in what time each
checkpoint was read and the status of each checkpoint. There is a Summary bar at the
bottom of each tour that displays Duration, Tour Hits, Total Hits, Event, Missed, Gaps
and sequence.
- OK: It was hit correctly which means it was hit in accord with the assigned tour
schedule.
- Missing: The checkpoint was built into the tour but was not hit by a Patrol Officer
in this tour.
- Extra: The checkpoints hit exceed the assigned hit amount for the given tour. That
is it was hit more times than it is scheduled in the given tour.
- Additional: The checkpoint hit is not a part of current tour.
- Unknown: The checkpoint hit is not identified in the Client Information Database.
- Event: An incident was reported when the checkpoint was read.
- Missing: The checkpoint was built into the tour but was not hit by a Patrol Officer
in this tour.
- Early - X Mins: The checkpoint was hit X minute earlier than the assigned
schedule of a Timed Tour.
- Late - X Mins: The checkpoint was hit X minutes later than the assigned schedule
of a Timed Tour.
- Out of Sequence: The checkpoint was hit in a different order with the given
Sequential Tour.
- Anti-Vandal: attempts to damage the device. This includes fall/impact damage,
and electrocution. (Note: Your hardware may or may not necessarily support this,
depending on what was purchased.)
A TourTrax Event Report displays individual Tours that events were declared with, and
what was reported.
- Event Status: An incident was reported when the checkpoint was read in the tour.
A TourTrax Missed Report allows you to see all missed checkpoints in the performed
tours.
- Missing: The checkpoint was built into the tour but was not hit by a Patrol Officer
in this tour.
- The Full with Serial Numbers Report generates a full detailed report of your
selection, also showing the individual serial numbers of each checkpoint.
- The Time Apart Report generates a report displaying the frequency in which each
location has been checked, and the amount of time that passed before it is visited
again. This report can be useful in determining which areas require more or less
supervision, to optimize officer coverage.
- The Officer List Report generates a list of your officers and their corresponding
officer buttons.
As an example of how this feature works, let’s say you desire to review a particular
Security Officer’s performance in the field. To do this, we would first begin by enabling
the Filter options to make changes. Go to File, Filters.
You can now add your desired criteria to the filter. Place a checkmark next to the Officer
filter item to enable the option. Now, use the dropdown menu to select the officer desired.
Memorized filters allow you to save commonly used filters so that you do not have to
recreate them over and over again. In addition to manually creating yours in the
Programming area (see the Using Memorized Filters section on Page 39 for details on
how to do this, synopsis of the different filter options), you can access them by selecting
the desired filter from the Memorized Filters area, and clicking on “set”, then the desired
report you wish to generate..
You can also edit them on the fly after you’ve “set” them using the filters pane, by
clicking on the “save” button.
When you have selected the desired options, click on OK to send the report to your
printer.
To save a report outside of TourTrax, first generate, then click on Save As and choose
the type of file to export it as.
Note: Typically, it is recommended to primarily use the PDF option, as this is the only
format listed that cannot be edited in any way once generated.
In some cases, you may want to personalize reports by modifying the report header
and/or footer images with your own company’s logo.
To do this:
2.) Next, using the Report Images area, assign the desired images you want to place
in your reports, using the browse buttons . Currently, the supported filetypes
that can be used are BMP, JPG,PNG,ICO,WMF, and EMF.
For best results, the report header should be 307x73 pixels, while both footers
should be 150x50. Keep in mind that images drastically larger or smaller than
these sizes will be automatically scaled to fit.
When you are finished, close the Programming window, and generate a report of your
choice to test.
By default, TourTrax only shows download data that has been performed up to 60 days
prior to viewing. This makes the download list less cluttered, and the data can still be
recalled when it is needed. However, in some cases you may want to change this, to
allow you to see further into past downloads, such as if you are auditing the last
To do this:
3.) Under the Download List area, change the Number of Days to Display to the
desired value. When you are finished, close the Programming window. Changes
should take effect immediately.
If you click on the Work Order button, a Create Work Order window will open as below
which allow user to fill in some information so that a Work Order can be fully created.
Once the renovation or repairing is done, place a checkmark in the box ahead of “Work
Order Closed?” and fill the date in its following blank field.
Open Records means Open Work Orders i.e. the corresponding repair work by the
facility department has not been done yet whereas Closed Records represents Closed
Work Orders i.e. all the necessary repair work has been completed.
The Security Module (SM) controls access to the application through a login screen
where a user name and password are requested. Administrators are encouraged to specify
a unique user id and password for each user. Users are encouraged to not share their user
ids and passwords with others.
After entering a user id and password on the login screen, the SM verifies the user is still
valid, loads the user access configuration from the security database, and applies the
user's restrictions to the application. The module will then disables or makes invisible all
the application's components the user is not permitted to access. These restrictions can
apply to any individual buttons, panels, navigator button, data display grid, grid columns,
fields, toolbars, menu items, Action items, or control identified by the developer.
Primary Features:
User Administration
The User Administration Module allows the security administrators to have control over
the security of the application. The administrator can, for instance, add new users and
profiles, modify the access permissions and visualize the information of a certain user's
audit. Only users that are administrators can access the administration module.
The Administration module is accessed through the User Administrator option of the
Users menu in the TourTrax Client.
The User Data tab allows the administrator to view the following information:
• Name of the User: also known as the user id, this is the name used by the user to log
in into User Administration.
• Real name: This is the real name of the user.
• Password (encrypted): the user’s password
• Profile to which the user belongs.
Important: The data above is general to all applications that share the security database.
User Expires: indicates if the user will have a date limit to use the application. When this
field is checked, the field Expiration Date will be enabled.
• Expiration Date: indicates the date on which the user won't be able to use the
application.
• Audit Mode: indicates that the user's actions will be registered for visualization in the
audit module.(not recommended unless absolutely necessary, as this increases both
machine resources and potential database size)
• Active: indicates if the user is enabled to use the application or not.
• Last Password Change: indicates the date of the last password change made by the
user.
• User is Administrator: identifies whether the user is a security administrator. If the
user is marked as administrator, they will be able to access the User Administration
module.
Important: The data above applies to the current application. In other words, a user
can be active in one application and not active in another. Also, a user can be an
administrator in one application and not be in another. That makes possible more
flexibility in security administration when the SM component is being used in
environments with more than one application.
The change password button exists so that the security administrator can change a user's
password. This resource is useful in situations where the user has forgotten it.
Just above the User List, User’s Data, and Additional Information tabs are a series of
buttons to accomplish a variety of user related operations.
The New User button shows the screen for adding a new user. The Administrator must
enter the user's id, real name, and password. The system initially suggests the user’s
name as the password. As an option, the Administrator may specify the profile to which
the user belongs (the completion of that field is not obligatory) and if the user activities in
the application are subject to auditing (Audit Mode is checked.)
The Change Data button displays the User Data tab. The Permissions button displays
the Permissions tab with the current users set of access rights. The Delete User button
will delete the user and user’s information from the security database. If the module is
used for multiple applications, note that the user will be removed from all the
applications.
The User Profiles tab also contains four buttons to accomplish various profile operations.
The New Profile button will display the screen for adding a new profile. The users will
be able to assign a description of the profile, if users that belong to that profile are forced
or not to change passwords, the interval in days as to when a password change will be
required and whether the users of the selected profile are in audit mode. Note: the new
The button Data Change displays the Profile Data tab. The Permissions button displays
the Permissions set for the current profile selected. The Delete Profile button removes
the profile and all associated information from the security database. Notice that the
profile will be eliminated for all applications.
The Permissions tab is used to grant or restrict access to items in the application for each
user, profile, or for a group of users through the profile. Notice that when the Users tab
is selected, additional buttons labeled: Apply; Restore and Restore from the Profile are
displayed. These buttons allow the administrator to apply a profile permission set, re-
apply a profile permission set, or restore a changed permission set, respectively.
When the tab User Profiles is selected, the buttons Apply, Restore and Update Users
are displayed.
To change the permissions of a user, the administrator first must select the user from the
list and then select which application form with which the administrator wants to work.
The List of Forms of all forms subject to administration will be available from all forms
and data modules in the application.
NOTE: Right Click the mouse button to access the menu for fast configuration. See the
illustration to visualize the commands of the menu.
IMPORTANT: If the administrator changes the form or changes the current user without clicking
the Apply button first, all changes will be lost.
To cancel all changed attributes and restore the user's original settings, the Administrator
may press the Restore button. Note: the Restore button will only have an effect if the
administrator has not yet clicked the Apply button.
NOTE: If you do not assign access to a parent object, then all child objects will not be
accessible no matter what permission you assign to them.
With this tab the administrator can view the Login/Logout information of all application
users it is possible to limit the amount of information displayed by specifying restricted
From and To dates.
The administrator may also select from a list of users for whom access will be displayed.
In the tab User Activities, the administrator may display indicators of what the user has
been doing in the application, like the components they have manipulated and the values
they have inserted, modified, or deleted. The administrator has the ability to filter the data
by selecting the form or data module, and the user of interest. It is also possible to filter
the data for a specific date range
The Component Utilization tab allows the administrator to view the pattern of access by
specific form, data modules, or registered components. This allows the administrator to
identify all users that used a given component during a specified date period.
Current Users
This tab shows a list of the current users that are connected to the application. Click on
the button Refresh User List to update the list.
• Time Out (in minutes): specifies the time in minutes the application can be idle
(without the user using it). Passing the time specified, the login screen will be
executed again.
• Maximum number of login attempts: this value overrides the value that is
configured by the developer in design time.
• Disable user after exceeding login attempts: this component disables the users’
access after N attempts of login without success. In other words, the user won’t be
able to use the application until the security administrator gives him permission again
• Maximum number of days without using the application: If the user does not use
the application during N days or more, this user won’t be able to use the application
again until the security administrator gives him permission.
• Maximum number of passwords in the “Password History”: The component keeps
the history of N password to avoid the users to repeat them until reach the specified
limit. A password can also be only repeated after it reaches the position of Nnd older
password
• Allows multiple logins for a same user name: The component can prevent that a
same user name be used to enter in the application more than once at a same time. The
standard configuration does not allow this behavior.
Installation
On installation the user must be logged in as an Administrator to allow the Installation program to
add values to the “HKEY_LOCAL_MACHINE” hive in the registry. Additionally, some
required files are placed on the machine’s C:\Windows\System32 folder.
Setting information is stored in the main TourTrax application folders and sub-folders. These
files are located in “C:\Program Files\TourTrax” by default. For best performance, The NTFS
permissions for this folder and all subfolders must be configured with full access, for all users.
Setup
Download Guardian
The Download Guardian has a Permissions area that needs to be configured by an administrator.
In the Permissions area the Administrator can assign Network Users and Groups and give them
access to shut down the Download Guardian, and to make modifications to the DG settings.
The Download Guardian also stores some downloaded data in a folder called “DGFiles” that is
located in the “C:\DGFiles” directory.. For best performance, The NTFS permissions for this
folder must be configured with full access for all users.
Server
The TourTrax Server stores data in 2 folders that are located on the root of the C drive by default.
These folders are: “C:\ServerDownloads” and “C:\ServerLink” by default. For best
performance, The NTFS permissions for this folder must be configured with full access for all
users.
Client
The TourTrax Client will store data in the ClientLink folder that is located at: “C:\ClientLink”
by default. For best performance, The NTFS permissions for this folder must be configured with
full access for all users.
Control Panel
The control panel is where all of the above mentioned folder settings are set. It is also where you
will find the connection settings for the server. If you want to allow the client to have access to
making changes to these paths and connection information then they will need to have access to
the control panel. This is typically set up by the Administrator during initial setup and then not
changed after that so normal access to this area is not needed.
Officer Training
- Hardware
o Data Probes (Wands)
o Downloaders
o iButtons
o Incident Wallet
- Tour Procedures
o Patrol Officer Identification/”Signing in”
o Reading Start Buttons
o Reading Checkpoints
o Proper Read Tones (indication a button is read)
o Time Intervals (if used at site)
o Sequential (if used at site)
o Logging off the Data Probe
- Downloading
o Overview of the Download Guardian
o Downloading Data Probes