state of west virginia new state office building fairmont ... state office... · conditions and...

State of West Virginia New State Office Building � Fairmont General Services Division 416 Adams Street Project No. GSD 136417

INTEGRATED SECURITY MANAGEMENT SYSTEM 281300 � 1

SECTION 281300 � INTEGRATED SECURITY MANAGEMENT SYSTEM (ISMS)

PART 1 � GENERAL

1.1 RELATED DOCUMENTS

A. Drawings and general provisions of the Contract, including General and Supplementary Conditions and Division 1 Specification Sections, apply to this Section.

1.2 RELATED SPECIFICATION SECTIONS

A. Basic Electrical Requirements: 260100

B. Common Work Results for Electrical: Section 260500

C. Raceways and Boxes: Section 260533

D. Cable Trays: Section 260536

E. Low�Voltage Electrical Power Cables: Section 260519

F. Data Communications Circuits: Division 26

1.3 SUMMARY

A. Functional Description: Contractor shall provide an integrated security management system for the facility that operates through a secure internet connection with the existing central security system server located at the State Capitol Complex in Charleston, WV. The systems shall incorporate proximity card readers, electronic combo locks, duress buttons and other security devices as indicated on the drawings.

1. The security system shall have an on�site monitoring point located in the Central Control Room (Room # 211) with contractor supplied desktop computer and monitor. This onsite monitoring point shall be supplied with an access card reader/writer capable of serving as an enrollment station for creating access cards. Contractor to provide minimum of 500 access cards.

2. The system shall utilize and be fully compatible with the State’s existing window’s based ‘Facility Commander’ software (Lenel/United Technologies Corp/GE). Contractor to include any software upgrades (excluding incremental licensing) required to provide a fully functional system for the facility.

3. Security system control panel shall be located in the secure second floor data closet. 4. The supplied systems shall incorporate a fully functional CCTV system with cameras as

noted on the drawings. Provide a Digital Video Recorder capable of storing a minimum of three month’s data from all cameras. System shall be provided with secure IP addressable connection capable of monitoring/reviewing data from a remote location. While the CCTV system shall be operated and monitored from the control center located in Central Control Room (Room # 211), control panels, DVR and other critical equipment shall be located in the secure second floor Data Closet (Room # 204).



B. The Contractor shall provide all necessary wiring, cabling, labor, tools, equipment, and ancillary materials required to provide a complete and operational ISMS..

C. Requirements are indicated elsewhere in these specifications for work including, but not limited to:

1. Shall interface to the existing enterprise system at the West Virginia State Capitol. 2. Provide additional FC Wnx enterprise level software and SQL licenses as necessary to

support the server, workstation, readers and client workstation expansion counts as per drawings.

3. Shall be able to read cards to the existing West Virginia wide ISMS managed from the Capitol.

4. Conduit, 110 VAC power extensions, and other electrical work. 5. Electric door hardware, egress devices, Maglock power supplies and battery backup for

card reader doors shall be furnished and installed by the Division 8 contractor. 6. The Contractor shall attach to the local area network for the connections as shown on

the attached drawings for IP cameras, NVMS server and workstations, access control server and work stations, control panels and intrusion panel. NVMS server, access control server and work stations to be located as per drawings. Contractor to locate switch and server in contractor provided rack as per specification. Rack must be a minimum of 36 inches deep. See rack specification section.

D. The ISMS shall provide management, control, and monitoring of card access and alarms, locally and at the Capitol Complex. It shall integrate with the IP camera network video management system (NVMS) via OEM API interface and intrusion system via Osbourn Hoffman software interface.

E. The extent of ISMS work is defined to include but not limited to the following:

1. The ISMS client software shall be installed on PC and located as per drawings, with minimum 22 inch desktop monitor and connected to the LAN.

F. 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. Provide workstations as per drawings. 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.

G. This section covers the provision of ISMS including, but not limited to all items and sub�systems shown on drawings or otherwise required by these specifications.

1. ISMS computer hardware, software, and control panels for access control and alarm management.

2. Power over Ethernet (POE) Switches 3. Card readers and other security input/output devices for access control and alarm

monitoring of secured areas 4. Automatic Doors & Operators 5. Vehicle Access & Parking Gate Operators 6. Video Surveillance System and Cameras



7. Video Recorders 8. Intrusion Detection System 9. Video Management Software 10. Bading System

1.4 DEFINITIONS

A. CCTV: Closed�circuit television.

B. CPU: Central processing unit.

C. Credential: Data assigned to an entity and used to identify that entity.

D. dpi: Dots per inch.

E. DTS: Digital Termination Service. A microwave�based, line�of�sight communication provided directly to the end user.

F. GFI: Ground fault interrupter.

G. Identifier: A credential card; keypad personal identification number; or code, biometric characteristic, or other unique identification entered as data into the entry�control database for the purpose of identifying an individual. Where this term is presented with an initial capital letter, this definition applies.

H. I/O: Input/Output.

I. LAN: Local area network.

J. Location: A Location on the network having a PC�to�controller communications link, with additional controllers at the Location connected to the PC�to�controller link with a TIA 485�A communications loop. Where this term is presented with an initial capital letter, this definition applies.

K. PC: Personal computer. Applies to the central station, workstations, and file servers.

L. PCI Bus: Peripheral Component Interconnect. A peripheral bus providing a high�speed data path between the CPU and the peripheral devices such as a monitor, disk drive, or network.

M. PDF: Portable Document Format. The file format used by the Acrobat document�exchange�system software from Adobe.

N. POE: Power over Ethernet

O. RAS: Remote access services.

P. RF: Radio frequency.

Q. ROM: Read�only memory. ROM data are maintained through losses of power.

R. TCP/IP: Transport control protocol/Internet protocol incorporated into Microsoft Windows.



S. TWAIN: Technology without an Interesting Name. A programming interface that lets a graphics application, such as an image editing program or desktop publishing program, activate a scanner, frame grabber, or other image�capturing device.

T. UPS: Uninterruptible power supply.

U. USB: Universal serial bus.

V. WAN: Wide area network.

W. WAV: The digital audio format used in Microsoft Windows.

X. WMP: Windows media player.

Y. Wiegand: Patented magnetic principle that uses specially treated wires embedded in the credential card.

Z. Windows: Operating system by Microsoft Corporation.

AA. Workstation: A PC with software that is configured for specific, limited security�system functions.

BB. WYSIWYG: What You See Is What You Get. Text and graphics appear on the screen the same as they will in print.

1.5 SUBMITTALS

A. Product Data: For each type of product indicated. Include rated capacities, operating characteristics, and provided specialties and accessories. Reference each product to a location on Drawings.

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

C. Shop Drawings: Include plans, elevations, sections, details, and attachments to other work. All shop drawings shall be prepared in AutoCAD software. In addition to the drawings, the Contractor shall provide a CD containing the identical information. Drawings shall be B size or larger.

D. Shop drawings shall include:

1. Diagrams for cable management system. 2. System labeling schedules, including electronic copy of labeling schedules that are part

of the cable and asset identification system of the software specified in Parts 2 and 3. 3. Wiring Diagrams. For power, signal, and control wiring. Show typical wiring schematics

including the following:

a. Workstation outlets, jacks, and jack assemblies. b. Patch cords. c. Patch panels.

4. Cable Administration Drawings: As specified in "Identification" Article. 5. Battery and charger calculations for server, workstations, and controllers.



E. Submittal data shall contain manufacturer's data on all hardware and software products required by the specification.

F. Software submittals shall contain narrative descriptions of sequences of operation, program listings, point lists, and a complete description of the graphics, reports, alarms and configuration to be provided with the workstation software. Information shall be bound or in a three ring binder with an index and tabs.

G. Field quality�control reports.

1.6 SYSTEM OPERATING AND MAINTENANCE MANUALS

A. 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: Copies of the final as�built drawings shall be provided to the owner in

DXF format using the latest version of AutoCAD.

B. The operation and maintenance manuals shall contain all information necessary for the operation, maintenance, replacement, installation, and parts procurement for the entire Integrated Security System. This documentation shall include specific part numbers and software versions and dates. A complete list of recommended spare parts shall be included with the lead time and expected frequency of use of each part clearly identified.

C. Following project completion and testing, the Integrated Security Management System Vendor will submit as�built drawings reflecting the exact installation of the system. The as�built documentation shall also include a copy of all application software both in written form and on diskette.

D. Operation and Maintenance Data: For security system to include in emergency, operation, and maintenance manuals. In addition to items specified in Division 1 Section "Operation and Maintenance Data," include the following:

1. Microsoft Windows software documentation. 2. PC installation and operating documentation, manuals, and software for the PC and all

installed peripherals. Software shall include system restore, emergency boot diskettes, and drivers for all installed hardware. Provide separately for each PC.

3. Hard copies of manufacturer's specification sheets, operating specifications, design guides, user's guides for software and hardware, and PDF files on CD�ROM of the hard�copy submittal.

4. System installation and setup guides with data forms to plan and record options and setup decisions.

E. Software: 1 set of fully functional ISMS software in manufacturer’s original media packaging, temporarily licensed for a (30) day evaluation period.

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 Contractor shall guarantee that the ISMS application software/firmware remains current at all times during the warranty period with the latest enhancements, and is supported by the ISMS manufacturer with unlimited remote diagnostics capability and technical phone support.

C. The Contractor shall perform manufacturer’s recommended preventative maintenance on all applicable components and/or devices. (requires a service contract)

D. The 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. Provide a separate proposal for an extended warranty and maintenance service contract for consideration by Owner.

1. Length of Contract: 3 years. 2. Submit payment terms and conditions with proposal.

G. Updates to the manufacturer’s software shall be provided at no charge during the warranty period.

1.8 QUALITY ASSURANCE

A. Installer Qualifications: An employer of workers trained and approved by manufacturer.

B. Source Limitations: Obtain central station, workstations, controllers, Identifier readers, and all software through one source.

C. Electrical Components, Devices, and Accessories: Listed and labeled as defined in NFPA 70, by a qualified testing agency, and marked for intended location and application.

D. Comply with NFPA 70, "National Electrical Code."

E. Comply with NFPA 101, “Life Safety Code”

F. All equipment or wiring used in conditioned air streams, spaces or return air plenums shall comply with NFPA 90A Flame/Smoke/Fuel contribution rating of 25/50/0 and all applicable building codes or requirements.

G. Comply with National Electrical Manufacturers Association (NEMA).

H. Comply with FCC rules, Part 15 regarding Class A radiation for computing devices and low power communication equipment operating in commercial environments.

I. UL�294 Listed Access Control Systems.

J. UL�1076 Listed Line Supervision.

K. Comply with NIST Triple DES Certificate #206

L. Comply with Americans with Disabilities Act (ADA).



M. Comply with all applicable National, State and Local Codes.

1.9 SECURITY SYSTEMS COORDINATION

A. Coordinate the installation, operation and control of the whole building ISMS with the Owner’s Rep.

1.10 EXTRA MATERIALS

A. Furnish extra materials described below that match products installed and that are packaged with protective covering for storage and identified with labels describing contents.

1. Card Readers: One percent (1%), rounded down to the nearest whole number, minimum of one (1) device.

1.11 DELIVERY, STORAGE, AND HANDLING

A. Central Station, Workstations, and Controllers:

1. Store in temperature� and humidity�controlled environment in original manufacturer's sealed containers. Maintain ambient temperature between 50 and 85 deg F, and not more than 80 percent relative humidity, noncondensing.

2. Open each container; verify contents against packing list; and file copy of packing list, complete with container identification, for inclusion in operation and maintenance data.

3. Save original manufacturer's containers and packing materials and deliver as directed under provisions covering extra materials.

PART 2 � PRODUCTS

2.1 MANUFACTURERS

A. Manufacturers: Subject to compliance with requirements, provide products by one of the following:

1. Lenel/UTC/GE Security 2. Or equal.

B. All manufacturers’ published specifications pertaining to this specialization shall have the same force and effect as if shown here in full.

C. This integrated security management system shall be capable of operating through a secure internet connection with the existing central security system server located at the State Capitol Complex in Charleston, WV. System shall function such that each device can be monitored at State Capiton Complex. Provide all components and programming required for complete system monitoring.

D. Substitutions shall have minimum system capacities, minimum system features and require the same type/style cables and power requirements as the specified brand. Final review of brand



substitution shall take place prior to acceptance and Prime Contractor shall be responsible to make any required changes to meet specification prior to system acceptance,

E. Provide all ISMS access control hardware and software as standard catalog product offering of a single manufacturer.

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

G. Controlled devices, such as electric locks, door actuators, power supplies etc., are specified elsewhere and provided by OTHERS.

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.

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:

6. Real time and batch processing of data via ODBC, JDBC or OLE DB over a network connection.

7. Insert, update, and delete record information. 8. Automatic download of data to ISMS control panels based on database changes. 9. Provide audit trail in the operator history/archive database for all database changes

initiated by the interface. 10. 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.

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

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

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



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

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

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

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

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

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

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

21. 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 is capable of providing 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:

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

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

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

5. ISMS system configurations with multiple regional application/ database servers shall provide at a minimum the following redundancy and failover capability:

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

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



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

9. 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,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.

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.

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.

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. Input/Output Control

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

L. Alarm Management

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

M. 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 & time b. 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.

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. Source device location description & reference. g. 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.

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

O. 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 9760 5) Generic User�definable

2. Digital Video Recorders: The ISMS shall provide a fully integrated digital video recorder, Network Video recorders 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 100/1000Mb 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 and NVR 20, 40 or 60 model 6) American Dynamics Intellex DVMS8000. 7) Digital Watchdog DWPro. 8) Integral Technologies DVXi, DSXpress. 9) NiceVision Harmony & Pro. 10) Panasonic HD500. 11) Pelco DX8000. 12) Avigilon VMS

