security camera upgrade project rfp 418-16 00900-1 · security camera upgrade project rfp 418 ......

Security Camera Upgrade Project RFP 418-16 00900-1 J&A Engineering

SECTION 00900 ADDENDUM

ADDENDUM NO. 4, dated June 20, 2016 RE: Security Camera Upgrade Project 418-16

FROM: OWNER: FULTON COUNTY BOARD OF EDUCATION

CAPITAL PROGRAM CONTRACTS Sandy Springs, GA 30339 TO: ALL PROSPECTIVE OFFERORS: This Addendum forms a part of the Contract Documents and modifies the Proposal Documents as noted below. Acknowledge receipt of the Addendum in the space provided on Document 00400 - Proposal Acceptance Form. Failure to do so may result in the proposal being deemed non-responsive. The Addendum consists of 2 written page and the documents cited below. A. CHANGES TO PROPOSAL REQUIREMENTS TABLE OF CONTENTS: None B. CHANGES TO PRIOR ADDENDUM: None C. CHANGES TO PROPOSAL DOCUMENTS:

1. Replace Document 00400 with revised Document 00400 (dated 6-20-16) D. CHANGES TO CONDITIONS OF THE CONTRACT: None E. CHANGES TO SPECIFICATIONS:

1. Revised Section 28 30 00 – Access Control System (North Transportation Facility) dated 6.20.16 F. CHANGES TO DRAWINGS: None G. OTHER CHANGES AS SET FORTH:

1. Question: Where are the revised specifications for Section 28 30 00 - Access Control System (North

Transportation Facility) dated 6.10.16? They are referenced but not included in Addendum 3. Answer: This section was accidently not included in the previous addendum, but it has been included in this addendum.

2. Question: Where should the price for Add Alternate #1 for the North Transportation Facility be

entered on the bid form?

Answer: Please see the revised Document 00400 issued as part of this addendum.

3. Question: Please provide model number for camera CS-5 for North Transportation Facility. CS-5 is not listed on camera schedule.

Security Camera Upgrade Project RFP 418-16 00900-1 J&A Engineering

Answer: Please reference Drawing LV-101 for all exterior camera locations. Cameras CS-3 and CS-5 were deleted from LV-101 by ADDENDUM #3. However, J&A Engineering did not delete the cameras from Drawing LV-201. This was an error and the cameras should also be deleted from Drawing LV-201.

4. Question: Please double check interior camera model numbers and types for North Transportation

Facility. Many of the cameras appear to be the wrong type of camera for the environment they are to be mounted in. All interior cameras listed on camera schedule, shown on drawing LV-201, are in-ceiling cameras. However, the drawings show some areas do not have ceilings and are “Open to structure”. Answer: The BUS MAINTENANCE SHOP portion of the building does not have a ceiling and is open to structure. Please provide the following Avigilon camera models with associated mounting hardware for these locations: C-13 3.0C-H4A-DP1 – Short pendant needed C-14 Remains a ceiling mount C-15 3.0C-H4A-BO1 C-16 3.0C-H4A-DP1 – Short Pendant needed C-17 2.0C-H4A-BO1 C-18 Remains the same model but will need to be wall mounted C-19 2.0C-H4A-BO1 C-20 2.0C-H4A-BO1 C-21 Remains the same model but will need to be wall mounted C-22 2.0C-H4A-BO1 C-23 2.0C-H4A-BO1 C-24 2.0C-H4A-D01 C-25 2.0C-H4A-D01 C-26 2.0C-H4A-D01

Clarification or any other notice of a change in the Solicitation Documents will be issued only by the OWNER Contracts Department and only in the form of a written Amendment. Any other purported Amendments are void and unenforceable.

END OF ADDENDUM NO. 4

ADDENDUM #4 (6-20-16) DOCUMENT 00400

OFFER ACCEPTANCE FORM

Offeror Name: ______________________________

1.01 PROPOSAL SUBMISSION INSTRUCTIONS

Submit this form, in a sealed envelope, plainly showing Offeror’s business license name and number, description of the Work and the proposal submission date; and deposit with Fulton County Schools Capital Program Contracts located at 6201 Powers Ferry Road, Atlanta, Georgia 30339. A. Offerors shall keep the Proposal Acceptance Form intact and return all pages when submitting the

PROPOSAL.

B. Failure to submit the complete Proposal Acceptance Form may invalidate the PROPOSAL. 1.02 PROPOSAL DUE DATE: 2:30 p.m. on Thursday, June 23, 2016 1.03 PROJECT IDENTIFICATION:

A. The undersigned is familiar with the terms of the Contract, the local conditions affecting performance of Contract, the cost of the Work at the place where the Work is to be done, and with the Drawings, Specifications and all other PROPOSAL Documents. The undersigned hereby proposes and agrees to perform, within the Contract Time stipulated, the Work including all of its component parts; and to provide and furnish any and all of the labor, materials, tools, apparatus, facilities, expendable equipment, and all utility and transportation services necessary to perform the Work in accordance with the Contract and complete all Work in a workmanlike manner for:

Security Camera Upgrade Project - RFP 418-16

In strict conformity with the Drawings and Specifications issued by: ARCHITECT for Fulton County Schools, Georgia

1.04 Offeror acknowledges receipt of the following Addendum:

Number Number Number Number Number Number Number Number Number Number Number Number ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______

1.05 BASE OFFER (MUST BE FULLY COMPLETED BY OFFEROR)

A. Offeror will complete the Work in accordance with the Contract Documents for the following base OFFER amount which includes all allowances (including both specified and unit cost allowances):

B. The base OFFER amount shall include ALL applicable State Sales and Use Taxes and shall exclude

Federal Excise Taxes as set forth in Article 6.37 of the General Conditions.

C. The base OFFER amount shall include ALL Contract Allowances.

FAILURE TO SUBMIT THIS FORM OR ANY MODIFICATION(S) TO THIS FORM MAY RENDER THE PROPOSAL NON-RESPONSIVE

D. Allowances

1. Specified Allowances:

a. Include the lump sum amount of $60,000 to cover unforeseen code changes by a Government Agency or local city municipality.

1. Centennial HS Subtotal Specified Allowance (Code Changes): $10,000

2. Langston Hughes HS Subtotal Specified Allowance (Code Changes): $10,000

3. North Fulton Transportation Facility Subtotal Specified Allowance (Code Changes): $10,000

4. Renaissance MS Subtotal Specified Allowance (Code Changes): $10,000

5. Tri-Cities HS Subtotal Specified Allowance (Code Changes): $10,000

Total Specified Allowance: $50,000

2. Unit Cost Allowances: None.

E. BASE OFFER

The Offeror proposes to fully and completely construct the Project in conformity with all requirements of the Contract Documents and furnish all necessary labor, material and equipment for such construction, and furthermore, to fully, completely, and strictly perform all obligations of the Contractor as set forth in the Contract Documents, for the lump sum contract price of: SUB-TOTAL BASE OFFER AMOUNT Centennial HS (in words):

___________________________________________________________________________

SUB-TOTAL BASE OFFER AMOUNT Centennial HS (figures):

$________________________________________________


SUB-TOTAL BASE OFFER AMOUNT Langston Hughes HS (in words):

SUB-TOTAL BASE OFFER AMOUNT Langston Hughes HS (figures):

$_________________________________________

SUB-TOTAL BASE OFFER AMOUNT North Fulton Transportation Facility (in words):

___________________________________________________________________________

SUB-TOTAL BASE OFFER AMOUNT North Fulton Transportation Facility (figures):

$_________________________________________

SUB-TOTAL BASE OFFER AMOUNT Renaissance MS (in words):

___________________________________________________________________________

SUB-TOTAL BASE OFFER AMOUNT Renaissance MS (figures):

$_________________________________________

SUB-TOTAL BASE OFFER AMOUNT Tri-Cities HS (in words):

___________________________________________________________________________


SUB-TOTAL BASE OFFER AMOUNT Tri-Cities HS (figures):

$_________________________________________

TOTAL BASE OFFER AMOUNT (in words):

___________________________________________________________________________

TOTAL BASE OFFER AMOUNT (in figures): $___________________________________

(Note: Total Base Offer Amount shall include ALL Allowances listed in item D above).

E. Alternates: North Transportation Facility 1. Add Alternate #1: For doors #02, #03, and #06, provide pricing to supply and install electrified door hardware, card reader, door status switch, connect REX signal from door hardware, all low voltage cable, programming and connection to the new Avigilon Card Access System. Note that doors, door frames and walls shall be provided and installed by Owner. See sheet LV-201 (Security and Access Control Systems, North Fulton Transportation Facility). Add: ____________________________________ $_______________________________ (Use words) (Figures)

1.06 NOT USED

1.07 BASIS OF AWARD OF CONTRACT:

A. The best value responsive and responsible OFFER shall be determined by the best value OFFER amount including the allowances, unit costs, and any selected alternates for the base OFFER.

B. OWNER RESERVES THE RIGHT TO REJECT ANY AND ALL PROPOSALS.

Article 1 - Scope of Work The CONTRACTOR shall perform, within the time stipulated in the Contract Documents, all of which are incorporated herein and shall provide all labor, materials, equipment, tools, utility services, transportation and everything else necessary to complete in a workmanlike manner, and in exact compliance with the terms of the Contract Documents, all of the Work required in connection with the following titled Project:


Security Camera Upgrade Project – RFP 418-16

_______________________________________________________________________________________ [Proposal Number/Project Number(s) – to be filled in by Capital Program Contracts]

Article 2 - Time for Completion The Work shall be commenced on the date stated in the OWNER Notice to Proceed. The time period for Substantial Completion of the Work shall be set forth in the Notice to Proceed issued by the OWNER and 01010 Exhibit A Milestone Schedule document. TIME IS OF THE ESSENCE.

Article 3 - Hold Harmless, Defense and Indemnification

The CONTRACTOR, even if it is without fault itself, shall indemnify, defend and hold harmless the OWNER, the Board and its and their respective officers, employees, program administrators, representatives, agents and consultants, from every liability, claim, loss, cause of action, action, demand, penalty, cost, expense (including without limitation, attorneys’ fees) related to or arising from:

1. Any injury to person or property sustained by the CONTRACTOR or by any person, firm, or

corporation, employed directly or indirectly by it upon or in connection with the Work;

2. Any injury to person or property sustained by any person, firm, or corporation, caused by any act, neglect, default, or omission of the CONTRACTOR or any person, firm, or corporation, directly or indirectly employed by it upon or in connection with the Work, whether the injury or damage occurs upon or adjacent to the Work;

3. The furnishing or use of any copyrighted or uncopyrighted composition, secret process, patented or unpatented invention, article, or appliance under the Contract Documents; and

4. As otherwise provided in the Contract Documents. The CONTRACTOR at its own cost, expense, and risk, shall defend all legal proceedings that may be brought against all such potential indemnities for any such liability, claim, loss, cause of action, action, demand, penalty, cost and expense, and satisfy any resulting judgment that may be rendered against any of them whether or not the liability, claim, loss, cause of action, action, demand, penalty, cost and expense (including without limitation, attorneys’ fees) was actually or allegedly caused wholly or in part through the negligence or other tortious conduct of any of them. OWNER shall have the right to approve counsel proposed for any such defense and shall be consulted with regard to any proposed settlement. This Article 3 is not meant to require the CONTRACTOR to defend, indemnify or hold harmless the potential indemnities from their own active negligence.

Article 4 - Insurance

CONTRACTOR will provide its own insurance coverage as to all types of insurance relevant to the Project in amounts of coverage and by carriers approved by the OWNER.

Article 5 - Bonding

If the amount of original award of the Contract exceeds FIFTY THOUSAND DOLLARS ($50,000.00), the CONTRACTOR shall furnish to the OWNER a Payment Bond (Material and Labor). CONTRACTOR shall also provide a Performance Bond. Both Bonds shall be for 100% of the Contract Amount and contain the terms and conditions required by Articles 5.10 and 5.11 of the General Conditions.

Article 6 - Provisions Required by Law Deemed Inserted

Each and every provision of law and clause required by law to be inserted in the Contract Documents shall be deemed to be inserted and the Contract Documents shall be read and enforced as though it were included in the Contract Documents. If through mistake or otherwise any such provision is not inserted, or is not correctly inserted, upon


application of either party the Contract Documents shall forthwith be physically amended to make such insertion or correction. PROPOSAL DATE: _________________________________________, 20_________

By:___________________________________________________________________ (Firm Name as it appears on Business License) ______________________________________________________________________ (Signature of authorized person to sign Proposal) ______________________________________________________________________ (Print Name of authorized person to sign Proposal) Business Address: _____________________________________________________________________ ______________________________________________________________________ Phone No.______________________________________________________________

Fax No.________________________________________________________________ Federal Tax ID: _________________________________________________________ Email Address: _________________________________________________________

1.08 ACCEPTANCE

This Agreement is made and entered into on the date set forth on Page 4 of this Agreement, by and between the Fulton County Board of Education, by and through its Board of Education (hereinafter the “OWNER”), and

_________________________________________________________________________________________________

