NexSentry Manager Access Control & Security Management System

Transcription

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: NexWatch 7/28/2003 Rev i A Access Control System

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 , or visit the NexWatch Web page at For specification assistance For questions regarding application issues or use of this specification, please contact: William 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, Senior Technical 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. NexWatch 7/28/2003 Rev ii A NSM Access Control System

3 Table of Contents PART I GENERAL Introduction... 1 A. Complete system proposal:... 1 B. General services: 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: DESCRIPTION OF WORK... 2 A. General:... 2 B. Installation: Installing and bringing the system to operational status requires the following major steps: 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: QUALITY ASSURANCE... 4 A. Manufacturer:... 4 B. NexWatch Dealer:... 4 C. System Checkout:... 4 D. Regulatory Requirements:... 4 E. Security Management system computer workstations: 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 Manufacturer... 5 A. NexWatch Mission Falls Court Fremont, CA Telephone: 510/ Web Site: 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: E. Accessories: Access Control System A. System Description: B. Controller (NexSentry Star Series Controllers, Star I and Star II): B. [NexSentry UWIU Plus: 4-port Wiegand interface with MIRO 8/4 Monitor Input/Relay Output Board: C. [NexSentry MIRO 4/2 Monitor Input Unit: NexWatch 7/28/2003 Rev iii A Access Control System

4 D. [NexSentry MIRO 16/8 Monitor Input/Relay Output Board: E. [NexSentry MIRO 32/0 (and 64/0) Monitor Input Unit: F. [NexSentry MIRO 2/24 Relay Output Unit: G. [NexStar High Speed S-NET Multiplexer with RS-232 Conversion: Readers A. [Digital Proximity Reader (DigiReader): B. [Magnetic Stripe Pass Through Reader (MSR): C. [Keypad (4200K, 4205K): Credentials A. [QuadraKey Digital Proximity Card: B. [NexKey Digital Proximity Badge: C. [KeyMate Proximity Key Fob, Radio Frequency Identification (RFID tag): D. [2-Smart Digital Proximity / Smart Card: E. [Magnetic Stripe Card ISO/ABA format: Power A. Power Supply (PI-1) Power Inserter: Accessories: A. [Terminal: B. [Printer: C. [Modem: D. [Locking Hardware: E. [Switches: F. [External UPS batteries: PART II EXECUTION Installation A. General: B. Schedules: C. Telephone Lines: D. Field Quality Control: E. Documentation: SERVICE AND SUPPORT A. Startup: B. Training: C. Warranty Support: PART III Appendix...A NexWatch 7/28/2003 Rev iv A NSM Access Control System

5 NexSentry Star I Controller Hardware features summary Version Number of readers 2.37 or higher 2 standard, 4 or 8 with personality chip Card Technology - Digital Proximity - Keypad - Magnetic Stripe - Wiegand Reader-to-Controller protocol Microprocessor Host Communications Protocol Terminal Communications Protocol 32-bit Intel industrial microprocessor SEEP (Security Electronics Enhanced 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 Relay Outputs, Lock and Auxiliary 16 on board, 32 maximum 4 on board, 16 maximum Operator Interface Methods - Terminal: 1 RS-232 Communications to MIROs, Keypads and Readers - 4 S-NET (RS-485) Ports Specifications: - Host: 1 RS RS-485 or 1 Micro CoBox Ethernet Regulatory Approval - FCC, UL-1012, CSA, UL 294 Environmental - Humidity: 0% to 90% non-condensing Temperature: 20 to +120 F (-7 to +49 C) - NexWatch 7/28/2003 Rev v A Access Control System

6 NexSentry Star II Controller Hardware features summary Version 3.0 Number of readers 2 standard, 4, 8 or 16 with personality chip Card Technology - Digital Proximity - Keypad - Magnetic Stripe - Wiegand Reader-to-Controller protocol Microprocessor Host / Terminal Communications Protocol 32-bit Intel industrial microprocessor 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 16 on board, 255 maximum 4 on board, 96 maximum Operator Interface Methods - Terminal: 1 RS-232 Communications to MIROs, Keypads and Readers - 4 S-NET (RS-485) Ports Specifications: - Host: 1 RS RS-485 or 1 Micro CoBox Ethernet Regulatory Approval - FCC, UL-1012, CSA, UL 294 Environmental - Humidity: 0% to 90% non-condensing Temperature: 20 to +120 F (-7 to +49 C) NexWatch 7/28/2003 Rev vi A NexSentry Access Control System

7 NexSentry Input/Output (MIRO) Modules Hardware features summary 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 S-NET Communications 2 S-NET (RS-485) connectors MIRO 16/8: Monitor Inputs 16 Relay outputs 8 S-NET Communications 2 S-NET (RS-485) connectors MIRO 32/0: Monitor Inputs 32 Relay outputs 0 S-NET Communications 2 S-NET (RS-485) connectors MIRO 64/0: Monitor Inputs 64 Relay outputs 0 S-NET Communications 2 S-NET (RS-485) connectors MIRO 2/24: Monitor Inputs 2 Relay outputs 24 S-NET Communications 2 S-NET (RS-485) connectors NexWatch 7/28/2003 Rev vii A Access Control System

8 NexSentry Manager Security Management System Features Summary Version Summary Architecture Controller support: Star II Controller 2, 4, 8 and 16 Reader versions Star I Controller 2, 4 and 8 Reader versions NexSentry 4100 Series 2, 4 and 8 Reader Versions Alto 818SC Controller 8 Readers Technology support: Digital Proximity Analog Proximity Wiegand Reader-to-Controller protocol Keypad Magnetic Stripe Smart Card Biometrics 3.0 (2.2 for selected localization) 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. Windows NT 4 Client/Server w/ NT 4 Clients 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 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Time Periods 128 Holidays 30 Access codes 120 On-line Transaction storage 250,000 Off-line Transaction storage unlimited Alarm Monitoring: Monitor Points Output Relays Zones Logical/ACU (Star II only) 100/480 Reporting & Operating: Operators/Passwords 100 Operator Instructions 500 Floor Plan Maps May be limited by controller types used. See controller specifications for limits that may prevent security management system from having full functionality. NexWatch 7/28/2003 Rev viii A NexSentry Access Control System

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. NexWatch 7/28/2003 Rev ix A Access Control System

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. NexWatch 7/28/2003 Rev A Access Control System

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. NexWatch 7/28/2003 Rev A NexSentry Access Control System

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. c. Parts list, including: wiring and connection diagrams. NexWatch 7/28/2003 Rev A Access Control System

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 pretested 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 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. NexWatch 7/28/2003 Rev A NexSentry Access Control System

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: (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 Mission Falls Court Fremont, CA Telephone: 510/ Web Site: 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. NexWatch 7/28/2003 Rev A Access Control System

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 NexWatch 7/28/2003 Rev A NexSentry Access Control System

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 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. 3) Doors: 16, 32, 64, 128, 256. NexWatch 7/28/2003 Rev A Access Control System

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: ) Time Codes: 128. (i) May be limited by Controller. See Controller specifications for limits that may prevent system from having capabilities built into NexSentry Manager system software. 8) Holidays: 30 (i) May be limited by Controller. See Controller specifications for limits that may prevent system from having capabilities built into NexSentry Manager system software. 9) Access codes: 120. (i) May be limited by Controller. See Controller specifications for limits that may prevent system from having capabilities built into NexSentry Manager system software. 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: ) Operator instructions: ) Reports: 100. (i) May be limited by Controller. See Controller specifications for limits that may prevent system from having capabilities built into NexSentry Manager system software. 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. NexWatch 7/28/2003 Rev A NexSentry Access Control System

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 to which computer communication ports the Controllers are connected. 2) NexSentry Manager shall require a Poller Entry for each communication port to which Controllers are attached. 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, (vii) Acknowledge Time-out. (viii)retries. (ix) Shunt: Check or Uncheck NexWatch 7/28/2003 Rev A Access Control System

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 (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 NexWatch 7/28/2003 Rev A NexSentry Access Control System

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. (ii) Activate during these Building Modes: Open, Limited, Closed. NexWatch 7/28/2003 Rev A Access Control System

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 predefined 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 pre-defined Activity Times from predefined 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. NexWatch 7/28/2003 Rev A NexSentry Access Control System

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. NexWatch 7/28/2003 Rev A Access Control System

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 systemassigned 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 systemassigned 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. 5) Rank: System shall allow Administrator to assign a pre-defined privilege level for the Controller User. NexWatch 7/28/2003 Rev A NexSentry Access Control System

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 systemassigned 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 systemassigned 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 systemassigned 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. NexWatch 7/28/2003 Rev A Access Control System

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. f. Easy system customization: System shall allow additional customization, as follows: NexWatch 7/28/2003 Rev A NexSentry Access Control System

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 NexWatch 7/28/2003 Rev A Access Control System

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. d. Maps: (ii) Point ID Number Status. NexWatch 7/28/2003 Rev A NexSentry Access Control System

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: (a) Show Output Status. NexWatch 7/28/2003 Rev A Access Control System

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 shall be provided with the ability to monitor and to manage all actions performed by operators on the system. b. Audit trail records shall be saved to hard disk. c. Possible actions for audit records shall be report retrieval and archiving for off-line storage. 10. System Reports: a. NexSentry Manager shall be able to execute reports without impacting the real-time operation of the security system. b. NexSentry Manager shall track and report the dates of archived events available for reporting. System shall be able to generate reports for activity spanning any time period, using fixed disk files and high-density 3.5-inch floppy disk files. c. NexSentry Manager shall separate reports by group (door, monitor, time). d. NexSentry Manager shall provide reports for every data file maintained in the system. e. Database Reports: 1) Database Reports shall be accessible from the View dialogue of each data item. 2) NexSentry Manager shall grant option to view report on screen or to print. f. Transaction Reports: 1) NexSentry Manager shall provide transaction history reports. System shall provide filters allowing Operator to select the desired information for the report and the sorting order for that information. 2) Transaction Reports shall show whether the event was an alarm, acknowledgment to an alarm, the data and time of the event, the ID and description of the point involved, the cardholder ID and name, and a description of the transaction. Transaction reports shall be available from on-line or archived log files. g. Custom reports: NexSentry Manager shall allow custom reports to be generated using any SQL- or ODBCcompliant database. h. Pre-defined Reports: 1) Detail activity: Provides detail reports of all activity on the system within specified time intervals. 2) Exception activity: Provides selective reporting of specific types of activity on the system within specified time intervals. 3) Audit trail: Any time any data is changed, the system shall maintain an audit trail of the data changed and who made the change. This report allows management of database changes and is useful in meeting the requirements of most controlling agencies. NexWatch 7/28/2003 Rev A NexSentry Access Control System

31 4) History reports shall be available based on a particular cardholder or door. 11. Flexible archiving: a. On-line Storage of Security Events: When the database approaches a selected percentage of its limit, the system shall issue an alert to inform Operator(s) of the condition and to recommend that Operator perform a backup to the archival system. b. Archiving of Security Events: 1) NexSentry Manager shall provide the ability to backup all events stored in the transaction file. 2) In the event of hardware failure or need to execute a report using archived events, the events must be able to be retrieved by or restored to the system. c. Backup and Restoration of Security System Definitions: 1) The system shall provide the ability to backup definition, including both hardware and user information. 2) In the event of data corruption, tampering, or other loss of data integrity, the security system definitions shall be able to be restored to the on-line controllers. D. Other Common Requirements: 1. System Designed for Growth: a. Through addition of Controllers (and possibly software upgrade), the system shall provide support for expanded applications with a larger number of cardholders, card readers and alarm points. b. Modular software architecture and performance-oriented programming techniques shall optimize the system to provide minimum response time. 2. Capture of all Events from Access Control Units (Controllers): a. The server shall capture all events that occur at local access control units. b. Event capture shall occur real-time. c. These devices may include Multiple Switch Monitors (MSMs), Controllers, and alarm monitor units. 3. Failsoft Operation: a. If for any reason, communication between the computer and the Controller is interrupted, the Controller shall continue to make decisions. b. While connected to the Security Management System computer, the system shall constantly update the Controllers with the information necessary to operate in Failsoft mode. Each Controller has its own specific quantitative limitations. c. The Security Management System computer shall download a minimum of 20,000 card numbers, plus 120 access codes, to give full decision-making capability to each Controller. d. This capability shall provide for continued operation of distributed card readers at all times. 4. Automated System Control: The system shall provide the ability to automatically change the state of certain devices or areas based on time. 5. Multiple Identification Required for Access: a. Selected entrances and exits may require multiple methods of confirming identity for entry. b. The required system must support multiple technologies at any door, including any combination of the following: 1) Analog Proximity Sensors. 2) Digital Proximity Readers. 3) Keypads. 4) Magnetic Stripe Readers 5) Wiegand Reader-to-Controller protocol Readers including biometric identification devices. 6. Anti-passback: a. Ability to forgive passback per controller status shall be available via Operator overrides. NexWatch 7/28/2003 Rev A Access Control System