P. 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:

1) Bi�directional alarm event processing for monitoring and acknowledgement 2) Receiving ISMS card access activity events 3) Receiving digital input events 4) Receiving intrusion zone events 5) Control of operator logins 6) Control of alarm point monitoring On/Off 7) Control of digital input points Enable/Disable 8) Control of digital output points Open/Close 9) Control of intrusion zones Arm/Disarm 10) Control of control panel Modes

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

2.3 SOFTWARE

A. Application & Database Server Software: Will be provide by the Owner

B. Client Workstation Software:

1. Operating System: Microsoft Windows Windows 7.

C. Integrated Security Management System Software:

1. Security Contractor shall provide GE Security, Facility Commander Wnx 7.7 or latest a. License for additional client workstations. (As per drawings) b. License for all access control readers. (As per drawings) c. License for digital video surveillance cameras integration. (As per drawings)

2. Facility Commander Wnx 7x Photo ID Card Production Option. (As per drawings) 3. Facility Commander Wnx 7.x Application Program Interface Option. 4. Security Contractor shall provide Facility Commander Wnx 7.x Integrated Digital Video

3rd Party Driver Option, individually licensed separately per application/database server. (provide for Avigilon per NVR)

5. Facility Commander Wnx 7.x Client Redundancy Device Fail�Over Option, licensed separately per application/database server.

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

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

8. Security Contractor shall provide Facility Commander Wnx 7.x 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 ISMS supplier, factory�configured with all software pre�loaded and tested.



