NexSentry Manager Access Control & Security Management System

(1)

NexSentry Manager Access Control & Security

Management System

Featuring:

•

NexSentry Manager Security Management System, version 3.0

•

NexSentry Star I Controllers

•

NexSentry Star II Controllers

A/E Guideform Specification

Version 2.0 rev .8 • 7/28/2003

For the latest information about NexWatch Access Control and Security Management Systems and components, visit our web site at:

(2)

NOTES:

• The following A/E Guideform Specification conforms to CSI guidelines to provide Specifiers and Systems Integrators an easy way to include NexWatch products in their specifications.

• The Specifier should carefully select the portions of this document that fit the intended application. • Feel free to consult with your NexWatch Dealer regarding your particular application.

• Optional feature choices are represented by items enclosed in brackets [ ].

• Explanatory notes for the specifier are written in italics text and should be deleted in the final specification.

• This document is considered accurate through 7/28/2003. For updated specifications, call the NexWatch literature fulfillment desk at 800 232-9090, or visit the NexWatch Web page at http://www.NexWatch.com.

For specification assistance

For questions regarding application issues or use of this specification, please contact: William Kennedy @510-360-7878

Contributions

Project team leader:

- June Colagreco, MarCom Director

Editor:

- Bill Richardson, Technical Publications Manager

Core team members:

- William Kennedy, Product Manager

With contributions by:

- James Collins, System Design Manager

- Joe Oesterle, NexWatch Director Customer Service - Tony Smith, SeniorTechnical Writer

- George Sousa, Project Team Director

® ™ Microsoft and Windows NT are registered trademarks of Microsoft Corporation. Intel and

Pentium are registered trademarks of Intel Corporation. Dell is a registered trademark

of Dell, Inc.

NexSentry, NexKey, QuadraKey, are registered trademarks of NexWatch, Inc.

(3)

Table of Contents

PART I GENERAL ... 1

.1 Introduction... 1

A. Complete system proposal: ... 1

B. General services: ... 1

.2 System Description ... 1

A. Security Management System requirements: Required access control and security management system software shall:... 1

B. Computer Hardware:... 1

C. Access Control System: Access control system shall: ... 2

.3 DESCRIPTION OF WORK... 2

A. General:... 2

B. Installation: Installing and bringing the system to operational status requires the following major steps: ... 2

.4 SUBMITTALS... 3

A. Product Data:... 3

B. Shop Drawings: ... 3

C. One Line Diagram:... 3

D. Product Data:... 3

E. Contract Close-out Submittals: ... 3

F. As-Built Drawings: ... 4 G. Operator’s Manual: ... 4 .5 QUALITY ASSURANCE ... 4 A. Manufacturer: ... 4 B. NexWatch Dealer: ... 4 C. System Checkout: ... 4 D. Regulatory Requirements:... 4

E. Security Management system computer workstations:... 4

.6 WARRANTY... 5

A. Security Management system software: ... 5

B. Access control system components: ... 5

C. ID Credentials: ... 5 D. Computer workstation:... 5 E. Extended warranty: ... 5 F. Systems Integrator: ... 5 PART II PRODUCTS... 5 .1 Manufacturer... 5

A. NexWatch 47102 Mission Falls Court Fremont, CA 47102 Telephone: 510/360-7800 Web Site: http://www.NexWatch.com ... 5

.2 Security Management System... 5

A. NexSentry Manager Security Management System Compatible Hardware:... 5

B. NexSentry Manager Security Management System Software Platform: ... 7

C. Software Operation: NexSentry Manager shall be easy to learn and simple to use, while performing complex access control, security management and reporting functions. System shall fulfill the following requirements for operator monitoring and command functions:... 9

D. Other Common Requirements: ... 21

E. Accessories: ... 22

.3 Access Control System ... 23

A. System Description:... 23

B. Controller (NexSentry Star Series Controllers, Star I and Star II): ... 23

