Facility Commander Wnx 7 7 AE Specification RevA2

UTC Fire & Security 9 Farm Springs Road Farmington, CT 06034-4065

[AUTHOR] [FILE NAME]

ACCESS CONTROL SYSTEMS AND DATABASE MANAGEMENT 28 13 16

LENEL CONFIDENTIAL INFORMATION – For use by Lenel-authorized VARs, prospective or existing Facility Commander Wnx users and their respective authorized consultants. All other third-party use is prohibited without Lenel’s written permission.

FACILITY COMMANDER™ WNX 7.7 January 2012 A&E SPECIFICATIONS DIVISION 28 ELECTRONIC SAFETY AND SECURITY LEVEL 1 28 10 00 ELECTRONIC ACCESS CONTROL AND INTRUSION

DETECTION LEVEL 2 28 13 00 ACCESS CONTROL LEVEL 3 28 13 16 ACCESS CONTROL SYSTEMS AND DATABASE

MANAGEMENT LEVEL 4 28 13 16.00 NOT APPLICABLE LEVEL 5 28 13 16.00.FCW77 FILE REFERENCE ONLY This A&E Specification conforms to CSI MasterFormat 2004 guidelines. The bold highlighted level above identifies the level this specification meets in the CSI MasterFormat hierarchy. Feel free to consult with UTC Fire and Security regarding specific project requirements. For information and assistance contact:

UTC Fire and Security 791 Park of Commerce Blvd., Suite 100 Boca Raton, FL 33487 Tel: (561) 998-6100 U.S.A. Toll Free: (800) 428-2733 Fax: (561) 994-6572 Internet: http://www.utcfireandsecurity.com

DOCUMENT NOTES

Warranty Information: Product is warranted by the manufacturer for 12 months from the date of shipment to the dealer or integrator from the manufacturer. The warranty statement provided in Part 1 is an example of requirements to the installing contractor and may not directly represent the product. This document was created in Word 2007 and may lose some formatting when converted to earlier versions or to other programs. Please review the PDF version should formatting errors appear. To delete this cover page (Word 2007 or later): Click the Insert tab, click Cover Page in the Pages group, and then click Remove Current Cover Page.

http://www.utcfireandsecurity.com/

LENEL® - A UTC FIRE & SECURITY COMPANY FACILITY COMMANDER™ WNX 7.7 GUIDE SPECIFICATIONS [PROJECT NUMBER] [DATE]

[PROJECT NAME] [PROJECT LOCATION]


TABLE OF CONTENTS

PART 1 GENERAL .................................................................................................................................... 1

1.1 SUMMARY .................................................................................................................................... 1 1.2 REFERENCES .............................................................................................................................. 1 1.3 SUBMITTALS ................................................................................................................................ 1 1.4 CLOSE-OUT SUBMITTALS .......................................................................................................... 1 1.5 WARRANTY .................................................................................................................................. 1

PART 2 PRODUCTS ................................................................................................................................. 3

2.1 OWNER FURNISHED EQUIPMENT ............................................................................................ 3 2.2 SYSTEM ........................................................................................................................................ 3 2.3 PERFORMANCE CRITERIA ........................................................................................................ 4 2.4 SOFTWARE OPTIONS ............................................................................................................... 22

PART 3 EXECUTION .............................................................................................................................. 24

3.1 INSTALLERS .............................................................................................................................. 24 3.2 EXAMINATION............................................................................................................................ 24 3.3 PREPARATION........................................................................................................................... 24 3.4 INSTALLATION ........................................................................................................................... 24 3.5 QUALITY CONTROL .................................................................................................................. 25 3.6 SYSTEM STARTUP .................................................................................................................... 25 3.7 CLOSEOUT ACTIVITIES ............................................................................................................ 26

LENEL® - A UTC FIRE & SECURITY COMPANY FACILITY COMMANDER™ WNX 7.7 GUIDE SPECIFICATIONS [PROJECT NUMBER] [DATE]

[PROJECT NAME] [PROJECT LOCATION]


ACCESS CONTROL SYSTEMS AND DATABASE MANAGEMENT 28 13 16


SECTION 28 13 16

PART 1 GENERAL

1.1 SUMMARY

A. Section Includes 1. Integrated Security Management System Performance Requirements 2. Integrated Security Management System Operator Workstation Requirements

B. Related Requirements

1. Integrated Systems and Options a. 28 06 00 Schedules for Electronic Safety and Security b. 28 13 00 Access Control (exclusive of this section) c. 28 20 00 Electronic Surveillance d. 28 30 00 Electronic Detection of Alarms

2. Related Sections a. 26 33 53 Static Uninterruptible Power Supply b. 27 20 00 Data Communications

1.2 REFERENCES

A. NFPA 70 - National Electrical Code B. NFPA 101 - Life Safety Code C. UL 294 - Access Control Systems D. UL 1076 - Proprietary Burglar Alarm Units and Systems E. Americans with Disabilities Act - Public Law 101.336 F. FCC

1.3 SUBMITTALS

A. Single-line block diagram showing all related equipment interfaces B. Manufacturer technical data sheets C. Shop Drawings D. Software: 1 set of fully functional software in manufacturer’s original media packaging

1.4 CLOSE-OUT SUBMITTALS

A. Maintenance Contracts B. Operation and Maintenance Data/Manuals C. Warranty Documentation D. Record Documentation E. Software F. Commissioning Documentation and Check-Off List G. As-Built Drawings H. Training Course Materials I. Training Presentations J. Training Class Video Files

1.5 WARRANTY

LENEL® - A UTC FIRE & SECURITY COMPANY [PROJECT NUMBER] [DATE]

FACILITY COMMANDER™ WNX 7.7 GUIDE SPECIFICATIONS [PROJECT NAME]

[PROJECT LOCATION]


ACCESS CONTROL SYSTEMS AND DATABASE MANAGEMENT 28 13 16 - 2


A. Warranty

1. Warrant system against defects and workmanship for one (1) year, covering all parts and labor, from date of product shipment.

2. Assign all manufacturer warranties beyond the initial one year period to the owner. 3. Guarantee all application software/firmware is manufacturer supported. 4. Perform all manufacturer recommended preventative maintenance on all related

components and/or devices. 5. The Security Contractor shall be the primary contact and respondent for all service and

support and officially recognized and backed by the system manufacturer.

B. Special Warranty 1. Provide a separate proposal for extended warranty and maintenance service contract for

owner consideration. 2. One (1) year agreement. 3. Submit payment terms and conditions with proposal.



[PROJECT LOCATION]




PART 2 PRODUCTS

2.1 OWNER FURNISHED EQUIPMENT

A. Virtual Host 1. Configured to minimum requirements for memory and disk space allocation specified by

system edition and capacity

B. Host Computer or Server: 1. 2.x GHz dual processor (Dual or Quad Core) 2. 4 GB RAM 3. CD-RW/DVD 4. 80 GB HD, Raid-1 or Raid-10 Configuration 5. 19-inch flat panel display, supporting 16-bit high color at 1024 x 768 resolution 6. 10/100/1000 Mb Ethernet Network Interface Card 7. Standard 101-key keyboard and 2-button wheel mouse

C. Operator Workstation (Minimum Requirements):

