Facility Commander Wnx v7.0 A&E Specification v7 AE Spec 080915.doc · Web viewException: Controlled devices, such as electric locks, door actuators, sensors, etc., are specified

INTEGRATED SECURITY MANAGEMENT SYSTEM

FACILITY COMMANDER WNX v7.0

SEPTEMBER 2008

NOTES

1. The following A&E Specification conforms to CSI guidelines for providing specifiers and systems integrators an easy way to include GE Security products in their specifications.

2. Specifiers should carefully select the portions of this document that fit the intended application. Feel free to consult with GE Security regarding particular project requirements. For information and assistance contact:

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

http://www.gesecurity.com/

PREFACE

This specification includes a general description as well detailed functional and technical requirements for an Integrated Security Management System (ISMS). This specification provides all information necessary to produce a complete proposal for a scalable multi-user, multi-tasking ISMS based on Microsoft Windows platform technology. The ISMS shall include all computer hardware and software, control panels, interfaces, card readers/keypads, access cards, digital video recorders, cameras, alarm sensing devices, communication devices, electric door locking hardware, power supplies, cable/wire, conduit, raceways, enclosures, mounting hardware, and all other equipment as indicated on contract drawings and as specified herein. All material shall be of manufacturer’s standard catalog product.

CustomerAdaptable Integration

Global Operations Center

Local Door Reader Interfaces

Region 1

Multi-Purpose Client Application Workstation(s)

•System Management•Monitoring & Surveillance•Command & Control•Photo ID Credentialing•Device & API Service Hosting

Alarm InputsControl Outputs

DirecDoorPoEEdge IP Controllers

M-SeriesControllers Intrusion Panels

Alarm Monitoring

Fire PanelsAlarm Monitoring

Digital Video RecordersVideo Surveillance

Regional Server


TCP/IP Local Area Network

Region 2Region N

Microsoft SQL Server

GlobalServer •HR Personnel Database

•IT Active Directory Server•E-mail Server•Crystal Enterprise Report Server•Thin Client Application Deployment Server

Enterprise Business Systems

Database Replication


CustomerAdaptable Integration

Global Operations Center

Local Door Reader Interfaces

Region 1


•System Management•Monitoring & Surveillance•Command & Control•Photo ID Credentialing•Device & API Service Hosting

Alarm InputsControl Outputs

DirecDoorPoEEdge IP Controllers

M-SeriesControllers Intrusion Panels

Alarm Monitoring

Fire PanelsAlarm Monitoring

Digital Video RecordersVideo Surveillance

Regional Server


TCP/IP Local Area Network

Region 2Region N


GlobalServer •HR Personnel Database

•IT Active Directory Server•E-mail Server•Crystal Enterprise Report Server•Thin Client Application Deployment Server

Enterprise Business Systems

Database Replication


TABLE OF CONTENTS

PART 1 GENERAL...................................................................................................................................... 51.1 TERMS & CONDITIONS................................................................................................................51.2 SECTION INCLUDES..................................................................................................................... 51.3 RELATED SECTIONS.................................................................................................................... 51.4 REFERENCES............................................................................................................................... 61.5 SCOPE OF WORK......................................................................................................................... 61.6 SUBMITTALS................................................................................................................................. 71.7 WARRANTY AND MAINTENANCE................................................................................................7

PART 2 PRODUCTS................................................................................................................................... 92.1 MANUFACTURERS....................................................................................................................... 92.2 SYSTEM REQUIREMENTS...........................................................................................................92.3 SOFTWARE................................................................................................................................. 262.4 HARDWARE................................................................................................................................. 28

PART 3 EXECUTION................................................................................................................................ 323.1 SECURITY CONTRACTOR.........................................................................................................323.2 PROJECT MANAGEMENT..........................................................................................................323.3 PERSONNEL................................................................................................................................ 323.4 INSTALLATION............................................................................................................................ 323.5 COMMISSIONING AND TRAINING.............................................................................................33

PART 1 GENERAL

1.1 TERMS & CONDITIONS

A. This document covers the provision of an Integrated Security Management System (ISMS) for the [CUSTOMER NAME] facility located at [STREET ADDRESS], [CITY], [STATE], including all items and subsystems shown on drawings or otherwise required by these specifications.

B. The requirements of these specifications shall be understood to be the [CUSTOMER NAME] minimum. The requirements shall be expanded as necessary to ensure quality. However, unless [CUSTOMER NAME] approval is obtained, the requirement herein shall not be deleted or revised.

C. [CUSTOMER NAME] shall be hereinafter referred to in this document as the OWNER and the bid respondents shall be referred to as the SECURITY CONTRACTOR. The term OWNER includes direct employees and other appointed OWNER agents such as architects or consultants. These agents may be requested by the OWNER to represent the OWNER in undertaking certain project tasks.

D. If any statement in this or any other specification is in conflict with any provision of the General Terms and Conditions to the contract, the provision stated in the General Terms and Conditions shall take precedence. Any questions that require additional interpretation and guidance shall be immediately brought to the OWNER'S attention.

1.2 SECTION INCLUDES

A. This section covers the provision of ISMS including all items and subsystems shown on drawings or otherwise required by these specifications. 1. ISMS computer hardware, software, and control panels for access control and alarm

management.2. Card readers and other security input/output devices for access control and alarm

monitoring of secured areas.3. Photo ID Credentialing.4. Automatic Doors & Operators: Section [____]5. Vehicle Access & Parking Gate Operators: Section [____]6. Elevators: Section [____]7. Video Surveillance System: Section [____]8. Intrusion Detection System: Section [____]9. Fire Alarm Detection & Suppression System: Section [____]

1.3 RELATED SECTIONS

A. Conduit, Raceways, and Cable Trays: Division 16 Section [____]

B. Fire Stopping Penetration Through Rated Construction: Division 16 Section [____]

C. Electrical, Cabling, and Wiring: Division 16 Section [____]

ISMS Specification Page 5 of 39 Facility Commander Wnx V7.0September 2008

D. Door Hardware: Division 8 Section [____]

E. Data Communications Circuits: Division 17 Section [____]

1.4 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. American with Disabilities Act - Public Law 101.336

F. FCC

G. CE

H. NIST Triple DES Certificate #206

1.5 SCOPE OF WORK

A. The SECURITY CONTRACTOR shall include all necessary wiring, cabling, labor, tools, equipment, and ancillary materials required to furnish and install a complete and operational ISM.

B. Requirements are indicated elsewhere in these specifications for work including, but not limited to:1. Conduit, [110/230] VAC power extensions, and other electrical work shall be furnished

and installed by [SECURITY CONTRACTOR] or [OTHERS].2. Electric door hardware, sensors, egress devices, and associated lock power supplies

for card reader doors shall be furnished and installed by [SECURITY CONTRACTOR] or [OTHERS].

3. The OWNER shall arrange for [dedicated] or [dial-up] telephone lines and/or local area network (LAN) connections as shown on the attached drawings.

C. The ISMS shall provide management, control, and monitoring of card access and alarms to the following: [buildings] [and] [selected areas] using [specify type of card and reader technology].

D. The extent of ISMS work is defined to include but not limited to the following:1. The ISMS database and application host server shall be installed in [building] [room]

[location description].2. Operator workstations shall be installed in [buildings] [rooms] [location descriptions].3. Operator workstations fully equipped for producing custom photo ID credentials shall

be installed in [buildings] [rooms] [location descriptions].


E. Installing the ISMS and bringing it to operational status for acceptance shall include but not limited to the following:1. Determine hardware, software, and operations requirements for implementation.2. Install ISMS hardware and software.3. Setup and configure communications between the host server, operator workstations,

and control panels.4. Setup and configure ISMS application and database.5. Test ISMS operations based on a point-by-point walkthrough inspection.6. Perform end-user training.

1.6 SUBMITTALS

A. Submittals shall ensure that all parties involved can determine that the proposals meet the ISMS requirements as specified. Provide [____] sets.1. Executive Summary System Description: Descriptive statement and single-line block

diagram to show how all related equipment will interface and operate as a complete ISMS.