B. [NexSentry UWIU Plus: 4-port Wiegand interface with MIRO 8/4 Monitor Input/Relay Output Board: ... 29

(4)

D. [NexSentry MIRO 16/8 Monitor Input/Relay Output Board:... 31

E. [NexSentry MIRO 32/0 (and 64/0) Monitor Input Unit: ... 31

F. [NexSentry MIRO 2/24 Relay Output Unit: ... 32

G. [NexStar High Speed S-NET Multiplexer with RS-232 Conversion: ... 33

.2 Readers... 34

A. [Digital Proximity Reader (DigiReader): ... 34

B. [Magnetic Stripe Pass Through Reader (MSR):... 36

C. [Keypad (4200K, 4205K): ... 37

.3 Credentials ... 38

A. [QuadraKey Digital Proximity Card:... 38

B. [NexKey Digital Proximity Badge:... 38

C. [KeyMate Proximity Key Fob, Radio Frequency Identification (RFID tag): ... 39

D. [2-Smart Digital Proximity / Smart Card: ... 39

E. [Magnetic Stripe Card — ISO/ABA format: ... 40

.4 Power... 41

A. Power Supply (PI-1) Power Inserter: ... 41

.5 Accessories: ... 41 A. [Terminal: ... 41 B. [Printer:... 42 C. [Modem: ... 42 D. [Locking Hardware:... 42 E. [Switches: ... 42

F. [External UPS batteries: ... 42

PART II EXECUTION... 42

.1 Installation ... 42

A. General:... 42

B. Schedules: ... 42

C. Telephone Lines: ... 43

D. Field Quality Control:... 43

E. Documentation: ... 44

.2 SERVICE AND SUPPORT ... 44

A. Startup: ... 44

B. Training: ... 44

C. Warranty Support: ... 44

(5)

NexSentry Star I Controller

Hardware features summary

Version

2.37 or higher

Number of readers

2 standard, 4 or 8 with personality chip

Card Technology

- Digital Proximity

- Keypad

- Magnetic Stripe

-

Wiegand Reader-to-Controller protocol

Microprocessor

32-bit Intel industrial microprocessor

Host Communications Protocol

SEEP (Security Electronics Enhanced Protocol)

Terminal Communications Protocol

ASCII Text interface on ANSI standard Terminal

Database:

Card holders without names

50,000

Card holders with names

25,000 (Stand-Alone only)

Event Report Schedules

32

Access Codes

120

Time intervals

128

User-definable holidays

30

Transaction Buffers

100 for terminal port; 5,000 for host port

Hardware:

Monitor Inputs

16 on board, 32 maximum

Relay Outputs, Lock and Auxiliary

Operator Interface Methods

- Terminal: 1 RS-232

- Host: 1 RS-232 1- RS-485 or 1 Micro CoBox Ethernet

Communications to MIROs, Keypads and Readers

- 4 S-NET (RS-485) Ports

Specifications:

Regulatory Approval

-

FCC, UL-1012, CSA, UL 294

Environmental

-

Humidity: 0% to 90% non-condensing

Temperature:

20° to +120° F

(-7° to +49° C)

-

(6)

NexSentry Star II Controller

Version 3.0

Number of readers

2 standard, 4, 8 or 16 with personality chip

Card Technology

- Digital Proximity

- Keypad

- Magnetic Stripe

-

Microprocessor

32-bit Intel industrial microprocessor

Host / Terminal Communications Protocol

CHIP (Controller-Host Interface Protocol)

Database:

Card holders without names

100,000

Event Report Schedules

64

Access Codes

120

Time intervals

128

User-definable holidays

30

Transaction Buffers

100 for terminal port; 5,000 for host port

Hardware:

Monitor Inputs

Relay Outputs, Lock and Auxiliary

4 on board, 96 maximum

Operator Interface Methods

- Terminal: 1 RS-232

- Host: 1 RS-232 1- RS-485 or 1 Micro CoBox Ethernet

Communications to MIROs, Keypads and Readers

- 4 S-NET (RS-485) Ports

Specifications:

Regulatory Approval

-

FCC, UL-1012, CSA, UL 294

Environmental

-

Humidity: 0% to 90% non-condensing Temperature:

20° to +120° F

(-7° to +49° C)

(7)

NexSentry Input/Output (MIRO) Modules

UWIU Plus with MIRO 4/8/4:

Wiegand reader-to-controller protocol readers

4

Monitor Inputs

8

Relay outputs

4

S-NET Communications

2 S-NET (RS-485) connectors

MIRO 4/2:

Monitor Inputs

4

Relay outputs

2

MIRO 16/8:

Monitor Inputs

16

Relay outputs

8

MIRO 32/0:

Monitor Inputs

32

Relay outputs

0

MIRO 64/0:

Monitor Inputs

64

Relay outputs

0

MIRO 2/24:

Monitor Inputs

2

Relay outputs

24

(8)

NexSentry Manager Security Management System

Features Summary

Version

3.0 (2.2 for selected localization)

Summary

NexSentry Manager is a Microsoft Windows NT 4 based

multi-user, multi-site capable security management

system software package designed to manage access and

security solutions for small to medium-sized applications

with entry level to intermediate levels of complexity.

Architecture

Windows NT 4 Client/Server w/ NT 4 Clients

Controller support:

Star II Controller – 2, 4, 8 and 16

Reader

versions

Yes

Star I Controller – 2, 4 and 8

Reader

versions

Yes

NexSentry 4100 Series – 2, 4 and 8 Reader Versions

Yes

Alto 818SC Controller – 8 Readers

Yes

Technology support:

Digital Proximity

Yes

Analog Proximity

Yes

Keypad Yes

Magnetic Stripe

Yes

Smart Card

Yes

Biometrics Yes

Access control:

Clients

2, 4 or 8

Controllers

Up to 32

Card readers

16, 32, 64, 128, 256

Cardholders 100,000

1

Time Groups

128

Time Periods

128

Holidays 30

Access codes

120

On-line Transaction storage

250,000

Off-line Transaction storage

unlimited

Alarm Monitoring:

Monitor Points

8160

1

Output Relays

3072

1

Zones – Logical/ACU (Star II only)

100/480

Reporting & Operating:

Operators/Passwords 100

Operator Instructions

500

Floor Plan Maps

100

1

May be limited by controller types used. See controller specifications for limits that may prevent security management system from having full functionality.

(9)

Additional Features:

BMP Map Import

Yes

Graphical User Interface

Yes

Access Control

Yes

System and Activity Monitoring

Yes

Database Management

Yes

Database Reporting

Yes

Maps Yes

Status and Overrides

Yes

Custom Cardholder PIN

Yes

User-Definable Custom Cardholder Fields

Yes

Optional Modules

-NexSentry Imaging Solutions

1

May be limited by controller. See controller specifications for limits that may prevent security management system from having full functionality.

(10)

(11)

PART I GENERAL

.1 INTRODUCTION

A. Complete system proposal:

1. This document provides the information necessary to produce a complete proposal for a highly secure and dependable access control and security management system that provides the speed and flexibility of 32-bit multiple-technology controllers, and that can be managed by a client/server Security Management System using an intuitive graphical user interface running on the Microsoft Windows NT 4 operating system.

B. General services: 1. Access control 2. Alarm monitoring 3. Reporting

4. Security office management 5. Employee management 6. Maps

.2 SYSTEM DESCRIPTION

A. Security Management System requirements: Required access control and security management system software shall: 1. Be powerful and multi-functional with the ability to expand as project needs grow.

2. Be a 32-bit native Microsoft Windows NT 4 application with multi-user and multi-tasking capability, allowing independent activities and monitoring to occur simultaneously at different locations.

3. Be simple and economical enough to support a single site, but powerful and flexible enough to manage a multiple-site network from a single server location or from up to eight remote client locations, as allowed by the System Administrator (Administrator).

4. Be easy to use, employing intuitive graphical user interface and simple pull-down menus that conform to interface guidelines defined by Microsoft Corporation.

5. Allow for language localization.

6. Have a multi-threaded/multi-platform design that allows system to do multiple functions simultaneously.

7. Allow ODBC database access and conforms to standard networking protocols, including: TCP/IP, PPP, IPX/SPX, and NETBIOS.

8. Operate in a client/server configuration on high-quality Microsoft Windows NT 4 hardware platforms with powerful Pentium processors.

9. Easily accommodate addition of Controllers and doors while maintaining maximum performance.

10. Be designed to control NexWatch third and fourth-generation security architecture, including full support for the following Controllers: NexSentry Star II, Star I, 4100 Series and Alto 818SC controllers.

11. Provide all objects within System with ID numbers and descriptions. Hardware address shall be connected to ID numbers when the hardware is configured in NexSentry Manager. Hardware ID numbers shall be unique, and point numbering and mnemonics shall not be used.

12. Provide other database objects (such as Instructions, Time Codes, Holidays, etc.) with unique ID numbers for each type of object. But, differing objects may have identical ID numbers. For instance, only one Time Code shall have the ID number “1”; it shall be allowed to have both a Time Code and a Time Group with ID number “1”.

B. Computer Hardware:

1. Server PC shall be a powerful Microsoft Windows NT 4 capable PC with a Pentium processor. Hardware specifications are defined in PART II.2.A.

(12)

2. Client PC shall be a powerful Microsoft Windows NT 4 capable PC with a Pentium processor. Hardware specifications are defined in PART II.2.B.

C. Access Control System: Access control system shall: 1. Monitor and control access to areas defined herein.

2. Be capable of supporting multiple access control technologies at each door, as well as alarm inputs and control outputs. 3. Consist of the following major components:

a. A microprocessor based controller. b. Readers:

(Select reader type, or combination of reader types from following list)

1) [Digital proximity readers.]

2) [Digital proximity readers with integrated keypad.] 3) [Keypad readers.]

4) [Magnetic stripe readers.]

5) [Magnetic stripe readers with integrated keypad] 6) [Wiegand reader-to-controller protocol readers.] c. [Security Management System software.]

4. Be capable of operating with or without Security Management System software station. 5. Allow specific types of devices and their functions to be addressed in relevant sections. 6. System shall be capable of being wired to support a Wiegand physical interface. .3 DESCRIPTION OF WORK

A. General:

1. The NexWatch Dealer shall include all necessary labor, tools, equipment, and ancillary materials required to furnish and install a complete and operational access control and security management system.

2. NexWatch Dealer shall coordinate with the customer to supply the Windows NT server/network on system with greater than 2 clients.

3. The access control and security management system will manage access to [building] [and] [selected areas] using [encoded cards,] [and/or coded keypads] [and/or magnetic stripe cards].

4. Requirements are indicated elsewhere in these specifications for work including, but not limited to, raceways and electrical boxes and fittings required for installation of control equipment and wiring: not the work of this section.

5. The extent of access control and security management system work is defined to include, but not by way of limitation: a. [_____ NexSentry Manager Client/Server Stations.]

b. [_____ NexSentry Manager Client stations.] c. [_____ Wall mounted central controllers.]

d. [_____ External keyboard and printer (directly or via central Security Management System).] e. [_____ Digital proximity card Readers.]

f. [_____ Wiegand reader-to-controller protocol Readers.] g. [_____ Keypads.]

h. [_____ Magnetic stripe readers.]

i. [_____ Monitor input/relay output (MIRO) modules.]

j. [_____Wiring, power supplies, switches and ancillary equipment.]

B. Installation: Installing and bringing the system to operational status requires the following major steps: 1. Determine operational requirements and plan software to implement them.

(13)

2. Select computer sites.

3. Install and configure, where necessary, the communications network providing communications between the client and server computer workstations.

4. Install and integrate access control, alarm monitoring, security management and related hardware. 5. Configure NexSentry Controllers and NexSentry Manager to communicate with one another. 6. Enter data into the security system database.

7. Connect between Security Management System, Controllers, readers and related hardware. 8. Test security system communications and operation, including additional terminals as required. 9. Train operators.

10. Secure software maintenance contract from NexWatch Customer Service. .4 SUBMITTALS

A. Product Data:

1. Submit for prior approval, [__________] copies of manufacturer’s data on digital proximity or magnetic stripe access control system and components.

B. Shop Drawings:

1. Submittals shall include drawings detailing all connected devices. This document shall be adequate to ensure that all parties involved can determine that the recommended software meets security system requirements. These shop drawings shall include the following:

a. All system device locations indicated on architectural floor plans. No other system(s) shall be included on these plans. b. Full schematic wiring information on drawings for all devices. Wiring information shall include cable type, conductor

routings, quantities, and connection details at devices. c. A complete access control system diagram.

d. A statement of the system sequence operation. C. One Line Diagram:

1. NexWatch Dealer shall submit a diagram of the system configuration proposed if it differs from that illustrated in the riser diagram included in these specifications.

2. Submittals indicating typical riser diagrams are not acceptable. D. Product Data:

1. NexWatch Dealer shall provide complete product data, which includes the following:

a. Manufacturer’s data for all material and equipment, including terminal devices, local processors, computer equipment, access cards, and other equipment required for the complete access control and security management system.

b. A system description, including analysis and calculations used in sizing equipment required by the access control and security management system. Description to show how the equipment will work as a system to meet performance requirements.

c. A description of the operating system and application software. E. Contract Close-out Submittals:

1. NexWatch Dealer shall provide manufacturer-produced manuals including: a. Operating instructions.

b. Maintenance recommendations.

(14)

F. As-Built Drawings:

1. During system installation, NexWatch Dealer shall maintain a separate hard copy set of drawings, elementary diagrams, and wiring diagrams of the access control and security management system to be used for record drawings.

2. This set shall be accurately kept up to date by the NexWatch Dealer with all changes and additions to the access control and security management system.

G. Operator’s Manual:

1. NexWatch Dealer shall submit for prior approval, [__________] copies of manufacturer’s manual for programming and operating the Access Control and Security Management System systems and their related components.

.5 QUALITY ASSURANCE

A. Manufacturer:

1. Manufacturer of products defined in this section must have:

a. Industry experience: Company must have at least 25 years experience in manufacturing and servicing access control and security management systems.

b. ISO 9001 Certification: Manufacturing process of company must meet stringent standards of ISO 9001 Certification. B. NexWatch Dealer:

1. The NexWatch Dealer shall:

a. Be a local representative and factory-authorized local service organization for NexWatch.

b. Have been regularly engaged in the installation and maintenance of integrated access control and security management systems for no less than [enter time in business].

c. Be an authorized product Dealer for NexWatch integrated electronic access control and security management systems.

d. Be able to provide certification proving their installation and service technicians are competent, factory-trained personnel capable of installing and maintaining the system.

C. System Checkout:

1. Pre-testing: All components and assemblies of the Controller[s], readers and other hardware components are to be pre-tested at the factory prior to shipment.

2. On-site testing: Manufacturer-trained and authorized NexWatch Dealer shall functionally test each component in the system after installation to verify proper operation and confirm that the panel wiring and addressing conform to the wiring documentation.

3. Service facility: NexWatch Dealer shall have service facilities within [_____] miles of the installation. D. Regulatory Requirements:

1. NEC Compliance: All electrical wiring work shall comply with NEC.

2. NEMA Compliance: Electrical equipment shall comply with applicable portions of NEMA. 3. FCC Emissions: All assemblies shall be in compliance with FCC emission standards.

a. Microprocessor-based controller: Part 15, Subpart F, Class A. b. Digital proximity card-reading sensors: Part 15, Subpart F. c. Dial-up modems: Part 68.

4. UL-1012 and CSA: All power supplies shall be in compliance with Underwriters Laboratories standard 1012 and CSA standards for power supplies.

E. Security Management system computer workstations:

1. If NexSentry Manager is bundled with a DELL PC workstation or approved alternative, hardware shall meet UL and FCC requirements for class A computing devices.

(15)

.6 WARRANTY

A. Security Management system software:

1. The manufacturer shall support software for the selected system product family. B. Access control system components:

1. 15 (fifteen) months from shipment date or 12 (twelve) months from date of purchase by NexWatch Dealer, whichever comes first.

C. ID Credentials:

1. No less than 1 (one) year. D. Computer workstation:

1. If NexSentry Manager is purchased with computer hardware, hardware shall be warranted for at least 15 months from the date of shipment from the factory. The manufacturer shall support hardware repair for the system through Dell’s

worldwide service organization. E. Extended warranty:

1. Extended warranty terms at reasonable rates shall be available from the installing NexWatch Dealer. F. Systems Integrator:

1. NexWatch Dealer shall be the focal point of all service problems or questions (with manufacturer’s full support).

PART II PRODUCTS

.1 MANUFACTURER A. NexWatch

47102 Mission Falls Court Fremont, CA 47102 Telephone: 510/360-7800

Web Site: http://www.NexWatch.com .2 SECURITY MANAGEMENT SYSTEM

A. NexSentry Manager Security Management System Compatible Hardware:

1. Server/Client Configuration:

a. General:

1) The server/client CPU shall be a 100% IBM compatible PC approved by Microsoft Corporation for running the Microsoft Windows NT 4 operating system or higher (Microsoft posts compatible hardware on the Internet at:

ftp.microsoft.com/bussys/winnt/winnt-docs/hcl). b. CPU Requirements:

1) Processor: Pentium 200 MHz recommended. 2) Operating System: Microsoft Windows NT 4 or later. 3) RAM:128 MB minimum, 256 MB recommended. 4) Hard Disk: 750 MB free space.

5) 3.5 inch Floppy Drive: required.

6) Sound Card: required for sound operations; not required for system operation. 7) CD-ROM: required.

8) Modem (9600 baud +): required for over-the-phone technical assistance from manufacturer; not required for system operation.

(16)

9) Super VGA Video: required.

10) Tape / ZIP / Jaz / CD-RW Backup: recommended but not required for system operation. 11) RS232 Ports: 2 minimum.

12) Printer: required for transaction hard copy; not required for system operation. 2. [Client Workstation Configuration:

a. General:

1) The client CPU shall be a 100% IBM compatible PC approved by Microsoft Corporation for running the Microsoft Windows NT 4 operating system or higher (Microsoft posts compatible hardware on the Internet at:

ftp.microsoft.com/bussys/winnt/winnt-docs/hcl). b. CPU Requirements:

1) Processor: Pentium 200 MHz recommended. 2) Operating System: Microsoft Windows NT 4 or later. 3) RAM: 32MB recommended.

4) Hard Disk: 540 MB free space. 5) 3.5 inch Floppy Drive: required.

6) Sound Card: required for sound operations; not required for system operation. 7) CD ROM: required.

8) Modem (9600 baud +): required for over-the-phone technical assistance from manufacturer; not required for system operation.

9) Super VGA Video: required.

10) Tape Backup: recommended but not required for system operation.

11) RS232 Port: not required; client/server and server workstations must be connected by LAN. 12) Printer: required for transaction hard copy; not required for system operation.]

3. Compatible Access Control and Security Management Hardware:

a. Controllers:

1) NexSentry Star II Controllers 2) NexSentry Star I Controllers 3) NexSentry 4100 Series Controllers. 4) Alto 818SC Controller.

b. Readers:

1) DigiReader Series digital proximity readers. 2) MSR 42 magnetic stripe readers.

3) MSRK 42 combination magnetic stripe reader with keypad. 4) 4200K or VIP-2 Series keypad.

5) SE 2800 Series analog proximity sensors (818SC Only).

c. Cards:

1) QuadraKey multiple-technology proximity card. 2) NexKey digital proximity badge.

