Interlogix VEREX Director - Manual (Page 344)

336 Verex Director V4.9.1 User's Guide 21-0381E v4.9.1
Nothing feels better when setting up a new
system than that first "Access 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 (On), or checking system status
through a system (LCD) keypad.
The steps that follow provide the 'minimalist' approach to entering basic 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 operators required to complete this
task, along with their associated permissions.
"Operators...", and
"Operator Permissions".
Also: "Client/Server Access and
Permissions"
2) Multi-Account Systems: Set up account
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 default 'Panel Group' and Panel
name if desired, or set up new 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 doors
and/or elevators, be sure to specify the format
of the access cards/tokens.
"System Card-Access Settings"
6) If you wish to initially test any scheduling
features, be sure to create at least one
schedule for testing purposes.
"Schedules for User-Access and Area
Automation"
7) Ensure at least one "Area" has been set up to
allow testing your initial basic configuration.
"Areas and Related Settings"
8) Ensure one sample user "Authority Level" is
available to allow testing access-control and
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