{Name as it appears on Contractor's Business License – to be filled in by OWNER /Capital Program Contracts}

______________________________________________________________________________________________ {sole ownership, partnership, corporation, joint venture, or other}

This Agreement is for the purpose of constructing that Project identified as

Security Camera Upgrade Project – RFP 418-16 CONTRACTOR is the lowest responsive and responsible Offeror in response to a Request for Proposal issued by the OWNER and represents that it is qualified to perform all of the terms, covenants, promises and conditions of this Contract.

Article 7 - Contract Amount

The OWNER shall pay, and the CONTRACTOR shall accept, in full payment for performance as required by the Contract Documents, the sum of _____________________________________________________________________________

(To be filled in by OWNER / Capital Program Contracts)


($___________________), subject to any additions or deductions, if any, as provided in the Contract Documents. It is understood and agreed that all applicable taxes are included in the Contract Amount and that the Federal Excise Tax, from which the OWNER is exempt, is not included. The OWNER, upon request, will furnish the CONTRACTOR such Tax Exemption Certificates as may be required by the Manufacturer or Dealer. All of the above-named Contract Documents are intended to be complementary. Work required by one of the above-named Contract Documents and not by others shall be done as if required by all.

Executed on ________________________________________, 20_____ in Atlanta, Georgia.

FULTON COUNTY BOARD OF EDUCATION By_______________________________________ Superintendent

BLUE INK SIGNATURE REQUESTED FAILURE TO SUBMIT THIS FORM OR ANY MODIFICATION(S) TO THIS FORM

MAY RENDER THE PROPOSAL NON-RESPONSIVE

END OF DOCUMENT


Fulton County Schools: North Transportation Facility April 8, 2016 28 3000 - 1 J&A Engineering ADDENDUM #4 06/20/2016

SECTION 28 3000

ACCESS CONTROL SYSTEM

PART 1 - GENERAL

1.1 RELATED DOCUMENTS

A. Contract drawings, specifications, and general provisions of the Contract, including General and Supplementary Conditions, apply to this section.

1.2 SUMMARY

A. This section of the specifications requires the complete installation of the Card Access Control System (ACS), herein referred to as the ACS System. The ACS System shall be a distributed system, based upon the standard products of ACS System manufacturers, installed within Fulton County Schools and using conventional LAN network communication for information distribution.

B. Fulton County has standardized on Avigilon Access Control and currently has an enterprise level Avigilon Card Access System at the new Headquarters Buildings (Administration and Learning Center). The Security Contractor shall ensure that the North Transportation Facility card access system shall be connected to the existing enterprise level Aviglon Card Access Control and Security Management System at the new Fulton County Headquarters Buildings via wide area network connections provided by Fulton County Schools. Coordination with Fulton County School IT Support shall be required.

C. At the North Transportation Facility, the Avigilon ACS shall be installed at doors as noted in

the Construction Documents. At doors equipped with access control, the supply and installation of new electrified door hardware shall be required. This work shall be part of the Security Contractor’s scope of work.

D. At Centennial High School, Langston Hughes High School and Renaissance Middle School,

there will be no card access equipment required or installed. These schools will not receive ACS at this time.

1.1 ACCEPTABLE MANUFACTURERS

A. No substitutions shall be allowed. The equipment and systems conforming to this section of the specifications manufactured by the following companies is acceptable: 1. Avigilon Access Control System


B. Contractor must be an Enterprise Level Certified Dealer of the access control system manufacturer in order to qualify for this project.

1.2 QUALITY ASSURANCE

A. Industry Referenced Standards. The following specifications and standards are incorporated into and become a part of this Specification by reference. 1. FCC compliance 2. UL compliance 3. NEC compliance

1.3 SUBMITALS

A. Product Data: Submit manufacturer’s technical product data, including specifications and installation instructions, for each type of system equipment. Include drawings, which contain complete wiring and schematic diagrams and other details required to demonstrate that the system has been coordinated, and will function properly as a system. Drawings shall include floor plan layouts of devices, components, vertical riser diagrams, equipment rack details, elevation drawings of equipment racks, sizes and types of all cables and conduits.

B. Test Plan: Contractor shall submit a test plan which defines the tests required to ensure that the system meets technical, operational, and performance specifications, 15 days prior to the proposed test date. Owner/User must approve the test plan before the start of any testing. The test plan shall identify the capabilities and functions to be tested, and include detailed instructions for the setup and execution of each test and procedure for evaluation and documentation of the results.

C. Manufacturer Certification: Submit a letter from the manufacturer’s representative stating the proposed system being submitted for review is in accordance with the recommendations of the manufacturer.

D. It is the responsibility of the contractor to meet with the appropriate Fulton County Schools

Representative to compare the placement and installation of proper devices with the drawings and specifications. A 100% device by device test will be conducted by the vendor under the supervision of the owner’s representative. Punch lists will be developed at that time and furnished to the contractor. All punch list items must be corrected and verified prior to acceptance of the system.

1.4 DRAWINGS

A. The Contract Drawings indicate the arrangement of the access control system equipment. Coordinate installation of equipment with the structural, mechanical, and electrical equipment and access thereto. Coordination installation of recessed equipment with concealed ductwork and piping, and wall thickness.

B. All raceways required for the ACS System are not shown on the Contract Drawings. All access control system cabling shall be installed in raceway.


1.5 RECORD DRAWINGS

A. Original content, taken directly from the Contract Drawings, shall be refused. As-built

drawings must show true as-built conditions and must be prepared using the Contractors title block, symbols and notes explaining specific details of the installation.

B. The following are minimum requirements for close out documents. Final payment shall not be issued until all requirements have been met. 1. Prior to project closeout, provide two (2) sets of complete data on equipment used for the

school in this project. This data shall be in bound form and shall include 11 x 17 as built drawings for each school.

2. All as built drawings shall include system interconnection diagrams with major

components identified and number and type of interconnecting conductors. Drawings must show actual as built conditions and point-to-point diagrams for each school.

3. Two (2) full size sets of as built drawings shall be provided in hard copy format for each

school.

4. As built drawings shall be provided on CD and in electronic format (PDF and AutoCAD - DWG) for each school.

5. Letter of Certification from the ACS Manufacturer stating that the application software

is installed in accordance with manufacturer's recommendations and is functioning correctly at the time of final inspection for each school.

6. Operating and Maintenance (O & M) Manuals shall be provided to each school and

Owner’s Representative total of 2 copies) for each school.

7. Certificate or Letter of Acceptance from Principal of the school.

8. Training Sign-In Sheets for each training session.

9. A total of two (2) copies of the Training DVD’s shall be provided for each school.

10. Document and provide two (2) copies of network configuration (such as a list of IP addresses and the devices the addresses belong to, line diagram demonstrating network topology, etc.) for each school.

11. Laminated QUICK START INSTRUCTIONS for each Video Surveillance System

Workstation at each school that provide simple directions for:

a Logging into the system and viewing live video images at the workstation b Logging into the system, searching and reviewing recorded video images at the

workstation


c Copying recorded events onto CD, DVD, USB Storage Devices and External Hard drives.

C. Completed (meaning open items have been cleared) Construction Observation Report generated

by Consulting A/E and signed by Principals and Security Contractor.

D. Security Contractor Warranty Form / Letter providing detailed description of warranty provisions, duration and start date for each school.

E. Manufacturer’s Warranty Form / Letter providing detailed description of warranty provisions,

duration and start date for each school.

F. All related documents required for substantial completion, system acceptance and final payments.

1.6 WARRANTY

A. The Security Contractor shall warrant the Card Access System for one year from date of start-up against defects in equipment or workmanship. Failed equipment shall be replaced by the Security Contractor at no cost to the owner. Owner's personnel may perform initial trouble investigation but replacement of failed equipment and escalated problem support will be handled by the Security Contractor.

B. The Security Contractor shall provide a Warranty Letter indicating the start date of the warranty. The Warranty Letter shall also provide contact information (Company name, Service Supervisor’s name and phone numbers for normal working hours and Emergency Service request). The warranty period will not start until Warranty Letter has been reviewed, approved and agreed upon by Fulton County Schools.

1.7 DESCRIPTION

A. The work included under this section of the specifications consists of the installation of a complete ACS System. Provide all labor, equipment, materials, and supervision to install, calibrate, adjust, document, and test the total system as required herein and on the drawings.

B. The contractor shall provide all documentation and shall perform all duties involved in obtaining work permits as required to complete the project. All permitting shall be within the associated city or jurisdiction.

C. The work shall consist of the installation of a complete ACS System consisting essentially of, but not limited to, the following major components:

1. Physical Access Control System Enterprise Appliance 2. Intelligent Enterprise Controllers 3. Reader Interface Modules 4. Input / Output Modules


5. Field Peripheral devices (i.e., iClass Contact-less Smart Cards, Smart Card Readers, Bio-metric Readers, PIR-passive infrared motion sensors, duress switches, sounders, electric door hardware, etc.)

6. Client workstations 7. Software 8. Power supplies & Uninterruptable Power Supplies (UPS)

D. The new ACS shall be a distributed system, based upon the standard products of ACS

manufacturers, installed within multiple areas of the facility using conventional WAN/LAN network, RS485 multi-drop communication information distribution. This project deals with the installation of a new electronic access control system for Fulton County Schools North Transporation Facility.

E. The project requires the installation of a card access system, operating in conjunction with an intrusion detection system and CCTV system to provide an integrated access control and video surveillance system for the Fulton County Schools North Transporation Facility. See one-line diagrams in contract documents. The ACS shall perform all door control function for specific doors within the facility by routing power to the electric or pneumatic strikes, magnetic locks, and other electrified hardware devices. The ACS system shall also monitor the door position status of specific doors as indicated in this specification and shown on the Contract drawings.

1.8 SYSTEM OVERVIEW

A. The card access system shall be a distributed system, utilizing the existing LAN infrastructure for communication to client workstations, reader interface panels, and file server. The file server shall be dedicated to the access control system, contain the master database and be installed in the Data Center. Client workstations (coordinate installation location and connection to LAN with site) shall be provided in the administration work area. Reference one-line diagram in contract documents for system configuration. All computers shall be supported by a Windows 7 or 8 operating system and shall communicate over the Owner furnished LAN. The remote access control panels shall house the reader interface units and shall be networked together over an RS485 or RS422 data link to the ACS intelligent system controller. The intelligent system controller shall be connected to the file ACS server. The complete ACS system shall be provided by the Security Contractor, including all software/license.

B. The ACS System shall provide all software functionality as described within these

Specifications.

C. The ACS System shall be modular, configured in a network, and capable of handling a large facility-wide configuration consisting of multiple remote reader interface units. The ACS System shall allow for easy expansion or modification of inputs, outputs, operations, and functions. The ACS System software, located on the Physical Access Control Enterprise Appliance (Server), shall be under a single software program control, shall provide full integration of all components, and shall be alterable at any time (password protected), depending upon the facility requirements. Reconfiguration shall be accomplished on-line through system programming, without hardware changes.


D. Credentials (such as access cards, fobs, etc.) shall be addressable and assigned, by the system, to unique users. The ACS System shall utilize a single, seamlessly integrated database for both its card access and enrollment functions. This integration shall be provided under one operating environment. The system’s operating environment shall be a fully multi-tasking, multi-threading Microsoft Windows Server based Operating System. The system software shall be written so that the card access and the enrollment systems are developed and built from a unified 64-bit source code set. There shall not be separate source code bases for the card access and enrollment modules of the ACS System.

E. The contractor shall be responsible for providing the necessary labor and supplies to enroll a minimum of 250 Fulton County School staff into the new access control system. This includes taking photographs and printing ID badges for each individual as well as programming all access rights.

F. The integrated access control system shall allow for the configuration of a file server and alarm monitoring client workstations. The system shall be expandable to include five (5) enrollment client workstations initially and be expandable to 15 monitoring, administrative, or integrated client workstations.

G. The integrated access control system shall allow for a minimum of one (1) client workstation to be designating as the photo ID badging workstation. The workstation shall incorporate a camera, tripod, background (sky blue), enrollment card reader and ID Badging Printer.

H. The alarm monitoring client workstation shall be able to connect to and monitor field hardware devices, such as card readers, alarm inputs, etc. The administrative client workstation shall handle tasks such as defining access groups, time zones, generating reports, creating maps, etc. (password protected). The enrollment/badging client workstation shall serve as both the credential creation and data input workstation for the cardholder management module of the ACS system. The integrated client workstation shall allow for all functions of alarm monitoring, administration, and enrollment from the single workstation. All ACS system data shall reside in a single database (file server) on the network and shall be accessible in real time to every/any system client workstation connected to the LAN network. This shall allow for automatic change propagation to all client workstations in the system as well as serve as a common database to consolidate all information and allow for better disaster recovery.

I. The ACS System shall be designed to perform a wide variety of features and functions. These

system functions should be categorized into primary "system modules" which shall include access control, alarm monitoring, cardholder management, badge card creation, and data import/export.

J. The system's primary purpose shall be to provide access control. The system shall be able to make (access granted or denied) decisions for door unlocking control functions, define access levels, and set time zones and holidays, etc. An input/output linkage feature will allow linking of monitor zone points to output control points. The ACS System shall support such features as: Minimum 25,000 cards/key codes capacity, transaction storage capability, minimum eight User definable software commands, minimum eight site codes, timed anti-passback, I/O point


control, interlocks, elevator control, and time zone/holiday overrides, etc.

K. The system shall be used for alarm monitoring. Alarms are to be prioritized. The alarm-monitoring screen shall provide information about the time and location of the alarm(s), along with its priority. The alarm-monitoring screen shall be able to sort pending and/or insert new alarms based on any of the following attributes: priority, date/time, panel, card reader, or cardholder. Date/time sorts shall be user selectable to be either ascending or descending and shall have the option of displaying the seconds of the minute in which the alarm arrived into the system. All alarm points shall be logged, stored, and displayed by the ACS system.

L. The system shall allow unique emergency instructions to be specified for each type of alarm. A real-time graphic status screen shall indicate if card readers, motion detectors, or door position switches are secure, unsecured, in alarm, off-line, etc. Output control operations shall be available to lock, unlock or pulse control points as a standard feature. A cardholder call-up feature shall allow the quick search and display of cardholders in the database. A system operator journal shall be available to log important daily events. A trace function shall be available for system operators to locate and track activity on specific cardholders or card readers. All alarms and hardware icons shall have the ability to control the associated hardware via mouse clicks.

M. The system shall include an enrollment system integrated with the card access system. The enrollment functionality shall allow the enrollment of cardholders into the database, and import/export of employee data from/to the Owner’s human resource database. The import/export of data between the HR database and the ACS system database shall be through an ODBC connection to ACS systems database. This functionality shall also allow the system operator to assign or modify access rights of a cardholder. The enrollment system shall also allow the enrollment of personnel into the database and if available permit the import/export of employee data from/to the Owner’s human resource database.

N. System administrative tasks such as defining workstation & system operator permissions, access groups, time zones, reports, maps, etc. shall be provided from any workstation on the network (password protected). Initial setup of the cardholder screen layout shall occur on the database server. The contractor shall be responsible for the creation of these activities for the initial installation of the ACS and enrollment systems. This activity shall be closely coordinated with the Owner and User groups to achieve the results desired.

O. The ACS System and enrollment System shall provide an import utility that will allow the Owner/User to import cardholder information into the system database. This shall allow the Owner/User to pre-populate the system database with existing cardholder data and/or add new records to the ACS system database. The contractor shall be required to coordinate the requirements and provide the necessary import / export utility (and licensing) to allow Owner/User existing database information to be imported into the ACS System’s database and into the enrollment System.

P. The Enrollment System shall include an employee management module integrated with the

ACS System. The employee management functionality shall allow the enrollment of cardholders into the database, capturing of images and signatures, and import/export of


employee data. This functionality shall also allow the system operator to assign or modify access rights of a cardholder.

Q. The ACS System shall be provided with software that shall allow the contractor to import

customized map backgrounds of their facility and to attach custom icons to those maps. The contractor shall be responsible for developing, importing and populating the maps with all field devices properly located and identified with ICONS.

1.9 SYSTEM APPLICATION AND REQUIREMENTS

A. All ACS System application modules, features, and functions shall be generated from a single source code set. In addition, the source code shall be designed using object-oriented software development techniques and compiled into native 64-bit applications. The access control, alarm monitoring, and ID management modules of the software shall be created from this single source code set. A single manufacturer shall develop ID management software and the ID management software shall be a subset of the access control administrative module.

B. The ACS System shall have an open architecture design. It shall be a true open architecture design and support industry standards for databases, networks, ID card printers, and video cameras. No customized or proprietary PC or ID badge creation software or hardware shall be required or permitted to make the ACS System operate. The ACS System shall be both scalable and portable to give Owner/User the ability to increase performance based on Owner/User requirements. This shall give Owner/User maximum flexibility and room for unlimited growth.

1. The ACS System shall be open database connectivity (ODBC) compliant. The system

shall support any relational database management system with the proper 64-bit ODBC drivers. Examples of these databases include, but are not limited to, Microsoft SQL Server and Oracle Server.

2. The ACS System shall be designed so that two methods of integrating the aforementioned relational database management systems are possible. The first method shall be to use one of these databases as the system’s dedicated database server, meaning only the system’s information is stored in the database.

3. An alternative method is to use one of these databases as a non-dedicated database server and attach system database tables to the existing database that may be used by one or many systems.