32 b. Passback forgiveness shall be provided to a single cardholder or for all cardholders on a Controller-by-Controller basis. c. Automatically forgive passback at pre-determined time of the day on a Controller-by-Controller basis. d. In case of Controller failure, the Controller shall automatically forgive all passback status upon return to operational status. 7. Trace: a. NexSentry Manager shall provide the capability to trace activity for specific cardholders at specific doors. b. For a cardholder, the system shall report activities throughout the system. c. NexSentry Manager shall display trace activities with the transaction log messages to alert Operator. 8. Distributed Processing: E. Accessories: a. Distributed access control decision-making: NexWatch Controllers support distributed processing, with the capability to make access decisions independent of the server. b. Automated download of data to distributed controllers: 1) NexSentry Manager shall maintain a central database on all access control equipment. 2) Central database shall include: (i) Cardholders. (ii) Controller components and configurations. (iii) Access codes. (iv) Automatic events (such as auto unlock), etc. 3) NexSentry Manager shall sort the information in the central database and send it to the appropriate Controller, allowing the local Controller to make all necessary decisions without the NexSentry Manager central terminal support. 1. Communication Modems: a. Direct Connection: 1) Short distance (max. two miles point-to-point on 22-AWG twisted pair at 9600 baud. Uses line drivers or short haul modems). 2) Lease line, point-to-point: [Define modem]. 3) Dial-up (i) Clients (ii) Controllers (iii) Diagnostics b. Conversion devices from RS232 to 20mA: 1) SE CI-1 or SE CI-8. c. Conversion devices from RS232 to RS-485: 1) NexStar Multiplexer. d. Power Management: 1) UPS: (i) Provides continuous power, without interruption, should primary power be interrupted. (ii) Provides 1 hour or more continuous DC power, depending on configuration. NexWatch 7/28/2003 Rev A NexSentry Access Control System

33 .3 ACCESS CONTROL SYSTEM A. System Description: 1. The access control and security management system (System) within the building shall consist of microprocessor-based Controllers, Monitor Input/Relay Output modules, [reader types] Readers, [credential type] credentials, and other components. The access control and security management system shall be monitored and managed by a NexSentry Manager client/server network (See Part II.2). To accommodate growth and to facilitate implementation of future technologies, System components shall be modular and expandable. B. Controller (NexSentry Star Series Controllers, Star I and Star II): 1. General: a. [Star I Only: The Star I Controller (Controller) shall be a 2 (two) Reader controller with optional 4 (four) and 8 (eight) Reader Personality chip conversions.] b. [Star II Only: The Star II Controller (Controller) shall be a 2 (two) Reader controller with optional 4 (four), 8 (eight) and 16 (sixteen) Reader Personality chip conversions.] c. Controller shall have with an onboard INTEL 32-bit microprocessor, battery backup, database, user defined reports, and several communication ports. d. Controller shall have four S-NET communication channels to which a variety of S-NET devices can be connected. Two of the S-NET ports shall be convertible to function as Wiegand protocol ports at no additional expense. e. Controller shall support one optional daughter-board for additional memory and/or for future feature enhancements. f. Controller shall provide the following functions: 2. Capacities: 1) Provides central control for all devices attached. 2) Makes decisions for access. 3) (Star II Only), Makes decisions for Elevator control. 4) Responds to monitor activity. 5) Receives input to control its decision-making. 6) Reports activity to other devices. a. Addressable devices: 1) Proximity readers: (i) [Star I only: up to 8 (eight)] (ii) [Star II only: up to 16 [sixteen] 2) Magnetic stripe readers: (i) [Star I only: up to 8 (eight)] (ii) [Star II only: up to 16 [sixteen] 3) Magnetic stripe readers with integrated keypads: (i) [Star I only: up to 8 (eight)] (ii) [Star II only: up to 16 [sixteen] 4) Keypads: (i) [Star I only: up to 8 (eight)] (ii) [Star II only: up to 16 [sixteen] b. Default Monitor inputs: (Star I Only) User definable Limited and Closed Mode request switches, ACU Tamper and Power Fail (default location is first four on-board input connections, ). c. Default Relay outputs: (Star I Only) User definable Building Mode and Latched Alarm (default Relay 1 and 2). d. MIRO module(s): System shall connect with up to 8 (eight) additional monitor input/output modules via S-NET. e. Expansion Bus: Controller shall support 1 (one) daughter-board for memory expansion and/or for future feature enhancements, including: NexWatch 7/28/2003 Rev A Access Control System

34 1) LonWorks adapter. 3. Specifications: a. Controller card dimensions: 5 X 15 X 1.5 in. (12.7 X 38.1 X 3.81 cm). b. [Controller enclosure dimensions: X X in. (13.9 X X 5.06 cm.)] c. [UL Listed Controller/MIRO enclosure dimensions: 21 X 25 X 4 in. (53.3 X 63.5 X 10.2 cm). 4. Environmental: a. Humidity: 0 to 95% non-condensing. b. Temperature: 20 to 120 F (-7 to 49 C). 5. Mounting: a. The Controller shall be available [as a board-only option.] [in an enclosure.] b. If enclosure is used, the front cover shall attach with four flange detents and shall be easily removed without tools for access to internal switches and parts. 6. Power: a. Source: Power is provided via twisted pair (shielding optional) wiring from a power supply unit. b. Consumption: Less than 5 (five) watts with 17 to 28 volts D.C. c. [Battery: A low voltage battery (such as a lithium cell) shall maintain the internally stored database setup when no power is available to the controller.] 7. Wiring: a. Connectors: Twisted pair (shielding optional) wiring shall supply both power and communications to system devices using the following connectors: 1) Host: 9-pin D-sub DTE (male) for RS-232 networking from Controller to Host or Terminal. 2) Host: 6-pin Phoenix Connector for RS-485 networking from Controller to Host or Terminal. 3) Host: TCP/IP Ethernet Micro CoBox (Optional) for Ethernet link from Controller to Host. 4) Terminal port: 9-pin D-sub DTE (male) for RS-232 networking from Controller to Terminal only. 5) 4 - S-NET MIRO, UWIU, Reader, etc: Phoenix-type. 6) Power supply: Phoenix-type. 7) Monitor Inputs and Relay Output (MIRO) units: Phoenix-type. b. Cable limitations: 1) S-NET data channel shall not exceed 4,000 feet. 2) Every S-NET device requires 16 VDC minimum for power. 3) S-NET power cable length shall be limited by the cable losses, the length of the cable, and the devices to which it is connected. 8. Communications: a. S-NET devices: RS-485 through the system s twisted pair (shielding optional) wiring. b. Host: SEEP Protocol (Star I Only) or CHIP Protocol (Star II Only) through RS-232 port, RS-485 port or Micro CoBox Ethernet interface. c. Terminal: ASCII (Star I Only) or NSM Lite (Star II Only) through Terminal Port. 9. Feedback: To facilitate trouble-shooting, LED indicators shall be included for every serial port. 10. Diagnostics: LED status lights shall indicate: a. Operational status of the controller. b. Lock status of controlled entries. 11. Self-protection: The Controller shall have inputs to detect: NexWatch 7/28/2003 Rev A NexSentry Access Control System

