User manual NAPCO CARDACCESS 3000 ARCHITECTURAL AND ENGINEERING SPECIFICATION V2.7

[. . . ] CardAccess® 3000 Architectural & Engineering Specification Version 2. 7 Continental Access A Division of the Napco Security Group 355 Bayview Avenue Amityville, New York 11701 Phone (631) 842-9400 Fax (631) 842-9135 www. continentalaccess. net ARCHITECTURAL AND ENGINEERING SPECIFICATION, v 2. 7 1 PREFACE The Continental Access CardAccess 3000 Architectural & Engineering Specification is designed to serve as a guide for specifying a Continental Access state of the art integrated Access control, alarm, security, video management system. This document is available free of charge in both printed form and electronic media. CardAccess 3000 CardAccess 3000 will be a full-featured enterprise class access control solution, providing a scalable solution from stand-alone entry level through networked world class enterprise systems. This multi-tiered systems approach will provide for modular expansion and growth as required, and is designed to provide cost-effective system with expansion and functional enhancements. Key Features · A seamless integrated interface for Access Control, Alarm Monitoring, DVR/NVR Interface, Visitor Management Control, Time and Attendance/Payroll Functions, Photo Badging, Import/Export Utilities, Email/SMS Notification, Threat Level Management, Napco Security/Fire Interface and Open API support. 26 to 200 bit card formats plus FIPS 201-1 and NIST 800-116 compliancy. [. . . ] These formats will allow for the use of several card technologies, simultaneously. Alternately, the system shall support 100, 000 system facility codes per panel with Facility Code/Badge Concatenation. Alarm Monitoring Management and Alert Processing: 1. The system shall support 99 levels of alert priority. The system administrator will be able to assign these priorities uniquely to any alert or event in the system. The administrator may partition the events by user. Only events from the panels and readers in the operators' partition will be viewable. Each priority will be uniquely identified by color that is hard-coded in the software. The alert display screen will be divided into two sections. Those alerts requiring intervention by the system operator will be placed in the `Pending Alerts Grid'. These events will remain in the Pending Alerts grid until such time the operator makes a determination, or the system Auto-Acknowledge function determines that the event should be automatically acknowledged by the system. When an event is auto-acknowledged, the system will append to the event record the date and time the event was auto-acknowledged, the operator that was logged on, and an indicator that the event was auto-acknowledged. Alerts not requiring operator intervention will be placed directly in the `Events Grid'. The Events grid allows the operator to view the current and past events. The system administrator will be able to force the operators to enter a response for each event the operator processes. The administrator may predefine response messages which the operator may choose from, or the operator can enter his/her own response. The Events grid will contain button controls for sorting and viewing of events. Recent: This button will display the most recent / latest events. (This can be set per user). ARCHITECTURAL AND ENGINEERING SPECIFICATION, v 2. 7 28 b. Browse Mode: Once the user has logged in, the system shall automatically put the Events grid in Browse. This mode will `freeze' the event screen for browsing. Previous/Next: When sorting on a header there will be two buttons (PREVIOUS) and (NEXT). [. . . ] The contractor shall provide all personnel, equipment, instrumentation, and supplies necessary to perform all testing. Written notification of planned testing shall be given to the owner at least fourteen (14) days prior to the test, and in no case shall notice be given until after the contractor has received written approval of the specific test procedures. Test procedures shall explain in detail, step-by-step actions and expected results demonstrating compliance with the requirements of the specification. Test reports shall be used to document the results of the tests. [. . . ]