2. Product Data: Manufacturer's technical data sheets on each product to be used.3. Shop Drawings: Provide complete shop drawings that include the following:

a. Point-to-Point diagram of all system device locations on architectural floor plans; no other system(s) shall be included on these plans.

b. Detailed schematic wiring diagrams for all system devices. Wiring information shall include cable type, conductor routings, quantities, and connection details at devices.

4. Manuals: Manufacturer’s user’s manuals for operations, administration, installation, and maintenance.

5. Web-based Training: Access to web based training modules. 6. Software: 1 set of fully functional ISMS software in manufacturer’s original media

packaging, temporarily licensed for a (30) day evaluation period.

B. Contract Close-Out Submittals:1. Training Course Materials: Specified elsewhere in this document.2. Commissioning Test Plan and Check-Off List: Specified elsewhere in this document.3. As-Built Drawings: During system installation, the SECURITY CONTRACTOR shall

maintain a separate hard copy set of drawings, elementary diagrams, and wiring diagrams of the ISMS to be used for record drawings. This set shall be kept up to date, reflecting all changes and additions made to the ISMS. Copies of the final as-built drawings shall be provided to the owner in DXF format using the latest version of AutoCAD.

1.7 WARRANTY AND MAINTENANCE

A. The ISMS software, hardware, and installation shall be warranted against defects and workmanship for a minimum of (12) months, covering all parts and labor, after acceptance by OWNER.

B. The SECURITY CONTRACTOR shall guarantee that the ISMS application software/firmware remains current at all times with the latest enhancements, and is supported by the ISMS manufacturer with unlimited remote dial-in diagnostics capability and technical phone support.


C. The SECURITY CONTRACTOR shall perform manufacturer’s recommended preventative maintenance on all applicable components and/or devices.

D. The SECURITY CONTRACTOR shall be the primary contact and respondent for all service and support and officially recognized and backed by the ISMS manufacturer.

E. Extended and/or out of warranty terms at reasonable and customary rates shall be available from the SECURITY CONTRACTOR.

F. Include in contract sum, extended warranty and maintenance service after acceptance by Owner.1. Initial Warranty and Maintenance Service Extended to: [____] years.2. Submit payment terms and conditions with proposal.

G. Provide a separate proposal for an extended warranty and maintenance service contract for consideration by OWNER.1. Length of Contract: [____] years.2. Submit payment terms and conditions with proposal.


PART 2 PRODUCTS

2.1 MANUFACTURERS

A. This specification is based on software and hardware manufactured by GE Security; 791 Park of Commerce Boulevard, Boca Raton, FL 33487 USA. Tel: (561) 998-6100, Fax: (561) 994-6572, www.gesecurity.com.

1. Provide all ISMS access control hardware and software 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.

B. Substitutions: Not permitted.

C. Requests for substitutions will be considered in accordance with provisions of Section [____].

D. Other manufacturers seeking approval must provide the following information to the Owner's Representative [____] days PRIOR TO BID. If approved, written notification will be provided to all bidders of record; verbal approvals are not valid.1. Detailed bill of materials, correlating each item of equipment and software to

those specified.2. Manufacturer's standard published catalog data sheet for each proposed item

of equipment and software; if more than one model is shown on data sheet, mark exactly which model is being proposed.

3. Copy of this specification with each paragraph marked to show where on the data sheets the specification requirement specified in that paragraph is stated (use cross-reference numbers on data sheets).

4. If compliance with any specification requirements cannot be substantiated by reference to published data, provide typewritten compliance statement signed by executive officer of manufacturer stating that proposed products comply with all specified requirements.

2.2 SYSTEM REQUIREMENTS

A. Architecture:1. The ISMS shall be a Microsoft Windows based client/server application

capable of integrating multiple security functions including management, control, and monitoring of access control, alarms, photo ID credentialing, interfacing with video surveillance, other security subsystems and business database applications.

2. The ISMS shall be a true 32bit multi-threaded application, designed for Microsoft Windows technology platforms; with multi-user and multi-tasking capability, developed in a high level “C” language.

3. The ISMS shall use a commercially available standard database that is SQL and ODBC compliant, certified for the Microsoft Windows platform.


http://www.gesecurity.com/

4. The ISMS shall support user definable record-level database partitioning, for defining limited views of the ISMS database.

5. The ISMS database shall support open direct database connectivity for importing cardholder and card ID data from external systems and/or database applications. The ISMS shall facilitate interfacing by providing the following capabilities:a. Real time and batch processing of data via ODBC, JDBC or OLE DB

over a network connection.b. Insert, update, and delete record information.c. Automatic download of data to ISMS control panels based on database

changes.d. Provide audit trail in the operator history/archive database for all

database changes initiated by the interface.6. The ISMS be capable of operating in a Microsoft SQL Server Cluster

environment where the ISMS application server(s) support a shared database cluster. Cluster management shall be provided by industry standard Microsoft clustering services and should not require any proprietary clustering software.

7. It shall be possible to separate the ISMS database from the ISMS application including deployment of the database and application in separate geographical locations and communicating over standard network infrastructure to provide maximum flexibility and conformance to IT data center standards.

8. The ISMS shall be capable of supporting database and file replication using Microsoft SQL Server Replication Services and Microsoft File Replication Services for providing distributed database replication across multiple ISMS application servers allowing for system expansion and delivering N tiers of server redundancy. Database and file replication shall not require any proprietary database or file replication software.

9. The ISMS shall conform to the standard TCP/IP networking communications protocol between the application server(s), client workstations, control panels, video surveillance system(s) and database subsystems, using 10/100MbEthernet connectivity over LAN/WAN network typologies.

10. The ISMS shall be flexible and scalable in architecture, permitting expansion of both capacity and functionality, to be implemented progressively as needed, through software licensing and/or software upgrades.

11. The ISMS shall provide the ability to perform network deployed software updates. Network deployed updates shall have the option to be deployed manually or automatically.

12. The ISMS shall provide a real-time display of all system status and data at all operator workstations.

13. The ISMS shall monitor status and record activity transactions of all secured areas and alarm input/output points; visually and audibly annunciate alarms upon change of status, for assessment and response at all operator workstations.

14. The ISMS shall monitor and record card access, alarm, and operator activity to an online history/archive database for reporting.

15. The ISMS shall employ distributed processing technology, allowing the host to function almost entirely as an application/database server. The majority of the real time, day-to-day decisions shall be made locally by intelligent control panels. The control panels shall be the direct field interface for all access control, alarm sensing, and input/output-controlled devices.

16. Each control panel shall be able to continue access control and alarm-monitoring operations autonomously, in the event of ISMS hosting failure or network segment outage.


17. The ISMS shall manage and automatically download in real-time, all database changes made at all operator workstations, to the control panels that require notification of the specific database changes or updates.

B. System Redundancy & High Availability: The ISMS shall provide multiple levels of communications redundancy and failover for all ISMS hosted controllers, digital video recorders, API service connections, and client workstations. The ISMS shall be capable of automatically re-routing communications to alternate ISMS computers across the system without operator intervention.1. ISMS system configurations with a single application/ database server shall

provide at a minimum the following redundancy and failover capability:a. The ISMS shall provide communications redundancy and failover for

network-attached devices. Each network attached device (Control Panels, Digital Video Recorders, and API service connections) shall have one or more alternative communication sever(s) that can provide hosting in case of primary communications server failure.

b. In case of primary communications server failure, they system shall automatically re-route network-attached devices to their designated backup communications servers to allow continuous system operations without loss of alarm and event transaction processing during failover.

c. Network-attached devices which transition to backup communications servers, shall be able to be redirected back to their default primary servers, once the primary communications servers have been restored.

2. ISMS system configurations with multiple regional application/ database servers shall provide at a minimum the following redundancy and failover capability:a. The ISM shall support the same level of communications redundancy

and failover for network-attached devices per regional application/database server, allowable to span across regional application/database servers in the event of a regional application/database server failure.

b. In case of a regional application/database server failure, client workstations shall be able to failover to their designated backup regional application/database server to allow continuous system operations.

