Product data
[Project Number] [Project Name]
[Date] [Project Location]
28 10 00 26
Electronic Access Control/Intrusion Detection
a. Card transactions
b. Alarm transactions
c. Event transactions
d. Operator activity
3. Search Criteria: The database shall be structured such that the operator can determine the search
parameters based on variables available on the individual report menu. Systems requiring the user to
type complicated search strings will not be acceptable.
4. Hardware Report: The system shall have the capacity to generate one comprehensive report that shows
the exact configuration of all installed and programmed hardware.
5. Export Report Capability: The system shall support the export of custom reports to Excel, HTML and/or
Text file data types.
6. Badgeholders IN (Muster) Report: The system shall support the Badgeholders IN report to be run
automatically with the use of an Input.
FF. Help Screens:
1. Online help: The system software shall have online help available at any point requiring operator input.
The help screen shall be accessible by using the standard Microsoft Windows help system. These help
screens shall contain context sensitive information that will allow the operator to enter correct data
without consulting the manual.
GG. System Status:
1. Real time status: The operator shall be able to monitor via graphical screens, the status of the following in
real time:
a. Inputs
b. Outputs
c. Doors
d. Workstations on/off line
e. Napco Panels
HH. Graphical Floor Maps:
1. Graphics File Format: The floor plans will be configured in a .JPG, .BMP. .DWF & .Ico formats to allow for
the importation of existing drawings.
2. Icons: The system shall allow the operator to assign doors, inputs, relays, links and Access Control Panels
to these floor plans to indicate the exact location of the event.
3. Operation: Upon activation of a selected input or door alarm, the system shall be able to automatically view
the associated floor plan with the alarmed icon blinking on the monitor.
4. Acknowledging Alarms: System operators must be able to acknowledge alarms on the map
5. CCTV: Any camera represented on the map will be able to be viewed by simply right clicking the mouse
and choosing view camera.
II. NAPCO Burglar Alarm and Fire Integration:
1. The NAPCO panels that will be supported are the GEM P3200, P9600, X255 and the GEMC 128, 9600
and 255. The integration will support receiving event information from the NAPCO panels, as well as
arming and disarming of NAPCO panels from the CardAccess 3000 system. Arming and disarming of
NAPCO panels may be by means of reader(s) in the CardAccess 3000 system, as well as manually
through an interface similar to the current manual control interfaces in the CardAccess 3000 GUI. It
allows unlimited number of cardholders to be programmed for arming and disarming.
2. General Description: The integration will include CardAccess 3000 GUI (Display Screen) to display
NAPCO alert types. All events generated will have to be configured to display pending status, priority
and/or response required. All these changes must be made through the CardAccess 3000 configuration
screens and stored in the same database as the CardAccess 3000 system.
3. Hardware and Communications
a. There must be one physical serial port for each NAPCO panel to be connected via serial
communications or, the NAPCO panel must be capable of interfacing over an existing network via
a Napco Netlink TCP/IP interface module. All network communication will be encrypted.