35 a. Power input failures. b. Controller tampering. 12. Software features: a. General: 1) Controller shall have the capability to act as a standalone unit with the software features described below. 2) Additional functionality and features may be added by networking system with a Security Management System computer (see specification for NexSentry Manager Security Management System software); however, the purpose of this section is to highlight the software features that are pre-programmed into the Controller. b. Database: Database shall store all user operating data and handle event reporting for all possible attached devices, and shall contain memory capacity for the following: 1) Users with unique ID: 50,000 maximum (Star I) 100,000 maximum (Star II)]. 2) Access Codes: The access code shall define where and when the cardholder will be granted access. (i) Number available: 120. (ii) Capacity: 4 (four) maximum time periods for each door in the system. (iii) Definable time periods: Start Time, Stop Time, Day(s) of week, and Holidays. 3) Time intervals: ) User-definable holidays: up to 30. 5) Transaction buffer: 5,000 maximum in Host port, 100 circular in the Terminal port. 6) Event Report (Action) Schedules: 32. c. Operational modes: Controller shall operate in one of two modes, as follows: 1) Standalone mode: (i) Controller shall not be attached to a Security Management System computer. (ii) (Star I Only) User interface shall be via an ANSI terminal configured for 7 Data Bits, Odd Parity and 1 Stop bit. Default baud-rate shall be (iii) (Star II Only) User interface shall be via the NexWatch NSM Lite configuration program operating on a Windows NT 4.0 PC. Default baud-rate shall be (iv) User interaction shall be via the user terminal (NSM Lite)or via access control card readers, keypads, etc. (v) All functions shall still be operable and commands normally done via the Security Management System computer shall still be done directly on the Controller via user terminal (NSM Lite) (vi) All system activity messages to Operator shall be printed in plain English (or other) Language Text. Mnemonic type or transaction code type operator messages are not acceptable. 2) Networked mode: (i) Controller shall be connected to a Security Management System computer. (ii) Changes to the database in the Controller shall be made on the Security Management System computer then downloaded to Controller. (iii) Log messages shall be stored on the Security Management System. (iv) If communications between Security Management System and Controller fails, Controller shall continue processing without degradation in function or responsiveness and log messages shall be stored in Controller memory until they can be delivered to Security Management System. (v) All system activity messages to the Security Management System shall be hexadecimal for efficient data communications supporting SEEP or CHIP protocol. (vi) The Security Management System shall have the responsibility for acknowledging and translating the received messages. (vii) While operating in Security Management System mode, a second port on the Controller shall be available for standalone mode connection and output. d. Building / ZONE Mode: Controller shall operate in one of three Building Modes, Open, Limited or Closed (Star I Only) or two Zone Modes, Disarmed or Armed (Star II Only) to determine if access will be allowed or denied. Star II Controllers may each consist of up to 16 ZONES. Each zone may be individually Armed or Disarmed in a manner similar to the Closing or Opening of the Star I and older ACUs. NexWatch 7/28/2003 Rev A Access Control System

36 1) Building Modes shall be defined as follows: (i) OPEN / Disarmed mode: designates any cardholder, privileged or not, may enter the building provided he has a valid access code (used during peak normal hours). (ii) LIMITED mode: designates when a privileged cardholder may enter the building, provided he has a valid access code. (iii) CLOSED / Armed mode: is used when the building is unoccupied. Although a privileged cardholder may enter a closed building, he must put the structure in the open or limited mode within one minute or an alarm will be activated. 2) Any card shall have means to be programmed as PRIVILEGED and be authorized to Close / Arm or Open / Disarm the building / Zone Mode feature. 3) If the card is not authorized (Privileged) to Open / Disarm the ACU / Zone, the Cardholder shall be unable to gain entry, regardless whether the Cardholder s Access Code has been programmed for that period. e. Operator Modes: Controller shall always operate in one of two states, depending on whether or not an operator is present, as follows: 1) Operate Mode: System shall operate in OPERATE Mode whenever Operator is not logged on. Log records shall be displayed on the screen as they are generated, if so configured. 2) Command Mode: System shall operate in COMMAND Mode whenever an operator is logged onto the Controller. All operations can be performed from the terminal or from the Security Management System computer. Command Mode shall have three functions: (i) To configure the system. f. Readers: (ii) To override the system. (iii) To use print commands. 1) System shall be able to assign a 24-character name for each reader. 2) System shall be capable of defining which reader(s) will report valid access reports, and at what times. 3) User shall be able to select which times and at what reader card trace reports are generated. 4) User shall be able to define which are CLOSED readers (readers where privileged cards function). 5) Type: Controller shall support 5 (five) (Star I Only) or 6 (six) (Star II Only) reader types, as follows: (i) NORMAL: Shall operate during all building modes for all users who meet the regular access criterion for that door. Privileged access criterion shall be disregarded. g. Anti-passback: (ii) OPEN: Shall operate only during the Building OPEN (ZONE Disarmed) mode: everyone shall be denied access during the LIMITED and CLOSED (ZONE Armed) modes. (iii) CLOSED: Shall operate during all modes, but, during the LIMITED and CLOSED (ZONE Armed) modes it shall operate under the regular access criteria only for users with privileged access. (iv) STATION: Shall be available if the Building Mode feature is used. Shall allow authorized users to change the Building operation mode to or from OPEN (ZONE Disarmed), LIMITED or CLOSED (ZONE Armed). Building modes may be completely controlled by direct commands. The STATION Type Reader shall have the same operation restrictions as the CLOSED Type Reader. (v) CONTINUOUS: Shall be capable of maintaining relay contact closure as long as a valid access card is within the read range of a Digital Proximity Reader. (vi) ELEVATOR (Star II Only): A card reader specifically designated for control of floor selection within an elevator cab. 1) System shall have capability to designate any card so that when it is used to enter an area or Zone, it must be used to exit that area or Zone before it can be reused for entry. 2) System shall have capability to manually or automatically reset the passback status of all cards to UNKNOWN (FORGIVEN) at any time. 3) Anti-passback modes: (i) HARD mode: Denies re-entry into a Passback Zone and reports passback violation. (ii) SOFT mode: Allows re-entry into a Passback Zone, but reports passback violation. NexWatch 7/28/2003 Rev A NexSentry Access Control System