4. The ACS System shall be scalable to support symmetric multi-processing (SMP) machines. The relational database management system (RDBMS) within the system shall use a single-process, multi-threaded architecture, which provides scalable, high system performance with very efficient use of system resources.

5. The ACS System shall be provided with an industry standard network protocol and topology listed below: a. TCP/IP b. Novell Netware (IPX/SPX) c. Digital PATHWORKS d. Banyan VINES e. IBM LAN Server (NetBEUI) f. IBM SNA Networks


g. Microsoft LAN Manager (NetBEUI) h. NFS Networks i. Remote Access Service (RAS) via ISDN, x.25, and standard phone lines

C. The ACS System shall support a user friendly, Windows style Graphical User Interface (GUI) that shall be intuitive to operate. All messages and interface text shall be in English prose. All functions shall be either keyboard or mouse driven to allow the system operators to choose the method of navigating through the screens. In the alarm-monitoring module of the system software, all major functions (opening a door, acknowledging alarms, etc.) shall be accomplished in one or two mouse clicks. This shall allow for ease of operation, especially in an emergency situation.

D. The ACS System shall be extensively integrated and utilize multimedia throughout the system software. Real-time, dynamic graphical maps will mean that the map screen will not have to re-paint or refresh each time a new alarm or event condition occurs. The ACS System shall support and provide a flashing colored icon annunciation system for each alarm in the system. The ACS System shall also support and provide customizable instructions so that each alarm or event in the system can have a text set of instructions.

1.10 OPERATING SYSTEM REQUIREMENTS

A. The ACS System shall support the 64-bit Microsoft Windows XP or Windows 2000/2004 (latest revision) multi-tasking, multi-threading operating system. The ACS System shall meet the following minimum requirements for a Windows NT based system.

B. The operating system shall offer the look and feel of Windows NT 4.0 or Windows 2000 to enhance usability and efficiency. The operating system shall come complete with administrative wizards and interactive help to guide system administrators in the configuration of the system.

C. The operating system shall support a minimum of 5 networking protocols including, but not limited to, TCP/IP, IPX/SPX, RAS, and NetBEUI. The system shall also support peer-to-peer and FTP server capabilities.

D. The operating system shall support both dial-out capabilities to remote servers as well as remote dial-in capabilities.

E. The operating system shall support multiple user profiles on the same workstation so system administrators can assign which programs will be available to system operators based on their operating system user log-on. Local workstation security access will be available through User ID and required password log-on. The operating system shall also offer government C-2 level certifiable security.

F. The ACS System shall be provided with a network connection to the CCTV System. This

interface between the ACS System and the CCTV System shall permit the ACS System to


control and automatically display camera video on designated CCTV monitors in conjunction with controlling and monitoring card access controlled doors.

1.11 DATABASE MANAGEMENT

A. The operating system shall support any relational database management system that is industry standard Open Database Connectivity (ODBC) compliant. This shall include relational database management systems such as Microsoft SQL Server and Oracle Server. These databases, through ODBC, shall be true client/server, high performance, and ANSI standard capable of handling high transaction rates and multiple users concurrently accessing and modifying the database.

B. The system’s RDBMS shall preserve data integrity in the following ways:

1. Transaction processing guarantees the consistency and recoverability of the RDBMS. Transaction processing shall assure that all transactions are performed as a single unit of work, even in the presence of a hardware or general system failure.

2. The system’s RDBMS shall enforce data integrity within the database itself, guaranteeing that complex business policies will be followed. “Referential Integrity” maintains consistency between multiple tables of a database. For example, you do not want to delete an access level from the database without removing that access level from all cardholders that are assigned the access level.

3. The system’s RDBMS shall use advanced data integrity features such as data types, defaults, and rules to enforce data integrity. Stored procedures and triggers shall also be used to insure the integrity and security of data.

4. The system’s RDBMS shall utilize data types, which provide the simplest form of data integrity by restricting what kinds of information (for example: characters, numbers, or dates) may be stored in the columns of the database tables.

5. The system’s RDBMS shall also utilize defaults, which allow the system to specify a value that the RDBMS inserts if no explicit field value is entered.

6. The system’s RDBMS shall enforce rules, which are integrity constraints that go beyond those implied by a field’s data type. Whenever a user enters a value, the RDBMS shall check the value against any rule that has been created for the specified field. For example, rules can require that a value fall within a particular range, match a particular pattern, or match one of the entries in a specified list. The system’s RDBMS shall also provide two powerful and flexible features for enforcing programming integrity and business rule logic centrally at the Network File Server’s stored procedures and triggers. a. The RDBMS shall incorporate stored procedures for increased data integrity. For

example, whenever a SQL command is sent to the RDBMS for processing, the server shall parse the command, check its syntax to see if it makes sense, check to see if the requester has the permissions necessary to execute the command, and formulate an execution plan to process the request.

b. Triggers are a special type of stored procedure. Triggers are associated with particular pieces of data and are automatically initiated whenever attempts to modify that data are made.

Fulton County Schools: North Transportation Facility April 8, 2016 28 3000 - 11 J&A Engineering ADDENDUM #4 06/20/2016 1.12 NETWORK CONFIGURATION

A. The system shall be designed to allow it to work with any industry standard network protocol

and topology listed below:

1. TCP/IP 2. Novell Netware (IPX/SPX) 3. Digital PATHWORKS 4. Banyan VINES 5. IBM LAN Server (NetBEUI) 6. IBM SNA Networks 7. Microsoft LAN Manager (NerBUI) 8. NFS Networks 9. Remote Access Service (RAS) via ISDN, x.25, and standard phone lines

B. There shall not be a limit to the number of client workstations that can be attached to the

database server. Each client shall have the ability to consist of any combination of access control, system administration, alarm monitoring, or ID management functions.

C. The system shall be designed so that any Windows NT based workstation on the network that is licensed to operate the system Software can have field control panels connected to them. This design shall save installation and wiring costs, as field control panels do not have to be home-run wired back to the Network File Server.

D. As such, any alarm in the system, regardless of the field control panel that generated the alarm, can be routed to any workstation on the network. Alarms shall also be routed to multiple workstations on the network and shall have the ability to be routed to different workstations during different hours of the day through time zone control.

1.13 WORKSTATION/USER INTERFACE

A. The ACS System shall have an easy to use Windows Graphical User Interface (GUI). It shall be intuitive and all messages and commands shall be in English Prose. All functions shall be both keyboard and mouse driven.

B. Within the alarm monitoring module of the system, all major functions (such as acknowledging alarms, opening doors, and viewing cardholder information, etc.) shall be able to be accomplished in one or two mouse clicks.

C. The ACS System shall have the ability to have system information that will be viewed in the application windows to be in a user defined type face and point size. The ACS System shall support a minimum of 55 Fonts. These fonts shall be available from a pick list to the system administrators. This shall be especially important in the alarm-monitoring module of the software.


D. A Help icon shall be available in all modules of the software giving system operators/ system administrators the ability to obtain on-line help with a single click of the mouse. The help command shall also be keyboard driven.

E. The ACS System shall utilize a tabular format within the software to group procedures and

forms together to guide the system administrator through system configuration.

PART 2 – PRODUCTS 2.1 ACCESS CONTROL SYSTEM (ACS) HARDWARE

A. System Description

1. The Electronic Access Control solution shall be available in the following form(s):

a. Access Control System Enterprise Appliance

2. The ACS Appliance shall be an IT standards compliant, fully featured Access Control

System solution.

3. The ACS Appliance shall be available in the following format(s):

a. ACS: As a true network hardware appliance with all software applications preinstalled.

4. The ACS Appliance shall be built upon a hardened Linux network appliance using LDAP compliant directory structure.

5. The ACS Appliance shall automatically manage updates to:

a. Operating system service packs

b. License seats

c. Virus control 6. The ACS Appliance and solutions shall use industry standard TCP/IP network

infrastructures to communicate with, but not limited to:

a. All ACS Appliances

b. Enterprise Intelligent Field Hardware Controllers

c. Browser based workstations 7. The ACS Appliance shall be comprised of industry standard pre-installed components

including:

a. An embedded Linux operating system using an open source kernel.


b. An OpenLDAP Directory structure for identity data storage.

c. Splunk enterprise software to allow users to easily search, monitor, and analyze all ACS transaction data from any ACS Appliance across the enterprise.

d. A NGINX Web server

e. ACS application software.

8. All set up, maintenance and interaction with the system shall be accomplished with no interaction with the operating system or directory structure.

9. The ACS Appliance shall act as the central repository for all system configuration and activity.

a. Interfacing with the ACS Appliance shall be via a web browser only.

b. A separate database server with a unique operating system and database server shall not be acceptable.

10. The ACS Appliance shall provide browser-based accessibility to all Appliance applications, without a dedicated client workstation. The following industry standard web browsers shall be supported:

a. Mozilla Firefox

b. Google Chrome

c. Internet Explorer

11. The ACS Appliance shall support industry standard field hardware platforms, including but not limited to:

a. Mercury Security’s access control product line

b. HID Physical Access Control Solutions

12. The ACS Appliance shall be hardened to safely secure all communications and data.

a. Data communicated over the network to/from the ACS Appliances and the web browser workstations shall be secured via SSL 128-bit encryption.

b. ACS Appliance backups shall be encrypted using AES Encryption.

c. ACS Appliance backs up to

1) USB Storage Device,

2) Windows shared directory or network shared folder,

3) Secured SCP servers.


d. All passwords required to login to the ACS Appliance shall be encrypted within the OpenLDAP directory structure.

13. The ACS Appliance architecture shall enable distributed decision making at the enterprise intelligent field hardware controllers.

a. The ACS Appliance architecture shall enable complete functionality when communication is lost between an Appliance and its associated enterprise intelligent field hardware controllers.

b. During downtime, the enterprise intelligent field hardware controllers shall maintain an audit log of all activity that occurs and shall upload this data to the ACS Appliance once normal communications is restored.

14. The ACS architecture shall provide scalability to support the addition of:

a. Card readers and/or input/output points

b. Additional ACS Appliances c. Enterprise intelligent field hardware controllers

15. The ACS shall support a hot standby, auto-failover architecture. Should a Primary ACS Appliance fail to function, an assigned secondary ACS Appliance shall automatically detect the problem and assume system control.

16. The ACS shall support integration with 3rd party subsystems through use of its collaboration interface. These systems shall include but not limited to:

a. Integrated Access Management (IAM) systems,

b. Security Information and Event Management (SIEM) systems,

c. 3rd party IT and business systems, including but not limited to

1) Oracle RDBMS

2) Microsoft SQL Server

d. The ACS shall be able to pull information into its directory structure and push events out to 3rd party systems.

17. The ACS shall provide single software based license key that resides on each enterprise ACS Appliance to control licensed features and/or components.

a. Software licenses shall be upgradable and/or amendable via email or download from the manufacturer’s secured web site.

b. The ACS Appliance shall support a minimum of 50 concurrent client connections.

1) Individual license keys for traditional client workstations and/or physical hardware license keys is not required.

18. The ACS Appliance shall support seamless, forward compatible upgrades of the ACS application software.


a. All systems of the same generation shall be upward compatible

b. Access control field hardware devices shall be scalable

2.2 ACCESS CONTROL SYSTEM (ACS) APPLIANCE HARDWARE

B. Access Control System Enterprise Appliance

1. Appliance hardware platform shall consist of a 1U, short depth, rack-mount unit meeting the following minimum specifications:

a. CPU: Intel® Quad Core 3.1 GHz 8M Cache

b. Memory: 4GB, 1600Mhz

c. Network Interface: Minimum of 2 x 1GbE per port

d. OS Compatibility: Linux Hardened Virtual Appliance

e. 1TB, 7200 RPM disc for OS/Appliance and storage

2. ACS Appliance Capacities

a. Doors: 2048

b. Alarm Input Points: 5,060

c. Relay Output Points: 5060

d. Card Holder Identities: 500,000

e. Concurrent Web Client Connections: 50

f. On-line Event History Log: 150,000,000]

2.3 ACCESS CONTROL SYSTEM (ACS) SOFTWARE

C. Access Control Functionality

1. Alarm and Event Attributes:

a. The ACS shall allow Administrators to configure how each alarm and event is announced in the Alarm Monitor window.

b. The Event Listing window shall list all alarms and events with their associated event type and trigger source.

2. For each alarm and event in the system, Administrators shall have the option to:

a. Rename the alarm or event

b. Name the “return to normal” status for the alarm or event.

c. Assign a default event type for the alarm or event.

d. Display the alarm or event in the Alarm Monitor.


e. Mask the alarm or event from displaying in the Alarm Monitor.

f. Display text instructions that shall guide the Operator in responding to the alarm.

g. Automatically send an email message.

h. Have the alarm display in alarm priority. A minimum of 99 priorities shall be supported.

i. Set the priority of the alarm or event, as well as its associated “return to normal” event priority.

j. Automatically launch the video player if video is linked to the alarm or event.

k. Store alarm or event information.

l. Create a schedule to enable/disable global events, which include but not limited to:

1) Shunt/un-shunt doors

2) Mass denial of credentials (“lock down”)

3. Alarm and Event Logging - All alarms and events shall be logged according to the ACS Appliance's internal data storage logging structure.

4. Offline Alarm/Event Queue - The ACS shall queue alarms and events that occur:

a. While the ACS software is offline

b. When an Operator is not logged into the ACS software. 5. Upon logging in and accessing the Alarm Monitor window, all queued alarms and events

shall be reported in the Alarm Monitor for Operator action.

6. Alarm and Event Types - The ACS shall support the creation of alarm and event types:

a. Alarm and event templates shall be created as part of the installation.

b. Event type options shall include but not limited to:

1) Priority,

2) Text instructions,

3) Masking and unmasking schedule,

4) Logging

5) Reporting

6) Email notifications

c. Each alarm and event type shall support multiple alarm and event assignments. 7. Alarm/Event Synchronization - The ACS shall support alarm synchronization for alarm

and events. When an alarm or event is acknowledged or cleared by an Operator, it shall be cleared for all other Operators.


8. Alarm Reporting Based on Schedule - The ACS shall report alarms based on a schedule. Each alarm in the system shall have the ability to have its own associated schedule.

9. Alarm/Event Text Instructions - The ACS shall allow each alarm and event in the system to have associated text instructions.

a. Text instructions shall support a minimum of 200,000 characters. 10. Access Groups – An access group shall consist of card reader and schedule

combinations.

a. Access groups shall consist of any number of card readers assigned to a single schedule.

b. Any card reader shall have the ability to belong to one or more access groups..

c. The ACS shall allow credential holders access to secure areas based on:

1) Card reader

2) Time

3) Day

d. The ACS shall support a minimum of:

1) 255 access groups per intelligent enterprise controller

2) Access groups can be assigned to each credential holder per intelligent enterprise controller, and shall optionally be selectable up to:

a) 8 total

b) 16 total

e. Access groups shall support names with up to 50 alphanumeric characters. 11. Schedules – The ACS shall support the creation of schedules:

a. Schedules shall serve as templates for, but not limited to:

1) Access Groups,

2) Masking devices,

3) Device modes.

b. Each schedule shall have the ability to repeat after a predetermined interval.

1) Shall have the ability to be assigned to any day(s) of the week

2) Shall be assigned to function on up to 8 Holiday types

3) Up to 10 intervals shall be supported