3) KeyMate digital proximity key fob. 4) ABA magnetic stripe card.

5) SE 1030, SE 1040, SE 1050, SE 1060 analog proximity cards. d. High Speed NexStar RS-485 / RS-232 Multiplexer

(17)

e. CI-1 & CI-8 Multiplexers:

1) The system may require one or more CI-1 or CI-8 multiplexers to allow the integration of up to 32 remote distributed intelligence NexWatch Controllers into a multi-location network.

f. Communication Interface:

1) Controllers shall connect directly to the server workstation RS232 serial ports.

2) Optionally, controllers shall connect to the Server workstation via Dial-Up Modem communication. 3) Optionally, controllers shall connect to the Server workstation via CoBox Ethernet communication. g. Printer:

1) All Microsoft Windows NT supported printers.

B. NexSentry Manager Security Management System Software Platform:

1. Operating System: Microsoft Windows NT 4. 2. Capacities:

a. NexSentry Manager shall be a 32-bit access control and security management system that conforms to the programming and interface guidelines defined by Microsoft Corporation for Microsoft Windows NT 4 compatible software.

b. This shall allow NexSentry Manager to take full advantage of these and other features inherent in the Microsoft Windows NT 4 operating system:

1) Multi-user/multi-tasking operation on an open architecture system.

2) Less costly language localization where language is supported by Microsoft Windows NT 4. 3) SQL compliant with ODBC support.

4) Support for most standard networking protocols, including: TCP/IP, PPP, IPX/SPX and NETBIOS. 5) 32-bit multi-threading.

6) Graphical user interface, pull-down menus, mouse, and keyboard control. c. Basic Functions:

1) Access control.

2) System and activity monitoring. 3) Database management. 4) Database reporting. 5) Maps.

6) Status and overrides.

d. Access Control: NexSentry Manager shall be configured with the following standard features: 1) Multiple technology support:

(i) NexSentry Manager shall provide multiple technology support in a single system, including full support for the following technologies: digital proximity, analog proximity, magnetic stripe, keypad, Wiegand reader-to-controller protocol Readers and smart card Readers.

(ii) Multiple technology support may be limited by technology supported by Controllers used in access control and security management system. Following are the Controllers supported by NexSentry Manager with a list of the technologies supported by each Controller:

(a) NexSentry Star II Controllers: Digital proximity, keypad, magnetic stripe, and 26- and 32-bit Wiegand. (b) NexSentry Star I Controllers: Digital proximity, keypad, magnetic stripe, and 26- and 32-bit Wiegand. (c) NexSentry 4100 Series Controller: Digital proximity, keypad, magnetic stripe, and 26- and 32-bit

Wiegand.

(d) Alto 818SC: Digital proximity, analog proximity, keypad, and smart card. 2) Controllers: up to 32.

(18)

4) Card readers: 256 maximum. 5) Cardholder records: 100,000.

(i) May be limited by Controller. See Controller specifications for limits that may prevent system from having capabilities built into NexSentry Manager system software.

6) Time groups:128. 7) Time Codes:128.

8) Holidays:30

9) Access codes:120.

e. Alarm Monitoring:

1) Monitor points: 8,160, maximum.

(i) May be limited by Controller. See Controller specifications for limits that may prevent a complete system from having total capabilities built into NexSentry Manager system software.

2) Zones: 100 maximum.

(i) May be limited by Controller. See Controller specifications for limits that may prevent a complete system from having total capabilities built into NexSentry Manager system software.

3) Visual and audible alarms: audible alarm annunciation with user-definable sounds.

f. Database Management:

1) Cardholder data fields: 31 total.

2) User-definable custom cardholder text fields: 8 (eight). 3) User-definable custom cardholder look-up fields: 6 (six). 4) Custom cardholder PIN number:

(i) 4100 series, Star I and Star II Controllers shall be capable of accepting a user-selected PIN Number for each cardholder. This PIN Number shall be independent of any Card Number, and not altered if the associated Card number must be changed.

(ii) 818SC, 4100 series and Star I Controller shall be capable of generating Personal Identification Numbers (PIN) for each cardholder.

(iii) 818SC, 4100 series and Star I: PIN field shall be descriptive only.

(iv) 818SC, 4100 series and Star I: By using the same PIN seed on all Controllers, the assigned PIN shall work for the cardholder at every Controller and Door.

5) Cardholder access privilege activation and expiration date.

6) On-line transaction storage: limited only by hard disk space. 7) Off-line transaction storage: unlimited.

g. Reporting and Operating:

1) Operator passwords: 100. 2) Operator instructions: 500. 3) Reports: 100.

h. Maps:

1) Graphical maps: NexSentry Manager shall allow import and use of bitmap graphics created in CAD/CAM, drawing, painting, and other common graphics programs.

(19)

2) Operator-defined color floor plan maps: 100. i. Dial-Up remote diagnostics:

C. Software Operation: NexSentry Manager shall be easy to learn and simple to use, while performing complex access control, security management and reporting functions. System shall fulfill the following requirements for operator monitoring and command functions:

1. User interface: The required software shall provide a sophisticated, easy-to-operate graphical interface for security operators. Multiple aspects of the system shall contribute to the effectiveness of the operator interface:

a. Interface shall be localized in [English] [French] and [German] languages. Other languages can be translated on special request.

b. Icon-based graphical user interface configurable by user and definable by zones.

c. Menu-driven screen selection with audiovisual messages and warnings shall allow even an infrequent operator to move through and manage the functions of the system easily and with minimal training. There shall be no need to memorize complicated commands or procedures.