37 4) Auto-forgive: A supervisor shall have a method of selectively disabling anti-passback protection. During the time auto-forgive is active, the system shall ignore the anti-passback protection and reset the cards that use the door within the specific ACU to UNKNOWN. h. Alarm monitoring and control functions: 1) Latch Alarm: Any monitor point can drive a report that shall trigger the Controller s latched alarm contact. This alarm shall stay on until an operator performs the SILENCE command to turn it off. Star I Controllers support 1 (one) Latched contact. Star II Controllers can support up to 96 Latched contacts. 2) Alarm points: Alarm monitors, such as Passive Infrared Motion Detectors, Glass-Break detectors, etc., shall be monitored constantly by the Controller. These shall be capable of being programmed to cause output contacts to be closed to sound alarms or activate other devices. 3) Output contacts: shall be used to activate silent alarms or to report alarms to the central station or to control devices such as pumps and sirens. Star I will support up to 16 (sixteen) contacts, Star II will support up to 96. 4) Alarm Silence: Latched alarm may be silenced either via the user interface or from the Security Management System computer. The alarm may be turned on again if the alarm trigger is still activated. 5) Alarm shunts: System shall have means to connect presence detecting device to shunt alarms when authorized employee uses an alarmed exit. Exit reporting shall be selected by user. 6) Open door detection: Any time a door is left open for more than the configured amount of time, a configured action can be taken. 7) Forced door detection: Any time a door is forced open, a configured action can be taken. 8) Loss of power alarm: Controller shall indicate when the UPS is about to run out of power. If possible, a POWER FAIL log message shall be produced. 9) Tamper detection: Controller shall indicate when the unit s enclosure is being tampered with. i. User interface: 1) Star I Controller shall support an ASCII character-based line-oriented interface via the RS-232 Terminal line. 2) Star II Controller shall support direct user interface via the NSM Lite program using the CHIP protocol. 3) If Controller is configured without a Security Management System connection, then the User interface may also be performed via the Security Management System port. j. Passwords: 1) Authorization levels: Each password shall be assigned to one of 6 (six) authorization levels. 2) Operator passwords: up to 8 (eight) defined. 3) Duplication: If a password is duplicated, Controller will only recognize the first occurrence. 4) Identification of operators for terminal use: 8 (eight) different operators. 5) User definable passwords: Up to 12- (twelve) -character user, definable passwords shall be used to log on to the system. k. System diagnostics: 1) System shall be capable of automatic system diagnostics and automatic alarming based on detected faults in the controller, readers, monitor input and relay controlling devices and keypads. l. Control operation: 1) Control operation shall be based on the ability to force relay lock outputs to an operating mode. 2) Forcing action may be initiated by: (i) Time-of-Day schedule. (ii) Switch Closure. (iii) Command Key Presentation. (iv) Keyboard Command. m. Card/Key Commands and Functions: 1) Cardholders allowed: (i) Standard configuration: NexWatch 7/28/2003 Rev A Access Control System

38 (a) Standard Controller configuration shall allow up to 50,000 (Star I) or 100,000 (Star II) unique numeric identification numbers to be entered including PIN Codes of up to 6 digits. 2) Both keys with and without names shall be allowed within the same database (Star I Only). 3) Any card usage may be traced by the system and a card trace report generated. 4) Access parameter definition: any single card can be programmed to open a given door during four different time periods. 5) Modification of card access parameters: may be modified at any time by an operator with a sufficient authorization level. n. Pre-programming: The access control and security management system shall have pre-programmed default data for ease in start-up and testing of equipment. o. Printed Data Output: 1) System shall be capable of selecting which access and monitor point activity messages are to be output to the printer. 2) System shall be capable of printing the following information: (i) card Definitions: (a) Card Numbers (b) Names (c) Access Codes (d) Privileged status (e) Card trace function (Enable/Disable) whether Privileged or not. (f) Location (In-Out status for anti-passback) (g) User selected PIN Number (ii) Monitored Point Parameters. (iii) Door Parameters. (iv) (Star II Only) Elevator Parameters (v) Access Code Parameters. (vi) User Names, Passwords, and Access Levels. (vii) (System Status (real time report). (viii)all Report Types. p. Relay outputs: Each Controller shall initiate up to 96 relay output commands based on: 1) Card Access Activity. 2) Operator Keyboard Inputs. 3) Pre-programmed Time Schedule. 4) Switch Input. q. Monitoring: 1) Supervised alarm contacts: up to 255 per Controller. 2) Character names: up to 24 characters defined by user. 3) Monitor points shall: (i) Be designated by the user as an alarm or non-alarm event. (ii) Be elected to either monitor at all times or during selected ACU / Zone modes and/or time periods. (iii) Be capable of being enabled/disabled from terminal or externally from cardholder. (iv) Be capable of enabling any lock output or annunciator output including the latched alarm contact. (v) Work with the controller to provide immediate re-lock after cardholder has gained access into a facility. Systems re-locking only after adjustable time delay shall be acceptable. r. Forced Entry Alarms: 1) System shall have means to select which doors shall report forced entry alarms or door held open alarms. NexWatch 7/28/2003 Rev A NexSentry Access Control System

39 2) On a door by door basis, user shall be able to select which doors are to report forced entry and during what time periods. 3) User shall be able to select whether such alarms will be generated at all times or when system is in OPEN (DISARMED) / LIMITED / CLOSED (ARMED) mode. s. Disk backup: The access control and security management system shall allow for disk backup and restoration of user data in the event of database loss if connected to a Security Management System computer. t. Battery backup: The access control and security system shall include internal battery backup to maintain controller database, program, time, date, and building mode during a power loss. 13. Manufacturer: NexWatch 14. Model: a. [(Star I Only): NexSentry Star I Controller.] b. [(Star II Only): NexSentry Star II Controller.] C. [NexSentry UWIU Plus: 4-port Wiegand interface with MIRO 8/4 Monitor Input/Relay Output Board: 1. General: a. NexSentry Universal Wiegand Interface Unit (UWIU) Plus shall be a module that accepts up to 4 Readers using Wiegand Reader-to-Controller protocol and converts their data output to S-NET protocol. The UWIU Plus also monitors inputs that occur over the S-NET and sends them to the Controller. b. UWIU Plus shall execute relay commands received from the controller out to S-NET devices. 2. Capacities: a. Wiegand protocol Readers: 4 (four) using any common Wiegand Reader-to-Controller protocol. b. Relay Outputs: 4 (four) 5-Amp form C relays. c. Monitor Inputs: eight (eight) four-state monitor points. 3. Specifications: a. Board dimensions: 5 X 7.25 X 1.25 in. (12.7 X 18.5 X cm) b. [Enclosure dimensions (Holds two UWIU Plus units) : 16.8 X 4.6 X 5.5 in. (42.6 X11.7 X 13.9 cm)] 4. Environmental: a. Humidity: 0 to 95% non-condensing. b. Temperature: 19 to 120 F (-7 to 49 C). 5. Mounting: UWIU Plus shall be mounted in an enclosure with the Controller or standalone in a controlled area. 6. Power: a. Source: Twisted pair (shielding optional) connected to Controller. b. Consumption: Less than 300mW with 16 to 28 volts DC. 7. Wiring: a. Connectors: Twisted pair (shielding optional) wiring shall supply both power and communications to system devices using the following connectors: 1) Wiegand protocol Readers: Phoenix type 2) Monitor Inputs: Phoenix-type. 3) Relay Outputs: Phoenix-type. 8. Communication: S-NET Communications through 2 (two) RS-485 connectors via the twisted pair (shielding optional) wiring. 9. Manufacturer: NexWatch 10. Model: NexSentry UWIU Plus] NexWatch 7/28/2003 Rev A Access Control System

40 D. [NexSentry MIRO 4/2 Monitor Input Unit: 1. General: NexSentry MIRO 4/2 Monitor Input Unite (MIRO 4/2) shall send input changes and perform commands as directed by S-NET messages from the NexSentry Controller. MIRO 4/2 shall have the following: a. Two (2) relay outputs. b. Four (4) four-state monitor inputs. c. One input for use as an override command to cause all relays to energize d. One (1) RS-485 communication channel to an SNET host designed for daisy chain (1 connector in, 1 connector out) e. Power conversion circuitry required for use with a 24V-power supply. f. One 4-state input for tamper detection. g. Reset switch with power-up reset logic. h. All circuits shall be designed for compliance with UL-294 and FCC requirements. 2. Performance: MIRO 4/2 shall digitally filter input contacts such that only changes lasting 100 msec or more are reported. No valid changes shall be missed. MIRO 4/2 shall also provide: a. Timed ON output pulses in increments of 100msec. b. Timed OFF output pulses. c. Alternating ON/OFF timed cycles as directed by NexSentry Controller. 3. Capacities: a. Relay Outputs: Two (2) 5-Amp form C relays. b. Monitor Inputs: Four (4) 4-state monitor points. 4. Specifications: a. Board dimensions: 5 X 5 X.75 in. (12.7 X 12.7 X C). b. Enclosure dimensions: 7.5 X 6 X 1.25 in. (19.05 X X C). c. Weight: 10 oz. (280 g) 5. Environmental: a. Humidity: Zero to 95% non-condensing. b. Temperature: 19 to 120 F (-7 to 49 C). 6. Mounting: MIRO 4/2 shall be mounted in an enclosure with the Controller or standalone in a controlled area. 7. Power: a. Source: NexSentry Controller. b. Consumption: accepts 9 to 32 volts DC. and consumes 1.2 watts when all relays are energized. 8. Wiring: a. Connectors: Twisted pair (shielding optional) wiring shall supply both power and communications to system devices using the following connectors: 1) Monitor Inputs: Phoenix-type. 2) Relay Outputs: Phoenix-type. 9. Communication: One (1) RS-485 communication channel to an SNET host designed for daisy chain (1 connector in, 1 connector out). 10. Regulatory Requirements: NexSentry MIRO 4/2 shall meet the requirements specified by the following: a. UL294 Standard for Safety: Access Control Units. b. FCC EMI and EMC Class A. c. En55022 EMI and EMC Class A. 11. Manufacturer: NexWatch 12. Model: NexSentry MIRO 4/2] NexWatch 7/28/2003 Rev A NexSentry Access Control System