c. The ACS shall support a minimum of 255 schedules. Each schedule shall be set to one of 3 operating modes:

1) On - The schedule is active 24 hours per day / 7 days per week


2) Off - The schedule is not active

3) Scan - The schedule is active during its assigned intervals

d. Schedules shall be downloaded to all related enterprise intelligent field controllers for local processing and decision making.

e. Schedules shall support names with up to 50 alphanumeric characters. 12. The ACS shall allow specific dates and/or date ranges to be designated as holidays.

a. The ACS shall support a minimum of 255 holidays.

b. Each holiday shall have the ability to span multiple days and be assigned up to 8 different holiday types.

c. When a specific day has been designated a holiday, parameters within the ACS shall be temporarily altered, adjusted or suspended, including but not limited to:

1) Card reader modes

2) Identity’s access rights

3) Masking schedules

d. Each schedule shall have the ability to include up to 8 independent holiday types.

e. The ACS shall support an embedded calendar to assist in the configuration of holidays.

f. Holidays shall support names with up to 50 alphanumeric characters. 13. Card reader options - The ACS shall have the following options for card readers in the

system:

a. “Installed” shall identify the card reader as active.

b. Offline mode is used when the card reader loses communication with the enterprise Intelligent Field Controller.

c. Custom mode for a predefined schedule. At the completion of the schedule, the card reader shall revert to its standard operating mode.

d. “Door Forced Filter” shall reduce false Door Forced Open alarms when doors open within 3 seconds of closing.

e. “Deny if Duress” shall deny a credential holder access to the card reader even if the proper duress code is used. An alarm shall be generate to note duress access was requested and denied.

f. “Mask Alarms” shall allow Door Forced Open and Door Held Open alarms to be masked either permanently or during a scheduled basis..

g. “Strike Mode” shall allow Administrators to define if:

1) The door strike remains active for the entire strike time


2) The door strike turns off after the door has closed

3) The door strike deactivates as soon as the door is open h. “Do Not Pulse Door Strike on REX” shall determine if the door strike shall be

pulsed upon a valid request to exit.

i. “Do not log REX Transactions” shall not log requests to exit.

j. “Log all Access as Used” can be used when there is no door contact to monitor door position. Upon a valid access grant, the ACS shall assume entry and report an event into the Alarm Monitor.

k. “Two-Card Control” shall require that two valid access requests occur prior to granting access to the door.

1) Both requests must occur within a 10 second period.

2) In the event a second valid access does not occur within 10 seconds, the card reader shall reset and the first credential must be presented again.

l. “LED Mode” shall allow Administrators to choose from three light settings that will specify how LEDs operate during specific system activities.

m. “End-of-Line Resistance” shall give Administrators the option to:

1) Independently define requests to exit and door contacts as Normally Open or Normally Closed

2) Independently define request to exit and door contacts as Supervised or Unsupervised.

n. “Activate Schedule” shall allow Administrators to activate outputs attached to the card reader on a scheduled basis:

1) “Use Shunt Relay” shall have the ability to shunt a door contact of separate intrusion detection systems:

a) When the ACS provide an access grant, a dedicated auxiliary output shall first trigger and bypass the door contact of the separate intrusion detection system, and then the door locking mechanism shall unlock.

b) Once the door returns to a secure state, the door contact of the separate intrusion detection system shall return to its normal state.

2) Whether a card reader is part of an anti-passback area and if so, it’s related configuration.

o. PIN Attempts shall define the number of invalid attempts a credential holder may present before generating an alarm to the Alarm Monitor.

p. Door Held Open Pre-Alarm shall define the number of seconds prior to a generated Door Held Open alarm that an audible annunciation will begin sounding at the door.


14. Recent Door Transactions - The ACS shall provide a form listing the most recent transaction activity associated with a door, without having to run a report.

a. Information provided shall include

1) transaction activity,

2) time/date,

3) identity

4) Token related details. 15. Door Summary and Status Page - The ACS shall support a Door Summary and Status

Page that shall display a list of all doors defined in the system. For each door in the system, the Door Summary and Status page shall display:

a. Door Name

b. Current Door Mode

c. Door Status including forced and held states, masking states, as well as communications and tamper states

16. Buttons in the Graphical User Interface shall be available to control the operational state of the door including:

a. Disable

b. Lock

c. Unlock

d. Grant

e. Restore

f. Mask Held

g. Unmask Held

h. Mask Forced

i. Unmask Forced

17. The Door Summary and Status Page shall be filtered by Door Group or by other searchable criteria.

18. Card Reader Scheduled Mode Overrides - The ACS shall support the ability for card reader modes to be overridden from the standard mode on a scheduled basis.

a. Based on the card reader type, custom modes shall include

1) Card only,


2) Card and PIN,

3) Card or PIN,

4) Locked,

5) Unlocked,

6) Facility code.

7) At the end of the scheduled override, the card reader shall return to its default standard mode.

19. Cipher Mode - The ACS shall support Cipher Mode, which shall emulate the presenting of a credential to a card reader with a keypad.

a. In Cipher Mode, an authorized credential holder shall attempt access by entering their Credential ID/Card Format at the keypad.

1) The card reader shall treat the information as a magnetic card format read.

2) The number sequence must match an existing magnetic card format configured in the system, including facility code.

3) Correct entry of code will allow access

4) Incorrect entry of code will be ignored:

a) Deny access to the card reader,

5) Will not send a transaction to the Alarm Monitor.

b. A card reader in Card and PIN Mode and Cipher Mode shall also require that the credential holder’s PIN be entered after the original sequence.

c. Changes in card reader mode shall not remove a card reader from Cipher Mode. 20. Duress Access to a Card Reader - The ACS shall support a Duress Mode for a credential

holder’s entry through a card reader.

a. When a credential holder is gaining entry under duress, they shall append the number “5” to the end of their PIN code.

1) Thus, a credential holder with PIN of 9999 would enter 99995 when entering an area under duress.

b. Duress access shall be made for card readers in

1) Card and PIN mode,

2) Card or PIN mode,

3) PIN Mode only.

c. Upon entrance to a card reader under duress, an alarm shall be sent to the Alarm Monitor and logged to the audit database.

21. Extended Cardholder Strike Times - The ACS shall allow a card reader’s strike to be extended beyond the normal strike time for specific individual credential holders.


a. The extended strike time shall be definable up to 255 seconds.

b. ACS shall be able define application of this functionality by:

1) Card reader,

2) Credential holder. 22. Extended Cardholder Door Held Open Time - The ACS shall allow a card reader’s door

held open time to be extended beyond the normal configured time

a. The extended door held open time shall be definable up to 32,767 seconds.

b. ACS shall be able to define application of this functionality by

1) Card reader

2) Credential holder. 23. Multiple Card Formats - The ACS, enterprise Intelligent Field Controller, and card

readers shall all support a minimum of 8 card formats, including but not limited to:

a. Wiegand

b. Magnetic Stripe

c. The ACS shall support any industry standard format that uses:

1) A card number,

2) Facility code,

3) Issue code combination.

d. The ACS shall support

1) A maximum nineteen (19) digit card number

2) Two digit issue code. 24. Wireless Reader support – The ACS shall support the Mercury enabled Aperio 8:1 Hub

from ASSA ABLOY allowing connectivity to wireless readers.

25. Pre-Alarm - The ACS shall support a door held open pre-alarm capability. When a door has been held open for a pre-determined amount of time after a valid access grant, a local audible annunciation shall alert the credential holder to close the door. Failure to close the door between the pre-alarm annunciation and the configured door held open time shall generate an alarm at the Alarm Monitor. Pre-Alarm parameters apply to

a. Door held open time

b. Pre-alarm time

c. Shall be configurable up to 65,534 seconds.

d. Pre-alarm setting shall be distinct for each door.


26. Invalid PIN Attempts Counter - The ACS shall support an invalid PIN attempts count on a per card reader basis. Invalid PIN attempts parameters shall include, but not be limited to:

a. Unknown PIN entry at a card reader configured as “PIN or Card” mode

b. Invalid cipher entry at a card reader in Cipher Mode

c. Invalid PIN entered for a given card at a card reader configured as 'Card and PIN‟ mode

d. The “Denied PIN Attempts” value shall be configurable from 0 to 255.

e. The following events shall cause the counter to rest to zero:

1) X (User Defined) minutes pass without any of the above denial types

2) An access grant at the given card reader f. When the current denied count reaches the threshold configured for the card reader,

a “Deny Count Exceeded‟ transaction shall be reported.

1) This transaction shall only be reported when the limit is initially reached.

2) It shall not report on subsequent denials. 27. ACS shall support Macro/Trigger functionality when the “Deny Count Exceeded”

transaction occurs. Actions shall include, but not be limited to:

a. Lock down the card reader

b. Annunciating a local siren.

c. Shall be configured to execute for a given card reader, 28. Custom End of Line Resistance Configuration - The ACS shall allow Administrators to

define configurations to be assigned to alarm inputs.

a. A minimum of 4 custom end-of-line resistance configurations.

b. Configurations shall be given a priority of low, medium or high

c. Configurations shall include options for low range and high range resistance thresholds.

d. Configuration options shall include the following input line statuses:

1) Inactive,

2) Active,

3) Ground Fault,

4) Open,

5) Short,

6) Foreign,


7) Non-Setting. 29. Elevator Control - The ACS shall provide elevator control:

a. Using standard access control field hardware

b. Permits the restriction of access to certain floors

c. Shall not restrict access to general admittance floors.

d. Card readers shall be located in the cab of the elevator.

1) Shall be able to control access for a minimum of 1[*Section 28 floors.

2) Shall integrate to Input and Output Control Modules

3) Shall restrict which floor select buttons are accessible when a credential is swiped based on the identity’s access level.

4) Shall permit only one authorized floor to be selected per single card swipe.

5) Shall not require a swipe by any passenger to access floors programmed as public access.

30. The ACS shall support a separate mode for each floor to allow visitor/general access to different floors during different times of the day.

31. The ACS shall be able to track which floor was selected by an individual cardholder for auditing and reporting purposes.

32. Anit-Passback

a. The ACS shall provide area control features including, but not limited to: 1) Hard Anti-passback, 2) Soft Anti-passback, 3) Timed Anti-passback, 4) Two Person Control. 5) Occupancy Count.

a) A minimum of 127 areas shall be able to be created per ACS Appliance.

b. Hard and Soft Anti-Passback Common Function: In addition to functions specific to Hard or Soft Anti-passback, either function shall include, but not be limited to:

1) Initially (Time 0) all credential holders are reset to Area 0.

2) Any credential holder shall enter a controlled area any time after Time 0 by presenting a Token to an entry card reader.

3) A credential holder shall not exit the controlled area unless he/she has entered the area presenting a Token to the area entry card reader.

4) A credential holder shall not enter the controlled area a second time unless the credential holder has exited that area previously.


5) A credential holder shall be able to enter through any entry card reader and exit through any exit card reader of a single controlled area.

6) A "forgiveness" feature that shall allow the Administrator to give credential holders “One Free Pass” to allow the ACS to move them into the next area they enter, regardless of their current anti-pass pack status.

a) One Free Pass shall be given to an individual credential holder, to all credential holders in a single enterprise Intelligent Field Controller, or to all credential holders in the ACS

7) The ACS shall provide an anti-passback exempt option for privileged or VIP credential holders. Credential holders with this option will not have anti-passback rules applied to them.

8) An area shall have the ability to be disabled/closed that shall not allow any access into the area with the exception of those Tokens with APB privileged status.

c. Hard Anti-passback (APB) –

1) Shall require that a Token always be used to enter and exit an area.

a) The controlled areas shall have both entry and exit card readers at all portals.

b) Entry and Exit Readers shall be confined to a single enterprise Intelligent Field Controller.

c) Areas shall be logically defined.

d) Area control shall not be required to encompass every card reader in the system.

2) Shall work in the following manner.

a) Once in an area, a credential holder must present their Token at an exit card reader of the area they are currently in and wish to leave.

b) Once access has been granted to leave the area and enter a new area, the credential holder must present their Token at an exit card reader of the new area.

c) Should a credential holder present their Token at any other card reader involved in Area APB, the credential holder shall be denied access and an alarm shall be reported.

d) Nested control areas (areas inside areas) shall be definable with a minimum of 64 entry and exit card readers. It shall be possible to have an area within an area and/or multiple areas that are independent of each other in which Hard Anti-passback rules shall apply.

d. Soft Anti-passback (APB) - Soft Anti-passback shall require that a Token be used to enter and exit an area.


1) The controlled areas shall have both entry and exit card readers at all portals.

a) Entry and Exit Readers shall be confined to a single enterprise Intelligent Field Controller.

b) Areas shall be logically defined.

c) Area control shall not be required to encompass every card reader in the system.

2) Shall work in the following manner.

a) Once in an area, a credential holder must present their Token at the exit card reader of the area they are currently in and wish to leave.

b) Once access has been granted to leave the area and enter a new area, the credential holder must present their Token at an exit card reader of the new area.

c) Should a credential holder attempt this, the credential holder shall be allowed access (if that credential holder has the appropriate access level to access the new area), and an alarm shall be reported.

d) It shall be possible to have an area within an area and/or multiple areas that are independent of each other.

e. Timed Area Anti-passback (APB) - Timed Area Anti-Passback shall allow an Administrator to decide how long after a credential holder has swiped their Token that they will have to wait before the same Token will be accepted again at the same card reader.

1) If a credential holder swipes their Token a second time after initial entry and after the delay time has expired, access shall be granted and an Anti-passback alarm shall be reported into the Alarm Monitor.

2) Administrators shall be able to set the delay time up to 65,535 seconds.

f. Two-Person Control shall be provided to restrict access to certain areas unless there are two (2) credential holders present.

1) When an area is configured for Two Person Control, the following criteria shall prevail:

a) The card reader shall grant access only if two valid credential holders (with authorized access privileges) swipe their badges one after the other. In the event that a second authorized badge is not presented within 10 seconds of the first authorized badge, the card reader shall reset and the first card will have to be swiped again.

b) Once 2 people occupy an area, individual access shall be granted.

c) Individual exit shall be permitted until an area is occupied by only 2 credential holders at which point the Two Person Control applies for exit,


meaning both credential holders must present their cards at the exit reader within 10 second of each other and exit together.

33. Occupancy Count / Control - Occupancy Count / Control shall restrict the number of credential holders that shall be present in an area at any given time.

a. The Occupancy Controlled area shall be able to be defined by the Administrator to limit up to 250,000 credential holders to be in that area at any given time.

b. Once the occupancy limit has been reached, a credential holder must swipe out of the exit card reader before the next credential holder may enter.

c. Each area for which Occupancy Control is enabled shall be definable with up to 64 entry/exit card readers.

d. Multiple Occupancy Controlled Areas shall be definable. 34. Custom Device Mappings / Local Alarms – Local Alarms shall give administrators the

ability to assign a unique group of alarm attributes to specific device-alarm combinations to override the global settings for generic attributes.

a. Administrators may assign a different set of attributes to be applied to a ‘forced door’ at a research lab than they would for a ‘forced door’ at a perimeter location.

35. Entry / Exit Delay - Administrators shall have the ability to set up entry/exit delays for inputs that are attached to any Input Control Module, Single Reader Interface Module, or Dual Reader Interface Module.

