19
Item 52 - Zones assigned to keypad.
Program zones one (1) through twelve (12) for keypad 1, keypad
address of "0". Program zones thirteen (11) through sixteen (16) for
keypad 2, keypad address of "1".
Item 66 - User pass codes
Program the first group of users (1-12) that will access the office.
Program the second group of users (13-21) that will have access to
the warehouse. User codes 1 and 2 would be duplicated as users
13 and 14.
Item 67 - User Attributes
Program user 13 as the User Group Boundary. This user is now
identified as the first user of the second partition.
Item 68 - Zones assigned to user
Program users 1-12 with zones 1-10. Program users 13-21 with
zones 11-16. This location can also be used to have the "Limited
Access" feature by simply omitting the zones a particular user will
not have access to.
7.7
7.7
7.7
7.7
7.7
DISARMING THE SYSTEM
DISARMING THE SYSTEM
DISARMING THE SYSTEM
DISARMING THE SYSTEM
DISARMING THE SYSTEM
As in arming the system, the entire system must be disarmed to
display the ready status. Referring to our previous example in
section 7.5, if the maid disarmed the system, she would have only
disarmed her partitioned area zones one (1) through seven (7).
Zone eight (8), the safe, would still be armed and zones 1-7 would
indicate BYPASSED.
7.8
7.8
7.8
7.8
7.8
COMMON ZONING
COMMON ZONING
COMMON ZONING
COMMON ZONING
COMMON ZONING
SC System partitioning is very flexible. Both users and keypads may
control common zones (an example would be a hallway common to
a set of offices).
EXAMPLE:
EXAMPLE:
EXAMPLE:
EXAMPLE:
EXAMPLE:
An example of Common Zoning would be four doctors offices
sharing an SC800/1600 panel. Each office is given a separate
keypad with its own unique address. Each office (keypad) can now
be assigned a group of different zones (partitions) and finally each
office is assigned user codes with the user group assigned to zones
of their associated office. The common zone will be zone 1 shared
by all users and partitions. For "Common Zoning", each partition
must have a separate group delay assigned to it.
The programming required for this partition example would be as
follows:
Item 52 - Zones assigned to keypad
Program zones two (2) through four (4) for keypad 1, keypad
address = 0.
Program zones five (5) through eight (8) for keypad 2, keypad
address = 1.
Program zones nine (9) through twelve (12) for keypad 3, keypad
address = 2.
Program zones thirteen (13) through sixteen (16) for keypad 4,
keypad address = 3.
Refer to the keypad installation manual for proper keypad program-
ming.
Item 30 - Miscellaneous system function select
Program second miscellaneous system function select with a “2” for
multi-premise operation.
Item 66 - User pass codes
Program all thirty two (32) user codes.
The SC800/1600 system has the capability to allow thirty two (32)
users to operate the system. In multi-premise partitioning, these
users must be assigned to the specific keypad area they will control.
This is accomplished by setting up a user boundar
user boundar
user boundar
user boundar
user boundary
y
y
y
y - programming
an eight (8) in item 67 - user attributes for the fir
fir
fir
fir
first user of the
st user of the
st user of the
st user of the
st user of the
second,
second,
second,
second,
second, thir
thir
thir
thir
third and f
d and f
d and f
d and f
d and four
our
our
our
ourth
th
th
th
th partitions.
Any user who is allowed to change codes will have the ability to alter
an
an
an
an
any and all
y and all
y and all
y and all
y and all of the system user codes regardless of which partition
to which he is assigned.
Item 67 - User attributes
In an equally divided 32 user system as in the example the user
attribute 8 would be programmed at users 9, 17 and 25.
Item 68 - Zones assigned to user
Program the zones assigned to each individual user of the system.
Users 1-8 would be programmed for zones 1-4, users 9-16 pro-
grammed for zone 1 and 5-8, users 17-24 programmed for zone 1
and 9-12, and users 25-32 programmed for zone 1 and 13-16 .
One or more of the offices may have a sub-partition (partition within
a partition). For example, users 6,7 and 8 of partition one may be
denied access to the drug cabinet by not assigning these users the
zones associated with the drug cabinet.
PR
PR
PR
PR
PROGRAMMING CONSIDERA
OGRAMMING CONSIDERA
OGRAMMING CONSIDERA
OGRAMMING CONSIDERA
OGRAMMING CONSIDERATIONS
TIONS
TIONS
TIONS
TIONS
Common zoning is accomplished by assigning Zones per Keypad in
Item 52 that are strictly for that partition, except the common
zone(s). Assigning all common zones to appropriate users in Item
68 is how the operation is implemented. This will allow the first
partition disarmed to disarm the common zone(s) and the last
partition armed will arm the common zone(s). While the common
zone is disarmed, the zone will indicate as "Bypassed" on any and
all keypads that are in the armed state.
These zones must be specified as Entry/Exit Zones only and
assigned to an E/E Zone Delay Group. All partitions must have at
least one of their zones programmed into their respective Delay
Groups. In the above example zone 1 would be in 41 and 42 for
Group #1, Z5 would be in 42 for Group #2, Z9 would be in 42 for
Group #3 and Z13 would be in 42 for Group #4. Each keypad then
would tone during the Entry time as well as the Exit time. It is
recommended that the Entrance/Exit times be set the same for all
of the partitions to minimize nuisance alarms caused by inadequate
disarm time. Any alarm report generated for the common zone will
be reported to Partition (1) Account number.
7.9
7.9
7.9
7.9
7.9
MULTI-PREMISE SYSTEM OPERATION
MULTI-PREMISE SYSTEM OPERATION
MULTI-PREMISE SYSTEM OPERATION
MULTI-PREMISE SYSTEM OPERATION
MULTI-PREMISE SYSTEM OPERATION
System operation in multi-premise partitioning is the same as it
would be in the normal mode of operation except that the following
two system features are unavailable:
A
A
A
A
Automatic Bell
utomatic Bell
utomatic Bell
utomatic Bell
utomatic Bell T
T
T
T
Test
est
est
est
est
T
T
T
T
Test Mode
est Mode
est Mode
est Mode
est Mode