B. 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. Dell Poweredge R710 Rack server b. Xeon Quad Core E5504/2.0Ghz c. 4Gb Ram d. 4X73Gb Raid10 SAS Hot Plug Hard drive e. Redundant power supply f. Dvd+/�Rw g. Dual Port Gigabit NIC h. Internal/Ext Scsi Tape Drive Ready i. 3Yr Onsite next business day Warranty

1) Windows 2003 / SQL 2005 Server software preload and application configuration service per server

2) Microsoft SQL Server 2008 Standard Edition SFTW, Includes 10 Client Access Licenses (5 Device CAL)

3) Windows 2008 Server software

2. Operator Workstation Minimum Requirements:

a. Dell Optiplex 990MT Minitower Workstation b. Intel core I5 2400 Processor (3.1Ghz,6M) c. 4GB RAM, 2 X 250GB SATA HD Raid 1 d. Dual 512MB AMD Radeon HD 6350 (2 DVI) e. 16X DVD+/�RW, Gigabit NIC f. Windows 7 Pro 32 Bit or 64 Bit g. Dual 24 Inch HD monitor DVI or HDMI h. USB Mouse and keyboard i. 3�Year On�Site Next Business Day Warranty

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

D. 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: 1) Proximity. 2) Smart Card. 3) Magnetic Stripe. 4) Wiegand. 5) Barcode. 6) BaFe Touch. 7) Biometrics.

2. Input / Output Point Interfaces:

a. Shall support 4�State supervised alarm inputs. b. Shall support relay and TTL level output points.

E. Power Over Ethernet Switch:

1. GE�DSSG�244�POE Power over Ethernet Managed Switch or equal

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

G. 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 � transition series b. 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.

H. Card Holder Management and Enrollment 1. The SMS shall include an employee management system integrated with the access

control system. This employee management functionality shall allow the enrollment of card holders into the database, capturing of images, and import/export employee data. This functionality shall also allow the user to assign or modify access privileges of a card holder.

2. The SMS shall include a state�of�the�art credential creation and production system

integrated with the card holder management system. This shall allow the creation of



different badge types based on database fields and the use of security colors to allow security officers to quickly identify personnel access authority by the badge design.

I. Badge Creation 1. Image Capture

a. Each SMS photo imaging workstation shall include all equipment required to capture a high quality portrait image, with flash lighting and a high quality RGB digital video camera. The photo imaging workstation shall allow the camera user to view a live video image of the subject on the screen. The user shall view the subject in an upright position as they are captured.

b. While capturing subjects, the user shall have the option of capturing a new image of any subject without affecting the subject’s record. The photo imaging workstation shall provide a digitizer color control window in order to adjust the contrast and brightness of images. For convenience, default settings shall be provided.

c. The system shall provide the ability to move via mouse a “capture window” over any portion of the live image displayed on the monitor and store only the image information within the outline of the window. The SMS shall include the ability, upon command, to preview, online and in full color, the badge as it will appear when printed. This preview mode shall require less than 10 seconds to create a complete example of the badge online.

d. SMS image capture, storage, and hardware compression techniques shall be in compliance with the ANSI X3L2.8 standard or JPEG.

2. Pre�defined Badge Formats a. The badge format, including background color, layout, location of photo image,

applicable graphics or company logos, text, etc., shall be completely and automatically determined by the system based on employee record information. Where choices are available to the user, choices are to be made via pre�defined list boxes to avoid user errors in spelling and badge assignment errors.

3. Multiple Badge Formats/Badge Layout Services a. The successful vendor shall provide services for creating badge layouts based on

this specification. A single badge layout shall be provided with the system. Additional badge layouts and logos shall be available through the vendor if required. The screen design and database configuration shall be done in conjunction with the badge layout design.

4. Color Credential/Badge Printing a. Credential printers shall be high�density dye�sublimation type printers offering, a

minimum of 300 dots per inch resolution with a clear overlay option for high durability. The credential media used shall be compatible with the credential printer. The credential printer shall be able to print one�sided or two�sided credentials in credit card sizes and in portrait or landscape orientations.

b. The user shall be able to print the badge as soon as it is created or to send the badge to a print queue for later batch printing. Within the print queue the user may print all badges, print a selected badge, and delete a selected badge or preview without printing.

c. The credential printer shall incorporate a card cleaning system that cleans the front and back of the card simultaneously before printing begins.

5. Batch Printing a. The CUSTOMER photo imaging user shall be able to print a credential

immediately or send it to a print queue. The SMS photo imaging workstation shall have the ability to print a large volume of badges with a single command using a print queue screen. At the print queue, the user shall have the option of printing all badges, printing selected badges, deleting a badge, or previewing badges without printing.

6. Security Color Levels



a. The SMS shall be able to print badges with varying, user�defined security color levels created from the entire RGB spectrum. For example, a blue background badge may designate SECURITY, a orange background badge may designate EMPLOYEE, a red background badge may designate VENDOR, and a green background badge may designate ESCORT REQUIRED.

7. Online Magnetic Stripe Encoding a. Utilizing a magnetic stripe encoder device, the SMS shall allow for magnetic stripe

encoding of all its permanent credentials. This magnetic stripe shall conform to ABA Track II and ANSI specifications. Track II has a recording density of 75 bits per inch and five bits per character that results in 40 numeric characters including start sentinel, end sentinel and longitudinal redundancy check character.

b. The user may select a badge for encoding or delete a selected badge. Encoding and verification of the badge is performed on�line.

8. Search Records a. The SMS shall allow the user to search for records and images using search

criteria on any field(s) in the database. The user shall be able to enter the search criteria for one or a combination of fields

J. 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: GE ProxLite card Model 7000055001 or equal

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 500 cards 4. Provide Keyboard Wedge reader for entering new users

K. Computer Hardware

1. Unless otherwise stated, computer equipment needed for each workstation consists of the following minimum requirement:

a. 3 GHz Pentium 4 processor b. 1 GB of RAM c. Serial port, parallel port, USB port d. 10/100 Ethernet NIC e. 80 GB hard drive f. 3½" diskette drive g. CD�RW drive h. High resolution (minimum 1920 x 1080), 22” flat panel display i. Optical mouse and full function keyboard j. Audio sound card and speakers k. License agreement for all applicable software l. Provide an alarm printer and a separate report/graphics printer. The alarm printer

shall be an Epson Inkjet or equivalent and the report printer shall be a black�and�white HP LaserJet



m. Uninterruptible power supply

L. Alarm Monitoring and Display Workstation

1. The alarm monitoring workstation shall be provided with full imaging display capability and shall be configured to perform alarm monitoring operations. The following major alarm Monitoring tasks shall be included: graphical alarm monitoring, acknowledging alarms, performing traces, output control functions, and badge record lookup. In addition, the alarm monitoring workstation shall also be utilized as an administration workstation as required.

2. The alarm monitoring and display workstation shall be the main workstation for providing the alarm monitoring and access control features described in this specification.

M. Integrated Workstation

1. The integrated workstation shall be provided with full alarm monitoring and photo imaging functionality on a single workstation. Full imaging display capability and all administrative operations shall be provided.

2. The integrated workstation shall be the main alarm monitoring workstation, for configuring the access control features described in this specification, for image capture, badge production, and employee enrollment. The integrated workstation shall consist of the same hardware as the alarm monitoring workstation, with the following exceptions:

a. RGB video camera with flash lighting, stand, and backdrop. b. PCI video capture board for PC c. PVC card printer d. Photo imaging Software option

3. Workstation Options:

a. Configurable bar code printing b. Signature capture equipment

N. Photo Imaging Workstation

1. The photo imaging workstation shall be a complete electronic photo ID computer workstation that creates high quality, tamper�resistant color credentials in a production environment. This workstation shall enroll card holders and maintain personnel information and images into the SMS relational database. This information can be recalled at any time to modify existing records, verify employee status, or reissue new credentials.