d. Mouse or key control.

e. Interactive on-line help with extensive on-line manual.

f. Language localization allows the same ease of use for international customers.

g. Items shall be displayed and features shall be available based on the current operator’s security level.

2. Help: System shall provide multiple levels of help to facilitate navigation through and operation of NexSentry Manager. The following levels of help shall be available:

a. Interactive help: Help phrases shall automatically appear in Help window at bottom of display screen, in Help line of entry windows, and over graphical icons.

b. On-screen help: Each data entry screen shall contain a one-line help message, which will be content sensitive to the field where the cursor is located. This help message shall provide a brief message to inform Operator as to the task, which can be performed on that field.

c. On-line help through Help icon: Detailed help from an on line manual shall be available by selecting the interactive Help icon then clicking on the item with which the operator needs help. The screen shall contain detailed information that will allow the operator to perform correct actions without having to consult a manual.

d. Interactive manual with hypertext links: An on-line manual shall be available to allow the operator to obtain detailed help without having to consult a manual. The on-line manual shall be easily available under the Help menu. The Help menu will provide an index which includes Contents, Index, and a Find engine which allows operator to perform simple and complex word or phrase searches to assist the operator in finding the necessary help. Hypertext lines shall be used throughout the on-line manual to guide operator through related help features.

3. Data entry: Data entry screens comprised of tabbed dialogs containing multiple pages shall provide the means for configuring NexSentry Manager.

4. Hardware configuration:

a. Pollers:

1) The Pollers database shall provide a means by which a system operator can specify towhich computer communication ports the Controllers are connected.

2) NexSentry Manager shall require a Poller Entry for each communication port to which Controllersareattached. 3) The Poller database shall allow Administrator define the following:

(i) ID: 9-digit identifier.

(ii) Description: 30-character identifier. (iii) Instruction.

(iv) Activity reporting times.

(v) Port.

(vi) Baud: 300, 1200, 2400, 4800, 9600, 19200, 38400, 52600, 115200. (vii) Acknowledge Time-out.

(viii)Retries.

(20)

(x) .Dial-Up Modem parameters

b. Access Control Units: The Access Control Units database shall allow system operator to define a Controller to the system with the following:

1) Controller type:

(i) NexSentry Star II Controllers (ii) NexSentry Star I Controllers (iii) NexSentry 4100 Controller. (iv) 818SC Controller. 2) General:

(i) ID: System shall automatically define a unique ID for each Controller. Administrator shall be able to override ACU ID assigned by system.

(ii) Description: System shall allow Administrator to enter a unique description for each Controller. (iii) Address: System shall allow Administrator to enter a unique address for each Controller. (iv) Shunt: Check or Uncheck.

(v) Poller ID: System shall allow Administrator to select pre-defined Poller ID, or define new Poller ID from “General” without leaving Access Control Units entry screen.

(vi) Instruction ID: System shall allow Administrator to define instructions for alarms that specifically refer to the Controller being defined. Administrator shall be able to select pre-defined Instruction ID or create a new Instruction ID without having to leave Access Control Units entry screen.

(vii) Minutes between “Building not closed” reminder messages.

3) Time Groups: Administrator shall be able to select user pre-defined Time Groups or define new Time Groups without having to exit Access Control Unit database:

(i) Building / Zone Should be Closed times. (ii) Auto Forgive times.

(iii) Show Activity times.

4) VIP: Administrator shall be able to define limitations on cardholder PIN codes: (i) Number of PIN Retries allowed.

(ii) Number of Digits.

(iii) Number of Digits if using VIP only. (iv) PIN Seed.

(v) Grace period. (vi) Display PIN number. (vii) Duress enable.

5) Actions: Administrator shall be able to define the actions to take place in case of the following user-definable fields:

(i) Operator override. (ii) Duress.

(iii) Tamper. (iv) Power fail. 6) Cards:

(i) Digital: NexKey, QuadraKey, KeyMate. (ii) Magnetic stripe.

(iii) Smart card.

(iv) Analog proximity: SE 1030, SE 1040, SE 1050, SE 1060.

(v) Facility code: System shall allow Administrator to select pre-defined Facility Code or Create New Code without having to leave Controller entry screen. Facility Code shall be entered only for those custom-made cards that require it, i.e., SE 1030 and SE 1040.

(21)

7) Reader: System shall allow Administrator to accept pre-defined defaults for readers or to configure the following:

(i) Verification sweeps. (ii) Access denied time. (iii) Misread filter. (iv) Reread delay.

8) Misc.: Administrator shall be able to define the following miscellaneous items for each Controller: (i) Security Management System connection.

(ii) Terminal connection.

9) For Star II Controllers; Available and Selected Actions and Action Groups: Star II Controllers require separately configured Actions and Action Groups. A dialog box allows selection of any or all available Actions and Groups to be used with each Star II Controller.

c. Doors: System shall allow Administrator to define each door with the following parameters: 1) General:

(i) ID: System shall allow Administrator to define a unique number for each door. Administrator shall be able to override ID assigned by system.

(ii) Description: User-definable name for the door.

(iii) Shunt: Selecting Shunt shall cause the system to ignore all transactions relating to the door.

(iv) ACU ID: System shall allow Administrator to designate Controller to which the door is connected. Select pre-defined Controller, or define new Controller without leaving Door database.

(v) Sensor Number.

2) Time Groups: System shall allow Administrator to select user-defined Time Groups or to define new Time Groups without having to exit Door database:

(i) Auto Unlock: Define the times that door will automatically unlock.

(ii) Show Activity: Define the time period during which activity from door shall be reported. 3) Lock: Administrator shall be able to define the following:

(i) Use Door Switch: Check or Uncheck to allow or disallow editing of the door switch parameters.

(ii) Contact Point: Select user definable Contact Point to define input record that represents the switch for the door. In addition, System shall allow Administrator to define new Contact Point without leaving Door database.

(iii) Maximum door open time: Enter amount. (iv) Read cards when open: Check or Uncheck. (v) Unlock time: Enter amount.

(vi) Reverse lock: Check or Uncheck.

4) Proximity Reader: Administrator shall be able to configure the reader as follows:

(i) Enable: Check or Uncheck to determine whether proximity reader is being used at the door. (ii) Type: Define Digital, Analog, or Smart Card Reader.

(iii) Used as: Define whether a reader is being used to grant access or if it is being used for building mode operation.

(iv) Disable MSM: Check or Uncheck. (v) Configure Digital Reader:

(vi) Setup: Read range, Verification time window, Forward digit code, Number of verifies. (vii) Beeper timing: On, Off, Cycles.

(viii)Red LED timing: On, Off, Cycles. (ix) Green LED timing: On, Off, Cycles.

5) VIP: Administrator shall be able to define VIP as follows: (i) Enable: Check, Uncheck.

(22)

(iii) For Star II Controllers: Activate during these Zone Modes: Armed, Disarmed, Shunted, Disabled, Monitored..

(iv) Activate during this Time Group: Select pre-defined Time Group, or select Option to create new Time Group without leaving Door database.

6) REX: Administrator shall be able to define Request to Exit points (REX) as follows: (i) Enable REX: Check or Uncheck

