User`s guide

334 VEREX Director V4.73 User's Guide 21-0381E v4.7.3
Nothing feels better w hen setting up a new
system than that first "Ac cess Granted". If
your system does not include door control , the
equivalent might be verifying that first motion
sensor as being monitored only when the area
is armed (O n), or checki ng system status
through a system (LCD) keypad.
The steps th at follo w provide the 'min imalist'
approach to entering b asic settings, and
getting you communicating with a panel so you
can transfer the information, and test for basic
operation.
Tips: In general, look for the sub-topic that refers to
"Adding..." in each referenced section. As well, for
initial testing, you can typically leave all settings at the
factory default values.
Basic Account and Device Settings for Initial Testing
Step (Do This): For details, refer to:
1) Set up the o perators requ ired to complete t his
task, along with their associated permissions.
"Operators...", and
"Operator Permissions".
Also: "Client/Server Access and
Permissions"
2) Multi-Account S ystems: Set up ac count
folders and accounts as desired.
"Working with Accounts and Folders
(multi-account systems)"
3) Set these items under "Account
Information": • Account Name;
• Account Type; • Panel Operating Mode;
• Panel Version; • Feature Set.
"Account-Wide Panel Settings..."
For system security, you may also wish to change the default 'service PIN'.
Tip: Be sure to log the new Service PIN somewhere, and/or select one that is easy to remember.
4) Rename the d efault ' Panel Group' and P anel
name if d esired, or set u p ne w ones as
required for additional panels.
"Panels, Panel Groups, and
Related Settings"
Tip: You can leave any panel communications settings as-is for now.
5) If the site includes access-controlled d oors
and/or elevators, be sure to specif y the format
of the access cards/tokens.
"System Card-Access Settings"
6) If you wish to initi ally test an y sc heduling
features, be sure to cre ate at le ast o ne
schedule for testing purposes.
"Schedules for User-Access and Area
Automation"
7) Ensure at le ast one "Area " has been set up to
allow testing your initial basic configuration.
"Areas and Related Settings"
8) Ensure on e sample us er "Authorit y Level" is
available to allo w testi ng ac cess-control a nd
other user-related features.
"Authorities for Users/Entrants"
9) Define one system "User" (with sample access
card/token) to allow testing access-control and
other user-related features.
"Users (Entrants / Panel Users)"
...continues...
Basic Settings for Testing, and Panel Communications