2. The photo imaging workstation shall be the primary workstation for employee enrollment, badge production, and access privileges assignment to card holders. The photo imaging workstation shall consist of the same hardware as the alarm monitoring workstation, with the following exceptions:

a. RGB video camera with flash lighting, stand and backdrop. b. PCI video capture board for PC c. PVC card printer d. Photo imaging software option

3. Workstation Options:

a. Configurable bar code printing



b. Signature capture equipment

O. Badging System 1. General PVC Card Printer Fargo DTC550: The contractor shall provide a high density

dye�sublimation/resin thermal transfer type image printing system which prints two sides, edge to edge, directly onto a white�unfinished 0.030 PVC, PVH or PVCH card at a rate of approximately 20 seconds per card. Provide Three (3) spare DTC 550 Printer Ribbon.

2. The card media is to be fed to the printer automatically through a card hopper that shall accommodate 100 30�mil (0.030") thick cards. The IBAS shall download the badge layout directly to the printer and, using a dye diffusion thermal transfer process, print it directly onto the card. The dyes are to be embedded into the top layer of the card, making it difficult to permanently alter its appearance. The card production system shall also apply a clear ultraviolet security overprint to the entire printable area of the card. This overprint shall expose card tampering when viewed under reflected or ultraviolet light.

3. Web Camera Pro 9000: The contractor shall provide a Logitech Web Camera Pro 9000 4. Photo Imaging Workstation: The photo imaging workstation is a complete electronic

photo ID computer workstation that creates high quality, tamper�resistant color credentials in a production environment. This workstation shall enroll card holders and maintain personnel information and images into the IBAS relational database. This information can be recalled at any time to modify existing records, verify employee status, or reissue new credentials.

5. The photo imaging workstation shall be the primary workstation for employee enrollment, badge production, and access privileges assignment to card holders. The photo imaging workstation shall consist of the same hardware as the alarm monitoring workstation, with the following exceptions:

a. RGB video camera with flash lighting, stand and backdrop b. PCI video capture board for PC c. PVC card printer d. Continuum LAN�SEC�U�P� B�USB Software License with USB Key.

P. 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. 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 CONTRACTOR shall coordinate with the Fire Alarm and Sprinkler Contractors for the interconnection of the specified ISMS.

4. Specified Products: Door hardware provided by Section 08712.

a. Electric Strike: see door hardware specification in section 08712 b. Crash Bar: see door hardware specification in section 08712 c. Electric Mortise Lock: see door hardware specification in section 08712 d. Provide quantities for each model indicated on drawings.

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

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



R. Intrusion Detection Devices:

1. Door Sensor Contacts:

a. Recessed magnetic door contacts with dual output 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. Specified Products:

a. Provide quantities for each type and model indicated on drawings. b. Request to exit: [GE] RCR�REX�W or equal [counts per drawing] c. Door sensor contacts:[GE], [1074D�N] or equal [counts per drawing] d. Intrusion Panel [GE], NX�8E or equal – Size IO as per drawings

2.5 SUMMARY � INTEGRATED IP BASED CCTV

A. Scope of Work

1. The Contractor shall include all necessary wiring, cabling, labor, tools, equipment, and ancillary materials required to provide a complete and operational Video Management System.

2. Requirements are indicated elsewhere in these specifications for work including, but not limited to:

a. Conduit, 110 VAC power extensions, and other electrical work. b. Provide cameras, encoders, POE switches, NVMS server and workstations as per

drawings. c. The Security Contractor shall attach to owner local area network for the

connections as shown on the attached drawings. Contractor switch and server are to be located in contractor provided rack. See rack specification.

3. NVMS shall integrate with the Facility Commander Wnx card access system via software.

4. The extent of VMS work is defined to include but not limited to the following:

a. Security Contractor shall provide Hardware and software as per drawings connected to the OWNER LAN, WAN or VLAN.

b. Security Contractor shall provide Avigilon vandal resistant cameras outdoors as specified in the drawings.

5. Installing the Video Management System and bringing it to operational status for acceptance shall include but not limited to the following:

a. Determine hardware, software, and operations requirements for implementation.



b. Install hardware and software. c. Setup and configure communications between the host server, operator

workstations, and cameras. Provide workstation as per drawings. d. Setup and configure VMS application and database. e. Test VMS operations based on a point�by�point walkthrough inspection. f. Perform end�user training.

B. Integrated IP Based CCTV

1. All systems and components shall have undergone a thoroughly documented quality assurance process by the manufacturer. The manufacturer’s warranty, extended warranty and replacement policies shall be included for each specified component.

2. The Network Video Management Software, NVR Hardware and related components shall be installed and commissioned by authorized integrators trained and certified by the manufacturer. Certification and training for authorized integrators shall be available from the manufacturer.

3. The manufacturer shall have a dedicated professional services group providing Integrators and End Users the following fee�based services including but not limited to: training, installation, commissioning, remote diagnostics and integration with 3rd party software and hardware systems.

C. Description

1. The Network Video Management Software (NVMS) shall be Avigilon Control Center (ACC) version 4.10 or later. The NVMS shall be installed on the access control work station and integrated with Facility Commander Wnx software as per drawings.

2. The Network Video Management Software (NVMS) shall be an enterprise level software solution that shall be scalable from one client, server, and camera to hundreds of clients, servers, and cameras.

3. The Network Video Management Software (NVMS)shall consist of server software applications and client software applications.

4. The Network Video Management Software (NVMS)shall be available in the following languages:

a. English b. Finnish c. French d. German e. Italian f. Portuguese g. Spanish h. Swedish

5. The Network Video Management Software (NVMS) shall include the following applications:

a. Server Software Applications

1) Control Center Server 2) Control Center Admin Tool

b. Client Software Applications

1) Control Center Client



2) Control Center Web Client 3) Control Center Player 4) Control Center Camera Installation Tool

6. The Network Video Management Software (NVMS) shall permit server and client software applications to be installed and run on both the same computer or on separate computers.

7. The Network Video Management Software (NVMS) shall support edge based storage and processing of video and audio inputs.

8. The Network Video Management Software (NVMS) shall support High Definition Stream Management (HDSM) architecture which includes:

a. Support for industry standard JPEG2000, MJPEG, MPEG�4, and H.264 compression formats

b. Support for reducing the required client bandwidth and processing power by only transmitting what is necessary to view the video stream at full quality (e.g. if a user is viewing a 16MP camera in a 1MP window then a 1MP representation of the 16MP image shall be transmitted).

9. The Network Video Management Software (NVMS) shall support recording and management of video and audio sources including:

a. Avigilon HD IP Cameras (1 – 5 Megapixel) b. Avigilon HD IP Dome Cameras (1 – 5 Mega pixels) c. Avigilon Panoramic HD IP Dome Cameras (8 Megapixels) d. Avigilon HD H.264 Day/Night IP Cameras (1– 2 Megapixel) e. Avigilon HD H.264 Day/Night IP Dome Cameras (1– 2 Megapixel) f. Avigilon HD PRO IP Cameras (2 – 16 Megapixel) g. Composite video from analog cameras, PTZ domes and thermal imagers via

Avigilon ENC�4PORT analog encoder h. Third�Party IP Devices

1) ACTi Cameras/Encoders 2) Arecont Cameras 3) Axis Cameras/Encoders 4) Mobotix Cameras 5) ONVIF Cameras 6) Panasonic Cameras 7) Pelco Cameras 8) Samsung Cameras 9) Sanyo Cameras 10) Sightlogix Cameras 11) Sony Cameras 12) VideoIQ Cameras