41 E. [NexSentry MIRO 16/8 Monitor Input/Relay Output Board: 1. General: a. NexSentry MIRO 16/8 Monitor Input/Relay Output Board shall be a module that monitors inputs that occur over the S-NET and sends them to the Controller. b. MIRO 16/8 shall execute relay commands received from the controller out to S-NET devices. 2. Capacities: a. Relay Outputs: 8 (eight) Normally opened (NO) or Normally Closed (NC) via strap position. b. Monitor Inputs: 16 (sixteen) four-state monitor points. 3. Specifications: a. Board dimensions: 5 X 15 X 1.25 in. (12.7 X 38.1 X cm) b. [Enclosure dimensions: X 4.6 X in. (42.64 X11.68 X 13.9 cm)] 4. Environmental: a. Humidity: 0 to 95% non-condensing. b. Temperature: 19 to 120 F (-7 to 49 C). 5. Mounting: MIRO 16/8 shall be mounted in an enclosure with the Controller or standalone in a controlled area. 6. Power: a. Source: Twisted pair (shielding optional) connected to Controller. b. Consumption: Less than 3 watts with 16 to 28 volts D.C. 7. Wiring: a. Connectors: Twisted pair (shielding optional) wiring shall supply both power and communications to system devices using the following connectors: 1) Monitor Inputs: Phoenix-type. 2) Relay Outputs: Phoenix-type. 8. Communication: S-NET Communications through 2 (two) RS-485 connectors via the twisted pair (shielding optional) wiring. 9. Manufacturer: NexWatch 10. Model: NexSentry MIRO 16/8] F. [NexSentry MIRO 32/0 (and 64/0) Monitor Input Unit: 1. General: NexSentry MIRO 32/0 (64/0) Monitor Input Unit shall be a module that sends input changes to the NexSentry Controller via S-NET communications, and shall have the following features: a. 32 (thirty two) or 64 (sixty four) 4-state-state monitor inputs. b. 1- (one) RS-485 communication channel to an SNET host designed for daisy chain (1 connector in, 1 connector out). c. Power conversion circuitry required for use with a 24V-power supply. d. One input for tamper detection. e. Reset switch with power-up reset logic. f. All circuits shall be designed for compliance with UL-294 and FCC requirements. 2. Performance: MIRO 32/0 (64/0) shall filter input contacts such that only changes lasting 100 msec or more are reported. No valid changes shall be missed. 3. Capacities: a. Relay Outputs: None. b. Monitor Inputs: 32 (thirty two ) or 64 (sixty four) four-state monitor inputs, one (1) input for tamper detection. 4. Specifications: a. Board dimensions: 5 X 15 X 1.25 in. (12.7 X 38.1 X 3.2 cm). NexWatch 7/28/2003 Rev A Access Control System

42 b. Enclosure dimensions: 5 X X (12.7 X 41.3 X 4.7 cm). c. Weight: 16 oz. (448 g). 5. Environmental: a. Humidity: Zero to 95% non-condensing. b. Temperature: 19 to 120 F (-7 to 49 C). 6. Mounting: MIRO 32/0 (64/0) shall be mounted in an enclosure with the Controller or standalone in a controlled area. 7. Power: a. Source: NexSentry Controller b. Consumption: 215 mw (400 mw) with all relays active 8. Wiring: a. Connectors: Twisted pair (shielding optional) wiring shall supply both power and communications to system devices using the following connectors: 1) Monitor Inputs: Phoenix-type. 2) Relay Outputs: Phoenix-type. 9. Communication: S-NET Communications through 2- (two) RS-485 connectors via the shielded twisted pair (shielding optional for the 24VDC power)wiring. 10. Manufacturer: NexWatch 11. Model: NexSentry MIRO 32/0 (64/0)] G. [NexSentry MIRO 2/24 Relay Output Unit: 1. General: MIRO 2/24 Monitor Input Unit (MIRO 64/0) shall be a module that accepts relay commands from the NexSentry Controller via S-NET communications, and shall have the following features: a. Twenty-four Form C relays b. One input for tamper detection c. One input for use as an override command to cause all relays to energize d. One RS-485 communication channel to an SNET host designed for daisy chain (1 connector in, 1 connector out) e. Power conversion circuitry required for use with a 24V-power supply. f. One input for tamper detection g. All circuits shall be designed for compliance with UL-294 and FCC requirements. 2. Performance: MIRO 2/24 shall provide: a. Timed ON output pulses in increments of 100msec. b. Timed OFF output pulses. c. Alternating ON/OFF timed cycles as directed by NexSentry Controller. 3. Capacities: a. Relay Outputs: 24 (twenty four) Form C relays. b. Monitor Inputs: 1) One (1) for use as an override command to cause all relays to energize. 2) One (1) input for tamper protection. 4. Specifications: a. Board dimensions: 5 X 15 X 1.25 in. (12.7 X 38.1 X 3.2 cm) b. Enclosure dimensions: 5 X X (12.7 X 41.3 X 4.7). c. Weight: 16-oz. (448 g.) NexWatch 7/28/2003 Rev A NexSentry Access Control System