a. Administrators shall have three options for entry/exit delay: b. Non-Latched Entry: Administrators shall have the ability to set an input to non-

latched entry.

1) When non-latched entry mode is selected and an entry delay is specified, the following procedure ensues:

a) When an input activates, the alarm will not be reported until the Entry delay expires. If the input is still active when the entry delay expires, the alarm will be reported.

b) If the input is not active when the entry delay expires, then the alarm will not report.

c. Latched Entry: Administrators shall have the ability to set an input to latched entry.

1) When latched mode is selected and an entry delay is specified, the following procedure ensues:

a) When an input activates, the alarm will not be reported until the Entry delay expires.

b) If the alarm has not been masked by the time the entry delay expires, the alarm will be reported.


c) If the input has been masked when the entry delay expires, then the alarm will not report.

d. Exit Delay: Administrators shall have the ability to set an input to Exit Delay that activates directly after an input has been unmasked.

1) When an exit delay is specified, the following procedure ensues:

a) When an input activates, the alarm will not be reported (operates as if masked) until the Exit delay expires.

b) If the input is still active when the exit delay expires, the alarm will be reported.

c) If the input is not active when the exit delay expires, the alarm will not be reported. This is useful to secure a door when an individual is leaving.

e. The ACS shall support a minimum of 65,535 seconds for entry and exit delays.

36. Input Control Module Options - The ACS shall allow the following options to be defined for inputs or outputs in the Input Control Module:

a. Debounce Time shall allow Administrators to control the time that an input state change must remain consistent in order for it to be considered a real change of state.

b. End of Line Resistance shall give Administrators the option to define an Input as Normally Open or Normally Closed and define an input as Supervised or Unsupervised.

c. Hold Time shall be the amount of time in seconds to wait to report an input activation as restored when an input goes active and then is restored.

1) The hold time shall be configurable from 0-15 seconds. d. Alarm Masking shall allow the input to be masked either all the time or during a

defined schedule.

e. Activate Output shall allow Administrators to configure an output to activate all the time or during a defined schedule.

f. Installed shall define whether the ACS shall consider the input an active component of the on-line system.

g. Logging shall allow Administrators to determine whether to log all change of state events or only when the event is not masked.

37. Relay Output Options - The ACS shall allow the following options to be defined for outputs in the Output Control Module:

a. Installed shall define whether the ACS shall consider the output an active component of the on-line system.


b. Relay Output Mode shall set the default mode of the relay output.

c. Pulse Time shall define how long the output shall pulse when the command is given.

d. Schedule shall define the time the relay output is active.

38. Input / Output / Event Linkages - The ACS shall support input/output/event linkage whereby an input/output/event in an enterprise Intelligent Field Controller can trigger an action within the same enterprise Intelligent Field Controller.

a. All linkage decisions shall be made local to the Intelligent Enterprise controller. b. Administrators shall be able to create macros, each consisting of a sequence of

actions to be performed, such as changing card reader modes and activating outputs.

c. Each macro shall include up to 30 actions.

d. Administrators shall then be able to link events to the aforementioned macros such that a particular action will trigger a macro to execute.

39. The ACS shall provide administrators the ability to create action groups that may include multiple actions associated with a single event.

a. Identity filters shall be available to allow activity from specific identities to trigger an action.

b. Additional filters shall be applied so that an Event Input can be filtered to a specific hardware device and/or a specific credential holder Token ID.

40. Inputs shall include any enterprise Intelligent Field Controller level event, including but not limited to:

a. enterprise Intelligent Field Controller Events

1) Cabinet tamper

2) Power failure

b. Input Control Module Events

1) Communication loss 2) Cabinet tamper 3) Power failure 4) Input points

c. Card Reader Events 1) Cabinet tamper 2) Communication loss


3) Door contact tamper 4) Door forced open 5) Door held open 6) Power failure 7) Card reader tamper

41. Macro actions shall include, but not be limited to:

a. Activating an Output Control Module Output

b. Masking/Unmasking an Alarm Input

c. Setting the active mode of a card reader

d. Activating/Deactivating a Schedule D. Identity Management Functionality

1. Identity Management Integration - The ACS shall offer an integrated Identity Management and Enrollment functionality as part of the core system functionality.

2. The ACS Identity Management Integration shall be provided with a photo ID capture camera with tripod and backdrop, FARGO DTC4250e photo ID badging printer with double side printing capability as well as printing supplies to print 250 double sided badges, read /write encoder for contactless smart cards, dual-sided printing module, enrollment card reader at the Photo ID Badging Station and all associated cables and light kits.

3. Data Import - The ACS shall have to ability to import Identity records and their associated image in a standard jpeg format.

a. Identity records shall be able to be pre-loaded prior to implementation or added at any time after deployment.

4. The ACS shall provide a pre-configured one-time import utility, using standard Comma Separated Value (.csv) files that shall allow the import of Identity information based on the factory shipped data fields.

5. Identity Enrollment - The ACS shall allow individual enrollment of identities. Each Identity shall allow entry of required and optional fields.

a. For identities that have access to the ACS application, the following security parameters must be defined during the enrollment process

1) User account,

2) Account password,

3) Non-activity timeout. 6. The ACS shall use Role Base Permissions.

a. Roles shall be assigned during enrollment.


b. Identity’s role shall determine their Access Groups

1) Which card readers they have access,

2) Which times access to those card readers is allowed. 7. A Token shall be created and assigned during enrollment.

a. For each Token, credentials shall include, but not be limited to:

1) a Badge ID

a) A minimum of a 19 digit Badge ID shall be supported

2) Embossed number as required.

3) PIN code shall be assigned as required.

4) Activation and deactivation date

5) Associated settings for anti-pass back as required

b. Optional credential parameters shall include, but not be limited to:

1) Adding token to a Group during enrollment.

a) A Group may have predefined Role and Policy Settings that will drive the configuration of the Identity information.

2) Expiration of the credential due to non-use. The Credential can be set to expire if not used within a certain timeframe. The parameters shall include, but not be limited to:

a) System wide for every credential

b) Variable parameters per individual or access level

c) Individual or access levels can be exempt from expiration

d) Scheduled time for expiration do to non-use shall be at least 1 year from date of activation.

8. During Enrollment, the Identity’s image shall be captured or loaded in from a JPEG file format and a badge template shall be assigned.

9. The ACS shall allow credential suspension if the card certificate serial number is on a designated list, including, but not limited to:

a. Certificate Revocation List (CRL)

b. If the FASC-N is on TSA Canceled Card List (CCL). 10. Credential Re-Issuance -

a. The Operator shall be able to deactivate the existing credential by marking it 1) Lost, 2) Stolen, 3) Etc.


b. The ACS shall be able to use the existing Identity information and photo for the new credential,

1) The process shall not require re-enrollment of the credential holder. c. The re-issuance process shall automatically

1) Remove access rights from the deactivated Token 2) Enable those same rights in the new Token; 3) Automatically send the appropriate changes to the Intelligent Enterprise

Controllers. 11. Identity Database - Each Identity shall have a unique record in the Open LDAP directory

structure.

a. LDAP Directory Structure must include the use and definition of User Defined Fields and Forms.

12. Deleting Identities – Highest level administrators shall be given the ability to:

a. Delete Identities.

b. Bulk Delete Identities - the ability to delete a group of identities

1) Based on a user defined search set. 13. Assign Access Groups - The ACS shall allow Administrators to assign Access Groups to

Roles.

a. A Role shall then be assigned to an Identity during enrollment.

b. Each Identity may have up to 8 Access Groups assigned to their record per Intelligent Enterprise Controller through the assignment of one or more Roles to their record.

14. Access Groups Modifications or Assignments shall be automatically downloaded to the appropriate Intelligent Enterprise Controllers

a. Without Operator intervention

b. Completed as a “push communication” immediately after an Identity record is saved. Scheduled, batch updated are not accepted.

15. The ACS shall support an Access Group View form that allows Operators to view

a. All Roles that have been assigned to an Identity,

b. Which Access Groups are associated with the Role

c. What doors in which an Identity has access. 16. Roles - The ACS shall support a Role Based permission methodology to be used in

conjunction with Identities.

a. Roles shall be assigned to Identities to determine door access as well as access into the system application.


b. Multiple Roles shall be able to be assigned to an Identity.

1) A Parent/Child relationship can be defined, per Role.

2) Duplicating Role information for multiple roles shall not be required c. Identities shall aggregate all Role assigned permissions.

d. Each Role shall have a defined start and stop date

1) To allow assignment of Roles on a temporary basis.

2) Roles can be manually activated or deactivated through the use of a checkbox. e. Each Role shall consist of any combination of the following components that shall

determine which Roles an Operator shall be able to assign to other Identities during enrollment:

1) Access Groups,

2) Delegation Assignments,

3) Role Assignments. 17. Image Capture Device - The ACS shall support IP based cameras for Photo Capture.

a. The Operator shall be able to view a live image on screen of the Identity to move them into a proper pose or position prior to freezing the image.

b. If the Operator is not satisfied with the captured image, they shall be able to revert to a live view and freeze a new image.

c. Configuration settings for IP cameras, as well as viewing a live and still image of a person shall be user configurable.

18. Photo Capture - The ACS shall support Photo Capture through used of an IP based camera.

a. The Operator shall be able to view a live image on screen of the Identity to move them into a proper pose or position and then be able to freeze the image.

b. If the Operator is not satisfied with the captured image, they shall be able to revert to a live view and freeze a new image.

19. Additionally and optionally, the ACS shall support the ability to import industry standard JPEG photos from digital cameras or other image capture sources.

20. The ACS shall allow the captured photo to be cropped via use of the mouse to define the crop window. Only information inside the crop window shall be saved and stored in the directory structure. a. Images shall be associated with the Identity and shall be stored in the OpenLDAP

directory.


21. Token Activation and Deactivation Dates - The ACS shall support activation and deactivation dates for all Tokens created.

a. A Token shall have the ability to be configured to activate at a future date from time of creation.

b. When a Token reaches its deactivation date/time, the ACS shall automatically deactivate the access rights associated with the Token.

c. All access rights of a Token shall be eliminated after the deactivation date.

d. Should the Identity become authorized for access again, new access rights shall be applicable to the same Token, and re-issue shall not be required.

e. Expiration of the credential due to non-use. The Credential can be set to expire if not used within a certain timeframe. The parameters shall include, but not be limited to:

1) System wide for every credential

2) Variable parameters per individual or access level

3) Individual or access levels can be exempt from expiration

4) Scheduled time for expiration do to non-use shall be at least 1 year from date of activation.

22. Token Audit Trail - The ACS shall keep an on-line record of all Tokens issued to an Identity.

a. For each record, details will be recorded including activation and deactivation dates, Token status, and Token ID.

23. Token Issue Codes - The ACS shall support a minimum of a 2 digit issue code.

24. PIN Codes - The ACS shall support up to 8 digit PIN codes.

a. Each credential holder in the ACS shall have the ability to choose a PIN to be associated with their record.

b. A credential holder’s PIN shall have the ability to be changed should the original PIN code be compromised.

c. An Identity shall be able to be exempted from PIN requirements within the system.

25. Credential Options - The ACS shall support industry standard pre-encoded physical credential options including:

a. Composite Credentials such as PVC cards

b. Proximity Credentials including dual PVC technology that includes both proximity and magnetic stripe technology

c. Contact Smart Credentials


d. MiFare Credentials

e. DESFIRE Credentials

f. HID iClass Credentials

26. Last Access Information - A credential holder’s last entry point

a. shall be displayed on the main Identity form

b. Along with a date/time stamp for when entry occurred. Additionally, for

c. If a credential holder has multiple Tokens, the Tokens form shall also show the last entry point with date/time stamp for each Token in a credential holder’s possession.

27. Last Identity Record Modification - The ACS shall display the date and time of the last modification to that Identity record from the main Identity form.

28. Search Capabilities - The ACS shall have the ability to search Identities by a. First Name, b. Last Name c. By Identity d. By Token field in the system.

29. The ACS shall allow multiple field based identity / token searches using AND / OR logic. Filters shall include, but not be limited to: a. Equals, b. Starts With, c. Ends With, d. Contains.

30. Pick List Builder - The ACS shall include a Pick List builder that allows Administrators to define Operator selection options that appear in Identity form pick lists. Each pick list shall have an unlimited number of pre-defined selections.

31. The ACS shall support the standard identity and Token fields: a. Last name b. First name c. Middle Name d. External System ID e. Address f. City g. State h. Zip i. Phone j. Work Phone k. E-mail Address l. Title m. Department n. Division o. Site Location


p. Building q. Last record Modification r. Status s. Type t. Issue date u. Login v. Password w. Password Confirmation x. Inactivity Timer y. Last Door Accessed z. Last Time Accessing Last Door aa. Photo bb. Embossed Number cc. Internal Number dd. PIN ee. Token Status ff. Issue Level gg. Activate Date hh. Deactivate date

32. Transaction Activity - The ACS shall provide a form listing the most recent transaction activity associated with an Identity, without having to run a report. Information provided shall include

a. transaction activity b. time/date c. Related token.

33. User Defined Fields - The ACS shall support the ability to add additional Identity Based forms to support User Defined Fields.

a. Up to 10 User Defined Forms shall be able to be added.

b. Each user defined field shall be given a Field Name/Label and be defined as one of the following field types: 1) String, 2) Integer, 3) Boolean, 4) Date.

c. Up to 300 User Defined fields shall be available. 34. Badge Layout Tool - The ACS shall support a tool to allow for the custom creation of

Identity/Token Badge Layouts.

35. The ACS shall support any size badge provided the printer used for badge creation supports the desired badge size.

36. The ACS shall allow multiple objects to be configured for a badge layout including a. alphanumeric text fields,


b. database fields, c. photos, d. Identity photos, e. Graphics (i.e. logos).

37. Each text and database field added to the layout shall have the ability to employ the following properties; a. Location of the object, b. Height and width, c. Background color, d. Rotation, e. Typeface of text, f. Size of text, g. Color of text, h. Horizontal and vertical alignment of text.

38. Each Photo and Graphic field added to the layout shall have the ability to employ the following properties; a. Location of the object, b. Height and width, c. Maintain aspect ratio. d. The ACS badge layout tool shall support a color palette that supports a minimum of

16.7 million colors that can be applied to applicable objects.

E. Alarm and Event Monitoring

1. Tabbed User Interface - The ACS shall support a tabbed view for the Monitor User Interface. The following tabs shall be supported:

a. Event Monitor shall be used to monitor system level events such as Operator activity and field level events.

b. Alarm Monitor shall be used to monitor field level events such as Identity access activity, input alarms, and door alarms as well as system level events configured as alarms.

c. Swipe and Show Verification shall be used to view Identity information in real time as credential holder’s access specific doors.

d. Search shall be used to search up alarm and event transactions currently stored in the ACS.

e. Hardware Status shall be used to view the real time status of field hardware devices configured in the system, as well as to manipulate/override those devices.

2. Alarm Annunciation - The ACS shall allow Administrators to configure how alarms and events annunciate into the Alarm Monitor.


a. Support audible notification at the workstation when alarms arrive in the system.

1) Users shall have the ability to adjust the configuration and parameters.

2) Administrators shall be able to choose a specific sound to pair with each type of alarm.