1. 2.x GHz dual processor (Dual or Quad Core) 2. 2 GB RAM 3. CD-RW/DVD 4. 80 GB HD 5. 19-inch flat panel display, supporting 16-bit high color at 1024 x 768 resolution 6. 10/100/1000 Mb Ethernet Network Interface Card 7. Standard 101-key keyboard and 2-button wheel mouse 8. Integrated sound with speakers

D. Host Server Software:

1. Virtual Host Platform a. VMware® or Hyper-V™ environments

1) EMC VMware Infrastructure Enterprise 2) Microsoft Virtual Server 2008 with Hyper-V

2. Professional Class Platform a. Operating System: Microsoft Windows XP SP3, Windows 7 (32-bit or 64-bit) b. Database: Microsoft SQL Server 2008 Express SP1 (32-bit or 64-bit)

3. Enterprise Class Server Platform a. Operating System: Microsoft Server 2008 R2 SP1 (64-bit) b. Database: Microsoft SQL Server 2008 R2 (32-bit or 64-bit)

E. Operator Workstation Software: 1. Operating System: Microsoft Windows XP SP3, Windows 7 (32-bit or 64-bit)

2.2 SYSTEM

A. Manufacturer

1. Provide all system access control software and related hardware as standard catalog product offering of a single manufacturer.

2. Exception: Servers, workstations, and related computing peripherals shall be specified characteristics that are in regular production by an industry recognized computer manufacturer, provided that replaceable components are available from multiple third-party sources.

3. Exception: Controlled devices, such as electric locks, door actuators, sensors, etc., are specified elsewhere.



[PROJECT LOCATION]




4. This specification is based on Facility Commander Wnx 7.7 software manufactured by UTC Fire & Security; 791 Park of Commerce Boulevard, Boca Raton, FL 33487 USA. Tel: (561) 998-6100. Fax: (561) 994-6572. http://www.utcfireandsecurity.com.

B. Description 1. The system is an integrated security management system that combines detection devices,

intelligent data gathering panels and peripherals, output devices, and supplemental operating software programs into a unified functioning system.

2. Provides management, control, and monitoring of access and alarm components. 3. Installed system database and application host server software. 4. Installed operator workstations. 5. Integration to related software and hardware. 6. Setup and configuration of communication between the host server, operator workstations,

and control panels. 7. Setup and configuration of system application and database.

2.3 PERFORMANCE CRITERIA

A. System Architecture: 1. Microsoft Windows-based, scalable client/server application integrating multiple security

functions including management, control, and monitoring of: a. Access control b. Alarm management c. Photo ID badge making d. Video surveillance interface e. Interfacing with secondary security subsystems f. Interfacing with business database applications

2. Operational on the Microsoft Windows XP SP3, Windows 7, Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 operating systems a. Multi-user capability b. Multi-tasking capability c. True 32-bit multi-threaded code set d. Supported on 32-bit or 64-bit server deployments

3. Database a. Microsoft SQL Server 2005 and SQL Server 2008 b. 32-bit or 64-bit server deployments c. Allow separation of database, file and application server roles d. User definable record-level database partitioning e. Support open direct database connectivity

1) Import cardholder and card ID data from external systems 2) Import cardholder and card ID data from database applications

f. Facilitate interfacing 1) Real time and batch processing of data via ODBC, JDBC or OLE DB over a

network connection 2) Insert, update, and delete record information 3) Automatic download of data to control panels based on database changes 4) Provide audit trail in the operator history/archive database for all database

changes initiated by the user interface 4. Support operating in a Microsoft SQL Server Cluster where the application server(s) support

a shared database cluster 5. Support database and file replication

a. Using Microsoft SQL Server Replication Services and Microsoft File Replication Services

b. Provide distributed database replication across multiple system application servers

http://www.utcfireandsecurity.com/



[PROJECT LOCATION]




c. Allow for system expansion and delivering N-tiers of server redundancy d. Database and file replication shall not require any proprietary database or file

replication software 6. Standard TCP/IP networking communication protocol between application server, client

workstations, control panels, video surveillance system(s) and database subsystems a. Support 10/100/1000 Mb Ethernet connectivity over LAN/WAN network typologies b. Support systems with multiple network interface cards

7. Flexible and scalable architecture, permitting expansion of both capacity and functionality with software licensing and/or software upgrades

B. System Redundancy and High Availability

1. Provide multiple levels of communication redundancy and failover a. Hosted controllers b. Digital video recorders c. Client workstations

2. Manually re-route communication to alternate system computers across the system 3. Single application/database server configuration redundancy and failover

a. Network attached devices shall have one or more alternative communication server(s) b. Manually re-route network-attached devices to designated backup c. Provide continuous system operation without loss of alarm and event transaction d. Redirect network-attached devices to their default primary servers upon primary server

restoral 4. Multiple regional application/database server configuration redundancy and failover

a. Support the same level of communication redundancy and failover for network-attached devices per regional application/database server

b. Permit spanning across regional application/database servers c. Client workstations shall failover to their designated backup regional

application/database server d. Redirect workstations to their default regional application/database server when server

functions are restored e. Manually update and synchronize the regional application/database server upon

server restoration

C. System Functions 1. Monitor and record card access, alarm, and operator activity to an online history/archive

database for reporting. 2. Display real-time system status and data at all operator workstations. 3. Visually and audibly annunciate alarms upon change of status, for assessment and response

at all operator workstations. 4. Monitor status and record activity transactions of all secured areas and alarm input/output

points. 5. Manage and automatically download all database changes made at all operator workstations

in real-time to control panels requiring notification of the specific database changes or updates.

6. Perform network deployed software updates, manually or automatically. 7. Employ distributed processing technology, allowing the host to function almost entirely as an

application/database server. a. The majority of the real-time, day-to-day decisions shall be made locally by intelligent

control panels. b. The control panels shall be the direct field interface for all access control, alarm

sensing, and input/output-controlled devices.

D. System Capacity: 1. Provide for a minimum of 25,000 access control cards, upgradeable to 500,000 without

restriction.



[PROJECT LOCATION]




2. Provide for an unlimited number of access events, alarm events, and operator transactions. 3. Must be capable of centrally storing a minimum of 1,000,000 historical events (transactions)

online. 4. Support the designated capacities per application/database server, and be upgradeable to

support the same capacity for up to 64 synchronized application/database servers in a multi-server configuration.

Autonomous Control Unit

(ACU) deployment Micro deployment

Definable Time Schedules 2551 Unlimited Concurrently Active Time Schedules 2551 1,024 combined time

schedules and interval

Access Rights Unlimited2 on host Unlimited2 on host 96 per reader 96 per badge

Concurrent Workstations (Log-ins) 100 100 Control Panels 4,096 4,096 Access Readers 16,384 20,480 General Purpose Alarm Inputs 16,384 16,384 General Purpose Relayed or TTL Outputs 4,096 4,096 1 – With 16 individual intervals 2 – Per card, per control panel

E. Operator Interface:

1. Use a single Windows-based client user interface for system configuration, administration, management, and monitoring operations

2. Provide a mouse-driven, Windows-based graphical user interface allowing operator(s) to open and work on multiple windows simultaneously, at client workstation(s) with minimal degradation to system performance

3. Support menu and toolbar customization a. Allow any operator to add or remove system application icons to the Application

Toolbar for applications the operator has permission to access, which is used to help personalize the operator’s system desktop

