Product data

[Project Number] [Project Name]
[Date] [Project Location]
28 10 00 24
Electronic Access Control/Intrusion Detection
3. Reader Modes: In addition to the normal mode, each reader will be able to be programmed to respond in
the following modes:
a. ESCORT: Visitors or non-supervisory personnel may only gain access after presenting a valid
card, followed by an authorizing cardholder presenting his/her card.
b. TWO-PERSON: Two valid card reads will be required for access.
c. DURATION-USE: A user-definable time period may be set to reject successive card reads by the
same cardholder.
4. Access Modes: Each door may be programmed to switch automatically between the following modes of
operation, based on a user defined time schedule:
a. CARD ONLY
b. CARD + PIN
c. FREE ACCESS
d. COMMON 4 DIGIT KEYPAD ENTRY
e. CARD OR CARD # THRU KEYPAD
5. Duress: If a reader is operating in “CARD + PIN” mode, the duress feature will allow an alternate code to
be entered into the keypad for access. The system will then generate an alert that may be linked to
control relays for the notification of the duress alarm.
6. Door Alarms: Each door may be programmed to generate FORCED DOOR and DOOR OPEN TOO
LONG alarms. These alarms will be able to be allowed to have a time delay as required.
7. Door Alarm Annunciation: In addition to generating an alarm message, the following conditions may
activate an output for annunciation:
a. FORCED DOOR
b. DURESS
c. DOOR OPEN TOO LONG (DOOR AJAR)
d. VOID CARD
e. DENIED CARD
f. ANTIPASSBACK
g. INPUT DOOR ALARM
h. TAMPER
8. Card Data: The system software shall allow for card numbers up to 19 digits.
9. Facility Codes: The system software shall allow for up to 10 facility codes per-panel to be used in the
system simultaneously. All 10-facility codes can be downloaded to the Access Control Panels to function
in a stand-alone mode, with or without the PC. Alternately, 100,000 system facility codes per panel with
Facility Code/Badge Concatenation shall be supported. Systems supporting only one (1) facility code will
not be acceptable.
DD. Cardholder Database:
1. The cardholder database will contain all information required to control the cardholders’ access to the
facilities.
2. The system administrator will be able to restrict a system operator’s privileges to disable, view-only,
create-only, and create/edit.
3. Cardholder Records: Cardholder records will consist of a minimum of the following:
a. Card Number: The actual badge number assigned to the badge holder.
b. First and Last Name
c. Issue level: This indicates the number of times a particular badge number has been issued to a
badge holder.
d. Up to (6) Access Groups: Each badge record will be able to be assigned up to six access groups.
e. User-Definable PIN Code: A badge holder will be able to select his/her own PIN code. The PIN
code must have a minimum of 4 digits
f. Facility Code: The system shall be capable of accommodating various facility codes within the
system. A badge holder will be able to be assigned one of the ten available facility codes.
g. Anti-Passback Location and Status: This field shows the badge holder’s current anti-passback
status, Exempt from APB, In or Out, and the last In/ Out door they were allowed to enter or exit.
h. Activation Date: The system administrator will be able to enter a date in this field to enable the
concerned badge automatically.