c. In case of a regional application/database server failure, upon server restoration, the ISMS shall automatically update and synchronize the regional application/database server.

d. Client workstations which transition to a backup regional application/database server, shall be able to be redirected back to their default regional application/database server, once the regional application/database server functions have been restored.

C. System Capacity: Provide total system capacity to accommodate the following:1. Application/Database Servers: Must be capable of supporting a Single

application/database server upgradeable to a multi-server configuration with up to 64 synchronized application/database servers operating as a single unified system.

2. Workstations: Must be capable of supporting a minimum of 5 concurrent operator workstation sessions per server upgradeable to 50 concurrent operator workstation sessions per server.

3. Cardholder Database: Must be capable of supporting a minimum of 25,000 access control cards upgradeable to 500,000. Multiple access control cards


assignable per cardholder, each tracked separately. Access control cards shall be unique 4 to 16-digit numbers without facility code dependency.

4. Control Panels: Must be capable of supporting a minimum of 64 per server upgradeable to 1,024 per server

5. Access Control Readers: Must be capable of supporting a minimum of 256 readers per server upgradeable to 4,096 readers per server.

6. General Purpose Alarm Inputs: Must be capable of supporting a minimum of 2,560 alarm input points per server upgradeable to 20,048 per server.

7. General Purpose Outputs: Must be capable of supporting a minimum of 2,048 relayed or TTL level output points per server upgradeable to 16,384 per server.

8. Time Schedules: Unlimited definable in system database, up to 1,024 concurrently active per control panel.

9. Access Rights: Unlimited definable in system database, up to 96 concurrently active per access card per control panel.

10. Transactions: Centralized on-line storage of historical transactions, a minimum of 1,000,000 events

11. Digital Video Recorders: Must be capable of supporting a minimum of 16 per server upgradeable to 256 per server

12. Video Surveillance Cameras: Must be capable of supporting a minimum of 256 per server upgradeable to 4,096 per server.

D. Control Panel Capacities:1. Field Configurable Control Panel:

a. Card Readers: Capable of supporting up to 16 card readers.b. General Purpose Alarm Points: Capable of supporting up to 80 four-

state supervised alarm input points.c. General Purpose Outputs: Capable of supporting up to 64 relay or TTL

level output points.d. Access Control Card Memory: Up to 100,000e. Offline-History Transaction Buffer: Up to 16,000f. Time Schedules: Up to 1,024g. Access Rights: Up to 96 per access control card per panelh. Uninterruptible Power Supply: Battery rated for a minimum 4 hours of

continuous operation at full load.2. Fixed Configuration Control Panel:

a. Card Readers: Support 4 card readers.b. General Purpose Alarm Points: Support 10 four-state supervised alarm

input points.c. General Purpose Outputs: Support 8 relay output points.d. Access Control Card Memory: Up to 100,000.e. Offline-History Transaction Buffer: Up to 16,000.f. Time Schedules: Up to 1,024.g. Access Rights: Up to 96 per access control card per panel.h. Uninterruptible Power Supply: Battery rated for a minimum 4 hours of

continuous operation at full load.3. IP Network Edge Door Control Panel:

a. Card Readers: Support 2 card readers.b. Door Control Inputs: Support 2 supervised/non-supervised door

contacts and 2 supervised/non-supervised REX inputs.c. Door Control Outputs: 2 relay output points, configurable for 12/24VDC

output or dry contact output.d. Support 1 Tamper Switch input.e. Support 1 AC Power Fail input.


f. Support 1 Fire Alarm Control Panel input.g. Access Control Card Memory: Up to 100,000.h. Offline-History Transaction Buffer: Up to 16,000.i. Time Schedules: Up to 1,024.j. Access Rights: Up to 96 per access control card per panel.k. IEEE 802.3af PoE or Auxiliary Uninterruptible Power Supply: Battery

rated for a minimum 4 hours of continuous operation at full load.

E. Operator Interface: 1. The ISMS shall use a single Windows based client application interface for

system configuration, administration, management, and monitoring operations.

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

3. The ISMS shall provide on-line context sensitive help files to facilitate operators in the configuration and operation of the ISMS. Standard Windows help commands for Contents, Search, Back, and Print shall be supported.

4. The ISMS shall implement National Language Support (NLS) in a manner that allows simultaneous multi-lingual operation, based on individual operator language preference. The graphical user interface and on-line help shall support English and [Spanish] [French] [Portuguese] [Italian] [German] [Chinese] [Korean] [Japanese].

5. The ISMS shall support defining an unlimited number of operators; application access via workstation(s) shall be restricted by operator login and password. Operator passwords shall be stored in the database in an encrypted manner. The ISMS shall provide that ability to setup password rules for password length and expiration periods for system operators. Operator profiles shall be configurable to include form level permissions, database partition views, and language preference.

6. The ISMS shall allow operator authentication through an Active Directory Server, bypassing ISMS storing passwords. Operator access with the ISMS shall continue to be defined within the ISMS configuration forms.

7. The ISMS shall support the use of thin client application deployment to provide remote access to the Operator Interface. Thin client application support shall be via standard Microsoft Terminal Services, Citrix MetaFrameXP and Microsoft Virtual Terminal Services using a standard web browser

F. Cardholder Management: 1. The ISMS shall provide an operator interface for enrollment, modification, and

deletion of cardholder’s personnel and access control information. The ISMS shall allow enrollment of cardholder’s personnel and access control information in advance, without requiring assignment of access control card(s). The ISMS shall provide the ability to select multiple cardholders and badge records in applying mass changes. The cardholder’s personnel and access information shall include the following data:a. First Name.b. Middle Name 1.c. Middle Name 2.d. Last Name.e. Employee Number.


f. Personnel Type (Selectable from a user defined list that shall include at a minimum; Permanent, Temporary, Contractor, and Visitor classifications).

g. Department (Selectable from a user defined list).h. Facility (Selectable from a user defined list of database partitioned

views).i. Trace Activity (Enable/Disable).j. Address 1 (User definable label).k. Address 2 (User definable label).l. Address 3 (User definable label).m. Address 4 (User definable label).n. Address 5 (User definable label).o. Telephone.p. 90 User Fields (User definable labels).q. Access Right(s) (Multiple assignments).r. Access Card(s) (Multiple assignments).

G. Card ID Management:1. The ISMS shall provide an operator interface for enrollment, modification, and

deletion of access control card ID information in advance, without requiring assignment to a cardholder and shall include the following data:a. Description.b. Card ID number (4 to 16 digit, unique access control identifier).c. Pin Number (4 digit number for authenticating cardholder in card &

keypad reader applications).d. Status (Issuable, Active, Lost, Suspended, Remake).e. Assigned Cardholder (Selectable from predefined list of cardholders).f. Issue Date (Required to support advanced date issuance with

automatic activation of access control card ID numbers at control panel level in real-time without ISMS host notification).

g. Return Date.h. Expire Date (Required to support out to year 2099 and automatically

expire access control card ID numbers at control panel level in real-time without ISMS host notification).

H. Access Control Management:1. The ISMS shall allow or deny access to secured areas, arm and disarm

intrusion zones, and provide output control via access control readers, based on validation of a cardholder’s assigned access rights.

2. The ISMS shall support defining an unlimited number of access rights in a manner that associates reader(s) with a specific time schedule. 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. The ISMS shall allow cardholders to be assigned multiple access rights and multiple access control cards, without requiring duplicate database entry of cardholder personnel information.

4. Any and all access control cards assigned to a cardholder, shall automatically inherit all of the access rights assigned to the cardholder.

5. The ISMS shall monitor all secured areas and process an alarm notification whenever a reader controlled door is opened, unless door is opened pursuant to a valid card read, exit request through egress device, or door has been manually unlocked via remote command from an authorized system operator.


6. The ISMS shall be user configurable to operate in either global or local mode, controlling IN and OUT access of secured areas for anti-passback and time & attendance applications.

I. Time Schedule and Mode Management: The ISMS database shall support defining an unlimited number of schedules. Schedules shall define time, day, and date intervals for automatically executing ISMS functions, events, and mode changes. 1. Time schedules: Shall define start and stop interval(s) by time of day and day