10. The Network Video Management Software (NVMS) shall support recording and monitoring video and audio streams from sources with bandwidth up to 90 Mbit/sec, frame rate up to 60 fps, and video resolution up to 16MP (4872x3248).

11. The Network Video Management Software (NVMS) shall support the decompression of H.264 video through the client graphics card instead of using the client processing power.

12. The Network Video Management Software (NVMS) shall require no proprietary recording hardware, no hardware multiplexer or time�division technology for video and audio recording or monitoring.



13. The Network Video Management Software (NVMS) shall not limit the storage capacity and shall allow for upgrades of recording capacity.

14. The Network Video Management Software (NVMS) shall digitally sign recorded video and audio using 256�bit encryption so video can be authenticated for evidentiary purposes.

15. The Network Video Management Software (NVMS) shall securely transmit all command and control data via TCP/IP using cryptographic keys based on SSL to prevent eavesdropping or tampering.

16. The Network Video Management Software (NVMS) shall be installed on systems which meet or exceed the manufacturer’s requirements found in this link: http://avigilon.com/support/req/

17. The Network Video Management Software (NVMS) shall also be available in turn�key NVR platforms utilizing enterprise�grade servers and workstations pre�loaded with NVMS software and tested to manufacturer specifications for deployment in enterprise applications.

18. The Network Video Management Software (NVMS) shall be available in either a licensed Enterprise or Standard edition.

19. The Network Video Management Software (NVMS) shall support integration with the GE Security Facility Commander Wnx v7.x platform for Electronic Access Control and Alarm Monitoring (Access System).

a. Network Video Management Software (NVMS) will provide the mechanism by which individual alarm(s) from the Access system can be pre�selected and configured to be monitored and, in turn, trigger event driven video operations

b. The Network Video Management Software shall support software level integration (via the Wnx API) with GE Facility Commander for facilitating real�time response to monitored events processed by Wnx v7.x. Alarm events. The API integration should include:

1) Bi�directional alarm event processing for monitoring and acknowledgement 2) Receiving card access activity events 3) Receiving digital input events 4) Receiving intrusion zone events

c. Occurrences for “Alarm” and “Reset” conditions for each of the pre�selected Access system alarms will be processed and managed from the NVMS system’s Live View workspace that is reserved for displaying alarm notifications in the alarm list message pane or from the FCWnx alarm viewer. If the Alarm pane is hidden, the alarm can be acknowledged from the Camera display tile.

d. Once an Access system initiated alarm occurrence is acknowledged from the NVMS system, it should be automatically acknowledged and processed in the Access System alarm monitor queue without further operator intervention.

20. The Network Video Management Software (NVMS) shall support integration with Lenel OnGuard and Lenel Facility Commander Wnx.

21. The Network Video Management Software (NVMS) shall support integration with Cardax FT Command Center.

22. The Network Video Management Software (NVMS) shall support integration with RS2. 23. The Network Video Management Software (NVMS) shall support integration with DSX. 24. The Network Video Management Software (NVMS) shall support integration with

Jacques VoIP Voice Communication System. 25. The Network Video Management Software (NVMS) shall support integration with

Stentofon AlphaCom XE. 26. The Network Video Management Software (NVMS) shall support integration with DDS

Amadeus.



27. The Network Video Management Software (NVMS) shall be capable of being upgraded from one version to another without having to uninstall the previous version.

28. The Network Video Management Software (NVMS) shall be capable of being upgraded from Standard edition to Enterprise edition without having to uninstall the application.

29. The Network Video Management Software (NVMS) shall automatically detect if video or audio source firmware is out of date with respect to the current installed software and upgrade it.

30. The Network Video Management Software (NVMS) shall automatically detect if client application software is out of date with respect to the current installed server software and upgrade it.

31. The Network Video Management Software (NVMS) shall run as a service configured to automatically start when the server or workstation is powered on and automatically recover from failure or attempted tampering.

32. The Network Video Management Software (NVMS) shall allow system administration, and live and recorded video and audio monitoring all from a single client application that can be located anywhere on the network.

33. The Network Video Management Software (NVMS) shall automatically discover all Control Center Server instances running on computers connected to the same network as the Control Center Client.

34. The Network Video Management Software (NVMS) shall provide a search functionality to discover Control Center Server instances running on computers connected on a different network segment than the Control Center Client by using IP addresses or hostnames.

35. The Network Video Management Software (NVMS) shall automatically discover video and audio sources that are connected to the same network as the Control Center Server.

36. The Network Video Management Software (NVMS) shall provide a search functionality to discover video and audio sources that are connected on a different network segment than the Control Center Server.

37. The Network Video Management Software (NVMS) shall provide the ability to connect a video or audio source to multiple NVRs to achieve redundant recording.

38. The Network Video Management Software (NVMS) shall provide the ability to create a failover connection for a video or audio source. If the NVR that the video or audio source is connected to goes offline then the failover NVR will take over the connection.

39. The Network Video Management Software (NVMS) shall provide administration of all system connections from a single window.

40. The Network Video Management Software (NVMS) shall support receiving Simple Network Management Protocol (SNMP) messages from servers and alert the user.

41. The Network Video Management Software (NVMS) shall detect if the video or audio signal is lost and alert the system administrator.

42. The Network Video Management Software (NVMS) shall provide the capability to rename all video and audio sources and NVRs.

43. The Network Video Management Software (NVMS) shall record video and audio streams based on a recording schedule that can be defined individually for each video source. The schedule shall be created with the following parameters:

a. Recording Mode

1) Continuous 2) Motion 3) Digital Inputs 4) Alarms 5) POS Transactions 6) License Plates



b. Time and Date Settings

1) Daily 2) Weekly

44. The Network Video Management Software (NVMS) shall provide the ability to manually trigger recording.

45. The Network Video Management Software (NVMS) shall provide a pre�event and post�event recording option.

46. The Network Video Management Software (NVMS) shall provide a reference frame recording option in the absence of events.

47. The Network Video Management Software (NVMS) shall perform motion detection on each individual video source with adjustable sensitivity, threshold and detection zones.

48. The Network Video Management Software (NVMS) shall provide the ability to reduce the image rate of recorded video over time as a means of increasing record time. The image rate shall be able to be reduced to one half or one quarter of the original image rate. This setting can be configured separately for each video source.

49. The Network Video Management Software (NVMS) shall provide the ability to set a maximum recorded video retention time for each video source.

50. The Network Video Management Software (NVMS) shall perform dynamic bandwidth management to ensure that the total bandwidth does not overload the system.

51. The Network Video Management Software (NVMS) shall authenticate users before granting access to the system. Access rights for each user shall be able to be defined individually for each user, and shall and include:

a. Viewing live images

1) Using PTZ controls 2) Locking PTZ controls 3) Trigger manual recording

b. Viewing recorded images

1) Exporting images 2) Backup recorded images

c. Connect and disconnect cameras d. Setup cameras

1) Setup general settings 2) Setup network settings 3) Setup image and display settings 4) Setup compression and image rate 5) Setup image dimension settings 6) Setup motion detection settings 7) Setup privacy zone settings 8) Setup manual recording settings 9) Setup digital input & output settings 10) Setup microphone settings

e. Setup servers

1) Setup general settings 2) Setup schedule settings



3) Setup recording and bandwidth settings 4) Setup user and group settings 5) Setup alarm management settings 6) Setup scheduled backup settings 7) Setup POS transaction settings 8) Setup email settings 9) Setup rule engine settings 10) View system log

f. Access to individual video and audio sources

52. The Network Video Management Software (NVMS) shall provide the ability to import Windows users and use Windows credentials to authenticate users.

53. The Network Video Management Software (NVMS) shall provide the ability to create alarms.