b. Allow operators with permissions to add or remove the External Application Toolbar in addition to allowing the assignment of generic icons with a specified execution string for launching external applications or command scripts

c. Allow operator to use right-click navigation to related forms 4. Provide online context-sensitive help files to facilitate operators in system configuration and

operation a. Support standard Windows help commands

1) Contents 2) Search 3) Back 4) Print

5. Implement National Language Support (NLS), allowing simultaneous multi-lingual operation. a. Language selection per individual operator language preference b. Graphical user interface and online help shall be in English and [Spanish] [French]

[Portuguese] [Dutch] [Italian] [German] [Russian] [Arabic] [Korean] [Japanese] [Chinese Simplified] [Chinese Traditional]

6. Support defining an unlimited number of operators a. Application access via workstation restricted by operator login and password

1) Operator passwords shall be encrypted and stored in the database 2) Password configuration shall support IT Department password strength rules

b. Configurable operator profiles



[PROJECT LOCATION]




1) Form level permissions 2) Tab level permissions (for person, alarm monitor, and manual control only) 3) Image capture and print permissions 4) “Remove all” and “remove individual” permissions on alarm monitor 5) Permission control for External Application Toolbar 6) Database partition views 7) Language preference

7. Allow operator authentication through an Active Directory Server a. Bypass system storing passwords b. Operator access shall be defined within the system configuration forms

8. Support the use of thin client application deployment to provide remote access to the Operator Interface a. Thin client application support using a standard Web browser

1) Standard Microsoft Terminal Services 2) Citrix® MetaFrame® XP 3) Microsoft Virtual Terminal Services

F. Cardholder Management:

1. Provide an operator interface for enrollment, modification and deletion of cardholder data and access control information

2. Allow enrollment in advance without requiring access card assignment a. Cardholder personnel information b. Cardholder access control information

3. Allow selection of multiple cardholders and badge records in applying mass changes 4. Provide cardholder data and area access information including the following data:

Cardholder Data Fields First Name Middle Name 1 Middle Name 2 Last Name Address 1 (User-definable label) Address 2 (User-definable label) Address 3 (User-definable label) Address 4 (User-definable label) Address 5 (User-definable label) Phone Number Employee Number Personnel Type1 Department2 Facility (User-defined list)3 Access Rights (Multiple Assignments) Threat Level Access Clearance4 Access Cards (Multiple Assignments) 90 User-definable fields 1 – User-defined selectable list – list could include at a minimum, Permanent, Temporary, Contractor, and Visitor Personnel Types 2 – User-defined selectable list 3 – Selectable from database partition views 4 – Selectable from Normal, Low, Medium, High

5. Allow cardholder configuration to initiate extended unlock or sense function on designated

access control doors 6. Support the ability to enforce assignment of a single active credential per database record

G. Card ID Management:



[PROJECT LOCATION]




1. Provide an operator interface for enrollment, modification and deletion of access card ID data 2. Allow enrollment in advance without requiring assignment to a cardholder 3. Provide card information including the following data:

a. Description b. Badge ID number (unique 4 to 20 digit identifier) c. PIN (4 digit Personal Identification Number) d. Status (Issuable, Active, Suspended, Lost, Remake) e. Assigned Cardholder (Selectable from predefined list of cardholders) f. Issue Date (Automatically activate ID numbers at control panel level in real-time

without host notification) g. Return Date h. Expire Date (Automatically expire ID numbers at control panel level in real-time without

host notification) i. Extended unlock/sense time

H. Access Control Management:

1. Allow or deny based on validation of a cardholder’s assigned categories a. Access to secured areas b. Arm and disarm intrusion zones c. Output control via access control readers

2. Support defining an unlimited number of access rights in a manner that associates reader(s) with a specific time schedule a. The time schedule shall define the specific time(s) of day and day(s) of the week for

which access will be granted for the associated reader(s) and/or controlled output(s) 3. Allow cardholders to be assigned multiple categories and multiple access control cards

without requiring duplicate cardholder database entries a. Assigned cards shall automatically inherit all assigned access rights

4. Permit cardholder assignable threat level access clearance levels to override cardholder access rights

5. Allow threat levels to be changed per site a. Manually by operators b. Automatically based on alarm events

6. Suspend card access rights system-wide automatically upon one (1) to 999 consecutive days of inactivity

7. Monitor all secured areas and initiate alarm notification when reader controlled doors are breached

8. Allow secured doors to be open without generating an alarm condition upon a. Valid card read b. Exit request using egress device c. Door has been manually unlocked via authorized remote command

9. Enforce in/out badge use sequencing on designated doors a. Operate in global or local mode b. Function as anti-passback or time and attendance readers

10. Area anti-passback (APB) a. Support definition of system-wide operational mode for APB access grant requests b. APB Local c. APB Global Fail-Safe d. APB Global Fail-Secure

I. Time Schedule and Mode Management:

1. Allow an unlimited number of schedules defining time, day, and date intervals for automatic execution of system functions, events, and mode changes

2. Time schedules a. Start and stop interval(s) by time of day and day of week or mode b. Support multiple intervals per day



[PROJECT LOCATION]




c. Support multiple days per week d. Applicable to the following system functions:

1) Cardholder access rights to secured areas 2) Readers online/offline 3) Doors lock/unlock 4) Alarm monitoring on/off 5) Inputs enabled/disabled 6) Outputs on/off 7) Transaction routing for alarm and card activity

3. Event Schedules a. Define specific time(s) for events to occur by time of day and day of week or mode b. Support multiple events per day and multiple days per week c. Applicable to the following system functions:

1) Change reader modes of operation (a) Badge only (b) Badge and keypad (c) Badge or keypad

2) Change alarm monitoring sense times 3) Reset anti-passback and/or time and attendance IN/OUT status of all

cardholders in control panel databases 4) Initiate a scheduled dial from host to communicate to remote dial-up control

panels 4. Mode Schedules

a. Define specific times and dates for indicating to system control panels which time and event scheduled functions to execute

b. Support a minimum of four (4) distinct mode classifications for categorizing time and event scheduled functions

c. Mode classifications will include user Normal plus three (3) definable modes such as holiday, evacuation, lock-down, etc

d. Mode changes can be scheduled to occur at a specific date and time or manually changed by an operator

e. Mode changes can be automatically changed based on alarm events

J. Card Reader / Door Control: 1. System shall allow access control readers to be individually configured for different

applications and modes of operation 2. Physical/Logical Reader Configurations:

a. Physical Reader: 1) Mode of operation shall be operator adjustable for modifying the security access

level at a designated point (a) Badge Only (b) Badge and Keypad (c) Badge or Keypad

2) Manual mode change shall operator initiated 3) Automatic mode change via a system event schedule

b. Logical Reader: 1) Each reader’s logical mode of operation shall be configurable to support the

following: (a) Normal access control operation (b) Anti-passback

(1) IN (2) OUT (3) Configurable to operate in enforced or passive mode

(c) Time and Attendance: (1) IN



[PROJECT LOCATION]




(2) OUT (3) Configurable to operate in enforced or passive mode

(d) IN Required (1) Configurable to operate in enforced or passive mode

(e) Elevator Control (f) Dual Credential Required

(1) When any two (2) valid credentials are presented, access shall be granted and both credential transactions shall be reported consecutively as individual Valid Open transactions

