OIAA_Security_Systems_Standards_FINAL_v2.0_2202.04.08.pdf

Electronic Security System Standards

Version 2.0 (April 2022)

Electronic Security

Systems

Design and Construction Standards

Version 2.0

April 2022

Ontario International Airport Authority

Electronic Security Systems Standards

Version 2.0 (April 2022)

INTRODUCTION AND OBJECTIVE

Ontario International Airport Authority (OIAA) requires a robust IT infrastructure to run its airport-based security systems. There is a growing desire to use technology to manage the Airport Operations more efficiently as well as to allow greater accountability and record keeping of historic events through the electronic security systems. The objective of this document is to disseminate requirements to OIAA for the installation and operation of these systems.

OIAA, as the owner and operator of the Ontario International Airport, shall maintain its own Airport

Security Program (ASP). The ASP shall be in compliance with all requirements of CFR Part 1542, and all security designs shall be in accordance with the ASP and be subject to final approval by the OIAA Airport

Security Coordinator. This document provides additional guidelines for designers, engineers, general contractors, and other industry specialists.

SUMMARY

This document provides design guidance for an Electronic Airport Security system that includes an Access

Control and Alarm Monitoring System (ACAMS), a Perimeter Intrusion Detection System (PIDS), Intercom

Systems and a Video Surveillance System (VSS). The purpose of these systems is to alert OIAA of security violations within a defined perimeter, such as a terminal door or the airport perimeter. A properly designed system creates an environment that deters access, detects violations, delays an intruder and allows for a coordinated response. This document provides guidance for systems that will provide enhanced layers of detection and risk management for the Airport and mitigate the impact of airport security incidents.

The material provided in the following sections includes the minimum requirements, general information, design criteria, guide specifications and details for the Information Technology (IT) Department at OIAA.

While this document addresses major areas of concern to OIAA, it is not an all-inclusive document.

HOW TO USE THIS DOCUMENT

This document should be used as a resource for the development of project-specific design documents including drawings, details, and specifications. It is the responsibility of the design, engineering, and construction professionals to adhere to all applicable codes and regulations related to the content presented.

The OIAA Security Systems Standards has been written to define and provide a benchmark criterion of their security systems and supporting infrastructure. Using lessons learned from recent airports undergoing similar standards-based development, its purpose is to provide guidance and input into new projects across the OIAA site to ensure a consistency of approach in providing the required infrastructure and security systems.

Version Publish Date Revisions Reviewed By

1.0 03/16/2022 Electronic Security Systems

Standards

Faith Group (internal)

1.2 03/17/2022 Content, formatting OIAA

1.3 03/22/2022 Incorporated initial feedback from OIAA, added content and formatting

OIAA

2.0 04/08/2022 Incorporated final feedback from OIAA and formatting

Version 2.0 (April 2022)

Table of Contents

INTRODUCTION AND OBJECTIVE

SUMMARY

HOW TO USE THIS DOCUMENT

VIDEO SURVEILLIANCE SYSTEM (VSS)

ACCESS CONTROL AND ALARM MONITORING SYSTEM (ACAMS)

PERIMETER INTRUSION DETECTION SYSTEM (PIDS)

INTERCOMMUNICATION (INTERCOM)

INFRASTRUCTURE

ACRONYMS/GLOSSARY

Video Surveillance System (VSS) Electronic Security Systems Standards

VIDEO SURVEILLIANCE SYSTEM (VSS)

Version 2.0 (April 2022)

PART 1 – GENERAL REQUIREMENTS

1.1 OIAA shall utilize a network-based Video Surveillance System throughout the airport to include terminal buildings, auxiliary buildings, cargo areas, Tenants buildings, ramp areas, secure doors and portals, baggage, high value rooms, pedestrian and vehicle gates, parking lots, curbside, airport entry areas, and perimeter.

1.2 The VSS shall consist of software, servers, cameras, ancillary equipment, and an extension of the Airport’s existing IP network with integration between the VSS and other security related software providing monitoring and situational awareness.

1.3 The VSS shall be fully integrated with the ACAMS, PIDS and Intercom, to provide complete a holistic security and monitoring system.

PART 2 – SOFTWARE VIDEO COMPONENTS

2.1 Video system software shall be compatible with both Analog and Digital video streams to support complete migration to fully digital system in the future.

2.2 Video system software shall support full operational capability of all PTZ-enabled cameras’ control

2.3 All cameras must be integrated with the video management system, and not run in an isolated environment where custom software is required for user interface

2.4 Video system shall be the most recent supported version as recommended by the system manufacturer for all camera models installed within the system

2.5 VSS storage shall be a minimum of 1 year at 4CIF resolution

2.6 TSA area video storage shall be a minimum of 90 days and comply with TSA requirements for view, placement, and resolution.

2.7 VSS system shall accommodate future camera and server-based analytics.

2.8 Servers and storage requirements related to VSS systems shall be coordinated with OIAA

IT on a project basis. All VSS systems installed in the project meet the required recording rates, storage requirements and server requirements. All the components are required to interface seamlessly with the OIAA network and to be sufficient to support all the cameras for the project.

2.9 All servers shall rack mounted within a secure IT / communications room.

Version 2.0 (April 2022)

PART 3 – CAMERAS and COVERAGE CRITERIA

3.1 Fix view cameras shall be used to view fixed assets, locations, or areas of interest. Views include doorways, equipment, areas of congestion, POS or other OIAA to public transactions. These include but not limited to curbside, ticket counters, baggage, SIDA doors and gates, vehicle entry/ exit lanes, inspections, TSA, IDF / MDF locations, equipment, or other critical or high value assets. Fixed cameras views can be specific targets and events or general views such as lobbies or hold areas. Camera selection shall be based on required resolution to achieve the desired view, detection, recognition, and identification (high and low).