54. The Network Video Management Software (NVMS) shall provide the ability to schedule backups of recorded video with associated events to a local folder or mapped network drive.

55. The Network Video Management Software (NVMS) shall provide the ability to email users and system administrators when an event or system health error occurs.

56. The Network Video Management Software (NVMS) shall maintain an event log for the following events:

a. User Events

1) User(s) login 2) User(s) logout 3) Server setting changed 4) Device setting changed 5) Device connection 6) Device disconnected 7) Digital output triggered 8) Bookmark added 9) Bookmark updated 10) Bookmark deleted 11) PTZ moved 12) PTZ idle 13) Export performed

b. Device Events

1) Connection created 2) Connection removed 3) Connection created to standby server 4) Connection removed from standby server 5) Connection failure 6) Connection restored 7) Network packet loss unacceptable 8) Network packet loss acceptable 9) Motion started 10) Motion ended 11) Recording started 12) Recording ended 13) Recording interrupted 14) Recording resumed 15) Digital input activated



16) Digital input deactivated 17) Firmware upgrade started 18) Firmware upgrade completed 19) Firmware upgrade failed 20) License plate watchlist match

c. Server Events

1) Control Center license expired 2) Control Center license expires soon 3) Control Center Server started 4) Control Center Server shutting down 5) Control Center Server terminated unexpectedly 6) Database error 7) Data initialization error 8) Data volume failed 9) Data volume recovered 10) Data volume size reduced 11) Data write error 12) Data upgrade started 13) Data upgrade completed 14) Data upgrade failed 15) Data recovery started 16) Data recovery completed 17) Data recovery failed 18) Network connection found 19) Network connection lost 20) Network error 21) Network error resolved 22) Email send error 23) Server hardware error 24) Backup started 25) Backup completed 26) Backup failed

57. The Network Video Management Software (NVMS) shall have the capability to execute any of the following actions in response to any of the events listed above:

a. User Notification Actions

1) Display on�screen message 2) Send an email 3) Play a sound

b. Monitoring Actions

1) Start live streaming video

c. Device Actions

1) Reboot camera 2) Trigger digital output

d. PTZ Actions

1) Go to preset



2) Run a pattern 3) Set auxiliary 4) Clear auxiliary

e. Alarm actions

1) Trigger an alarm 2) Acknowledge an alarm

58. The Network Video Management Software (NVMS) shall provide a maintenance log and audit trail of all system errors and events.

59. The Network Video Management Software (NVMS) shall provide the ability receive transaction information from point�of�sale sources.

60. The Network Video Management Software (NVMS) shall provide the ability to generate events based on point�of�sale transaction exceptions.

61. The Network Video Management Software (NVMS) shall provide the ability to define a region of an image where license plate detection is performed. Detected license plates shall be stored along with the video data.

62. The Network Video Management Software (NVMS) shall provide the ability to create a watchlist that will be used to create events when any license plate on the watchlist is detected in the images being analyzed.

63. The Network Video Management Software (NVMS) shall provide the ability to enable and configure PTZ control on the RS�485 interface of a video source.

64. The Network Video Management Software (NVMS) shall support the following list of PTZ camera protocols:

a. American Dynamics Sensormatic b. AXSYS c. Ernitec d. Honeywell Diamond e. Kalatel ASCII f. Pelco D g. Pelco P h. Videotec

65. The Network Video Management Software (NVMS) shall provide the ability to change the network settings for a video and audio source.

66. The Network Video Management Software (NVMS) shall provide the ability to change image quality and image rate parameters for a video source without affecting the settings on the other video sources.

67. The Network Video Management Software (NVMS) shall provide the ability to enable a secondary stream for live viewing.

68. The Network Video Management Software (NVMS) shall provide the ability to change the exposure, iris, IR filter, backlight compensation, gain, priority, sharpening, saturation, focus, and white balance settings for a video source.

69. The Network Video Management Software (NVMS) shall provide the ability to change the image dimensions for a video source.

70. The Network Video Management Software (NVMS) shall provide the ability to add privacy zones to a video source to block unwanted areas in the image field of view.

71. The Network Video Management Software (NVMS) shall provide the ability to set a maximum recording duration for manually triggered recording for a video source.

72. The Network Video Management Software (NVMS) shall provide the ability to change the input and gain for an audio source.

73. The Network Video Management Software (NVMS) shall provide the ability to link any audio source to any video source.



74. The Network Video Management Software (NVMS) shall provide the ability to set a limit on the maximum bandwidth transmitted to the Control Center Client application from the Control Center Server application.

75. The Network Video Management Software (NVMS) shall provide the ability to automatically log in to an NVR.

76. The Network Video Management Software (NVMS) shall provide the ability to automatically log out of an NVR when the application is left idle.

77. The Network Video Management Software (NVMS) shall provide the ability to save and restore the window layout.

78. The Network Video Management Software (NVMS) shall provide the ability to control the system using a PC keyboard or joystick.

79. The Network Video Management Software (NVMS) shall provide the ability to import and export client settings such as maps, views, and web pages.

80. The Network Video Management Software (NVMS) shall support live or recorded video monitoring of 1 to 36 video streams simultaneously on a single monitor with the following possible layouts.

a. Full Screen b. 2 x 2 c. 3 x 3 d. 4 x 4 e. 5 x 5 f. 6 x 6 g. 1 + 5 h. 1 + 7 i. 1+ 12 j. 2 + 8

81. The Network Video Management Software (NVMS) shall support the ability to bias the displayed video to a higher frame rate or to a lower image resolution if the client network bandwidth or client processing power is insufficient to display the full frame rate and image resolution.

82. The Network Video Management Software (NVMS) shall support the ability to display the following list of image overlays:

a. Camera Name b. Camera Location c. Timestamp d. Record Indicator e. PTZ Controls f. Motion Activity g. License Plate

83. The Network Video Management Software (NVMS) shall support an unlimited number of monitors for monitoring video and audio streams.

84. The Network Video Management Software (NVMS) shall support monitoring live and recorded video and audio streams simultaneously on the same monitor.

85. The Network Video Management Software (NVMS) shall support viewing the same live or recorded video stream at different zoom levels.

86. The Network Video Management Software (NVMS) shall support the creation of unlimited views with unique layouts of video streams.

87. The Network Video Management Software (NVMS) shall support the ability to full�screen a view.

88. The Network Video Management Software (NVMS) shall support the ability to save views.



89. The Network Video Management Software (NVMS) shall support the ability to cycle through views (guard tour) based on a specified interval.

90. The Network Video Management Software (NVMS) shall display all video sources connected to the system.

91. The Network Video Management Software (NVMS) shall support the ability to drag and drop a video source from a tree of video sources into a window for live or recorded video and audio monitoring.

92. The Network Video Management Software (NVMS) shall support the ability to drag and drop a view from a tree of views into a window for live or recorded video and audio monitoring.

93. The Network Video Management Software (NVMS) shall support the ability to configure how the tree of video sources and views is displayed.

94. The Network Video Management Software (NVMS) shall support the ability to designate one or more regions in a window for displaying video directly linked to triggered alarms and rules.

95. The Network Video Management Software (NVMS) shall support the ability to acknowledge alarms from the designated video display area.

96. The Network Video Management Software (NVMS) shall support the ability to manually trigger digital output.

97. The Network Video Management Software (NVMS) shall support the ability to create a map that represents the physical location of cameras and other devices throughout the surveillance system. Maps shall be created from images stored in JPEG, BMP, PNG, or GIF image formats. Maps shall have the ability to contain links so as to create a hierarchy of interlinked maps.

98. The Network Video Management Software (NVMS) shall support the ability to create a map that has a link to a section of the entire image region.

99. The Network Video Management Software (NVMS) shall support the ability to drag and drop a video source from a map into a window for live or recorded video and audio monitoring.