(2) If one (1) or both credentials are invalid, access shall be denied and both credential transactions shall be reported consecutively as individual Valid or Invalid No Passage transactions

(3) Required to be used in conjunction with Valid No Passage c. Configurable maximum unlock time after a valid card read from 0 to 59 minutes, 59

seconds d. Extended unlock time control

1) Valid card read shall activate rights to override the default unlock time (a) Specified command code will activate override (b) Keypad entry initiates two (2) to ninety-nine (99) minute delay

2) Local alarm indicating a door held condition will commence sixty (60) seconds prior to shunt expiration

e. Configurable alarm sense time after a valid card read for a door to remain open, before signaling a door held open alarm, from 0 to 61 minutes, 59 seconds 1) Configurable pre-alarm during a door held open condition to signal locally for a

specified amount of time prior to alarm transmission f. Configurable door relock after a valid card read shall support the following:

1) Lock on duration 2) Lock on open 3) Lock on close

g. Each reader shall operate in multiple states, operator changed manually or changed automatically under a time of day and day of week schedule 1) Default online 2) Offline

h. Each door shall operate in multiple states, changed automatically under a time of day and day of week schedule 1) Default locked 2) Unlocked state

i. Automatic Unlock 1) Each door shall be configurable to automatically unlock under a time of day and

day of week schedule 2) Configurable to require a valid card transaction to execute

j. Normal access shall be granted with an alarm condition immediately transmitted to the system operator workstation(s)

k. Reader Transaction Routing: 1) Transactions for valid, invalid, and lost cards from each reader shall be

independently configured for default routing to history/archive, system printer, and/or all operator workstations

2) Valid card transaction from each reader shall be independently configured to support routing under time of day and day of week schedule to history, system printer, and/or all operator workstations

3. Toggle Card Reader Control: a. Designated card readers shall support switching states upon valid transaction b. Lock or unlock associated door c. Enable or disable associated alarm points



[PROJECT LOCATION]




K. Elevator Control 1. System shall integrate with elevator controls, providing multiple configuration options 2. Elevator Cab Access

a. Authorized badges shall cause the system to illuminate and enable elevator call buttons

3. Floor Access a. Readers located in each elevator cab shall permit designated floor buttons to be

enabled upon activation from an authorized badge b. Control of a maximum of 64 floors serviced by an elevator cab shall be available. c. Floor access shall be configurable to operate with or without floor tracking

1) Cardholder badges presented to the elevator cab card reader shall initiate the elevator controls corresponding to the user access rights

2) Controls will be ‘available’ for a user-definable length of time to allow selection 3) Floor tracking

(a) Authorized badges shall activate the reader keypad (b) User shall manually enter a two (2) digit floor code (c) Transaction is recorded in the card history/archive database

4) No floor tracking (a) Authorized badges shall enable designated floor buttons (b) User shall manually select floor button

L. Input and Output Control

1. System shall allow input and output points to be individually defined, configured, and controlled.

2. Input Points: a. User-configurable for specific applications.

1) Alarm - digital input used to trigger an alarm and any selected output. 2) Digital Output - digital input used to trigger a selected output without alarm

notification. 3) Elevator - digital input used for elevator control. 4) Inactive - digital input is disabled.

b. Configurable sense time from 0 to 59 minutes, 59 seconds. 1) Sense time changes supported via event schedules.

c. Active state configured as open or closed. d. Configurable to control a primary and/or secondary output.

1) Input points configured for output control shall allow being enabled or disabled via time schedule. (a) The primary output shall be configurable to follow the input point’s state

change or activate for its defined output duration. (b) The secondary output shall be configurable to follow the input point’s

state change or remain activated until manually reset or scheduled off. 3. Output Points

a. Configurable duration time from 0 to 64 seconds. b. Active state to be configured as on or off. c. Automatically controlled via time schedule to turn on or off. d. Allow grouping to facilitate activating multiple output points, on or off, via time

schedule. e. Output points, including reader controlled doors, shall allow manual control by

authorized operators in the following manner: 1) Activate/unlock for duration. 2) Activate/unlock indefinitely. 3) Deactivate/Lock. 4) Schedule override. 5) System shall require a text entry explaining reason for manual operator control

to be recorded in operator history/archive database.



[PROJECT LOCATION]




M. Intrusion Zone Control:

1. Define local intrusion zones that consist of: a. One or more access control readers b. One or more alarm inputs c. An input point to designate for arming and disarming d. An output point to designate for arming and disarming

2. Arm or disarm intrusion zones by: a. Access control reader, using card and keypad

1) Deny cardholders access unless the intrusion zone is disarmed 2) Flash LED indicators on readers assigned to an intrusion zone to annunciate the

intrusion zone status 3) Configurable time delay shall allow user to exit the intrusion zone before the

zone is armed 4) Card permissions will include intrusion zone control authorization 5) Users will enter keypad information to initiate arm or disarm function prior to

presenting access card (a) Authorized users with active access rights and arming rights

(1) Arm intrusion zone (2) Take associated intrusion zone readers (other than the arm/disarm

reader) offline (3) Associated intrusion zone inputs will be monitored on (4) Generate an output based on the arm event (5) Generate a history record of the event

(b) Authorized users with active access rights and disarm rights (1) Disarm intrusion zone (2) Return associated intrusion zone readers to normal operation (3) Associated intrusion zone inputs will be monitored off (4) Generate an output based on the disarm event (5) Generate a history record of the event

6) Access will be denied to users with active access rights who do not have intrusion zone disarm rights when the zone is armed, and a history record shall be generated

b. Manual Operator control 1) Authorized operators can manually arm or disarm an intrusion zone 2) Intrusion zones shall be partitioned to restrict operator access and control

c. Digital Input state change 1) Automatically arm/disarm by time schedule 2) Automatically arm/disarm by event 3) Automatically arm/disarm by mode schedule

N. Alarm Management

1. Define, configure, and control alarm conditions individually a. Configure if monitoring of the alarm is enabled or disabled

1) Allow alarm monitoring to be controlled manually by an authorized operator 2) Allow alarm monitoring to be controlled automatically via time schedule

b. Configure if operator alarm acknowledgement is required to clear it from the operator workstation alarm monitor

c. Define up to 20 levels for prioritizing alarm processing and display per alarm d. Configure alarms to trigger primary and/or secondary outputs

1) Configure the primary output to follow the alarm state change or activate for its defined output duration

2) Configure the secondary output to follow the alarm state change or remain activated until manually reset or scheduled off



[PROJECT LOCATION]




e. Allow grouping alarms to facilitate monitoring multiple alarms, on or off, via time schedule and changing alarm sense times via event schedules

f. Support regrouping alarms via event schedules, allowing alarms to be reassigned to different alarm groups

g. Configure if the alarm shall be routed to the history/archive database and/or printed on a host/server alarm printer

h. Route alarms to specific workstations on specific time schedules 1) If alarm is not responded to within a definable time period, shall be able to be

bumped to another workstation for acknowledgement i. User-definable instructions shall be assignable to each alarm, identifying alarm

assessment and response requirements, in the operator workstation alarm monitor 2. Alarm text and processing state shall be definable by color and by priority 0 - 19 to aid alarm

management 1) Foreground and background colors shall be designated from a palette of 256