of week or mode. Each time schedule shall support multiple intervals per day and multiple days per week. Time schedules shall be applicable to the following ISMS functions:a. Cardholder access rights to secured areas.b. Readers online/offline.c. Doors lock/unlock.d. Alarm monitoring on/off.e. Inputs enabled/disabled.f. Outputs on/off.g. Transaction routing for alarm and card activity.

2. Event Schedules: Shall define specific time(s) for an event to occur by time of day and day of week or mode. Each event schedule shall support multiple events per day and multiple days per week. Event schedules shall be applicable to the following ISMS functions:a. Changing reader modes of operation between card only, card-plus-

keypad, and card or keypad.b. Changing alarm monitoring sense times.c. Resetting anti-passback and/or time and attendance IN/OUT status of

all cardholders in control panel databases.d. Initiating a scheduled dial from host to communicate to remote dial-up

control panels.3. Mode Schedules: Shall define specific times and dates for indicating to

system control panels which time and event scheduled functions to execute. a. A minimum of 4 distinct mode classifications will be supported for

categorizing time and event scheduled functions. Mode classifications shall include Normal and 3 user definable modes such as holiday, evacuation, lock-down, or others.

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

J. Reader / Door Control:1. The ISMS shall allow access control readers to be individually configured for

different applications and modes of operation and shall support the following:a. Physical Reader Type: Each reader’s physical mode of operation shall

allow to be manually changed by an operator, or automatically via a system event schedule, for increasing or decreasing the level of security required for accessing secured areas at any time. 1) Card Only.2) Card-plus-keypad.3) Card or Keypad.

b. Logical Reader Type: Each reader’s logical mode of operation shall be configurable to support the following:1) Normal.2) Anti-passback IN, configurable to operate in enforced or passive

mode.


3) Anti-passback OUT, configurable to operate in enforced or passive mode.

4) Time & Attendance IN, configurable to operate in enforced or passive mode.

5) Time & Attendance OUT, configurable to operate in enforced or passive mode.

6) IN Required, configurable to operate in enforced or passive mode.

7) Elevator Control.c. Maximum unlock time after a valid card read shall be configurable from

0 to 59 minutes and 59 seconds.d. Alarm sense time for allowing a door to remain open after a valid card

read, before reporting a door held open alarm, shall be configurable from 0 to 61minutes and 59 seconds.

e. Extended unlock /alarm sense time after a valid card read shall be configurable from 0 to 59 minutes and 59 seconds, for cardholders requiring extended unlock duration times as in ADA applications. Cardholders and individual credentials for cardholders shall be configurable to initiate Extended unlock/sense functionality on doors configured to do so.

f. “Toggle” Card Reader: In addition to normal time duration control, the system shall support configuring readers to switch between on /unlock and off/locked with each valid card read.

g. Door relock after a valid card read shall be configurable to support the following:1) Lock on duration.2) Lock on open.3) Lock on close.

h. Reader / Door State:1) Each reader shall support operating in a default on-line or off-line

state, allowing to be manually changed by an operator, or automatically under a time of day and day of week schedule.

2) Each door shall support operating in a default locked or unlocked state, allowing to be automatically changed under a time of day and day of week schedule.

3) Each door, when scheduled to automatically unlock, shall be individually configurable to additionally require a valid card transaction to occur first before automatically executing the door unlock schedule.

4) Each door shall be individually configurable to monitor aperture of the door after a valid access grant, validating actual passage of the cardholder for accurately managing individual card IN & OUT status.

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


K. Elevator Control1. The ISMS shall provide the ability to control access for calling of elevators

cabs and selecting floor destination. The following elevator applications and configurations shall be supported:a. Elevator Cab Access: Elevator cab call buttons shall be illuminated and

enabled for selection when valid access via reader is granted. b. Floor Access: Floor access shall be controlled via a reader located

inside of each elevator cab; a minimum of 64 floors serviced by elevator cab(s) shall be controlled. Floor access shall support the following:1) Non Floor Tracking: when an authorized card is presented to the

reader located inside the elevator cab, only the floor buttons for the cardholder’s corresponding assigned access will be illuminated and enabled for a user definable length of time to allow selection.

2) Floor Tracking: when an authorized card is presented to the reader located inside the elevator cab, the cardholder shall be allowed to enter a 2-digit floor code on the reader’s keypad to which they have corresponding assigned access. The floor selected by the cardholder shall be a recorded transaction in the card history/archive database.

L. Input/Output Control1. The ISMS shall allow control panel input and output points to be individually

defined, configured, and controlled in the following manner:a. Input point(s) shall be user configurable for specific applications. The

following application types shall be supported:1) Alarm: digital input used to trigger an alarm and any selected

output.2) Digital Output:: digital input used to trigger a selected input

without alarm notification.3) Elevator: digital input used for elevator control.4) Inactive: digital input is disabled.

b. Input point(s) shall support a user configurable sense time from 0 to 59 minutes and 59 seconds. Sense time changes shall be supported via event schedules.

c. Input point(s) shall allow the active state to be configured as open or closed.

d. Input point(s) shall be user configurable to control a primary and/or secondary output. Input point(s) configured for output control shall allow being enabled or disabled via time schedule.1) The primary output shall be configurable to follow the input

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

point’s state change or remain activated until manually reset or scheduled off.

e. Output point(s) shall support a user configurable duration time from 0 to 61 minutes and 59 seconds.

f. Output point(s) shall allow the active state to be configured as on or off.g. Output point(s) shall be automatically controlled via time schedule to

turn on or off.h. Output points shall allow grouping to facilitate activating multiple output

points, on or off, via time schedule.


i. Output point(s), 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) Text entry explaining reason for manual operator control shall be

recorded in operator history/archive database.

M. Intrusion Zone Control:1. The ISMS shall provide the ability to define local intrusion zones that consist

ofa. One or more access control readersb. One or more alarm inputsc. An input point to designate for arming and disarmingd. An output point to designate for arming and disarming

2. The ISMS shall provide the ability to arm or disarm intrusion zones bya. Access control reader, using card and keypadb. Digital Input state changec. Manual Operator control

3. The ISMS shall provide the ability to arm or disarm intrusion zones from outside the protected area. a. Readers assigned to an armed intrusion zone shall deny access to card

holders unless the intrusion zone is disarmed.b. Readers assigned to an intrusion zone shall flash LED indicators on the

reader to annunciate the intrusion zone status.c. Cards shall be authorized as to which intrusion zones they can arm and

disarm.d. Users of the system will enter keypad information to tell the system to

arm or disarm and then they will present their carde. If the user is authorized to arm zone, and they have an active access

right for the reader, then the intrusion zone shall be armed and any readers associated with the intrusion zone (other than the arm/disarm reader) shall be placed offline, any inputs associated with the intrusion zone shall be monitored on. An output shall be able to be generated based on the arm event. A history record shall be generated for this event.

f. A configurable time delay before arming a zone shall exist allowing the user to leave the monitored area before the zone is armed.

g. If the user is authorized to disarm the intrusion zone, and they have an active access right for the reader, then the intrusion zone shall be disarmed and all readers associated with the intrusion zone will return to normal operation, any inputs associated with the intrusion zone shall be monitored off. An output shall be able to be generated based on the disarm event. A history record shall be generated for this event.

h. If the user is not authorized to disarm the intrusion zone, but the user has an active access right for the reader, then access will be denied, and a history record shall be generated.

4. The ISMS shall provide the ability to arm or disarm intrusion zones by manual controla. A properly permissioned operator shall be able to manually arm or

disarm an intrusion zone1) Intrusion zones shall be partitioned to limit restrict which operator

can view which intrusion zones.


N. Alarm Management1. The ISMS shall allow alarms to be individually defined, configured, and

controlled in the following manner:a. Configure if monitoring of the alarm is enabled or disabled. An alarm

shall allow monitoring to be controlled manually by an authorized operator and automatically via time schedule.

b. Alarm(s) shall be user configurable to trigger primary and/or secondary output(s).1) The primary output shall be configurable to follow the alarm’s