100. The Network Video Management Software (NVMS) shall highlight a camera on a map when an alarm linked to the camera is triggered.

101. The Network Video Management Software (NVMS) shall support the ability to save a link to a web page and view the web page in a window.

102. The Network Video Management Software (NVMS) shall support digital zooming and panning on live and recorded video streams.

103. The Network Video Management Software (NVMS) shall support controlling mechanical pan�tilt�zoom, iris, and focus as well as setting presets and patterns.

104. The Network Video Management Software (NVMS) shall support controlling mechanical pan�tilt�zoom camera on�screen display and auxiliary controls.

105. The Network Video Management Software (NVMS) shall support locking PTZ controls. 106. The Network Video Management Software (NVMS) shall support control of a

mechanical pan�tilt�zoom camera with a USB joystick. 107. The Network Video Management Software (NVMS) shall support forward and reverse

playback of recorded video and audio at variable speeds. 108. The Network Video Management Software (NVMS) shall synchronously playback

recorded video and audio from selected video sources. 109. The Network Video Management Software (NVMS) shall support navigation of recorded

video and audio via calendar, timeline, or events. 110. The Network Video Management Software (NVMS) shall support a timeline that

displays all connected video sources and the corresponding motion and recording events.

111. The Network Video Management Software (NVMS) shall support a timeline that can display the entire time range down to one second of recorded video and audio.



112. The Network Video Management Software (NVMS) shall support creating bookmarks for recorded video and audio, displaying the bookmarks on the timeline, and searching for bookmarks.

113. The Network Video Management Software (NVMS) shall support protecting a bookmark so the video and audio data is never overwritten.

114. The Network Video Management Software (NVMS) shall support monitoring alarms. 115. The Network Video Management Software (NVMS) shall support the ability to assign

alarms to users. 116. The Network Video Management Software (NVMS) shall support the ability to

acknowledge alarms. 117. The Network Video Management Software (NVMS) shall support searching through

recorded video and audio based on various search criteria including time, date, video source, and events.

118. The Network Video Management Software (NVMS) shall support searching through recorded video based on motion in user defined areas (pixel search).

119. The Network Video Management Software (NVMS) shall support searching through recorded video based on time, date, video source, and image region and have the results displayed as series of thumbnail images.

120. The Network Video Management Software (NVMS) shall support searching through recorded video based on alarm events.

121. The Network Video Management Software (NVMS) shall support searching through recorded video based on point�of�sale transaction events.

122. The Network Video Management Software (NVMS) shall support searching through recorded video based on license plates detected in the images of the video source.

123. The Network Video Management Software (NVMS) shall support the ability to export recorded video in the following formats:

a. Native b. JPEG c. PNG d. TIFF e. AVI f. WAV g. PDF h. Print

124. The Network Video Management Software (NVMS) shall support the ability to export recorded audio in WAV format.

125. The Network Video Management Software (NVMS) shall support the ability to snapshot a live or recorded image and export it from the system.

126. The Network Video Management Software (NVMS) shall support the ability to export a live stream of images in the following formats:

a. JPEG b. PNG c. TIFF

127. The Network Video Management Software (NVMS) shall support the ability to export video from multiple camera streams in Native format.

128. The Network Video Management Software (NVMS) shall support reviewing video and audio that was exported in the Native format.

129. The Network Video Management Software (NVMS) shall support authenticating video that was exported in the Native format to validate that it was not tampered with.

130. The Network Video Management Software (NVMS) shall support converting video that was exported in the Native format to an industry standard format.



131. The Network Video Management Software (NVMS) shall support reviewing video and audio stored in a backup.

2.6 VIDEO CAMERA MOUNTS

A. Security contractor shall furnish and install all interior and exterior CCTV camera mounts and mounting hardware as needed. All mounts shall be bolted or clamped (not welded) in place to allow for relocation. Pendant mounts shall be suitable for use as wall, ceiling, column and parapet. Pendant mounts shall attach to the camera housing with section of standard 1.5�inch threaded pipe. Fixed camera mounts shall be universal wall�ceiling mounts with adjustable mount head. Installation and mounting shall be in strict accordance with requirements for applicable seismic classification. The Wall Mount may be mounted to a standard outlet box, which allows convenient, concealed cable routing to the mount. The body of the mount is hollow allowing wiring to be concealed as it is run from the wall to the camera. It is intended for indoor use.

B. 110 volt supply on light poles and NEMA enclosure to be provided by others to mounted at a height of 16 feet. Multimode fiber if needed to be provided by others. Ethernet to fiber converters if needed to be provided by security contractor. Provide as per drawings.

2.7 INSTALLATION OF CCTV

A. Examine areas and conditions under which CCTV systems are to be installed, and notify Architect/Engineer in writing of conditions detrimental to proper completion of the work. Do not proceed with the work until unsatisfactory conditions have been corrected in a manner acceptable to Installer.

B. Install CCTV systems including components where indicated, in accordance with equipment manufacturer's written instructions, in compliance with National Electrical Code, and with recognized industry practices, to ensure that CCTV system complies with requirements and serves intended purposes.

C. Use extreme care in handling, fishing and pulling�in electronic coaxial cable to avoid damage to cable and shielding. Avoid excessive and sharp bends.

D. Install CCTV equipment properly to avoid causing mechanical stresses, twisting or misalignment of equipment being exerted by clamps, supports, and cabling.

E. Tighten connectors and terminals, including screws and bolts, in accordance with equipment manufacturer's published torque tightening values for equipment connectors. Where manufacturer's torquing requirements are not indicated, tighten connectors and terminals to comply with tightening torques specified in UL Standards 486A and B, and the National Electrical Code.

F. Provide equipment�grounding connections for CCTV systems as indicated. Tighten connections to comply with tightening torques specified in UL Standard 486A to assure permanent and effective grounds. Provide grounding conductors for antennas and antenna supporting structures without splices or connections in the conductor.

G. Set field�adjustable CCTV system components for input voltages, current settings and frequency settings.



H. Touch�up scratched and marred surfaces to match original finishes; remove dirt and construction debris.

I. The Network Video Management Software, NVR Hardware and related components shall be installed and commissioned by authorized integrators certified by the manufacturer.

2.8 NETWORK VIDEO RECORDER

A. Motion Detection: provide motion detection to analyze the motion content of all camera inputs, ensuring that cameras with motion present become priority for recording.

B. Network Digital Video Sever 15 TB of internal storage, Dual Gigabit Ethernet Connection, Raid 5 Storage, 2 GB memory minimum. The server shall have Hot�Swappable Hard Drives, redundant power supplies, Remote Configuration and Upgrade, Tamper�resistant Data Storage, Progressive lossless Recording. The NVR shall support Expansion Storage units HD�NVR�EXP�WREXP� xx.xTB as needed. See storage requirements to determine if additional storage is needed.

C. Back up Power � Provide Rack mount � MIDATLPRO�UPS2200R8IP � 2150VA/1650W UPS web enabled 9' cord, NEMA 5�20P plug or equal

D. Licensing: 3 years for all system software, client software and camera licensing. Provide client licenses for workstations as per drawings.

2.9 Rack MIDDLE ATLANTIC MRK�4436�NVR CONFIGURED NVR RACK, 44UD, 36D model number 358796 or equal

A. Power provided by others – 20 amp 110 VAC required

B. Provide 19” Rack system including the following components. Provide sides.

1. 231128 � PD�915R � 115 Volt rack mount 9� outlet power strip 2. 231190 � EB4 econo�blank flanged 4 RMU black power coat finish 7.00" 3. 231183 � EB2 2RU black 4. 231178 � EB1 panels in ploy bags 5. 369897� RM�KB�LCD17X8KV �17" rack�mount LCD screen monitor, keyboard with

