–8–
Example
Here is an example of how the area would react in a typical setup.
MAIN ENTRANCE
OFFICE #1
OFFICE #2
COMMON AREA
User #1 has access to Office #1 and the Common Area.
User #2 has access to Office #2 and the Common Area.
Office #1 is set up to affect the Common Area, but not arm it.
Office #2 is set up to affect and arm the Common Area.
For the purpose of this example, the ( ) indicate the current status of the other partition
when the user takes action.
Sequence #1:
Office 1
Office 2
Common Area Action
User #1: Disarms
(Armed)
Disarms
User #2:
(Disarmed) Disarms
No Change
User #1:
Arms
(Disarmed) No change
User #2:
(Armed)
Arms
Arms
Sequence #2:
Office 1
Office 2
Common Area Action
User #2:
(Armed)
Disarms
Disarms
User #1:
Disarms
(Disarmed) (No change)
User #2:
(Disarmed) Arms
No Change
User #1:
Arms
(Armed)
No Change
Notice that in sequence #1, since Office #2 was the last to arm, the common area also armed
(Office #2 is programmed to affect and arm the common area). In sequence #2, the common
area could not arm when Office #2 armed, because Office #1, which affects the common area,
was still disarmed.
When Office #1 armed, the common area still did not arm because Office #1 was not
programmed to arm the common area. User #1 would have to arm the common area
manually. Therefore, you would want to programme a partition to affect and arm the
common area, if the users of that partition are expected to be the "last out" of the building.
Common Area Programming Requirements
The following should be considered when assigning common areas.
1.
Common areas must be defined in ascending numerical order. That is, the common area
containing the lowest partition number should be defined as common area 1 (ex. Do not
define partition 8 as common area 1 and partition 1 as common area 2).
2.
Common area 1 must be defined before defining common area 2, and common area 2
must be defined before defining common area 3.
3.
A common area cannot be designated as an "affecting" and/or "arming" partition of
another common area.
4.
A partition not defined as a common area can be designated as an "affecting" and/or
"arming" partition for more than one common area. If designated as an "arming"
partition, it must also be an " affecting" partition