state change or activate for it’s defined output duration.2) The secondary output shall be configurable to follow the alarm’s

state change or remain activated until manually reset or scheduled off.

c. Alarms shall allow grouping to facilitate monitoring multiple alarms, on or off, via time schedule and changing alarm sense times via event schedules.

d. Alarms shall support regrouping via event schedules, allowing alarms to be reassigned to different alarm groups.

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

f. Alarms shall be able to be routed to specific workstations on specific time schedules. If an alarm is not responded to within a definable time period, it shall be able to be bumped to another workstation for acknowledgement.

g. User-definable instructions shall be assignable to each alarm, required to display in the alarm monitor window at all operator workstations for alarm assessment and response.

h. Configure if operator acknowledgement of the alarm is required before the alarm can be cleared from the alarm monitor window from any operator workstation.

i. 20 priority levels for prioritizing the processing and display of alarms.j. Configure and assign different foreground and background colors for

the alarm text from a palette of 256 different colors, based on the alarm priority and state (Alarm, Reset, Bumped Alarm, Bumped Reset).

k. E-mail Alarm Notification: The ISMS shall be capable of providing Alarm notification to email address(s) or devices using a SMTP messaging protocol.

O. Guard Tours: The ISMS shall support guard tour management allowing the configuration of access control readers and inputs to be used as guard tour points.1. The ISMS shall be able to configure multiple readers and inputs into named

guard tours, each definable with a maximum tour duration time up to 480 minutes (8 Hours).

2. The ISMS shall allow credentials to be assigned to guard tours where tour points may consist of access control readers.

3. An authorized operator shall be able to start, pause, re-start, and terminate a tour session.

4. The ISMS shall report an alarm if the overall time for the tour expired before the tour was completed.

5. The ISMS shall report transactions when tour points are hit.6. The ISMS shall report an alarm transaction if a tour point is hit more than

once on a tour.


7. The ISMS shall provide tour configuration reports.8. The ISMS shall provide tour history reports.

P. System Monitoring: The ISMS shall provide multiple monitoring application windows dedicated for displaying real-time information of ISMS card access and alarm activity as well as control panel and operator workstation status.1. Activity Monitor: shall display card access and non-alarm event activity from

all ISMS readers and relevant security devices that are on-line, active, and configured to route to monitor. The monitor window shall provide operator controls to clear, pause, and resume scrolling display of activity transactions. The following system activity transaction information shall be displayed:a. Transaction date & timeb. Access Control Transaction types:

1) Valid (Access granted).2) Valid Open (Access granted with door aperture confirmation).3) Valid No Passage (Access granted with no door aperture

detected).4) Invalid (Access not granted).5) Invalid Pin (Access not granted).6) Max Invalid PIN (Access not granted, card suspended).7) Suspended Card (Access not granted).8) Lost Card (Access not granted).9) Unknown Card (Access Not Granted).10) Duress Valid.11) Duress Invalid.12) Duress Valid Open.13) Duress Valid No passage.14) Anti-Passback IN Invalid.15) Anti-Passback OUT Invalid.16) Time & Attendance IN Invalid.17) Time & Attendance OUT Invalid.18) Floor selection for elevator control.19) Valid floor.20) Invalid floor.

c. Cardholder name.d. Card ID number for unknown or unassigned cards.e. Intrusion Zone Area Transaction Types:

1) Zone Armed.2) Zone Disarmed.3) Arm/Disarm Failed, Zone Not Secure.4) Arm/Disarm Failed, Invalid Access Right.5) Arm/Disarm Failed, Not in Zone.

f. Guard Tour transaction Types:1) Tour Started.2) Tour Ended.3) Tour Activity Valid.4) Tour Activity Invalid.5) Tour Paused.6) Tour Resumed.

g. Source device location description & reference.h. The ISMS shall allow direct navigation from any event within the

Activity Monitor to its related call-up of live and recorded video playback.


2. Alarm Activity Monitor: shall display alarm activity for all ISMS alarms configured or scheduled as monitored. The alarm activity monitor shall provide alarm notification and interaction for alarm assessment including acknowledgement and response. All operator acknowledgements and responses shall be recorded in the operator and alarm history/archive database. The following alarm activity information shall be displayed:a. Priority.b. Description.c. Reference type or additional alarm information.d. Alarm state:

1) Alarm.2) Reset.3) Cut (Tamper supervision).4) Short (Tamper supervision).

e. Process state:1) Acknowledged.2) Unacknowledged.

f. Occurrence Count.g. Host date and time.h. Control panel date and time.i. Predefined alarm instructions for operator assessment.j. Entry for operator alarm response in free form text and from pick list of

predefined alarm responses.k. Acknowledgement button.l. Alarm notification shall be provided via pop-up dialogue notifying the

operator of the occurrence of a new alarm. Direct navigation from the notification dialogue to the Alarm Activity Monitor shall be provided.

m. The ISMS shall allow direct navigation from any alarm within the Alarm Activity Monitor to its related call-up of live and recorded video playback as well graphics map location.

3. Control Panel Monitor: shall provide real-time communications status and connectivity control of all ISMS control panels. The control panel monitor shall support and provide the following:a. Display control panel properties, firmware version, and communications

status.b. The ability to remotely reset, configure online/offline, force database

downloads, and update control panel firmware.

4. Client Workstation Monitor: shall provide real-time communications status and connectivity control of all ISMS servers and client workstations.

5. Alarm Graphics Monitor: The system shall provide graphical map creation, editing, and real-time monitoring software for command & control visualization of ISMS alarms and device states via user configurable multi-state device symbols or icons.a. The following ISMS components shall be represented on graphics

maps for monitoring and control: area/zones, cameras, client workstations, controllers, digital inputs, digital outputs, digital video recorders, reader, control points, and command groups.


b. The ISMS shall 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.

c. The ISMS shall allow multiples of the same device type for the purpose of executing a single command on all the devices in the command group. Each command group icon can be defined as all devices of that type on the map, all devices of that type in a facility, or a user-defined set of devices.

d. The ISMS shall provide a series of default icons and user definable custom icons in JPG, GIF, animated GIF, and PNG file formats. Variable sizes shall be supported in 16x16, 24x24, and 32x32 pixels.

e. The ISMS shall support two icon techniques for alarm visualization: an overlay technique showing the state of the highest priority alarm on a device, and a decoration technique for displaying multiple alarms simultaneously for a device.

f. The ISMS shall support creation and importing of images in JPG, GIF, or PNG file formats imported as a single layer base map.

g. The ISMS shall support importing of multi-layer AutoCAD DXF R12 files, allow selected layers to be imported, and shall maintain layer separation within the system. The ISMS shall permit the re-import of a DXF file or individual layers from the file, without disturbing the other layers and icons previously placed on the map.

h. The ISMS shall provide the ability to define map layers that can be dynamically turned on or off while editing and viewing during monitoring operations.

i. The ISMS shall list maps alphabetically by facility in a navigation pane for easy access and additionally provide hyperlink icons that allow an operator to navigate and traverse through a series of maps quickly.

j. The ISMS shall allow a default map defined per operator, such that the map automatically displays when the alarm graphics monitor window is launched. The user shall be able to size the alarm graphics monitor window as desired, maps, graphics symbols and icons shall maintain aspect ratios.

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

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

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

n. 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 and include the following:1) Area/Zone – arm and disarm.2) Cameras – launch live video.3) Inputs – monitor on and off.4) Outputs – activate on and off.5) Reader/Doors – lock and unlock.

Q. Database Reporting: The ISMS shall provide on-line database reporting without degrading system performance. The following reporting functions and capabilities shall be supported:


1. Predefined reports with the ability to create and save user definable templates for grouping, sorting, and filtering data. A minimum number of predefined reports shall be furnished covering the following topics:a. Cardholder and card ID information.b. System administration and device configurations.c. System schedules and events.d. Reader access.e. Floor access.f. Roll call / Muster.g. Time and attendance.h. Alarm history.i. Badge history.j. Operator history.