3. Each alarm and event shall have the following configuration options:

a. Display in the Alarm Monitor.

b. Be masked from displaying in the Alarm Monitor.

c. Allow higher alarms to be displayed on top of the alarm monitor when an Operator sorts based on alarm priority.

d. Display Text Instructions that shall guide the Operator in alarm response.

e. Automatically send an email message to one or more recipients.

f. For Video related alarms and events, automatically launch the Video Player to display a live video feed from the camera that is associated with the generating alarm or event.

4. Alarm Management and Handling - The ACS Alarm Monitor shall provide a real time count of all alarms and events in the Alarm Monitor awaiting Operator action.

5. The ACS shall support the following options for handling / responding to alarms and events upon selection:

a. Acknowledge the alarm.

b. Review text instructions on pre-defined alarm response.

c. Enter unlimited Notes on reason for alarm and/or action taken in alarm response.

d. Review the History of the alarm.

e. For alarms and events that include a credential holder, call up the Identity Record of that credential holder.

f. Clear the alarm.

6. Bulk Alarm Management and Handling - The ACS shall support the ability to manage and handle multiple alarms.

a. Operators shall have the ability to clear or acknowledge all selected alarms in a single action.

7. Alarm Routing – The ACS shall allow Identity based alarm routing that shall route alarms to specific Identities monitoring the application based on

a. Schedule,


b. Event type,

c. Device. 8. Alarm Masking - The ACS shall allow masking of specific alarms or alarm types based

on pre-defined Schedules or via manual overrides.

a. Masked alarms shall not report into the Alarm Monitors

b. Logging the transaction database for reporting and audit trail shall not be effected by Masked status.

c. An Operator shall have the ability to mask or unmask any alarm point in the system based on permissions.

9. Alarm Sorting - The ACS shall allow alarms and events to be sorted in the Alarm Monitor by any of the currently configured viewable columns.

10. Alarm Prioritization Color Bars - The ACS shall provide the capability to emphasize alarm priority through the use of colored bars within the alarm monitor screen.

a. Each alarm priority shall have its own unique user-defined color assigned to it.

b. Color bars shall also have the ability to be assigned to individual alarm priorities or to a range of alarm priorities.

11. Column Configuration - The ACS shall allow Administrators to define which columns are displayed in the Alarm Monitor.

a. Administrators shall also be able to set the column order of the Alarm Monitor. Columns available for configuration shall include: 1) Time 2) Last Access 3) Token Expire Date 4) Token Issue Date 5) Panel Date 6) Priority 7) Operator 8) Identity First Name 9) Identity Middle Initial 10) Identity Last Name 11) Card Number 12) Embossed Number 13) Message 14) Event Name / Description 15) Event Type 16) Panel 17) Source 18) Location 19) Alternate Source 20) Input Address 21) Event Address


22) Source Type 23) Flags 24) Status 25) Issue Level 26) Role

12. E-Mail Capabilities - The ACS shall support integrated e-mail capabilities.

a. The ACS shall be able to generate an email message to send to one or more recipients upon a generated alarm or event.

b. The e-mail function shall interface with any E-mail Server that uses SMTP as its protocol.

13. Event Monitoring - The ACS shall support an Event Monitoring tab that shall be used to monitor system level events such as Operator activity.

a. An Operator shall be able to choose which field columns to display and shall be able to place those columns in their order of preference.

b. The Operator shall also be able to sort the events by any currently displayed column in the Event Monitor.

c. Administrators shall have the ability to configure the number of recent events to display in the Event Monitor upon accessing the Events tab.

14. Field Hardware Device Status Summary Counter - The ACS shall support a real-time Field Hardware Device Status Counter displaying a summary of the total number of Doors, Input Points, Intelligent Enterprise Controllers, and Sub Panels that are active, masked, and off-line.

15. Field Hardware Device Status Tab - The ACS shall support real-time system status that depicts all field hardware devices configured.

a. The real-time system status tab shall list

1) Intelligent Enterprise Controllers,

2) Input Control Modules,

3) Alarm inputs,

4) Relay outputs,

5) Card readers.

6) The hardware status shall show the real time status of all these devices (on-line vs. off-line, alarms activated, masking status, etc.).

16. The Hardware Status tab shall display all hardware devices separately in their own row. The following shall exist in the tab:

a. Device Name


b. Intelligent Enterprise Controller / Input Control Module / Output Control Module Name

c. Current Device Status

17. The ACS shall also allow Operators to affect the access mode of card readers, open doors, mask/unmask alarm inputs, and activate/deactivate/pulse an output from the tab. The ACS shall also allow Operators to affect the access mode of multiple devices with a single action by selecting multiple devices and then performing the command.

18. The ACS shall support integration with Life Safety Power’s N1 network module. When configured, the LSP power supply link shall appear in the Field Hardware Device Status tab and when the link is clicked, the N1 diagnostic and configuration window shall appear.

19. History Record Call-up - The ACS shall support the ability to call up the history of an alarm. The History call up window shall display the associated alarm information including time/date stamp, acknowledgement actions by Operators, and entered Notes. The Operator shall not be required to exit the Alarm Monitor to access this information and this functionality shall not prevent additional alarm activity from reporting to the Alarm Monitor.

20. Identity Record Call-up - The ACS shall support the ability to call up the Identity Form to display the Identity record associated with an alarm.

a. The Identity call up window shall display the Identity’s information and photo. The Operator shall not be required to exit the Alarm Monitor to access this information and this functionality shall not prevent additional alarm activity from reporting to the Alarm Monitor.

21. Operator Control of Field Hardware Devices - The ACS shall allow Operators to manually control the state of field hardware devices and their input/output points from the Alarm Monitor.

a. Card Readers

1) Manually control reader state or Based on current schedule a) Unlocked b) Locked c) facility code d) card only e) PIN only f) card and PIN g) card or PIN h) pulse the door open, i) mask/unmask j) door forced opens/door held opens,


k) disable the door, l) restore the door to its correct state m) Inputs – mask and unmask input

b. Outputs –

1) Manually control reader state or Based on current schedule a) Turn on, b) Turn off, c) Pulse outputs.

22. Field hardware devices shall be available for Operator control from the Hardware Status tab.

23. The ACS shall utilize a last command wins methodology. For example if an output is set to off due to a schedule and an Operator manually turns it on, then the output will remain on until it is manually turned off or until the next scheduled interval occurs.

24. All manual controls shall be recorded in the Operator Audit log with the time of the change, Operator performing the function, and description of the activity performed.

25. Maps - The ACS shall support graphical maps through the import of map backgrounds from standard “off-the-shelf” drawing packages in the formats listed below: a. Bitmaps (.bmp, .dib) b. JPEG (.jpg) c. Portable Network Graphics (.png) d. TIFF (.tif) e. Windows Metafile (.wmf, .emf)

f. Encapsulated Post Script(.eps)

26. The ACS Administrator shall have the ability to place system icons including card readers, input & output points, video cameras, and other access control field hardware to indicate their location in the facility.

27. Zoom capabilities shall be available to provide closer or farther views of the area. From the Map, operators shall be able to: a. Acknowledge an alarm b. Change the Access Mode of Readers c. Mask/Unmask Inputs d. Pulse, Set ON/OFF of Relay outputs e. Launch a Video “Window”


28. System Status Indicators - The Alarm Monitor shall provide status indicators to display the current status of multiple elements of the ACS including:

a. Total number of pending Unacknowledged Alarms and Events

b. Status of all field hardware devices (Intelligent System Controllers, subpanels, card readers, inputs, and outputs) including off-line, active, and masked.

c. The hardware status tab will show all devices that are in alarm as well as the on-line /off-line status for all field hardware devices.

29. Swipe and Show - The ACS shall support Swipe and Show functionality that allows the display of the credential holder’s photo as they swipe their badge through a specified card reader.

a. Up to four card readers shall be active for swipe and show in each browser window.

b. Swipe and show allows Operators to verify the credential holder to their photo as they enter a portal.

F. System Configuration and Administration

1. Alarm and Event Logging - The ACS shall track and keep a comprehensive log of all alarm and event activity. All alarms and events that occur shall be logged with the following information: a. Alarm Name b. Time and Date Stamp c. Where the alarm occurred d. Acknowledgement information e. All Operator actions associated with the alarm or event

2. Administrators shall be able to suppress certain alarms from logging during pre-defined scheduled times of the day.

3. Alarm and Event information can be viewed through the ACS reporting engine that shall list the total number of alarms and events that are logged in the ACS Appliance.

a. The number of stored alarms and events shall be limited only by the amount of disk space available in the ACS Appliance.

4. Operator Session Timeout / Logout - The ACS shall support an Auto Logout feature that shall allow the system to automatically log an Operator out of the system after a period of inactivity. Auto logout timeout choices shall include a. 10 minutes b. 15 minutes c. 30 minutes d. 60 minutes


e. 1 hour. f. Indefinite - A selection shall be available to not log out an Operator regardless of

inactivity length.

5. Delegations - All major ACS features and functions shall be permission protected through the use of delegations.

a. Each Operator Account shall be assigned a Role, which shall include a list of delegations assigned to that Role.

b. Operator access to ACS screens, as well as their ability to view, add, edit, or delete ACS objects shall be controlled though delegations.

6. Software Based Licensing - The ACS shall support a software based License Enforcement model.

a. A hardware key or dongle shall not be acceptable for controlling licensed features and functionality.

7. ACS Appliance Diagnostic Information - The ACS shall support the ability to analyze real time diagnostic information for each ACS Appliance by viewing the About Page for the appliance. Diagnostic data shall include a. Number of days online b. Current load c. Memory d. Disk space usage e. Network communications data.

8. On-Line, Context Sensitive Help - The ACS shall support on-line, context sensitive help to assist system users in the operation of the system.

a. Once inside the help program, users shall be able to navigate the help files, moving to other areas of the documentation with having to go back into the application software.

b. The Help files shall have a linked table of contents, index, and search capability.

9. Operator Accounts - The ACS shall support Operator Accounts.

a. Each Operator Account shall require a unique user name password to access the system.

b. Each Operator Account shall also be assigned a Role, which shall determine the permission level for that account, thus controlling what functions the Operator can perform in the system.

c. All modifications to an Operator Account shall be reported to the Event Monitor and logged to the LDAP directory structure for audit and reporting processes.


d. The ACS shall support as many Operator Accounts as configured identities.

10. Password Protection - Each Operator Account shall require a unique user name and password that would tie that identity to delegation rights to access the ACS.

a. This denotes Operator access to:

1) Screens the Operator can access

2) Tasks the Operator can perform.

b. An Operator shall be able to change their ACS password at any time.

c. Strong Password parameters shall be supported.

1) Requiring system users to enter at least 8 characters

2) Include at least one upper case letter, one lower case letter and one numeral 11. Policies - The ACS shall support Policies that shall act as templates to be applied to field

hardware devices in the system to ease in configuration of similar devices.

a. Each Policy shall consist of a template for card readers, inputs, or outputs.

b. The ACS shall support an unlimited number of policies.

12. Groups - The ACS shall support Grouping of parameters for ease of configuration. Grouping concepts should include, but not be limited to:

a. Roles,

b. Field Hardware Devices,

c. Policies. 13. System Partitioning - The ACS shall provide the capability for advanced system

partitioning.

a. Each partition shall be allowed its own group of identities, field hardware, and parameters such as schedules and access groups.

b. Identities shall be allowed to belong to one or multiple partitions.

c. Partitioning shall provide a flexible “tenant/landlord” architecture whereby partition users can only view, add, modify, and delete identities, system parameters and field hardware that belong to their respective partitions.

d. ACS operators may be assigned to more than one partition. A partition may be assigned to more than one operator.

14. Operator Activity Logging - The ACS shall track and keep a comprehensive log of all Operator Account activity. All changes that occur in the directory structure shall be logged including, but not limited to:

a. Operator Account Login / Logout Activity.


b. Adding, Deleting, or Changing Identity Records.

c. Change to system configurations to include, but not limited to field hardware, Access Groups, or Schedules.

d. Activity performed inside the Alarm and Event Monitor, to include but not limited to acknowledging alarms, opening doors, or clearing events.

15. The logged activities shall include, but not be limited to: a. Operator Account. b. Date and time of the activity. c. Activity that was performed. d. Original data prior to change, if applicable.

e. New data that was updated.

16. The Operator Account activity information can be viewed through the ACS reporting engine that shall list the total number of Operator events that are logged in the ACS Appliance.

a. The number of stored Operator Account events shall be limited only by the amount of disk space available in the ACS Appliance.

17. System Scheduler Utility – The System Scheduling Utility shall allow System Administrators to schedule actions

a. On Demand or Single Use

b. Recurring basis.

c. The types of actions include, but not limited to running reports.

d. The Scheduling Utility shall satisfy a wide range of scheduling needs, including, but not limited to:

1) Hourly – i.e. “Every day on the hour”,

2) Specific Day, specific time – i.e. “every Monday at 8:00 am”,

3) Monthly – i.e. “the first Sunday of every month”, etc.

4) Specific Recurring Date – i.e. “Every February 29th @ noon”

5) Specific Date in the future – i.e. “December 7, 2017 @ 5pm”

6) Recurring activities shall have

a) a master start and stop date or

b) set to run indefinitely

18. The Scheduling Utility shall provide a job monitor allowing the System Administrator to:

a. See the status of currently running tasks


b. See a chronological list of future scheduled tasks

c. See a history log of completed tasks 19. Reports - The ACS shall support a minimum of 19 standard reports.

a. Reports shall have the ability to be created as a: 1) PDF document 2) Spreadsheet format, 3) Both depending on the report.

b. Once generated, the report shall 1) Be able to be saved to a file 2) Printed to a local or networked printer. 3) Both depending on report

c. Each report shall have the ability to be customized / filtered on relevant data for that particular report.

d. Standard ACS reports shall include:

1) Access Grant Audit Report – The Access Grant Audit Report shall present information on all access grant activity that was manually generated by an Operator and shall include the door that was opened, time, and Operator executing the door grant.

2) Access Group Report - The Access Group Report shall present information on all defined ACS Access Groups, including but not limited to: a) which Roles are assigned to the Access Group, b) the Schedule assigned to the group, c) the number of doors assigned to the group, d) List of the doors assigned to the group.

3) Alarm Report – The Alarm Report shall present information on all alarms that occurred in the system including Panel Name, Operator action taken, Operator responding to the alarm, and any Operator Notes entered pertaining to the alarm

4) Appliance (ACS) Report - The Gateway Report shall present information on each defined ACS Appliance, including: a) ACS Appliance type, b) DNS Name and Domain, c) Local Time Zone and Daylight Savings Time Settings, d) Listing of field hardware manufacturers are enabled,

5) Listing of Intelligent Enterprise Controllers has been configured to report to the panel.

6) Area Report - The Area Report shall present information on all defined Areas. Each Area entry shall include area name, ACS Appliance where the area exists, and doors assigned to the area.

7) Audit Log Report - The Audit Log Report shall present information about each change made to the ACS by an Operator. Each Audit log entry shall include:


a) A date/time stamp, b) Description, c) The Operator who made the change, d) The type of change, e) The details of the change, f) What the changed information was prior to the change (if any).

8) Camera Report – The Camera Report shall present information on each camera configured in the system including Camera Name and its attributes.