(ii) Contact Point: Select user-defined Contact Point or select option to define new Contact Point without leaving Door database.

(iii) Valid REX Time Group: Select user-defined Valid REX Time Group or select option to define new Time group without leaving Door database.

(iv) Unlock on REX: Check or Uncheck.

7) Misc.: Administrator shall be able to define the following miscellaneous items for each door: (i) Enable Anti-Passback: Check or Uncheck.

(ii) Anti-Passback Method: Hard/Soft. (iii) Anti-Passback Type: Entry/Exit.

(iv) For Star II Controller, Select Entering and Leaving Zones.

(v) Instruction: Select instruction that should be displayed if an alarm occurs relating to this door from pre-defined instruction list, or select option to define new Instruction without leaving Door database.

(vi) Action Group: Select Actions that should be downloaded for door to the Controller from pre-defined list or select option to define new Action Group without leaving Door database.

d. General Purpose Input: Administrator shall be able to define the following for each General Purpose Input: 1) General:

(i) ID: System shall assign a unique ID to each Input or shall allow Administrator to override ID assigned by system.

(ii) Description: System shall allow Administrator to enter custom name for the input.

(iii) Instruction ID: System shall allow Administrator to define instructions for alarms that specifically refer to the Controller being defined. Administrator shall be able to select pre-defined Instruction or create a new Instruction without having to exit General Purpose Input database.

(iv) Action ID: System shall allow Administrator to define Action ID by selecting pre-defined Action ID or create a new Action ID without having to exit General Purpose Input database.

2) Connection:

(i) Controller: System shall allow Administrator to select pre-defined Controller or select option to define a new Controller without having to exit General Purpose Input database.

(ii) Controller Port: System shall allow Administrator to select Controller Port from pre-defined list. (iii) Contact Number: System shall allow Administrator to select Contact Number from pre-defined list. (iv) Shunted: Check or Uncheck.

e. Output: Administrator shall be able to use the Outputs dialog to define the outputs on the Controller to the system, as follows:

1) General:

(i) ID: System shall allow Administrator to accept a system-defined ID used to identify the output or to override system-defined ID by entering a unique number with up to 9 digits.

(ii) Description: System shall allow Administrator to define name for the Output.

(iii) Instruction ID: System shall allow Administrator to define instructions for alarms related to Output point. Administrator shall be able to select pre-defined Instruction ID from list or select option to create new Instruction ID without exiting Output dialogue.

(iv) Show activity time: System shall allow Administrator to select defined Activity Times from pre-defined list, or select option to create new Activity Time without exiting Output dialogue.

2) Connection:

(i) ACU: System shall allow Administrator to select Controller to which Output is connected from pre-defined list, or select option to define new Controller without exiting Output dialogue.

(23)

(ii) ACU Port: System shall allow Administrator to select Controller Port from pre-defined list. (iii) Contact Number: Select from pre-defined list.

(iv) Shunted: Check or Uncheck.

f. Instructions: System shall allow Administrator to define instructions that will appear when an alarm occurs, as follows:

1) ID: System shall allow Administrator to accept a system-defined ID or to override system-defined ID by entering a unique number with up to 9 digits.

2) Description: System shall allow Administrator to select a pre-defined name for the Instruction.

3) Instruction: System shall allow Administrator to define text that shall appear to instruct Operator what to do when an alarm occurs.

g. Zones: System shall provide ability to group hardware (points) into zones. This shall allow points to have operations applied to them as a unit. Administrator shall define zones as follows:

1) ID: System shall automatically assign unique Zone ID. Administrator shall be able to override system-assigned Zone ID with unique 9-digit ID.

2) Description: User-definable name for Zone.

3) Defined Points: System shall display a list of all defined points.

4) Selected Points: Administrator shall define points to Zone by selecting points from Defined Points list. 5. Personnel configuration:

a. Cardholder: Administrator shall be able to define cardholders as follows: 1) General:

(i) Cardholder ID: System shall automatically assign a unique Cardholder ID. Administrator shall be able to override system-assigned Cardholder ID with unique 9-digit ID.

(ii) Name: First Name, Last Name. 2) Access:

(i) Access options: Trace, Visitor, Privileged. (ii) Dates: Start, Stop.

(iii) Active Times: Select Active Times from pre-defined list or select option to create new Active Time without exiting Cardholders.

(iv) Access Code: Select Access Code to be assigned to cardholder from pre-defined list, or select option to create new Access Code without exiting Cardholders.

(v) For Star II Controllers: Elevator Access Code: Select Access Code to be assigned to cardholder from pre-defined list, or select option to create new Elevator Access Code without exiting Cardholders. 3) Credentials:

(i) Card type: Select Card Type from pre-defined list.

(ii) Facility code: Select facility code from pre-defined list, if using 1030 or 1040 analog command key. (iii) 818SC PIN: PIN field shall be descriptive only. Controller shall generate PINs independently. By using the

same PIN seed on all Controllers, the assigned PIN shall work for the cardholder at every Controller and Door.

(iv) 4100 series, Star I and Star II PIN: Each user shall be able to select their own PIN Number. The selected PIN shall work for the cardholder at every Controller and Door where a Keypad is installed.

(v) Card number.

4) Address: Flexible fields for keeping address and telephone number information for cardholder. 5) Additional Text Fields: System shall provide eight (8) user-definable text fields for storing cardholder

information.

6) Additional Lookup Fields: System shall provide six (6) user-definable lookups that can be used by Operator or Administrator to track custom information such as departments, location, or codes. Operator shall be able to use Lookup fields to generate custom reports using any ODBC compliant database application.

(24)

b. Access Codes: System shall provide a convenient mechanism for grouping access privileges together. Administrator must create Access Codes and assign to a cardholder before access can be granted to Cardholder. Access Codes shall consist of groups of Doors and Time Groups. Doors may be assigned without regard to physical connections of the hardware. Doors from any Controller may be combined together to form an Access Code. Administrator shall be able to define Access Codes as follows:

1) ID: System shall automatically assign unique Access Code ID. Administrator shall be able to override system-assigned Access Code ID with unique 9-digit ID.

2) Description: User-definable name for the Access Code.

3) Time Groups: To specify when access will be granted, a Time Groups may be assigned for each door from a pre-defined list, or Administrator shall be able to select option to create new Time Group without exiting Access Code dialogue.

4) Defined Doors: System shall display a list of all defined doors. Administrator shall be able to select option to Create New door without exiting Access Codes.

5) Selected Doors: Administrator shall assign doors to Access Codes by selecting doors from pre-defined Doors list.

c. Elevator Access Codes (Star II Controllers only): System shall provide a convenient mechanism for grouping elevator access privileges together. Administrator must create Elevator Access Codes and assign them to a cardholder before elevator access can be granted to Cardholder. Access Codes shall consist of groups of Elevators and Time Groups. Elevators may be assigned without regard to physical connections of the hardware. Elevators from any Star II Controller may be combined together to form an Elevator Access Code. Administrator shall be able to define Star II Elevator Access Codes as follows:

1) ID: System shall automatically assign unique Access Code ID. Administrator shall be able to override system-assigned Access Code ID with unique 9-digit ID.

2) Description: User-definable name for the Access Code.

3) Time Groups: To specify when access will be granted, a Time Group may be assigned for each elevator from a pre-defined list, or Administrator shall be able to select option to create new Time Group without exiting the Elevator Access Code dialogue.