2. Reports shall allow operators to perform page setup, preview report on-line, print, and export reports to multiple file formats and destinations.a. Export file formats supported shall include:

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.11) Unformatted Text.12) Word.

b. Export destinations supported shall include:1) Disk File.2) Exchange Folder.3) Lotus Domino Database.4) Microsoft Mail (MAPI).

3. The ISMS shall support direct database connectivity for facilitating report generation from external 3rd party database applications. The following applications shall be supported:a. Microsoft SQL Server.b. Microsoft Access.c. Crystal Reports Enterprise.

R. Photo ID Card Production:1. The ISMS cardholder management interface shall incorporate capture,

display, and print capabilities for producing custom photo ID cards by authorized operators from any operator workstation licensed to do so. Photos and signatures shall be available on-line for positive identification from all operator workstations. The cardholder management interface shall include the following:a. Digitized Photo.b. Digitized Signature.c. Card Design (Selectable from a user defined list and associated to

cardholder based on personnel type classification).2. The ISMS shall provide card design and production capabilities that shall

include the following:


a. Support industry standard image formats for capture, storage, and printing of digitized photos and signatures. Image formats shall support user selectable settings for optimizing file size, compression/quality, and color depth.

b. Support industry standard and commercially available live video and still image capture devices and interfaces including support for:1) Composite, S-Video, RGB, and digital cameras.2) Scanners.3) Signature pads.4) TWAIN driver interface.

c. Support image capture of photos and signatures from file.d. Support image cropping and quality enhancement controls at time of

capture.e. Support on-screen print preview of card design prior to printing.f. Support industry standard and commercially available printers and

printer interfaces including support for:1) Color Laser, Inkjet, and Bubble jet printers.2) Color dye sublimation card printers. Supported card printer

functions shall include:(a) Direct printing on standard CR-80 PVC cards.(b) Single and dual sided printing.(c) In-line magnetic stripe HiCo/LoCo encoding.(d) Clear overcoat with optical or holographic security logo.

g. Provide a user interface for creating custom card design templates including the following:1) Full compliment of drawing and editing tools.2) Define and edit text and graphic object properties.3) Link cardholder database fields to static text, dynamic text, and

graphic objects.4) Use of standard and custom color palette definitions.5) Support industry standard graphics formats for importing logos

and backgrounds.6) Define and apply ANSI standard barcode formats to text objects.7) Define and apply magnetic stripe encoding formats to text

objects.h. Support image export of cardholder’s photos and signatures from ISMS

database to industry standard graphic file formats.

S. Integrated Video Surveillance: The ISMS shall support software level integration with video surveillance systems for facilitating real-time response to monitored events processed by the ISMS.1. CCTV Matrix Switchers: The ISMS shall provide a CCTV matrix switcher

interface that supports the following functionality:a. Serial interface support via industry standard RS232 communications

protocol.b. Interface with multiple CCTV matrix switchers locally and remotely, via

ISMS host server(s) and/or network connected client workstation(s).c. The ability to define and assign CCTV “Enable”, “Disable”, and

“Camera Alarm” messages to ISMS alarms.d. The ISMS shall process alarms and transmit applicable “Enable”,

“Disable”, and “Camera Alarm” messages to the CCTV matrix switcher in real-time.

e. The ISMS shall support a supervised bi-directional communications interface for receiving “video loss alarms” and detecting communication


failure, should the specific CCTV matrix switcher interface provide that support.

f. The ISMS shall support the following CCTV matrix switcher interfaces:1) American Dynamics 168 and 2150.2) PHILIPS/Burle Allegiant TC8500 to TC8901series.3) Kalatel KTD 312 and 348.4) Pelco 97605) Generic User-definable

2. Digital Video Recorders: The ISMS shall provide a fully integrated digital video recorder and camera management interface for command and control video surveillance that supports the following functionality:a. The ISMS shall support network connectivity to multiple digital video

recorders (DVR) via ISMS host server (s) and network connected client workstation(s).

b. The communications interface between the ISMS and all DVR units shall be via 10/100Mb Ethernet connectivity using industry standard TCP/IP protocol.

c. The ISMS shall provide a multi-window video management console for real time video device monitoring and control from any ISMS operator workstation. DVRs, cameras and assigned presets shall be displayed alphabetically and grouped by facility in a navigation pane for easy operator access.

d. The video management console shall permit operators to 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.

e. ISMS operators shall be able to simultaneously view and control multiple live video cameras across multiple DVR units. Camera control shall be mouse driven on-screen and shall support pan, tilt, zoom, iris, focus, and camera preset call-up functions.

f. ISMS operators shall be able to perform quick recall video playback on any selected camera view to request last 15sec, 30sec, 1min, 2min, 5min or selection from last 4 events listed for the selected camera.

g. ISMS operators shall be able to access and playback recorded video events with on-screen controls that support play forward, play reverse, fast forward, fast reverse, single frame advance, single frame reverse, pause, stop, and variable speed control functions.

h. ISMS operators shall be able to playback tagged video events stored locally on DVR units, based on date, time, alarm, event, text, and motion search queries from the ISMS history/archive database.

i. ISMS operators shall be able to save still image snapshots to file in the jpg file format from any live or recorded playback video stream.

j. ISMS operators shall be able to save video clips to file in native or AVI file formats from any live or recorded playback video stream.

k. ISMS operators shall be able to create and burn evidence CDs of selected video clips with required video player.

l. The ISMS shall support request for live and recorded video transmission from DVR units at various resolutions and display sizes, independent of actual DVR resolution setting for local recorded video. Such a feature shall be user configurable from the ISMS to facilitate network adaptability.

m. The ISMS systems shall allow the assignment of CCTV cameras and presets to ISMS alarm and card access events; for automating real-time camera control, automatic live video pop-up on alarm, video event


tagging and providing quick access to live and recorded video from any ISMS operator workstation.

n. The ISMS shall provide simultaneous support for multi-vendor video drivers.

o. The ISMS shall monitor status of all DVR units for processing and reporting the following conditions:1) Online / Offline.2) Record status.3) Disk capacity status.4) Camera video loss.5) Camera alarm.

p. The ISMS shall be capable of supporting the following DVRs:1) GE Security DVMRe CD models.2) GE Security DVMRe CT and CT-II models.3) GE Security StoreSafe Pro and Pro-II models.4) GE Security SymDec, SymSafe and SymSafe Pro models.5) GE Security VisioWave.6) American Dynamics Intellex DVMS8000.7) Digital Watchdog DWPro.8) Integral Technologies DVXi, DSXpress.9) NiceVision Harmony & Pro.10) Panasonic HD500.11) Pelco DX8000.

T. Application Program Interface: The ISMS shall support an application program interface (API), which allows authorized software connections between the ISMS and external systems for developing custom interfaces and providing tightly coupled integrated solutions. The API for the ISMS shall facilitate real-time response to monitored events processed by the ISMS as well as control of devices managed by the ISMS.1. The ISMS shall only allow authorized connections through the API.2. The ISMS shall allow up to twenty-five (25) concurrent connections to external

systems through the API.3. The API shall expose the following aspects of the ISMS:

a. Bi-directional alarm event processing for monitoring and acknowledgement

b. Receiving ISMS card access activity eventsc. Receiving digital input eventsd. Receiving intrusion zone eventse. Control of operator loginsf. Control of alarm point monitoring On/Offg. Control of digital input points Enable/Disableh. Control of digital output points Open/Closei. Control of intrusion zones Arm/Disarmj. Control of control panel Modes

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

2.3 SOFTWARE

A. Application & Database Server Software:1. Operating System: Microsoft Windows [XP Professional or Server 2003]2. Database: Microsoft SQL Server [MSDE or Server 2005]


B. Client Workstation Software:1. Operating System: Microsoft Windows [XP Professional or Server 2003].

C. Integrated Security Management System Software:1. GE Security, Facility Commander Wnx 7.0.

a. Licensed for a total of [___] client workstations.b. Licensed for a total of [___] access control readers.c. Licensed for a total of [___] digital video surveillance cameras.

2. Facility Commander Wnx 7.0 Photo ID Card Production Option.a. Licensed on [___] out of the total client workstations specified above.