43 5. Environmental: a. Humidity: Zero to 95% non-condensing. b. Temperature: 19 to 120 F (-7 to 49 C). 6. Mounting: MIRO 2/24 shall be mounted in an enclosure with the Controller or standalone in a controlled area. 7. Power: a. Source: NexSentry Controller b. Consumption: 215 mw with all relays active 8. Wiring: a. Connectors: Twisted pair (shielding optional) wiring shall supply both power and communications to system devices using the following connectors: 1) Monitor Inputs: Phoenix-type. 2) Relay Outputs: Phoenix-type. 9. Communication: S-NET Communications through 2 (two) RS-485 connectors via the twisted pair (shielding optional) wiring. 10. Manufacturer: NexWatch 11. Model: NexSentry MIRO 2/24] H. [NexStar High Speed S-NET Multiplexer with RS-232 Conversion: ********** Note: If the system must use a home-run wiring scheme, rather than the standard daisy-chain wiring scheme of a typical NexSentry Controller installation, you must use a NexStar S-NET Multiplexer to join the multiple wire runs into a single wire run that feeds into the NexSentry Controller or NexSentry MIRO. If system uses a daisy-chain wiring scheme, delete this section. ********** 1. General: NexStar S-NET Multiplexer (NexStar) shall: a. Be a 5-port RS485 multiplexer that provides a link between a NexWatch access control unit and multiple S-NET runs. b. Have the ability to accept an RS-485 to RS-232 adapter for any number of the 5 ports. c. Provide maximum flexibility for wiring RS-485 and RS-232 communications in an installation through multi-drop connections. d. Consist of a single printed circuit assembly (PCA) in a two-part housing. Male Phoenix connectors on the PCA shall be accessed through the side of the housing for port connections. RS-232 adapters shall plug in to existing 8-pin sockets on the PCA. e. Allow home run wiring to connect between S-NET communication devices and a controller. f. Be able to be used with all multi-door controllers that support S-NET protocol using twisted pair wire. g. [Star I and Star II Controllers only: Provide a convenient RS-232 to RS 485 conversion to allow the Serial port of a Host PC to connect to a network of up to 16 Star Controllers. h. [Conversion Solutions only: Provide an easy conversion path from analog technology to digital technology. Using NexWatch NexLine adapters, existing coax can be used in a digital system. i. [Wiegand system upgrades only: Provide an easy upgrade path for Wiegand style networks to advanced RS-485 using the existing twisted-pair wiring. j. Provide network-wiring lengths up to 20,000 feet. 2. Specifications: a. Dimensions: 4.10 X 7.25 X 1.35 in. (10.41 X X 3.43 cm) b. Construction: 1) Sheet Metal ESD protected enclosure. 2) Five identical ports. NexWatch 7/28/2003 Rev A Access Control System

44 c. Weight: 13 oz. (400 g) 3. Environmental: a. Operating Temperature range: 4 F to 120 F (-20 C to 50 C) b. Operating humidity range: 0 to 90%, non-condensing 4. Mounting: a. Four screw holes in the corners of the enclosure. 5. Power:.4 READERS a. Input voltage: +15 to+28 VDC b. Operating current: 50 ma c. Pass through current: 2A 6. Connectors: Phoenix. 7. Compatibility: a. DigiReader Series digital proximity readers. b. NexSentry Star I and Star II Controllers c. NexSentry 4100 Series Controllers. d. Alto 818 SC Controllers. 8. Communications: S-NET communications through single twisted pair wire with overall shield. 9. Wiring: a. Single S-NET run using twisted pair wiring up to 4,000 feet (1,200). b. Using all NexStar s five symmetrical ports, the end-to-end S-NET length shall be able to span up to 8,000 feet (2400 meters) and contain up to 20,000 feet (6,000 meters of installed wiring. c. Separate twisted-pair cables for data and power shall be used when wire run lengths exceed 500 feet (150) meters. 10. Feedback: a. 5- (five) port LEDs shall illuminate when the associated port is transmitting. b. The COM ACTIVE LED shall be illuminated when any data is being passed through NexStar. 11. Manufacturer: NexWatch 12. Model: NexStar High Speed] A. [Digital Proximity Reader (DigiReader): *********** Note: There are a number of DigiReader digital proximity readers available to meet varying needs of most installations. Each reader provides different read ranges. When compiling Specifications, use the Read Range Matrix (Appendix) to determine the reader and card that best suit the specific application. Determine which reader best suits your application and enter the appropriate model number in place of the [XX]. *********** 1. General: a. DR 42[XX] DigiReader digital proximity reader shall read NexWatch digital proximity ID credentials and send signal to Controller for processing. b. [DR 4205K version shall have an integrated keypad for additional security, be weatherized for external use, and comply with the ADA. Keypad shall provide a standard 12-key telephone pad layout with 10-digit numeric entry pad, and * (star) and # (pound) keys.] c. [DR 4201 and DR 4208 versions shall be capable of reading HID proximity cards.] d. [42[XX]E version shall be weatherized and splash-proof for external use.] NexWatch 7/28/2003 Rev A NexSentry Access Control System

45 e. [4205GM version shall feature a glass-mount kit with LED status display on front and back of reader.] f. [DR 4201, 4203, 4205, 4208 and 4220 versions shall be a proximity reader that interfaces to any Access Control panel that employs Wiegand Reader-to-Controller communication protocol. Wiegand protocol connection to a NexWatch controller shall be through a NexSentry Wiegand Interface Unit and operates using 26- or 34-bit 5-wire Wiegand standard.] 2. Capacities: a. DR 42[XX] shall read digital proximity keys supporting phase shift signals to a distance of [ ] (enter optimum read range as defined in DigiReader/Prox Card Read Range Matrix in appendix) inches and does not require contact with the reader. 3. Construction: Material shall be high-impact Lexan with 94V-2 UL flame class rating, and shall be UV resistant, sealed, water and weather resistant, and tamperproof. 4. Environmental: a. Humidity: 10% to 90% non-condensing. [ E version: 5% to 100% condensing]. b. Temperature: -4 to +140 F (-20 to +60 C) [ E version: -31 to 150 F (-35 to 66 C)] 5. Power: a. Source: Via the network twisted pair (shielding optional) wiring. b. Consumption: 1) [DR 4201: Less than 50 mw.]] 2) [DR 4203: Less than 100mW.] 3) [DR 4205 Series: Less than 120mW.] 4) [DR 4208 Series: Less than 150mW.] 5) [DR 4220 Series: Less than 400mW.] 6. Regulatory: DigiReaders shall be designed to meet the following regulatory requirements: a. UL294 Listing Standard for Safety. b. FCC EMI and EMC Class A. c. EN55022 EMI and EMC Class A. d. American with Disabilities Act (ADA). 7. Mounting: a. DR shall have the capacity to be mounted and operated behind any non-metallic, non-conductive surface, including glass. b. [(DR 4203 only) DR 4203 shall have the capability to be mounted on any metal door frame.] 8. Wiring: Twisted pair (shielding optional) with 4,000 foot maximum recommended length. 9. Feedback: a. Single tri-color LED (green/amber/red) shall provide capability for diagnostic feedback. b. Tri-color LED shall be programmable. c. An audio tone shall indicate successful digital proximity card read and Access Granted. 10. Diagnostics: DR and data-line integrity shall be monitored continuously and shall alarm if failure is detected and indicate device and location of fault. 11. Self-protection: a. Physical damage, including breaking open sensor housing, shall not allow access to any circuitry, which would allow the system to be compromised. Tampering shall be annunciated to the Controller. b. Transmission of any frequency (or set of frequencies) into the sensor at any power level shall not compromise the system. 12. Manufacturer: NexWatch 13. Model: NexWatch 7/28/2003 Rev A Access Control System

46 a. [DR 4201] b. [DR 4203] c. [DR 4205], [DR 4205GM], [DR 4205K] d. [DR 4208] e. [DR 4220] B. [Magnetic Stripe Pass Through Reader (MSR): *********** Note: There are currently two models of MSR 42 Series Magnetic Stripe readers. Both MSR42 and MSRK 42 readers are identical in every way, with one exception: MSRK 42 adds an integrated key pad for numeric verification of magnetic stripe input data. When compiling spec, determine which reader best suits your requirements, or whether you want to use both for different applications on the same system. Delete the [bracketed] information that does not apply to your specification. *********** 1. General: a. [MSR42: MSR shall read magnetic stripe cards that have been encoded with standard ISO/ABA Track II card numbering format.] b. [MSRK42: MSRK shall read magnetic stripe cards that have been encoded with standard ISO/ABA Track II card numbering format, and shall have an integrated 12-key Keypad for numeric entry to verify magnetic stripe input data.] c. Magnetic stripe cards shall be read in either direction while being swiped through the MSR. 2. Capacities: a. Readers shall read all 40 (forty) digits of the swiped magnetic stripe card. b. [MSRK42: MSRK readers with integrated keypad shall allow numeric entry for additional security.] 3. Specifications: a. Dimensions: 1.95 X 1.30 X 5.50 in. (5 X 3.3 X 14 cm). b. Card accommodation: ISO standard Credit card sized magnetic stripe card (2.125 X X.030 in., +/-.003 in.; 75 bip; ANSI X 4.16). c. Read speed: 3 to 50 ips. 4. Environmental: a. Humidity: 0% to 95% RHNC (weatherized option to 100%). b. Temperature: -31 F to 150 F (-35 C to +66 C). 5. Mounting: Wall-mounted either horizontally or vertically on a standard single-gang handy box (preferred method), on any flat surface, on a structured door frame (mullion), or as a Wiegand (Sensor Model 30387) reader replacement using matching hot holes on the adapter plate. a. [MSR42G / MSRK42G: are designed for indoor use, but can be used for most sheltered outdoor applications.] b. [MSR42GW / MSRK4GW: are weatherized for outdoor use and can withstand direct exposure to the elements.] 6. Power: a. Source: Powered from the system twisted pair (shielding optional) wiring connected to the Controller. b. Current: 50mA. c. Wiring: Twisted pair cable with maximum recommended length of cable being 4,000 feet. 7. Feedback: a. Reader shall provide a two state LED that indicates door status as follows: 1) A red light indicates active but locked; 2) A green light indicates unlocked. b. Realer shall sound an alarm upon improper card entry. NexWatch 7/28/2003 Rev A NexSentry Access Control System