mouse.

2.10 WORK STATION MONITOR

A. Network drop provided by others

B. Provide as per drawings. Avigilon 24” commercial grade CCTV monitor model (M2300) or equal

1. Monitor 2. 24", 3. LCD, 4. 2.3 Megapixel 5. 16:10 Widescreen Aspect Ratio



2.11 DEMOSTRATION

A. Train Owner's operating personnel in the operation of the system. Provide a minimum of 2 hours of training.

B. Schedule training with advance notice of at least 7 days

2.12 NETWORK BACKBONE (BETWEEN BUILDINGS)

A. Contractor shall provide a fiber based network connection between buildings

B. Conduit provided by others

C. Network connection shall be 1 Gigabit from the security network switch to switch

2.13 CAMERAS

A. Conduit provided by others

B. Avigilon Model number 1.0�H3�D1 � 1.0 Megapixel HD H264,3�9mm lens, f/1.2 or equal as per drawings

C. Avigilon Model number 2.0�H3�B1 � 2.0 Megapixel HD H264,4.7�84.6mm lens f/1.2 or equal as per drawings

D. Avigilon model number 5.0�H3�DP1 � 5.0 Megapixel Day/Night Pendant Dome, 3�9mm f/1.2 P�iris lens or equal as per drawings

E. Avigilon model number 29MO�HD�PRO�C 29.0 Megapixel Day/Night Professional series camera with Canon, 35mm, f/1.4, Auto�Iris model number LEF3514CA or equal as per drawings

2.14 CCTV WORK STATION

A. Contractor shall furnish and install CCTV workstation(s) as per drawings

B. Avigilon Control Center Professional high performance remote monitoring workstation for up to two monitors model number 2MN�HD�RMWS – or equal

1. Control Center Edition Enterprise, Standard or Core compatible 2. Viewing streams up to 144 3. Viewing rate up to 10 MB/s 4. Operating system Microsoft Windows 7 Professional 64�bit 5. Processor Intel Xeon Processor E3�1220v2 6. Memory 4 GB Ram 7. Network Interface 1 Gigabit Ethernet RJ�45 port (1000Base�T) 8. Video Outputs 2 active (1 DisplayPort and 1 DVI) 9. Optical Drive 1 DVD�RW

C. Location to be determined by Owner



2.15 CCTV VIDEO SWITCH

A. Contractor shall furnish and install UTC/Interlogix/GE Security (a Division of UTC Fire & Security) model #GE�DSSG�244�PoE Managed Switches or approved equal as needed to support all CCTV cameras shown on project drawing.

B. Installation Location � as per drawings

2.16 SURGE AND TAMPER PROTECTION

A. Surge Protection: Protect components from voltage surges originating external to equipment housing and entering through power, communication, signal, control, or sensing leads. Include surge protection for external wiring of each conductor�entry connection to components. DITEK�12POE or equal

1. Minimum Protection for Power Connections 120 V and More: Auxiliary panel suppressors complying with requirements in Division 16 Section "Transient Voltage Suppression."

2. Minimum Protection for Communication, Signal, Control, and Low�Voltage Power Connections: Comply with requirements in Division 16 Section "Transient Voltage Suppression" as recommended by manufacturer for type of line being protected.

B. Tamper Protection: Tamper switches on enclosures, control units, pull boxes, junction boxes, cabinets, and other system components shall initiate a tamper�alarm signal when unit is opened or partially disassembled. Control�station control�unit alarm display shall identify tamper alarms and indicate locations.

PART 3 � EXECUTION

3.1 SECURITY CONTRACTOR

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

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

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

D. 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 Facility Commander Wnx and Avigilon 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 CONTRACTOR shall be advised of designated service and support personnel responsible for warranty service.

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

3.4 EXAMINATION

A. Examine pathway elements intended for cables. Check raceways, cable trays, and other elements for compliance with space allocations, installation tolerances, hazards to cable installation, and other conditions affecting installation.

B. Examine roughing�in for LAN and control cable conduit systems to PCs, controllers, card readers, and other cable�connected devices to verify actual locations of conduit and back boxes before device installation.

C. Proceed with installation only after unsatisfactory conditions have been corrected.

3.5 PREPARATION

A. Comply with recommendations in SIA CP�01.

B. Comply with TIA/EIA 606�A, "Administration Standard for Commercial Telecommunications Infrastructure."

C. In meetings with the CONTRACTOR, present Project planning documents and review, adjust, and prepare final setup documents. Use final documents to set up system software.

3.6 INSTALLATION

A. Comply with NECA 1, "Good Workmanship in Electrical Construction."

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

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



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

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

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

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

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

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

J. 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.7 GROUNDING

A. Comply with Division 26 Section "Grounding and Bonding."

B. Comply with IEEE 1100, "Recommended Practice for Power and Grounding Electronic Equipment."

C. Ground cable shields, drain conductors, and equipment to eliminate shock hazard and to minimize ground loops, common�mode returns, noise pickup, cross talk, and other impairments.

D. Bond shields and drain conductors to ground at only one point in each circuit.

E. Signal Ground:

1. Terminal: Locate in each equipment room and wiring closet; isolate from power system and equipment grounding.

2. Bus: Mount on wall of main equipment room with standoff insulators. 3. Backbone Cable: Extend from signal ground bus to signal ground terminal in each

equipment room and wiring closet.

3.8 IDENTIFICATION

A. In addition to requirements in this article, comply with applicable requirements in Division 16 Section "Electrical Identification" and with TIA/EIA 606�A.



B. Using software, develop cable administration drawings for system identification, testing, and management. Use unique, alphanumeric designation for each cable, and label cable and jacks, connectors, and terminals to which it connects with the same designation. Use logical and systematic designations for facility's architectural arrangement.

C. Label each terminal strip and screw terminal in each cabinet, rack, or panel.

1. 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 shown.

2. Each wire connected to building�mounted devices is not required to be numbered at the device if the color of the wire is consistent with the associated wire connected and numbered within the panel or cabinet.

D. At completion, cable and asset management software and drawings shall reflect as�built conditions.

3.9 FIELD QUALITY CONTROL

A. Perform tests and inspections.

1. Manufacturer's Field Service: Engage a factory�authorized service representative to inspect components, assemblies, and equipment installations, including connections, and to assist in testing.

2. Correct all deficiencies found in testing and retest.

3.10 CLEANING

A. Clean factory finished surfaces. Repair any marred or scratched surfaces with manufacturer's touch up paint.

3.11 COMMISSIONING AND TRAINING

A. The SECURITY CONTRATOR is required to place entire system into full and proper operation as designed and specified.

B. Verify that all hardware components are properly installed, connected, communicating, and operating correctly.

C. Verify that all system software is installed, configured, and complies with specified functional requirements.

D. The SECURITY CONTRACTOR shall perform final acceptance testing executing a point by point inspection that demonstrates compliance with system requirements as designed and specified:

E. Conduct final acceptance tests verifying that each device point and sequence is operating correctly and properly reporting back to control panel and control center.



F. The system shall not be considered accepted until all acceptance test items have been successfully checked�off. All access control power supplies, panel(s) and door sub component sets shall be labeled with a unique barcode identifier used to log the inspection/checkout and stored in the web based software system Building Reports.com and provide a report to the OWNER.

G. The SECURITY CONTRACTOR shall provide system operations, administration, and maintenance training by factory trained personnel qualified to instruct:

H. OWNER will designate personnel to be trained.

I. Provide printed materials for each trainee including product manuals.

J. Provide hands�on training with operational equipment.

K. Training shall be oriented to the specific system being installed under this contract as designed and specified.

END OF SECTION 281300

state of west virginia new state office building fairmont ... state office... · conditions and...

Documents