colors (a) Alarm text defined for each type of alarm in the system (up to six (6) lines

of instruction per alarm) (b) Alarm text defined based on the operator processing state of the alarm,

that is, ALARM, and RESET 2) Alarm states

(a) Alarm (b) Reset (c) Cut (d) Short

3) Processing states (a) Unacknowledged (b) Acknowledged (c) Completed

O. Guard Tour Management

1. Configure access control readers and inputs to function as guard tour points. 2. Configure multiple readers and inputs into named guard tours, each definable with a

maximum tour duration time up to 480 minutes (8 hours). 3. Assign credentials for guard tours when tour points include access control readers. 4. Authorized operators shall be able to start, pause, re-start, and terminate a tour session. 5. Transaction Monitoring:

a. Report an alarm if the overall time for the tour expired before the tour was completed. b. Report transactions when tour points are hit. c. Report an alarm transaction if a tour point is hit more than once per tour.

6. Reporting: a. Provide tour configuration reports. b. Provide tour history reports.

P. System Monitoring 1. System shall provide multiple monitoring application windows at operator workstations.

a. Display real-time information of card access activity. b. Display real-time alarm activity. c. Display control panel status. d. Display operator workstation status.

2. Activity Monitoring a. Display card access and non-alarm event activity from online and active readers and

security devices configured to route to the monitor. b. Provide operator controls to clear, pause, and resume scrolling display of activity

transactions. c. Display activity transaction information.



[PROJECT LOCATION]




1) Transaction date and time. 2) Access Control Transactions:

(a) Valid (Access granted). (b) Valid Open (Access granted with door aperture confirmation). (c) Valid No Passage (Access granted with no door aperture detected). (d) Invalid (Access not granted). (e) Invalid PIN (Access not granted). (f) Max Invalid PIN (Access not granted, card suspended). (g) Suspended Card (Access not granted). (h) Lost Card (Access not granted). (i) Unknown Card (Access not granted). (j) Duress Valid. (k) Duress Invalid. (l) Duress Valid Open. (m) Duress Valid No Passage. (n) Anti-Passback IN Invalid. (o) Anti-Passback OUT Invalid. (p) Time and Attendance IN Invalid. (q) Time and Attendance OUT Invalid. (r) Floor selection for elevator control. (s) Valid floor. (t) Invalid floor.

3) Cardholder name. 4) Card ID number for unknown or unassigned cards. 5) Intrusion Zone Area Transactions:

(a) Zone Armed. (b) Zone Disarmed. (c) Arm/Disarm Failed, Zone Not Secure. (d) Arm/Disarm Failed, Invalid Access Right. (e) Arm/Disarm Failed, Not in Zone.

6) Guard Tour Transactions: (a) Tour Started. (b) Tour Ended. (c) Tour Activity Valid. (d) Tour Activity Invalid. (e) Tour Paused. (f) Tour Resumed.

7) Source device location description and reference. 8) Allow direct navigation from any event within the activity monitor to its related

call-up of live and recorded video. 3. Monitoring and Validation (Swipe and Show):

a. Following a credential transaction, the operator shall be able to observe a credential photo and text description of the transaction. An operator shall be able to monitor transactions and compare the photo ID to a live image.

b. Display credential photo and transaction information: 1) Photo. 2) Name. 3) Employee number. 4) Department. 5) Transaction type:

(a) Valid. (b) Invalid. (c) Unknown. (d) Area arm. (e) Area disarm.



[PROJECT LOCATION]




(f) Tour started. (g) Tour ended. (h) Tour started manually. (i) Tour ended manually. (j) Tour activity. (k) Invalid tour activity. (l) Tour paused. (m) Tour resumed.

6) Date/time. 7) Reader description.

c. Support four (4) lanes of traffic with last four (4) badges/photos displayed for each lane of traffic.

4. Alarm Monitoring: a. The alarm monitor shall display only those activities that have been assigned to an

operator’s permissions. 1) System shall allow alarms to be routed individually. 2) System shall allow multiple workstations to receive the same alarms. 3) Unassigned alarm activity shall be transmitted to every system workstation by

default. b. Pop-up alarm alert windows shall notify the operator of a new alarm occurrence.

1) Window shall beep and display notification dialogue. 2) Provide direct navigation from the notification dialogue to the alarm monitor.

c. Each alarm condition shall present specific data in the alarm window. 1) Priority. 2) Description. 3) Reference type or additional alarm information. 4) Alarm state:

(a) Alarm. (b) Reset. (c) Cut (Tamper supervision). (d) Short (Tamper supervision).

5) Process state: (a) Acknowledged. (b) Unacknowledged. (c) Completed.

6) Occurrence Count. 7) Host date and time. 8) Control panel date and time. 9) Predefined alarm instructions for operator assessment. 10) Entry for operator alarm response in free form text and from pick list of

predefined alarm responses. 11) Acknowledgement button.

d. Allow sorting on alarm monitor form columns. e. Positive action shall be required by the operator to acknowledge an alarm. All displays

shall indicate the acknowledged state. f. System shall allow a “specified” user to purge all alarms on a given alarm screen

regardless of their state. g. Operators shall be able to select and review pending alarms.

1) A pending alarm is an alarm that has been acknowledged, but the input point has not been reset.

2) Display corresponding operator details. 3) Display all information, date, time and the complete response.

h. Alarms in the “reset” state that have been acknowledged shall be automatically removed from the Alarm Monitor window.



[PROJECT LOCATION]




i. Allow direct navigation from any alarm within the alarm monitor to its related call-up of live and recorded video.

j. Allow direct navigation from any alarm within the alarm monitor to its related graphics map location.

5. Control Panel Monitoring: a. Provide real-time status and connectivity of system panels.

1) Display control panel properties. 2) Display firmware version. 3) Display communication status.

b. Provide remote management of system panels. 1) Remote reset. 2) Configure online/offline. 3) Force database downloads. 4) Update control Panel firmware.

6. Client Workstation Monitor: a. Provide real-time status and connectivity control of all servers and client workstations.

7. Alarm Graphics: a. Provide graphical map creation, editing, and real-time monitoring software for

command and control visualization of alarms and device states via user-configurable, multi-state device symbols or icons.

b. Graphical Map Creation: 1) Support creation and importing of images in JPG, GIF, or PNG file formats

imported as a single layer base map. 2) Support importing of multi-layer AutoCAD DXF R12 files.

(a) Allow selected layers to be imported. (b) Maintain layer separation within the system. (c) Permit the re-import of a DXF file or individual layers from the source file

without disturbing other layers and icons previously installed. 3) Define map layers that can be dynamically turned on or off while editing and

viewing during monitoring operations. 4) List maps alphabetically by facility in a navigation pane.

(a) Provide hyperlink icons that allow operators to navigate and traverse through a series of maps quickly.

5) Allow operator defined default maps to automatically display upon launching the alarm graphics monitor window. (a) The user shall be able to size the alarm graphics monitor window as

desired. (b) Maps, graphics symbols and icons shall maintain aspect ratios.

c. Represent system components on graphics maps for monitoring and control. 1) Areas, zones, cameras, client workstations, controllers, digital inputs, digital

outputs, digital video recorders, reader, control points, and command groups. 2) Allow a group of same or different devices to be represented by a single icon as