A. Fixed Cameras shall be at a minimum:

i. Minimum 2.1 megapixel

ii. Day / night and low light

iii. Indoor/outdoor

iv. Fixed lens for specific view or veri-focal

v. Auto-iris

vi. Wide dynamic range

vii. Up to 30 FPS

viii. H.264, H.265

ix. POE

1. Manufacturer:

a. AXIS

b. Hanwha Techwin

c. Or approved equivalent

3.2 Pan Tilt Zoom (PTZ) shall be used for investigation, observation and tracking of individuals or events. PTZ are normally set on a fixed object or connected to system that automatically moves the view based on events such as time, door alarms, PIDS alarms and target tracking, and/or other programmed events.

A. PTZ Cameras shall be at a minimum:

i. Indoor/outdoor

ii. H.264, H.265

iii. Optical 10x

iv. 25/30 FPS

v. Pan 360 endless

vi. Wide Dynamic Range

vii. IP66

viii. Low light, .01lux

ix. POE

Version 2.0 (April 2022)

1. Manufacturer:

a. AXIS

b. Hanwha

c. Or approved equivalent

3.3 Specific use cameras shall be use in challenging or where unique views are required such

Automatic License Plate Readers (ALPR) or thermal imagers for all weather observation, or long-range views.

3.4 Multi-imager cameras are used where wide general view are required while limiting network ports and drops. Multi-imager cameras provide panoramic 180-, 270-, or 360-degree views at high resolution providing detailed views. Multi-imager locations can be, but not limited to curbside, ticketing, baggage, building perimeters, ramp areas, parking, and vehicle gates. 360-degree fisheye cameras shall not be use.

A. Multi-imager Cameras shall be at a minimum:

i. Indoor/outdoor

ii. H.264

iii. 8 Megapixel

iv. Wide Dynamic Range

v. 25/30 FPS

vi. IP66

vii. Low light, .05lux

viii. POE

1. Manufacturer:

a. AXIS

b. Hanwha

c. Or approved equivalent

3.5 Camera Coverage

A. Camera view selection shall be based on view required

i. Detection – shall be able to detect a target at 0,6 pixels per inch

ii. Recognition – shall be able to easily recognize the target at 3,2 pixels per inch

iii. Identification (low) - shall be able to identify the target with low assurance at 6,3 pixels per inch

iv. Identification (high) – shall be able to identify the target with high assurance at 12,5 pixels per inch.

Detection Recognition Identification

Figure 01 - Typical Camera Resolution

ONT Camera Coverage Area

D e te ct io n

R e co g n it

Id n ti fi ca ti o