4) Defined Elevators: System shall display a list of all defined elevators. Administrator shall be able to select option to Create New elevator without exiting Star II Elevator Access Codes.

5) Selected Elevators: Administrator shall assign elevators to Access Codes by selecting doors from pre-defined Elevators list.

6. System Administration configuration:

a. System Users: NexSentry Manager shall require all System Users to be entered with unique identifying information as follows:

1) ID: System shall automatically assign unique User ID. Administrator shall be able to override system-assigned User ID with unique 9-digit ID.

2) Description: A comment field for the Administrator. 3) User name: Log-in name of the operator.

4) User password: Password of the System User, using a password with a combination of up to nine numbers or characters.

5) Security level: System shall allow Administrator to select system-definable access levels.

b. ACU Users: NexSentry Manager shall allow Administrator to authorize direct access to the Controllers by providing the following information:

1) ID: System shall automatically assign unique User ID. Administrator shall be able to override system-assigned User ID with unique 9-digit ID.

2) Description: A comment field for the Administrator. 3) User name: Log-in name of the Controller User.

4) User password: Password of the Controller User, using a password with a combination of up to nine numbers or characters.

(25)

c. Alarm Responses: System shall allow custom entry of Alarm Responses, as follows:

1) ID: System shall automatically assign unique Alarm Response ID. Administrator shall be able to override system-assigned Alarm Response ID with unique 9-digit ID.

2) Alarm Response: Administrator shall be able to enter 30-character description of Alarm Response to instruct Operator what to do in case of an alarm.

3) Remarks: Administrator shall be able to add remarks to the Alarm Response to indicate usual responses to alarms. NexSentry Manager shall allow operator to select a pre-defined response, add to a pre-defined response, or enter a different response.

d. Transactions: System shall provide general on-screen and printed reports of Transaction Logs and Transaction Types.

e. Holidays: Administrator shall be able to define holidays and modify System behavior by combining holidays with Time Codes:

1) Date. 2) Description.

f. Facility Codes: System shall support unique facility codes for use with 1030 and 1040 analog proximity cards as follows:

1) ID: System shall automatically assign unique Facility Code. Administrator shall be able to override system-assigned Facility Code with unique 9-digit ID.

2) Description: A user-definable descriptor. 3) Code.

g. Site Codes: System shall support unique Site Codes for use with ABA magnetic stripe cards, as follows:

1) ID: System shall automatically assign unique Site Code. Administrator shall be able to override system-assigned Site Code with unique 9-digit ID.

2) Description: A user-definable descriptor. 3) Code.

7. Miscellaneous Configuration:

a. Time Codes: Administrator shall be able to create Time Codes which can be assigned to Time Groups, as follows: 1) ID: System shall automatically assign unique Time Code ID. Administrator shall be able to override

system-assigned Time Code ID with a unique 9-digit ID.

2) Description: Administrator shall be able to define a unique descriptive phrase for each Time Code. 3) Active Times:

(i) Start Time. (ii) Stop Time.

(iii) Active Days: Administrator shall be able to select individual days or select options to Check All, Uncheck All, Check Weekdays.

b. Time Groups: System shall offer convenience of grouping Time Codes into Time Groups so up to four Time Codes can be assigned as a group:

1) ID: System shall automatically assign unique Time Group ID. Administrator shall be able to override system-assigned Time Group ID with a unique 9-digit ID.

2) Description: Administrator shall be able to define a unique descriptive phrase for each Time Group. 3) Time Codes: Administrator shall be able to select up to four different Time Codes from pre-defined lists, or

select option to Create New Time Code without exiting Time Groups.

c. Actions: NexSentry Manager shall allow System Administrator to define the Actions that are downloaded to the Controllers, as follows: Star II Actions are distinct from Actions in other ACUs and have slightly different configuration dialog boxes. The program automatically distinguishes between the two distinct types. 1) General:

(i) ID: System shall automatically assign unique ID. Administrator shall be able to override system-assigned ID with unique 9-digit ID.

(26)

(ii) Description: A comment field to describe Action.

(iii) Prevent Controller/Zone Closure: Check to prevent Controller from entering Closed mode when Action is active.

(iv) Print asterisk: Check to print an asterisk with each log transaction.

(v) Send to host: Administrator shall be able to select building modes (Open, Limited, Closed) and Time Group when information regarding the event to which this Action is linked will be sent to the Security Management System.

2) Latched Contact (818SC/4100 series/Star I):

(i) Closed Latch Contact: Administrator shall be able to select Building Modes (Open, Limited and Closed) and the Time Group in which the latched contact will be activated.

(ii) Time Group: Administrator shall be able to select Time Group from pre-defined list, or shall have the option to Create New Time Group without exiting Actions.

3) Regular Contact:

(i) Closed regular contact: Administrator shall be able to select the Building Modes (Open, Limited and Closed) and Time Group when a normal contact will be activated when this Action is active.

(ii) Time Group: Administrator shall be able to select Time Group from pre-defined list, or shall have the option to Create New Time Group without exiting Actions.

d. Action Groups: Administrator shall be able to combine Actions under a single ID that can be assigned to doors as a single unit, as follows: : Star II Action Groups are distinct from Actions in other ACUs and can not be intermixed. The program automatically distinguishes between the two distinct types.

1) General:

(i) ID: System shall automatically assign unique Action Group ID. Administrator shall be able to override system-assigned Action Group ID with unique 9-digit ID.

(ii) Description: Administrator shall be able to define a unique descriptive phrase for each Action Group. (iii) General Actions: Administrator shall be able to select the following General Actions from a pre-defined

list, or select option to Create New General Actions without leaving Action Groups: (a) Key Trace.

(b) Door open too long. (c) Door forced open. (d) Device tamper. (e) ABA card.

2) Access: Administrator shall be able to define the Action Group access and exit actions, as follows: (i) Access Actions:

(a) Access Granted. (b) Access Denied. (ii) Exit Actions:

(a) Exit Granted. (b) Exit Denied.

3) Failure: Administrator shall be able to define the Failure Actions by selecting options from a pre-defined list or by selecting option to Create New Actions without leaving Action Group:

(i) Failure Actions: Including, but not limited to:

(a) Coax. (b) Sensor. (c) MSM. (d) VIP.

(e) S-NET Reader.

e. Holidays: System software shall allow definition of holidays that are considered as additional days of the week and shall have different user-programmable parameters from the normal designations for that day.

(27)

1) Custom sounds: System shall allow import of custom sounds to be assigned to alarms and actions. Sounds shall provide audible sounds that can alert Operator to situations that may occur off screen.

2) Custom icons: System shall allow assignment of custom icons for display in monitoring windows. Such icons shall provide instant visual status of actions and alarms using intuitive graphics to allow Operator to easily assess activities taking place in the system.

3) Custom text: System shall allow custom color assignments to text. Such color shall allow Operator a more intuitive means for assessing system activity. For example, all alarm text can be assigned the color red.

8. System Monitoring and Control: NexSentry Manager shall provide flexible and intuitive ways to monitor and control the activities taking place on the system, as follows:

a. Alarms:

1) General: System shall provide live on-screen status of any active alarm, providing the following information: (i) Description.