a control point, such that the group is treated as a single object for alarm status purposes.

3) Allow command group icons representing multiples of the same device type. (a) For executing a single command on all the devices in the group. (b) Command group icons can represent:

(1) All devices of that type on the map. (2) All devices of that type in a facility. (3) User-defined set of devices.

4) Provide a series of default icons and user-definable custom icons in JPG, GIF, animated GIF, and PNG file formats. (a) Variable sizes shall be supported in 16x16, 24x24, and 32x32 pixels.

5) Support two icon techniques for alarm visualization.



[PROJECT LOCATION]




(a) Overlay technique showing the state of the highest priority alarm on a device.

(b) Decoration technique for displaying multiple alarms simultaneously for a device.

d. Command and Control 1) The user shall be able to zoom in to the map using a mouse wheel or right

mouse click on a background point on the map. 2) The user shall be able to determine the state of each device by the icon’s

appearance, which shall change dynamically as alarms are set, reset, and cleared.

3) The user shall have right mouse button click access to the Alarm and Response Monitor from any symbol icon in an alarm state.

4) The user shall be able to initiate device control commands from a map using right mouse button click access of selected symbol icons. The control commands shall be device-type dependent, including but not limited to the following: (a) Area/Intrusion Zone – arm and disarm. (b) Cameras – launch live video. (c) Inputs – monitor on and off. (d) Outputs – activate on and off. (e) Reader/Doors – lock and unlock.

Q. Reporting

1. Provide online database reporting without degrading performance 2. System shall provide predefined reports with ability to create and save user-defined report

templates for grouping, sorting, and filtering data 3. Predefined reports shall be provided

a. Configuration 1) Cardholder and card ID information 2) System administration 3) Device

b. Schedules 1) System 2) Time 3) Event

c. Access 1) Reader access 2) Floor access 3) Roll call / muster 4) Time and attendance

d. History 1) Alarm 2) Person / credential 3) Operator

4. Support multiple export file formats 1) Crystal Reports 2) Data Interchange Format 3) Excel 4) HTML 5) Lotus 6) ODBC 7) Paginated Text 8) Report Definition 9) Rich Text Format 10) Tab Delimited Text



[PROJECT LOCATION]




11) Unformatted Text 12) Word

5. Export Destinations a. Disk File b. Exchange Folder c. Lotus Domino Database d. Microsoft Mail (MAPI)

6. Support direct database connectivity for facilitating report generation from external third-party database applications a. Microsoft SQL Server b. Microsoft Access c. Crystal Reports

7. External Reports a. Reader Where When Report

1) Selected readers and their associated access rights and time schedules b. Who Has Access Report

1) Selected readers, exception areas, person type, and department when grouped by access right

2) Selected access rights, exception areas, person type, and department when grouped by reader

3) Selected access rights, readers, person type, and department when grouped by area exception (ACU only)

R. Photo ID Badge Making

1. Incorporate capture, display, and print capabilities for producing custom photo ID cards from any licensed operator workstation.

2. Operate from a single database for employees, contractors and visitors. 3. Permission controlled operator function at operator workstations. 4. Capture and display personnel photos and signatures. 5. Support biometrics identity enrollment and smart card credentialing. Includes fingerprint

capture, document capture, and MIFARE smart card encoding. 6. Card design and production.

a. Card Design 1) System shall allow multiple badge types to be configured and stored as

templates. (a) Badge format, layout, background color, location of photo, text, applicable

graphics or company logos, etc., shall be defined and stored in the system database.

(b) Support industry standard graphics formats for importing logos and backgrounds.

(c) Each badge type shall be uniquely defined. (d) Badge types will be assigned automatically as determined by the system

from field data selections. (e) Field data selections are to be made via pre-defined list boxes to avoid

operator errors and badge assignment errors. 2) Define and apply American National Standards Institute (ANSI) standard

barcode formats to text objects. 3) Define and apply magnetic stripe encoding formats to text objects.

b. Image Capture 1) Capture, store, and print industry standard image formats, digitized photos, and

signatures. (a) Support user selectable settings for optimizing file size,

compression/quality, and color depth. 2) Live video and still image capture devices and interfaces.

(a) Composite, S-Video, RGB, and digital cameras.



[PROJECT LOCATION]




(b) Scanners. (c) Signature pads (d) TWAIN driver interface.

3) Image capture of photos and signatures from file. 4) Support image cropping and quality enhancement controls at time of capture.

c. Fingerprint capture 1) Capture and store fingerprints.

(a) Up to two (2) fingerprints shall be able to be acquired per person. (b) Depending on the reader, each fingerprint shall be able to be uniquely

identified as the primary or secondary fingerprint image in addition to the source hand/finger location from which it was captured.

(c) The secondary fingerprint image shall allow an operator to designate if the secondary fingerprint should be used for “Duress” in smart card applications.

2) Selection of fingerprint biometric template generation algorithms shall be supported and configured as a property associated with the device driver for the fingerprint capture device.

d. Production 1) On-screen WYSIWYG print preview of card design. 2) Printers and printer interfaces including:

(a) Color Laser, Inkjet, and Bubble jet printers. (b) Color dye sublimation card printers. Supported card printer functions shall

include: (1) Direct printing on standard CR-80 PVC cards. (2) Single and dual sided printing. (3) In-line magnetic stripe HiCo/LoCo encoding on Tracks 1, 2, and 3. (4) Clear overcoat with optical or holographic security logo.

7. Support cardholder photo and signature image export from system database to industry standard graphic file formats.

S. Integrated Video Surveillance:

1. Support software level integration with video surveillance systems. a. CCTV Matrix Switchers:

1) Interface with multiple matrix switchers. (a) Serial interface support via RS-232 communication protocol. (b) Locally and remotely. (c) Via system host servers and/or network connected client workstations.

2) Define and assign CCTV “Enable”, “Disable”, and “Camera Alarm” messages to system alarms.

3) Process alarms and transmit applicable messages to the matrix switcher in real-time “Enable”, “Disable”, and “Camera Alarm”.

4) Support a supervised bi-directional communications interface for receiving “video loss alarms” and detecting communication failure, should the specific matrix switcher interface provide that support.

5) Support the following CCTV matrix switcher interfaces: (a) American Dynamics 168 and 2150. (b) PHILIPS/Burle Allegiant TC8500 to TC8901series. (c) Kalatel KTD 312 and 348. (d) Pelco 9760. (e) Generic User-definable.

b. Video Recorders: 1) Provide a fully integrated digital video recorder and camera management

interface for video command and control. 2) Support network connectivity to multiple video recorders via system host

server(s) and client workstation(s).



[PROJECT LOCATION]




3) Provide a multi-window video management console for real time video device monitoring and control from any operator workstation.

4) Display video recorders, cameras and assigned presets in a navigation pane for operator access.

5) Support up to 256 video cameras per video device. 6) Support World Time Zones by allowing each device to be assigned a World

Time Zone independently of its hosting computer’s World Time Zone to insure proper time synchronization and reporting into the system history logs, event and alarm monitors.

7) Operator Controls (a) Select or drag and drop cameras to create and save custom views using

cameo formats for 1-UP, 2-UP, 4-UP, 9-UP, 16-UP, Custom 7-UP, Custom 11-UP, and Custom Center/Perimeter.

(b) Simultaneously view and control multiple live video cameras across multiple DVR units.