9) Collaboration Report - The Collaboration Report shall present information on all defined ACS collaboration scripts, including collaboration type and if the collaboration is active.

10) Delegation Report - The Delegation Report shall present information on all defined ACS delegation groups, including which identities have been assigned to the delegation and what permission have been configured for that delegation.

11) Door Access Report - The Door Access Report shall present information on credential holder access to each door in the ACS, including the schedule that the credential holder can access the door.

12) Door Configuration Report - The Door Configuration Report shall present information on the complete configuration / settings of each door configured in the ACS.

13) Event Report - The Event Report shall present information on defined events in the system along with their attributes including a) Event Name, b) Assigned Event Type, c) Priority, d) Masking Schedule, e) If the event is configured to always mask and/or log the event.

14) Event Type Report - The Event Type Report shall present information on each defined ACS Event Type, including a) Suppression Schedule, b) Priority, c) Retransmission Time, d) Retransmission Procedure, e) Procedure, f) If the Event Type is set to be masked, logged, and/or sent to the Alarm

Monitor.

15) Group Report - The Group Report shall present information on all defined Groups, including Group Name, Type, and Members information such as card readers and Roles.

16) Holiday Report - The Holiday Report shall present information on each defined ACS Holiday, including the date of the holiday, number of days the holiday is in effect and the holiday type(s) assigned to the holiday.


17) Identity Access Report - The Identity Access Report shall present information on each defined ACS Identity with respect to which ACS doors they have access. The report shall include the schedule in which access has been granted to each reader as well as the Access Group and Role assignments that allow access to each reader.

18) Identity Summary Report - The Identity Summary Report shall present information on each defined ACS Identity with respect to Identity Status and Type, Token(s) issue and expiration date, and which Roles and Access Groups have been assigned to the Identity.

19) Panel Report - The Panel Report shall present information on the complete configuration/settings of each Intelligent Enterprise Controller configured in the ACS.

20) Policy Report - The Policy Report shall present information on all defined policies in the ACS, including a) Policy Name, b) Active Status, c) Which hardware components the policy encompasses.

21) Role Report - The Role Report shall present information on each defined ACS Role, including a) Parent information, b) Activation/deactivation dates, c) Child Roles, d) Identities assigned to that Role, e) Access Groups assigned to that Role, f) Doors assigned to that Role.

22) Schedule Report - The Schedule Report shall present information on each defined ACS Schedule, including its mode and each interval configured a) Days of the week, b) Holiday types c) Start and end times of the interval)

23) Token Report – The Token Report shall present information on all tokens in the system including token number, identity to whom the token is assigned, and active / de-active status.

24) Transaction Report - The Transaction Report shall present information on each ACS transaction generated at the field hardware level. Each transaction log event shall in include a) Date/time stamp, b) Event Source, c) Event name and type, d) Identity and Token information.

25) Quick Reports - The ACS shall support Quick Reports.


a) Each of the standard reports defined in the Reports section shall have the ability to have relevant data filters applied to them, prior to running, in order to provide a report with more specific information than the generic report. Quick Report settings shall be designed to run once and shall not be saved.

b) Quick reports shall have the ability to output their results to a PDF file format or to a spreadsheet file format.

26) Custom Reports - The ACS shall support Custom Reports.

a) Each of the standard reports defined in the Reports section shall have the ability to have relevant data filters applied to them, prior to running, in order to provide a report with more specific information than the generic report.

b) Custom Reports shall be designed to run multiple times and shall be saved in the Custom Reports form for fast future execution.

c) Custom reports shall have the ability to output their results to a PDF file format or to a spreadsheet file format.

d) Each Custom Report shall be given a unique name to identify it in the Custom Reports list.

20. Remote Support - The ACS shall allow Remote Support Capability to allow VAR or Manufacturer, based on Customer permission, to access Customer’s ACS Appliance for:

a. Troubleshooting, b. Diagnostics, c. Load review, d. Assistance with configuration.

21. ACS shall offer the ability to obtain software log data out of the system ACS Appliance Logs for further application support.

22. Grid Based Replication - The ACS shall support automated grid based replication architecture of the ACS Appliance directory structure for customers that deploy multiple ACS Appliances.

a. The replication architecture shall be peer-to-peer and not require a dedicated database server to enable replication of identities and configuration data across ACS Appliances.

b. The ACS shall support encrypted communications between ACS Appliances using SSL Encryption.

c. Replication shall allow the LDAP data of all ACS Appliances to be synchronized with each of the others in the system, allowing for a ACS Appliance to rebuild itself from replicated data found on another ACS appliance found in the system.

23. Hot Standby Functionality - The ACS shall support a hot standby, auto-failover architecture.


a. For each ACS Appliance, a Hot Standby Appliance shall be configured to monitor the status of its primary partner device.

b. Should a ACS Appliance fail to function, the hot standby ACS Appliance shall be able to automatically detect a problem and assume control of the system.

24. Software Updates - The ACS shall support updates via downloading from the manufacturer web site, or receiving via email the update files.

a. No physical interaction with the ACS Appliance shall be required to perform a successful update or upgrade to the system software.

25. System Backups - The ACS shall have the ability to backup and restore the LDAP directory structure.

a. Backups shall run concurrently with the rest of the system and shall not require all Operators to log out of the ACS.

b. Backups shall include transaction data and system configuration data.

c. ACS Appliance backups be encrypted using AES Encryption.

d. ACS Appliance backups to 1) USB Storage Device, 2) Windows shared Directory or network shared folder, 3) Secured SCP servers.

e. Backups shall have the ability to 1) Run automatically on a predefined daily schedule. 2) Manually via the GUI

26. Hide Main Menu Icon Pane - The ACS shall include a Show/Hide button that toggles the view of the Main Menu Icon Pane.

a. When hidden, additional screen space shall become available.

27. Elegant Restart and Shutdown of Appliance - The ACS shall support Elegant Restart and Shutdown capabilities of the Appliance.

a. Buttons shall be available in the User Interface to both re-start and shutdown the Appliance.

b. Rights and access to those buttons shall be denoted by login. 28. European Time Display – The ACS shall support a European time display (dd/mm/yyyy)

in addition to the traditional format (mm/dd/yyyy).

29. System Data Logs - The ACS shall support system data logs to assist with diagnostics and troubleshooting.


a. Standard logs shall include web server logs, field hardware communication logs, system software logs, and system transaction logs.

b. All logs shall be viewable in a plain text format.

G. Video Management System (ACS) Integration

1. Integration with Netowrk Video Servers - The ACS shall support digital video integration with digital video servers including but not limited to:

a. Avigilon

2. LAN/WAN Connectivity - The ACS shall support connectivity for streaming live video of a camera or for reviewing stored recorded video of alarm or event activity in the Alarm Monitor across datacom networks including but not limited to: a. LAN/VLAN/WLAN (Local Area Network/Virtual LAN/Wireless LAN) b. WAN (Wide Area Network) c. MAN (Managed Area Network) d. VPN (Virtual Private Network)

3. Device Association - Each access control field hardware device that is configured in the ACS shall have the ability to be associated with a camera from the VMS.

a. An unlimited number of device associations shall be possible.

b. A camera shall have the ability to be associated with multiple access control hardware devices.

c. An access control hardware device shall have the ability to be associated with multiple cameras.

d. Where multiple cameras are associated to a single access control hardware event or alarm, all associated cameras shall appear in the video player in the appropriate matrix view.

4. Pre-Roll and Post-Roll Marking of Event Based Video - When an alarm triggers, the ACS shall notify the VMS to mark a pre and post roll time for the associated recorded video clip.

a. Pre-Roll shall be the number of seconds of video that the VMS will store previous to the event time.

b. Post-Roll shall be the number of seconds of video that the VMS will store after an associated event is generated.

c. The pre and post roll times shall be configurable up to 100 seconds.

5. Stored Video Events - Each alarm / event condition shall have the ability to mark the start of a video event or the end of a video event in real time. For example, when a door held open is activated, the VMS shall mark the start of the video event. When the alarm restores, the VMS can mark the end of the video event.


6. VMS Event Reporting - The ACS shall support following incoming VMS events:

a. Panel Offline/NORMAL Panel Offline. This event shall report connection losses and restores of the digital video servers]

b. Motion Detection / No More Motion Detected. This event shall report motion events from cameras on the VMS.]

c. Video Loss / Video Restored. This event shall report connection losses and restores of analog cameras connected to the VMS.]

d. Connection Loss / Connection Restored. The event shall report connection losses and restores of IP Cameras connected to the VMS server.]

7. Video Recall - Upon generation of an alarm that has associated video, the Operator shall be able to recall the video segment associated with the alarm.

a. Once launched, the Operator shall have the ability to adjust the start and end time of the video segment.

8. Video Player - The Video Player shall support a Matrix View for On-line cameras.

a. The number of video windows in the matrix shall be dependent on the frame rate and resolution of the cameras / number of video clips viewing.

b. The Matrix view shall allow sizing the matrix windows.

c. The ACS shall provide the ability to launch more than one camera on a generated alarm.

1) When an alarm with multiple cameras is generated, a matrix window shall launch displaying all associated cameras.

2) The Operator shall also have the ability to switch between other cameras if the device that generated the event has more than one camera associated with it.

d. Operators shall be able to concurrently playback recorded video from any clip, even as that video clip is being recorded.

e. The Operator shall have the option to switch to Live Mode from a camera at any time during the operation.

f. The digital video player shall show the date and time of the video clip frame, as well as the current mode of the player (play or live).

g. Playback Control - The ACS shall provide the following playback controls for viewing recorded video: 1) Start and Stop Playback - The Operator shall be able to start and stop playback.

2) Pause and Resume - The Operator shall be able to pause and resume current playback.

3) Play in Reverse - The Operator shall be able to reverse video in normal speed.


4) Skip Backward - The Operator shall be able to use the Skip Backward button to rewind the playback.

5) Frame Advance - The Operator shall be able to use the Frame Advance button to advance the video clip one frame at a time.

h. Auto-Launch of Video Player - Any alarm / event generated shall be configurable to automatically launch the Video Player in the ACS Alarm Monitor.

9. Pan/Tilt/Zoom Command Functionality - The ACS shall support pan / tilt / zoom (PTZ) controls from the Alarm Monitor. Supported command settings shall be available for: a. Pan Left b. Pan Right c. Tilt Up d. Tilt Down e. Zoom In f. Zoom Out g. Focus Near h. Focus Far i. Iris Open j. Iris Close k. Go to Preset l. Stop PTZ Movement

10. Go-To PTZ Presets on Alarm - The ACS shall support pre-defined PTZ presets that are executed based on alarm generation.

a. Each event/alarm in the ACS shall be able to be assigned to a PTZ preset on the associated camera.

b. Upon alarm generation, the associated camera shall automatically pan, tilt, and/or zoom to its pre-configured location.

11. Video Motion Detection Alarms - The ACS shall report video motion detections alarms such that

a. When a monitored camera senses motion in its range of site, it will report a “Motion Detection” alarm to the ACS Alarm Monitor.

b. When the camera no longer senses motion, it will report a “Motion Detection Restored” alarm to the ACS Alarm Monitor.

12. Video Motion Detection Event Smoothing - The ACS shall allow Video Motion Detection Event smoothing that shall assist in eliminating the generation of multiple motion detection alarms due to an object repeatedly and quickly entering and exiting a camera’s field of view.

a. Administrators shall be able to set a time period from when an initial motion event is restored, that no other video motion is detected before reporting the alarm.


b. If motion is detected during the smoothing time, the ACS shall wait for the motion to subside, then again wait for the configured smoothing time to expire without new motion before reporting the alarm.

13. Video Motion Detection Event Masking - The ACS shall have the ability to mask video motion detection events on a per camera basis.

a. Each camera shall have the ability to be assigned a schedule; during which video motion detection events generated by that camera shall be masked.

14. Off-line Alarms - Should a VMS Server or any associated cameras go off-line, a specific alarm shall be sent to the ACS Alarm Monitor.

15. Still Image View - During playback of recorded of video, the Operator shall use the Pause button to create a still picture. This operation shall not affect any other operation and shall not alter the recorded video.

16. Video Icons - The ACS shall support video icons. Alarms that enter the Alarm Monitor generated by a device that has an associated camera shall display an icon next to the alarm to alert the Operator that video is associated with the alarm.

17. Video Server / Video Camera Status Listing - The ACS shall support a status listing page that shall list the connection status of all configured video servers and cameras.

18. Video Delegations - User defined delegations shall restrict each Operator’s security access to specific system operations, such as video monitoring and associating cameras to devices.

H. 3rd Party Collaboration

1. The ACS shall support a Collaboration utility that shall allow for real-time or scheduled transfer of information, including images and events, between the ACS and 3rd party IT, Security, and other systems.

2. A user interface shall allow for the generation of import and export collaborations. A Start and Stop date shall be applied to run the Collaboration during the scheduled intervals only between certain dates.

3. The ACS shall support a minimum of 32 Collaborations per ACS Appliance.

4. The ACS shall support the following Collaboration Types: a. Identity LDAP Pull b. Identity Oracle RDBMS Pull c. Identity LDAP SQL Server Pull d. Events push to ArcSight CEF e. Events push to Splunk f. Events push to Syslog g. Events push to SNMP h. Events push to Milestone Video


i. One Time Import of Identity Records Using Factory Shipped Fields 5. Identity Pulls - Identity Pull Collaborations shall allow Identity, Token, and Role related

data to be imported into the system directory structure. Importing of information shall occur in the following method:

a. Add/Modify - If a record in the file exists in the directory structure, it shall be replaced according to the layout configuration specified.

b. Records that don’t already exist shall be added to the directory structure.

6. Identity Pull Collaborations shall support BLOB image file formats to be imported into the OpenLDAP directory structure.

7. The ability to encrypt the exported Identity information shall be available using SSL encryption.

8. Each collaboration shall utilize an error log that shall report all errors that occur during a file import. Any and all errors can then be viewed from this log and once corrected the import may be run a second time to download the corrected records.

9. As a Collaboration Pull completes, imported changes shall be automatically downloaded to Intelligent Enterprise Controllers on a real-time basis as information is being imported into the directory structure.

10. Event Pushes - Event Push Collaborations shall allow alarm and events to be exported from the ACS to other 3rd party reporting engines.

11. Each Event Push Collaboration shall be defined with specific Event Types to be exported along with the schedule in which they are to be exported.

12. Events shall have the option to be exported with detailed alarm response information including Acknowledgments, Clears, and Operator Notes.

13. Data Filters - Collaborations shall allow Administrators to select a subset of data for export or import operations. Filters shall be used do define which records would be selected for the import or export.

2.4 BULDING CARD READERS

A. The ACS System shall provide the ability to support HID multiCLASS readers.

B. Each card reader shall have a low profile, rugged, weatherized polycarbonate sealed enclosure with multi-color LEDs and sounder for access granted and access denied indications. Each reader shall be mountable indoor or outdoor. All readers mounted externally shall be environmentally sealed. Card reader shall be one of the models stated below based on mounting requirements.

1. HID model RP15 multiCLASS card reader – mullion mounted (typically utilized for

store front style entry / exit doors).


2. HID model RP40 multiCLASS card reader – single gang back box mounted (typically utilized for interior doors).

