EST-EST3-v1.0-Access-Control-Database-User-Manual
EST-EST3-v1.0-Access-Control-Database-User-Manual
User Manual
P/N 270961 • Rev 1.0 • 25OCT01
DOCUMENT HISTORY
Date Revision Reason for change
25OCT01 01.00 Initial release.
Y Glossary • Y.1
Z Index • Z.1
Important information
Limitation of liability
This product has been designed to meet the requirements of
Underwriters Laboratories, Inc., Standard 294. Installation in
accordance with this manual, applicable codes, and the
instructions of the authority having jurisdiction is mandatory.
EST shall not under any circumstances be liable for any
incidental or consequential damages arising from loss of
property or other damages or losses owing to the failure of EST
products beyond the cost of repair or replacement of any
defective products. EST reserves the right to make product
improvements and change product specifications at any time.
While every precaution has been taken during the preparation of
this manual to ensure the accuracy of its contents, EST assumes
no responsibility for errors or omissions.
Intended audience
This manual was written for people who have a working
knowledge of Windows-based computer programs.
Organization
This manual is organized to serve as a guide for the first-time
user. It takes you through the steps required to set up the system
for the first time, introducing you to each ACDB feature or
function as it’s needed. The chapters are presented in the
sequence you will need as you work through the ACDB program
from start to finish.
If your system has already been set up by your administrator and
all you wish to do is add users, proceed to Chapter 11:
Cardholders basic. For you to be able to gain access to the
ACDB, your system administrator must set you up as an operator
with proper privileges.
The manual consists of the following chapters:
Chapter 1: Introduction. This chapter introduces you to the
manual and explains the basic concepts of access control.
Chapter 2: Getting started. This chapter provides information
and procedures required to navigate and customize the ACDB
program. It also describes the Log In process for first-time users
and shows how to import a Resource Profile (RP) file.
Chapter 3: Basic operations. This chapter shows you the steps
for common operations including downloading, saving, backing
up, and exiting from the program.
Chapter 4: System and hardware configuration. This chapter
provides information about the administration functions of the
ACDB. It also provides procedures for configuring hardware
elements of the program.
Chapter 5: Operators. This chapter provides general information
required for defining and creating additional operators. The
functions the operators can perform are controlled by the
privileges that are assigned to them.
Chapter 6: Tasks. This chapter defines ACDB tasks and the
important functions they perform. Some of the functions that
tasks perform are system updates, access event history
management, database maintenance, and report automation.
Chapter 7: Outbound ports and routes. This chapter shows you
how to configure your system to communicate with the access
Purpose
The purpose of this manual is to give users of the Access Control
Database (ACDB) detailed operating instructions for the
program.
This manual provides a reference for both novice and
experienced users of the ACDB software. The manual assumes
that the necessary hardware and software installation has been
successfully completed.
Note: Depending on your specific operator privileges, you may
not see all of the system menus shown or described in this
manual.
Summary
Welcome to the Access Control Database (ACDB). The ACDB
has feature-rich software that makes it easier and more efficient
to manage access control at your site. This chapter introduces the
ACDB program, defines access control, and discusses the
program’s functions within an integrated life safety system. It
also covers the conventions we use in this manual when giving
the instructions for completing specific tasks.
Content
Using this manual • 1.2
Mouse vs. keyboard • 1.2
Step-by-step instructions • 1.2
Available versions • 1.3
Stand-alone system requirements • 1.4
Network requirements and installation • 1.5
General requirements • 1.5
Network installation • 1.6
System features • 1.8
What is access control? • 1.9
What is the ACDB program? • 1.9
Card types • 1.10
ACDB building blocks • 1.11
Schedules • 1.11
Holidays • 1.11
Access levels • 1.11
Cardholders • 1.13
Special access • 1.14
Setting up the system • 1.15
Step-by-step instructions
The table below shows the conventions used in this manual.
Notation Meaning
Ctrl + P Simultaneous key press: Press and
hold Ctrl, press and hold P, then
release both keys
Alt, P, N Sequence of key presses: Press and
release Alt, press and release P,
press and release N
Tip: Text of the tip. Tips, displayed in the left column, give
keyboard shortcut or alternative
method for the particular task
Note: Text of the note. Notes are important facts that can
save you time or prevent serious
mistakes
Available versions
ACDB versions
Model Description CRC KPDISP HASP Key Network
KPDISP-CF Keypad Display Configuration None Unlimited Not No
software version. Configures required network
keypad display devices only. support
No configuration of CRCs or
entry of cardholders.
ACDB8 Access Control Database 8 or less Unlimited Required No
software integrated with network
EST3 that supports 8 or fewer support
doors
ACDB8+ Access Control Database Unlimited Unlimited Required No
software integrated with network
EST3 that can support any support
number of doors
ACDB-CLNT ACDB client used with a Unlimited Unlimited Required Yes
networked ACDB database
server. Database is only
stored on the server.
ACDB-SVR ACDB database server and Unlimited Unlimited Required Yes
client combination. The
server portion supports other
clients on a network. The
client portion can be used like
any other client on the
network.
Network
Desktop computer
running ACDB-CLNT
RS-232
ACDB Server
Main Server running ACDB-SVR Modem
Example network diagram for the ACDB-CLNT and ACDB-SVR
Network installation
Begin a network installation with the server. After installing the
ACDB-SVR software, your IT staff should configure DCOM
settings on the server by running the DCOM Configuration tool
as follows.
1. Click Start > Run, then type dcomcnfg and click OK.
This opens the Distributed COM Configuration Properties
dialog box.
2. From the Applications list, select the DataServerComponent
object.
System features
The ACDB provides a user-friendly environment for entering
and tracking access control information and for integrating it into
an overall access control system. It makes managing your access
control system easier and more efficient.
The ACDB includes these features:
• Data import from several commonly used databases
• Filter-defined cardholder search capability
• Cardholder photo import/export
• Cardholder import from an external file
• Operator define options (PIN schedule, unlock time)
• Administrator definable operator privileges
• Access history event log
• Database, access event, and presence reports
• Predefined and user-defined reports
• Muster reports
• Task manager to automate routine functions
• Encrypted external communications
The ACDB lets you search, sort, edit, and print access control
data. The data includes information on cardholders, schedules,
holidays, and access levels. The ACDB also lets you run reports
to track access event history from all CRCs.
Card types
The ACDB lets you use several types of cards and card readers
to restrict access to a site. Cards and readers can be any of the
following:
• Proximity
• Wiegand pin
• Magnetic stripe
• Keypad
• Smart card
A cardholder can only gain entry to an area by presenting a valid
card at a card reader located at a specific entry point.
Using card and card readers lets the ACDB and your access
control system uniquely identify and monitor individuals as they
enter or leave controlled areas. Other methods of restricting
access, such as door locks and keys don’t provide a record of
access events.
Schedules
Schedules let you grant or deny access based on the time of day.
Any controlled door of your facility can be assigned a schedule.
Schedules include access times for working days, nonworking
days, and holidays.
Example: General office staff working from 8 a.m. to 5 p.m.
require access during those hours. Janitorial staff working from 5
p.m. to 11 p.m. require a different schedule than the office staff.
Holidays
Holidays are the days on which the holiday schedule (defined as
part of each schedule) takes effect. The date of a holiday can be
defined as a fixed date or as a specific week and day of a month.
Example: Good Friday is not a fixed date holiday but is set to
the first week and first Friday of the month of April. Christmas is
a fixed date holiday and is set to December 25.
If the holiday falls on a weekend, you can set an alternative day
off rule for the holiday. The alternative day off rule has three
options:
• Friday off if holiday falls on Saturday. Monday off if holiday
falls on Sunday.
• No day off if holiday falls on Saturday. Monday off if
holiday falls on Sunday.
• Friday off it holiday falls on Saturday. No day off if holiday
falls on Sunday.
Example: If Christmas falls on a Saturday or Sunday, companies
often allow their employees an alternative day off. Christmas
could be set to use the rule: Friday off if holiday falls on
Saturday and Monday off if holiday falls on Sunday.
Access levels
Not all employees require the same type of access. Therefore, the
ACDB lets you create different groups of schedules, privileges
and command lists. These predefined groups are called access
levels.
Privileges
In addition to access rights (as defined by schedules), you can
define additional privileges for an access level.
Command privileges determine which security commands the
cardholder can execute.
Example: Arming or disarming a partition.
Access privileges determine when access also disarms a
partition, or when access is permitted outside of scheduled times.
Example: A manager might have irregular entry privileges,
while a clerical worker would not.
For a CRC the following privileges apply:
• Disarm privilege
• Irregular entry privilege
KPDISPs have the following fire alarm privileges:
• Disable privilege
• Panel silence privilege
• Reset and alarm silence privilege
KPDISPs also have the following security privileges, which
apply only to the partition:
• Arm away privilege
• Arm stay privilege
• Bypass/Disable privilege
• Disarm privilege
Command lists
You can think of a command list as a predefined set of system
responses. Your system can include several command lists. Your
integrated system installer defines command lists.
When you add a command list to a CRC, the system performs
that set of responses when the CRC sees a given event (e.g.
access granted).
Example: A CRC controlling an outside door could have a
command list that activates a CCTV camera.
Cardholders
Each cardholder record you create has an access level. The
access level contains the CRC schedules, privileges, and
command lists that define the cardholder’s access. The access
level defines when and where this cardholder can gain access.
Cardholder records also include access card numbers, photos,
personal information, and activation and expiration dates.
Special access
You can also specify special access schedules and privileges that
override normal system operations.
The ACDB lets you define and apply three additional schedules
that are specific to individual doors. These door schedules
override the access levels of cardholders. The door schedules
are:
• Unlock schedule
• PIN schedule
• Suppression schedule
Unlock schedules define times when a door is unlocked to allow
free access.
Example: A front door of a retail business open during retail
hours.
PIN schedules define times when a cardholder must enter a PIN
number in additional to presenting a valid access card.
Example: Requiring a PIN at a back door during off-hours can
guard against the use of a stolen card.
Suppression schedules define times normal access granted events
are not logged to history.
Example: During normal office hours you may wish to suppress
access granted events at restroom doors.
11. Set up an access level for each employee group. Attach the
appropriate schedule, privileges, and commands to each
access level created. Refer to Chapter 10: Access levels.
Note: To improve the overall performance of the ACDB,
download to the access control system after creating your access
levels.
12. Set up all the cardholders that will access the building. Each
cardholder must be assigned at least one access level and a
card ID. The access level has a schedule attached to it. The
schedule may or may not have a schedule for holidays. Refer
to Chapter 11: Cardholders: Basic.
Note: To improve the overall performance of the ACDB,
download cardholders after each 1000 created.
13. Select and print any of the default reports provided, or create
custom reports for your specific needs. Refer to Chapter 13:
Reports.
Summary
This chapter defines the process of logging on for the first time
and importing the Resource Profile (RP) file for your company.
Not all of the ACDB’s features and functions become active
until an RP file is imported.
This chapter also provides general information about screen
layouts and navigation for the ACDB program. Included are
discussions on the menus, functions, and procedures of the
ACDB.
Content
Starting the program • 2.2
Logging on for the first time • 2.4
What is an RP file? • 2.4
Logging on as an installer • 2.4
Changing the installer password • 2.5
Importing an RP file • 2.6
Importing a sample RP file • 2.9
What you should and should not add to the sample
database • 2.9
Importing the real RP file into the sample RP file • 2.11
Removing the sample RP file hardware • 2.11
Logging on after RP file import • 2.13
Importing an RP file into an existing company • 2.14
Modifications to the existing SDU project • 2.14
Importing a new SDU project • 2.15
Deleting an SDU project • 2.17
Deleting a company • 2.18
Interface overview • 2.19
Title bar • 2.19
Menu bar • 2.20
Toolbar buttons • 2.23
Tabs • 2.25
Selection list or tree • 2.26
Left, middle, and right panes • 2.26
Status bar • 2.26
• Click Start > Programs > Access Control DataBase > Access
Control DataBase, or double-click the Access Control
DataBase icon on your desktop.
The ACDB displays a progress bar indicating that the program is
starting.
• Help
• About
Log In
The Log In option is the entry point for using the software. Users
are issued an Operator ID and a password that lets them gain
entry to the program and make modifications to their access
control system.
Exit
The Exit option lets you exit from the program.
Help
The Help option launches an online version of this manual. The
online version includes three navigation tabs:
• The Contents tab provides a table of contents view of the
help system
• The Index tab is an alphabetical list of terms. Use the index
to find topics associated with each term.
• The Search tab lets you search for keywords you enter. This
is generally the fastest method of locating answers to your
questions.
About
The About option brings up a box displaying the current version
of the ACDB software. This information is useful if you decide
to upgrade your software and need to know what version you are
currently running.
What is an RP file?
The RP file defines the access control system for the ACDB
program. It includes detailed information about each CRC and
KPDISP used in your access control system. It contains the
following:
• CRCs, KPDISPs, partitions, and buildings in the system
• Routing required to access each device for downloads
• KPDISP fire alarm command privileges
• Primary company for each CRC
• Primary partition for each KPDISP
• Number of allocated cardholders for each CRC and KPDISP
• Number of allocated access levels, schedules, and holidays
for CRCs
• Command lists used for CRCs
• All MODCOM (integrated system dialer/modem card)
information
Logging on as an installer
If you do not have an operator ID and a password, you must
import an RP file to obtain them. Begin by logging on to the
software as the installer.
Note: The initial installer password is 3333. We suggest that you
change the installer password after your initial log on. Make sure
to record and save the revised password in a safe place.
Importing an RP file
After logging on as an installer, your next task is to import an RP
file. The integrated system installer should have given you the
RP file for your company. The RP file contains the database for
a single site. This includes information about the company,
buildings, partitions, CRCs, and KPDISPs.
Note: To improve the performance of the ACDB, we
recommend that you download to the hardware of your access
control system immediately after importing your RP file. You
must log on as the administrator to download.
Each RP file represents one site of one company. A large
company may have multiple sites.
Example: A company has two different locations of operation.
One is in New York and the other is in Tennessee. Each site
would have a separate RP file.
You can only import one RP file at a time. Importing the first RP
file defines the company. If you have two sites, you import the
second RP file into the existing company.
Note: To import any additional RP files into an existing
company, you must log off as the installer and log on as the
administrator (ADMIN1).
At the end of the import, the ACDB assigns an administrator ID
and password, using the default password ADMIN.
Each company is assigned an administrator ID after the RP file is
imported. You can use this ID and password to begin to add
information to your ACDB system.
The default operator ID is ADMIN1, with password ADMIN.
ADMIN1 is always used for the first company imported by the
integrated system installer. If a second company is imported, the
operator ID is ADMIN2, again using password ADMIN.
If your integrated system installer has not completed or given
you your RP file, proceed to Importing a sample RP file in this
chapter. Importing a sample RP file allows you to begin adding
information to your database while your installer completes your
RP file.
Before using the ACDB you must import an RP file, using the
Resource Profile Manager (RPM) file import dialog box
To import an RP file:
Tip: Press Alt + F, I, R to 1. From the file menu, click Import > RPM Configuration
launch the Import Information.
Resource Profile Manager
(RPM) File dialog box. 2. Locate the RP ZIP file you want to import, select it, and
click Open.
If your integrated system installer gave you a floppy disk
containing your RP file, insert the disk and select the RP file
from your floppy drive.
3. Click OK to confirm that the ACDB has extracted your
database.
4. Type a company name if your company name does not
match the company name given and click Done.
5. Type a Site name and click Done.
Both company and site are new, since this is the first RP file
import. An example of a site name is Chicago Campus or
North Campus.
6. Click the OK button.
Note: The system displays the administrator operator ID and
password. Write these down in a safe place.
7. Click OK.
Note: To improve the performance of the ACDB and assure
hardware connection, we recommend that you download to the
hardware of your access control system immediately after
importing your RP file. Log on as the administrator to download.
See Chapter 7: Outbound ports and routes for information on
configuring the ACDB for downloading.
Tip: Press Alt + F, I, R to 1. From the file menu, click Import > RPM Configuration
launch the Import Information.
Resource Profile Manager
(RPM) File dialog box. 2. Locate the Sample_Company ZIP file in the ACDB
directory, select it, and click Open.
3. Click OK to confirm that the database has been extracted.
4. Type your company name over the Sample_Company name
given and click Done.
5. Type your site name and click Done.
Both company and site are new, since this is the first RP file
import. An example of a site name is Chicago Campus or
North Campus.
6. Click OK.
Note: The system displays the administrator operator ID and
password. Write these down in a safe place.
7. Click OK.
Note: Once you have imported the Sample RP file, do not
download to the hardware of your access control system.
Tip: Press Alt + F, I, R to 2. From the file menu, click Import > RPM Configuration
launch the Import Information.
Resource Profile Manager 3. Locate and select the updated RP ZIP file you want to import
(RPM) File dialog box. and click Open.
If your integrated system installer gave you a floppy disk
containing your RP file, insert the disk and select the RP file
from your floppy drive.
4. Click OK to confirm that the database has been extracted.
5. Click Yes to confirm that you are importing a different
project into your database.
6. Select the existing company name.
7. Type the new site or select the existing site and click OK.
Type new site for a project from a separate location.
Select the existing site if the project is from the same
building.
8. If you selected an existing site, select an existing building
where the project is located.
A project being imported into an existing building can
contain no more than one building.
9. In the Options tab, click an Update Option, then click Done.
• Always overwrite with data from import
• Ask for each change
• Never overwrite
Note: The overwrite options do not apply to the hardware of
your access control system. All CRCs and KPDISPs are
overwritten each time you import a new RP file. The overwrite
options only apply to company address and company contact
information, and building address and building contact
information.
10. Click OK.
Deleting a company
If needed, you can delete a company from the ACDB database.
A company represents all RP imports including all sites,
buildings, partitions, CRCs, KPDISPs, and MODCOMs.
Deleting the company removes all RP files and data from the
database (cardholders, access levels, schedules, and holidays).
After the company has been deleted, you can import a RP file
that contains the correct information for your company.
To delete a company you must log on to the ACDB as the
Installer. Refer to Logging on as an installer in this chapter.
To delete a company:
Interface overview
Once you log on, the first screen you see is the main window of
the program. This window contains the navigation tools that you
need for performing tasks within the program.
The program defaults to the CardHolder tab, but you can
navigate to any part of the program by selecting the appropriate
tab.
The main window has these features:
• Title bar
• Menu bar
• Toolbar with buttons
• Page tabs
• Selection list or tree
• Left, middle, and right panes
• Status bar
Title bar
Menu bar
Toolbar
Page tabs
Selection
list or tree
Status bar
ACDB window
Title bar
The title bar shows if the current record you are working on has
been modified or is currently being modified. This makes it
easier to track which records have been modified.
Menu bar
Below the title bar is the menu bar. The menus available are:
Tip: When a menu • File
command has a keyboard • Edit
shortcut, the shortcut is • View
displayed on the menu. • Action
This helps you learn faster, • Tools
more efficient ways to use • Reports
the program.
• Help
Toolbar buttons
Below the menu bar is the toolbar. The toolbar buttons execute
many of the commands found in the menus.
When you point to a button, a tool tip is displayed indicating the
function of the button. Not all toolbar buttons are active at all
times. When a button is not active, it is grayed out.
Toolbar buttons
Tabs
Below the toolbar are the tabs. The tabs separate the ACDB
program into six main sections.
ACDB tabs
ACDB tabs
Tab Description
Displays the Cardholder tab
CardHolders tab
The CardHolders tab stores all cardholder information. You can
attach a photo to the cardholder information tab, determine what
type of access card (badge) should be issued for each cardholder,
and assign two different access levels to the cardholder.
Schedules tab
The Schedule tab is used to create and maintain schedules.
Schedules are used for various functions, including restricting
access by day and time.
Holidays tab
The Holidays tab is used to record your company’s holidays.
You can program holidays to occur on fixed dates or days of the
week. Through schedules, a holiday schedule alters the access
times for a holiday.
Reports tab
The Reports tab is used to generate reports. Reports can be
generated with information in the ACDB database concerning
cardholders and data gathered from the CRC (Card Read
Controller). You can choose reports from templates that have
been included or you can customize your own reports to include
information that you specify.
Administration tab
The Administration tab includes these subordinate tabs: System,
Operators, Command List, Tasks, Outbound Ports, and Routes.
Only operators with administration privileges have access to the
Administration tab. Options on the administration tabs let your
system administrator tailor the features and functions of the
ACDB.
Status bar
The status bar is located at the very bottom of the ACDB
window. The ACDB displays the following information in the
status bar:
• The operator that is currently logged on
Summary
The ACDB makes use of several basic functions. Learning these
basic functions will help you use the ACDB more effectively and
save you time in your day-to-day work. This chapter introduces
you to the basics of the ACDB.
Content
Entering a startup screen caption • 3.2
Setting system options and preferences • 3.3
Operator tab • 3.3
Preferences tab • 3.4
Company Information tab • 3.5
UD Cardholder Tab Labels tab and UDF Labels tab • 3.6
Card Code Formats tab • 3.6
Facility Codes tab • 3.6
Viewing the selection table • 3.7
Navigating with the arrow buttons • 3.7
Selecting with the letter tabs • 3.7
Saving your changes • 3.9
Multiple selection • 3.10
Selecting multiple records with the four action
commands • 3.10
Additional methods to select multiple records • 3.11
Downloading information • 3.12
When to download • 3.12
Downloading failure • 3.12
Backing up your system • 3.14
Moving your database to a new PC • 3.15
Exiting from the ACDB • 3.16
Operator tab
The Operator tab lets you view information for the operator
currently logged on. You can also change the operator’s
password using this tab.
The Operator tab also shows the date and time for the current
operator’s last session. See Chapter 5: Operators for detailed
information regarding operators.
Preferences tab
Preferences are set for the current operator of the ACDB.
Operators can set their own preferences. The Preference tab is
divided into three subtabs:
• General
• Confirmations
• Diagnostics
General tab
The General tab has the following fields:
• Time Display: Determines whether time is displayed in 12
hour or 24-hour format.
• Date Display: Determines whether dates are displayed in
short or long date format.
Example of long date: Thursday, January 11th, 2001
Example of short date: 01/11/01
• Automatic Logout: Sets the program to automatically log
you off after a specified time.
• Access Colors: Defines the colors of the time bars used for
schedules. See Chapter 8: Schedules for detailed
information.
In addition there is a group of fields called Miscellaneous
options. This includes:
• Weeks Start On Sunday: Determines the starting day
(Sunday or Monday) for calendars.
• Restore to Last Context: Saves your location in the ACDB
and starts each session where you ended the previous
session. Normally, the software opens at the Cardholder tab.
• Restore Last Operator ID at Login: Retains your login ID
when logging on to the software.
Confirmations tab
For some actions, the system displays a confirmation dialog box.
You can choose whether or not the system displays confirmation
dialogs for the following actions:
• Deleting photos
• Adding schedules
• Deleting schedules
• Setting privileges
• Resetting privileges
• Adding command lists
• Deleting command lists
Diagnostic tab
The Preferences tab provides diagnostic information for client
activity within the ACDB. This section is for factory use only.
General tab
Company information is the information specific to the owner
and controller of the entire site. This information includes the
company address and contact information.
Typically, the Resource Profile (RP) file provides company
information. The company information is imported into the
ACDB along with your access control system information, but
you can revise the imported information as required. See Chapter
4: System and hardware configuration for further information.
Note: If you make changes to the company information, contact
your integrated system installer and inform him of the
corrections. For installer contact information, click the Hardware
View tab and the SDU icon in your company tree. The installer
will need the information to correct his records for future contact
with you.
Default
For each cardholder you assign a card format and possibly a
facility code. Some cards formats do not require a facility code.
The majority of cardholders will be using the same card format
and facility code. Once you know the card format and facility
code for your access control system, you can set them as the
defaults.
Each new cardholder added will be assigned the default card
format and facility code. This avoids having to select the same
card format and facility code for every new cardholder.
For further information on setting the default card format and
facility code, refer to Chapter 12: Cardholders: Advanced.
You can also configure an auxiliary card reader input. A card
reader input device gives you the ability to scan a card number
into the cardholder file, instead of manually entering it. The card
is simply scanned with a standard card reader and the card
number is inserted into the cardholder file. For further
information on configuring an auxiliary card reader input, refer
to Chapter 12: Cardholders: Advanced.
The arrow buttons at the top and letter tabs at the bottom are two
ways to navigate through a selection table
You can display more letter tabs by clicking the left and right
arrows adjacent to the letter tabs. The tab on the far left displays
all records in alphabetical order.
Multiple selection
You can select two or more items at once and make a single
change to all selected items. Most tabs with selection tables
allow this functionality.
When you have selected multiple records, some fields can not be
changed. The ACDB automatically hides fields that can not be
changed with multiple selections.
To select Do this
A single Hold down Ctrl and select the record
record
Nonadjacent Hold down Ctrl and select the individual records
records
A large range Hold down Ctrl and select the first record of the
of records range, and then hold down Shift and click the
last record in the range
Downloading information
Once information has been entered into the ACDB, the data must
be downloaded to your access control system. Only after the
information has been downloaded will cardholders be able to
gain access.
Any time changes are made to the ACDB that affect your access
control system, the revised data must be downloaded to your
access control system. No changes will be active in the CRCs or
KPDISPs until they are downloaded.
For you to be able to download to the CRCs and KPDISPs, the
Outbound port and Route of the ACDB must be configured. For
further information, see Chapter 7: Outbound ports and routes.
Note: You can download changes to your system at any time or
from any tab within the software. Make sure all information has
been saved before downloading.
• From the File menu, click Send Changes, or click the Send
Changes button on the toolbar.
Note: Verify that the date and time are current at the system
panel. Incorrect date and time causes incorrect operation of the
access control system.
When to download
To improve the performance of the ACDB, it is recommended
that downloads are performed at specific times while setting up
your database. The following gives the times when you should
download.
• After importing your companies RP file
• After creating and activating no more than 1000 cardholders
Downloading failure
When a yellow X is displayed over a CRC or KPDISP this
indicates that the system failed to download to this CRC or
KPDISP. This can be seen from the tree view in the Access
Levels tab and the Administration > System tab.
If you see a yellow X over a CRC or a KPDISP, confirm that the
device has not been removed from your system and that it is
functioning properly. Also, confirm that you have configured
your outbound ports and routes properly.
The yellow X over CRC3 shows that the ACDB could not
download to it because of a communication error
Summary
This chapter defines the process of configuring your access
control system including Keypad Displays (KPDISPs) and Card
Reader Controllers (CRCs).
This chapter also provides information about command lists.
Note: As an end user, you may not be required or allowed to edit
the configuration of your access control system. This section is
provided so you can have a complete understanding of all
program options, and is not meant to imply that all operators
must perform these configuration procedures. If you have any
questions regarding system setup, check with your ACDB
administrator for clarification.
Content
Configuring your system • 4.2
Configuring your system in company view • 4.3
Reviewing and editing company information • 4.3
Viewing the project site information • 4.4
Reviewing and editing building information • 4.5
Viewing the partition information • 4.6
Configuring your system in hardware view • 4.7
Viewing SDU, CPU, and 3-SAC • 4.8
MODCOM • 4.8
Configuring the doors • 4.9
Viewing door summary information • 4.9
Communication routes • 4.10
Other companies with access • 4.10
Configuring and viewing door options • 4.11
Configuring door timers • 4.13
Viewing miscellaneous door information • 4.16
Viewing Keypad Displays (KPDISPs) • 4.18
Communication routes • 4.19
Other companies with access • 4.19
Command lists • 4.20
Viewing a command lists • 4.20
Company information
MODCOM
The MODCOM is only visible in the hardware view. The
MODCOM has modem and dialer capabilities. It is used for
downloading information from remote sites. MODCOMs are
configured, programmed, and installed by your system installer.
You can not change any of their parameters except their
communication route.
Each MODCOM has one communication route. The
communication route defines how the ACDB downloads
information to the MODCOM. All MODCOMs are initially set
to a default route. For information on how to change the
communication route for a MODCOM refer to Chapter 7:
Outbound ports and routes.
When you select a door from the company view tree or the
hardware view tree the door’s configuration tabs are displayed
Communication routes
Each CRC and KPDISP has a communication route. The
communication route defines how the ACDB downloads
information to these devices. All CRCs and KPDISPs are
initially set to a default route. For information on how to change
the communication route for CRCs and KPDISPs refer to
Chapter 7: Outbound ports and routes.
This dialog box lists the other companies with access to the
door. It also displays the primary company contact information.
The primary company controls the configuration of the door.
The Timers tab is divided into unlock, open, exit, and control
timers groups
Bypass time
The bypass time is the number of seconds (0 to 255) that the
CRC suppresses signaling an event to the integrated system. The
default is 0 seconds, which means that there is no suppression.
The bypass timer is activated after a valid cardholder badges in
or upon activation of various exit devices with bypass features.
KPDISP privileges
The privileges for a fire alarm KPDISP differ from the privileges
for a security KPDISP. The same KPDISP can be displayed
under a building for fire alarm applications and under a partition
for security applications.
The company view shows which fire alarm privileges are
available for a given KPDISP. These privileges are assigned
when you create access levels. See Chapter 10: Access levels for
more information.
Communication routes
Each CRC and KPDISP has a communication route. The
communication route defines how the ACDB downloads
information to these devices. All CRCs and KPDISPs are
initially set to a default route. For information on how to change
the communication route for CRCs and KPDISPs refer to
Chapter 7: Outbound ports and routes.
Command lists
Your integrated system installer defines the command lists
available for your system. These are imported with the RP file.
Command lists are typically are used to:
• Transmit access events to the Central Monitoring System
(CMS)
• Activate remote gates
• Activate CCTV cameras
• Activate relays that control other devices, such as elevator
controls
The Command Lists tab shows all the commands that have been
imported for your company.
A command list can be attached to a CRC in an access level. The
system activates the command list when the CRC grants access.
The command list window shows all the command lists that have
been imported into the ACDB
Summary
Operators are users of the ACDB. The system administrator can
define as many operators as required. You define each operator
by specifying the command privileges that the operator has. This
chapter shows you how to define and create operators.
Content
What is an operator? • 5.2
Creating a new operator record • 5.3
Operator information • 5.3
Last Login and Logout • 5.4
Adding a photo to an operator record • 5.5
Importing and sizing an operator photo • 5.5
Exporting an operator photo • 5.6
Deleting an operator photo • 5.7
Setting operator privileges • 5.8
Default operator privileges • 5.8
Privilege tabs • 5.8
Activating and deactivating an operator • 5.11
Activating an operator • 5.11
Deactivating an operator • 5.11
Logging on as a new operator • 5.13
Changing operators while the system is running • 5.13
Changing your operator password • 5.14
Changing your password from the Operators tab • 5.14
Changing your password from the Tools menu • 5.15
Resetting an operator's password • 5.15
Editing and deleting an operator record • 5.16
Editing an operator record • 5.16
Deleting an operator record • 5.16
Changing operator information • 5.17
What is an operator?
An operator is someone who enters data into the Access Control
Database (ACDB). An operator ID and password are required in
order for an operator to log on to the ACDB.
We suggest that you designate a single administrator for each
company in your ACDB. The administrator is an operator with
full privileges, including the ability to create and revise operator
records.
The ACDB assigns each company an administrator operator ID
and password when importing the RP file. When first logging on
to the ACDB you must use this ID and password.
The default administrator operator ID is ADMIN1, with
password ADMIN. ADMIN1 is always used for the first
company imported by the integrated system installer. If a second
company is imported, the operator ID is ADMIN2, again using
password ADMIN.
When you log on, the ACDB prompts you to change your
password for future use. To change the ADMIN password, see
Changing an operator password, later in this chapter.
Operator information
You use the Information tab to enter personal information about
the operator, such as name and address.
Operator ID
Operator ID is the first field entered when logging in. The ID can
consist of up to 20 characters. You can use upper case letters or
numbers for Operator IDs. The Operator ID and Password are
required when logging on.
Name
The first information required is the operator’s full name and an
optional title, e.g., Mr., Mrs., Ms, or Miss. Operator names can
be up to 25 characters long.
Passwords
Each operator has an individual password that is required when
logging into the system. The password is specific to the
individual operator. Operators are responsible for remembering
their own passwords. The Operator ID and Password are
required when logging in.
A new operator has the initial default password of PASSWORD.
The operator should change this default password after logging
in.
Crop: Lets you select a certain portion of the photo. Using your
mouse, drag a selection box on the photo. When you release the
mouse button, the selected portion of the photo is displayed in
the right pane.
You can move the selection box to any location on the photo. To
do so, simply drag the box. Notice the mouse changes its
appearance once over the selected area. The display area changes
as you move the selected box.
Scale to fit: Lets you enlarge the selected area of the photo to fit
the display pane. You select a portion of the photo by dragging a
selection box.
Select Entire Image: Selects the entire photo image. You must
first click Scale to fit for the Select Entire Image button to
become available. Your entire photo is selected and displayed in
the right pane.
After sizing, the photo is displayed in the right display pane
exactly as it will appear on the Operators tab.
1. In the left pane, select the operator for whom you want to
import a photo.
Tip: Press Alt + I to launch 2. Click Import.
the Edit Photo dialog box.
3. Load or copy the photo.
4. Size your photo.
5. Under Storage, move the Image Quality slider to the desired
quality.
The higher the quality, the larger the image size. The image
file size is displayed under the slider bar.
6. Click OK to import the file.
7. Save the operator record.
Tip: Press Alt + E, to 1. In the left pane, select the operator you wish to export.
export a photo. 2. Click the Export button in the Photo group.
3. Browse to the desired location to export the photo.
4. Type a name for the file in the Name field. The default is the
operator's name.
Tip: Press Alt + C to clear 1. On the Operator tab, click the Clear button in Photo group.
the photo. 2. Click Yes to delete the photo.
3. Save the Operator record.
Privilege tabs
The privilege check boxes are divided into three tabs.
Regular: The regular tab contains privileges for cardholders,
access levels, schedules, holidays, and reports.
Administration: The administration tab contains privileges for
systems, operators, command lists, CMS account user IDs, tasks,
outbound ports, and routes.
Special: The special tab contains privileges for company
information, cardholder user defined tab captions, cardholder
user defined field labels, sending changes to the system, and
importing external data.
Example 1: If you need to set privileges for an operator allowing
him read-only rights to the system, you deny all privileges, then
grant the ability to browse system information. You can do this
manually, or simply by clicking the Browse Only default button.
Example 2: If you need to set privileges for an operator to enter
cardholders only, you deny them all privileges except the ability
to create, browse, and edit information on the cardholder pages.
You would do this manually.
If there are only a few items you do not want to grant an operator
access privileges to, it may be easier to first select Grant All,
then go back and remove the privileges you do not want enabled.
The same procedure can be used for Browse Only if you want an
operator to be able to see most, but not all of the options. You
can go back and delete the privileges for certain items you do not
want them to be able to browse.
Since each site has different parameters for their operators, it is
up to the administrator of the ACDB to set and assign the
appropriate privileges for the operators in your system.
To activate an operator:
Deactivating an operator
The ability to deactivate an active operator lets you temporarily
deny the operator access to the ACDB.
Example: An operator has a temporary job function in the
ACDB and can be activated and deactivated as needed. This
prevents you from having to reenter the operator each time you
need him to work in the ACDB.
To deactivate an operator:
To change operators:
Tip: Press Alt + A, L to log 1. From the Action menu, click Login.
off.
2. Click OK to log off.
3. Type in the new operator ID and password and click OK.
Summary
Tasks let you automate important ACDB operations. For
example, tasks can update hardware, purge old data from the
database, retrieve access history for reports, or automate the
running of reports. This chapter provides information on how to
create, define, edit, activate, and schedule tasks.
Content
What is a task? • 6.2
Default tasks • 6.4
Creating a task • 6.5
AC history request • 6.5
DB maintenance • 6.5
Hardware initialization • 6.5
Presence request • 6.5
System update • 6.5
Cardholder re-initialization • 6.6
Hardware configuration initialization • 6.6
Run transaction queue • 6.6
Starting a task • 6.7
Starting a task manually • 6.7
Scheduling a task • 6.7
Configuring the time range of an AC history task • 6.8
Setting properties for a DB maintenance task • 6.8
Assigning a task to CRCs and KPDISPs • 6.10
Associating a task with a report • 6.11
Activating and deactivating a task schedule • 6.12
Activating a task schedule • 6.12
Deactivating a task schedule • 6.12
Viewing the status of a task • 6.13
Editing and deleting a task • 6.15
Editing a task • 6.15
Deleting a task • 6.15
What is a task?
Tasks let you automate important ACDB functions, such as:
• System updates
• Access control event gathering
• Database maintenance
• Automatic data gathering for reports
• Hardware initialization
System updates
Whenever you make changes to your ACDB, those changes must
be sent to the hardware of your access control system. System
update tasks send the new information from the database to the
doors and keypads of your access control system.
Database maintenance
A task can be used to purge old records from the ACDB. You
can schedule a database maintenance task to routinely remove
old records. You can also define the age of the records to be
removed.
Hardware initialization
A task can initialize the hardware of your access control system.
The task loads all access control information, including
cardholders and hardware configuration, to the designated
hardware. This task is used for new hardware that has been
added to your system. It also can be used for damaged hardware
that may have lost its access control information.
The Tasks tab lets you create, edit, schedule, and run tasks
Default tasks
Several default tasks are included in the ACDB. Default tasks
serve as templates for most commonly used tasks.
You can modify the default tasks to meet your specific needs;
however, you cannot modify the Update task in any way. The
Update task is the task that runs when you click Send Changes
from the File menu or click the Send Changes button on the
toolbar.
All tasks, except Update, can be started manually or given a
starting schedule (see Starting a task in this chapter). The default
tasks are:
Creating a task
New tasks can be created and added to the list of default tasks. A
task can be one of these types:
• Access Control (AC) history request
• Database (DB) maintenance
• Hardware initialization
• Presence request
• System updates
• Cardholder re-initialization
• Hardware configuration initialization
• Run transaction queue
AC history request
An AC history request task pulls access event information from
the CRCs and stores it in the database. The information stored in
the database can then be used to run access event history reports.
The task can be limited to specific doors and to events within a
specific time range. You can schedule the task to activate daily,
weekly, monthly, or on demand.
DB maintenance
DB maintenance tasks can be used to purge old data from the
database. A DB maintenance task is one of the default tasks
provided. The age of the data to be purged is set by you. You can
also schedule the task to run daily, weekly, or monthly.
Hardware initialization
Hardware initialization tasks initialize the hardware in your
system. If a piece of hardware (CRC or KPDISP) has lost its
database or had its data degraded, database information can be
restored using this task type. Typically, your service department
would use this task to restore data to hardware. Hardware
initialization tasks are also used when new hardware is added to
your access control system.
Presence request
Presence request tasks gather information about who is present
in a specified area of your site. This could be your entire site or a
single partition. The information gathered is stored in the
database where it is used to run presence reports.
System update
The system update task is used to send changes from your
database to the hardware (CRCs and KPDISPs) in your access
control system. This task only sends changes that have been
Cardholder re-initialization
The Cardholder Re-init task reinitializes the cardholders of your
access control system. The task reloads all cardholders, not
including hardware configuration, to all hardware (CRCs and
KPDISPs).
To create a task:
Starting a task
All tasks, except for Update, can be started manually or by a
schedule. A scheduled task can be run on a daily, weekly, or
monthly basis. If you do not want to schedule the start of your
task, it can be set to start on demand.
1. In the left pane, select the task you want to start manually.
2. Click the Start Now button.
Scheduling a task
You can use the Schedule tab to schedule a task to run on a
daily, weekly, monthly, or demand basis. The frequency you
select determines the scheduling options for the task.
Note: If the task is active before scheduling it, the schedule time
will not take effect until the task is deactivated and reactivated.
To schedule a task:
1. In the left pane, select the AC history task for which you
want to set the time range.
2. Click the Schedule tab.
3. In the Time Range of Access Events group, enter the time
range of access events you want to retrieve.
4. Save the task record.
1. In the left pane, select the task you want to associate with a
report.
2. In the Associated Report list, select the report you want to
associate with the task.
3. Save the task record.
In process
The In Process tab shows the status of the task as it is running.
The In Process tab provides a table with the following columns:
• ID
• Started
• Type
• Priority
• Current Status
• Name
• Task ID
• tip.Current Status
This information lets you accurately track the process of the task
as it is running.
Note: The Transaction Not Sent tab does not show task failures
due to communication errors.
1. In the left pane, select the task for which you want to view
the status.
2. Click the Status tab.
To edit a task:
Deleting a task
You can delete all tasks except for the Update task. You may
find it easier deactivate a task rather than deleting it. A
deactivated task can be reactivated later. A deleted task is gone
forever.
Note: Before deleting a task, you must deactivate its schedule.
To delete a task:
Summary
This chapter shows you how to create and configure outbound
ports and routes. Outbound ports and routes define how the
ACDB downloads information to the hardware of your access
control system.
Content
Outbound ports and routes overview • 7.2
Outbound ports • 7.2
Routes • 7.3
Creating an outbound port • 7.6
Creating a route • 7.7
Configuring the default route • 7.8
Configuring your system for an alternative route • 7.9
Modifying the default route for MODCOMs, CRCs, and
KPDISPs • 7.9
Assigning a new route to MODCOMs, CRCs, and
KPDISPs • 7.10
Editing and deleting an outbound port • 7.12
Editing an outbound port • 7.12
Deleting an outbound port • 7.12
Editing and deleting a route • 7.13
Editing a route • 7.13
Deleting a route • 7.13
Outbound ports
An outbound port specifies the computer and port you are
transmitting from.
During installation, the ACDB detects your PC ports
automatically. These are displayed on the Outbound Port tab of
the Administration tab.
Typically, a PC has communication ports at COM1 and COM2.
You are not bound to the automatically detected outbound ports.
You can edit, delete, and add outbound ports as needed.
Routes
Routes define how the ACDB connects to the hardware of your
access control system. There are two different types of routes:
• Modem connection
• Direct connection (RS-232)
Modem
A modem route uses a telephone line to communicate. The
connection leaves the modem from the PC and connects to the
modem at the control panel.
For a modem route, you configure the Outbound Properties tab
and ModCom tab for that route. The receiving modems are
imported into the ACDB with your RP file.
RS-232
An RS-232 route connects directly to the control panel. The
RS-232 line runs from your PC serial port and plugs directly into
the control panel.
Communication parameters
Field Default Description
Baud rate None The speed at which at which data can
be transmitted
Maximum 8 The number of times the ACDB will try
retries to communicate before timing out
Maximum 800 The maximum length of the message
message sent at any one time
length
Timeout 20 The amount of time before the ACDB
will retry to connect
Tracing None Tracing tells the ACDB to generate trace
files of the communications stream.
Technical support uses the trace files to
determine communication problems.
Default routes
The ACDB automatically creates two default routes for you. (If
your system does not contain a MODCOM, the ACDB will not
create a Modcom default route.) The default routes are:
• 3-CPU Default
• Modcom Default
If your control panel has no MODCOM, the ACDB uses the
3-CPU Default route to communicate to the hardware of your
access control system. The ACDB assigns all CRCs and
KPDISPs to this default route.
If your control panel has a MODCOM, the ACDB uses the
Modcom Default route to communicate.
When you click Send Changes from the Action menu or click the
Send Changes button on the toolbar, the system uses the
appropriate default route to communicate to your access control
system. The system will not use the default route if you create an
alternative route and assign it to the CRCs and KPDISPs. See
Configuring your system for an alternative route in this chapter.
Although the ACDB creates a default route for you, the default
route still requires configuration. See Configuring default routes
in this chapter.
Routes tab
Creating a route
After you have created your outbound port, you can either assign
the outbound port to the default route or create a new route.
Each CRC and KPDISP automatically uses the default route. For
a CRC or KPDISP to use a different route, you must manually
assign that route to the device. See Configuring your system for
an alternative route in this chapter.
To create a route:
To edit a route:
Deleting a route
You can delete a route at any time. You might want to delete a
Tip: Use the multiple select route if your access system is no longer using the route to
toolbar buttons or the
download information.
multiple select action menu
items, to select multiple
routes for deleting. You can To delete a route:
delete all selected records
at once.
1. Click the Administration tab.
2. Click the Route tab.
3. In the left pane, select the route you want to delete.
Tip: Press Alt + F, D to
delete an outbound port. 4. From the File menu click Delete or click the Delete button
on the toolbar.
5. Click Yes to delete.
Summary
Schedules establish the days and times when cardholders can
gain access to your site. This chapter provides the information
required for creating, defining, editing, and deleting schedules.
The chapter also defines schedules for holidays and door options.
Content
What is a schedule? • 8.2
Monday through Sunday schedules • 8.2
Holiday schedule • 8.3
Door option schedules • 8.3
Creating a schedule • 8.4
Copying from one timeline to another • 8.5
Resetting a timeline • 8.5
Editing and deleting a schedule • 8.7
Editing a schedule timeline • 8.7
Deleting a schedule • 8.7
Defining the timeline colors • 8.8
Adding a custom color to your pallet • 8.8
What is a schedule?
A schedule is a group of eight timelines, one for each day of the
week and one for holidays. Each timeline is divided into 15-
minute increments. You select blocks of time on these timelines
to define when access is granted.
Schedules define the days and times when access is granted,
when doors are unlocked, when PIN numbers are required, and
when normal access events are suppressed.
Schedules are an integral part of controlling how cardholders
access your site. You assign schedules to the individual doors of
an access level. You then assign the access level to individual
cardholders. You also use schedules to define the days and times
when door options are in effect.
Holiday schedule
A schedule contains a holiday timeline in addition to timelines
for Monday through Sunday. The holiday timeline defines the
time when the ACDB grants or denies access for any of the
holidays you define. To learn how to define holidays see Chapter
9: Holidays.
Unlock schedule
The unlock schedule defines the days and times when the CRC
automatically unlocks the door.
PIN schedule
For added security, a card reader can be equipped with a PIN
pad. The PIN schedule defines when a PIN number is required,
in addition to an access card, to gain entry.
Suppression schedule
The suppression schedule defines when the CRC does not log
normal events into history. The CRC always logs access denied,
disarm, and irregular access events. This feature is provided to
reduce the large number of normal access events being put into
history during normal business hours.
Creating a schedule
To facilitate the creation of schedules, you may want to start
with a list of the allowable access times you want to set up. This
will make the process much easier and faster.
Each interval on the timeline represents 15-minute increments.
The exact time for each block is shown in a pop-up display as
you roll your mouse over the timeline. The time is also displayed
in the bottom status bar.
When you drag the mouse along the timeline, the schedule
blocks you select change from red to green. This indicates that
the selected time period is enabled: Red bars indicate disabled
times. You can define as many blocks on a timeline as needed.
To create a schedule:
1. Right-click on the timeline for the day you wish to copy the
schedule to.
2. Click Copy From.
3. Select the day of the week or holiday that contains the
schedule you wish to copy.
4. Save your schedule record.
Resetting a timeline
You can reset the timeline for a specific day or for the entire
schedule. When you reset a timeline for a day, the timeline is set
to deny access for the entire day. You can also reset an entire
schedule, which changes all timelines to deny all access.
To reset a timeline:
Deleting a schedule
If a schedule is no longer being used in your access control
system, it can be deleted. Deleting a schedule completely
removes it from the ACDB.
Note: Before deleting a schedule, make sure the schedule is not
assigned to an access level. The ACDB will not allow you to
delete a schedule that is assigned to any door of any access level.
To delete a schedule:
Summary
This chapter provides general information explaining what
holidays are and how you create and modify them.
Content
What is a holiday? • 9.2
Creating a holiday • 9.3
Setting alternate days off for a holiday • 9.3
Projected day calendar • 9.3
Sorting your holidays • 9.6
Activating and deactivating a holiday • 9.7
Activating a holiday • 9.7
Deactivating a holiday • 9.7
Editing and deleting a holiday • 9.9
Editing a holiday • 9.9
Deleting a holiday • 9.9
What is a holiday?
Holidays are exceptions to the normal seven-day workweek
schedules. A holiday automatically changes a timeline schedule
for the given day, to the holiday timeline. The holiday timeline
in a schedule, typically has different access granted and access
denied times. Timelines for holidays are defined by your
company or organizational requirements.
Note: Holiday timelines are defined on the bottom of the
Schedules tab (see Chapter 8: Schedules). Each schedule
contains one holiday timeline that applies to all holiday dates.
Active holidays will occur yearly on their specified date. Inactive
Holidays will not occur until you make them active.
Here are the default holidays:
• New Years Day
• Memorial Day
• Independence Day
• Labor Day
• Thanksgiving
• Christmas
• New Years Eve
You can modify the default holidays to your needs or create new
holidays.
Creating a holiday
To facilitate the creation of holidays, you will want to have your
company’s holidays determined before getting started. Holidays
can occur on a fixed date, or a numbered week of the month and
a numbered day of the week (see Week starts on Monday or
Sunday in this chapter for day number).
The Alternate Day Off Rule group lets you choose one option for
each fixed date holiday
The Holiday tab lets you use the default holidays given to by the
ACDB or create your own
To create a holiday:
Tip: Press Alt + F, N to 2. From the File menu, click New or click the New Button on
create a new holiday. the toolbar.
3. Type a name for the holiday.
4. Select a month.
5. Select the week.
• Holiday is a Fixed Date
• 1st Week
• 2nd Week
• 3rd Week
• 4th Week
• Last Week
Example: If you enter a holiday such as President’s Day,
which occurs the third Monday in February, you would
select third week.
6. Type or scroll to the day of the week or day of the month the
holiday will occur.
• If it is a fixed date holiday, type or scroll to the day of
the month the holiday is on.
• If it is a specific day of the week, type or scroll to the
number of the day of the week that the holiday falls on.
See Week starts on Monday or Sunday in this chapter.
Example: For President’s Day, you would select 1 for
Monday, which is the first day of the week (for week that
begins on Monday).
7. If the holiday is a fixed date, click the appropriate Alternate
Day Off Rule for the holiday.
Example: Christmas Day is a fixed date holiday on
December 25. If your organization allows observance of the
holiday on an alternate day when the holiday falls on a
Saturday or Sunday, you would need to select this
Alternative Day Off Rule.
8. Save your holiday record.
To activate a holiday:
Deactivating a holiday
Any holiday that you can activate you can also deactivate.
Inactive holidays will not affect the ACDB schedules until you
make them active.
To deactivate a holiday:
To edit a Holiday:
Tip: By using the 2. In the left pane, select the holiday you want to edit.
multi-select toolbar buttons 3. Edit the holiday.
or the multi-select action
menu items, you can select 4. Save the holiday record.
multiple holidays for Note: If you are unable to navigate and select a specific holiday,
editing and deleting. All the list may be locked. You need to save the changes to the
selected holidays can be holiday currently being modified before you can select a
edited or deleted at one different holiday.
time. Only limited editing
functionality is available Deleting a holiday
when selecting multiple
holidays. The need may arise for you to remove a holiday.
Example: Your organization may have an employee
appreciation day that has been given annually, but this holiday
has been eliminated and will no longer be used.
To delete a holiday:
Summary
This chapter describes access levels and shows you how they
work. It also covers the process of creating access levels and
assigning schedules, command lists, and privileges to an access
level.
A cardholder can not enter through a door until access levels are
created. Assigning access levels to cardholders defines their
access properties.
Content
What is an access level? • 10.2
Access level tab • 10.2
Icons on the access level tree • 10.2
Access level toolbar and view buttons • 10.3
States of an access level • 10.4
Creating an access level • 10.6
Expanding and collapsing an access level • 10.8
Assigning a schedule • 10.10
Assigning a different schedule • 10.11
Removing a schedule • 10.11
Assigning a command list • 10.13
Assigning a different command list • 10.14
Removing a command list • 10.15
Setting door privileges • 10.16
Setting door privileges • 10.17
Setting door privileges for multiple doors • 10.17
Removing door privileges • 10.17
Setting KPDISP privileges • 10.18
KPDISP security privileges • 10.18
KPDISP fire alarm privileges • 10.20
Setting KPDISP privileges • 10.20
Setting KPDISP privileges for multiple KPDISPs • 10.20
Removing KPDISP privileges • 10.21
Deleting an access level • 10.22
The Manager Shift 1 access level has a red X over all icons. This
indicates that no schedules or privileges have been assigned to
this access level.
Note: The Access Level name is not updated in the tree view,
until you save the access level.
Assigning a schedule
Assigning a schedule to a door in an access level determines the
time when access is granted at that door. The cardholders that
have this access level assigned to them can enter the door during
the scheduled time.
Doors that do not have a schedule are not accessible by
cardholders with this access level. Doors without schedules are
displayed with a red X.
Schedules can be assigned to an access level, site, building,
partition, or individual doors. Assigning a schedule to an access
level, site, building, or partition assigns the same schedule to all
the doors shown within the selected item. This is the quickest
and easiest way to assign the same schedule to multiple doors.
To assign a schedule to single door, simply select the individual
door and assign the schedule.
After a schedule has been assigned, the associated schedule
name is shown below the door.
Removing a schedule
If a group of cardholders no longer requires access to an area in
the access level, the schedule for that area can be removed.
To remove a schedule:
Disarm privilege
A door with disarm privilege disarms the associated partition
when a valid cardholder badges in. For the door to have disarm
privilege it must be associated with a partition.
1. Check or clear the desired door privilege check boxes for the
door.
2. Save the access level record.
Disarm privilege
An KPDISP with disarm privileges allows cardholders to disarm
a partition with the keypad. When you disarm a partition, you are
advising the system to stop monitoring devices in the partition
for security alarm events.
Disable privilege
The fire alarm disable privilege allows a cardholder to disable a
fire alarm device from a keypad.
Tip: Press Alt + F, D to 2. From the File menu, click Delete or click the Delete button
delete an access level. on the toolbar.
3. Click Yes to delete the access level.
The access level state changes to Pending Deletion.
4. From the File menu, click Send Changes or click the Send
Changes button on the toolbar.
This downloads the database to your access control system.
After the download, the system changes the access level’s state
to Deleted. When you exit from and restart the ACDB, the
deleted access level is no longer present.
Summary
This chapter provides instructions for creating a cardholder
record and entering basic cardholder information. Cardholders
are granted access to your site by assigning access levels and an
access card ID.
Content
What is a cardholder? • 11.2
Creating a cardholder record • 11.3
Card information • 11.4
KPDISP password • 11.5
Access levels • 11.5
Adding personal information • 11.8
Naming cardholder UD tabs and UDFs • 11.10
UD cardholder tabs • 11.10
UDF labels • 11.11
Adding a photo to a cardholder record • 11.13
Importing and sizing a cardholder photo • 11.13
Exporting a cardholder photo • 11.14
Clearing a cardholder photo • 11.15
Activating and deactivating cardholders • 11.16
Activating a cardholder • 11.16
Deactivating a cardholder • 11.16
Filtering cardholder information • 11.18
Letter tabs • 11.18
Filters • 11.18
Editing and deleting cardholder records • 11.20
Editing cardholder records • 11.20
Deleting a cardholder record • 11.20
Reissued cards vs. lost cards • 11.21
Reissuing a card • 11.21
Lost cards • 11.21
What is a cardholder?
A cardholder is any person to whom you issue a card that grants
access to your site. To access a building, a cardholder must have
an access level and an access card ID. The cardholder is then
downloaded to the Card Reader Controllers (CRCs) of your
access control system.
When a cardholder presents his card at a card reader, the CRC
verifies that the request for access falls within the parameters of
the cardholder’s access level and either grants or denies him
access based on this assessment.
Each cardholder can be assigned different levels of access.
Access levels are customized according to site specifications. A
photograph of the cardholder can be added for additional
security and identification purposes.
Cardholders tab
Name
The first field in a cardholder record is the cardholder’s full
name. The title (Mr., Mrs., Ms, or Miss) is optional.
Status
In the interest of controlling building access, cardholders are
placed in one of three main status categories: Employee, Visitor,
or Visitor Requiring Escort. One of these categories must be
selected for each cardholder.
Visitor requiring escort means that a visitor can not gain access
without an escort (a cardholder with access to the door) badging
in at the same door and at the same time.
Disability
Cardholders with a disability can be assigned disability
privileges by checking the Has Disability check box. A disabled
cardholder is granted extra access time when badging into a
door. If the door has an automatic door opener installed, the
CRC can be configured to activate the door opener.
Card information
After selecting the correct status for the cardholder, information
specifying the card type, card ID, and PIN number can be set.
Format
Wiegand 26-bit to 38-bit card formats are available in the Format
list. You can use one of the card formats provided or create your
own card format.
To create your own card format and to set the default card
format, refer to Chapter 12: Cardholders advanced.
Facility
Some card formats use a facility code. You can define the name
and number for each facility code you need to use. Facility
names and facility codes are specified in Tools>Options>Facility
Codes.
For more information on facility codes and to set the default
facility code, refer to Chapter 12: Cardholders: advanced.
Card ID number
Each cardholder has a 10-digit card ID number that uniquely
identifies the cardholder in your access control system.
Specific types of cards are used within the ACDB. They include:
• Construction cards: used when the system is being set up,
installed, and programmed (Number = 000,000,001)
• HID Prox cards: have a number preprinted on the card
(Number range = 000,000,002 to 129,999,999)
KPDISP password
The PIN number is also used to log on to the Keypad Display
(KPDISP). The password to log on to a KPDISP must consist of
seven digits. The password consists of the last three digits of
your card ID plus a four-digit PIN number.
Access levels
An access level defines access properties for cardholder groups.
Properties of an access level consist of the following:
• Schedules for doors
• Command lists for doors
• Privileges for doors
• Privileges for KPDISPs
Normally you give each access level a name based on the job
function of a group of cardholders. Cardholder groups that need
different access properties are assigned a different access level.
An access level defines the doors and times at which cardholders
are granted access. It also defines what privileges a cardholder
has at each door and each KPDISP. A command list can be
assigned to a door, so that each time the CRC grants access, the
attached command list is activated.
Access Level #1 list contains all the access levels you created
earlier, using the Access Level tab
Level name
Cardholders access properties are determined by assigning the
appropriate access levels. You can assign up to two different
access levels per cardholder.
Note: Access levels must be created before you can assign them
to cardholders.
While only one access level is required to grant a cardholder
access, you can grant an additional, optional access level. Two
different access levels can be used to set up employees who
work rotating shifts.
When the access levels are used to control access during rotating
time shifts, the first access level is the current schedule and the
second is the future schedule.
Access levels and dates can also be used to control parking lots
and enable the use of temporary schedules.
Note: If you need the second access level to override the first,
check the Second Access Level Overrides First check box.
Activation date
An activation date is required for each access level you assign.
The default is the current date, but if you need to delay activation
for any reason, you can select a future date and the system denies
access until that date.
Expiration date
In some cases, an expiration date is required. An expiration date
is used to deactivate a cardholder’s access to your site.
You can enter activation and expiration dates by selecting them
from the calendar tool that opens when you click the list drop-
down arrow. You can edit dates using this tool, or by typing in
the list box.
Example: If you had a telephone technician in your facility, he
could be classified as a visitor requiring escort. If he needed to
be there for two days, you could set the expiration date so that
the assigned access level would expire in two days.
Tip: You can press the Tab 8. Type the card’s ID or swipe the card to obtain the card’s ID.
key on the keyboard to 9. If applicable, type a PIN number for the cardholder.
move from field to field
within the CardHolder tab. 10. In Access Level #1, select an access level for the cardholder.
11. Select an activation date.
12. If the cardholder’s access level needs to have an expiration
date, clear the Does not expire check box and select an
expiration date.
13. If the cardholder requires an additional access level, select a
second access level in Access Level #2 .
14. Repeat steps 11 and 12 for Access Level # 2.
15. If Access Level #2 overrides Access Level #1, check the
Second Access Level Overrides First check box.
16 Save the cardholder record.
1. From the left pane, select the cardholder to whom you wish
to enter personal information.
UD cardholder tabs
The UD CardHolder Tab Labels tab is where you customize the
three UD cardholder tabs. Each tab supports ten UDFs. This lets
you group custom cardholder fields together, to meet your needs.
Operator privileges can be set individually for each UD
cardholder tab, so you can restrict sensitive data from all but
authorized operators.
To name UD tabs:
UDF labels
The UDF Labels tab is where you name the thirty custom fields
on the UD cardholder tabs. You can create custom fields to store
such information as internal company training dates, pay levels,
or family information.
UDF labels 1–10 are for tab one, 11–20 are for tab two, and 21–
30 are for tab three
To name UDFs:
The Edit Photo dialog box lets you add the cardholder’s picture
to their record
Crop: Lets you select a certain portion of the photo. Using your
mouse, drag a selection box on the photo. When you release the
mouse button, the selected portion of the photo is displayed in
the right pane.
You can move the selection box to any location on the photo. To
do so, simply drag the box. Notice the mouse changes its
appearance once over the selected area. The display area changes
as you move the selected box.
Scale to fit: Lets you enlarge the selected area of the photo to fit
the display pane. You select a portion of the photo by dragging a
selection box.
Select Entire Image: Selects the entire photo image. You must
first click Scale to fit for the Select Entire Image button to
become available. Your entire photo is selected and displayed in
the right pane.
After sizing, the photo is displayed in the right display pane
exactly as it will appear on the Cardholders tab.
1. In the left pane, select the cardholder for whom you want to
import a photo.
Tip: Press Alt + I to launch 2. Click Import.
the Edit Photo dialog box. 3. Load or copy the photo.
4. Size your photo.
5. Under Storage, move the Image Quality slider to the desired
quality.
The higher the quality, the larger the image size. The image
file size is displayed under the slider bar.
6. Click OK to import the file.
7. Save your changes.
1. In the left pane, select the cardholder for whom you want to
export a photo.
Tip: Press Alt + E to export 2. Click the Export button in the Photo group.
the photo. 3. Browse to the desired location to export the photo.
4. Type a name for the file in the Name field. The default is the
cardholder’s name.
5. Click Open to export.
1. In the left pane, select the cardholder for whom you want to
Tip: Press Alt + C to clear clear a photo.
the photo.
2. Click the Clear button in Photo group.
3. Click Yes to clear.
An inactive cardholder
To activate a cardholder:
Tip: By using the
multi-select toolbar buttons 1. In the left pane, select the cardholder you want to activate.
or the multi-select action
menu items, you can select 2. Click the Activate Card button.
multiple cardholders for 3. Save the cardholder.
activating or deactivating.
All selected cardholders The status of the cardholder record changes from Inactive to
can be activated or Pending Active indicating that the information is now ready to
deactivated at one time. be downloaded to the hardware of your access control system.
It is recommended that no more than 1000 cardholders be
activated and downloaded at any one time.
Note: Cardholder data that is saved is not active until it is
downloaded to the access control system. See Chapter 3: Basic
operations for information about downloading.
Deactivating a cardholder
Any card that can be activated can also be deactivated. A
deactivated cardholder does not have any access privileges. A
To deactivate a cardholder:
Letter tabs
The simplest method is to use the letter tabs at the bottom of the
cardholder selection list. These tabs let you display only those
records beginning with the letter you select.
Filters
You can show specific cardholders by applying various filters to
the list. To apply a filter, you select a field from the On list, then
specify a value for that field. On records matching the specified
value are displayed.
Filter Definition
Filter Definition
To apply a filter:
1. At the top of the cardholder record list in the left pane, check
the Filter check box.
2. In the On list, select the desired filter.
3. In the field below, select or type the desired value.
Cardholders that meet the filtered criteria are shown in the left
pane.
Tip: Press Alt + F, D to 1. In the left pane, select the cardholder record you want to
delete a cardholder. delete.
2. From the File menu click Delete or click the Delete button
on the toolbar.
3. Click Yes to delete the record.
Reissuing a card
Reissuing a card removes all cardholder data from the record
except for information about the access card itself. The
information that is retained is the Card Format, Facility Code,
and Card ID. The cardholder’s last name is changed to !Reissue-
x.
For a card to be reissued the cardholder must be deactivated
before reissuing.
Any card activity that occurred before the reissue date is
attributed to the previous cardholder, but once the card is
reissued; all future activity is attributed to the new cardholder.
Note: The undo function is NOT available when reissuing a
card. Once you execute the reissue command, the data associated
with that card is deleted and can not be retrieved.
To reissue a card:
1. In the left pane, select the cardholder record for the card to
be reissued.
2. From the Action menu, click Reissue Card or click the
Reissue button on the toolbar.
3. Click Yes to reissue the card.
The card is now ready to be issued to a new cardholder.
Lost cards
If an ACDB cardholder loses his access card, you have two
options.
• Wait to see if the cardholder finds his card
• Issue the cardholder a new card
If you are not going to issue the cardholder a new access card,
deactivate the cardholder. Deactivating the card prevents anyone
who finds the access card from illegally entering your site. Keep
the cardholder inactive until he finds his card or until you issue
Summary
This chapter provides detailed instructions on the advanced
features for cardholders in the ACDB.
Content
Adding a card format and a facility code • 12.2
Adding a custom card format • 12.2
Adding a facility code • 12.4
Setting the default card format and facility code • 12.6
Administration > System tab • 12.6
Options command • 12.7
Configuring an auxiliary card reader input • 12.9
Scanning in card numbers • 12.10
Assigning central monitoring station user IDs • 12.11
Modifying a CMS user ID • 12.12
Deleting a CMS user ID • 12.13
Exporting a cardholder for badging • 12.14
Exporting a cardholder • 12.14
Exporting additional fields to EPISUITE • 12.15
Changing the EPISUITE database • 12.15
Importing cardholders from an external database • 12.17
Start the database import utility • 12.17
Creating an import definition • 12.17
Assigning import fields • 12.20
Formatting photos • 12.21
Importing the data • 12.22
Card Code Format Editor dialog box lets you create a custom
card format
5. In the Type box, click Even or Odd to specify the parity bit
type.
6. In the Position box click Precedes or Trails to specify the
position of the parity bit.
7. Type the binary constants for the card ID.
The binary constants are constant values included at the
beginning or end of each card ID.
1. If the card format has a facility code, click the Facility Code
tab.
2. Scroll up or down to select the bit size of the facility code.
3. Type a test value for the facility code (optional).
4. If the facility code has a parity bit, check the Has a Parity Bit
check box. If not skip to step 7.
5. In the Type box, click Even or Odd to specify the parity bit
type.
6. In the Position box click Precedes or Trails to specify the
position of the parity bit.
7. Type the binary constants for the facility code.
The binary constants are constant values included at the
beginning or end of each card ID.
Note: If most of your cardholders will be using this card code
format, make it the default. See Setting the default card format
and facility code in this chapter.
To set the default card format and facility code using the
System tab:
4. In the Default Card Format list, select the card format that
your company will be using most often.
5. In the Default Facility Code list, select the facility code that
your company will be using most often.
Options command
The default card format and facility code can also be set using
the Options command on the Tools menu.
Setting the default card format and facility code from Tools >
Options > Company Information tab > Default
To set the default card format and facility code using the
Options dialog box:
Note: If the card format or facility code is not listed, you can
create a new one. Click the New button to the right of the
appropriate list. The New buttons open the Card Code Format
tab or the Facility Code tab. You can create a new card format or
facility code using these tabs. See Adding a custom card format
and facility code in this chapter.
The CardHolder > System tab lets you assign CMS user ID
numbers to individual cardholders
Exporting a cardholder
You must install the EPISUITE software on the same computer
as the ACDB to activate the Badge button.
When the Badge button is pushed from the CardHolder tab the
following ACDB fields are exported to the corresponding
EPISUITE fields:
ACDB EPISUITE
Title Title
First Name First Name
Last Name Last Name
Address Line 1 Address
City City
State State
ZIP ZIP Code
Country Country
Phone Number Home Home Phone
Phone Number Business Work Phone
IDs Company Company
IDs Employee Employee Number
Card ID Person ID
To export a cardholder:
1. From the bottom left list, select the import definition you
want to use.
2. From the Unassigned External Fields list, drag each field
you want to import into the Crossed Field Name column.
Place it beside the CH Display Name (ACDB) in which the
data should be stored.
Note: The CH Display Name is where the imported data will
be stored in the ACDB. Not all fields need to be dragged
from the Unassigned External Fields column to the Crossed
Field Name column. Only drag the fields you want to import
into the ACDB.
Formatting photos
If your external database includes photos for import, you can edit
the import properties for the photos. The Image button becomes
active as soon as a crossed field name is dragged to the photo
row. The Image button opens the Set Photo Properties dialog
box.
The Set Import Photo Properties dialog box lets you set import
properties for all photos being imported. The properties you set
apply to all photos. You can not set individual properties for
each photo. You can view each photo by clicking the arrow
buttons to preview all photos before import.
For information on how to set photo properties refer to Chapter
11: Cardholder: Basic.
The Set Photo Import Properties dialog box lets you set the
properties for all photos being imported
To format photos:
Summary
This chapter describes the ACDB reports, and shows how to
create and run reports. You will find that reports are a valuable
tool for providing information about your access control system.
Content
What is a report? • 13.2
The Reports tab • 13.2
Reports and tasks • 13.3
Default reports • 13.5
Customizing a default report • 13.5
Creating a report • 13.7
Filtering reports • 13.9
Filtering doors • 13.9
Filtering access events • 13.10
Filtering conditions • 13.11
Setting the styles for a custom report • 13.15
Creating report headings • 13.15
Creating report groups • 13.16
Setting report fonts • 13.16
Setting report orientation • 13.17
Adding fields to a custom report • 13.18
Running a report • 13.20
Viewing and printing a report • 13.22
Deleting a previously requested report • 13.22
Editing and deleting a report • 13.24
Editing a report • 13.24
Deleting a report • 13.24
What is a report?
A report is information that is gathered about your access control
system, then displayed in a preview format. Information for
reports can come from your ACDB database, or from the
hardware of your access control system.
Several types of report provide information about your access
control system. Each report falls into one of three categories.
• Access event reports
• Database reports
• Presence reports
Database reports
Database reports use data from the ACDB. They can include
information that is stored about cardholders, access levels,
schedules, or holidays.
Presence reports
A presence report shows where cardholders are located in the
site. In order to run a presence report, you must set up an access
control system that has partitions, and entry and exit card
readers.
The Reports tab lets you run reports on access events, database
information, and cardholder location or presence
Default reports
The ACDB has several predefined or default reports. You can
use the default reports as they are, customize them, or create new
custom reports. The default reports are listed below.
Creating a report
If the default reports or customized default reports do not meet
your needs, an entirely new custom report can be created. All
reports fall into one of the following report types.
Filtering reports
Default reports, customized reports, and new reports can be
filtered, using the Filter tab. Filtering lets you narrow the
information provided in a report. The Filter tab contains up to
three sub-tabs, which can be used to filter a report:
• Doors
• Access events
• Conditions
Not all report types have the Filter tab or all filter options. The
following table shows the reports you can filter, and the sub-tabs
available.
Filtering doors
Filtering doors limits reports to specific areas of your site. A
report can be filtered by selecting your entire building or any
combination of partitions, KPDISPs, and CRCs (doors). The
CRCs and KPDISPs that are to be included in the report are
highlighted in gray when selected.
Note: Selecting no keypads or doors includes all doors and
keypads in the report. This is the default.
To filter a report:
Filtering conditions
You can create complex selection and filtering criteria to further
refine your reports. The logical statements you create on the
Conditions tab limit the data included in the report.
5. Click the circle in front of the word Choose and select Add
Condition.
8. Click the blank line at the end of the condition, and select
from the list or type the specific item of the condition.
To group a report:
To select fonts:
Portrait
Landscape
To orient a report:
1. In the left pane, select the report you want to add fields to.
2. Click the Fields tab.
3. Select the field you want to include in your report and click
the large right arrow to add the field. Fields must be selected
and added one at a time.
4. If you want to sort a field, select the field from the right pane
and click the sorting arrow. Select Not sorted, Ascending, or
Descending.
Note: Not Sorted is the default setting. The first item sorted
takes priority over any items that follow.
Running a report
You can run a report at any time by clicking the Run Now
button.
For access event history reports, the ACDB prompts you to
select a source for the report data. You have two options, the
ACDB database, or your access control system hardware.
If you click Assemble report from database, the report uses the
data that is in the ACDB. This includes any data that has been
collected by AC History type tasks. See Chapter 6: Tasks for
more information.
If you click Collect from hardware, the report uses the data from
each CRC you have specified. This report gives the most current
information from your access control system. The data collected
from the hardware is stored in the database for later reports.
If you are running a report type other than access event history,
the report will run as soon as you click Run Now. As the report
is running, its status can be viewed on the Status tab.
Once all the information for the report is gathered, the ACDB
displays a preview of the report. From the preview window the
report can be reviewed, saved, and printed. All reports are stored
and can be viewed from the Reports Status tab.
To run a report:
1. In the left pane of the Report tab, select the report you want
to run.
2. Click the Run Now button.
View button 1. In the left pane, select the report you want to view.
2. Click the Status tab.
Delete button
3. Click the Finished Reports tab.
4. From the Finished Reports table, select the report you want
to view.
5. Click the View button.
6. From the Preview window click the Print button.
7. Click the Close button.
To edit a report:
Deleting a report
You can delete a Report at any time. It may be easier to edit the
report into a new report rather than delete it and start over.
To delete a report:
badging (in or out) A general term for the process whereby a cardholder presents
credentials to a reader in order to request access into or out of
a controlled area.
bypass Devices can be bypassed or disabled. When a device is
bypassed, the system ignores its alarm events, but continues to
monitor other events. When a device is disabled, the system
ignores all event messages from the device.
bypass time The bypass time is the number of seconds (0 to 255) that the
CRC suppresses audible annunciation and alarm notification.
card reader Any of the different types of credential reader supported by the
CRC. We use card reader as a general term to refer to
proximity, Wiegand pin, magnetic stripe, and smart card
readers, as well as readers equipped with a keypad.
Card Reader Controller CRC. A module that performs card access processing
module (CRC) decisions for a door, and grants or denies access to a
cardholder. Each CRC stores a complete database and is
capable of granting or denying access without external
communication.
cardholder A general term used to refer to any user of an access control
system issued with a valid access card (or other access
credentials). This also refers to users of a security system.
central monitoring station CMS. A station to which alarm and supervisory signaling
devices at the site transmit event messages. The central
monitoring station is staffed continuously to monitor, record,
and investigate alarm or trouble signals.
Central Processor module CPU. The primary processing module for an EST3 control
panel.
CMS See central monitoring station.
command list A predefined event that can be used to trigger execution of
SDU rules The CRC can be programmed to transmit these to
the control panel in response to certain access events.
Command lists are typically used to trigger transmission of
access event messages to a CMS, or to trigger activation of
remote gates, CCTV, or relay modules.
common door An access control application where a given door is used by
several different companies, as in the main entrance of an
office building.
company General term for a group of end-users who use the access
control or security system at the project site. Projects can
include one or more companies. Generally, the resources of
dedicated security and access control devices are controlled by
a single company. Several companies may share the resources
of common devices.
construction card Special access cards that will work with any CRC prior to a
database being downloaded.
construction mode Before a database is downloaded to a CRC it is in construction
mode. Building contractors can use specially coded
door ajar timer The door ajar timer is the number of seconds that an access
door can be left open before a signal is sent to the fire alarm
system. If the door is left ajar past the door ajar time, the local
sounder in the CRC (if installed) sounds for one second every
minute. This is a security feature, ensuring that doors are not
propped open and left for an extended time.
door contact A switch that monitors the position (open or closed) of the door.
download Sending a compiled project database from a PC to the fire
alarm control panel. Also, sending an access control database
from a PC to the CRC devices via the control panel.
elevator control An access control application that determines which floors are
available to a given cardholder.
emergency exit door An access control application where an exit door can be
unlocked from the inside by badging out or by mechanical
means. If the door is opened without badging out, it causes an
immediate security alarm.
emergency exit sounder timer The emergency exit sounder timer is the number of seconds (0
to 255) the CRC sounder sounds when an emergency exit door
is violated without badging out or using a request to exit device
(without bypass).
enable Permit an input, output, or system feature to function. Also, to
instruct the system to monitor event messages from a device.
See also disable.
FireWorks A computerized display and control system used with EST2,
EST3, FCC, and IRC-3 fire networks. FireWorks uses one or
more display computers to monitor and control several
networks of multiplex signaling systems, card access systems,
and CCTV systems.
handicap access door An access control application for a door that provides
mechanical assistance and extended access time for a
handicapped cardholder.
Handicap unlock timer The handicap unlock time is the number of seconds that the
door stays open before relocking, when a cardholder
designated as handicapped badges in.
holiday An exception to the normal way of operating an access control
system.
holiday schedule Exceptions to normal schedules, when different access times
are desired.
input circuit Each CRC has two input circuits for use with access control
and security devices. These are typically used for a door
position sensor and a request to exit device. The input circuits
can also be used as security input points.
integrated system A panel-based system that can integrate fire alarm, security,
and access control functions.
integrated system Installer Typically an employee of the company that installed the access
control system.
irregular entry Entry into a building outside the cardholders normal access
time.
keypad Some card readers are equipped with a keypad to allow entry
of a PIN number in addition to the access card. We do not use
the term keypad to refer to the KPDISP Keypad Display
module.
Keypad Display module KPDISP. A control and display module used in security and life
safety applications. The KPDISP includes an LCD display, a
telephone-style keypad, a variable-tone sounder, and an
internal processor. It is most typically used to arm and disarm
security partitions.
KPDISP See Keypad Display module.
KPDISP password A password that allows cardholders access to the KPDISP. It
contains seven digits, the last three digits of the cardholder’s
access card and a four digit PIN number.
LED Light emitting diode.
lock Any type of door securing device. We use lock as a general
term to refer to both strikes and maglocks.
maglock Magnetic lock. A type of lock that secures the door (holds it
shut) when power is applied.
magnetic stripe card A type of access card having a data encoded magnetic tape or
stripe on one side.
manual open timer The manual open time is the number of seconds that the
auxiliary relay stays active, when an open command is received
from the fire alarm system, Fireworks, or from a local ADA
request to open device.
manual unlock timer The manual unlock timer is the number of seconds that the
door stays open before relocking, when an unlock command is
received from the fire alarm system, Fireworks, or a local
request to exit device.
MODCOM See Modem Communication module.
Modem Communication MODCOM. An communication module with modem and dialer
module capabilities. The MODCOM can be used to download
information from remote sites or to report events to a central
monitoring station. The MODCOMP can communicate to
telephone pagers using TAP protocol.
muster An access control application that lets users determine who has
exited a controlled area in the event of an emergency
evacuation.
muster report station A PC located in a secure area, outside the controlled area,
equipped with the ACDB program. Security staff use this PC to
create a muster report after an emergency evacuation.
muster station A CRC located outside the controlled area at which cardholders
badge out after an emergency evacuation.
NFPA 72 National Fire Alarm Code.
assigning buttons
new routes • 7.10 Start Now • 6.7
operator privileges • 5.9 Toggle Selection of Eligible Tree Nodes • 2.24
privileges • See Access Levels tab toolbar • 2.23
schedules • 10.10 Undo • 2.23
tasks to CRCs and KPDISPs • 6.10 Bypass privilege • 10.19
associating tasks with reports • 6.11 Bypass time • 4.16
attaching
command lists to access levels • See Add Access
Level Command List command
C
schedules to access levels • See Add Access calendars • 9.3
Level Schedule command canceling data entry mistakes • See Undo command
automatic logout settings • See General tab captions, startup screen • 3.2
(Preferences) card
automating ID numbers • 11.4
data retrieval for reports • 13.3. See also information • 11.4
associating tasks with reports number ranges • 11.4
system updates • See system updates types • 1.10
Card Code Format Editor • 12.3
B card code formats • 3.6, 12.2
Card Code Formats tab • 3.6
backing up your system • 3.14 Card ID filter • 11.18
Badge button • 12.14 CardHolder Import dialog box • 12.23
badging • 12.14 cardholder re-initialization • 6.6
Baud Rate field • 7.4 cardholder reports • 13.5, 13.7
Boolean filters • See brackets and conditions cardholders
brackets and conditions • 13.12 defined • 11.2
branches, access level • 10.8 deleting • 11.20
Browse Only button • 5.8 editing • 11.20
building blocks, ACDB • 1.11 filtering • 11.18
buildings, company • 4.5 introduced • 1.13, 1.15
Bus. Phone field • See Information tab sorting and searching • See cardholder information
buttons under filtering
access level tab • 10.4 CardHolders command • 2.21
Activate Holiday • 9.7 CardHolders tab • 2.25, 11.3
Activate Operator • 5.11 categorizing specific data • See reports under filtering
Activate Task Scheduling • 6.12 caution, reduced security • 10.19
Administrator • 5.8 changing
Browse Only • 5.8 EPISUITE database software • 12.15
Collapse Branch • 2.24 installer passwords • 2.5
Collapse Tree • 2.24 multiple items simultaneously • 3.10
Copy • 2.24 operator information • 5.17
Cut • 2.23 operators • 5.13
Deactivate Operator • 5.11 passwords • 5.14. See also Operator tab
Delete • 2.23 (Preferences for Operator ADMIN1 and
Deselect all records • 2.24, 3.10 Options)
Deselect All Tree View Nodes • 2.24 checking operator status • See operators under
Deselect current record • 2.24, 3.10 activating
Discard All Changes • 2.23 Christmas • See definition under holiday
Expand Branch • 2.24 City filter • 11.19
Expand Tree • 2.24 clearing cardholder photographs • 11.15
Grant All • 5.8 CMS (Central Monitoring Station) user IDs • 12.11,
Help Contents • 2.24 12.12
Message Center • 2.24 codes, facility • 12.4
New • 2.23 Collapse Branch button • 2.24
Operator • 5.8 Collapse Branch command • 2.21
Other Companies With Access • 4.10, 4.19 Collapse Tree button • 2.24
Paste • 2.24 Collapse Tree command • 2.21
Print Preview • 2.23 collapsing access levels • 10.8. See also Collapse
Redo • 2.23 Branch command; Collapse Tree command
Reissue • 2.24 Color dialog box • 8.8
Re-synchronize with Server • 2.24 colors • 8.8
Revoke All • 5.8 column widths, report • 13.19
Run Now • 13.20 command
Save • 2.23 lists • 1.13, 10.13
Select all records • 2.24, 3.10 privileges • 1.12
Select current record • 2.24, 3.10 Command Lists tab • 4.20
Send Changes to Access Equipment • 2.24
commands configuring
About • 2.23 doors • 4.9
Access Events • 2.22 hardware • See Hardware View tab
Access Levels • 2.21 site information • See Company View tab
Action Send Changes • 2.21 system hardware • See new routes under
Add Access Level Command List • 2.22 assigning
Add Access Level Schedule • 2.22 system sites • See new routes under assigning
Administration • 2.21 time ranges for AC history tasks • 6.8
CardHolders • 2.21 Confirmations tab • 3.4
Collapse Branch • 2.21 construction cards • 11.4
Collapse Tree • 2.21 Contents, Index command • 2.23
Contents, Index • 2.23 controlling access privileges • See Set Access Level
Copy • 2.20 Privilege command
Cut • 2.20 converter, Cypress • 12.9
Database • 2.22 Copy button • 2.24
Delete • 2.20 Copy command • 2.20
Delete Access Level Command List • 2.22 copying from one timeline to another • 8.5
Delete Access Level Schedule • 2.22 CPU (Central Processor Unit) • 4.8
Deselect All Records • 2.21, 3.10 CRC (Card Reader Controller)
Deselect All TreeView Nodes • 2.21 functions • 1.9
Deselect Current Record • 2.21, 3.10 new route assignments • 7.10
Discard All Changes • 2.20 privileges • 1.12
Exit • 2.20 schedules • 1.12
Expand Branch • 2.21 task assignments • 6.10
Expand Tree • 2.21 creating
Holidays • 2.21 access levels • 10.6. See also Access Levels tab
Import • 2.20 cardholders • 11.3
Login • 2.21 connection strings • 12.18
Message Center • 2.22 holidays • 9.3
New • 2.20 identification cards • See badging
Options • 2.22 import definitions • 12.17
Paste • 2.21 new card formats • 12.3
Photo • 2.22 new card formats and facility codes • 12.8
Presence • 2.22 new files • See New command
Print • 2.20 new operator records • 5.3
Print Preview • 2.20 outbound ports • 7.6
Printer Setup • 2.20 report groups • 13.16
Redo • 2.20 report headings • 13.15
Reissue Card • 2.22 reports • 13.7
Reports • 2.21 routes • 7.7. See also Hardware View tab
Reset Access Level Privilege • 2.22 schedules • 8.4. See also Schedules tab
Resource Usage • 2.23 tasks • 6.5
Resync with Server • 2.21 cropping photographs • 5.6, 11.14
Save • 2.20 customizing
Schedules • 2.21 ACDB features • See Administration tab;
Select All Records • 2.21, 3.10 Preferences tab
Select Current Record • 2.21, 3.10 applications and requirements • See UDF Labels
Set Access Level Privilege • 2.22 tab
Set Network Server • 2.22 card code formats • See card code formats
Toggle All Selections • 2.21 default reports • 13.5
Troubles Display • 2.22 Cut button • 2.23
Undo • 2.20 Cut command • 2.20
communication Cypress
errors • See yellow X symbols converter • 12.9
routes • 4.10, 4.19 interface • 11.5
Company Information tab • 3.5
company view icons • 4.3
Company View tab • 4.2, 4.3, 7.10
D
conducting a filtered query • See cardholder information Daily AC Events task • 6.4
under filtering Daily Updates task • 6.4
Configure Card Reader dialog box • 12.9 Data Link Properties dialog box • 12.18, 12.19
configuring database
alternative routes • 7.9 maintenance • 6.2, 6.5
auxiliary card reader inputs • 12.9. See also reports • 13.2. See also running reports
Default tab Database command • 2.22
default routes • 7.8 Database Import Utility • 12.21
door options • 4.11 Database Maintenance task • 6.4
door timers • 4.13 date displays • See General tab (Preferences)
Deactivate Operator button • 5.11 Deselect All Tree View Nodes button • 2.24
deactivating Deselect All TreeView Nodes command • 2.21
cardholders • 11.16. See also expiration date; lost Deselect current record button • 2.24
cards Deselect Current Record command • 2.21
holidays • 9.7 deselecting CRCs • See Toggle All Selections
operators • 5.11 command
task schedules • 6.12 Destination DB Init task • 6.4
Default tab • 3.5 determining operator logon status • See Status bar
defaults Diagnostic tab • 3.5
3-CPU • 7.4 dialog boxes
activation date • 11.6 CardHolder Import • 12.23
administrator operator ID • 5.2 Color • 8.8
card format • 12.6 Configure Card Reader • 12.9
facility code • 12.6 Data Link Properties • 12.18, 12.19
holiday • 9.2 Edit Photo • 5.5, 11.13
MODCOM route • 7.4 Import Resource Profile Manager (RPM) file • 2.7
operator ID • 2.6 Import Source Properties • 12.18, 12.20
operator privilege • 5.8 Modify Password • 5.14
password • 5.4 Options • 13.4, 13.20
photograph size • 5.5, 11.13 Preferences for Operator ADMIN1 and Options •
report • 13.5 3.3, 5.17
route • 7.4, 7.9 Set Photo Import Properties • 12.21, 12.22
schedule • 8.2 disabilities, cardholder • 11.4
sorting • 13.18 Disability filter • 11.19
task • 6.4 Disable privilege, Fire Alarm • 10.20
timeline color • 8.8 disabling fire alarms • See fire alarm privileges, KPDISP
timer • 4.14, 4.15 Disarm privilege • 10.16, 10.19
defining Discard All Changes button • 2.23
custom labels • See UDF Labels tab Discard All Changes command • 2.20
custom tabs • See UD Cardholder Tab Labels tab displaying current data • See Resync with Server
data for import • See import definitions under command
creating door
timeline colors • 8.8 option schedules • 8.3
Delayed Egress timer • 4.15 timers • 4.13, 4.14, 4.15, 4.16
Delete Access Level Command List button • 10.4 Door Ajar timer • 4.15
Delete Access Level Command List command • 2.22 downloading information • 3.12
Delete Access Level Schedule button • 10.4
Delete Access Level Schedule command • 2.22
Delete button • 2.23
E
Delete command • 2.20 Edit menu • 2.20
deleted state • 10.5 Edit Photo dialog box • 5.5, 11.13
deleting editing
access levels • 10.22 cardholder information • See CardHolders tab
actions by series • See Discard All Changes cardholders • 11.20
command company information • 4.3
cardholder photographs • See clearing cardholder databases without RP files • See sample RP files
photographs under importing
cardholders • 11.20 holidays • 9.9
CMS accounts • 12.13 operator records • 5.16
companies • 2.18 outbound ports • 7.12
holidays • 9.9 reports • 13.24
operator records • 5.16 routes • 7.13
outbound ports • 7.12 schedules • 8.7
photographs • 5.7 tasks • 6.15
previously requested reports • 13.22 Emergency Exit Sounder timer • 4.15
reports • 13.24 ending an ACDB session • See exiting the ACDB
routes • 7.13 entering new facility codes • 12.5
RP files • 2.17, 2.18 EPISUITE software • 12.14, 12.15
sample RP files • 2.12 event history reports • 13.5
schedules • 8.7 events, access granted irregular history • 10.16
SDU project • 2.17 exchanging network information between operators •
SDU projects • 2.11 See Message Center command
tasks • 6.15 Exit command • 2.20
denying operator access • See operators under Exit option • 2.3
deactivating exiting the ACDB • 3.16
Derived Card Number filter • 11.18 Expand Branch button • 2.24
Deselect all records button • 2.24 Expand Branch command • 2.21
Deselect All Records command • 2.21 Expand Tree button • 2.24
J M
Job Title field • See Information tab main headings • 13.15
maintenance, database • 6.5. See also setting
properties for DB maintenance tasks under
K procedures
keyboard shortcuts managing lost cards • 11.21
clearing photographs • 5.7, 11.15 Manual Open timer • 4.14
collapsing trees and branches • 10.8 Manual Unlock timer • 4.14
creating new access levels • 10.7 Maximum Message Length field • 7.4
creating new cardholders • 11.7 Maximum Retries field • 7.4
creating new holidays • 9.4 Memorial Day • See definition under holiday
creating new operators • 5.4 Menu bar • 2.20
creating new outbound ports • 7.6 menus
creating new reports • 13.8 Action • 2.21
creating new routes • 7.7 Edit • 2.20
creating new tasks • 6.6 File • 2.20
deleting access levels • 10.22 Help • 2.23
deleting cardholders • 11.20 Reports • 2.22
deleting operators • 5.16 Tools • 2.22
deleting reports • 13.24 View • 2.21
deleting schedules • 8.7 Message Center button • 2.24
deleting tasks • 6.15 Message Center command • 2.22
expanding trees and branches • 10.8 middle pane description • 2.26
exporting photographs • 5.6, 11.14 minimum system requirements • 1.4
finding • 2.20 miscellaneous door information • 4.16
launching the Edit Photo dialog box • 5.6, 11.14 MODCOM
launching the Options dialog box • 2.5, 5.17, default routes • 7.4
11.11, 12.3 route assignments • 7.10
launching the RPM Import dialog box • 2.10 user ID translation reports • 13.5, 13.7
logging off • 5.13 modem routes • 7.3
saving information • 3.9 modifications, SDU project • 2.14
selecting multiple holidays • 9.9 Modify Password dialog box • 5.14
selecting multiple outbound ports • 7.12 modifying
selecting multiple routes • 7.13 CMS user IDs • 12.12
selecting records • 3.11 default routes • 7.9
KPDISP (Keypad Display) Monday through Sunday schedules • 8.2. See also
applications • 4.18 Monday workweeks; Sunday workweeks
fire alarm privileges • 1.12, 4.18, 10.20 Monday workweeks • 9.4
functions • 1.9 monitoring
new route assignments • 7.10 employee attendance • See data retrieval for
password • 11.5 reports under automating
PINs (personal ID numbers) • 11.5 personnel on location • See presence requests
security privileges • 1.12, 4.18, 10.18 Monthly AC Events task • 6.4
task assignments • 6.10 moving
databases to new PCs • 3.15
text to and from the clipboard • See Edit menu
L multiple
labels, UDF (User-Defined Field) • 11.11 record selections • 3.10, 3.11
Labor Day • See definition under holiday sites and RP files • 4.5. See also RP file imports
landscape orientation • 13.17 muster reports • 13.5, 13.8
Language field • See Information tab
Last Login and Last Logout display • 5.4 N
Last Name filter • 11.18
left pane description • 2.26 Name field • 5.3
letter tabs • 3.7, 11.18 names, cardholder • 11.3
Level Name field (access level groups) • 11.6 navigation arrows • 3.7
levels, access • 1.11 network, ACDB
limits, system • See miscellaneous door information diagram • 1.6
lists, command • 4.20 versions • 1.5
Location field • See Information tab New button • 2.23
Log In option • 2.3 New command • 2.20
logging on after RP file imports • 2.13 New Year • See definition under holiday
logging on as a new operator • 5.13 No alternate day off rule • 9.3
logging on as an installer • 2.4 No day off rule • 9.3
Login command • 2.21 No Expiry filter • 11.19
printing procedures
command; Database command; Presence deactivating operators • 5.12
command; Print Preview command; Resource deactivating task schedules • 6.12
Usage command; running reports deleting access levels • 10.22
privilege tabs • 5.8 deleting cardholder photographs • See clearing
privileges cardholder photographs
access • 1.12 deleting cardholders • 11.20
Alarm Silence • 10.20 deleting CMS accounts • 12.13
Arm Away • 10.18 deleting companies • 2.18
Arm Stay • 10.18 deleting holidays • 9.9
Bypass • 10.19 deleting operator records • 5.16
command • 1.12 deleting outbound ports • 7.12
default operator • 5.8 deleting photographs • 5.7
Disable • 10.19 deleting reports • 13.24
Disarm • 10.16, 10.19 deleting routes • 7.13
Fire Alarm Disable • 10.20 deleting sample RP files • 2.12
Fire Alarm Panel Silence • 10.20 deleting schedules • 8.7
Fire Alarm Reset • 10.20 deleting SDU project • 2.17
Irregular Entry • 10.16 deleting tasks • 6.15
KPDISP fire alarm • 10.20 downloading changes • 3.12
KPDISP security • 10.18 editing company information • 4.4
problems, import • 12.23 editing holidays • 9.9
procedures editing outbound ports • 7.12
activating cardholders • 11.16 editing reports • 13.24
activating holidays • 9.7 editing routes • 7.13
activating operators • 5.11 editing schedules • 8.7
activating task schedules • 6.12 editing startup screen captions • 3.2
adding custom colors • 8.9 editing tasks • 6.15
adding fields to custom reports • 13.18 entering new facility codes • 12.5
applying cardholder filters • 11.19 entering personal cardholder information • 11.8
assigning CMS user IDs • 12.12 exiting the ACDB • 3.16
assigning command lists • 10.14 expanding access levels • 10.8
assigning different command lists • 10.15 exporting additional fields to EPISUITE • 12.15
assigning different schedules • 10.11 exporting cardholder photographs • 11.14
assigning fields to the ACDB database • 12.21 exporting cardholders • 12.14
assigning new routes • 7.11 exporting photographs • 5.6
assigning operator privileges • 5.9 filtering access events • 13.11
assigning schedules • 10.10 filtering conditions for cardholder reports • 13.12
assigning tasks to CRCs and KPDISPs • 6.10 filtering reports • 13.10
associating tasks with reports • 6.11 finding installer contact information • 2.8
backing up your system • 3.14 formatting photographs for import • 12.22
changing installer passwords • 2.5 grouping reports • 13.16
changing operator information • 5.17 importing and sizing cardholder photographs •
changing operators • 5.13 11.14
changing passwords • 5.14, 5.15 importing data • 12.23
changing the EPISUITE database • 12.16 importing new RP files into existing companies •
clearing cardholder photographs • 11.15 2.15
collapsing access levels • 10.8 importing photographs • 5.6
configuring auxiliary card readers • 12.9 importing real RP files • 2.11
configuring default routes • 7.8 importing RP files • 2.7
configuring time ranges for AC history tasks • 6.8 importing sample RP files • 2.10
copying from one timeline to another • 8.5 logging in as an installer • 2.5
creating access levels • 10.6 logging on after RP file imports • 2.13
creating connection strings • 12.19 modifying CMS user IDs • 12.13
creating holidays • 9.4 modifying default routes • 7.9
creating import definitions • 12.18 modifying SDU projects • 2.14
creating new card formats • 12.3 moving databases to new PCs • 3.15
creating new cardholders • 11.7 naming UD cardholder tab labels • 11.11
creating new operators • 5.4 naming UDF labels • 11.12
creating new reports • 13.8 orienting reports • 13.17
creating outbound ports • 7.6 printing reports • 13.22
creating report headings • 13.16 reissuing lost cards • 11.21
creating routes • 7.7 removing access level schedules • 10.11
creating schedules • 8.4 removing command lists • 10.15
creating tasks • 6.6 removing door privileges • 10.17
customizing default reports • 13.6 removing KPDISP privileges • 10.21
deactivating cardholders • 11.17 removing sample RP files • 2.12
deactivating holidays • 9.8 resetting operator passwords • 5.15
procedures removing
resetting timelines • 8.6 access level schedules • 10.11
reviewing building information • 4.5 command lists from access levels • 10.15. See
reviewing company information • 4.4 also Delete Access Level Command List
running reports • 13.20 command
saving changes • 3.9 door privileges • 10.17
scanning card numbers with auxiliary card readers KPDISP privileges • 10.21
• 12.10 schedules from access levels • See Delete Access
scheduling tasks • 6.7 Level Schedule command
selecting database tables for import • 12.20 removing sample RP files • 2.12
selecting report fonts • 13.17 repeating the last action • See Redo command
setting default card formats • 12.6, 12.7 report
setting default facility codes • 12.6, 12.7 customized default • 13.5
setting door privileges • 10.17 database-assembled • See running reports
setting door timers • 4.16 default • 13.5
setting KPDISP privileges • 10.20 hardware-based • See running reports
setting properties for DB maintenance tasks • 6.9 previously requested • 13.22
setting schedule options • 4.13 task associations • 6.11
setting up your system • 1.15 reports
sizing photographs • 5.6 AC (access control) history • 13.3
specifying card ID formats • 12.3 adding fields to custom • 13.18
specifying facility code formats • 12.4 defined • 13.2
starting external database imports • 12.17 filtering • 13.9
starting tasks manually • 6.7 printing • See running reports
starting the ACDB program • 2.2 running • 13.20
viewing 3-SAC information • 4.8 styling • 13.15
viewing command lists • 4.20 viewing • See running reports
viewing CPU information • 4.8 Reports command • 2.21
viewing door summary information • 4.10 Reports menu • 2.22
viewing KPDISP summary information • 4.19 Reports tab • 2.26, 13.2
viewing miscellaneous door information • 4.16 requirements, minimum system • 1.4
viewing partition information • 4.6 Reset Access Level Privilege button • 10.4
viewing reports • 13.22 Reset Access Level Privilege command • 2.22
viewing SDU information • 4.8 Reset privilege, Fire Alarm • 10.20
viewing site information • 4.5 resetting
viewing task status • 6.14 fire alarms • See fire alarm privileges, KPDISP
programming holidays • See Holidays tab operator passwords • 5.15
project sites • 4.4 timelines • 8.5
projected Resource Usage command • 2.23
day calendars • 9.3 resource usage reports • 13.5, 13.7
holiday reports • 13.5, 13.7 restoration settings • See General tab (Preferences)
prompts, save information (*) • 3.9 restoring system hardware • See initialization under
properties, access level • 10.2, 11.5 hardware
purging old data • See maintenance, database Resync with Server command • 2.21
Re-synchronize with Server button • 2.24
retrieving
Q access event information • See AC (access
queries, alphabetical • See filtering cardholder control) history requests
information information about logged-on operators • See
Quick Defaults group • 5.8 Operator tab (Preferences for Operator
ADMIN1 and Options)
reviewing
R building information • 4.5
records, new operator • 5.3 company information • 4.3
red X symbols • 10.10 project data • See View menu
Redo button • 2.23 reports • See running reports
Redo command • 2.20 Revoke All button • 5.8
Regular tab • 5.8 right pane description • 2.26
Reissue button • 2.24 rotating shifts • 11.6
Reissue Card command • 2.22 route
reissuing lost cards • 11.21 alternative • 7.9
Relay Open timer • 4.15 communication • 4.10, 4.19
relocating ACDB network servers • See Set Network default • 7.4, 7.9
Server command modem • 7.3
RS-232 • 7.3
routes setting
creating • 7.7 operator preferences • See Options command
defined • 7.3 operator privileges • 5.8
deleting • 7.13 properties for DB maintenance tasks • 6.8
editing • 7.13 report fonts • 13.16
RP (Resource Profile) functions • 2.4 report orientation • 13.17
RP file deletions • 2.17 styles for custom reports • 13.15
RP file imports • 2.6, 2.7 system access privileges • 1.15
RS-232 routes • 7.3 system preferences and options • 3.3
rules, alternative day off • 1.11 task frequencies • See scheduling tasks
Run Now button • 13.20 silencing fire alarms • See fire alarm privileges, KPDISP
run transaction queue • 6.6 sites, project • 4.4
running reports • 13.20 sizing photographs • 5.5, 11.13, 11.14
software, EPISUITE • 12.14, 12.15
Sort By Holiday Name checkbox • 9.6
S sorting
sample RP file imports • 2.10 cardholders • See cardholder information under
Save button • 2.23 filtering
Save command • 2.20 holidays • 9.6
save information prompts (*) • 3.9 special access • 1.14
saving your changes • 3.9 Special tab • 5.8
scaling photographs • 5.6, 11.14 specifying
scanning card numbers with auxiliary card readers • computers and COM ports • See Outbound Ports
12.10 tab
schedule reports • 13.5, 13.7 facility code formats • 12.4
schedules workweek start days • 9.4
assigning • 10.10 Standard Unlock timer • 4.14
CRC • 1.12 Start Now button • 6.7
creating • 8.4 start screen, ACDB • 2.2
defined • 8.2 starting
deleting • 8.7 ACDB programming sessions • 2.2
editing • 8.7 external database imports • 12.17
Schedules command • 2.21 tasks • 6.7
Schedules tab • 2.25 starting tasks manually • 6.7
scheduling tasks • 6.7 start-on days • See General tab (Preferences)
SDU (Systems Definition Utility) • 4.8 startup screen • 3.2
SDU project deletions • 2.17 startup screen captions • 3.2
Second Overrides First filter • 11.19 State/Province filter • 11.19
security privileges, KPDISP • 1.12, 4.18, 10.18 states, access level • 10.5
Select all records button • 2.24 Status bar • 2.26
Select All Records command • 2.21 Status filter • 11.19
Select current record button • 2.24 Status tab (Tasks) • 6.13
Select Current Record command • 2.21 status, cardholder • 11.3
selecting Style tab • 13.5, 13.15
alphabetical entries • See letter tabs subordinate headings • 13.15
database tables for import • 12.19 Summary tab • 4.9
doors (Card Reader Controllers) • See Toggle All Sunday workweeks • 9.4
Selections command suppression schedules • 1.14, 4.13, 8.3
entire images • 5.6, 11.14 Swipe button • 12.10
multiple records • 3.10, 3.11 system features • 1.8
printer options • See Printer Setup command system responses, predefined • See lists under
report source options • See running reports command
selection lists • 2.26 System tab (Administration) • 7.10, 12.6
Send Changes to Access Equipment button • 2.24 System tab (CardHolders) • 12.12
sending system updates • 6.2, 6.5
changes from the database to the hardware • See systems, access control and integrated • 1.9
system updates
new information to CRCs and KPDISPs • See T
Action Send Changes command
Set Access Level Privilege button • 10.4 tab
Set Access Level Privilege command • 2.22 Access Levels • 2.25, 10.2
Set Network Server command • 2.22 Administration • 2.26
Set Photo Import Properties dialog box • 12.21, 12.22 Administration (Privileges) • 5.8
setting Card Code Formats • 3.6
alternate days off for holidays • 9.3 CardHolders • 2.25, 11.3
default card formats and facility codes • 12.6 Command Lists • 4.20
door privileges • 10.16 Company Information • 3.5
KPDISP privileges • 10.18 Company View • 4.2, 4.3, 7.10
tab tips
Confirmations • 3.4 creating new access levels • 10.7
Default • 3.5 creating new cardholders • 11.7
Diagnostic • 3.5 creating new holidays • 9.4
Extra # • See UD CardHolder Tab Labels tab creating new operators • 5.4
Facility Codes (Preferences for Operator ADMIN1 creating new outbound ports • 7.6
and Options) • 3.6, 12.5 creating new reports • 13.8
Fields • 13.5, 13.18 creating new routes • 7.7
General (Company Information) • 3.5 creating new tasks • 6.6
General (Preferences) • 3.4 default communication parameters • 7.7, 7.8
Hardware View • 4.2, 4.7, 7.10 deleting access levels • 10.22
Holidays • 2.25, 9.4 deleting cardholders • 11.20
In Process • 6.13 deleting operators • 5.16
Information • 5.3 deleting outbound ports • 7.12
Operator (Preferences for Operator ADMIN1 and deleting reports • 13.24
Options) • 3.3 deleting routes • 7.13
Operators (Administration) • 5.3 deleting schedules • 8.7
Outbound Ports • 7.2, 7.3 deleting tasks • 6.15
Personal • 11.8 exporting photographs • 5.6, 11.14
Preferences • 3.4 finding keyboard shortcuts • 2.20
Regular • 5.8 information for scheduling tasks • 6.7
Reports • 2.26, 13.2 information for scheduling time ranges • 6.8
Schedules • 2.25 launching the Edit Photo dialog box • 5.6, 11.14
Special • 5.8 launching the Options dialog box • 2.5, 5.15,
Status (Tasks) • 6.13 11.11, 12.3
Style • 13.5, 13.15 launching the RPM Import dialog box • 2.7, 2.10,
Summary • 4.9 2.16
System (Administration) • 7.10, 12.6 logging off • 5.13
System (CardHolders) • 12.12 multiple selection • 3.11
Task Event Log • 6.13 quickening field navigation • 11.7
Tasks • 6.3, 13.3 save information prompts (*) • 3.9
Timers • 4.13 saving information • 3.9
Transactions Not Sent • 6.13 schedule names and descriptions • 8.4, 8.7
UD CardHolder Tab Labels • 3.6, 11.10 selecting multiple cardholders • 11.16, 11.20,
UDF Labels • 3.6, 11.11, 11.12 12.14
task selecting multiple doors • 10.10, 10.14
Daily AC Events • 6.4 selecting multiple holidays • 9.9
Daily Updates • 6.4 selecting multiple outbound ports • 7.12
Database Maintenance • 6.4 selecting multiple routes • 7.13
default • 6.4 Title bar • 2.19
Destination DB Init • 6.4 Toggle All Selections command • 2.21
functions • 6.2 Toggle Selection of Eligible Tree Nodes button • 2.24
Monthly AC Events • 6.4 toolbar buttons • 2.23
report associations • 6.11 toolbar, Access Level • 10.3
Update • 6.4 Tools menu • 2.22
Weekly AC Events • 6.4 Tracing checkbox • 7.4
Task Event Log tab • 6.13 tracking
tasks cardholder movements • See presence reports
activating scheduled • 6.12 CRC events • See event reports under access
creating • 6.5 database queries • See reports under database
deactivating scheduled • 6.12 modified records • See Title bar
deleting • 6.15 progress on a task • See task status under viewing
editing • 6.15 Transactions Not Sent tab • 6.13
scheduling • 6.7 tree view • 2.26
starting manually • 6.7 Troubles Display command • 2.22
tracking • See task status under viewing
Tasks tab • 6.3, 13.3
telephone communications • See modem routes
U
Thanksgiving • See definition under holiday UD CardHolder Tab Labels tab • 3.6, 11.10
time displays • See General tab (Preferences) UDF Labels tab • 3.6, 11.11, 11.12. See also EPISUITE
time ranges, AC history • 6.8 software
timelines • See schedules under creating Undo button • 2.23
Timeout field • 7.4 Undo command • 2.20
Timers tab • 4.13 Unlock on first Access Granted check box • 4.12
times, access • 1.11 unlock schedules • 1.14, 4.12, 8.3
tips unsaved information reminder • 3.9
case sensitivity • 2.5 unscheduled access • See Irregular Entry privilege
clearing photographs • 5.7, 11.15 Update task • 6.4