3. Facility Commander Wnx 7.0 Application Program Interface Option.a. Licensed for a total of [___] API connections.

4. Facility Commander Wnx 7.0 Integrated Digital Video 3rd Party Driver Option, individually licensed separately per application/database server.

5. Facility Commander Wnx 7.0 Client Redundancy Device Fail-Over Option, licensed separately per application/database server.

6. Facility Commander Wnx 7.0 Guard Tour Option, licensed separately per application/database server.

7. Facility Commander Wnx 7.0 Terminal Services Option, licensed separately per application/database server.

8. Facility Commander Wnx 7.0 OH Central Station Receiver Emulator Option for GE NX590E intrusion alarm monitoring direct over IP, licensed separately per application/database server.


2.4 HARDWARE

A. Host Server and Operator Workstations: Provided by Owner, to ISMS manufacturer's requirements specified below:

B. Host Server and Operator Workstations: Provided by ISMS supplier, factory-configured with all software pre-loaded and tested.

C. Computer requirements may vary based on system size and customer specific application requirements. Increasing memory capacity, hard drive capacity, processor speed, as well as specifying single dual core or dual processors, and multi-monitor displays shall be considered and recommended when required above minimum specifications.1. Host Server Minimum Requirements:

a. Xeon 2.xGHz processor (Dual or Quad Core).b. 4 GB RAM.c. 3.5-inch floppy drive, 4mm DAT tape drive, CDROM or CDRW.d. 10 GB available hard disk space.e. 19-inch flat panel display, supporting 16bit high color at 1024x768 resolution.f. 10/100MB Ethernet Network Interface Card.g. Standard 101-key keyboard and 2-button wheel mouse.

2. Operator Workstation Minimum Requirements: a. 2.xGHz processor (Dual Core)b. 2 GB RAM.c. 3.5-inch floppy drive, CDROM or CDRW.d. 1 GB available hard disk space.e. 19-inch flat panel display, supporting 16bit high color at 1024x768 resolution,f. 10/100MB Ethernet Network Interface Card.g. Standard 101-key keyboard and 2-button wheel mouse.h. Integrated sound with speakers.

D. Photo ID Card Production Hardware: Provide video capture device, camera, light kit, signature pad, card printer, and related peripherals compatible with ISMS software.

E. Control Panels: GE Security, M5, M2000 and M3000 PXNplus series as appropriate. The control panels shall be intelligent and fully stand-alone processor capable, making all local access control and alarm monitoring decisions without host server dependency. Control panels shall support and provide the following:1. UL listed under UL 294 and UL 1076; FCC Part 15 and CE compliant.2. Direct on-board support for industry standard RS232, RS422, Dial-up modem AT

command set, and 10/100Mb Ethernet communications interfaces to ISMS host.3. The 10/100Mb Ethernet NIC shall be onboard and support IT standard methods of

communications with ISMS host including configuration support for static IP addressing, dynamic DNS, DHCP and DES encryption. PCMCIA Adapters or external terminal server devices will not be acceptable.

4. Support redundant communications to ISMS host; primary communications via 10/100Mb Ethernet with automatic switchover to secondary communications via dial-up modem when detecting network failure.

5. RS232 and RS422 communications ports for cascading/clustering multiple control panels via a single communications port interface to ISMS host.

6. Flashable memory support for facilitating remote firmware updates from ISMS host server and operator workstations; control panels shall remain on-line and operational during firmware update process.


7. The control panel shall be able to be configured & diagnosed remotely through a standard browser interface, independently of the ISMS host application.

8. The control panel shall support local database retention in the event of power failure, without the use of batteries that have to be replaced. Minimum retention without primary power source shall be 20 days. When primary power is restored, the control panel shall automatically attempt to establish communications with the ISMS host, in the event communications to ISMS host is not available, the control panel shall automatically return to operation with its last local database configuration.

9. Control panel cabinets shall be an industrial grade enclosure with knockouts outs for field wiring and have a key-locked and tamper protected door.

10. Low voltage power supply with uninterruptible battery backup allowing continued operations for a minimum of 4 hours at full load

F. Control Panel Interface Boards: The ISMS control panels shall support on board and/or expansion interface boards for access control readers, alarm monitoring, and input/output control. Control panels shall support and provide the following as required:1. Access Control Reader Interfaces:

a. Shall support hard-wired connections to readers, including power and communications. Connections shall be supported at a minimum distance of 2,000ft. (610m) Utilizing 22AWG 2-pair shielded and unshielded cabling.

b. Shall support supervision, monitoring, and processing of the following:1) Reader tamper and communications.2) Status changes from locally wired door sensor and request to exit device.

c. Shall support card only and card-plus-keypad style readers of the following technologies:

(a) Proximity.(b) Smart Card.(c) Magnetic Stripe.(d) Wiegand.(e) Barcode.(f) BaFe Touch.(g) Biometrics.

2. Input / Output Point Interfaces:a. Shall support 4-State supervised alarm inputs.b. Shall support relay and TTL level output points.

G. IP Network Edge Door Control Panel: GE Security DirecDoor. The control panels shall be intelligent and fully stand-alone processor capable, making all local access control and alarm monitoring decisions without host server dependency. Control panels shall support and provide the following:1. UL listed under UL 294 and UL 1076; FCC Part 15 and CE compliant.2. Direct on-board support 10/100Mb Ethernet communications interfaces to ISMS host.3. The 10/100Mb Ethernet NIC shall be onboard and support IT standard methods of

communications with ISMS host including configuration support for static IP addressing, dynamic DNS, DHCP and DES encryption. PCMCIA Adapters or external terminal server devices will not be acceptable.

4. Support redundant communications to ISMS host; primary communications via 10/100Mb Ethernet with automatic switchover to secondary communications via dial-up modem when detecting network failure.

5. Flashable memory support for facilitating remote firmware updates from ISMS host server and operator workstations; control panels shall remain on-line and operational during firmware update process.


6. The control panel shall be able to be configured & diagnosed remotely through a standard browser interface, independently of the ISMS host application.

7. The control panel shall support local database retention in the event of power failure, without the use of batteries that have to be replaced. Minimum retention without primary power source shall be 20 days. When primary power is restored, the control panel shall automatically attempt to establish communications with the ISMS host, in the event communications to ISMS host is not available, the control panel shall automatically return to operation with its last local database configuration.

8. Control panel cabinets shall be an industrial grade enclosure with knockouts outs for field wiring and have a key-locked and tamper protected door.

9. IEEE 802.3af PoE or Auxiliary Uninterruptible Power Supply: Battery rated for a minimum 4 hours of continuous operation at full load.

H. Access Control Card Readers:1. Reader Technology: As specified by selected card technology and application

requirements; compatible with ISMS control panels and commercially available from industry leading manufactures that include but not limited to:a. GE Security.b. HID.c. Other approved equals.

2. The specified card and reader manufacturer shall support a full product line that offers multiple models and/or styles to fit various installation and application requirements including:a. Multi-technology readers that will read Proximity, Vicinity, and Mifare Smart

Card credentials simultaneously.b. Card only and card-plus-keypad style readers.c. Rugged, weatherized enclosures rated for indoor and outdoor mounting.d. Rated for mounting on metal and non-metal surfaces.e. Provide audible and visual indicators for reader status and validation of granted

and denied access.3. Provide quantities for each model and/or style indicated on drawings.

I. Cards: As specified by OWNER preference and application requirements; shall be CR-80 standard credit card size; top quality, durable and resilient PVC or PVC/polyester composite material.1. Card Technology:

a. Proximity: [Manufacturer], [Model], [Applicable Format/Description].b. Smart Card: [Manufacturer], [Model], [Applicable Format/Description].

2. Card Options:a. Single sided gloss white photo finish for direct printing.b. Double sided gloss white photo finish for direct printing.c. Stamped or marked with external ID reference number.d. Capable of being slot-punched at edge and equipped with strap clip for

attachment to cardholder's clothing.3. Provide initial quantity of [___].

J. Electric Door Hardware:1. Electronic locking devices shall have a separate power supply to support the locks

