WSE • 3/21/97 16720 — 19 SE 6000 Security Management System
3) Automatic transaction logging to the time and attendance database. The logs shall include
card holder id, no less than 6 user definable fields, clock in/out date and time.
4) Time transaction editing capability to ensure that data is accurate and complete prior to
transmittal to an ancillary database.
5) Time transaction reporting to provide a means of verifying the accuracy of any
transactions to be exported to a payroll system.]
6. [Electronic Visitor Directory (optional module):
a. General: The system shall provide an Electronic Visitor Directory option by which to process
and monitor visitors to a facility. This module shall provide the capability of storing both
permanent and current information for each visitor, as well as flexible reporting and badge
printing capabilities.
b. Database: A permanent database entry shall exist for each visitor, that can be retrieved,
modified and expanded with each ensuing visit, and transferred to the correct files for badge
creation, storage and reporting.
c. Reporting: Visitor reporting shall be selectable according to specific search criteria.
d. Pre-registration: The system shall also provide the capability for pre-registration and
advance preparation of visitor badges in order to facilitate the visitor registration process.]
7. [Remote Dial-up Interface (optional hardware):
a. General:
1) The system shall provide dial-up capability through an intelligent link between Host and
multiple Controllers, via dial-up phone lines.
2) A microprocessor-based hardware platform in conjunction with application software
shall provide remote dial-up support for no less than 3 Controllers.
b. Functions: The functionality of a remote dial-up interface shall include the following:
1) Automatic, high-speed download of data from Host to the Controller, thereby eliminating
data integrity problems and the need for human intervention between the two device
types.
2) Error free download of data through a communications protocol to provide error
detection and acknowledgment of each transaction as it is received by Host computer.
3) Automatic re-transmission of downloaded data upon detection of an error through a
database verification and memory check procedure.
4) Buffer storage capacity of no less than 6,000 transactions, with an automatic dial-out upon
a pre-defined threshold.
5) Immediate call in, to Host computer, of alarms based upon a user-definable table of alarm
conditions.
6) Redundant communications path with no less than 3 programmable, alternative phone
numbers to the RDI unit, which shall be used in the event of a communications failure to
Host computer. Upon dial-out of an alternative phone number, the alarm condition or
transaction buffer shall be routed to an optional computer, thereby triggering a report of
the communications failure to the primary computer.]
8. [Parking/ Revenue Control (optional module):
a. General: The system shall provide the capability to control access to, and the revenue
generated by, a parking facility. Through integration of cardholder access control with the
cashiering function required for transient parkers, the system shall provide total control of a
parking facility by tracking entry and egress of any type.
b. Functions: The parking control system shall encompass both the control of cardholder
parking and the control of transient parking by providing the following functionality:
1) Keyholder Parking Control:
(i) The same system that controls access to any facility shall control access to parking,
thereby optimizing the use of a single access card per cardholder.
(ii) The capability shall be provided to define parking access privileges by day of week,
time of day, and card reader.
(iii) Anti-passback shall also be supported.
Comentários a estes Manuais