47 8. Diagnostics: Reader shall perform a power-up self test, which indicates the success or failure of the test. 9. Self-protection: a. Physical damage, including breaking open reader housing, shall not allow access to any circuitry, which would allow the system to be compromised. Tampering shall be annunciated to the Controller. 10. Manufacturer: NexWatch 11. Model: a. [MSR42-G, Magnetic Stripe Card Reader.] b. [MSR42-GW, Weatherized Magnetic Stripe Card Reader.] c. [MSRK42-G, Magnetic Stripe Card Reader with Keypad.] d. [MSRK42-GW, Weatherized Magnetic Stripe Card Reader with Keypad.]] C. [Keypad (4200K, 4205K): 1. General: a. The system shall have the means to utilize a numeric keypad for entry of a Personal Identification Number (PIN). b. The Keypad shall provide information to the Controller, either alone or in conjunction with a [DigiReader Series digital proximity reader] [credential reading device], thereby providing an additional level of security. The 4205K is an integrated DigiReader with Keypad. c. The system shall have the means to recognize special duress codes that can be entered into the Keypad to be available to any user during an emergency. d. System administrator shall have capability to program a reaction based on keypad duress code input. 2. Capacities: a. Keypad shall provide a standard 12-key telephone pad layout with 10-digit numeric entry pad, and * (star) and # (pound) keys. b. The user shall be able to enter a 4- to 8-digit Personal Identification Number (PIN). 3. Specifications: The keypad unit shall be surface mounted using mounting holes in the device backplate. 4. Environmental: a. Temperature: 20 F to 120 F (-7 C to +49 C). b. Humidity: 10% to 95% non-condensing. 5. Regulatory: The unit shall meet the following regulatory requirements: a. FCC Class A computing device when installed in the system. 6. Mounting: a. Keypad shall be mounted on the outside of a building, in a wall, or against it. 7. Power: Keypad receives power from the network twisted pair wiring. 8. Wiring: Twisted pair cable with a maximum recommended cable length of 4,000 feet. 9. Feedback: Keypad shall provide three LED status for awaiting card presentation, awaiting keypad entry and acknowledgment of successful access granted and door unlock. 10. Self-protection: Keypad is protected against the circuitry being removed from the outlet box or the box being forcibly removed from the wall by means of a strategically placed internal tamper switch. 11. Manufacturer: NexWatch Model: 4200K / 4205K NexWatch 7/28/2003 Rev A Access Control System

48 .5 CREDENTIALS *********** Note: There are a number of credentials available to meet varying needs of most installations. In most situations, more than one kind of credential can be used with certain readers. When compiling Specifications, use the Read Range Matrix (Appendix) to determine the reader and card that best suit the specific application. Determine which card (or cards) best suits your application delete the other options from your specification. *********** A. [QuadraKey Digital Proximity Card: 1. General: a. QuadraKey Digital Proximity Card (Card) is an ISO-compliant, single-coil passive digital proximity ID credential that supports multiple technologies on one card, including: digital proximity, magnetic stripe, bar code and photo ID. b. Design shall be capable of smart chip insertion, color imaging on both sides and hole punch horizontal or vertical for using the card as a badge. c. Note: Active circuit type cards (those requiring batteries) shall not be acceptable. 2. Capacities: a. QuadraKey shall be able to generate a minimum eight-digit access number. b. Cards shall have numeric encoded data embedded in an integrated circuit within the card. c. Each card shall be encoded so that it is unique and exists in no other system anywhere in the world. 3. Specifications: a. Dimensions: ISO standard size and thickness of 3.37 X X in (8.55 X 5.39 X cm). b. Material: Single-coil in PVC. c. Magnetic stripe material: single-layer 3M type 5203 High Coercivity, 4000 Oerstad using Track 2, without exception. d. Magnetic stripe dimensions: The stripe shall minimally extend from in. to in. from the upper card edge and for the entire length of the card. 4. Environmental: a. Temperature: 14 to 140 F (-10 to 60 C). b. Humidity: 0% to 100%. 5. Regulatory: N/A (Card is totally passive requiring no approval.) 6. Power: a. Source: Passive - powered by DigiReader digital proximity reader. 7. Communication: Via low-power radio frequency, providing read ranges up to [20] inches depending on the selected DigiReader. (see "DigiReader/Prox Card Read Range Matrix" in Part IV.1 for actual figures). 8. Manufacturer: NexWatch Model: QuadraKey.] B. [NexKey Digital Proximity Badge: 1. General: a. NexKey Digital Proximity Command Badge (Card) is a single-coil passive digital proximity ID credential that can, through add-on options, support additional technologies, including: bar code and photo ID with lamination. b. Card shall be highly resistant to face abrasion or bending. c. Card shall have a slot in the vertical position for use as a badge. d. Note: Active circuit type cards (those requiring batteries) shall not be acceptable. 2. Capacities: NexWatch 7/28/2003 Rev A NexSentry Access Control System

49 a. Card can generate a minimum eight-digit access number. b. Cards shall have numeric encoded data embedded in an integrated circuit within the card. c. Each card shall be encoded so that it is unique and exists in no other system anywhere in the world. 3. Specifications: a. Dimensions: 3.37 X X in. (8.55 X 5.93 X 0.19 cm). b. Construction: Single-coil in ABS polycarbonate base covered with Lexan skin. 4. Environmental: a. Temperature: 14 to 140 F (-10 to 60 C). b. Humidity: 0% to 100% humidity. 5. Regulatory: N/A (Card is totally passive requiring no approval.) 6. Power: Passive - powered by DigiReader digital proximity reader. 7. Communication: Card shall communicate via low-power radio frequency, providing read ranges up to [22] inches depending on the selected DigiReader. (See "DigiReader/Prox Card" read range matrix for actual figures). 8. Manufacturer: NexWatch 9. Model: NexKey. C. [KeyMate Proximity Key Fob, Radio Frequency Identification (RFID tag): 1. General: a. KeyMate Digital Key Fob is a compact, single-coil passive digital proximity access credential for use in environments requiring a flexible alternative to access cards for tracking people, items or inventory. b. Fobs shall be constructed of a lightweight yet highly durable, waterproof polypropylene material and feature one built-in slot for easy conversion to a key chain, bracelet or commercial ID tag. c. Note: Active circuit type cards (those requiring batteries) shall not be acceptable. 2. Capacities: a. KeyMate Digital Key Fob shall generate a minimum eight-digit access number. b. Numeric encoded data shall be embedded in an integrated circuit within each fob. Each fob shall be encoded so that it is unique and exists in no other system anywhere in the world. 3. Specifications: a. Dimensions: X X.125 in. (3.49 X 4.13 X.125 cm). b. Construction: Single-coil molded in durable polypropylene material. 4. Environmental: a. Temperature: -31 to 270 F (-35 to 132 C). b. Humidity: 0% to 100% condensing. 5. Regulatory: N/A (Fob is totally passive requiring no approval). 6. Power: Passive - powered by DigiReader digital proximity reader. 7. Communication: KeyMate Digital Key Fob shall communicate via low power radio frequency, providing read ranges up to [15] inches depending on the selected DigiReader (See DigiReader/Prox Card read range matrix for actual figures). 8. Manufacturer: NexWatch 9. Model: KeyMate.] D. [2-Smart Digital Proximity / Smart Card: 1. General: a. 2 Smart Digital Proximity /Smart Card (Card) is an ISO-compliant, single-coil passive digital proximity ID credential that supports multiple technologies on one card, including: digital proximity, magnetic stripe, bar code Contact Smart-Chip and photo ID. NexWatch 7/28/2003 Rev A Access Control System

50 b. Design shall be prepared for smart chip insertion, color imaging on both sides and hole punch horizontal or vertical for using the card as a badge. c. Note: Active circuit type cards (those requiring batteries) shall not be acceptable. 2. Capacities: a. 2 Smart card shall be able to generate a minimum eight-digit access number. b. Cards shall have numeric encoded data embedded in an integrated circuit within the card. c. Each card shall be encoded so that it is unique and exists in no other system anywhere in the world. 3. Specifications: a. Dimensions: ISO standard size and thickness of 3.37 X X in (8.55 X 5.39 X cm). b. Material: Single-coil in PVC. c. Magnetic stripe material: single-layer 3M type 5203 High Coercivity, 4000 Oerstad using Track 2, without exception. d. Magnetic stripe dimensions: The stripe shall minimally extend from in. to in. from the upper card edge and for the entire length of the card. 4. Environmental: a. Temperature: 14 to 140 F (-10 to 60 C). b. Humidity: 0% to 100%. 5. Regulatory: N/A (Card is totally passive requiring no approval.) 6. Power: a. Source: Passive - powered by DigiReader digital proximity reader. 7. Communication: Via low-power radio frequency, providing read ranges up to [20] inches depending on the selected DigiReader. (see "DigiReader/Prox Card Read Range Matrix" in Part IV.1 for actual figures). 8. Manufacturer: NexWatch Model: QuadraKey.] E. [Magnetic Stripe Card ISO/ABA format: 1. General: The ISO/ABA format magnetic stripe card shall conform to the ISO/ABA standards for size and encoding characteristics. 2. Capacities: a. Each card shall support up to 40 digits in an ISO/ABA format on track two of the magnetic stripe. b. The information contained in the 40 digits shall include at least a 4- to 8-digit number for identification or access purposes. c. Additional information can include a site code (4 digits) and an expiration date of month and year (4 digits). 3. Specifications: a. Dimensions: X X.030 in. (5.4 X 8.57 X.07 cm) b. Construction: Polyester and appropriate adhesive-based materials. c. Magnetic stripe material: Single layer 3M type 5203 High Coercivity, 4000 Oerstad using Track 2, without exception. d. Magnetic stripe dimensions: From in. to in. minimum from the upper card edge and for the entire length of the card. e. Photo ID ready: Photo ID Badge shall be available as an add-on to all magnetic stripe systems. It uses the NexSentry Imaging Solutions system with ANSI X encoding. 4. Environmental: a. Temperature: -30 to +122 F (-35 to 50 C). NexWatch 7/28/2003 Rev A NexSentry Access Control System

51 b. Humidity: 5% to 95% relative humidity. 5. Communication: Via physical read by a Magnetic Stripe Reader. 6. Manufacturer: NexWatch 7. Model: ISO/ABA Magnetic Stripe Card].6 POWER A. Power Supply (PI-1) Power Inserter: 1. General: Uninterruptable power source module shall provide low voltage DC power. It shall also support optional external lead acid batteries to maintain all controller operations for at least 4 (four) hours in event of power failure. 2. Capacities: a. 28 volt DC output to Controller, MIROs and Readers. b. Limited lock power output at 24 Volts DC. c. 5 ampere output current. d. Power failure output. e. Battery charger output. f. Additional power supplies may be required based upon system configuration of other devices and wiring distances. 3. Specifications: a. Dimensions: 12 X 5.25 X in. (31 X 13.4 X 9.5 cm). 4. Environmental: a. Humidity: 10% to 90% non-condensing. b. Temperature: 20 to +120 F (-7 to +49 C). 5. Regulatory: UL 1012 or 1310 and CSA or cul listed. a. NOTE: The PI-1 Power Inserter is required when configuring NexSentry with a keypad and/or digital readers to meet FCC requirements. 6. Mounting: Power supply should be installed in a secure area at least two feet from the Controller. 7. Power: 115VAC/60Hz source. 8. Wiring: a. Power Supply shall be connected to the controller and keypad network wiring via twisted pair wire (shielding optional) of at least 18 AWG. b. Connectors: Phoenix-type. 9. Feedback: A single LED indicates power ON condition. 10. Self-protection: PI-1 shall send a POWER FAIL signal to the controller. 11. Manufacturer: NexWatch 12. Model: PI-1, or other manufacturer-approved device..7 ACCESSORIES: A. [Terminal: 1. General: An optional terminal shall be a standard video display terminal (CRT) with full keyboard and display. It may be connected to the Terminal Port of any Controller for monitoring and/or override control. 2. Throughput: Terminal shall be capable of data throughput at 300 through 115,200 baud. 3. Plans: NexWatch Dealer shall furnish as shown on plans. NexWatch 7/28/2003 Rev A Access Control System

52 4. Manufacturer: As determined by NexWatch Dealer.] B. [Printer: 1. General: Printer shall be standard RS-232 serial communications printer. 2. Throughput: Printer shall be capable of data throughput at 300 through 115,200 baud. 3. Plans: NexWatch Dealer shall furnish as shown on plans. 4. Manufacturer: As determined by NexWatch Dealer.] C. [Modem: 1. Baud Rate: 9600, 19, 200, 38, 400 baud as required by system environment. 2. Regulatory: FCC registered, UL listed. 3. Manufacturer: NexWatch, US Robotics (3-Com) or equal.] D. [Locking Hardware: 1. NexWatch Dealer shall furnish all system electrified locking hardware as shown on plans and which is used in conjunction with access control and security management system.] E. [Switches: 1. Provide all necessary monitoring and manual switches as shown on plans and which are used in conjunction with access control and security management system.] F. [External UPS batteries: 1. Provide necessary batteries to be used with UPS power supply to maintain all controller operations and provide limited DC lock power at either 12VDC or 24VDC.] PART III EXECUTION.1 INSTALLATION A. General: 1. The access control and security management system shall be installed and wired completely as shown on the plans by a trained and authorized NexWatch Dealer. 2. NexWatch Dealer shall make all necessary wiring connections to external devices and equipment. 3. The contractor shall install all system components and appurtenances in accordance with the manufacturer s instructions, and shall furnish all necessary interconnections, services, and adjustments required for a complete and operable system as specified and shown. Control signal, communications, and data transmission line grounding shall be installed as necessary to preclude ground loops, noise, and surges from adversely affecting system operation. Required mounting hardware shall be provided. B. Schedules: 1. NexWatch Dealer Preparation: a. Data Requirements. b. Operators & privileges. c. Access Hardware. d. Card readers and/or keypads. e. Monitor Points. f. Card holders. g. Card holders access codes. h. Maps. NexWatch 7/28/2003 Rev A NexSentry Access Control System

53 i. Prepare room for system installation. j. Receive equipment. 2. System Installation: a. Security management hardware. b. On-site commission of NexWatch Dealer and manufacturer (when ordered). c. Initial startup and verification. d. Data entry. e. Data entry listing & verification. 3. Verify Installation: a. Connect access control hardware to security management system. b. Data downloaded and correct operation verified. c. Total access and management system. d. Sample Reports. e. Daily Operation and Monitoring. f. NexWatch Dealer delivers as-built drawings. C. Telephone Lines: 1. The owner shall arrange for dedicated or dial-up telephone lines for the telecommunications equipment as shown on the plans. 2. Each telephone line shall be terminated in an RJ-11 telephone jack. 3. Note: Any connections to the public telephone system require notification of the local telephone company. See specific instructions in manual for modem used. D. Field Quality Control: 1. Tests: a. The selected NexWatch Dealer shall supply a proposed acceptance test procedure. b. Testing the system shall be the sole responsibility of the NexWatch Dealer. c. Communications tests: 2. Inspection: 1) Controllers to NexSentry Manager server. 2) NexSentry Manager server to client. 3) Remote dial-up support. a. The selected NexWatch Dealer shall provide an on-sight, factory-trained technician to assist, advise or manage installing personnel. b. The manufacturer shall make available on-site inspection. c. All final connections shall be made under the direct supervision of the NexWatch Dealer. 3. Field Service: a. A NexWatch Dealer, authorized by the manufacturer, shall provide first line support for both the hardware and software properties of the selected system. b. NexWatch Dealer shall in turn be provided second line support directly from the manufacturer, or manufacturer s OEM, for all component and computer hardware, and all operating and application software which comprise the complete system. c. NexWatch Dealer shall determine and report all problems to the manufacturer s customer service departments. d. Support shall be available to the integrator via the following methods: NexWatch 7/28/2003 Rev A Access Control System