specified below. The unit shall incorporate integral battery charging capabilities and a fused line voltage input for a minimum of eight (8) individual locks. All power supplies shall be equipped with optional battery pack for up to 48 hours. The unit shall be equipped with a module to accommodate fire alarm NC contacts when a fire alarm activates.


2. All locks shall be fail-secure unless otherwise specified by the Security Consultant/Designer. Locks specified, as being fail-safe shall be installed in accordance to Section 5-2.1.6.2 of NFPA Life Safety Code 101.

3. The SECURITY CONTRACTOR shall coordinate with the OWNER approved Fire Alarm and Sprinkler Contractors for the interconnection of the specified ISMS.

4. Specified Products:a. Electric Strike: [Manufacturer], [Model].b. Magnetic Locks: [Manufacturer], [Model].c. Crash Bar: [Manufacturer], [Model].d. Electric Mortise Lock: [Manufacturer], [Model].

5. Provide quantities for each model indicated on drawings.

K. Door Hardware Configuration:1. Card access controlled doors shall be equipped with a passive infrared request-to-exit

device specifically designed for [magnetic lock] [electromechanical lock] release. Device shall be equipped with a DPST (NO & NC) 1-amp contact.

2. Card access controlled doors shall be equipped with a non-illuminating emergency exit button to momentarily deactivate the magnetic lock. The device shall be equipped with DPDT contacts with one side sending a REX to the ISMS control panel and the other directly interrupting power to the magnetic lock. The device shall fit into a single gang electrical box.

3. Card access controlled doors shall be equipped with a touch sense exit device to momentarily deactivate the magnetic locking device. The device shall be 24VDC and equipped with DPST (NC & NO) contacts.

L. Intrusion Detection Devices:1. Door Sensor Contacts:

a. Recessed magnetic door contacts shall be provided for all card access doors and doors requiring intrusion detection. Door contacts shall be provided on single doors and both leaves of double doors at locations indicated on drawings. Color to match existing finish.

b. Where building structure makes it impossible to install conduit within the wall or doorframe, the SECURITY CONTRACTOR shall substitute surface-mount contacts with armored cable for the specified contacts.

c. Heavy-duty door contacts with armored cable shall be provided for all Roll-Up Doors where indicated on the drawing.

d. All devices shall be wired point to point and to the nearest ISMS control panel interface.

2. Motion Detectors:a. [WALL MOUNTED] [CEILING MOUNTED] passive infrared (PIR) motion

detectors shall be provided where indicated on drawings. Motion detectors shall be masked or oriented to minimize the likelihood of nuisance alarms caused by environmental conditions.

b. All devices shall be wired point to point and to the nearest ISMS control panel interface.

c. A 12VDC centralized power supply shall be utilized to power motion detectors.

3. Glass Break Detectors:a. Acoustic glass break detectors with latching LED shall be provided where

indicated on drawings. The devices shall be surface mounted for attractive and


unobtrusive appearance. The device shall have a 25', 360-degree range measured to the furthest point on all type of glass.

b. All devices shall be wired point to point and to the nearest ISMS control panel interface.

c. A 12VDC centralized power supply shall be utilized to power glass break detectors.

4. Specified Products:a. Provide quantities for each type and model indicated on drawings.b. Door sensor contacts:[Manufacturer], [Model].c. Motion Detectors:[Manufacturer], [Model].d. Glass Break Sensors:[Manufacturer], [Model].


PART 3 EXECUTION

3.1 SECURITY CONTRACTOR

A. The SECURITY CONTRACTOR shall be a local installation and service organization, currently recognized as a factory authorized representative by the manufacturer of the specified system.

B. The SECURITY CONTRACTOR shall provide a minimum of (3) references whose systems are of similar complexity and have been installed and maintained by the SECURITY CONTRACTOR in the last (5) years.

C. At time of bid, the SECURITY CONTRACTOR shall be licensed by the state or local jurisdiction to perform security work within the state. Contractors who have security licenses or permits pending shall not be considered acceptable for bidding on this project.

D. The SECURITY CONTRACTOR shall assure that all personnel working on the project are registered with the state or local jurisdiction Systems Licensing Board as provided for by current state statutes.

E. At the time of bid, the SECURITY CONTRACTOR shall provide satisfactory evidence of liability insurance and Workmen's Compensation coverage for employed personnel as required by law.

3.2 PROJECT MANAGEMENT

A. The SECURITY CONTRACTOR shall provide an on-site, factory-trained technician to assist, advise and manage installing personnel.

B. All of the SECURITY CONTRACTOR'S personnel and operating forces including subcontractors and delivery personnel, shall be made aware of, and shall comply at all times, with the regulations, project requirements, and directions of responsible OWNER personnel.

3.3 PERSONNEL

A. The SECURITY CONTRACTOR’S personnel shall be qualified to accomplish all work promptly and satisfactorily. The OWNER shall be advised in writing of all designated service and support personnel responsible for installation as well as pre and post warranty service.

B. The SECURITY CONTRACTOR shall provide proof that designated service and support personnel have successfully completed the appropriate level of both hardware and software training offered by the manufacturer for installation and maintenance of the specified system.


3.4 INSTALLATION

A. The SECURITY CONTRACTOR shall install all system components and appurtenances in accordance with the manufacturer’s specifications, referenced practices, guidelines, and applicable codes. Furnish all necessary interconnections, services, and adjustments required for a complete and operable system as specified. 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.

B. All wiring is to be installed in dedicated conduit throughout. Cable shall not be pulled into conduits or placed in raceways, compartments, outlet boxes, junction boxes, or similar fittings with other building wiring.

C. All low voltage wiring outside the control console, cabinets, boxes, and similar enclosures, shall be plenum rated where required by code.

D. All wiring conductors connected to terminal strips shall be individually numbered and each cable or wiring group being extended from a panel or cabinet to a building mounted device shall be identified with the name and number of the particular device as identified and shown on building drawings.

E. All exposed wiring inside and outside the control console, cabinets, boxes, and similar enclosures, shall be dressed down neatly and secured with wiring cleats or wire ties.

F. All exposed metallic flexible conduit and armored cable shall be dressed down neatly and secured with low profile, metal fasteners.

G. All cabinets, boxes, and similar enclosures containing security system components and/or cabling and which are easily accessible to employees or to the public shall be provided with a lock. Boxes above ceiling level in occupied areas of the building shall not be considered to be accessible.

H. All junction boxes and small device enclosures below ceiling level and easily accessible to employees or the public shall be covered with a suitable cover plate and secured with tamper proof screws.

I. End-of-Line resistors shall be installed at the field device location and not at the controller panel location.

J. System devices identified on building drawings are intended to generally indicate areas where such devices are to be located. Security Contractor shall be responsible for determining final location of these devices in accordance with OWNER’S requirements.

K. Riser diagrams are schematic and do not show every conduit, wire box, fitting, or other accessories. Provide such materials as necessary for a complete and functioning installation. Install in accordance with referenced codes and these specifications. Use weatherproof equipment or covers where installed in areas exposed to weather.


3.5 COMMISSIONING AND TRAINING

A. The SECURITY CONTRATOR is required to place entire system into full and proper operation as designed and specified.1. Verify that all hardware components are properly installed, connected,

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

functional requirements.

B. The SECURITY CONTRACTOR shall 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:1. Submit documented test plan to OWNER at least (14) days in advance of acceptance

test, inspection, and check-off.2. 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.

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

4. The 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.

C. The SECURITY CONTRACTOR shall provide system operations, administration, and maintenance training by factory trained personnel qualified to instruct:1. OWNER will designate personnel to be trained.2. Provide printed training materials for each trainee including product manuals, course

outline, workbook or student guides, and written examinations for certification.3. Provide hands-on training with operational equipment.4. Training shall be oriented to the specific system being installed under this contract as

designed and specified.

END OF SECTION


Documents

Facility Commander Wnx v7.0 A&E Specification v7 AE Spec 080915.doc · Web viewException: Controlled devices, such as electric locks, door actuators, sensors, etc., are specified