(ii) Message. (iii) Point ID Number. (iv) Log Code. (v) Date. (vi) Time.

2) Custom audible alarms: In addition to providing alarm status with text and intuitive graphical icons, NexSentry Manager shall allow custom sounds to be assigned to each alarm type. System operator shall be able to use standard sounds provided by manufacturer or shall be able to create custom sounds for each alarm. 3) Animated alarms: NexSentry Manager shall provide an animated icon to alert Operator to an active alarm. 4) Alarm response: System shall allow Operator to acknowledge an alarm by clicking on alarm in the on-screen

report or by clicking on the animated alarm icon in the Status bar. When acknowledging an alarm, Operator shall have the following options:

(i) Message: System shall provide message describing the alarm.

(ii) Instructions: System shall provide instructions about what Operator should do in the event of Alarm. (iii) Acknowledgment: System shall provide list of pre-defined acknowledgment options from which Operator

can select the response to resolve the alarm.

(iv) Remarks: System shall allow operator to enter detailed remarks about the alarm and the actions taken in response to the alarm.

b. System Monitor:

1) General: System shall provide live on-screen status of all activities taking place on the system, providing the following information about each activity: The visibility, size and position of each column shall be user selectable. Columns available include, but are not limited to:

(i) Description. (ii) Message. (iii) Name.

(iv) Point ID Number. (v) Log Code. (vi) Card Number. (vii) Date.

(viii)Time.

2) On-screen sorting: System shall allow all information displayed in System monitor window to be sorted by activities described in General above. Sorting by activity shall be done by simply selecting the applicable column at the head of the on-screen report; the system shall then organize the activities by that item in ascending or descending order.

c. System Status:

1) General: NexSentry Manager shall provide easy current status of Pollers, Controllers, Doors, Inputs, and Outputs through live, on-screen reports that use text and intuitive graphical icons to describe the status of the hardware. Status windows can be viewed individually or simultaneously while other mapping or monitoring

(28)

windows are opened. Operator shall be able to filter hardware status through pre-defined Zone Filters. System shall allow all information displayed in status windows to be sorted by activities described in General above. Sorting by activity shall be done by simply selecting the applicable column at the head of the on-screen report; the system shall then organize the activities by that item in ascending or descending order.

2) Pollers: System shall display the following live Poller status information: The visibility, size and position of each column shall be user selectable. Columns available include, but are not limited to:

(i) Description. (ii) Point ID Number. (iii) Shunted. (iv) Status.

3) Controllers: System shall display the following live Controller status information in Controller status window: The visibility, size and position of each column shall be user selectable. Columns available include, but are not limited to:

(i) Description. (ii) Point ID Number. (iii) Building Mode. (iv) Should be Closed. (v) Tamper. (vi) Power.

(vii) Communications.

4) Doors: System shall display the following live Door information: The visibility, size and position of each column shall be user selectable. Columns available include, but are not limited to:

(i) Description. (ii) Point ID Number. (iii) Door Forced. (iv) Door Held Open. (v) Shunted. (vi) Unlocked. (vii) MSM. (viii)Coax.

(ix) Analog Reader. (x) Keypad (4200K, VIP). (xi) Keypad (4200 K VIP) Tamper. (xii) Smart Card Reader/DR. (xiii)Smart Card Reader/DR Tamper.

5) Inputs: System shall display the following live Input status information in the Input status window: The visibility, size and position of each column shall be user selectable. Columns available include, but are not limited to:

(i) Description. (ii) Point ID Number. (iii) Shunted. (iv) Active.

6) (Outputs: System shall display the following live Input status information in the Output status window: The visibility, size and position of each column shall be user selectable. Columns available include, but are not limited to:

(i) Description.

(ii) Point ID Number Status. d. Maps:

(29)

1) General: System shall allow visual monitoring of all secure areas using interactive graphic maps that can be generated using bitmap graphics created in Auto Cad or other graphics programs. Administrator shall be able to set up map by simply importing a graphical image of the area to be controlled, then dragging pre-defined icons to the appropriate areas of the image. Operators shall be able to obtain a visual status of a Controller, change the status of a control point, and respond to an alarm through the map.

2) Easy to define maps: Administrator shall be able to create a new map by simply selecting Select Background and importing bitmap images into NexSentry Manager. NexSentry Manager shall support the following formats generated by Auto Cad or other graphics programs:

(i) Windows Bitmaps (.bmp). (ii) JPEG (.jpg).

(iii) GIF (.gif). (iv) PCX (.pcx). (v) TIFF (.tif). (vi) TARGA (.tga). (vii) DIB (.dib).

3) Easy-to-assign control points: Administrator shall be able to add monitor and control points by simply dragging pre-defined Controllers, Doors, Inputs, and Outputs from pre-defined lists.

4) Monitoring and control: System shall provide visual status of any controlled point on a map through icons representing the controlled points. Icons shall provide instant visual status; for example, door icons will display an unlocked lock if the door status is unlocked, or a question mark if door status is unknown. Operator shall be able to change the status of a control point through the applicable icon and to respond to alarms through the map. Through these icons, Operators shall be able to perform the following control functions: The functions available will depend on the type of ACU that is selected. Override and control features available include, but are not limited to:

(i) ACU Icon:

(a) Show Controller Status.

(b) Shunt: Controller, Power, Tamper. (c) Unshunt: Controller, Power, Tamper. (d) Building mode: Open, Limited, Closed. (e) Download: System, Keys.

(f) Forgive. (g) Silence. (h) Reset.

(i) Overrides: Shunt, Building Mode, Download, Forgive Silence, Reset.

(ii) Door Icon: The functions available will depend on the type of ACU connected to the Door that is selected. Override and control features available include, but are not limited to:

(a) Show Door Status.

(b) Shunt: Door, Coax, MSM, Analog reader, VIP, VIP tamper, Digital reader, Digital reader tamper. (c) Unshunt: Door, Coax, MSM, Analog reader, VIP, VIP tamper, Digital reader, Digital reader tamper. (d) Lock.

(e) Unlock. (f) Timed Unlock. (g) Override.

(iii) Input: The functions available will depend on the type of ACU connected to the Input that is selected. Override and control features available include, but are not limited to:

(a) Show Input Status. (b) Shunt.

(c) Unshunt.

(iv) Output: The functions available will depend on the type of ACU connected to the Output that is selected. Override and control features available include, but are not limited to:

(30)

(b) Shunt. (c) Unshunt.

(v) Elevator (Star II Controllers Only) (a) Show Elevator Status.

(b) Shunt: Elevator, VIP, VIP tamper, Digital reader, Digital reader tamper, MSR, MSR Tamper. (c) Unshunt: Elevator, VIP, VIP tamper, Digital reader, Digital reader tamper, MSR, MSR Tamper. (d) Lock. (e) Unlock. (f) Timed Unlock. (g) Override. (vi) Map: (a) Jump. (b) Properties.

5) Mouse-click navigation: Administrator shall be able to create an unlimited number of jump-to icons by simply dragging a pre-defined map to the current map. The Operator shall be able to jump from one map to another by selecting the tab associated with the map to be monitored, by selecting the applicable icon on the current map, or by right-mouse clicking on the map and selecting Jump to Map from the dialogue box.

9. Audit Trail of all Operator Activity:

a. Administrator s