(c) On-screen mouse driven control of pan, tilt, zoom, iris, focus, and camera preset call-up functions.

(d) Quick recall video playback on any selected camera view to request the last 15 seconds, 30 seconds, 1 minute, 2 minutes, 5 minutes, or the selection from the last four (4) events listed for the selected camera.

(e) Access and playback recorded video events with on-screen controls: play forward, play reverse, fast forward, fast reverse, single frame advance, single frame reverse, pause, stop, and variable speed control functions.

(f) Playback tagged video events stored locally on DVR units, based on date, time, alarm, event, text, and motion search queries from the system history/archive database.

(g) Save still image snapshots to file in the JPG file format from any live or recorded playback video stream.

(h) Save video clips to file in native or AVI file formats from any live or recorded playback video stream.

(i) Create and burn evidence CDs of selected video clips with required video player. (1) Permit launching from Video Management Console. (2) Include a Terms and Conditions dialog box for reviewing on the

evidence CD. (j) Set and store preset of PTZ cameras via right-click on preset in

navigation tree for the active camera tile live view. (1) Support limited to GE Sym protocol and VOS-based platforms,

which support PTZ program pass through. (2) Message pop-up shall be posted for operator confirmation prior to

committing preset store to PTZ dome. 8) Support request for live and recorded video transmission from video recording

units at various resolutions and display sizes, independent of actual resolution settings for local recorded video, user configurable to facilitate network adaptability.

9) Support setting defined preset positions for PTZ cameras. 10) Allow the assignment of video cameras and presets to system alarm and card

access events from operator workstations. (a) Automating real-time camera control. (b) Automatic live video pop-up on alarm. (c) Video event tagging. (d) Quick access to live and recorded video.

11) Provide simultaneous support for multi-vendor video drivers. 12) Monitor video recording unit status for processing and reporting the following

conditions:



[PROJECT LOCATION]




(a) Online / Offline. (b) Record status. (c) Disk capacity status. (d) Camera video loss. (e) Camera alarm. (f) Camera analytics alarm. (g) Camera trouble alarm. (h) Video device health trouble alarm. (i) Video device health fail alarm.

13) Support of recorders running VOS 4.4 operating system. 14) Support multiple video recording devices:

(a) UTC Fire & Security: (1) DVMRe CD, CT, CT-II. (2) StoreSafe Pro and Pro-II. (3) SymDec, SymSafe and SymSafe Pro. (4) TruVision Devices:

(i) TruVision DVR 10. (ii) TruVision NVR 40.

(5) UltraView Devices: (i) UltraView Encoder 10 (formerly Discovery 105E). (ii) UltraView Recorder 40 (formerly Discovery 1205). (iii) UltraView Recorder 60 (formerly Discovery 2415). (iv) UltraView NVR 80 (formerly ECVRS). (v) Ultraview Storage 80 (formerly VRU).

(6) DVSRxU. (b) American Dynamics Intellex DVMS8000. (c) Integral Technologies DVXi, DSXpress. (d) NiceVision Harmony, Pro. (e) Panasonic HD500. (f) Pelco DX8000, DX8100. (g) TVR 30. (h) TVR 60 (analog channels only are supported).

T. Integration with Video Security Center (VSC)

1. The system shall support integration with Video Security Center (VSC) 2. Users and Permissions Management

a. The system shall support the management of users, user groups, permissions assignment to user groups, facilities, user assignment to facilities, and clients.

b. The system shall have the ability to synchronize the users, user groups, permissions assignment to user groups, facilities, user assignment to facilities, and clients with VSC, either at the end of configuration or on a scheduled basis.

3. Video Device Configuration a. Config Panel to configure VOS based video and storage devices b. Assignment of video devices to system facilities and clients c. Ability to host up to a maximum of 600 video devices per system client VSC shall have

the ability to synchronize with the system the video and storage devices facility and client assignments and the preset settings either at the end of configuration or on a scheduled basis.

4. Video Client Launch a. Launch of Config Panel from the system b. Launch of Security Center from the system

5. Access Control Configuration and Management a. The system shall support the management of access control, cardholders,

permissions, reporting, badge events, and event monitoring



[PROJECT LOCATION]




6. Video Management a. The system shall support Video Live and Playback functions of VSC from Alarm

Monitor, Activity monitor, and Graphics Maps b. Multi-camera views c. Enhanced recording and playback d. MultiVision e. Client connectivity to KTD-405 keyboard in VSC

7. Audio a. Audio Playback b. IP Audio Support

8. Alarm Management a. Launch of live, recorded video upon alarm/event in the system

9. Graphical Maps a. Launch of live, playback video from graphic maps

10. Multiple Monitor setup a. Single application login to the system, VSC launch from the system

11. Failover and Redundancy 12. Database Maintenance

U. Application Program Interface 1. The system shall support an application program interface (API), which allows authorized

software connections with external systems for developing custom interfaces and providing tightly coupled integrated solutions. a. Only allow authorized connections through the API. b. Allow up to twenty-five (25) concurrent connections to external systems through the

API. 2. The API shall facilitate in real-time:

a. Response to monitored events processed by the system. b. Control of devices managed by the system.

3. The API shall expose the following aspects of the system: a. Bi-directional alarm event processing for monitoring and acknowledgement. b. Receiving card access activity events. c. Receiving digital input events. d. Receiving intrusion zone events. e. Control of operator logins. f. Control of alarm point monitoring On/Off. g. Control of digital input points Enable/Disable. h. Control of digital output points Activate/Deactivate. i. Control of intrusion zones Arm/Disarm. j. Control of control panel Modes.

4. The API shall be fully documented and made available with sample application code.

V. Intrusion Alarm Receiver IP Gateway 1. The system shall support an intrusion alarm receiver IP gateway, which allows for secondary

alarm monitoring of intrusion type panel alarms based on standard CID and SIA code formats over IP.

2. The “Intrusion Alarm Receiver” type driver shall be for supporting the GE Security NetworX series intrusion panels equipped with the NX590E TCP/IP communications module.

2.4 SOFTWARE OPTIONS

A. Software Option Packages and Interfaces:



[PROJECT LOCATION]




1. Software Options: a. Photo ID Card Production Option. b. Biometrics Identity Enrollment and Smart Card Credentialing Option. c. Guard Tour Option.

2. Interface Options: a. Application Program Interface Option. b. Integrated Digital Video Third-Party Driver Option Facility. c. Client Redundancy Device Fail Over Option. d. Intrusion Alarm Receiver IP Gateway Interface Option.



[PROJECT LOCATION]




PART 3 EXECUTION 3.1 INSTALLERS

A. Contractor requirements: 1. Factory authorized representative for no less than two (2) years, recognized by the

manufacturer of the specified system. 2. Local installation and service organization. 3. Provide three (3) references (minimum) whose systems are of similar complexity.

a. Installed by this contractor in the last five (5) years. b. Presently maintained by this contractor.

4. Provide satisfactory evidence of liability insurance and Workmen's Compensation coverage for employed personnel as required by law.

B. Ensure that all personnel working on the project are registered with the state or local jurisdiction

licensing board as provided for by current state/municipal statutes. 1. At time of bid, the contractor shall be licensed by the state or local jurisdiction to perform

security work within the state. 2. Contractors who have security licenses or permits pending shall not be considered