(L w

Id e n ti fi ca ti

(H ig h

Airfield Movement/Parking Areas X

Airport Fuel Farm X

Baggage Claim Unit X

Baggage Claim-Public Area X

Baggage handling system-conveyors X

Baggage Make-up Area X

Baggage Screening Equipment X

BHS Server Room X

Cash transaction areas X

Curbside X

Data Center X

Direct Access Point Doors X

Electrical Rooms X

Electrical Switchgear Room X

Elevators X

Emergency Egress to Secure Area X

Emergency Panelboard Room X

Escalators X

Food Court X

Gate Hold Areas X

General Terminal Overview/Circulation X

IDF's X

Landside Roadways X

Loading Dock X

Maintenance Yard X

MDFs X

Mechanical Rooms X

MPOE X

Version 2.0 (April 2022)

ONT Camera Coverage Area

D e te ct co g n it n ti fi ca ti w

Id e n ti fi ca ti h

On Screen Resolution (OSR) X

Parking Lots/Areas X

Passenger Boarding Bridges (interior) X

Passenger Circulation Areas X

Portals In/Out of Airport X

Ramp Areas X

Rental Car Facility/GTC X

ONT Camera Coverage Area

D e te ct co g n it n ti fi ca ti w

Id e n ti fi ca ti h

Security Screening Checkpoint X

Shipping/Receiving Center X

SIDA Doors X

Stair Wells – entry/exit X

Ticket Counters X

UPS and Battery Room X

Vehicular ingress/egress-ALPR X

Table 01 – Camera Coverage Chart

PART 4 – TENANT REQUIREMENTS

4.1 Tenant building with access to the AOA shall follow OIAA security standards.

4.2 Each exterior door having access to the AOA shall have a VSS camera attached to OIAA security network monitoring door status and activity.

4.3 OIAA requires general view cameras on the ramp areas.

4.4 Tenant is responsible for providing camera coverage to the perimeter in which their buildings or any structure impedes the view of the secured perimeter.

4.5 Tenant to provide all equipment required to meet IOAA standards

A. Cameras, mounts and other hardware as required

i. Tenant workstations to be provided, with limited video access to only their cameras, using different username and password credentials separate from that of OIAA’s identity management system.

Version 2.0 (April 2022)

B. Additional storage capacity

i. Includes primary full resolution storage medium and duration requirements set forth by IOAAs video retention policy

ii. Includes secondary lower resolution longer-term storage medium and duration requirements set forth by IOAAs video retention policy

PART 5 – DESIGN and SUBMITTAL REQUIREMENTS

5.1 DESIGN SUBMITTALS

A. Contractor Qualifications: Submit letters and or certifications from the CCTV manufacturer evidencing that the Contractor has been trained and certified in the installation of the system.

B. Product Data:

i. Provide product data for each type and configuration of component specified herein and to be supplied. Submittals must include both product construction and performance specifications.

C. Shop Drawings:

i. Device placement on floor plans.

ii. Point-to-Point Diagrams: Include wiring, points of connection and interconnecting devices between the following:

1. Video Cameras.

2. Interface to ACS.

3. Interface to SLAN.

4. Cable conductors (identify conductors on the point-to-point diagrams with the same tag as the installed conductor).

5. Controllers and custom enclosures

6. Reader boards and custom enclosures

7. Card readers

8. Biometric readers

9. Door position monitoring contacts

10. Alarm input modules

11. Relay output modules

12. Fire Alarm interface wiring

13. Electric door locks & hardware

iii. Label Samples

1. ACS Sample Test Forms

2. Operations & Maintenance Manual

iv. Schedules: Provide schedules for CCTV cameras that show each point ID with a description of the connected devices.

Version 2.0 (April 2022)

v. Block Diagram/Riser Diagram: Show the CCTV components, conduit, wire types, and sizes between them, including cabling interconnections between termination hardware.

vi. Examples of planned mounting matching the custom mounting details shown on the architectural drawings.

PART 6 – CONSTRUCTION AND INSTALLATION

6.1 GENERAL REQUIREMENTS

A. OIAA shall utilize a network-based Video Surveillance System throughout the airport to include terminal buildings, auxiliary buildings, cargo areas, Tenants buildings, ramp areas, secure doors and portals, baggage, high value rooms, pedestrian and vehicle gates, parking lots, curbside, airport entry areas, and perimeter.

B. The VSS shall consist of software, servers, cameras, ancillary equipment, and an extension of the Airport’s existing IP network with integration between the VSS and other security related software providing monitoring and situational awareness.

C. The VSS shall be fully integrated with the ACAMS, PIDS and Intercom, to provide complete a holistic security and monitoring system.

6.2 NETWORK VIDEO COMPONENTS

A. The network video components shall be installed by a certified dealer/integrator. Certification for installation shall be conducted by the manufacturer and shall provide all necessary knowledge to fulfill the systemization and deployment across diverse networks and infrastructures, as well as provide commissioning abilities at the integrator level.

B. Coordinate programming requirements with OIAA. At the minimum provide the following programming:

i. IP addressing.

ii. Camera titles.

iii. Specific frame rate and compression for each camera.

iv. Motion detection zones.

v. Archiving parameters.

vi. ACS (Access Control and Alarm Monitoring System) and PSIM system interfaces.

vii. User level setups.

viii. Workstation and video console display programming.

6.3 VIDEO CONTROL AND SWITCHING SYSTEMS

A. Coordinate programming requirements with OIAA. At the minimum provide the following programming:

i. Camera titles.

ii. ACS system interface.

iii. User level setups.

Version 2.0 (April 2022)

iv. Video routing for event-based video switching.

6.4 CABLES

A. Fiber optic cable shall be used for all exterior, roof, or pole mounted camera locations.

B. Fiber optic cables shall be visually inspected, and continuity testing shall be performed on each fiber of each cable reel onsite prior to installation to ensure no damage occurred during shipment.

C. Each end of each fiber optic cable shall be terminated in a patch panel using field-installable

ST compatible connectors and fan-out tubing. Patch cord jumpers shall be pre-connectorized on one end with ST compatible connectors and on the other end with the connector type compatible with the end equipment. Jumpers shall be used to connect the cables terminated at the patch panel in the control center to the end equipment.

D. Each camera utilizing fiber optics shall have a dedicated 2 fiber cable.

E. The connector loss for field installed connectors shall not exceed 0.5 dB for ST compatible connectors.

F. Network Cables shall be installed and terminated in accordance with the manufacturer's recommended procedures.

G. The installing contractor shall label VSS devices, panels, enclosures, pull boxes and junction boxes as required, following the naming standard provided by OIAA.

H. Coordinate with OIAA for text and font styles

I. Labels shall be machine printed and suited for application

PART 7 - CONFIGURATION AND LABELING

7.1 All cameras are to be labeled and linked to the 2-Dimensional graphic called the “Canvas”

A. The Canvas shall be floor plans imported (into the VMS software platform allowing the physical locations of cameras installed to be graphically displayed and selected to either see real time video or recorded video.

B. Labeling shall follow the following hierarchical labeling scheme:

i. Terminal, Ancillary building or section of airfield

1. Building level (if applicable)

a. Landside or Airside (if applicable)

a) Room name and Room Number

(i) Coverage area of camera

See example below for hierarchal naming and organization of cameras

Figure 02 – Hierarchical Naming Convention of Cameras

Access Control and Alarm Monitoring System (ACAMS) Electronic Security Systems Standards

ACCESS CONTROL AND ALARM MONITORING

SYSTEM (ACAMS)

Version 2.0 (April 2022)

PART 1 GENERAL REQUIREMENTS – ACCESS CONTROL SYSTEM

1.1 A physical electronic access control and monitoring system (ACAMS) is currently deployed to restrict and manage access to secure areas, monitor alarms, and maintain a record of entry and exits events and alarms. The access control system shall consist of software, servers, intelligent control panels, reader boards, power supplies, badge readers with keypads, cabling, and enclosures. The access control system shall be programming to control access to areas, maintain records, report alarms and integrated with the video surveillance system. The system shall control and monitored doors, systems, devices, or items as required. All doors include an integrated VSS camera and intercom

1.2 All new software, equipment, ICS, card reader interface boards, and input/output boards shall be compatible with the current system.

A. Manufacturer shall be Lenel

B. Software shall be the latest version of OnGuard

C. All hardware shall be new Lenel equipment

1.3 Due to rapid technological advancement, all supplied products shall be approved latest equivalents of the specified products.

1.4 Door controls by the access controls system consists of specific hardware such as card readers, electric locks, exit hardware, monitoring devices, and local alarm notification.

1.5 The access control and alarm monitoring system (ACAMS) shall consist of intelligent control boards that communicate utilizing a TCP/IP based Ethernet network. Reader interface boards and input/out boards shall connect via RS-485 to the IC board and manage the door and alarm conditions.

1.6 All door portal cabling for locks, card reader, monitoring devices, shall be routed to central location, either a IDF or secure room and wired to the reader installed within a secure enclosure. See typical layout figure XX

1.7 ACAMS enclosures shall be include power supplies for system and field hardware such as locks, motion detectors, horns, strobes, and other ancillary devices as required.

1.8 The system shall be capable of routing individual alarms to select workstations based on event type and time of day.

1.9 ACAMS devices to cover all areas to including but not limited to terminal buildings, perimeter, sterile and secure areas, cargo, offices, baggage, and vehicle gates.

1.10 ACAMS shall seamlessly interface with the Genetec VSS, and other systems as required.

Version 2.0 (April 2022)

1.11 The contractor shall contact the Airport for OIAA Standard Door Security Details or custom panel layouts as well as labeling requirements for the work indicated within the specification and on the Security Drawings.

1.12 ACAMS shall communicate with the existing dedicated access control/VSS system network backbone as per Division 27. Network switches for the SLAN shall also be provided as per Division 27.

Figure 03 - Typical ACAMS Field Equipment Configuration

Version 2.0 (April 2022)

PART 2 – PORTAL ACCESS AND COMPONENT REQUIREMENTS

2.1 Access control doors and portal openings shall have specific hardware, function and security requirements as shown in the following table.

Table 02 – Portal Access and Component Requirements

PART 3 – ACCESS CONTROL FIELD EQUIPMENT

3.1 Intelligent System Controller (ISC)

A. The ISC shall provide full distributed processing of access control & alarm monitoring operations.

B. Each ISC board will utilize a separate 10/100 Mbps TCP/IP connection to the Head End for communication purposes. The ISC shall support a secondary communications method, including Serial, LAN, or dial-up.

C. The ISC board will utilize at least a local 32-bit processor.

D. The ISC board will support at least 15 MB of On-Board non-volatile memory and be capable of storing 450K Cardholder records and 50K event records within this memory.

Version 2.0 (April 2022)

E. The ISC board will support multiple card technologies and be capable of integrating with other manufacturer’s card readers.

F. The ISC board will have Biometric Interface support.

G. The ISC board will support up to Nine (9) digit pins.

H. The ISC board will contain LEDs for communications and component status.

I. Each ISC board will be limited to supporting a maximum 16 doors, in order to minimize the number of doors that must be secured in the event of a ISC failure.

J. The ISC board will be UL 294, ULC, and CE Certified and will support UL 1076 RS-485 downstream communications.

K. Manufacturer

i. Intelligent Controller shall be LNL-3300 or Approved Equivalent

3.2 Dual Reader Interface Board

A. Description:

i. The Dual Reader Interface (DRI) shall provide onboard control for up to 2 card readers and 2 doors, as well as 4 auxiliary inputs and 4 auxiliary outputs.

ii. Each DRI boards will communicate with the ISC board utilizing RS-485.

iii. The DRI board will support up to 8 card formats and will be capable of granting or denying access based on a facility code verification while offline with the ISC board.

iv. The DRI will utilize Form C relays and support four-state supervision of all inputs.

v. The DRI will support multiple card technologies and will integrate with other manufacturers card readers.

vi. The DRI board will support Individual Shunt Times (ADA requirement).

vii. The DRI will support OSDP readers, and both Wiegand and Magnetic Card formats.

viii. The DRI will support up to 9-digit PIN codes.

ix. The DRI board will contain LEDs for communications and component status.

x. The DRI board will be UL 294, ULC, and CE Certified.

xi. The Contractor shall utilize the Lenel 1320 DRI board as a standard at IOAA for all doors, regardless of the number of card readers at each door.

3.3 Input Control Module (ICM):

A. Description:

i. The Input Control Modules (ICM) shall provide full supervision of up to 16 UL 1076

Grade B analog supervised or unsupervised inputs zones.

ii. Each ICM board will have 16 supervised inputs and 2 Auxiliary Relays.

iii. The ICM board input will be capable of reporting secure, alarm, open, short, ground, or circuit fault conditions.

Version 2.0 (April 2022)

iv. The ICM board will scan each zone up to 180 times per second.

v. The ICM board will include 2 additional dedicated inputs for tamper and power status.

vi. The ICM board will be UL 294, ULC, and CE Certified.

vii. The ICM board will contain individual LEDs for each input zone and will show status for “No Alarm”, “Alarm Condition” or “Circuit Fault.”

viii. The ICM board will contain LEDs for board communications and power status.

B. Manufacturer:

i. Lenel LNL-1100 Input Control Module board

3.4 Output Control Module (OCM)

A. Description:

i. The Output Control Modules (OCM) shall contain 16 Output Relays that are capable of controlling a corresponding output device upon an input activation or on command from the system.

ii. Each OCM board will have 16 digitally controlled Form C Relays rated at 5A at 30

VDC.

iii. The OCM board relays shall be capable of responding to input alarms from within the same ISC, commands from a System Operator, Time Zone commands for automatic operation, or System commands while online from an input from another

ISC.

iv. The OCM board will be UL 294, ULC, and CE Certified.

v. The OCM board will contain individual LEDs for each relay and will show status for

“Activated” or “Not-Activated.”

vi. The OCM board will contain LEDs for board communications and power status.

B. Manufacturer:

i. Lenel LNL-1200 Output Control Modules boards.

3.5 Card Readers

A. HID Card Readers that support the multi-technologies. The specific model of the Card reader will vary based on the installation location, the locations performance requirements (read range), and environmental (indoor, outdoor) conditions.

i. The readers shall support 125 kHz proximity cards, key fobs and tags.

ii. The readers shall support 13.56 MHz contactless smart cards.

iii. The readers shall be capable of outputting 26-bit, 32-bit, 34-bit, 37-bit, 40-bit, or 56-bit Wiegand formats.

iv. The reader shall support HID iClass cards and tags

v. The reader shall support mobile technologies.

vi. The readers shall be made with rugged, weatherized polycarbonate enclosures, designed to withstand harsh environments while providing reliable performance.

Version 2.0 (April 2022)

vii. The readers shall have LEDs which can be configured to display visual notification of a successful Access attempt as well as an un-successful Access attempt.

viii. The card readers shall have UL 294 certification.

B. Manufacturer:

i. Lenel LNL-R10330-05TB mullion reader

ii. Lenel LNL-R10320-05TB standard reader

iii. Lenel LNL-R10325-05TB standard reader with keypad

3.6 Power supplies

A. General:

i. Transformers and power supplies shall be provided for detectors, panels, and accessories.

ii. Power supplies shall meet or exceed the manufacturer's recommendations for the individual devices served. Devices requiring common voltages shall be powered from a common power supply at the locations indicated on the Drawings. System components such as control boards, reader interface boards and monitoring devices shall not be powered from the same power supply as the locking hardware.

B. Power Supplies

i. Mounted in a NEMA 1 hinged enclosure with power indicator integral with door.

ii. Rated at 1.5 times the current draw for devices served. Coordinate with the Division

8 Subcontractor for electrical power requirements.

iii. Individually fused outputs to each locking device

iv. Input for connection to a UL listed fire alarm panel output, which upon initiation shall disconnect power to the lock outputs. Only fail-safe locking hardware shall drop on fire alarm trigger.

v. Field devices such as IC board, reader interface boards, and other field devices shall have individual fused outputs.

vi. Sufficient battery back-up to power devices connected for 30 min in the event of primary power failure.

vii. UL Class 2 rated outputs

1. Manufacturer:

a. Altronix AL600ULXB or approved equivalent

b. Altronix ACM8CB or approved equivalent

Version 2.0 (April 2022)

3.7 Physical Locks and Cores

A. Part of the overall physical security program is Key Control. OIAA will utilize an electronic core as part of the Key Control program. Each door shall be fitted with an electronic core and each Access Control door shall use an electronic core as back-up for accessing the doorway.

i. Manufacturer:

1. CyberCore

3.8 Access Control enclosures

A. Exterior enclosures shall be suited for purpose, NEMA rated, all weather, tamper resistant, vented as required, and secured with approve OIAA lock.

B. Interior enclosures shall be suited for purpose, tamper resistant, and secured with approve OIAA lock.

C. All interior enclosures shall be mount to ¾ inch fire resistant plywood.

D. Exterior enclosures shall be mounted on Unistrut connect to posts, walls, or other structures designed and rated for equipment enclosures.

E. All enclosures shall include surge protected AC power, monitor for tamper, and utility outlet and back plane for equipment mounted and grounded per local codes.

3.9 Physical Door Lock Cores

A. All doors shall include a CyberLock core.

i. Cores shall match existing OIAA requirements

PART 4 – TENANT SECURITY REQUIREMENTS

4.1 Tenant building with access to the AOA shall follow OIAA security standards

4.2 Each exterior door having access to the AOA shall be access controlled by the Airport’s

ACAMS.

4.3 Design Requirements

A. Pedestrian doors that have AOA access shall be secured with an electrified lock, card readers, and monitored on the OIAA ACAM system in compliance with OIAA security standards.

Version 2.0 (April 2022)

B. Hanger and sliding doors not normally used for pedestrian shall be monitored on the

OIAA ACAM system in compliance with OIAA security standards.

C. Tenant to provide all equipment and inspections required to meet OIAA standards

i. Card Pin readers, locks, DPS/BMS, and ancillary hardware as required

ii. Intelligent control, reader and I/O boards

iii. Reader licenses

iv. CyberLock cores

v. Signage as required

vi. Any additional components or software required to secure the perimeter, gates, and doors.

PART 5 – DESIGN and SUBMITTAL REQUIREMENTS

5.1 Design Submittals

A. Submit in accordance with the requirements the following items:

i. Product Data

ii. Shop Drawings: Including Point-to-Point Diagrams between the following devices:

1. Controllers and custom enclosures

2. Reader boards and custom enclosures

3. Card readers

4. Biometric readers

5. Door position monitoring contacts

6. Alarm input modules

7. Relay output modules

8. Fire Alarm interface wiring

9. Electric door locks & hardware

10. ACS Sample Test Forms

11. Operations & Maintenance Manual

12. Label Samples

a. Coordinate with OIAA for text and font styles

b. Labels shall be machine printed and suited for application.

13. Submit Contractor qualifications: letters or certifications and like projects showing product competency, training, and installation knowledge.

14. ACAMS Sample Test Forms

15. Operations & Maintenance Manual

16. Record Drawings

a. Record drawing set shall be maintained on-site to reflect current conditions at all times

b. As-Built drawings shall be produced within 30 days of completion, in AutoCAD and PDF electronic format

Version 2.0 (April 2022)

PART 6 – CONSTRUCTION and INSTALLATION

6.1 Boxes, Panels, and Enclosures

A. Install boxes, panels, and enclosures plumb, square, level and true to building lines.

Set "flush mounted" units so that the face of the cover, bezel or escutcheon shall be in the same place as the surrounding finished surface. Mount boxes, panels and trim so that there are no gaps, cracks or obvious lines between the trim and the adjacent finished surface and ready them to receive final finish, as applicable.

B. Install insulating terminations in signal circuit boxes, panels, wire-ways, or enclosures of this section.

C. Write the destination for every conduit entering a door junction box, ACAMS enclosure, or wire way using a printed label next to the conduit inside the box.

D. Install all door junction boxes on secured side of door.

E. Plug any holes in enclosures not used for ventilation.

F. Install approved labels on the outside of each Security enclosure and relay termination enclosures.

6.2 Components

A. General

i. Follow manufacturers recommended guidelines for installation.

B. Access Controllers

i. Locate power supplies and all associated hardware in same location.

C. Special Connectors

i. Comply with the Owner’s requirements for specially configured Molex connectors and wire color coding on all electrified, monitored mortise locks and exit devices.

6.3 Programming

A. The Subcontractor shall provide the required ACAMS programming necessary to achieve a functioning ACAMS system.

B. OIAA is responsible for determining Access Level, Time Zone, and new Cardholder programming.

Version 2.0 (April 2022)

C. Prior to the completion of construction, schedule a meeting with the Owner and the

Engineer to determine all the programming criteria. The issues that shall be discussed are as follows:

i. Point naming conventions.

ii. Point addresses.

iii. Requirements for access control alarm monitoring on activation gate release from intercom master station.

D. Document the results of the meeting and perform all necessary programming to achieve the Owner’s requests.

E. Use the point and address agreed upon at in the programming meeting when terminating the system.

F. Program access rights, password protection, VSS interface, holidays, area control, inputs and outputs, schedules, and elevator control

G. System Integration and Interfaces:

H. Interface with the VSS system: the ACAMS shall interface with the VSS system to cause automatic camera call-up utilizing an API level software interface. Upon an alarm condition at but not limited to, an access point, vehicle post, duress button or other alarm input, the ACS shall cause the CCTV system to automatically call up the associated camera image. The system shall be programmed with at least one camera call- up per access control point.

6.4 Access Control and Alarm Monitoring Systems

A. Configure field panel communications as indicated on the Construction Drawings.

B. Access Control System Parameters:

i. Program the alarm bypass or shunt time (the time period the door can remain open before an alarm event is created) as directed by submitted door details.

ii. Program the door relock time (the time period after which the door will relock unless opened) for 10s.

iii. The systems must conform to OIAA’s Standard Door Security Details.

6.5 Labeling

A. The installing contractor shall label ACAMS devices, panels, enclosures, pull boxes and junction boxes as required, following the naming standard provided by OIAA.

Perimeter Intrusion Detection System (PIDS) Electronic Security Systems Standards

PERIMETER INTRUSION DETECTION SYSTEM

(PIDS)

Version 2.0 (April 2022)

The purpose of a Perimeter Intrusion Detection system is to alert an organization to the violation of a defined perimeter. Penetration events are classified as a human or object attempting to pass through the detection zone(s) within the defined perimeter. The large span of geography covered by OIAA, integration with the

Genetec VSS can provide the visual observation as to the cause of the detection event.

The PIDS perimeter is defined as the Airfield perimeter and other operational fence line required to be covered by PIDS technology. This defined perimeter would be the first and preferred line of detection providing as much time as possible for responders to verify and respond to breach events.

The PIDS system shall be a system of systems, utilizing a variety of devices for detection enhancing a physical barrier. As shown in Figure 1, a typical design includes multiple sensors integrated together into the airport Genetec platform to provide a holistic operating picture for operators and may include mobile communications for field response teams. This combination of sensors enables a broader range of detection while decreasing false and nuisance alarms.

Figure 04 - OIAA High Level PIDS Block Diagram

Version 2.0 (April 2022)

PART 1 – PHYSICAL PERIMETER FENCE

1.1 The perimeter shall include a fence or other physical barrier that is resistant to attack, climbing, access below or above. The physical barrier must be inclusive of all areas creating a complete perimeter to a minimum of 10 feet high and include anti-climb features. There may be areas of the SIDA perimeter that includes buildings, retaining walls other structures. Where other structures are part of the perimeter, they shall meet the minimum requirement.

1.2 Chain link sections shall include a concrete base, bottom and top rail, dual outriggers with three stands barbed wire. All chain link sections shall be stretched to meet tension requirements for fence mounted detection systems.

A. Where there is direct access to the fence it shall include:

i. 3-foot K rail base

ii. 5-foot chain ling with 1 inch no climb spacing

iii. Top and bottom rail

iv. 45-degree dual outrigger, with three strand barbed wire topper

B. Indirect access shall include:

i. 8-foot chain link with 1 inch no climb spacing

ii. top and bottom rail

iii. 45-degree dual outrigger with three strand barbed wire.

C. Sections of existing fence, where direct access may exist, anti-ram barriers shall be added.

1.3 Metal fence panels shall be made of welded steel sections no less than 10 feet high with pointed pickets and spaced to deter climbing. Posts shall be at a minimum 4-inch square mounted in at least 2 feet of concrete and a bottom rail installed to deter under fence access.

1.4 Walls shall be made of solid materials such as re-enforced concrete or filled CMU blocks with rebar to minimum of 10 feet with a dual outrigger with three strands barbed wire.

Wall shall be designed to minimize climbing or physical attack.

1.5 All perimeter fence or walls shall meet TSA / FAA physical security requirements.

1.6 Perimeter barrier, either fence or wall, shall have minimum of 10-foot clear zone on each side of the structure.

Version 2.0 (April 2022)

1.7 Vehicle gate entries / exits shall be by controlled by access control and guard verification and include Card and PIN readers, egress with badge only, intercoms and slide gate operators with a guard post.

A. Gate operators shall be HySecurity

B. Operable gates shall include electronic PIDS and status monitored by ACAMS.

1.8 All Perimeter fences shall have signage as directed by OIAA

A. Airport Security Plan (ASP)

1.9 Tenant to provide all material, labor, and inspections required to maintain Perimeter fence

A. Tenant shall maintain the perimeter fence where their operations, renovations or other work impacts the integrity of the physical perimeter fence.

B. Where tenant operations impact the PIDS system, the tenant shall provide any additional equipment, licensing, or work required to maintain 100% coverage of the perimeter.

PART 2 – CORE DESIGN AND SYSTEM COMPONENTS

2.1 Perimeter intrusion detection systems shall consist of multi-tier, overlapping coverage and sensors designed to detect, validate, and track alarms while minimizing nuisance alarms.

2.2 System shall include a single user interface, ease of use and expansion, and an integrated and automated workflow.

2.3 Systems include technology such as but not limited to:

A. Fiber Optic Fence Line Detection

B. Video Management System (VSS)

C. LiDAR

D. Solid State Radar

E. Surveillance Cameras.

2.4 Perimeter intrusion detection system shall provide 100% coverage of fence as well as other related sections.

Version 2.0 (April 2022)

2.5 Perimeter detection system shall have the capability of detecting targets above or below the perimeter fence / wall.

2.6 Perimeter detection system shall be flexible and reconfigurable to add or remove devices or coverage as needed.

2.7 Perimeter detection solution shall have the ability to identify human targets to a minimum of 18 inches in all weather and 24/7/365 reliability.

2.8 System shall have the ability to integrate into Genetec VMS and Lenel access control system and display continuous mapping and active tracking of targets.

2.9 System UI shall support open-source GIS or ESRI GIS. System shall allow third-party integration of stand-ff devices such as Lidar, radar or other volumetric systems.

2.10 Solution UI shall display zones and sub-zones to provide accurate response and detection.

2.11 Solution shall support real-time operational health and reporting of system, (including interfaces and connectivity) and each piece of field equipment and display visible and audible alerts for OIAA maintenance response.

2.12 System panels or controllers shall be IP based and environmentally hardened.

PART 3 – PHYSICAL INFRASTRUCTURE

3.1 All cabling and enclosures shall be suited for purpose, all weather, tamper resistant and secured with approved OIAA lock.

3.2 All enclosures shall include surge protected AC power, monitored for tamper, utility outlet and back plane for equipment mounting and grounded per local codes.

3.3 Fiber shall be installed per requirements and industry standards.

3.4 3All devices shall be design for specific purpose, off the shelf and serviceable with minimum down time or interruption of system integrity.

3.5 Cabinet mounted fiber shall include cable routing and strain relief supports. Cabinet shall allow of top and bottom conduit entries.

Figure 05 – Existing Defined Perimeter

Intercommunication (INTERCOM) Electronic Security Systems Standards

INTERCOMMUNICATION (INTERCOM)

Version 2.0 (April 2022)

PART 1 – INTERCOM GENERAL REQUIREMENTS

Intercom is an integral part of the Airport’s operation and security. An operational intercom allows for simplified communications around the airport for staff and customers on the property.

In this document, intercoms and their uses will be broken down into two main categories:

1.1 Emergency Panic Intercoms - located on stanchions or wall mounted to existing buildings allowing hands free calls for emergencies to the OIAA Security staff.

1.2 Access Controlled Door Intercoms - Intercoms at access control doors and gates to help verify personnel access when access cards are not operational or where alarms have been triggered by accident (extended period of holding the door open).

It is used at SIDA doors to allow for emergency communications and to provide two-way communications between security staff and person requesting access reduces demand on staff to resolve accidental alarms. The intercom provides a level of safety for customers in the parking lots or other surface areas where emergency blue stanchions are located. General use include intercom at access control doors and gates to help verify personnel access when access cards are not operational.

1.3 The Parking Lot intercom shall be AlphaCom by Zenitel. Software shall be the newest version.

1.4 The Intercom System shall be server based and operate on the existing Airport IP network.

1.5 The exchange server shall be located within the Security IDF

1.6 The intercom shall be SIP enabled and support direct connection to SIP appliances.

1.7 The intercom system shall support forwarding of Intercom calls to outside locations via existing SIP enabled phone system

1.8 The Intercom system shall be fully integrated into the Genetec VSS and Lenel ACAMS platform to allow certain personnel to release specific access-controlled doors and gates upon verification of a person’s identity

1.9 The intercom system shall have SIP to allow two-communications between new or existing Voice Over Internet Protocol (VOIP) systems.

1.10 Intercom System shall be composed in its entirety of Commercial off the Shelf products

1.11 The substations shall be vandal and weather resistant stainless-steel stations.

1.12 The system shall have routing and parking to administer emergency calls.

Version 2.0 (April 2022)

1.13 New intercom software and hardware shall be compatible with the existing Zenitel

AlphaCom system.

A. New components shall be native IP based.

B. New exchanges or servers shall be rack mountable.

Figure 06 - Typical Intercom System diagram

PART 2 – INTERIOR STATIONS

2.1 Interior substations shall be located on the unsecure side of the door in a housing or flush mounted in the wall, with back box, close the doorway for ease of operation.

2.2 Substations shall be IP and rated for locations

2.3 Substation shall be fully integrated into the VSS and ACAMS systems.

2.4 Manufacturer

A. AXIS A8105-E Network Video Door Stations or approved equivalent

Version 2.0 (April 2022)

PART 3 – EXTERIOR EMERGENCY STANTIONS

3.1 Wall or pole exterior substations shall be within a weatherproof enclosure

3.2 Substations shall be vandal and weather resistant stainless-steel.

3.3 3Exterior substations will be included in “Blue light” emergency stanchions

3.4 Fiber optic cable shall be used for all exterior intercom substations.

3.5 Manufacturer

A. Zenitel AlphaCom TCIS-1 or approved equivalent

Infrastructure Electronic Security Systems Standards

INFRASTRUCTURE

Version 2.0 (April 2022)

PART 1 – INTRODUCTION

The intent of the infrastructure section of this standards document is to provide design guidance and benchmarks to support OIAA’s security systems’ requirements. All the systems indicated above will require active electronics and/or structured cabling and conduit to enable these systems.

Many of the security systems mentioned above require network infrastructure (section below) and require a properly conditioned environment to operate (temperature and humidity) in addition to the electrical and data connections required to operate.

To enable the security systems indicated above to function properly, it is assumed that the two MDF

Rooms will either need to be retrofitted and expanded or a separate Data Center would need to be built out to accommodate the future needs of OIAA’s security systems.

In addition to the upgrades of to either the MDF Rooms pr a new Data Center there will be the need for numerous additional External IT Enclosures primarily to support the exterior cameras located in parking lots and the PIDS system surrounding the perimeter of the airport.

PART 2 – SUPPORTING ROOMS

Ontario International Airport currently has one Main Distribution Frame (MDF) at each of the two main operating terminals (Terminals 2 and 4) and numerous IDFs and Zone Closets (see definition below) scattered within the two operational terminals, the old terminals, and numerous ancillary buildings (see existing conditions drawings).

The four types of security system spaces supporting the security systems indicated above would fall under the following categories:

1. Main Distribution Frame (MDF)

2. Data Center (DC)

3. Intermediate Distribution Frame (IDF)

4. Indoor IT Enclosure

5. Outdoor IT Enclosure

2.1 MDF ROOMS VS DATA CENTER

The introduction above outlines the need for either a separate Data Center or an expansion of the two existing MDF rooms. Due to the critical systems currently being supported in the existing MDFs and the nature of performing an augmentation to an active IT Room we recommend building out a separate Data Center at the ONT site and connecting it to the two MDFs via independent fiber backbone trunks between each as this would be the lowest risk option to the OIAA and their current operations.

2.2 DATA CENTER

The Data Center will be a dedicated space for head end servers and data storage for OIAA security systems (and potentially other OIAA systems in the future). For the purpose of this standard we’re

Version 2.0 (April 2022) covering requirements as they relate to security systems and their required equipment and infrastructure for proper operation.

It’s assumed that all core switches (servicing edge switches within IDF Rooms and IT Enclosures) would be located within the existing IDF room 1316 at both Terminals 2 and 4. The current MDF and any future Data Center would connect to the two IDF Rooms via Top-of-Rack Switches connecting the two space types via a fiber trunk. See topology below:

Figure 07 – Data Center Topology

The Data Center would be a single space connecting to both MDFs in terminal 2 & 4. Each MDF would connect to the data center via a trunked fiber optic backbone and would have a very similar infrastructure layout as a MDF Room. See Data Center Architectural and MDF/FP requirements below:

Architecture

Size Dependent on storage cabinet quantities and types of cabinets

OIAA requires, typically approximately 18ft. x 25ft

Ceiling 10’ (2.6m) minimum clearance AFF

Lighting 500 Lux at 3ft. (1m) AFF.

Version 2.0 (April 2022)

Doors & Access

Double Door hinged to open outward. 3’ doors each.

Lockable by access control

(See Security below)

Floor Type Anti-static tile, with 12” raised floor for plenum air supply via centralized CRAC

Walls & Partitions

Dust proof finish.

Walls capable of equipment support

Plywood backboards shall be ¾” thick fire rated, painted with rating stamp visible on all walls.

No skirting.

Conduit Sleeve penetrations Min of (8) 4” conduit Sleeves stubbed into the room extending

6” on both sides. (4) 4” conduits to each existing MDF Room

Ladder Rack/Basket Tray

Provide ladder rack anchored to the top of equipment cabinets to support cabinets.

18” Basket tray mounted 12” above ladder rack for fiber backbone cable pathways and support

HVAC

Equipment Centralized CRAC unit with raised floor plenum supply (cold aisles)

Topology Hot aisle and cold aisle topology for air management

Heat Load 4 kW per cabinet

Humidity Control Require 30-55%, 24hrs/day for 365 days/year.

Temperature Control 64° - 75°F 19° - 23°C, with a maximum rate of change not to exceed 3°C in any one hour, 24Hrs/day.

Ventilation Maintain Positive Pressure to mitigate ingress of dust. One air change per hour.

Power

Power Distribution

All power and circuits in the room is to be supplied by the centralized UPS. UPS is to be sized based on room load with

50% additional capacity.

• (1) 120V 30A duplex receptacles dedicated, terminated on L5-30R at every cabinet.

• One (1) 208V, 30A receptacle required at the top of each cabinet.

• One (1) 120V, 20A duplex receptacle required at the top of each rack/cabinet.

• 120V, 20A duplex convenience outlets every 4 feet around the walls of the room.

Power to be fed by conduit from ceiling down.

Convenience Power Outlets

Convenience wall receptacles at minimum 10ft. (3.5m) spacing around perimeter walls. At least one quad receptacle at each plywood backboard.

Emergency Power

Generator power Required on all circuits servicing the data center. E-Power is to be provided to a dedicated electrical panel used only for the data center.

Version 2.0 (April 2022)

Emergency Power Off Button (EPO) Emergency Power Off button to be located by entrance/exit door with protective cover.

Power Load Approximately 4000 watts Per Equipment Rack/Cabinet

Uninterruptible Power Supply (UPS)

Power conditioning and protection capable of maintaining the full room power load for 30 minutes min. Centralized UPS unit either rack configuration or floor mounted.

Grounding and Bonding

Building Grounding

Provide a main telecommunications grounding busbar (MTGB) and bond to the TBB. The sizing of the telecommunications bonding backbone (TBB) shall follow ANSI/TIA/EIA 607-B conductor size and guidelines. Where building steel is accessible and in the same room as the MTGB, bond to the building steel with a minimum No. 6 AWG.

Rack and Cabinet Grounding

Racks and cabinets shall be bonded to the dedicated main telecommunications grounding busbar (MTGB) with a 6 AWG stranded copper wire with green insulation.

Cable Tray and Runway Ladder Bond to the TGB with a 6 AWG stranded copper wire with green insulation.

Fire and Water Protection

Fire Suppression System Oxygen depriving gas system (FM200 or similar) Gas or Water

Pre-action System.

Fire stopping All penetrations through fire rated barriers to…