3. HID model RPK40 multiCLASS card reader with keypad – single gang back box mounted (typically utilized for interior doors that require a higher level of security such as card plus pin).

C. Security Contractor to coordinate color with Owner.

D. The acceptable manufacture for card readers shall be HID Corporation. No substitutions

allowed.

2.5 NETWORK SWITCH

A. Ethernet switches shall be U.L. listed and shall minimally meet with all regulatory agency approvals specifications as the recommended models (e.g. Safety Certifications, Electromagnetic Emission Certifications, NEBS).

B. All switches to be mounted in “OWNER” provided standard 19” racks.

C. All switches to be covered by limited lifetime warranty. Extended warranty services have been

included in the estimated cost of construction for the following benefits to Fulton County Schools, North Transporation Facility: s/w upgrades and bug fixes, telephone technical support and advanced hardware replacement.

D. All switches must support QoS. All switches should support minimally: IEEE 802.1p COS, and

DSCP.

E. Additional standards that must be supported: IEEE 802.3ad, IEEE 802.1Q, 802.1D, 802.1x and 802.3af for Power over Ethernet switches (POE).

F. All switches shall be provided with a minimum of two (2) Small Form-factor Pluggable (SFP)

slots. Fiber optic SFP, 10GbE modules shall be LC ports.

G. Specified manufacturers for Ethernet switches shall be Cisco Systems, Inc 3500 Series. 2.6 ACCESS CARDS

A. A quantity of fifteen hundred (1500) printable HID iClass, model 2020 Smart Cards shall be provided with Corporate 1000 facility code (Note that Corporate 1000 facility code has already been established on previous project). Security Contractor to coordinate with Fulton County Schools on this project to ensure that cards are provided with the same facility code as the previous project.

1. The card shall function at 13.56 MHz. 2. The card shall function as a 125kHz proximity card. 3. The card shall have a read range of up to 4 inches. 4. The card shall be compatible with HID multiCLASS card readers.


5. The card shall have an ISO MIFARE microprocessor. 6. The card shall have 2k bits of memory. 7. The cards shall be ordered with Corporate 1000 with facility code. 8. The card shall be ISO14443 compliant.

B. Fulton County Schools has the FARGO DTC4250e photo ID badging printer with double side printing capability. Provide print ribbons, as well as any additional printing supplies needed to print 1500 double sided badges.

2.7 CENTRAL SYSTEM

A. The ACS System’s Central System equipment shall be comprised of but not limited to the

following minimum components/equipment:

1. Access Control System (ACS) Enterprise Appliance shall include: a. The server shall be rack configuration server provided with 19” rack mount kit. b. Embedded Linux operating system suing an open source kernel c. An OpenLDAP Directory structure for identity data storage d. A NGINX Web Server e. ACS Application Software

2. Client Workstation/Enrollment Workstation minimum configuration shall be a Pentium 4,

3.4 GHz based PC with 1 gigabytes of RAM, 160-GB hard disk drive, CD-ROM drive, 2 serial ports, USB ports, parallel port, 3.5” floppy drive, internal zip drive, 1000BASE-FL (fiber optic) Ethernet Network Adapter, 19-inch SVGA-monitor with minimum resolution of 1280 x 1024 pixels, mouse, keyboard, Microsoft Windows XP Workstation and Microsoft SQL Server 6.5 software, 5-client license.

2.8 DOOR POSITION SWITCH CONTACTS

A. Provide high security type balanced magnetic contacts where shown on the contract drawing.

B. Surface mounted: Door contacts shall be balanced, triple-biased type. Door contacts shall be provided with supervised loop and shall have a flexible armored cable with total encapsulation to protect against moisture. Door contact shall have anodized aluminum finish, with stainless steel flexible cable. Door contacts shall be UL Listed and be warrantied for two years. Door contact for surface mount swing door locations shall be Sentrol 2700 series or approved equal. Door contacts for surface mount roll-up door locations shall be Sentrol 2720 series or approved equal. Door contacts for recessed mounted swing or sliding door locations shall be Sentrol 1078 or equal.

2.9 D.C POWER SUPPLY

A. Provide low voltage power supply units associated with Local Interface Units and Door Control Panels and as required to provide 24 volt regulated, filtered D.C. power for locking controls, D.C. locks and signal devices. Output power shall be12 or 24 volt D.C. with ampere rating not


less than 150% of load imposed on power supply under most severe conditions of load. D.C. output shall be fused. Output voltage shall be regulated within plus or minus 5% from no load to full load. Power supply shall be UL listed.

B. Contractor to provide power supplies for all electric and electro-magnetic door hardware not

furnished with its own power supply. Contractor responsible for coordinating with project door hardware schedule.

2.10 DOOR CONTROL PANEL

A. The ACS 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 ACS hosting server or operator workstations.

3. Support for redundant communications to ACS hosting server or operator workstations; primary communications via 10/100Mb Ethernet with automatic switchover to secondary communications via dial-up modem when detecting network failure.

4. The ACS shall use DES/3DES encryption algorithms for the protocol between network based control

5. RS232 and RS422 communications ports for cascading/clustering multiple control panels via a single communications port interface to ACS hosting server or operator workstations.

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

7. Persistent Memory: The database memory downloaded to the ACS control panel shall be written to FLASH memory for permanent retention during the event of total power failure. The database shall automatically recover after power is restored without requiring any connection to the ACS server.

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

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

B. Control Panel Interfaces: The ACS 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.

2.11 EQUIPMENT RACKS

A. Floor Mounted Equipment Racks- Floor mounted equipment racks shall be aluminum relay racks with uprights to mount equipment. Uprights shall be 3 inch deep channel, 1-1/4 inches wide, drilled and tapped 12-24 in a 1/2 inch pattern. Racks shall be provided with a standard top cross-member, and pre-drilled base plate to allow floor fastening. Equipment cabinets shall be provided with side panels, rear louvered metal doors, depth-adjustable front and rear mounting rails, and louvered top. Ventilation fans shall be included. Equipment racks shall mount equipment 480 mm (19 inches) wide and shall be 1828 mm (72 inches) high and 760 mm (30 inches) deep. Cabinet exteriors shall be painted beige.

2.12 REQUEST TO EXIT DEVICES

A. Provide request to exit (REX) devices where shown on the Contract Drawings.

B. Wall mounted pneumatic type (REX) devices at 42 inches AFF. Coordinate exact mounting location with other wall mounted devices and equipment. Wall mounted (REX) devices shall be single-gang aluminum faceplate with heavy duty mushroom head type pushbutton. Pushbutton contacts shall have minimum contact ratings of 24 VDC/2 Amps, 120 VAC 60 Hz./5 Amps. (REX) shall have permanent text labeling to read “PUSH TO EXIT”. (REX) shall fit standard single-gang electrical backbox and shall be secured to backbox using tamperproof type screws. Termination of (REX) device wiring may be by screw terminal or pigtail wiring using proper crimp type connectors.

C. Mount wall mounted type passive infrared motion detectors (PIR), used as (REX) devices, to

effect automatic unlocking of electric door operators and locks via ACS System’s LIU’s and/or DCP’s. (PIR) devices shall have wide angle, long range lenses (adjustable) to detect motion of personnel desiring to exit through the door. Coordinate exact field mounting location to provide best operation of (PIR) type (REX) device. (PIR) device shall operate at 9.0 to 16.0 VDC and have form-C output contacts rated at minimum 24 VDC/0.5 amps.

Fulton County Schools: North Transportation Facility April 8, 2016 28 3000 - 61 J&A Engineering ADDENDUM #4 06/20/2016 2.13 UNINTERUPTIBLE POWER SUPPLY (UPS)

A. Furnish and install uninterruptable power supply (UPS) at the location of the ACS server in the MDF Server Room and the client work stations in the administration area. UPS system to provide battery backup for a minimum of 30 minutes.

B. The UPS shall be an on-line double conversion UPS which meets the following minimum

criteria:

1. UPS shall have the ability to handle crest factor ratios of 2.5 or above. 2. UPS shall have a sine wave output with a total harmonic distortion of 5 percent or less. 3. UPS shall provide continuous (no-break power) during momentary or complete blackouts. 4. UPS shall have the ability to recharge the battery to 90 percent capacity within a

reasonable period of time (5 to 10 times the discharge time). 5. The UPS output shall be regulated with maximum deviations from nominal of +6 percent

to –13 percent over the full input range, both AC and DC. 6. UPS shall meet ANSI C84.1 requirements

C. UPS and batteries shall be sized to 150% output VA required and shall be valve regulated

(sealed or maintenance free) lead-acid cell type. Batteries shall be installed within the UPS enclosure or in a standard enclosure provided for that purpose by the UPS manufacturer.

D. Furnish and install a UPS bypass switch which, when actuated, will bypass the UPS and

connect the load directly to the emergency supply source.

E. Furnish calculations with shop drawings verifying UPS sizing in compliance with these specifications.

2.14 TRANSIENT VOLTAGE SURGE SUPPRESSION

A. Protect all equipment against surges induced on all control, video, and power cables. All copper cables and conductors which serve as 120V power, control, or video conductors shall have surge protection circuits installed at each end and locations where conductors enter or exit a building. Fuses shall not be used for surge protection.

B. Surge suppression devices shall meet the following standards/publications:

1. UL 497B 2. UL 1449 (must meet 330 Volt suppression rating) 3. IEEE Category B impulse and ring wave test

C. Acceptable Manufacturers: Northern Technologies, Inc., EDCO. Product shall be warranted

against defect for a period of not less than five (5) years.

D. All power connections, including 24 VDC and 24 VAC power supplies and direct wired or plug-in 120 VAC power connections, for all systems and components specified herein, shall be


equipped with surge suppression devices. Devices shall be bonded to building grounding system in accordance with Article 250 of the National Electric Code.

E. Grounding: Provide a dedicated, separate No. 6 AWG copper conductor from building

grounding system to all security equipment rooms, security equipment cabinets, and control rooms. Connect all lightning protection devices and security equipment non-current carrying metal parts to grounding conductor in accordance with Article 250 of the National Electric Code. Provide ground bus bar in each equipment room and control room with dedicated ground conductor to each cabinet, enclosure, pull/junction box and all equipment.

F. Ground Resistance Measurement: Each signal ground system D.C. resistance shall be measured between any point on the signal ground bus and the earth ground. An instrument designed specifically to measure the resistance of a point to each earth ground shall be used. The systems subcontractor shall measure ground resistance in accordance with the procedure as outlined by the test equipment manufacturer. Instrument shall be Biddle earth resistance test instrument, or approved equal.

2.15 SYSTEM WIRING

A. Card reader connection cable shall be of a type specified by the manufacturer of the ACS System. Cable must meet minimum NEC requirements for Class 2 wiring.

B. Power wiring for electrified door hardware shall not be smaller than No. 18 THWN or XHHW.

C. All wiring systems shall use solid copper conductors except where flexibility is required.

Stranded conductors shall be acceptable only where all terminations can be made to crimp type screw lug.

D. All wiring systems shall be color-coded so that each conductor for individual lock set is of a

distinctive color. All wiring shall be in accordance with the manufacturers written recommendations. All cabling/wiring shall be submitted in a detailed spreadsheet including cut sheets and samples to the Owner prior to any installation.

E. All conductors within junction boxes, pull boxes, and equipment cabinets shall be grouped and

laced with nylon tie straps with identification tab, for individual lock sets.

2.16 EMERGENCY EXIT PULL STATIONS

A. Furnish and install Emergency Exit Push Buttons at all doors equipped with magnetic locking hardware.

B. Emergency Exit Push Buttons shall meet the following requirements:

1. Faceplate to match décor (stainless steel, brushed aluminum, etc.) 2. High visibility 2” square, illuminated buttons clearly identified as “PUSH TO

EXIT”


3. Minimum 30 second timer that activates as buttons is pressed and breaks lock power

4. SPDT contacts UL/CSA approved and rated for 10 amps @120 VAC that break lock power immediately upon button activation.

C. At doors with hollow metal frames, Emergency Exit Push Buttons shall be recessed into the

door frame. Faceplates are to be the width of the frame. D. Emergency Exit Push Buttons shall be Camden Door Controls model CM-30 Series or equal.

2.17 ELECTRIFIED DOOR HARDWARE

A. All electrified door hardware shall be provided and installed by the General Contractor.

B. The Contractor shall be responsible for connecting and terminating all electrified door

hardware and associated devices to the new ACS System.

PART 3 - EXECUTION

3.1 SEQUENCE OF OPERATIONS

A. The enrollment workstation shall serve as the data credential input workstation for the cardholder management module of the ACS System. This station shall be connected to the LAN to allow total system integration with the Network File Server and Client workstations.

B. The Network File Server shall serve as the central server computer that shall manage all ACS System network, control, and administration functions. The System shall provide a local interface with the Fire Alarm System to effect automatic unlocking of all doors controlled by the ACS System during Fire alarm conditions.

3.2 WIRING SYSTEMS

A. Protect all communication and data equipment against surge induced on all control, sensor and data cables. All cables and conductors which serve as control, sensor, or data conductors shall have surge protection circuits installed at each end that meet the IEEE 472 surge withstand capability test and the electrical transient tests established in UL365. Fuses shall not be used for surge protection.

B. The work under this section of the specifications includes the installation of all wiring for the electrified door hardware. The actual connections to the electrified hardware and the access control system shall be done under this section of the specifications. It is the responsibility of the Security Contractor to coordinate all electrical requirements and connections of the electrified hardware.

3.3 CARD READER AND DOOR CONTROL PANELS


A. Mount card reader sensors at a height of 48" AFF to center, unless shown otherwise. Mount card readers securely to the mounting surfaces and provide weather caulking around exterior mounted readers.

B. Mount door control panels where shown on the contract drawings or where required to provide a completely operational system. All door panels must incorporate a minimum of 4 hours battery back for micro-processors as well as electrified door hardware.

3.4 TESTING

A. Testing requirements apply to all new construction.

B. Materials and documentation to be furnished under this specification are subject to inspections and tests. All components shall be terminated prior to testing. Equipment and systems will not be accepted until the required inspections and tests have been made, demonstrating that the access control system conforms to the specified requirements, and that the required equipment, systems, and documentation have been provided.

3.5 TRAINING

A. The Contractor shall include in the base Contract all costs required to train Fulton County School, North Transporation Facility operating and maintenance personnel in the use and maintenance of systems provided under this section of the Specifications. Training sessions shall be conducted by instructors that are certified by the manufacturer of the specific system.

B. Sessions shall be conducted for not less than four hour periods during normal working hours, i.e., Monday through Friday, 8:00 AM to 5:00 PM. Training session schedules shall conform to the requirements of; therefore such schedules shall be submitted to Fulton County Schools for approval not less than two weeks prior to the training session. All training sessions shall be video-taped for future use. At Fulton County School’s discretion, provisions shall be made to allow up to 2 owner personnel to participate in final system check out of all systems.

C. The Contractor shall keep a sign-in sheet during training. Sign-in sheet must be provided as part of close out documentation.

D. Video tapes shall be of professional quality both for video and audio and must be approved by the Owner/User. Provide two copies to Owner/User. Time to be included in base Contracts for specific systems shall be as follows: 1. ACS System entirely - 8 hours

END OF SECTION 28 3000