acceptable for bidding on this project.

C. Installer and technician requirements: 1. Must be experienced and qualified to accomplish all work promptly and satisfactorily. 2. Provide proof that designated service and support personnel have successfully completed

the appropriate manufacturer offered hardware and software training and certification for installation, service and maintenance of the specified system.

3. Advise owner in writing of all designated service and support personnel responsible for installation as well as pre and post warranty service.

3.2 EXAMINATION

A. Inspect the installation site prior to bidding the job. B. Report any discrepancies between the project specification and bid documents and the site

examination prior to the bid opening date.

3.3 PREPARATION

A. Order all required parts and equipment upon notification of award. B. Bench test all equipment prior to delivery to the job site. C. Verify the availability of power where required. If a new source of power is required, a licensed

electrician shall be used to install it. D. Verify the availability of communication infrastructure where required. E. Arrange for obtaining all programming information including access times, free access times, door

groups, operator levels, etc.

3.4 INSTALLATION

A. Requirements 1. Install all system components and appurtenances in accordance with the manufacturer’s

specifications, referenced practices, guidelines, and applicable codes. 2. Furnish all necessary interconnections, services, and adjustments required for a complete

and operable system as specified.



[PROJECT LOCATION]




3. 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.

4. Carefully follow the instructions in the manufacturers’ installation manual to ensure all steps have been taken to provide a reliable, easy to operate system.

5. Perform all work as indicated in the project specifications and bid documents. 6. Pre-program system and load onto owner’s host computer.

B. Systems Integration 1. Coordinate with the owner’s IT Department prior to connecting to the owner’s network. 2. Work in harmony with all other trades. 3. Integrate related system and sub-systems.

3.5 QUALITY CONTROL

A. Workmanship 1. Comply with highest industry standards, except when specified requirements indicate more

rigid standards or more precise workmanship. 2. Perform work with persons experienced and qualified to produce workmanship specified. 3. Maintain quality control over suppliers and subcontractors. 4. Quality of workmanship is considered important. Owner’s representative will have the

authority to reject work which does not conform to the project documents.

B. Site Tests and Inspections 1. Execute adequate testing of the system to insure proper operation. 2. Upon reaching Substantial Completion, perform a complete test and inspection of the

system. If found to be installed and operating properly, notify [Client] of your readiness to perform the formal test and inspection of the complete system.

3. Submit the Record Drawings (as-builts) to owner’s representative for review prior to inspection.

4. During the formal test and inspection (commissioning) of the system, have personnel available with tools and equipment to remove devices from their mounts to inspect wiring connections. Provide wiring diagrams and labeling charts to properly identify all wiring.

5. If corrections are needed, the contractor will be provided with a punch list of all discrepancies. Perform the needed corrections in a timely fashion.

6. Notify owner when ready to perform a re-inspection of the installation.

C. Software Engineering Support 1. Provide software engineer services to assist the owner in coordinating the interfaces between

the security management system and the staff databases or other remote systems. 2. Software engineer shall be certified by or employed by the system manufacturer, and shall be

thoroughly knowledgeable of the system applications. 3. Software engineer shall be on-site and available to meet with owner’s representatives for a

period of not less than two consecutive days. On-site visit shall be scheduled at the convenience of the owner.

3.6 SYSTEM STARTUP

A. Provide initial programming and configuration of the security management system. B. Programming shall include defining hardware, doors, monitor points, clearance codes, time codes,

door groups, alarm groups, operating sequences, camera call-ups, etc. Input of all program data shall be by contractor. Consult with owner’s representative to determine operating parameters.

C. Develop and input system graphics, such as maps and standby screens. 1. Development of maps shall include the creation of icons for all doors, monitor points, and

tamper circuits.



[PROJECT LOCATION]




2. Owner shall provide AutoCAD .DWG or .DXF file floor plan drawings as the basis for the creation of maps.

D. Owner, with the cooperation and assistance of contractor, will input the cardholder data for each access card.

E. Maintain hard copy worksheets which fully document the system program and configuration 1. Worksheets shall be kept up to date on a daily basis until final acceptance by owner. 2. Worksheets shall be subject to inspection and approval by owner. 3. Provide final copies to owner prior to project close-out.

F. Maintain a complete, up-to-date backup of the system configuration and cardholder database. 1. Backup shall be maintained throughout programming period until final acceptance by owner. 2. Submit back-up media to owner upon Final Acceptance.

G. Provide follow-up assistance with system configuration sixty (60) days after start-up of system as requested by owner. Include a labor allowance for follow-up assistance in base bid price.

3.7 CLOSEOUT ACTIVITIES

A. Commissioning 1. Place entire system into full and proper operation as designed and specified. 2. Verify that all hardware components are properly installed, connected, communicating, and

operating correctly. 3. Verify that all system software is installed, configured, and complies with specified functional

requirements. 4. Perform final acceptance testing in the presence of owner’s representative, executing a point

by point inspection against a documented test plan that demonstrates compliance with system requirements as designed and specified.

5. Submit documented test plan to owner at least fourteen (14) days in advance of acceptance test, inspection and check-off.

6. Conduct final acceptance tests in presence of owner’s representative, verifying that each device point and sequence is operating correctly and properly reporting back to control panel and control center.

7. Acceptance by owner is contingent on successful completion of check-off; if check-off is not completed due to additional work required, re-schedule and perform complete check-off until complete in one pass, unless portions of system can be verified as not adversely affected by additional work.

8. System shall not be considered accepted until all acceptance test items have been successfully checked-off. Beneficial use of part or all of the system shall not be considered as acceptance.

B. Training

1. Provide system operations, administration, and maintenance training by factory trained personnel qualified to instruct. a. Training shall be oriented to the specific system being installed under this contract as

designed and specified. b. Provide training sessions at owner’s facility, and schedule at the owner’s convenience. c. Provide written training outline and agenda for each training session prior to

scheduling. d. Record and provide copies of training programs for owner knowledgebase.

2. Owner will designate personnel to be trained. a. Provide classroom instruction for people selected by owner. b. Provide two (2) hours of individual hands-on training for each person.

1) Hands-on training shall include the opportunity for each person to operate the system.

2) Hands-on training shall include practice of each operation that an operator would be expected to perform.



[PROJECT LOCATION]




c. Provide printed training materials for each trainee including product manuals, course outline, workbook or student guides, and written examinations for certification.

3. Cover all operating features of the system, including the following: a. System set-up and cardholder database configuration. b. Access control features. c. Alarm monitoring features. d. Report generation and searches. e. Card management. f. Disk backup procedures. g. Routine maintenance and adjustment procedures.

END OF SECTION Facility Commander Wnx 7.7 A&E Specification, RevA2 Copyright © 2011 Lenel Systems International, Inc. Information in this document is subject to change without notice. Lenel is a registered trademark of Lenel Systems International, Inc. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Citrix®, and MetaFrame® are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. Other names mentioned in this document may be trademarks or registered trademarks of their respective owners and are hereby acknowledged. LENEL CONFIDENTIAL INFORMATION – For use by Lenel-authorized VARs, prospective or existing Facility Commander Wnx users and their respective authorized consultants. All other third-party use is prohibited without Lenel’s written permission.

Documents

Facility Commander Wnx 7 7 AE Specification RevA2