Product data

[Project Number] [Project Name]
[Date] [Project Location]
28 10 00 20
Electronic Access Control/Intrusion Detection
3. The system operator may program these changes for the current year or any year in the future that the
operating system can support.
S. Badge Holders IN (Muster List):
1. The system shall be capable of providing a list of all badge holders currently logged as IN the building.
2. The list shall include the Name, Location and Time of the badge holders’ last IN transactions.
3. The default readers for this list shall be all readers. The operator will have the privilege of selecting any
reader in the system for the list, provided, the reader has been programmed to report ‘In’ and ‘Out’
events.
4. The operator shall be able to print a report of this list directly from the Badgeholders IN screen to any
printer on the system or it can be generated automatically in response to an event or input.
T. Find Usage:
1. The system shall enable the administrator.
a. To determine the time schedules and access groups that will be contained within a particular
Access Control Panel.
b. To determine the exact counts of badges, access groups and time schedules that will be contained
within a particular Access Control Panel.
c. To determine the presence of any Time Schedules or Access Groups that will no longer be used by
the system.
U. Badge Formats:
1. The system shall accommodate various badge data formats, simultaneously, by allowing the system
operator to enter into the system, the information about the data contained within a particular badge.
2. The system shall support multiple badge formats, simultaneously.
3. The Badge Format function shall support American Banking Association (ABA), FIPS 201-1, PIV II,
CHUID TWIC and Wiegand data formats.
4. The system software shall have the capacity to download a minimum of ten (10) user defined badge
formats to each panel. These formats will allow for the use of several card technologies, simultaneously.
Alternately, the system shall support 100,000 system facility codes per panel with Facility Code/Badge
Concatenation.
V. Alarm Monitoring Management and Alert Processing:
1. The system shall support 99 levels of alert priority. The system administrator will be able to assign these
priorities uniquely to any alert or event in the system.
2. The administrator may partition the events by user. Only events from the panels and readers in the
operators’ partition will be viewable.
3. Each priority will be uniquely identified by color that is hard-coded in the software.
4. The alert display screen will be divided into two sections.
a. Those alerts requiring intervention by the system operator will be placed in the ‘Pending Alerts
Grid’. These events will remain in the Pending Alerts grid until such time the operator makes a
determination, or the system Auto-Acknowledge function determines that the event should be
automatically acknowledged by the system. When an event is auto-acknowledged, the system will
append to the event record the date and time the event was auto-acknowledged, the operator that
was logged on, and an indicator that the event was auto-acknowledged.
b. Alerts not requiring operator intervention will be placed directly in the ‘Events Grid’. The Events grid
allows the operator to view the current and past events.
5. The system administrator will be able to force the operators to enter a response for each event the
operator processes. The administrator may predefine response messages which the operator may
choose from, or the operator can enter his/her own response.
6. The Events grid will contain button controls for sorting and viewing of events. The buttons will be:
a. Recent: This button will display the most recent / latest events. (This can be set per user).
b. Browse Mode: Once the user has logged in, the system shall automatically put the Events grid in
Browse. This mode will ‘freeze’ the event screen for browsing.