54 1) Telephone inquiries. 2) Direct dial-in to the customer system for remote system troubleshooting by a qualified Field Service Engineer. 3) On-site visits if required, upon approval by the manufacturer's Customer Service Manager. e. Manufacturer shall provide reliable field service support for the computer hardware utilizing Hewlett-Packard service. f. A complete DELL On-site Warranty/Service Agreement is provided with each standard system utilizing DELL computer hardware. This agreement shall provide complete on-site service with a one-day response time guaranteed, from Monday through Friday, 8:00 am to 5:00 p.m. from a local DELL Service Center. g. Extended and peripheral service and maintenance agreements shall be available for purchase by the customer. 4. On-Site commissioning and/or training: a. The manufacturer shall provide direct participation in the On-Site Commissioning (OSC) activity of new systems, in conjunction with the dealer. b. The OSC shall provide the systems integrator with the manufacturer s expertise on installing, configuring and commissioning the system to the customer s specific requirements; and to provide on-site training on system operation and administration. c. On-site factory training shall be available for System Administrators, Operators and other qualified personnel. d. The OSC shall include the following: E. Documentation: 1) Hardware set-up and test. 2) Communication configuration and test. 3) Preventative maintenance and troubleshooting training for the systems integrator. 4) End-user training. 5) Database configuration and build assistance. 1. Accurate as built drawings shall be furnished by the NexWatch Dealer to aid the owner in programming. These should indicate the door(s) controlled by each lock output, the monitoring points for the door controlled area, and any relay outputs or special inputs into the system. 2. The NexWatch Dealer shall supply operating and maintenance manuals to aid the owner in the programming of the system..2 SERVICE AND SUPPORT A. Startup: 1. After the system has been installed, the documentation delivered to the owner and the telephone lines are operational in compliance with Part III.1 above, the NexWatch Dealer shall verify correct operation of all system components. 2. The NexWatch Dealer shall guarantee all material and workmanship involving the system for up to [ ] year after startup. B. Training: 1. After system startup, the NexWatch Dealer shall instruct owner s personnel in how to program the system. 2. On-site training from manufacturer shall be available. 3. Manufacturer-direct training shall be available through University of Security Electronics, Fremont, CA. C. Warranty Support: 1. The authorized NexWatch Dealer shall be available during the warranty period to answer programming and application questions to support owner s personnel during this period. 2. [Authorized NexWatch Dealer shall have capability to have a remote terminal for programming the Controller to support the owner s personnel during this period. The owner s system shall include a modem, necessary cabling and telephone extension to support this telecommunications operation.] 3. [Authorized NexWatch Dealer shall have the training and capability to provide additional support services including: NexWatch 7/28/2003 Rev A NexSentry Access Control System

55 a. Regular testing and inspection of all system components and to submit reports on the results. b. Emergency service for repairs and adjustments to the system and part replacement if necessary.] 4. Software Maintenance contracts (various levels available). NexWatch 7/28/2003 Rev A Access Control System

56

57 PART IV APPENDIX NexWatch 7/28/2003 Rev A A Access Control System

58 NexWatch Mission Falls Court Fremont, CA (510) NexWatch 7/28/2003 Rev B A NexSentry Access Control System