automated access control system integrator and …

8005453 Automated Access Control System Integrator and Maintenance Services Scope of Work

of 111

Automated Access Control System Integrator and Maintenance Services

Solicitation No. 8005453 Attachment A

Scope of Work - Updated

Dallas-Fort Worth International Airport

September 13, 2021


of 111

TABLE OF CONTENTS 1 INTRODUCTION .......................................................................................................................... 8

1.1 Background ...................................................................................................................................... 8

1.2 Purpose ........................................................................................................................................... 10

2 TERMS AND ACRONYMS .........................................................................................................11

3 REFERENCE DOCUMENTS ......................................................................................................14

3.1 Overview ......................................................................................................................................... 14

3.2 Airport Reference Documents ...................................................................................................... 14

3.3 Federal Regulations ....................................................................................................................... 14

3.4 Industry Standards and Best Practices ....................................................................................... 14

4 QUALIFICATIONS ......................................................................................................................16

4.1 General ............................................................................................................................................ 16

4.2 Company Qualifications ................................................................................................................ 17

4.3 Personnel Qualifications ............................................................................................................... 18

4.4 System Requirements Document ................................................................................................ 18

4.5 Integrator Response ...................................................................................................................... 19

5 SCOPE OF WORK OVERVIEW ................................................................................................20

5.1 General ............................................................................................................................................ 20

5.2 Indefinite Delivery Contract Scope (IDC) .................................................................................... 21

5.3 Automated Access Control System (AACS) Definition ............................................................. 22

5.4 Implementation Strategy ............................................................................................................... 22

6 ROLES AND RESPONSIBILITIES ...........................................................................................28

6.1 Airport Responsibilities ................................................................................................................ 28

6.2 Integrator / Contractor Responsibilities ...................................................................................... 29

6.3 Other Program Stakeholder Responsibilities – Designer ......................................................... 32

6.4 Matrix of Responsibilities ............................................................................................................. 34

7 PROJECT PHASING ...................................................................................................................41

8 SYSTEMS INTEGRATION ........................................................................................................46

8.1 Automated Access Control System (AACS) Background ......................................................... 46


of 111

8.2 Integrations Overview ................................................................................................................... 46

8.3 New Lenel OnGuard PACS Integration with ACMS (HID SAFE) ............................................... 49

8.4 New OnGuard Integration with Existing Picture Perfect ........................................................... 50

8.5 New PSIM Integration with Everbridge ........................................................................................ 50

8.6 New PSIM Integration with HID SAFE .......................................................................................... 50

8.7 New PSIM Integration with the Existing Lenel Picture Perfect ................................................. 50

8.8 New PSIM Integration with the New PACS .................................................................................. 50

8.9 New PSIM Integration with the Existing Qognify NiceVision VMS ........................................... 50

8.10 New PSIM Integration with the Existing American Dynamics Analog Video System ............ 51

8.11 New PSIM Integration with the Existing NICE Inform Audio Recording System .................... 51

8.12 New PSIM Integration with the Existing Zenitel Alphacom Exchange ..................................... 51

8.13 New PSIM Integration with the Existing Parking Control System (PCS) ................................. 51

8.14 New PSIM Integration with Infor ................................................................................................... 51

8.15 Old PSIM (Kaplogic) Integration with the New PACS ................................................................ 52

9 PROJECT MANAGEMENT REQUIREMENTS ......................................................................53

9.1 ITS PMO .......................................................................................................................................... 53

9.2 Contractor’s Project Manager ...................................................................................................... 53

9.3 AACS Integrator Project Plan ....................................................................................................... 53

9.4 Additional Management Plans and Reports Required ............................................................... 54

9.5 Project Execution ........................................................................................................................... 57

10 DISCOVERY/SYSTEM REQUIREMENTS VALIDATION ...................................................58

10.1 Requirements Validation ............................................................................................................... 58

10.2 System Requirements Review ...................................................................................................... 58

10.3 AACS Test Lab ............................................................................................................................... 58

11 SYSTEM DESIGN AND PROTOTYPE ....................................................................................60

11.1 AACS System Design .................................................................................................................... 60

11.2 System Design Review .................................................................................................................. 63

11.3 Prototype and Portal Design and Development ......................................................................... 63


of 111

11.4 User Validation/Configuration Workshops ................................................................................. 64

11.5 PACS Technical Transition Plan (TTP) ........................................................................................ 64

11.6 AACS Implementation / Cutover Plan .......................................................................................... 65

11.7 Final Design Documentation ........................................................................................................ 66

11.8 Critical Design Review (CDR) ....................................................................................................... 67

12 PROCUREMENT .........................................................................................................................68

12.1 Hardware and COTS Software ...................................................................................................... 68

13 SYSTEM INSTALLATION AND TEST ....................................................................................69

13.1 System Installation in Development Environment ..................................................................... 69

13.2 Test Readiness Review ................................................................................................................. 69

13.3 Preliminary User/System Acceptance Test ................................................................................. 70

13.4 Test/Training Environment Installation ....................................................................................... 71

13.5 Implementation in Primary and Secondary Production Environments ................................... 72

13.6 System Cutover .............................................................................................................................. 72

13.7 Endurance Testing ......................................................................................................................... 73

13.8 Operational Readiness Acceptance Test (ORAT) ...................................................................... 74

13.9 PACS Transition Readiness ......................................................................................................... 74

13.10 Final AACS Acceptance ............................................................................................................ 75

13.11 Training Program ....................................................................................................................... 76

13.12 System Administration, Programming, and Monitoring Training ........................................ 77

13.13 User Training .............................................................................................................................. 78

14 WARRANTY AND MAINTENANCE SERVICES ...................................................................81

14.1 General Warranty Requirements .................................................................................................. 81

14.2 Run and Maintain Service Definitions ......................................................................................... 81

14.3 Maintenance ................................................................................................................................... 83

14.4 Maintenance Schedule .................................................................................................................. 84

14.5 Level 1 Maintenance ...................................................................................................................... 84

14.6 Level 2 Maintenance ...................................................................................................................... 85


of 111

14.7 Service Level Agreement Expectations ...................................................................................... 85

14.8 Warranty and Maintenance Service Level Response Times ..................................................... 86

14.9 Software Warranty and Maintenance ........................................................................................... 86

14.10 Warranty and Maintenance Labor Services ............................................................................ 87

15 SUBMITTALS AND DOCUMENTATION...............................................................................89

15.1 Submittal Media Requirements .................................................................................................... 89

15.2 Submittal Log ................................................................................................................................. 89

15.3 Contractor Contacts ...................................................................................................................... 89

15.4 Submittal Quantities ...................................................................................................................... 89

15.5 Delivery Schedule of Submittals .................................................................................................. 89

16 EXISTING AUTOMATED ACCESS CONTROL SYSTEM ....................................................92

16.1 Overview and Background ........................................................................................................... 92

16.2 Existing Automated Access Control System (AACS) ................................................................ 92

16.3 Physical Security Information Management System (PSIM) ..................................................... 92

16.4 Physical Access Control System (PACS) ................................................................................... 93

16.5 Biometric Verification System (BVS) ........................................................................................... 94

16.6 Access Control Management System (ACMS) ........................................................................... 95

16.7 High Security Programmable Smart Key System (PSK) ............................................................ 95

16.8 Radio Frequency (RF) Coded Wireless Remote Gate Control (Genie) .................................... 95

16.9 Call Light / Mantrap System (CLMS) ............................................................................................ 96

16.10 Airport Video System (VMS) ..................................................................................................... 96

16.11 Infrastructure Topology Security Network .............................................................................. 96

16.12 Fire Detection and Alert System .............................................................................................. 97

16.13 Automated Baggage Handling Systems (BHS) ...................................................................... 97

16.14 Electronic Mail Notifications ..................................................................................................... 97

17 ALTERNATE #1 – HARDWARE PROCUREMENT .............................................................98

18 ALTERNATE #2 - COTS SOFTWARE ................................................................................. 100


of 111

19 ALTERNATE #3 - HOURLY TIME AND MATERIAL LABOR ....................................... 101

20 ALTERNATE #4 - REFRESHER TRAINING ...................................................................... 103

21 ALTERNATE #5 - EXTENDED WARRANTY AND MAINTENANCE ........................... 104

22 ALTERNATE #6 – ALTERNATE DELIVERY APPROACH AND PHASING ............... 105,

23 ALTERNATE #7 – PRICING - OPTIONAL/ALTERNATE PSIM SOLUTION ............. 106

24 APPENDIX 1 PSIM WORKFLOWS ..................................................................................... 107

25 APPENDIX 2 AUTOMATED ACCESS CONTROL SYSTEM INTEGRATIONS

SUMMARY MATRIX ........................................................................................................................... 109


of 111

TABLE OF TABLES

Table 1 AACS SOW Summary .................................................................................................................... 24 Table 2 Summary of Work Scope Tasks and Responsibilities .................................................................... 34 Table 3 Summary of Unit Price Based Integrator Tasks and Responsibilities ............................................ 39 Table 4 Procurement Roles and Responsibilities ........................................................................................ 40 Table 5 AACS Example Integrator Implementation Schedule..................................................................... 42 Table 6 Summary Listing of Systems Integrated with the PSIM ................................................................. 47 Table 7 Integrations with New OnGuard PACS........................................................................................... 49 Table 8 Maintenance Schedule ................................................................................................................... 84 Table 9 Submittal Quantities ........................................................................................................................ 89 Table 10 Submittal Delivery Schedule ......................................................................................................... 90


of 111

1 INTRODUCTION

1.1 BACKGROUND

The Dallas/Fort Worth International Airport (Airport) maintains an Automated Access Control

System (AACS) to assist in monitoring and controlling access/egress of secure areas of the

Airport in compliance with Federal Regulation §1542 and high value asset locations of the

Airport in accordance with Texas State Laws, and DFW Airport Policies.

The Airport is the fourth busiest airport in the world, by aircraft movements, and the fifteenth

busiest airport in the world, by passenger traffic. The Airport has an expansive footprint that

occupies an area of approximately 18,000 acres. It hosts critical infrastructure that not only

includes aviation, but also passenger rail, water and wastewater treatment plants, energy

infrastructure, information technology infrastructure and several government facilities. Each is

subject to its own set of federal and state laws and regulations and local ordinances.

The AACS is critical to daily operations. The system is used by Airport staff to manage day-to-

day operations, as well as conduct forensic investigations. The system is used to secure

Terminals, Airport buildings and other outlying facilities.

The Airport is undertaking a project at the Airport to expand, enhance and replace the entire

AACS for the Airport’s passenger terminals, Airport buildings, remote facilities, and vehicle

gates on and around the Airport campus.

The Airport’s existing Access Control System consists of three major subsystems,

independently managed but operates as one single cohesive system. The existing

subsystems include: (1) Physical Access Control System (PACS), (2) Biometric Verification

System (BVS) and (3) Call Light/Mantrap System (CLMS). These will all be replaced as part

of this Scope of Work.

The Airport has solicited proposals for a new Physical Access Control System (PACS)

software platform and has selected “OnGuard®” from Lenel S2, as its state-of-the-art modern,

highly efficient, highly available, flexible, open architecture based Physical Access Control

System software package, capable of running on the latest, encrypted series of the Linux-

based HID Mercury field hardware platform, with the appropriate and specified features,

capacities, and capabilities. This new/y selected PACS platform is intended to fully replace the

existing “Picture Perfect” PACS Software, associated field hardware and the CLMS.

The “PACS System Requirements Specification and Technical Requirements” Matrices

were issued by the Airport in the earlier RFP which was used to select the new

OnGuard® PACS software platform. These matrices provide the requirements and

specifications for the selected Lenel S2 Software. The fully completed LenelS2 System

Requirements Specification and Technical Requirements Matrices SRS Matrices are

reference documents. Authorized LenelS2 integrators will need to obtain their own copies

of these matrices directly from LenelS2 by contacting Eric Joseph

([email protected])

The Airport has constructed a new state-of-the art 24/7 Integrated Operations Center (IOC)

which will consolidate critical airport operations, airport security, and customer service

functions in an open and highly collaborative environment and has selected the Saab SAFE

product for the IOC’s Situational Awareness System (SAS).

mailto:[email protected]


of 111

The Tactical Communications unit (TacComm), which is responsible for 911/Public Safety

Answering Point and security monitoring, is located within the Integrated Operations Center

(IOC). TacComm uses a Physical Security Information Management System (PSIM) as the

primary tool for managing, monitoring, and correlating security system alarms and sensors

and for handling incidents that require security and Department of Public Safety (DPS)

response. TacComm also uses a Computer Aided Dispatch (CAD) for managing 911 calls,

emergencies, medical emergencies, and fires.

The Physical Security Information Management System (PSIM) is a category of software that

provides a platform and applications designed to integrate multiple unconnected security

applications and devices and control them through one comprehensive user interface. It

collects and correlates events from existing disparate security devices and information

systems (video, access control, sensors, intercoms, analytics, networks, etc.) to empower

personnel to identify and proactively resolve situations. PSIM integration shall enable

numerous organizational benefits to the Airport by increased control, improved situational

awareness, and management reporting. The PSIM solution is intended to support improved

efficiency and to improve security through increased intelligence.

One of the objectives of this Scope of Work is to provision a new PSIM solution as part of the

replacement AACS works. This new PSIM will be focused on airport security and alarm

monitoring and security event management functions, and is intended to replace the existing

PSIM.

The PSIM will be the Airport’s primary tool for managing, monitoring, and correlating security

system alarms and sensors and for handling incidents that require Department of Public

Safety (DPS), Airport Security and Customs and Border Protection (CBP) response. The new

PSIM will integrate with the existing and new Physical Access Control Systems, the existing

Video Management (Nice), Identity Management (HID SAFE), Emergency Notification

(Everbridge), Intercom, Audio Management Systems, and othersThe PSIM will also interface

with the existing Computer Aided Dispatch System (CentralSquare) and our Situational

Awareness System (Saab SAFE) for event messaging and coordination purposes (subject to

SSI/CJIS data considerations)..

In implementing a new PSIM, the Airport desires to leverage the existing Saab SAFE

Situational Awareness System (SAS) software platform, implemented at the IOC. The

goal would be for the PSIM to share a unified server environment with SAS, and PSIM

functionality would be configured to provide required security between the two modules

via role based access. The primary contact for the Saab SAFE product, task assistance,

and cost information is Scott Remillard ([email protected]). Please advise the

Airport Board Contact, Shannon Hamilton ([email protected]), if further contact

assistance needed.

In identifying a preferred provider for the PSIM, it is not the intent of the Airport to place

any constraints or exceptions of the preferred provider’s role or performance on

Contractor beyond the desire to acheive a unified and common software and hardware

architecture. It is the Airport’s expectation is that any preferred providers are treated as

any subcontractors under Contractor and that their response fully complies with the

requirements of the RFP, including pricing.

While it is the Airport’s desire to utilize Saab as the preferred provider/manufacturer for

the PSIM, Contractor is free to also recommend other proven PSIM solution options they

believe can meet the functional and integration requirements in a more cost effective.




of 111

If an alternate PSIM solution option is offered, separately tab the Saab solution offering

and the alternate PSIM offering in the Proposal response. Separate Pricing Forms will

be provided for each (see Alternate #7)

Portions of the information related to the AACS, the PSIM, and the implementation of the new

PACS contain Sensitive Security Information (SSI), as defined in Title 49 CFR. Part 1520. This

information must be marked, controlled, protected as such. SSI shall not be released without

the prior written approval of the Airport Department of Public Safety, or their designee.

During the procurement stage for the Replacement Automated Access Control System

Integration and Maintenance Services (AACSI), proposing contractors shall review the

documentation provided to determine and evaluate the Scope of Work to be carried out. Lack

of knowledge of the requirements will not absolve the eventual AACSI Contractor, under any

circumstances, from fulfilling the contractual mandates.

1.2 PURPOSE

The purpose of this Request for Proposal (RFP). is to assist the Airport in selecting an

Automated Access Control System Integrator (AACSI) hereafter referred to as “Contractor”,

who is highly trained, qualified and certified to acquire, install, configure program, integrate

and implement the new Airport selected OnGuard® PACS software platform, which will run on

the most current version of encrypted HID Mercury Controllers and associated field panels, as

well as to implement the new Saab Physical Security Information Management System (PSIM)

supporting security operations for the Airport’s Department of Public Safety (DPS).

The overall objective of this Scope of Work is to implement a state-of-the-art modern

Automated Access Control System (AACS) designed to support security operations at the

Airport.

The AACS Integrator contractor shall provide, on a “turnkey” basis, the new PACS and PSIM,

including all software, and professional services, which includes integration/integrator

services, associated with the PSIM, the PACS, and other related AACS components for

installation, configuration, implementation, system maintenance, and support at the Airport.


of 111

2 TERMS AND ACRONYMS

ACL Access Control List AACS Automated Access Control System AACSI Automated Access Control System Integrator (Contractor) ACMS Access Control Management System (see also IDMS) ACSS Airport Campus Security System AED Automated External Defibrillator AD Active Directory AHJ Authority Having Jurisdiction ANSI American National Standards Institute AOA Air Operations Area AOC Airport Operations Center API Application Program Interface ASC Airport Security Coordinator ASD Airport Security Division – part of DPS ASF Airport Support Function ASOCS Airport Safety & Operations Compliance System ATP Acceptance Test Plan BAS Building Automation System BHS Baggage Handling System BICSI Building Industry Consulting Service International BOM Bill of Materials BVS Biometric Verification System CAD Computer Aided Dispatch CARMA Card Access Report Management Application CBP Customs and Border Protection CDR Critical Design Review CFR Code of Federal Regulations CIR Critical Information Requirement CJIS Criminal Justice Information Services CLMS CBP Call Light /Mantrap System CMP Configuration Management Plan CONOPS Concept of Operations COTS Commercial Off the Shelf CPU Central Processing Unit CRR Cutover Readiness Review CS ITS Control System Group CSV Comma Separated Values CTA Central Terminal Area CUP Central Utility Plant DC Data Center DFW Dallas/Fort Worth International Airport DHS Department of Homeland Security DPS Department of Public Safety DVR Digital Voice Recorder EDS Explosive Detection System EM Emergency Management ENS Emergency Notification System EOC Emergency Operations Center ETAM Energy, Transportation and Asset Management FAA Federal Aviation Administration FIS Federal Inspection Services FOD Foreign Object Detection GIS Geospatial Information System


of 111

GPS Global Positioning System HA High Availability HVAC Heating Ventilation Air Conditioning ICD Interface Control Document ICP implementation Cut-Over Plan IDC Indefinite-Delivery Contract IDMS Identity Management System (see also ACMS) IOC Integrated Operations Center IP Internet Protocol ITS DFW Information Technology Services ITS PMO DFW Information Technology Services Program Management Office KPI Key Performance Indicators LAN Local Area Network LEO Law Enforcement Officer LMP Local Micro Controller Panel LPR License Plate Reader LRR Long Range Card Reader MCR Main Cross-Connect Room MDT Mobile Device Terminal MHTML Multipurpose Internet Mail Extensions Hyper Text Markup Language MTFB Mean Time Between Failures NFPA National Fire Protection Association NIC Network Interface Card NIST National Institute of Standards and Technology OCC CBP’s Operational Command Center (Terminal D) ORAT Operational Readiness Acceptance Test OOS Out of Service OS Operating System OnGuard® PACS Software from Lenel S2 Corporation PACS Physical Access Control System PCS Parking Control System PD Police Department PDF Portable Document Format PP Picture Perfect PACS Software from Lenel PMP Project Management Professional PS Field Panel Power Supplies PSIM Physical Security Information Management System QAP Quality Assurance Plan QOS Quality of Service RAACS Replacement AACS RAM Random Access Memory RCDD Registered Communications Distribution Designer RMP Risk Management Plan RTS Return to Service Saab The sub-prime contractor providing the PSIM and related integrations. SAS Situational Awareness System SAT System Acceptance Test SDD System Design Document SDK Software Development Kit SDR System Design Review SIDA Security Id Display Area SLAN Security Local Area Network SME Subject Mater Expert SRR System Requirements Review SRS System Requirements Specification SSI Sensitive Security Information


of 111

T&E Test and Evaluation Plan TacComm DFW Tactical Communications TIA Telecommunications Industries Alliance TIFF Tagged Image File Format TRR Test Readiness Review TSA Transportation Security Administration TTP Technical Transition Plan UAT User Acceptance Test UL Underwriters Laboratories UPS Uninterruptible Power Supply VAT Vehicle Authentication Technology VCRM Verification Cross Reference Matrix VIP Very Important Person VLAN Virtual Local Area Network VMS Video Management System VPN Virtual Private Network WS Workstation XML Extensible Markup Language


of 111

3 REFERENCE DOCUMENTS

3.1 OVERVIEW

Specific reference in this SOW and the System Requirements Specifications (SRS) to codes,

rules, regulations, standards, manufacturer’s instructions, or requirements of regulatory

agencies must mean the latest adopted edition of each, in effect at the date of contract unless

the document is shown dated.

3.2 AIRPORT REFERENCE DOCUMENTS

The following DFW documents are attached and are part of the specified system

requirements:

Data Security Compliance Provisions (See Contract Provisions)

AACS Integrator System Requirements Specifications (Attachment B)

NIST Special Publication 800-53 Rev 5 (Attachment C)

Data Classification Policy (Attachment D)

System User Administration Policy (Attachment E)

ITS System Disaster Recovery Policy (Attachment F)

The following document, while not attached, is part of the specified system requirements:

The Airport’s PACS System Requirements Specification and Compliance Matrices (as

provided to the Airport by LenelS2 Corporation, for the selected OnGuard® PACS

software platform) Authorized LenelS2 integrators will need to obtain their own copies of

these matrices directly from LenelS2 by contacting Eric Joseph

([email protected])

3.3 FEDERAL REGULATIONS

The following Federal Regulations, while not attached, are considered part of the specified

system requirements.

49 CFR Part 1520 – Protection of Sensitive Security Information

49 CFR Part 1542 – Airport Security

3.4 INDUSTRY STANDARDS AND BEST PRACTICES

The PACS shall meet or exceed the latest requirements of the following:

Federal Communications Commission (FCC):

FCC Part 15 – Radio Frequency Device


of 111

FCC Part 68 – Connection of Terminal Equipment to the Telephone Network

Federal Information Processing Standards (FIPS):

Advanced Encryption Standard (AES) (FIPS 197)

FIPS 201: Personal Identity Verification (PIV) of Federal Employees and Contractors

Homeland Security Presidential Directive 12 (HSPD-12)

Institute of Electrical and Electronics Engineers (IEEE):

IEEE 802.3 – IEEE Standard for Ethernet

National Fire Protection Association (NFPA):

NFPA 70 – National Electrical Code

NFPA 101 – Life Safety Code

Security Industry Association (SIA)

Open Supervised Device Protocol (OSDP)

Telecommunications Industries Alliance (TIA):

TIA-232-F – Interface between Data Terminal Equipment and Data Communications

Equipment Employing Serial Binary Data Interchange

TIA-485-A – Electrical Characteristics of Generators and Receivers for use in Balanced

Digital Multi-Point Systems

Underwriters Laboratories (UL):

UL 294 – Access Control System Units

UL 1076 – Proprietary Burglar Alarm Units and Systems


of 111

4 QUALIFICATIONS

4.1 GENERAL

All Automated Access Control System Integrator aka “Contractor” installation and service

personnel shall be required to obtain and maintain a current and valid Airport SIDA badge

prior to disclosure of any airport security system Sensitive Security Information (SSI), access

to any Airport AACS related systems, or Terminal Facilities. Integrator personnel who will

require access to the Airport’s IOC and the CAD System will require CJIS certification.

Integrator personnel who will require access to the Airport’s FIS facilities Customs Security

Area (CSA) must also apply for and have a Customs and Border Protection (CBP) Zone 1

seal. The Integrator must also maintain bonds in accordance with CBP bond requirements.

All Integrator/Contractor personnel are obligated to uphold all federal, state, local, and Airport

policies regarding the security of the Airport.

Sensitive Security Information (SSI) Management Plan - All responses to this RFP, must

provide the firm’s Sensitive Security Information (SSI) management plan which must include

and document.

Protection of SSI

Properly marking SSI

Password protection criteria for SSI

Logging and control of SSI documents

Destruction/deletion of SSI documents

How all team members will be trained on SSI

Cyber Security Plan - All responses to this RFP, must include detailed information on the

following.

How data/information is safeguarded at your company.

What types of client information are stored in the Cloud?

The type of documented information security policies that your firm has in place.

The types of training provided for Information Technology Security and/or Cyber Security.

How annual information security penetration tests of your IT systems are conducted and

if an independent third party is used.

Your company’s current information security management policy and how it’s enforced.

Your company’s third-party management strategy or policy.

Individuals responsible for managing third-party vendor compliance with your information

security protocols.


of 111

Third-party vendors you would share DFW information with.

Security practices in place to safeguard the confidentiality of DFW information with third-

party vendors.

Security incidents or events with a third-party vendor over the last 3 years.

4.2 COMPANY QUALIFICATIONS

The Texas Department of Public Safety requires that portions of the access control system

installation and maintenance, defined as regulated under the provisions of SB 1252, 78th

Legislative Session of the State of Texas, be performed by an integrator holding a valid and

current Class B Security Contractor Company License. Proof of valid license shall be provided

with the bid response.

The Airport has selected OnGuard® by LenelS2, to replace the existing Airport Physical

Access Control System (PACS) platform. The AACS Integrator shall be a highly trained, Lenel

Certified Expert (LCE) level VAR partner at the highest tier in products and services

associated with LenelS2 Access and Database tracks. Only LenelS2 Certified technical staff

shall be authorized to work on the AACS.

As part of the Contractor’s response to this RFP, the firm, as a LenelS2 VAR, shall

provide documentation that they have multiple technicians who will be assigned to this

AACS Integration project that have been through Lenel S2 OnGuard® certification

training program and have been LenelS2 OnGuard Certified “Professional” (LCP) or

higher in the Access, Database, and Intrusion Tracks. Only Lenel Certified engineers and

technicians will be authorized to work on the system. Contractor shall submit a list of

how many engineers / technicians they have at each tier with their name,

training/certification level, and training expiration date.

The Integrator firm, and staff shall maintain all certifications at the Lenel Professional

(LCP) and Expert (LCE) tier, for the duration of their engagement at DFW Airport. Such

certifications and provisions shall not, at any time, preclude the Airport from obtaining

support, or training directly from the manufacturer.

The Airport has selected the Saab SAFE product as its Situational Awareness System (SAS)

software platform. A new Saab PSIM would be built on this software platform and shall be

configured using the workflows provided in Appendix 1, to this SOW and in accordance with

the AACS System Requirements Specifications, attached. The AACS Integrator “Contractor”

will be responsible for obtaining all the required professional services and associated licenses

from Saab, who shall be considered a sub-prime integrator to the Contractor for the new

PSIM.

The Contractor shall be responsible for coordinating and managing all aspects of the

PSIM implementation, startup, integration, testing, training, transitioning, and

maintenance support. It is anticipated that the Contractor shall partner with Saab for the

duration of their engagement at DFW Airport. This necessary partnership shall not, at any

time, preclude the Airport from obtaining support, and training, directly from Saab.

The Airport intends to select a Contractor that is an integration firm (AACS Integrator)

regularly engaged in the installation of Electronic Access Control systems at Category X

Airport, or similar high security, large campus installations and have greater than five (5) years


of 111

of installation, configuration, and programming experience with the OnGuard® PACS software

platform and related HID® Mercury Security hardware. References provided shall document

that at least three (3) of these systems shall have been in continuous operation for at least 12

months.

4.3 PERSONNEL QUALIFICATIONS

Installation and service work on the DFW Physical Access Control System must be performed

by personnel licensed under Texas Occupational Code 1702, or the work must be performed

under direct supervision of, and inspected and certified by, a person under contract with the

Airport, who is licensed to install and certify the work, and who will assume full responsibility of

the installation and service work.

Where applicable, the Integrator shall have a BICSI Registered Communications Distribution

Designer (RCDD) review and supervise all work on-site. The BICSI Technician must

demonstrate knowledge and compliance with all applicable BICSI, TIA, UL, and NFPA

standards and codes. The BICSI RCDD Technicians may be subcontractors of the Integrator.

With their response to this RFP, prospective integrators are also required to submit the

personnel qualifications listed in section 4.3 as evidence of qualifications. The Contractor

shall submit a list of how many technicians they have that meet the above registrations

and license requirements with their name, license /registration, and associated

expiration date.

The firm, and technical staff shall maintain all registrations, certifications, and licenses for

the duration of their engagement at the Airport.

4.4 SYSTEM REQUIREMENTS DOCUMENT

To be responsive, each Integrator must completely fill out the attached “AACS System

Requirements Specification” document which can be found in Attachment B to this Request

for Proposal (RFP).

The “AACS System Requirements Specification” document describes the AACS architecture

requirements, functional requirements, information security requirements, system

administration requirements, and system performance requirements of the system. The

responses will be reviewed by the selection committee and used for scoring.

The Airport Requirements section of the “AACS System Requirements Specification”

document includes a list of desired features and capabilities of the replacement AACS. The

importance of each feature to the Airport is indicated as follows:

Mandatory (M)

The feature is a mandatory Airport requirement and must be present within the system

PRIOR to being placed into production.

Optional (O)

The feature is optional, but not necessarily an immediate need. If implemented, it will be

done under the IDC portion of the contract.


of 111

Future (F)

The feature is identified as a future requirement; however, it does not need to be initially

present. If implemented, it will be done under the IDC portion of the contract.

4.5 INTEGRATOR RESPONSE

The Integrator response section in the “AACS System Requirements Specification” provides

an area where respondents are required to indicate their Full Compliance or provide an

Exception or Clarification to each requirement, feature, or capability.

In the comments /explanation section of the Integrator Response, for Fully Comply and

Exception or Clarification response, the Integrator shall provide, explanatory comments

and/or provide a reference to any separate (and formally identified) attachments as required

and/or any additional documentation, as needed, to support any of the responses provided.

The respondent should articulate capabilities or functionality above and beyond the basic

requirements stated in the document. Additional capabilities or functionality offered may

be used as differentiators when selecting an integrated solution that can meet the long-

term requirements of the Airport.


of 111

5 SCOPE OF WORK OVERVIEW

5.1 GENERAL

The Automated Access Control Integrator (AACSI) “Contractor” shall provide, on a “turnkey”

basis the new Physical Security Information Management System (PSIM), and the new

Physical Access Control System (PACS). The scope of work includes but is not limited to: the

project management, quality assurance, design, software, configuration, interfaces,

installation, integration, implementation, testing, commissioning, system cut over/transitioning,

training, training materials, warranty, As-Built documentation, manuals, and maintenance for

the replacement AACS at the Airport.

The replacement AACS is focused on airport security, controlled access, alarm monitoring,

and associated functions. It will provide access control transaction and alarm tracking,

associated response management, security data aggregation, reporting and dashboard views

for security events.

The technical requirements for the AACS, and the new PACS are detailed in the “DFW

PACS System Requirements Specification and Compliance Matrices” and must be

obtained from LenelS2.

The technical requirements for the replacement AACS are detailed in the “AACS System

Requirements Specification,” which can be found in Attachment B to this Request for

Proposal (RFP).

The new Lenel OnGuard PACS shall be integrated with the existing ACMS (HID Safe Identity

Management System), existing Picture-Perfect Access Control System, and the new Saab

Physical Information Management System (PSIM) and will be part of DFW’s replacement

AACS. For reference, details of the existing AACS can be found in Section 16 of this SOW.

The Automated Access Control System Integrator’s scope includes, but is not limited to:

Providing, installing, programming, and configuring the new PSIM System, utilizing the

Saab SAFE software platform (preferred; see Section 1.1 above)Providing, installing,

programming, and configuring the new Lenel S2 OnGuard® PACS software,

Providing integration services associated with the PSIM, the PACS and the other related

AACS components,

Supporting the startup, installation, programming, configuration, training, phased cutover,

and transition from the existing PSIM and PACS to the new systems, and all associated

maintenance and warranty as defined herein.

Deliver run and maintain services for all implemented AACS related systems, with

minimum impact to System Service Availability.

Provide run and maintain services for support related systems which include

development and testing environments and the production systems and environment.

Provide, as required, SME support and recommendations for implementation of new, and

enhanced products and services as the AACS PACS software and hardware migrate

from existing to new.


of 111

5.2 INDEFINITE DELIVERY CONTRACT SCOPE (IDC)

The Airport desires the contractor to provide support for ongoing installation, testing, selection

support, additional future integrations, the addition, or removal, of AACS components, on an

as required basis.

All Work under this Contract must be authorized under individual Delivery Orders (DO) issued

by the Procurement and Materials Management Department (PMM). The total amount of all

Delivery Orders issued under the Contract shall not exceed the then not-to-exceed amount of

the Contract. Contractor shall not be authorized to begin work until a DO is issued by PMM

nor incorporate changes to the scope of work unless authorized by DO revision issued by

PMM.

A Delivery Order (DO) is a unit of work authorized under the Contract. A DO will detail the

agreement between the Board and the Contractor for work to be performed and will include

scope of work, physical location, performance time, pricing, and other specific criteria. DO

numbers are assigned beginning with the last four digits of the contract number, then the

delivery order sequence, followed by a delivery order revision sequence, if applicable, i.e.,

“4978-001R00”.

Each request will require a task requested by the Airport’s Technical Representative. The

Airport will provide the Contractor a scope of work for the individual requirement.

The Contractor must then prepare and submit to the Airport a Proposal further defining

and restating the scope and providing a line-item proposal of the individual tasks,

quantities, and cost in accordance with established unit pricing under the appropriate

schedule. DO proposal preparation work, including all time, labor, and expenses, shall be

at no cost to the Board.

The DO Proposal pricing will include all costs to perform the work including, but not be

limited to materials, labor, overhead, and profit.

Contractor shall respond to task requests in no more than seven (7) calendar days

unless otherwise agreed with the Airport Project Manager.

For each DO, the Contractor shall assign a project manager to be in charge of the Project

and act as liaison in all aspects of the performance of the work.

Typical requests will be for adding, removing, repairing, and changing any door type

configuration, equipment placement or configuration, as well as supporting an AACS

device/component selection process.

Quoted work shall be for near accurate estimates. IDC shall be remunerated based on

actual verified time and material per Contract Administrator’s (CA) direction.

Permits and fees shall be reimbursed by the Airport at actual cost.

All building codes and inspections will be adhered to.

Contractor shall provide actual time period required to perform each task, including

product delivery time, and must include all work required to complete.

Notice to proceed for each IDC request will be issued by the Contract Administrator.


of 111

If a Change in Scope occurs after a DO has been executed, PMM will negotiate a revision to

the DO, with concurrence by the Board representative requesting the work. After an

agreement has been reached, PMM will issue a DO Revision outlining the revised DO

agreement to the Contractor. The M/WBE goal for individual DOs is set at the same

percentage as provided for the contract’s M/WBE commitment percentage. That percentage

shall be applied to the cost of each DO.

Work executed under a Delivery Order will be performed in accordance with the scope and

terms of the Contract.

Each DO will be a supplement to this Contract. The Contractor will be required to complete all

work according to the provisions contained in the DO and this Contract. In the event of a

conflict in the language of this Contract and the language of the Delivery Order, the language

of this Contract shall control, unless and the DO explicitly states otherwise.

5.3 AUTOMATED ACCESS CONTROL SYSTEM (AACS) DEFINITION

The Automated Access Control System (AACS) consists of six (6) major independent

subsystems which, as integrated, essentially operate as one system. These subsystems

include:

Physical Security Information Management System (PSIM)

Physical Access Control System (PACS)

Biometric Verification System (BVS)

Access Control Management System (ACMS) – Also known as the SAFE IDMS.

High Security Programmable Smart Key System (PSK)

The Airport’s Video Management System (VMS) is not formally part of the AACS but it is

included in this definition, as it is required to support the AACS, and is an integral part of

the PSIM.

The AACS provides access control and monitoring for greater than 2300 portals. The PACS

shall provide for a scalable solution, sized to support configurations consisting of a minimum

of 3,000 thousand Portals, 60,000 active credentials utilizing multi-factor authentication,

140,000 total badge holders, with an estimated 150,000 badge transactions per day, in

facilities spanning multiple geographic areas.

5.4 IMPLEMENTATION STRATEGY

The implementation strategy calls for the new AACS, the new OnGuard PACS, the new Saab

PSIM, listed Integrations, and transition of all system portals, to be implemented incrementally

in four (4) phases. Table 1 AACS SOW Summary, below summarizes the project’s life cycle

activities, milestones and deliverables that will be required of the Contractor, during each life

cycle stage for each phase of the project.

The Airport requires that the time frames associated with each phase be optimized with tasks

being accomplished in parallel to the greatest extent possible. The Phases are listed below.


of 111

Phase 1 – Implementation and configuration of the new PACS

Phase 2 – Implementation and configuration of the new PSIM software

Phase 3 – Device Selection, Integration, and new AACS acceptance testing

Phase 4 – PACS Device installation, Door by door transition, testing and acceptance

The Airport is interested in an Alternate Delivery Approach, if feasible, which would allow

doors to be delivered at the earliest possible time. Contractor shall provide an outline

approach and include pricing as an Add Alternate.

See Project Phasing Section (7) below for additional information.


of 111

Table 1 AACS SOW Summary

System Life Cycle Phase

Project Management

Requirements Validation

Design and Development

Selection Installation

and Test Training

Warranty and Maintenance

Activities

Kickoff Meeting

PACS Stakeholder Requirements Workshops

PSIM System Design

Field Power Supplies (PS)

AACS Test LAB

PACS Software User Training

PSIM Configuration Management

Status Reports

PSIM Stakeholder Requirements Workshops

PACS: Program, Configuration

PACS Media (Card)

Install PACS and PSIM in Development Environments

PACS / Mercury Field Panel Training

PACS Configuration Management

Status Meetings PSIM Interface Definition(s)

PSIM Prototype Development


PACS UAT/SAT

PSIM User Training

PSIM Software Maintenance

Coordination Meetings

AACS Interface Definition(s)

PACS Prototype Development

Card Reader PSIM UAT/SAT

PACS Admin Training

PACS Field Panel Maintenance

Maintenance Support /Status Meetings

PACS Business Rule Definition

Install PSIM in Training Environment

Long Range Reader (LRR)

Install PACS and PSIM in Test/Training and Production Environments

PSIM Admin Training

PACS End Device and Door Hardware Maintenance

Respond to IDC Service Requests

PSIM Business Rule Definition

AACS User Validation Workshops

Vehicle Authentication Technology (VAT)

Validation Tests (PACS & PSIM) in Test/Training and Production Environments

PSIM Workflow Validation

Final PSIM System Design

High Security Programmable Smart Key (PSK)

PACS ORAT 2nd Level Support

Final PACS Configuration

PACS 60 Day Endurance Test

3rd Level Support

PSIM ORAT


of 111


Project Management




and Test Training


PSIM 60 Day Endurance Test

PSIM System Cutover

PACS Door by Door Transition

Milestones

PSIM SRR PSIM SDR Selection of a PS

PACS TRR

PACS SRR PACS SDR Selection of PACS Media

PSIM TRR

PACS CDR Selection and Implementation of PACS Reader

PSIM CRR

PSIM CDR

Selection, integration, and Implementation of a BVS

PSIM IOC

AACS Final System Configuration

Selection, integration, and Implementation of an LRR

Selection, integration, and Implementation of a VAT

PACS Transition Complete

Selection, integration, and Implementation of a PSK


of 111


Project Management




and Test Training


Deliverables

Project Plan SRS SDD IDC Pricing UAT/SAT Test Report

PACS Software Training Manuals

Monthly Maintenance Management Report

Project CMP Hardware BOM ICDs for each interface and integration

Test and Evaluation Plan

ORAT Test Report

PACS / Mercury Hardware Training Manuals

SLA

Quality Assurance Plan

VCRM VCRM

PSIM System Software Manuals

PSIM SW Licenses

Risk Management Plan

HDW BOM PACS User Manual

PACS SW Licenses

Communications Plan

COTS Software BOM

PACS System Admin Manual

Project Status Reports

Technical Transition Plan

PSIM System User Manual

Maintenance Management Reports

ATP

PSIM System Admin Manual

Maintenance Status Reports

Training Plan PACS O&M Manual

Project Problem Escalation Procedures

AACS IT Security Plan

PSIM O&M Manual

Meeting Minutes Implementation Cutover Plan

PSIM As-Builts


of 111


Project Management




and Test Training


IDC Service Request Pricing

PSIM DR Procedures & Plan

PACS As-Builts

PACS DR Procedures & Plan

Licenses

Maximum use shall be made of Commercial Off the Shelf (COTS) hardware and software, standardized material and equipment, end-

user enabled configuration capabilities, and open integration standards for interfacing the AACS with other Airport systems and

subsystems.

The new PSIM, PACS and resultant integrated replacement AACS shall meet or exceed the requirements and specifications (see

section 3.2 Airport referenced documents for the AACS and PACS SRS documents). Alternatives or variations proposed by the

contractor shall be fully documented and clearly costed, defined, and supported so that the suitability, compliance, equivalence, or

superiority can be readily determined by the Airport during the proposal evaluation.

The new System’s design, configuration, programming, materials, and workmanship shall be in accordance with the latest standards,

best commercial standards, practices, and state of the art equipment available on the market at time of delivery.


of 111

6 ROLES AND RESPONSIBILITIES

6.1 AIRPORT RESPONSIBILITIES

The Airport will provide a project manager for this Integrator Contract (see Section 9) who will

be the primary Airport POC with the Integrator to manage and coordinate all Technical Issues

associated with the AACS. See Table 2 Summary of Work Scope Tasks and

Responsibilities, and Table 3 Summary of Unit Price Based Integrator Tasks and

Responsibilities.

The Airport will contract with a Design Firm that will fully develop the Replacement AACS

(RAACS) project design and construction documents which will be used to construct the

System. See Table 2 Summary of Work Scope Tasks and Responsibilities, and Table 3

Summary of Unit Price Based Integrator Tasks and Responsibilities.

The Airport will contract with a Construction Manager at Risk (CMAR) Firm that will be

responsible for all construction activities associated with the transition and replacement of the

exiting PACS to the new PACS. See Table 2 Summary of Work Scope Tasks and


Responsibilities.

Airport will provide a staging/storage location for all equipment ordered and delivered

associated with the new PSIM System and the new PACS, associated with this Integrator

Contract.

For the specified development, test/training, and production environments the Airport will

provide the following:

Hardware and COTS software procurement

Rack space in data centers

Internet Access

Network connections and LAN configuration

Firewall and security appliance configuration

All Infrastructure needed to support the new AACS, including the PSIM and PACS

implementation

System administration: The server environment will be managed by DFW ITS and

monitored via the applications manager monitoring tools.

1st level server and associated network infrastructure maintenance support and Solutions

(Help) Desk for the AACS.

General information on the existing systems can be found in Section 16 of this SOW, After

award, the Airport will provide most current information regarding existing AACS and its


of 111

associated sub-systems that the new PSIM and PACS will need to integrate with, as well as

access to existing system support contractors for coordination.

The Airport will provide workspace for Development Test Lab workstations (3) and associated

Development Field Hardware.

The Airport will provide space for Test/Training/Demo Lab to accommodate at least 7

workstations and associated Test / Demo Field Hardware through the duration of the contract

and the warranty period.

The Airport will supply and install all workstations and monitors for the AACS in all

environments.

The Airport will procure and install all hardware and COTS software as specified by the

contractor to meet the new PSIM and PACS requirements.

The Airport has an existing AACS maintenance contractor (integrator) that is currently and will

remain responsible for maintaining and supporting the existing Picture Perfect PACS software

and field hardware (LMPs).

The Airport currently provides maintenance support to the existing Kaplogic AEGIS PSIM and

will remain responsible for maintaining and supporting this existing PSIM.

The Airport confirms that the Airport shall not contract with, or allow any other party to

integrate components, equipment, or processes into the new AACS, or any of its subsystems

during the Contractor’s period of performance without prior approval of contractor, which shall

not be unreasonably withheld, provided it becomes necessary to provide the security required

of the Airport. Contractor shall facilitate the expansion of any component of the system and

maintain such under this Contract.

The Airport shall be responsible for performing all user maintenance as defined in this

specification and for performing maintenance on the following:

Existing Kaplogic PSIM servers, workstations, and associated integrations.

All existing PP PACS LMP Field Panels and associated power supplies; up until the point

where, at each LMP location, all doors have been completely transitioned to the new

PACS Field Panels for that location, at which time the Contractor shall coordinate with

the Airport’s Technical Representative, who will direct the existing AACS Maintenance

Contractor to remove the existing LMP.

All Door hardware and associated AACS “Field Devices”, up until transition of each door

from the existing Picture Perfect PACS to the new Lenel OnGuard PACS, at which time

the warranty and maintenance responsibility also transitions to the Contractor under this

contract.

All Airport owned Fiber Optic cable used to connect the components of the existing

PACS, PSIM and the new PACS and PSIM.

6.2 INTEGRATOR / CONTRACTOR RESPONSIBILITIES


of 111

The AACS Integrator/Contractor shall provide a project manager for this Contract, who will be

the primary Airport POC with the Board, to manage and coordinate all Contractual and

Technical Issues. The Contractor shall be responsible for supporting and coordinating the

Contractor’s responsibilities as defined in Table 2 Summary of Work Scope Tasks and


Responsibilities

Badging of all Contractor personnel as necessary to perform the work under this contract.

Obtaining CJIS certification for personnel whose work efforts are associated with the CAD

System, or who will require regular access to the IOC.

Implement, configure, program, integrate and test the new AACS as specified herein, and as

required, based on Airport Approved 100% AACS Construction Documents. Based on this

SOW and the associated referenced SRS documents, Contractor shall prepare System

Design Document (SDD), and associated plans specified for software and equipment to be

implemented.

As part of this Scope of Work, Contractor shall participate in meetings and workshops

with the Airport’s AACS design firm to coordinate work and to understand and provide

SME/integrator inputs in support of edge device decisioning of units that will be part of

the PACS.

Provide the specified software based on approved SDD.

Provide any Hardware or Software the Contractor needs for design, development, and

configuration tasks.

Provide all application software licensing required, including any transitional licensing to

support operations during migration, as may be required.

Using the information provided by Lenel S2, for the DFW OnGuard PACS Platform, specify all

hardware (types and quantities) and COTS software licenses required to implement the new

OnGuard PACS in all 3 environments. See Table 4 Procurement Roles and Responsibilities.

Using the information provided by Saab Inc., specify all hardware (types and quantities) and

COTS software licenses required to implement the new Saab based PSIM workstations. See

Table 4 Procurement Roles and Responsibilities. It must be noted that the new PSIM will be

built on the existing Saab SAS Platform, which currently exists in 3 environments.

Load all software required and applications specified, including all patches required to bring

the new Saab PSIM and OnGuard PACS software to latest release levels.

Configure the new AACS (including the new PSIM and new PACS) to support the associated

approved SDDs. This includes general and event / incident management protocols,

development of business rules, workflows, response plans, portal configurations, interlocks

and programming, man machine interface screens, integrations, reports, and audit

configurations for the new PSIM and PACS in order to provide for full functionality of the new

AACS.

Provide all design, engineering, programming, installation, and technical services in support of

hardware and end device selection and associated testing as directed by Airport, as listed in

Table 2 Summary of Work Scope Tasks and Responsibilities.


of 111

Provide all design, engineering, programming, and technical services for the development and

testing of interfaces and integration. Coordination with all required Airport System contractors

for purposes of interface development and systems integration.

Test and verify all system components to ensure conformance with specifications. This

includes testing of application on all desktops (provided by Airport ITS).

Provide end device support and assistance to maintain network switching and connection to

properly connect any segments of the AACS installed/maintained under this contract to the

Airport Security LAN. Devices installed/maintained under this RFP will communicate over

single mode fiber between all facilities and the designated ITS data centers.

Cutover the new PSIM system to operational status, to include migration of existing data in old

system, as applicable, to new PSIM application. This will form the basis for the new Airport

AACS.

Cutover PACS software and associated field hardware to operational status, including

migration of existing data in old / existing systems to the new PACS application, as applicable.

Configure software, hardware, and network components to provide logging, monitoring

and audit reporting capabilities on confidentiality, integrity, and availability of data/information

for the configured environment to limit vulnerability and ensure compliance with organizational

and security standards.

Provide, in a reasonable and timely manner, IDC pricing, as requested and required, for labor

and material involved with adding, removing, repairing, and changing any door type

configuration, equipment placement or configuration, as well as supporting an AACS

device/component selection process.

Contractor shall maintain factory and/or manufacturer trained, and certified full-time

employees qualified to perform remedial and preventive maintenance on all components of

the new AACS. Contractor may use sub-contractors to meet parts of this requirement provided

all Board requirements of this Scope are maintained.

Contractor shall maintain necessary equipment, supplies, transportation, and material

necessary to maintain the performance of the new AACS within normal operating parameters.

Fully and completely document the configured environment.

Train system administrators, operator/users, and maintenance support staff, prior to Cutover,

and provide refresher training, as required throughout the warranty period.

Participate, as a subcontractor to the CMAR, and provide, installation, commissioning,

transition, and documentation support for all field related PACS control panels and electrical

door hardware.

Participate, as a subcontractor to other future AACS related construction projects to provide,

installation, commissioning, and documentation in support of future PACS field control panels

and electrical door hardware, based on submitted unit costs. See Table 3 Summary of Unit

Price Based Integrator Tasks and Responsibilities


of 111

Coordinate and cooperate with any required System adds, moves, outages and changes as

required.

Coordinate with the Board’s Technical Representative, about access to, and support for, all

existing PP AACS LMP Field Panels and associated power supplies, up until the point where,

at each LMP location, all doors have been completely transitioned to the new PACS Field

Panels for that location. At that time, the Contractor shall request that the Airport remove and

salvage the existing LMP and all associated boards, power supplies and cabinets.

Coordinate with the Airport’s Technical Representative, with regard to support for, all door

hardware and associated AACS “Field Devices”, up until transition of each door from the

existing PP PACS to the new PACS at which time the warranty and maintenance

responsibility also transitions to the Contractor.

Contractor shall provide a 12-month period of warranty for all software, hardware, and

components of the new AACS that are installed under this Scope of Work beginning at the

date of final system acceptance by an authorized representative of the Board.

Contractor shall provide maintenance support as defined in this Scope of Work, as necessary

to keep the new AACS and each subsystem in good working order during the period for which

maintenance services are authorized. Contractor’s Period of performance for maintenance

support shall begin upon successful completion of the system stress tests.

Contractor shall perform a full and complete preventative maintenance service on the new

AACS in compliance with the requirements of this Specification.

The first preventative maintenance, service shall begin with the first month following

Airport acceptance of the transitioned system components to the new AACS and shall

occur every year thereafter for the term of the contract.

Contractor will provide agreed upon reports as required by the Airport at each preventive

maintenance service on the AACS.

For routine, ongoing maintenance, Contractor shall provide the Airport with a status report in a

form approved by the Airport that includes a summary of all site activity and client requests.

6.3 OTHER PROGRAM STAKEHOLDER RESPONSIBILITIES – DESIGNER

The AACS Designer is responsible to:

Provide facilities and infrastructure requirements confirmation and design associated with

the replacement AACS locations including door details, communication room updates,

and cable pathing.

Facilitate the selection process for AACS devices and provide SME input in conjunction

and coordination with Contractor to assist the Airport in making decisions and providing

approvals; Devices will include:

Indoor and outdoor field panels

Power supplies


of 111

Card and card readers

Long range card readers

Vehicle Authentication Technology

Biometric Verification System

Programmable Smart Key System

Assist the AACS Program Team, Integrator Contractor, and Airport Stakeholders to

develop the Program’s System Transition Plan. Specific roles and documentation

responsibilities will be finalized once all working groups are on board and workshops are

underway.

.


of 111

6.4 MATRIX OF RESPONSIBILITIES

The following table summarizes the Automated Access Control System Integrator / Contractor work scope tasks and related

responsibilities

Specific roles and documentation responsibilities are subject to adjustment and will be finalized once all working groups are on board

and workshops are underway. In particular, this table will be also expanded to incorporate DFW ITS roles and responsibilities

Table 2 Summary of Work Scope Tasks and Responsibilities

CONTRACTOR SCOPE Task Summary List

AACS PROJECT MATRIX Post AACS Project

REF No

CONTRACTOR (Board

Contract) Design DFW CMAR

Unit Cost CONTRACTOR

(CMAR Contract)

Door Maint. (DFW)

ITS AACS Maint.

Contractor

1 Develop Door Details Lead Approve

2 Develop Indoor and Outdoor Field Panel Designs

Review Lead Approve

3 Develop Project Technical Implementation Plan and WBS

Lead Support Approve

4

Design Process Documents, Approvals for Code and Permits, in support of Construction Package

Support Lead Approve

5 Constructability Reviews - Prior to CMAR

Support Lead Approve

6 Furnish and Install New AACS Software



of 111



REF No

CONTRACTOR (Board



(CMAR Contract)

Door Maint. (DFW)

ITS AACS Maint.

Contractor

7 Configure Software /Servers for three (3) Environments


8 Integrate with PSIM and Test (integrate all designated systems)


9 Integrate with SAFE IDMS and Test


10 Import PP / CARMA History and Test


11 Migrate Existing PP Portal Configurations to new per design and Test

Lead Review Approve

12 Program / Configure DFW PACS

Lead Review Approve

13 Configure and Set up Test Lab (Including DEMO Lab)

Lead Review Approve

14 Select Power Supplies and related components

Support Lead / Facilitate Approve

15 Select Card and Card Reader Support Lead / Facilitate Approve

16 Select Long Range Gate Reader


17 Select Vehicle Authentication Technology


18 Select Biometric Verification System and device


19 Integrate Biometrics with PACS, SAFE IDMS & PSIM and Test

Lead Review Approve


of 111



REF No

CONTRACTOR (Board



(CMAR Contract)

Door Maint. (DFW)

ITS AACS Maint.

Contractor

20 Select Programmable Smart Key


21 Integrate new PSK with IDMS and Test

Lead Review Approve

22 Integrate IDMS / PACS with Vehicle Authenticator

Lead Review Approve

23 Furnish and Install PSK Components at AccessDFW & Test LAB

Lead Review Approve

24

Furnish and Install Test Lab field devices, Biometric devices, field panels, test door hardware and power supplies

Lead Review Approve

25 Configure /Setup up and Test Doors for Evaluation (Lab and Demo)

Lead Review Approve

26 Test DFW PACS Software with All Integrations and field hardware (Lab and Demo)

Lead Review Approve

27 Programming of all doors per AACS Design

Lead Review Approve

28 System Transition Planning Lead Support Approve Support

29 CMAR Constructability Reviews / GMP/ Construction & Transition

Review Approve Lead Support

30 Furnish and Install Power and Data Cable and Conduit in support of Indoor and Outdoor



of 111



REF No

CONTRACTOR (Board



(CMAR Contract)

Door Maint. (DFW)

ITS AACS Maint.

Contractor

Field Panel Designs in the Field

31

Furnish and Install Field Panels / intelligent controllers and related Power Supplies and associated components

Review Approve Support Lead

32 Furnish / Install / selected Card Readers in the Field per design


33 Furnish / Install selected Long Range Gate Readers in the Field per design


34 Furnish / Install / selected Biometrics Devices in the field per design


35 Furnish and Install selected PSK Cores in the field per design


36 Install conduit and cable at existing door, as required by design


37 Wiring of existing Door using existing Door Hardware per design


38 Door Conversion and Commissioning - existing door

Support Review Approve Support Lead


of 111



REF No

CONTRACTOR (Board



(CMAR Contract)

Door Maint. (DFW)

ITS AACS Maint.

Contractor

39 New /Changed Partition Wall - Including Conduit / Wire as needed


40 New Door / Frame / Mech Hardware


41 Install Conduit / Cable and Boxes for new Door


42 New Door Electrified Door Hardware / Card Reader / Devices


44 Commissioning new door Support Review Approve Support Lead

45 Warranty Support (During AACS Project)


46 Warranty/Maintenance Support (AFTER 1-year AACS Project Warranty)



of 111

The following table summarizes the Unit Price Based AACSI tasks and related responsibilities.

Table 3 Summary of Unit Price Based Integrator Tasks and Responsibilities

CONTRACTOR SCOPE Unit Priced Task Summary List


REF No

CONTRACTOR (Board Contract)

Design DFW Door

Maint. (DFW)

ITS AACS Maint.

Contractor

INTEGRATOR SHALL PROVIDE UNIT COST FOR THE BELOW TASKS

A New Door / Frame / Mech Hardware / Conduit / Wire

Approve

B Install Conduit / Cable and Boxes for new Door

Approve

C New Door Electrified Door Hardware / Card Reader / Devices

Approve

D Install / Wire /program Intelligent Controller

Approve

E Install New Door Electrified Hardware Approve

F Wiring of new Door and associated devices

Approve

G Programming of Door Lead Approve

H Commissioning of Door Support Approve

I Warranty Support of Door (During Project)

Approve

I Warranty Support of Door (After 1 year Project Warranty)

Approve Support Lead


of 111

The following table summarizes the procurement responsibilities of the contractor and the

airport.

Table 4 Procurement Roles and Responsibilities

ITEM

Specified by

Software

Vendor

Specified by

DFW

Furnished by

CONTRACTOR

Furnished

By DFW

PSIM System Software X X

PACS Software X X

AACS Server Hardware X Alternate X

AACS Workstation Hardware X X

COTS Server Software X Alternate X

COTS Workstation Software X X

PACS Field Hardware X X


of 111

7 PROJECT PHASING

To help ensure a smooth and low risk implementation of the new AACS (new PSIM,

associated integrations, and new PACS), the system will be implemented in four (4) phases.

Phase 1 will include the installation, startup, testing and configuration of the new PACS

software and the core essential integrations to enable standing up of the testing

environment. The contractor shall initiate PACS software maintenance at the end of

Phase 1. It is desired that the Phase 1 milestone be completed in 252 days after

NTP.

Phase 2 will include the installation, startup, testing and configuration of the new PSIM

software and the core essential integrations to enable standing up of the testing

environment. The contractor shall initiate PSIM software maintenance at the end of

Phase 2. The Integrator shall note that portions of Phase 2 run parallel with Phase 1. It is

desired that Phase 2 be completed in 293 days after NTP.

Phase 3 includes selection, testing and integration of PACS Access Control Media, Multi-

Class Card Readers, Biometrics, associated end devices and power supplies. Additional

sub-systems and devices, and their associated functionality will be tested in the Test Lab

and at selected Test Doors in a controlled and documented manner. This phase also

includes the cut-over to the new PSIM. It is desired that Phase 3 be completed in 790

days after NTP.

Phase 4 includes the programming of all the access-controlled portals/doors. This phase

also includes the transition and migration process in the field to the new PACS and

Biometrics, in conjunction with the DFW selected CMAR. It is desired that the

migration and transition from the existing PP PACS to the new OnGuard PACS will

be completed no longer than 1885 days after NTP.

A proposed representative implementation schedule, example, depicting tasks for each of the

phases associated with this replacement AACS work scope is shown in Table 5 below for

information. This table also depicts the phases and the systems that will be integrated as part

of the replacement AACS in each phase.

The Airport is interested in an Alternate Delivery and Phasing Approach, if feasible, which

would allow doors to be delivered at the earliest possible time.

To achieve this the Airport will would like consider an alternate/optional approach which

would integrate the new Lenel OnGuard PACS with the current Kaplogic PSIM to

eliminate schedule risk should the new PSIM implementation schedule be delayed.

The approach would have doors migrate from new PACS Lenel OnGuard to the Kaplogic

PSIM and proceed until the new PSIM is fully completed and tested. At the point the new

PSIM is ready, doors already migrated to the Kaplogic PSIM would be transfered to the

new PSIM and critical event history data (e.g. Action List events) would be migrated, one-

time, to the new PSIM. Going forward, all doors would then migrate from new PACS to

new PSIM

Contractor shall provide an outline approach, timeline impacts, and any cost

impact//savings.


of 111

Alternate Approach should be included as separate section/tab in the Proposal

response..

A detailed task schedule shall be proposed by Contractor and submitted as part of their RFP

response.

Contractor shall provide feedback regarding the representative implementation schedule

(Table 5)and the overall delivery timetable suggested. Specifically, whether the 12-14 month

schedule to complete Phase 1-3 is achievable/at risk/aggresive, and if not, what Contractor

believes is more realistic.

Table 5 AACS Example Contractor Implementation Schedule

Task Name

Days

from

NTP

Proposed

Duration

Example

Start Date

Example

Finish Date

Notice to Proceed 0 1 day Wed 9/1/21 Wed 9/1/21

Mobilize 14 14 days Thu 9/2/21 Tue 9/21/21

Submit Project, Technical Implementation, QAP, RMP, Plans and WBS

28 14 days Wed 9/22/21 Mon 10/11/21

Establish 3 Environments for new PACS Software

33 5 days Tue 10/12/21 Mon 10/18/21

Furnish and Install New PACS Software

38 5 days Tue 10/19/21 Mon 10/25/21

Configure PACS Software /Servers for 3 Environments

43 5 days Tue 10/26/21 Mon 11/1/21

Set up and configure AACS Dev Env Test Lab

57 14 days Tue 10/12/21 Fri 10/29/21

Field Power Supplies and related components Selection

72 15 days Mon 11/1/21 Fri 11/19/21

Validate PACS Requirements 103 31 days Tue 10/12/21 Tue 11/23/21

PACS Requirements Review 105 2 days Wed 11/24/21 Mon 11/29/21

Program / Configure DFW PACS 120 15 days Tue 11/30/21 Mon 12/20/21

Set up and Configure AACS Training & Demo/Test LAB at DPS- HQ

136 16 days Tue 11/30/21 Tue 12/21/21

Import PP / CARMA History and Test 151 15 days Tue 12/21/21 Fri 1/14/22

Card and Card Reader selection 166 15 days Wed 12/22/21 Mon 1/17/22

PACS Admin Training 171 5 days Tue 12/21/21 Wed 12/29/21


of 111

Task Name

Days

from

NTP

Proposed

Duration

Example

Start Date

Example

Finish Date

Integrate PACS with SAFE IDMS and Test

232 61 days Tue 11/30/21 Mon 2/28/22

Migrate Existing PP Portal Configurations to new per design and Test

252 20 days Tue 3/1/22 Mon 3/28/22

Phase 1 Milestone 252 0 days Mon 3/28/22 Mon 3/28/22

Establish 3 Environments for new PSIM Software

62 5 days Tue 10/12/21 Mon 10/18/21

Furnish and Install New PSIM System Software

67 5 days Tue 10/19/21 Mon 10/25/21

Configure PSIM Software /Servers for 3 Environments

72 5 days Tue 10/26/21 Mon 11/1/21

Validate PSIM Requirements 103 31 days Tue 10/12/21 Tue 11/23/21

PSIM System Requirements Review 105 2 days Wed 11/24/21 Mon 11/29/21

PSIM System Initial Design Prototype (assumes prior Saab SAFE integration with VMS, GIS, ENS Systems )

135 30 days Tue 11/30/21 Fri 1/14/22

Integrate PACS with PSIM and Test (integrate with legacy and new systems)

195 60 days Mon 1/17/22 Fri 4/8/22

Integrate PSIM with ACMS 209 14 days Thu 3/10/22 Tue 3/29/22

Integrate PSIM with Intercom 216 7 days Wed 3/30/22 Thu 4/7/22

Integrate PSIM with CAD 223 7 days Fri 4/8/22 Mon 4/18/22

Integrate PSIM with Audio Management

230 7 days Tue 4/19/22 Wed 4/27/22

Integrate PSIM with Infor 237 7 days Thu 4/28/22 Fri 5/6/22

Integrate PSIM with PCS 251 14 days Mon 5/9/22 Thu 5/26/22

Integrate PSIM with Mobile Devices 258 7 days Fri 5/27/22 Mon 6/6/22

Integrate PSIM with SAS 263 5 days Tue 6/7/22 Mon 6/13/22

PSIM Prototype Test and Acceptance 293 30 days Tue 6/14/22 Mon 7/25/22

Phase 2 Milestone 293 0 days Mon 7/25/22 Mon 7/25/22

Biometric Verification System and device selection

230 64 days Tue 1/18/22 Fri 4/15/22

Long Range Gate Reader selection 290 60 days Wed 12/22/21 Mon 3/21/22

Vehicle Authentication Technology selection

350 60 days Wed 12/22/21 Mon 3/21/22

Programmable Smart Key selection 380 30 days Wed 12/22/21 Mon 2/7/22


of 111

Task Name

Days

from

NTP

Proposed

Duration

Example

Start Date

Example

Finish Date

Integrate vehicle authenticator with PACS, SAFE, and PSIM and Test

410 30 days Tue 3/22/22 Mon 5/2/22

Integrate Biometrics with New PACS, SAFE IDMS & New PSIM and Test

440 30 days Mon 4/18/22 Fri 5/27/22

Integrate new PSK with IDMS and Test

455 15 days Tue 5/3/22 Mon 5/23/22

Integrate with IDMS with New PSIM and Test

485 30 days Tue 5/24/22 Mon 7/4/22

Furnish and Install C/R, Biometrics & PSK Components at AccessDFW & Training/Demo -Test LAB

495 10 days Tue 7/5/22 Mon 7/18/22

Access DFW Training 505 10 days Tue 5/24/22 Mon 6/6/22

TacComm Training 515 10 days Mon 5/30/22 Fri 6/10/22

CBP Training 520 5 days Mon 6/13/22 Fri 6/17/22

ASD/Police Training 530 10 days Mon 6/20/22 Fri 7/1/22

Configure /Setup up and Test Doors for Evaluation

541 11 days Mon 5/30/22 Mon 6/13/22

Test DFW PACS Software with All Integrations and field hardware in Test Lab (and at Demo Doors)

556 15 days Tue 6/14/22 Mon 7/4/22

AACS System Endurance Testing 617 61 days Tue 7/5/22 Tue 9/27/22

Cutover to New PSIM @ TacComm and Test

619 2 days Wed 9/28/22 Thu 9/29/22

Programming of all doors per design 780 161 days Tue 7/5/22 Tue 2/14/23

Install and Test New PSIM at ASD, Police, and CBP OCC

790 10 days Wed 8/31/22 Tue 9/13/22

Phase 3 Milestone 790 0 days Thu 9/29/22 Thu 9/29/22

Furnish, Install, and wire selected Card Reader, Biometric Devices, PSK Cores, Field Panels / intelligent controllers, related Power Supplies and associated Door components for existing doors per design

1840 1050 days Fri 9/30/22 Thu 10/8/26

Door Conversion, Startup, Test, Commissioning, and acceptance of existing doors

1845 1055 days Fri 9/30/22 Thu 10/15/26

Furnish / Install selected Long Range Gate Readers in the Field per design

1885 45 days Fri 9/30/22 Thu 12/1/22


of 111

Task Name

Days

from

NTP

Proposed

Duration

Example

Start Date

Example

Finish Date

Furnish, Install, Wire NEW Door Electrified Door Hardware, selected Card Reader, Biometric Devices, PSK Cores, Field Panels / intelligent controllers, related Power Supplies and associated Door components and devices for NEW Door per Design

1840 1050 days Fri 9/30/22 Thu 10/8/26

Startup, Test Commissioning, and acceptance of new doors

1845 1055 days Fri 9/30/22 Thu 10/15/26

Phase 4 Milestone (Project Complete)

1885 0 days Thu 10/15/26 Thu 10/15/26


of 111

8 SYSTEMS INTEGRATION

8.1 AUTOMATED ACCESS CONTROL SYSTEM (AACS) BACKGROUND

The replacement AACS will consist of the following major subsystems which, while they may

be managed separately, essentially operate as one system. These subsystems include:


Airport Video Management System (VMS) – (NiceVison IP based cameras and American

Dynamics analog cameras)

GIS – (ESRI)

Physical Access Control System (PACS) – (Existing Picture Perfect /New OnGuard)


Access Control Management System (ACMS) – (HID SAFE IDMS)

Digital Voice Recorder – (NICE Inform)

Digital Intercom – (Zenatel /Stentofon)


Computer Aided Dispatch (Central Square Technologies)

Emergency Notification System – (Everbridge)

8.2 INTEGRATIONS OVERVIEW

The AACS consists of several individual sub-systems integrated to allow for; collection and

aggregation of data, alarm response, effective management of security events, and overall

security based situational awareness.

The PSIM System, while listed as part of the AACS, shall be configured as the primary

platform for integrating, managing, visualizing, controlling, aggregating as needed, and

reporting on security events, data, and information from all the other sub-systems through a

single, comprehensive interface. The role of the PSIM is to provide the system’s users with

situational awareness, and TacComm and CBP with alarm and incident management, by

presenting complex data in a simple to understand way to enhance operational efficiency for

the Airport. Specific details and technical requirements associated with the integrations of the

sub-systems required can be found in the AACS SRS

The following summary provides a high-level overview of the AACS integrations associated

with the PSIM.


of 111

Table 6 Summary Listing of Systems Integrated with the PSIM

Systems Integrated With PSIM

Key Functionality

(based on rights)

Existing Access Control System (Picture Perfect) • Receive Alarm / Event

• Acknowledge Alarm

• Lock / Unlock Door

• Record security events and manage the

response to all events with automatic

response plans

• Make all events / transactions which are

recorded in existing Picture Perfect available

to the new OnGuard PACS for consolidated

reporting, either by accessing the underlying

Picture-Perfect database via ODBC or JDBC,

or by forwarding copies of events via API

calls.

New Lenel OnGuard Access Control System • Integrate such that all PACS functionality

associated with new PACS is accessible via

PSIM. Specific functions shall be based on

Roles and User Rights For example:

o Configure Door

o Configure Time Zones / Threat Levels

o Receive Alarm / Event

o Acknowledge Alarm

o Lock / Unlock Door

o View Card Holder Data / Transactions

o Run Reports

GIS (ESRI) • View maps associated with any Security

Alarm.

• View maps associated with any Event.

• View maps associated with an Intercom Call.

• Use maps to locate PACS device.

• Use maps to locate VMS Cameras.

• Use maps to locate an Intercom

Video Management Systems (NiceVision and American Dynamics),

• Select a camera from a map and view live or

recorded video.

• Select a camera from a list and view live or

recorded video.

• PTZ control for both IP and Analog cameras

via joystick

• view video associated with an event

Biometric Verification System (TBD) • Provide access to biometric verification data

and associated alarms

Audio Management (Nice Inform), • Find and attach video snapshots and audio

recordings to event logs,


of 111

Systems Integrated With PSIM

Key Functionality

(based on rights)

Identity Management System (SAFE)

• View Card Holder Data

• Support research of real time and historical

Card Holder Data related to door alarms,

access transactions, access attempts

Intercom (Stentofon)

• Select Intercom from Map

• Make and Answer Intercom calls (from map or

list)

Emergency Notification System (Everbridge),

• Automatically send emergency messages

needed during an event, such as notifying

service personnel of trouble with a portion of

the system.

Work Order Management System (Infor)

• Automatically populate service requests with

event data

• Allow existing service requests to be called up

by selecting an event.

Parking Control System (PCS)

(SkiData Systems)

• Real time access of time stamped PCS Toll

Tag and LPR Data

• LPR data to include Overview vehicle

snapshot, License plate snapshot and the

License Plate OCR data

• Allow PSIM operator to search on License

Plate data

• Allow for agitation of all sources of LPR or Toll

Tag data and correlation of this data with

ACMS based cardholder data

Computer Aided Dispatch

(Central Square)

• Receive and upload CAD events into PSIM

for video support of dispatch events.

• Send and track till closeout PSIM events

requiring Dispatch Response

Mobile Devices • Support mobile applications, including video

and data using mobile devices,

Situational Awareness System (Saab SAFE)

• Allows operators to selectivity upload

PSIM/Security event Information to the SAS

for holistic view of airport events.

• Send data associated with Security related

system activity to the SAS for SAS

dashboards

The following summary provides a high-level overview of the integrations associated with new

Lenel OnGuard PACS


of 111

Table 7 Integrations with New OnGuard PACS

8.3 NEW LENEL ONGUARD PACS INTEGRATION WITH ACMS (HID SAFE)

The new OnGuard PACS is to have full integration with DFW’s Access Control Management

System (ACMS) which utilizes HID SAFE, in which HID SAFE replaces the underlying badging

/IDMS data source and functionality associated with Lenel OnGuard. The integration shall be

such that it is transparent to the end user and does not sacrifice any of the built-in functionality

of the PACS, such as badge holder maintenance, reporting, or any other system features.

Background Information on Existing Picture Perfect PACS integration with ACMS (HID SAFE)

The ACMS (HID SAFE) serves as the IDMS for the existing AACS, holding all of the

badging and PII for each individual badge holder. To integrate the two systems, a custom

software agent was developed for SAFE that scans for changes in the database. Any

changes found are then pushed to Picture Perfect in a controlled manner to prevent

Picture Perfect from being overloaded.

The data sent includes the following:

Badge Photo

Last Name

First Name

Middle Initial

Badge Number

Access Level

PII data is included to make Picture Perfect reporting more useful. However, the amount

of PII data provided is generally considered insufficient for needs of the stakeholders to

perform full and complete access control investigations. New OnGuard Integrations shall

resolve these issues.

Systems Integrated with New PACS

Key Functionality

(based on rights)

ACMS (HID SAFE)

• Transparent replacement of the new PACS’ underlying

badging functionality within OnGuard, with DFW’s ACMS (HID

SAFE).

New Biometric Verification System

• Provide for the implementation integration and use of the

selected, TBD, BVS with the new OnGuard PACS for multi-

factor authentication at selected portals.

Picture Perfect • Existing system configuration data – including Cardholder

migration, Cardholder Synchronization, and Device Migration

Kaplogic (old PSIM) • Integrate such that all PACS functionality associated with new

PACS is accessible via old PSIM.


of 111

Access levels and door assignments are defined in Picture Perfect. Access levels are

periodically pulled from Picture Perfect by the SAFE agent and made available to the

SAFE application.

8.4 NEW ONGUARD INTEGRATION WITH EXISTING PICTURE PERFECT

During the transition period, DFW Airport requires that the Automated Access Control System

(via the PSIM) be capable of aggregating events from Picture Perfect into the new system and

provide consolidated logging, reporting and historical analysis of events for both systems.

To accomplish this, Picture Perfect is to be integrated with the new PACS, such that all of the

events logged within Picture Perfect are made available to the new PACS. This may be either

through a direct ODBC or JDBC connection to Picture Perfect or by forwarding events from

Picture Perfect to the new PACS through an API call.

8.5 NEW PSIM INTEGRATION WITH EVERBRIDGE

The new PSIM will need to be integrated with Everbridge for forwarding certain events to a

wider audience, such as to alert service personnel and maintenance staff of trouble with a

portion of the system. The information would be populated in a series templates (e-mail, text,

voice, etc.), depending on the type of event

8.6 NEW PSIM INTEGRATION WITH HID SAFE

The new PSIM shall facilitate access to the Airport HID SAFE web portal.

8.7 NEW PSIM INTEGRATION WITH THE EXISTING LENEL PICTURE PERFECT

The new PSIM shall be capable of receiving and facilitating the acknowledgement of events

from Picture Perfect, acting upon them, using a rules-based engine and facilitate the

acknowledgement of events. The integration shall also allow the PSIM operator to bypass and

enable alarm point monitoring, unlock, and lock portals and provide feedback regarding the

status of all related elements.

8.8 NEW PSIM INTEGRATION WITH THE NEW PACS

The new PSIM shall be capable of receiving events from the new PACS, acting upon them,

using a rules-based engine and facilitate the acknowledgement of events. The integration

shall also allow the PSIM operator to bypass and enable door alarm monitoring, unlock, and

lock portals, select threat levels, facilitate lockdowns, and provide feedback regarding the

status of all related elements.

The new PSIM shall provide a portal to the new PACS graphical user interface to facilitate

reporting, maintenance, and all of the other PACS functions.

8.9 NEW PSIM INTEGRATION WITH THE EXISTING QOGNIFY NICEVISION VMS


of 111

The new PSIM shall be capable of calling up cameras based on events processed by a rules-

based engine, by clicking on an icon on a map, or through a portal to the NiceVision graphical

user interface. Controls for PTZ cameras shall be provided on-screen, as well as forwarded

from a separate USB or other hardware controller.

8.10 NEW PSIM INTEGRATION WITH THE EXISTING AMERICAN DYNAMICS

ANALOG VIDEO SYSTEM

The new PSIM shall be capable of calling up cameras based on events processed by a rules-

based engine or by clicking on an icon on a map. Controls for PTZ cameras shall be provided

on-screen or forwarded from a separate USB or other hardware controller. The PSIM shall

also allow the switcher state to be quickly determined.

8.11 NEW PSIM INTEGRATION WITH THE EXISTING NICE INFORM AUDIO

RECORDING SYSTEM

The new PSIM shall provide a portal to the NICE Inform graphical user interface to facilitate

audio playback.

8.12 NEW PSIM INTEGRATION WITH THE EXISTING ZENITEL ALPHACOM

EXCHANGE

The new PSIM shall be capable of receiving events from the existing Zenitel system and

acting upon them, using a rules-based engine.

The PSIM shall allow calls to be placed to stations by clicking an icon on a map.

8.13 NEW PSIM INTEGRATION WITH THE EXISTING PARKING CONTROL SYSTEM

(PCS)

The new PSIM shall be capable of receiving real time, date and time stamped LPR and Toll

Tag data from the Airport’s existing Parking Control System, acting upon that data, and

aggregating other future sources of Toll Tag and/or LPR data, using a rules-based engine to

facilitate License Plate searches. Creating and acknowledgement of Parking of AOA related

events. The integration shall also allow the PSIM operator to aggregate LPR data located in

the ACMS in order to obtain card holder data associated with parking and/or AOA gate

investigations.

The new PSIM shall be capable of calling up cameras based on parking and/or AOA Gate

events processed, and correlated by a rules-based engine, by clicking on an icon on a map.

8.14 NEW PSIM INTEGRATION WITH INFOR

The new PSIM shall be capable of automatically opening new event tracking work orders,

based on events processed by a rules-based engine, and automatically populating relevant

fields for the operator. The PSIM shall also allow an existing work order to be called up when

an active event triggers again or when the operator selects an event.


of 111

The PSIM shall also provide a portal into the Infor EAM system

8.15 OLD PSIM (KAPLOGIC) INTEGRATION WITH THE NEW PACS

The old PSIM shall be capable of receiving events from the new PACS. The integration shall

allow the PSIM operator to bypass and enable door alarm monitoring, unlock, and lock portals,

select threat levels, facilitate lockdowns, and provide feedback regarding the status of all

related elements.

This integration will be needed/utilized if an Alternate Approach for early delivery of doors is

pursued.


of 111

9 PROJECT MANAGEMENT REQUIREMENTS

9.1 ITS PMO

Contractor’s project manager shall fully coordinate with the Airport ITS Project Management

Office (ITS PMO) resources and procedures.

PMO resources will include the Airport Design, Code & Construction (DCC); ITS; Other Trade

Subcontractors; and stakeholder staff.

An ITS PMO point of contact (POC) for Contractor will be designated.

The ITS PMO shall be responsible for coordinating with appropriate Airport representatives for

all Airport approvals. ITS PMO shall coordinate with other stakeholder approval resources as

required.

The ITS PMO may delegate certain tasks/approvals to a designee. The Contractor will be

advised of any delegated authorities.

9.2 CONTRACTOR’S PROJECT MANAGER

Contractor shall assign an experienced Project Manager responsible for implementation of the

AACS and associated integrations, the PACS software, programming, training, testing and

acceptance efforts as detailed in the SOW and System Requirements Specification. Project

Manager shall oversee, coordinate, and serve as principal point of contact for AACS work

activities. It is preferred, but not required, that the Project Manager assigned be a PMP.

Project Manager shall have prior airport experience and shall have installed the same/similar

solutions in at least one airport or similar environment where Automated Access Control

System type platforms are critical to security and operations.

Saab, as a primary sub-contractor/integrator, shall designate an experienced Project Manager

responsible for program support to the Contractor to facilitate and coordinate configuration

and integration activities and meetings as related to implementation of the Saab SAFE

software for the PSIM.

Contractor Project Manager shall coordinate with the designated ITS PMO representative,

other Project Management Oversight (PMO) resources as required from ITS and the Airport

DCC organization. It is anticipated that the Airport will retain the services of a CMAR to

perform the AACS construction activities.

9.3 AACS INTEGRATOR PROJECT PLAN

The Contractor shall submit a detailed AACS Project Plan (PP), within four weeks after notice

to proceed, for approval by DFW.

The AACS Project Plan shall consider the Implementation Schedule and Phasing Plan

provided in the documents herein, with target completion dates for all phases of work.


of 111

This AACS Project Plan shall include the following:

Restatement of Scope which should align with the proposed solution.

WBS structure at the task level

Task descriptions of each discrete activity. No task should be less than 1 day. Include the

following for each task description:

WBS number

Narrative description

Planned start date

Duration

Planned resources (staff, lab, etc.)

Dependencies (including dependencies upon other tasks, Airport, and 3rd party tasks)

A fully dynamic project schedule in GANTT format showing dependencies and critical

path.

Description of project controls to be utilized for cost and schedule management.

Project Organization Chart and Staffing Plan:

The Contractor shall identify all key management, and all those associated with the

PSIM effort, skilled staff, and other key resources, including design/engineering,

selection, development, integration, installation, testing, and training resources enough

to undertake and complete the entire Project.

9.4 ADDITIONAL MANAGEMENT PLANS AND REPORTS REQUIRED

Risk Management Plan (RMP)

The RMP shall include technical, commercial and schedule risks and shall be updated

throughout the duration of the project. The contractor’s methodologies for Risk

Management shall involve the identification, evaluation, mitigation, and re-evaluation of

events that may have an unfavorable impact on the Project.

The Risk Management Plan will detail, for each identified risk, the areas of risk (scope,

schedule, cost, or quality), the risk warning flags, an estimate of potential and probable

risk cost, and activities to help mitigate identified risks.

Project Scope Configuration Management Plan (CMP)

The CMP shall be provided with the Project Plan, and be used throughout the contract

period in order to:

Provide monitoring, control and authorization of changes that effect Project scope,

schedule, and costs.


of 111

Ensure the approval status of proposed changes, the delivery status of approved

changes and the baseline associated with approved changes.

Address the impact and effect of the proposed change on schedule, effort and cost,

functionality and performance, original specifications/requirements deliverables

(hardware, software, infrastructure, etc.).

Communications Plan

A Communications Plan shall be provided with the Project Plan for maintaining an

excellent dialog with airport organizations, existing maintenance contractors, and

contractors/representatives of systems to be integrated and interfaced with the new

AACS (PACS and PSIM).

Quality Assurance Plan (QAP)

Four weeks after notice to proceed contractor shall deliver a Quality Assurance Plan

(QAP).

The QAP shall describe the quality control activities and guidelines to be performed.

The QAP must comply with ISO 9000 Quality guidelines and standards.

The contractor as well as the Saab Sub-Contractor, will identify a Quality Control

Manager and key positions needed to ensure effective and efficient execution of the

QAP. The Contractor’s Quality Control Manager will be responsible for carrying out all

QC activities in accordance with the QAP.

The QAP shall apply to all products and services delivered under the contract including

COTS and application specific software, hardware, interfaces, infrastructure,

installation, integration, testing, training, and documentation.

The QAP shall be designed to provide effective means to ensure that the PACS system

meets the intended purpose and objectives regarding functionality, performance,

reliability, user friendliness, maintainability, and availability.

The QAP shall provide the means to review and control defects, errors, and omissions.

The contractor shall maintain a Trouble Report (TR) database throughout the life of the

project to log all identified quality problems.

The QC Manager shall maintain a documentation library consisting of all documents

developed and delivered during the contract to include meeting minutes, specifications,

design documents, test plans, system documentation, status reports and

correspondence.

Inspection of each deliverable document for compliance with established quality criteria

and a signed quality statement shall accompany each document submission.

Status and Management Reports

Weekly email status report

A weekly email status report shall be provided (from project kickoff until final

acceptance of the last transitioned access-controlled portal) and shall identify:


of 111

The activities completed in the last week.

Percent complete information for key milestones and activities

The activities planned for the next week, including Contractor, Saab Sub-Contractor, Airport,

and 3rd party activities.

Project Risk analysis and risk mitigation approach

Current schedule for completion

Open action Items

Decisions needed

Monthly Maintenance Management Report

A monthly maintenance management report shall be submitted monthly following the

acceptance of the stress tests for the new PSIM, as well as new PACS Platform,

starting on the 1st business day of each month.

This information shall be used to determine Key Performance Indications for

Contractor’s ability to achieve the proposed Plan, and the minimum requirements for

the maintenance portion of this Scope of Work. Plan shall include Contractor’s

proposed method to determine KPI score with fair and reasonable consequences for

less than satisfactory performance.

At a minimum, the monthly report shall include the following summary of performance

planned:

System availability percentage

Calls received and performance (Non-Scheduled)

Preventative Maintenance (Routine and scheduled)

Return to Service performance

Portal type performance

System certification status

Response for IDC requests, implementation, documentation, and completion

Daily Maintenance Activity Summary

Daily Maintenance Activity Summary shall be submitted daily. At a minimum, the daily

report shall include the following:

Daily System Application Health Status

Maintenance Activity Report

Open and Closed corrective actions or repairs


of 111

Weekly Maintenance Activity Summary

Weekly Maintenance Activity Summary shall be submitted weekly. At a minimum, the weekly

report shall include the following:

Daily System Application Health Status Weekly Summary

Maintenance Activity Report Weekly Summary

Completed activities Weekly Summary

Planned Activities

9.5 PROJECT EXECUTION

Contractor shall conduct a project kickoff meeting 2 weeks after notice to proceed. Contractor

will review their project plan, project schedule, communications plan, Quality Assurance Plan,

Risk Management Plan, contractor staff, and problem escalation procedures.

Contractor will provide weekly status reports. At the discretion of Airport, a Microsoft Teams

teleconference will be conducted to review the emailed project status reports. Two days prior

to scheduled reviews the contractor shall provide a detailed agenda and presentation material.

Following any meetings or reviews, contractor shall circulate meeting minutes within 2

business days.


of 111

10 DISCOVERY/SYSTEM REQUIREMENTS VALIDATION

10.1 REQUIREMENTS VALIDATION

After notice to proceed, and the kickoff meeting, the Contractor will meet with designated key

stakeholders from DFW ITS and DPS in order to conduct interviews to refine the requirements

contained in the PSIM System Requirements Specification document as well as the PACS

Requirements Specification and Technical Specification Compliance Matrices.

Any clarifications/discrepancies related to systems architecture, cybersecurity, functional or

technical requirements, number of users and devices, phasing, integrations, and reports shall

be clarified. Contractor will identify any risks associated with integration and implementation.

Methods for interfacing and integrating with existing systems will be determined.

Contractor shall ensure all business rules, workflows, standard operating procedures, portal

configurations and operating models, programming, and technical implementation plans are

defined and agreed upon with users and stakeholders. All revisions will be incorporated into

an updated System Requirements Specification document (SRS) as well as an updated PACS

Requirements Specification and Technical Specification Compliance Matrices.

The Contractor shall define all user roles and associated access permissions and user rights.

The Contractor shall update the Hardware Requirements Document and COTS Software

Requirements Document provided by Saab for the PSIM and Lenel with their PACS software

vendor’s proposal.

The Contractor shall create a Verification Cross Reference Matrix (VCRM) which will provide

traceability to this RFP scope of work, specifications along with the PSIM and PACS

requirements documents provided. The VCRM will be maintained throughout the project life

cycle.

10.2 SYSTEM REQUIREMENTS REVIEW

Contractor shall conduct a System Requirements Review (SRR) with the airport prior to

proceeding to system design, implementation, and configuration portion of the work. The

purpose of the SRR is to review the updated SRS and other relevant AACS requirements

documents to ascertain that all requirements have been defined adequately.

10.3 AACS TEST LAB

The Contractor shall furnish and install an AACS Test Lab to be used by contractor and the

Airport staff to test, configure, and support the selection and implementation of AACS

components, PACS portal configurations, along with the testing and validation with the PSIM

and associated workflows.

The AACS Test Lab shall be in a location determined by the Airport, within a secure Airport

facility, and will house the Development/Test Environment. (see also Section 13.1 –

Development Environment)


of 111

The Test Lab shall be configured with AACS (PSIM and PACS) workstations, a min of 5 sets

of Intelligent Controllers, configured with field panels and end devices to support a min of 12

PACS portals.

In addition to configuration testing, the Contractor must use this facility to support Airport staff

in performing the listed device and component evaluations prior to formal Airport selection and

authorization to implement and integrate these end devices and/or components into the

AACS.

The contractor shall submit a formal testing and evaluation plan (T&E) for each of the

items to be tested in order to obtain authorization and budget from the DFW technical

POC to procure and begin the test and evaluation effort.

The T&E shall include, at a minimum:

Testing and Evaluation Procedures

Acceptance Criteria (document all systems features and functionality)

Notes and Testing Logs

Airport Stakeholder and Contractor Sign off sheet(s)

Proposed selection schedule

ROM cost estimate for obtaining, configuring, and testing the end device and/or

component.

For the purpose of this RFP, the contactor shall assume the following items are to be

tested, and once accepted integrated into the AACS, at a minimum:

Intelligent Field Panel Power Supplies

PACS Multi-Technology Smart Card Media

PACS Multi-Technology Card Reader

Biometric Verification and Authentication System

Long Range Card Reader

Vehicle Authentication Technology

High Security Programmable Smart Key System


of 111

11 SYSTEM DESIGN AND PROTOTYPE

11.1 AACS SYSTEM DESIGN

The new Physical Information Management System (PSIM) and Physical Access Control

System (PACS) shall integrate with other systems, and sub-systems as defined in this Scope

of Work, to form the replacement AACS. The AACS shall be designed to facilitate the

collection of data from several sources, and discrete security sub-systems, and present that

data in a unified, useful, and well-planned manner to the end users and to allow monitoring,

control, management and reporting on events and transactions from those systems and sub-

systems as required, from a single workstation.

The AACS shall be configured, managed, and operated based on Business Rules. The

development of the Business Rules shall be a collaborative effort between the Airport and the

Contractor, with the Contractor facilitating the definition of Business Rules based on Airport

requirements for the new PSIM, the new PACS, and the sub-systems the new AACS

integrates with.

The operation of the AACS shall enhance and facilitate the operation of the integrated

systems, and under no circumstances shall it limit or remove functionality or capabilities

inherent in these systems.

The contractor shall be the lead for designing and developing all interfaces to the new AACS.

It is anticipated that the Contractor may initially conduct separate System Requirements

Reviews for the new PSIM and the new PACS, however a full and complete SRR must take

into account the integrated functionality of the new AACS.

After successful SRR, the Contractor shall develop the following design documentation:

AACS System Design Document (SDD)

The SDD shall describe the system architecture, functional capabilities, and all aspects of

system communications, system interfaces, system security, system software, system

hardware, locations and quantities of hardware and workstations to be implemented,

system performance, and system maintainability.

Contractor is responsible for coordinating with all necessary DFW system contractors, as

required, to develop system interfaces to the new AACS.

The SDD must describe how the new AACS is designed and engineered to meet

capacity, functional, security, and performance requirements.

The SDD shall include the following:

Design summary of the AACS

Logic diagrams and system flow diagrams for complete integrated AACS

System architecture diagrams

Workflows and business rules that will be used to manage events.


of 111

Business rules and associated Boolean logic that will be used to configure and program

all PACS portal types.

Design detail shall include:

Core system configurations for the new AACS (both PSIM and PACS) including servers,

services, and applications.

Connectivity design details of requirements from DFW ITS for network communication, cable

infrastructure, and power requirements. This shall include all cabling types and

configurations (including fiberoptic cable), network communication services, QoS, port

requirements, firewall, and IP scheme, configuration needs, etc.

Redundancy and fail over architecture and recovery processes.

System Capacities

System Performance Calculations

Information Security Design

Deviations from any listed standards, including those published by DFW.

For PSIM and PACS Servers and AACS Workstations

Location plans illustrating equipment locations.

Rack layouts – Data Centers and Communication Rooms

Engineering drawings, where applicable.

Interface Control Documents (ICD)

An ICD must be developed for each and every system/sub-system to be integrated with

the replacement AACS.

These ICDs must describe in detail the interfaces to/from each system/sub-system

integrated with the replacement AACS.

Contractor shall participate in Interface Working Groups (IWG) with the other DFW

System providers and stakeholders as required to assist in defining and controlling all

the new AACS system interfaces and integrations. This must include all data

exchanged, business rules, and system logic for the interfaces that are required.

Interface Control Documents (ICD's) will support the specific interface regarding Open

architecture, open API, pre-defined architecture / protocols / rules.

The ICD shall address and include, but not be limited to:

Purpose of the interface

Mapping of requirements in the SDD that the interface helps meet.

Data elements exchanged.

Functionality


of 111

Business rules and logic that govern the exchange of information. The business rules shall

cover formatting, sequencing, error detection, commands, performance characteristics, and

workflow.

Technical design, including method, form, standards, and protocol of the data exchange.

Timing.

Data security.

Data integrity.

Handshake requirements.

Recovery modes.

Management, control, logging, and audit functions.

Implementation roles and responsibilities.

Testing and acceptance approach and procedures.

Manufacturer’s certification/verification of ICD.

Updated Hardware Requirements Document

The Contractor shall provide DFW with a bill of materials (BOM) for all required

hardware necessary for the replacement AACS implementation of both the new PSIM

and the new PACS (less associated intelligent controllers / door and I/O field panels,

power supplies, and associated door hardware required for the transition from the

existing to new PACS). The Airport intends to procure all BOM listed hardware.

The BOM shall include all server, firewalls, switches, storage, WS and monitor

requirements.

For each type of product required for the AACS, the Contractor shall provide all

minimum and recommended requirements, including quantities, features, performance,

and sizing requirements. Document shall contain a complete description of hardware,

product keys, product numbers and cut sheets. This will be an update to the lists

provided in the contractor’s proposal for the PSIM and in the Lenel S2 PACS proposal

response and based on final requirements and design activities

The Airport operates and maintains a Cisco Hyperflex VMware-based virtual machine

server environment which provides five-nines (99.999) availability and redundancy

between the Airport’s two data centers for fail over. The Airport desires to maintain, if

possible, a single hardware/server platform environment and seeks to leverage and use

the Hyperflex environment for requirements herein. The Saab SAFE application

currently operates in this environment. Please indicate whether this environment is

a suitable option for the PACS requirements in this work scope.

Updated COTS Software Requirements Document


of 111

The Contractor shall provide DFW with a bill of materials (BOM) for all required COTS

software necessary for the PACS implementation. DFW intends to procure all COTS

software.

The BOM shall include all server, storage, and WS COTS software requirements.

For each type of product required for the PACS, the Contractor shall provide all

minimum and recommended requirements, including quantities, features, performance,

and sizing requirements.

Document shall contain a complete description of COTS software, version, license

information, product keys, product numbers and cut sheets.

This will be an update to the lists provided in the contractor’s proposal for the PSIM and

in the Lenel S2 PACS proposal response and based on final requirements and design

activities.

11.2 SYSTEM DESIGN REVIEW

Contractor will conduct a System Design Review (SDR) to obtain approval of the SDD, ICD,

and Hardware and COTS Software Requirements Document. SDR includes:

A review of the System Computer Software Configuration Item (CSCI) requirements,

Hardware Configuration Item (HWCI) requirements and operational concepts. This shall

include graphical charts / flow charts.

Validate compliancy as defined in the VCRM

Evaluate the progress, technical adequacy, and risk resolution (on a technical, cost, and

schedule basis) of the design and determine its compatibility with functional and performance

requirements.

Evaluate the degree of definition and assess the technical risk associated with the

design/implementation methods of the physical and functional interfaces with other systems.

11.3 PROTOTYPE AND PORTAL DESIGN AND DEVELOPMENT

Upon Airport approval of the SDR, the Contractor may begin system development, interface

development and product configuration to meet system requirements. All development will be

done at the Airport’s facilities in space provided to the contractor at the AACS Test and

Development Lab.

As part of the design effort:

Contractor shall develop a prototype of the PSIM user interface for validation of

workflows implementation, response plans and ease of use, including support for full and

complete PACS reporting functionality.

Contractor shall develop prototype Portal Templates and programming configurations for

all Access Control System Portals / Portal Types to be implemented at the Airport on the

new PACS.


of 111

Design, prototype, and configuration effort shall include area/zone layout, access control

database configurations, including authorized card holder user groups and/or access profiles,

Interlock programming for FIS based portals, FIS call light monitoring and reporting, and

associated interface implementation, alarm types, responses, and report templates.

User roles and profiles shall be configured for validation during this prototype effort.

It is anticipated that during the period, the contractor will support the selection of the access

control media and associated keypad card reader, access media printer and programmer,

biometrics, long range reader and vehicle authentication device as well as the intelligent field

panel power supplies.

In preparation of the new AACS/PSIM prototype, system interfaces must be simulated for

prototype implementation. No system integrations are required for the PSIM prototype.

Mockup or emulations of interfaces must be acceptable.

11.4 USER VALIDATION/CONFIGURATION WORKSHOPS

Contractor shall implement the AACS/PSIM prototype user interface in the Development Lab,

along with the PACS Prototype. Workstations and monitors will be provided by the Airport

based on Contractor specifications. These prototype PSIM user interfaces, and PACS

configurations shall be useable on the workstations in the development environment.

Contractor shall conduct user validation and system configuration workshops.

The PSIM system users will exercise the prototype user interface and provide feedback

on specific functionality, ease of use, workflows/standard operating procedures, response

plans, screen displays, screen layouts, reports and dashboard formats. Contractor shall

refine the PSIM system configuration and design to meet user needs and expectations.

Using the Test Lab implemented field hardware, the PACS users will exercise the

prototype card holder and portal programming, system, zone/area, business rules, and

logic configurations, and monitoring and reporting requirements and provide feedback on

specific functionality, ease of use, workflows screen displays, reports and dashboard

formats. Contractor shall refine the PACS system configuration and design to meet user

needs and expectations.

These user validation workshops are not system tests. They are an opportunity to refine the

new AACS design to meet user needs and expectations.

This effort should last for a minimum of 3 weeks.

11.5 PACS TECHNICAL TRANSITION PLAN (TTP)

Following successful completion of the user validation/configuration workshops, the prototype

design development efforts, and review of the DFW AACS Project Design Team’s technical

documentation, the Contractor shall create a comprehensive, technical transition plan for

review and approval that provides a full description of the proposed technical solution for

transitioning from the existing PP PACS to the new OnGuard PACS, and the proposed

cutover from the existing KapLogic PSIM to the new Saab-based PSIM System.


of 111

The TTP shall include all aspects of the operational transition and migration planning required

for the project, including but not limited to:

Implementation of new multi-class access control media, card printers and encoders

Configuration of new multi-class devices capable of reading the existing and new Access

Control Media card formats.

Transition methodology for migrating portals from the existing PP LMPs to the new

Mercury based field panels, including any temporary or interim installations as may be

necessary.

Personnel training

Support and planning required for wiring and acceptance testing of all local door

equipment, end devices, including biometrics of the new PACS.

11.6 AACS IMPLEMENTATION / CUTOVER PLAN

Contractor shall deliver an Implementation/Cutover Plan coordinated with the AACS

replacement project’s Master Schedule describing schedule for production system

implementation, airport coordination activities and tasks for cutover to operational service of

the new AACS.

It shall include implementation in the production environment, validation testing in the

production environment, data migration/Data Base loading, and cutover to the new

replacement AACS using the New PSIM in the production environment to initially enable all

systems integrated with the new PSIM to function via the new PSIM prior to the start of PACS

Portal transition, in accordance with the TTP.

A schedule of activities for both contractor and airport staff shall be included. Dependencies

between tasks will be included.

The AACS Cutover plan must address the following:

Prerequisites to System Cutover/Site readiness criteria

Notification plan and procedures to all involved in Cutover process.

Responsibilities of all parties involved in Cutover.

Schedule of step-by-step activities to implement the new PSIM in the IOC for TacComm,

at the CBP’s OCC, and for ASD and the Police.

Tasks and dependencies of all contractor, airport, and 3rd party responsibilities.

Measures to ensure there are no outages of existing systems.

Fall back process and procedures if cutover does not go smoothly.

Upon successful cutover, the transition from the existing PP PACS to the new OnGuard PACS

can be started.


of 111

11.7 FINAL DESIGN DOCUMENTATION

Following successful completion of user validation/configuration workshops, contractor will

create final design documentation for the AACS, to include:

Updated VCRM,

Updated SDD,

Updated ICD,

Updated TTP,

Updated Implementation/Cut-over Plan.

Acceptance Test Plan (ATP)

The Acceptance Test Plan (ATP) shall address the functional requirements, all

Automated Access Control System interfaces, system access and security

requirements, system admin functions, system performance, system monitoring and

reporting functions, and cover each user role’s ability to access the AACS with

designated functionality.

The test plan shall identify test approach and methodology, test location and test

environment.

Test data, test databases, test software and/or simulations needed to accomplish

testing shall be documented.

Plan shall include test procedures, test steps, test sequences, expected test results and

test acceptance criteria with a sign off of each test by Airport representatives.

Resources required to conduct tests will be identified. Include airport staff and

interfacing system contractor staff to support testing.

Each requirement in the VCRM will be cross referenced to a test in the ATP. The

acceptance test plan will be used for each phase of testing. Appropriate test series

activities and procedures shall be defined in detail for each phase of testing.

Representative tests include, but are not limited to:

Functional Unit tests

Interface/integration tests to verify that the PACS and the AACS comply with ICD.

End to end tests

Endurance tests to ensure the system performs appropriately over an extended operational

period.

Fail over and recovery tests.

Data backup and recovery tests


of 111

Error detection tests to ensure the effectiveness of error detection, reporting, analysis, and

automated diagnostic tools.

Data integrity tests.

Performance Tests

System Administration tests

Training Plan

The contractor shall develop a comprehensive training plan for all users of the AACS

and system administrators.

Training plan will provide a syllabus for each course to cover user training, system

administration, system configuration and system maintenance.

Training plan shall identify minimum skill requirements for trainees taking each course.

A schedule for the delivery of all training courses accommodating staff shift

requirements must be included in the submittal.

AACS IT Security Plan

In accordance with NIST 800-53 (Revision 5) contractor will develop a Security Plan for

the AACS.

This plan will define the AACS – in terms of the new PSIM system and New PACS

classification and categorization and describe the security controls to be implemented

to protect the system and its data from possible security breaches.

11.8 CRITICAL DESIGN REVIEW (CDR)

The Contractor shall conduct a Critical Design Review (CDR) to approve all final design

documentation and obtain approval to move forward to system installation and test.

CDR shall validate requirements compliancy with VCRM and test matrix. It will determine the

design satisfies the functional, performance, security, and administrative requirements of the

PACS.


of 111

12 PROCUREMENT

12.1 HARDWARE AND COTS SOFTWARE

Following successful SDR, the Airport will move forward with procurement of all hardware and

COTS software for all 3 environments as specified in the updated hardware and COTS

software requirements document.

At Board’s discretion, the Airport may choose to purchase PSIM and PACS server hardware

and COTS software from the Contractor. If this option is exercised, contractor shall proceed

with procurement of all hardware and COTS software for all 3 environments for each system

as specified in the updated hardware and COTS software requirements documentIf the Airport

decides to exercise hardware procurement alternate, contractor must assume the following

responsibilities:

Contractor shall coordinate Staging/storage facility needs with DFW ITS.

Contractor shall be responsible for product delivery and logistics to designated staging,

storage, or installation locations. Delivery will be coordinated with the designated DFW

logistics coordinator.

Contractor shall be responsible for any and all loss or damage in the shipment and

delivery of all material.

Contractor shall arrange for their own logistical support to move product between

locations.

Contractor shall install hardware and COTS software in all 3 environments for the PSIM and

the PACS.

Contractor shall coordinate with ITS and perform asset management as part of final

placement, to include:

Label end user devices with IP address and device name

Affix a bar code asset tag (to be provided by the Airport) to all equipment/devices.

Log the asset (with required elements) to an excel asset/maintenance register (form and

format to be provided).

Contractor shall be responsible for all hardware maintenance from initial purchase through the

Warranty and Maintenance period.

All workstation equipment, monitors, and workstation cabling may be procured by the Airport.


of 111

13 SYSTEM INSTALLATION AND TEST

13.1 SYSTEM INSTALLATION IN DEVELOPMENT ENVIRONMENT

The airport will provide space for a development environment which will include the AACS

Test Lab, located in a secure facility at the airport to be used by the contractor for the new

AACS (PSIM and PACS) user testing, system testing, future developments, fixes, software

release testing and future phase development and testing.

The space will have enough network connections and adequate power for 3 Workstation

Consoles, 5 Intelligent Controller Field Panels, 10- 2-reader panels, keypad card readers,

associated portal edge devices and power supplies.

Upon successful completion of CDR and hardware and software procurement activities, the

Contractor shall update the PSIM and PACS software installation in the development

environment.

Contractor shall provide all tools and test equipment required to install, verify, and test the

installation and to determine that it meets the specifications.

Contractor shall complete development environment installation, PACS configuration, and

perform the AACS integrations in accordance with the schedule agreed upon with the Airport.

The development Test Lab will be used for UAT/SAT testing of the PACS software as well as

the integrations required to configure the new AACS.

Following final system acceptance, the development environment will be used for developing

and testing AACS (PSIM and PACS) upgrades, patches, and other configuration changes

during the warranty and maintenance periods for this contract.

13.2 TEST READINESS REVIEW

Following successful CDR, system development activities, AACS configuration and

implementation, along with the successful completion of the specified AACS integrations in the

development environment, the Contractor will conduct a test readiness review (TRR) to

ensure resources are available and everything is in place for UAT/SAT acceptance testing in

the development environment.

A TRR shall take place for both the new PACS and the new PSIM.

TRR shall ensure test procedures are complete and traceable to the VCRM. Any test data,

simulations or test interfaces must be available.

TRR shall review the acceptance test plan (ATP) for the planning and scheduling for

conducting UAT/SAT acceptance testing.

Contractor shall demonstrate readiness and availability of all test resources to include airport

staff, contractor staff, staff of contractors of the integrated / interfacing systems, as required.


of 111

13.3 PRELIMINARY USER/SYSTEM ACCEPTANCE TEST

Using the Acceptance Test Plan approved at CDR, testing will be conducted in the

development environment. There will be two (2) sets of tests. The first for the new Lenel S2

OnGuard PACS Software itself, and then the second will be for the newly Integrated AACS

(using the new Saab PSIM). Each of these sets of tests will be divided into two types: User

Acceptance Testing (UAT) and System Acceptance Testing (SAT).

UAT will test all functional requirements, user interfaces, and system interfaces from the

system design document (SDD) and the interface control documents (ICDs). Test shall be an

end-to-end system test encompassing all the software and hardware components of the

system and demonstrate that the specified features and performance criteria are met once all

components have been installed including, but not limited to:

Testing of the head-end system

Testing of end user devices

Functionality and response of system and system interfaces

User interfaces

Device interfaces

Data interaction

Integration/Interfaces - internal and external

Query and Report generation

Upon successful completion of UAT, SAT will be performed. System Acceptance Test

includes the following:

System Security Requirements

System Administration Requirements

System Access and Privilege Requirements

System Failover and Recovery

System Performance Requirements

Load and Capacity Requirements

Airport personnel will observe all testing and initial tests that successfully pass.

Following completion of testing, contractor shall deliver test reports documenting test activities

and any issues found during testing. Reports will include a Punch List of fixes required to be

retested before system implementation in the Test/Training and Production Environments.

Except for minor discrepancies, the Airport will determine if system is in full compliance with

SRS and SDD and is ready for implementation in the Test/Training and Production

Environments and commencement of training.


of 111

The final test records shall be submitted once all faults are corrected and the AACS system

passes all tests. The final test records shall include passed tests with initials by the Airport

representative(s).

13.4 TEST/TRAINING ENVIRONMENT INSTALLATION

The airport will provide space for a Test/Training environment at the airport. The Test/Training

Environment will have multiple purposes.

The Test/Training environment shall be used by the Airport and Contractor for initial

training of all users and administrators on the replacement AACS, specifically the new

Saab PSIM, the new Lenel OnGuard PACS. The workstations associated with the

Test/Training Environment must be in a lab with enough network connections and

adequate power for 7 Workstation Consoles.

Following the new fully integrated Automated Access Control System acceptance, the

Test/Training environment shall be used for pre-production testing of all new releases

and fixes to the PSIM and the PACS software. Having been developed and tested in the

development environment, all changes to the AACS will be tested in the Test/Training

Environment before implementation in the production system.

The Test/Training Environment will then be used for all user future and ongoing training,

PSIM and/or PACS new functionality incubation and user familiarization.

Upon successful completion of UAT/SAT in the development environment, contractor shall

install AACS (new PSIM and New PACS) software in the Test/Training Environment.

Contractor shall provide all tools and test equipment required to install, verify, and test the

installation and to determine that it meets the specifications.

Contractor shall complete Test/Training Environment system installation and AACS

configuration in accordance with the schedule agreed upon with the Airport.

Following successful UAT/SAT in the Development Environment, the approved tested version

of the PACS software will be installed in the Test/Training Environment.

A validation test of the Test/Training environment will be conducted. Validation testing will use

the ATP, but not all tests need to be executed. Enough tests should be executed to ensure:

All system interfaces are working properly.

All devices are accessible and working properly.

AACS functions are working properly.

A Test Report and Punch List for the Test/Training Environment validation test will be

delivered.

After successful validation testing of the Test/Training Environment, the Airport will give

permission to move forward with production environments implementation per the

Implementation/Cutover Plan.


of 111

The Test/Training Environment will be kept current to production configuration throughout the

warranty and maintenance period of this contract for pre-production testing of new releases,

refresher training and training new staff.

13.5 IMPLEMENTATION IN PRIMARY AND SECONDARY PRODUCTION

ENVIRONMENTS

Contractor shall install PACS software in both the primary and secondary server rooms

designated by the Airport for the production environment. The Contractor shall be responsible

for updating the installation of the PSIM and PACS application software after successful

completion of Validation Testing in the Test/Training Environment.

Production environment implementation shall consist of all activities necessary for systems

operation. At a minimum, this must includes:

Application Software

Network VLAN configuration (coordinated with ITS)

System Monitoring Workstations (provided by the Airport)

System Administration Workstations (provided by the Airport)

Other System Interfaces and Website Connections (coordinated with ITS)

A validation test shall be conducted in the production environments to ensure AACS

application (the fully integrated new PSIM, including all sub-systems, old and new PACS) is

accessible and working properly prior to system cutover. Enough tests should be executed to

ensure:

All system interfaces are working properly.

All devices are accessible and working properly.

Functions of the new AACS are working properly.

System failover/recovery processes are working properly for both the fully integrated

AACS (new PSIM and the new PACS)

Following completion of validation testing, contractor shall deliver a test report documenting

tests activities and a punch list of any issues found during testing.

13.6 SYSTEM CUTOVER

Following successful validation testing in the production environment of the AACS, the

contractor will submit all system documentation, as-builts, DR Procedures, SLA, and software

licenses for the new PSIM and PACS software platforms fully integrated with all sub-systems

forming the new replacement AACS.

Contractor shall conduct a Cutover Readiness Review (CRR). At the CRR, the Airport will

review test reports and ensure no major issues will prevent the PSIM cutover. The Airport will

review the cutover and determine if the PSIM (and associated sub-systems including the


of 111

VMS, IDMS, the existing PP PACS, Intercom, and the new Lenel OnGuard PACS) are

acceptable for operational use for responding to existing PP PACS Alarms, and that all actions

necessary to begin adding new doors/portals as well as migrating and transitioning existing

Portals have been completed.

Airport will review cutover plan to ensure all stakeholders have been notified and all resources

are available and ready to participate in system cutover of the new PSIM.

13.7 ENDURANCE TESTING

After the CRR but prior to the System Cutover, the AACS shall undergo endurance testing for

a period of 60 calendar days.

There shall be two distinct endurance tests: one for the new Lenel OnGuard software

platform and one for the new fully integrated Saab PSIM platform.

During this period, the Contractor shall provide on-site personnel to support these systems’

operation for the full 60 days, including weekends and holidays, of endurance testing.

The Contractor shall monitor both the PACS and PSIM systems during endurance testing in

conjunction with the Airport.

The Contractor shall record incident data and performance metrics to provide a continuous log

of system performance. The log shall include:

date and time for all entries.

name of individual making entry.

environmental conditions.

activities in process.

description of all classification of alarms, responses, corrective actions, and causes of

alarms.

description of all equipment failures.

description of all software errors.

description of all maintenance and adjustment operations performed on system.

daily and weekly tabulations; and

daily entries of performance data shall be reviewed by the DFW ITS representative

designated to observe monitoring of system.

The Airport may terminate endurance testing at any time either of the systems fails to perform

as specified. Upon early termination of endurance test, the Contractor shall commence a

corrective period, identify all failures, determine causes, and resolve all issues. The Contractor

shall submit a report of the Endurance Tests, explaining the nature of each failure, corrective

action taken, results of tests performed, and recommended point for resumption of that

system’s endurance testing.


of 111

After submission of the report referenced above, the Airport will schedule a review. At the

review meeting, the Contractor shall demonstrate through verification tests that all failures

have been corrected.

Based on the report and review meeting, the Airport Project Manager will approve resumption

of the endurance test.

To pass its endurance test, each system must run for 60 consecutive calendar days without

emergency or critical issues.

Upon successful completion of system endurance tests, the airport will begin beneficial use of

the new PACS and the PSIM systems. It is at this point that the AACS warranty and

maintenance period begins.

13.8 OPERATIONAL READINESS ACCEPTANCE TEST (ORAT)

The process of transitioning from an existing operating PACS to a new PACS that functions

seamlessly and meets all regulatory requirements from day one needs to be carefully planned,

managed, and fully tested. AACS operational readiness requires the full range of delivery

elements which include facility, people, process, and technology.

ORAT will be conducted by the AACSI Contractor in coordination with ITS, DPS and CBP

stakeholders following cutover to the production environments. Tests will be executed to

ensure the following:

All user functions are working in accordance with their requirements.

All interfacing systems are reachable.

Access Control, alarm monitoring and card holder functions are reporting based upon the

outlined parameters in the system specification.

System administration functions are functioning based upon the outlined parameters in

the SRS and SDD.

Following completion of testing, contractor shall deliver a test report documenting test

activities and a punch list of any issues found during testing.

13.9 PACS TRANSITION READINESS

In conjunction with, and after successful Operational Readiness Access Testing (ORAT) and

Endurance Testing in the production environment the Contractor will submit to the Airport test

reports and certification that the new AACS has been tested and that no major issues will

prevent the PACS to begin the transition in accordance with the updated TTP, in order to allow

the CMAR to begin planning the Portal-by-Portal Transition Process from existing PP PACS to

the new Lenel OnGuard PACS.

The Airport will review the documentation and the updated TTP and will make the final

determination that the AACS and associated systems are acceptable for operational use and

that all actions necessary to begin adding new doors/portals as well as migrating and

transitioning existing Portals have been completed.


of 111

Airport will ensure all stakeholders have been notified and all resources are available and

ready to participate in system transition.

Upon airport approval and notification, the CMAR can begin the transition effort to migrate

from the existing PP PACS to the new OnGuard PACS in accordance with the TTP.

Upon PACS Transition Readiness and System Acceptance of the Initial Portal on the new

PACS, the airport will begin beneficial use of the new PACS system, and which begins the

PACS warranty and maintenance period.

13.10 FINAL AACS ACCEPTANCE

No later than 5 working days following the successful completion of the Operational

Readiness Acceptance Testing (ORAT) the Contractor will conduct a post cutover

reassessment workshop. Any operational anomalies, user interfaces or system performance

issues will be discussed and a plan and schedule for resolution developed.

Final AACS acceptance is at the sole discretion of the ITS PMO.

To obtain final acceptance the following must be completed:

All punch list items from all testings have been resolved.

60 consecutive day endurance test for both the PSIM and PACS have been successfully

completed.

Resolution of post PSIM cutover issues completed.

All documentation delivered.

All training complete

Inventory reconciliation of the installed system against the As Built Documentation

Software Licenses

The Contractor shall provide software licenses for each type of application. The software

licenses shall be suitable for the quantities of users and equipment defined for the

project. All licenses shall be issued to DFW.

As-Built Documentation

As-Built documentation updated to the most current configuration at a minimum shall

include:

System Architecture Diagram with Hardware configuration items and Computer Software

configuration items

Server Names and installed equipment IP address listing.

Asset property tagging/accounting information.

Service Level Agreement


of 111

Contractor shall deliver a Service Level Agreement describing all warranty/maintenance

functions and performance requirements they will meet during the warranty and

maintenance period.

Disaster Recovery Procedures

In accordance with the referenced DFW ITS System Disaster Recovery Policy, contractor

will deliver Disaster Recovery Procedures, this shall include creation of the Disaster

Recovery Plan for submittal to DFW ITS DR team for the AACS. These procedures and

the plan will describe steps to perform to recover the system from backup in the event of

a PACS as well as a PSIM system failure.

13.11 TRAINING PROGRAM

The Contractor shall develop and implement a comprehensive training program for all required

Airport and CBP staff. Such training shall be implemented using formal classroom training,

training in the test/training environment and other forms of training that the selected Contractor

shall propose.

The contractor shall develop a comprehensive training plan for all users of the AACS and

system administrators. Training plan will provide a syllabus for each course to cover user

training, system administration, system configuration and system maintenance. Training plan

shall identify minimum skill requirements for trainees taking each course. A schedule for the

delivery of all training courses accommodating staff shift requirements must be included in the

submittal.

The training means shall be a combination of training classes and individual instruction, as

necessary. The Contractor shall fully instruct designated personnel in the operation, design,

and layout of the PACS. The training shall cover systems configuration, systems operation,

systems start up and use.

The Contractor shall:

Prepare training materials and conduct all training.

Training materials shall be provided to the Airport for review a minimum of 15 days before

training..

Training shall be conducted at the Airport’s facility and shall consist of classroom and

hands-on training on the AACS system installed in the Test/Training Environment.

Training shall be completed a minimum of two weeks prior to the system becoming

operational and utilized by the Airport. The training schedule is subject to Airport’s

approval.

The Contractor shall conduct the required training at times and locations coordinated by the

Airport. Training for three shift operations will be required. The class schedules must

accommodate shift schedules of Airport personnel and must be approved in advance.

The training shall include, but not be limited to, the following groupings of staff:

DPS (TacComm)


of 111

DPS (ASD and DPS Police)

DPS (Access DFW)

ITS

CBP

Training shall be conducted by experienced Contractor personnel using an adequate number

and amount of training material. Participants shall receive personal copies of technical

manuals and pertinent documentation. Each course’s material shall include a course

overview, prerequisite subjects/knowledge, objectives, and standards for

evaluation/successful completion.

Training shall include remote availability during the session via Airport MS Teams invite and

will be recorded in the Teams session for future viewing

A CD, DVD, or USB storage device with all course materials shall be provided to the Airport

for use in future training. The Contractor shall supply a professional video recording of each

training course.

The technical training documentation shall include OEM manuals, procedures as well as the

specific customized IT System supporting documentation.

13.12 SYSTEM ADMINISTRATION, PROGRAMMING, AND MONITORING TRAINING

The Contractor shall provide training for Airport System Administrators and Super Users; both

ITS and DPS. While ITS staff will perform the ‘system admin’ function select DPS staff, as the

system ‘owner’ will be super users. This training shall cover all AACS software, system

administration, programming, configuration and monitoring functions for ITS Level System

Administration staff and PACS configuration and Portal programming for DPS Level System

Super User Staff.

For both ITS and DPS, provide an overview of the complete system structure including

hardware, software, and networks. Describe all functions and applications needed to perform

system administration.

At a minimum, an ITS AACS (PSIM) system administrator must be able to:

Monitor system operations.

Access system logs containing warnings and error notifications.

Run audit and system health statistics and print reports.

Maintain user roles and user account configuration and management.

Manage and configure PACS software.

Perform backups of PACS system and data.

Develop, add, edit, and configure user views, Dashboard, and automated business

rules.


of 111

Develop add, edit, save, and run PACS reports.

This class must cover the reparative and preventative maintenance tasks for the

system. It will provide an in-depth trouble diagnostic tutorial with a trouble-shooting flow

chart, maintenance processes and procedures required to maintain warranty

compliance and keep the system in recommended operating order.

It is anticipated that 10 people will be trained.

At a minimum, a DPS system administrator must be able to:

Monitor PACS operations

Run access control audit and print audit logs/ reports.

Maintain user roles and user account configuration and management.

Manage and configure PACS software.

Program and configure Portals, create, copy, and edit Portal templates, add, and remove

portals from service.

Develop, add, edit, and configure user views, Dashboard, and automated business rules.

Develop add, edit, save, and run PACS reports.

This class will cover the operational and preventative maintenance tasks for the system.

It will provide an in-depth tutorial for Portal and Alarm system programming and

configuration with a trouble-shooting flow chart, programming and configuration

processes and procedures required to operate, configure, and Maintain system

functionality.

It is anticipated that 10 people will be trained.

Manuals and procedures shall include, but not be limited to, description of the tasks to be

performed during the day-to-day operation and maintenance including scheduled

maintenance, preventive maintenance, fault isolation and repair.

13.13 USER TRAINING

All airport and CBP staff that use the system shall be instructed in all aspects of the AACS

components, and application software, which are needed to perform their duties.

There must be at least four (4) types or levels for user training, based on AACS user.

Level 1 – Full System Functionality – this training will be for TacComm staff who have the

overall responsibility of monitoring the entire airport via the AACS 24/7

All AACS functions performed by TacComm staff must be covered to include at a

minimum:

Monitoring, responding to and investigating real-time portal-based alarms, airport wide,

Monitoring, responding to and investigating real-time card holder-based alarms, airport

wide,


of 111

Monitoring, responding to and investigating real-time system, field panel, cable and end

device-based alarms and notifications, airport wide,

Performing queries, research, and review of historical portal-based alarms, airport wide,

Performing queries, research, and review of historical card holder-based alarms, airport

wide,

Performing queries, research, and review of historical system, field panel, cable and

end device-based alarms and notifications airport wide,

Generating reports for all the above conditions.

It is anticipated that 35 TacComm staff members will be trained.

Level 2 – Sub-set of full System Functionality – this training will be for CBP staff who have the

responsibility of monitoring the AACS associated with the FIS areas, when the FIS is

occupied. All other times, the monitoring reverts to TacComm.

All AACS functions performed by CBP staff must be covered to include at a minimum:

Monitoring, responding to and investigating real-time portal-based alarms within the FIS,

Monitoring, responding to and investigating real-time card holder-based alarms

associated with FIS Transactions,

Performing queries, research, and review of historical portal-based alarms within the FIS,

Performing queries, research, and review of historical card holder-based alarms,

associated with FIS Transactions,


It is anticipated that 20 CBP staff members will be trained.

Level 3 – Sub-Set of full system functionality – this training will be for ASD and DPS Police

who will be using the system primarily for forensic investigations, historical reviews, and

audits.

All AACS functions performed by ASD and Police staff must be covered to include at a

minimum:

Reviewing, and investigating real-time card holder status and card holder-based

alarms, airport wide



wide,

Performing queries, research, and review of historical system, field panel, cable and

end device-based alarms and notifications airport wide,



of 111

It is anticipated that 50 ADS and Police staff members will be trained.

Level 4 – Sub-Set of full system functionality – this training will be for Access DFW, who have

the credentialing responsibility for the Airport.

All AACS functions performed by Access DFW staff must be covered to include at a

minimum:

Assigning, reviewing, and investigating real-time card holder status and card holder-

based alarms, airport wide



wide,


It is anticipated that 30 Access DFW staff members will be trained.

The ability to customize user defined parameters, response procedures and other configurable

items must be covered in detail.


of 111

14 WARRANTY AND MAINTENANCE SERVICES

14.1 GENERAL WARRANTY REQUIREMENTS

The Contractor shall warrant all systems installations, integration, software, and interfaces,

perform in accordance with all applicable standards, requirements, and specifications and

shall be without defects in materials and workmanship and design.

In cases failing to accomplish required performance and functionality as well as latent defects,

the contractor shall modify/repair all defects. The AACSI shall modify/add and/or exchange the

inadequate software if necessary, to provide the specified functionality and performance.

The Contractor shall provide a 12-month period of warranty for all components of the system

that are installed under this Scope of Work beginning at the date of final system acceptance

by the Board. This includes warranty and maintenance on all software and integrations,

including labor for all three environments.

Warranty shall include all labor, materials, and services for all products supplied as part of

Contractor’s solution, including any hardware component installed or certified under this scope

of work that is found to be defective, or that fails from normal wear and tear during the

warranty period. It also includes all product upgrades, updates, patches, and new releases at

no additional cost.

Warranty shall include the operational functionality of the software and hardware systems as

accepted by the Board at final system acceptance. For system fixes, no additional costs will

be incurred by DFW for contractor restoring system to normal operations.

Warranty service and repair work shall be performed by personnel who have been trained,

certified, and experienced in the operation and maintenance of the installed AACS.

14.2 RUN AND MAINTAIN SERVICE DEFINITIONS

General

Contractor shall provide maintenance support as necessary to keep the AACS and each

subsystem in, or restore the System to, good working order during the period for which

maintenance services are authorized. Contractor’s Period of Performance for

maintenance support shall begin after system endurance testing.

System Service Availability

System Service Availability is a measure of proportion of time the system is operating

normally as compared to the proportion of time the system is NOT available for normal

operation (downtime) due to controllable malfunctions. AACS availability is required for

regulatory compliance and is required 24 hours per day. The availability target will be

99.999%.


of 111

Preventive Maintenance

Shall mean maintenance which is performed, or required to be performed, by contractor

on a regular or scheduled basis in order to keep the system performing within normal

operating parameters.

Preventive Maintenance includes, but may not be limited to, testing, necessary

adjustments, cleaning, lubrication, and replacement of worn, defective, or questionable

parts.

Contractor shall provide to the Board a schedule of detailed planned preventive

maintenance activities to the Board's Designated Technical Representative.

Remedial Maintenance

Remedial Maintenance shall place system performance back into normal operating

parameters, and shall mean maintenance which is performed, or required to be

performed by contractor when any condition occurs that:

has caused, or may cause, the system to be inoperative.

has caused or may cause the system to be subject to malfunction.

has caused or may otherwise cause the system to fail to operate within normal

operating parameters or within the terms specified in the Base Contract.

User Maintenance

User Maintenance shall mean maintenance which is performed by the Board. User

maintenance shall include replacing consumable items for the AACS, replacing removable

magnetic recording media as required for system operation; verifying that required electric

power and required communications is available to system.

System Software Upgrade

Software Upgrade shall mean system software upgrades that consist of software

updates, upgrades, corrections, improvements, modifications, revisions, or other changes

which are logical improvements of any software component.

Upgrades shall include all enhancements, including patches, required to keep the system

software current, and secure, with the software provider's recommendations.

Severe Problem

A severe problem shall mean a problem that renders the AACS partially or wholly

unusable for its intended purpose, whether related to system hardware, software,

firmware, interface, or middleware.

Minor Problem

A minor problem shall mean any problem or issue affecting AACS operation that has not

been identified as severe.


of 111

On-Site Support

Contractor shall immediately dispatch a technician that is manufacturer trained and

certified to perform troubleshooting, diagnostic, and corrective services on the

components and operations of the AACS. Said technician shall report to the Board's

Technical Representative or designee and perform immediate remedial services to

restore the AACS to normal operating parameters.

Maximum allowable time for technician to appear on site, escalation procedures for

problem resolution, and maximum acceptable times for repairs to be completed shall be a

maximum of 1 hour.

On-Call Support

Contractor shall be available to respond to Board's request for maintenance support by

mutually agreed upon communications; telephone, text, email, etc.

Contractor shall maintain appropriate service center capabilities allowing it to receive and

respond to telephone request for maintenance support on x7x365 availability.

Contractor shall provide dedicated trained staff to respond to DFW Airport to fulfill the

SLA and shall be responsible for all components of the AACS and related subsystems

covered by the requirements of this specification.

14.3 MAINTENANCE

General

AACS equipment, and subsystems to be maintained shall include, but are not limited to

Servers, Field Devices and Edge Devices and Operator Workstations.

Contractor shall clean hardware, inspect wiring, and verify supporting power and ambient

conditions.

Contractor shall make adjustments and repairs and/or report as needed to maintain

System Service Availability.

It is noted that the AACS is required to support federal regulatory compliance for the

Airport. Strict adherence to security policies must be maintained at all times. Only the

Contractor, and the Board Technical Representative or their designee may authorize

individuals to maintain, repair or replace any portion of this system. AACS maintenance

on the SIDA line will require additional coordination with, and approval of, DPS.

For each component of the AACS the following maintenance shall be performed:

Routine Maintenance

Activities required to provide an operational AACS for Airport use. This includes routine

inspections and tests designed to identify any unusual or abnormal systems or equipment

conditions. Activities should not be conducted as to impact the System Service

Availability. Routine maintenance activities shall be as included in the Final Maintenance

Plan.


of 111

Scheduled Maintenance

Activities required to keep the AACS operating at prescribed levels of service and

reliability which are performed on a recurring basis at specified intervals. Activities

should not be conducted as to impact the System Service Availability. Scheduled

maintenance activities shall be as included in the Final Maintenance Plan.

Non-Scheduled Maintenance

Any corrective measure or repair necessitated by an inspection, a failure, or unusual

circumstances adversely affecting the normal AACS operations. Non-scheduled

maintenance may be required as a result of unsatisfactory conditions discovered during

an inspection, or because of an operational failure. Non-scheduled maintenance

activities shall be performed on a priority basis as necessary to meet required System

Service Availability.

14.4 MAINTENANCE SCHEDULE

Contractor shall perform maintenance at scheduled frequencies. Minimum frequency intervals

shall be in accordance with the table below.

Table 8 Maintenance Schedule

Hardware Maintenance Item Frequency

Servers Weekly

Field Panels and associated edge devices Semi-Annual

Operator Workstations Semi-Annual

14.5 LEVEL 1 MAINTENANCE

Level 1 Maintenance shall be performed by the Contractor staff supporting DFW.

Level 1 Maintenance is locally based and on-site for rapid response. Registers, investigates,

and classifies incidents and undertakes local and immediate efforts in order to restore a failed

service as quickly as possible and within SLA.

Level 1 Maintenance staff shall be trained on AACS hardware and software platform and will

attempt to resolve any problems reported.

If unable to resolve, Level 1 Maintenance transfers/escalates incident to expert technical

support groups.

Processes Service Requests and keeps users informed about their incident status at agreed

intervals.


of 111

Level 1 Maintenance functions include answering trouble calls regarding AACS System.

Assumes responsibility and utilizes techniques to restore failed service within SLA. If unable to

resolve, escalates incident to expert technical support groups.

Contractor shall be available 24x7 for handling trouble calls. Contractor must provide phone

number and help desk for handling all trouble calls.

The cost for Level 1 maintenance is to be included in warranty and maintenance line item.

14.6 LEVEL 2 MAINTENANCE

Level 2 Maintenance is typically located at software /hardware manufacturer’s (third-party

suppliers), from remote locations, until dispatched otherwise.

Level 2 maintenance assumes responsibility and utilizes techniques to restore failed service

as quickly as possible. Coordinates regularly with Level 1 for incident status updates.

The cost for Level 2 maintenance is to be included in warranty and maintenance line item.

14.7 SERVICE LEVEL AGREEMENT EXPECTATIONS

The Service Level Agreement intention is 99.999% system service availability. Scheduled and

allowed maintenance is generally not included in this goal.

Response is one hour to respond to a reported issue and return the item to service including

arrival at the point of service, commence assessment and complete RTS, or advise the Board

Technical Representative a responsible expectation for RTS.

Priority is generally determined by location of the issue and the impact on Airport operation

and access for our tenants, DHS, FAA, and Board staff.

Priority 1: System Applications

Priority 2: CFR 1542 listed Sterile Areas - SIDA, aircraft boarding gates, Secured Areas

at the Central Terminal Complex (CTA)

Priority 3: CFR 1542 listed Secured Areas - SIDA Airport Operations

Priority 4: CFR 1542 listed Secured Areas of the AOA

Priority 5: Secure Board Facilities

Staff Availability

Staff availability shall be the level of planned staff resources for the identified period.

Planned special events may warrant additional resources.

Final Maintenance Plan shall address planned resource levels and escalation process for

additional resources.


of 111

Availability will address the following periods:

High Availability Period

Uninterrupted staff to respond from 04:30 to 22:00 Monday – Friday.

Normal Availability Period

Staff available to respond 00:00 to 06:30 and 18:00 to 23:59 Monday - Friday and 00:00 to

23:59 Saturday and Sunday.

14.8 WARRANTY AND MAINTENANCE SERVICE LEVEL RESPONSE TIMES

Contractor shall provide 24 hour / 7 day point of contact.

Except as listed below, Contractor has 1 hour to determine issue on-site and RTS if possible,

during the hours of 0400 and 2200 7 days per week and 2 hours at all other times.

Contractor shall provide and report condition and disposition as appropriate.

If conditions exist which interfere with RTS the AHJ shall determine the acceptable condition

and method to obtain RTS.

Service level response and resolution times (from time of notification) for system failures

during the warranty period shall be:

14.9 SOFTWARE WARRANTY AND MAINTENANCE

The Contractor must provide AACS platform warranty and maintenance support during the

contract period.

The contractor is required to correct all known software bugs reported by Level 1

Maintenance. The contractor will implement a Software Problem/Change Request (SPCR)

process for reporting and correcting software issues.

During the Warranty and Maintenance period the Contractor shall be fully responsible to

provide at its sole cost, PSIM and PACS upgrades including patches and migration to new

versions at no additional costs. The Contractor is required to maintain all application software

at its most current release throughout the warranty period. This applies to all software

products supplied by the contractor.

Updates must be scheduled with ITS ahead of time. If they are downloaded, Airport must be

advised with two weeks advance notice that a new software release is available and that

notice must outline all the enhancements, fixes, and remaining known problems. Airport may

elect not to load one or more releases, and this shall not void the software support warranty.

Security patches and other patches which effect stability and security of the AACS (PSIM and

PACS) environment must be implemented within thirty (30) days of release. However, patches

which are required to protect the systems from an imminent risk shall be reviewed and

deployed on an expedited basis. Updates shall be coordinated with ITS.


of 111

The development lab environment may be used for debugging and testing fixes to issues.

Functional and regression tests will be run to ensure no negative impacts to other aspects of

the system will occur. After successful test in the development lab contractor will test fixes in

the test/ training lab. If it passes, the contractor will install the fix in the production

environment.

14.10 WARRANTY AND MAINTENANCE LABOR SERVICES

Software Configuration Management

The Contractor must always maintain configuration management of all application

software for all three environments throughout the warranty period.

Data Security Compliance

During the warranty and maintenance period, contractor shall meet all requirements of

the referenced Data Security Compliance Provisions. This includes the following:

Compliance with ISO 27002 and NIST 800-53

Compliance with 49 CFR Part 1520

Periodic vulnerability testing

Security software patches

Monthly security compliance reporting

Contractor shall notify the Airport Immediately (and follow up in writing within two days) of

discovery of any breach, suspected breach, or of any loss, unauthorized use, disclosure,

or access to any confidential data.

Disaster Recovery (DR) Exercise

During warranty and maintenance period, Contractor shall exercise the PSIM and PACS

Disaster Recovery procedures once per month to ensure that they are current and PSIM

and PACS will recover correctly from backup in event of a failure.

Service Level Agreement

A Service Level Agreement (SLA) shall be part of the AACS Integrator’s Contract.

Contractor shall provide a full description of warranty/maintenance functions and

requirements in the SLA.

The SLA requirements will include at a minimum compliance with:

System performance requirements

System functional requirements

System Security Requirements

Trouble ticket response times


of 111

Problem resolution times

A Quality of Service (QOS) Report shall be submitted monthly during the warranty period.

The QOS report must include at a minimum:

Monthly status and metrics on the performance of the AACS (including the PSIM and

PACS)

Security compliance report

Trouble ticket report showing response and resolution times.

Root Cause Analysis report for any issues exceeding Resolution Time requirements

Software/Hardware changes/patches during the month

Report of open trouble ticket items requiring hardware replacements or software fixes.


of 111

15 SUBMITTALS AND DOCUMENTATION

15.1 SUBMITTAL MEDIA REQUIREMENTS

The work under this section shall include all labor and materials necessary to complete the

writing, editing, assembling, packaging and delivery of product and systems documentation,

and training manuals in accordance with the requirements of this scope of work.

All documentation (text, graphics, illustrations, etc.) shall be delivered in both digital (CD,

USB) and hardcopy formats. The electronic documentation shall be delivered such that the

document "reads" as though the document were in printed form.

Documentation format shall be agreed with the ITS PMO. Documentation shall generally be

provided in pdf format. Engineering drawings shall be provided in AutoCAD latest version or in

certain instances for system drawings (e.g., MS-Visio format)

15.2 SUBMITTAL LOG

The Contractor shall create and maintain a log which lists all major submittal items including

descriptions of items, dates submitted, response dates and status of submittals.

15.3 CONTRACTOR CONTACTS

The Contractor shall submit company contact information two weeks after Notice to Proceed

including:

Organizational chart as applicable to this project.

Project management and technical staff names, emails, and cell phone contact

information.

15.4 SUBMITTAL QUANTITIES

The selected Contractor shall provide the following quantities of manuals, drawings, and

support documentation in both electronic and printed format:

Table 9 Submittal Quantities

Submittal Type Quantity of Submittal

System Documentation 3 sets

Training Manuals 1 per student

Test Plans and Procedures Documents 3 sets

Other Submittal Documents 3 sets

15.5 DELIVERY SCHEDULE OF SUBMITTALS

The following table depicts required delivery schedule of all submittals.


of 111

Table 10 Submittal Delivery Schedule

Submittal Due Date

Project Management Plan (w/ QAP, Project CMP, RMP,

Communications Plan) 4 weeks after NTP

Project Status Reports weekly

Submittal Log 3 weeks after NTP

Contractor Contacts 2 weeks after NTP

Meeting Minutes 2 days after every meeting

Updated System Requirements Specification 2 weeks prior to SRR

Updated Hardware and COTS software Requirements Document 2 weeks prior to SRR,

2 weeks prior to SDR

Verification Cross Reference Matrix

2 weeks prior to SRR,

2 weeks prior to SDR,

2 weeks prior to CDR

System Design Document 2 weeks prior to SDR,


Interface Control Document 2 weeks prior to SDR,


Acceptance Test Plan and Procedures 2 weeks prior to CDR

Training Plan 2 weeks prior to CDR

PACS IT Security Plan 2 weeks prior to CDR

System Implementation/Cutover Plan 2 weeks prior to CDR

Test Report – Development Environment 1 week following UAT/SAT

Punch List – Development Environment 1 week following UAT/SAT

Test Report – Test/Training Environment

1 week following Validation

Test in Test/Training

Environment

Punch List – Test/Training Environment


Test in Test/Training

Environment

Test Report - Production Environment


Test in Production

Environment

Punch List - Production Environment


Test in Production

Environment

Test Report - ORAT 1 week following ORAT

Punch List - ORAT 1 week following ORAT

Training Manuals 1 week prior to training

User Manual 1 week prior to CRR

System Administration Manual 1 week prior to CRR

Software Operations and Maintenance Manual 1 week prior to CRR

Service Level Agreement 1 week prior to CRR

As-Built Documentation 1 week prior to CRR


of 111

Submittal Due Date

Software Licenses 1 weeks prior to CRR

Disaster Recovery Plan and Procedures 1 weeks prior to CRR

Quality of Service Report Monthly during Warranty

Period


of 111

16 EXISTING AUTOMATED ACCESS CONTROL SYSTEM

16.1 OVERVIEW AND BACKGROUND

The following summary provides a high-level background of the existing AACS and current

configuration of the existing AACS in place at the Airport. The information is provided for

information only. Specific details of the Airport existing systems are considered SSI and will be

provided to the successful bidder after award.

All existing systems and devices listed below are currently maintained by the Airport AACS

Maintenance Contractor.

16.2 EXISTING AUTOMATED ACCESS CONTROL SYSTEM (AACS)

The existing AACS consists of eight (8) major subsystems, which are currently independently

managed, but essentially operate as one system. These subsystems include:


Physical Access Control System (PACS)


Access Control Management System (ACMS) – Also known as the SAFE IDMS.


Radio Frequency (RF) Coded Wireless Remote Gate Control (Genie)

The Call Light/Mantrap System (CLMS) used in support of CBP.

Airport’s Video Management System (VMS) is not formally part of the AACS but is

required to support the AACS.

16.3 PHYSICAL SECURITY INFORMATION MANAGEMENT SYSTEM (PSIM)

The current PSIM is KapLogic Aegis, Ver 3.1, migrating to Ver 3.2. The Aegis PSIM is

integrated with the following existing systems through a series of drivers that communicate

with the various vendors’ APIs. The existing PSIM is being replaced by the new Saab SAFE

PSIM, as part of the Saab Situational Awareness Platform.

Picture Perfect Physical Access Control System

Qognify NiceVision Airport Campus Video Management System (VMS) for interaction of

alarm monitoring and resolution activities.

Zenitel Alphacom Intercom system.

The PSIM unifies the access control system, video surveillance system, security intercom and

a few other ancillary systems under one common interface. The existing PSIM provides alarm

tracking, response, action plan, and reporting for security events.


of 111

The PSIM serves as the alarm monitoring and management interface for the existing PACS.

The new PSIM will be fully integrated with the new PACS as part of the Integrator SOW and

will be instrumental in managing the PACS transition.

The current PSIM system production environment contains approximately:

Windows Server 2012 (2016, 2019)

Stratus everRun hypervisor w/split-site.

The AEGIS OS Runs on Windows Server 2012; Virtual Server running on the Stratus

everRun hypervisor.

The AEGIS Database is MS SQL 2014; Database size range from 2GB-4GB; Virtual

Server running on the Stratus everRun hypervisor

Windows 10 (client)

Windows SQL 2014

Operator Stations (10)

16.4 PHYSICAL ACCESS CONTROL SYSTEM (PACS)

The existing PACS is at end of life and is being replaced by the new Lenel OnGuard PACS

Platform as part of this SOW.

The current PACS software is UTC FS Lenel Picture Perfect 4.61 and Card Access Report

Management Application (CARMA) 2.0. Head-end equipment consists of dual (redundant) Dell

PowerEdge R820 servers equipped with three (3) 1T RAID hard drives, 16G RAM and

configured for automatic fail-over in the event of a server failure. The servers run appropriate

Operating System Software (OS) Red Hat 5.11 and Application System Software for proper

operation of the PACS.

Historical storage capacity is provided by a separate networked long-term storage system,

running its own instance of CARMA.

The current PACS "field devices" consist of UTC Local Microprocessors (LMPs) and the

network systems that facilitate the required communications between the host servers and the

LMPs.

The existing PACS "edge devices" consist of UTC Lenel card readers, appropriate door

monitoring, locking and detection hardware systems. The existing PACS "edge devices" also

include operator stations consisting of workstations and associated peripherals.

The existing PACS exists in three (3) separate environments, Production, Test and

Development

The current production environment processes approximately 76,000 badge transaction

attempts per day and that Access DFW (badging office) processes between 200 and 300

badge requests per day.


of 111

The current PAC system production environment contains approximately:

Servers (2 PACS, 1 CARMA)

Field Panels (337)

Portals (2270)

Active Readers (1555)

Operator Stations (10)

35,000 Credentials

The current PAC system test environment contains approximately:

Servers (2 PAC, 1 CARMA)

Field Panels (10)

Portals (10)

The current PAC system development environment contains approximately:

Servers (2 PAC 1 CARMA)

Field Panels (5)

Portals (5)

16.5 BIOMETRIC VERIFICATION SYSTEM (BVS)

The existing BVS is at end of life. A new BVS will be selected as part of Integrator SOW and

will be fully integrated with the new PACS and the ACMS.

The current BVS software is Schlage HandNet Lite. Head-end equipment consists of a single

Dell Precision Rack 7910 500G hard drive, 16G RAM server. The server runs appropriate

Operating System Software (OS) Windows 10 Pro and the HandNet Lite application system

software for proper operation of the BVS. The existing BVS "edge devices" consist of Schlage

HandKey II units and the associated network systems for required system communications

with the host. The current BVS has been implemented in a limited number of locations and

interfaces with the existing PACS at those locations, at the field panel level only.

The BVS production environment contains approximately:

Servers (1)

Portal units (13) Enrollment units (15)

The BVS test environment contains approximately:

Servers (1)

Portal units (1)


of 111

16.6 ACCESS CONTROL MANAGEMENT SYSTEM (ACMS)

The existing Access Control Management System (ACMS) contains the identity, credentialing,

vetting and badge holder rights management functions of the AACS. The existing system is

HID (formally known as Quantum Secure) SAFE Release 4.9.1 (Build Ver 4.9.0.107) and is

managed by DPS and supported by DFW ITS.

The ACMS serves as the authoritative database for the AACS and provides user and rights

information to the existing PACS.

The primary stakeholder for this sub-system is Access DFW. The system facilitates identity

management, badge enrollment, managing credential holder authorization levels, background

checks.

Currently, only limited user information from the existing PACS is exchanged. The ACMS

holds a copy the Card Holder’s Unique ID and the associated authorization levels. The new

PACS (and PSIM) will be integrated under this integrator SOW, with the existing ACMS, to

allow for additional shared fields and to enable full PACS historical transaction reporting.

16.7 HIGH SECURITY PROGRAMMABLE SMART KEY SYSTEM (PSK)

The existing high security programmable smart brass key sub-system has been configured to

support remote, non-networked secure, regulated and operations related locations. The

current system implemented is manufactured by INTELLIKEY. The current system is

maintained by Energy, Transportation & Asset Management (ETAM) group, and has reached

its end of life.

The current INTELLIKEY system utilizes a programmable ‘smart key’ operated in an off-line

mode such that access to the locations where the keys are used are not connected in real

time with the authorization store. The key chip carries the access control and personal

identity data of the assigned key holder and can read only by site-specific INTELLIKEY

programmer unit or Lock Controller equipment.

The current PSK is not integrated with the ACMS. The new PSK system will be integrated

with the ACMS as part of this SOW and will be maintained by DFW ITS.

16.8 RADIO FREQUENCY (RF) CODED WIRELESS REMOTE GATE CONTROL

(GENIE)

The existing Radio Frequency (RF) Coded Wireless Remote Gate Control (Genie) System is

at end of life. The current system is maintained by DFW Energy, Transportation & Asset

Management (ETAM) group, and its functionality will be replaced with the new Lenel OnGuard

PACS Platform as part of this SOW.

The Airport currently has ten (10) unmanned, motor operated gates controlled by a RF Coded

Wireless Remote Gate Control sub-system that have obsolete controllers and have reached

their useful life. These gates are in operation at unmanned access to the Air Operations Area

(AOA) perimeter and they are also in operation at the Solid Waste Yard and the Fuel Farm.

The manufacturer of the control system for these gates stopped supporting the controllers a

few years ago. The maintenance is currently being performed using rebuilt equipment;


of 111

however, that equipment is no longer available. This system is at end of life. Eight (8) of these

controllers provide direct AOA Access. One (1) provides access to the Fuel Farm and One (1)

to the solid waste yard.

16.9 CALL LIGHT / MANTRAP SYSTEM (CLMS)

The existing CBP CLMS is at end of life, and its functionality will be replaced with the new

Lenel OnGuard PACS Platform. CBP will access this information and operate the system via

the PSIM configured for CBP’s use and associated Mercury Security field panel I/O, as part of

this SOW.

The current CLMS operates on an Allen Bradley PLC utilizing Flex I/O modules. The CLMS

man machine interface workstations run appropriate operating System Software (OS) and

Application System Software for proper operation of the CLMS. The current CLMS "field

devices" consist of Allen Bradley remote I/O units and required fiber communications links

between all POP and field devices for required system communications. The existing CLMS

“edge devices" consist of associated fiber optic and copper communications links, remote I/O

and with input switches and output lights for required system communications, and

appropriate door monitoring, locking and systems interfaces. System provides more than 100

duress inputs, 200 call buttons and 200 visual devices. Two Annunciation monitors are located

in two central monitor locations.

16.10 AIRPORT VIDEO SYSTEM (VMS)

The current Airport Campus Video Management System (VMS) is a Qognify NiceVision VMS.

And is integrated via the existing PSIM through a common API. The Airport is in the process

of upgrading to Qognify VisionHub VMS.

16.11 INFRASTRUCTURE TOPOLOGY SECURITY NETWORK

The current PACS, BVS, and VMS servers communicate with their field devices over a

dedicated Security LAN (local area network) and private fiber optic network infrastructure with

limited and closely controlled access to the Board’s Enterprise Data LAN (local area network).

These systems also share the network with Physical Security Information Management

System (PSIM) the video surveillance system, and the security intercom system. The Airport

Security LAN is managed by PRESIDIO (INX, LLC) for ITS.

The Airport maintains a Cisco powered network which consists of Cisco 9000-series hardware

and software platform constructed in a classical 3-tier (core, distribution, and access)

architecture. Diverse single mode fiber optic links are leveraged between the layers for

redundancy. The network cores are split between two diverse data centers. Traffic from the

access layer is typically aggregated through nearby distribution switches, before being sent to

the two cores. In locations where distribution is not available, access switches are directly

uplinked to both cores. Devices installed communicate over single mode fiber or discrete

copper between all facilities and the designated ITS data centers.

System level compatibility of hardware components integrated into the network must be

maintained to ensure the sustainability of the network environment.


of 111

The Integrator is advised that network equipment may be required to be purchased for

installation under future scope. Any network equipment proposed for purchase and installation

under the requirements of this Statement of Work shall:

Comprise the same network components that have been widely deployed in the Security

LAN and are supported by current maintenance and purchase agreements.

Incorporate into the Security LAN Remote Monitoring System

The power for the entire network is backed up by actively monitored UPS units. The amount of

backup time varies, depending on the location and critical nature of that location.

16.12 FIRE DETECTION AND ALERT SYSTEM

The current Airport fire detection and alert system is a Honeywell XLS3000 Fire Detection,

Suppression and Notification Control System. The system is deployed on a dedicated fiber

optic backbone and serves many Airport owned buildings.

The existing access control system interfaces with the fire detection system, in numerous

locations, using hardwired I/O points, for controlling portals that are required to fail safe.

16.13 AUTOMATED BAGGAGE HANDLING SYSTEMS (BHS)

The Airport has multiple automated Baggage Handling Systems in place for both inbound and

outbound checked luggage. These BHS support both domestic and international operations.

The existing PACS interfaces with the BHS utilizing card readers and monitors the system

using hardwired I/O points in order to authorize / interlock operation of the belt and monitor the

status of the associated BHS roll up door. It is currently anticipated that the new PACS will be

similarly interfaced.

16.14 ELECTRONIC MAIL NOTIFICATIONS

Notifications of certain events from the existing PACS are sent via DFW’s Office365’s

Microsoft Exchange e-mail server to predefined distribution lists, based on the event. The new

PACS will also be required to provide these same notifications.


of 111

17 ALTERNATE #1 – HARDWARE PROCUREMENT

The Airport may choose to have the Contractor procure and install all head end/server

hardware and complete workstations equipment. If this alternate is chosen, contractor shall

procure hardware specified in the Hardware Requirements List submitted during the design

phase and approved by the Airport at SDR.

Contractor shall procure and maintain spare hardware quantities to meet the availability and

performance requirements, considering installed quantities, MTBF, MTTR, redundancy and

criticality, long lead items, value, turnaround time etc. Spares shall be located on-site to allow

faulty equipment to be replaced in a timely manner.

Spare quantities will be recommended during design phase and approved at SDR.

Contractor shall be responsible for product delivery and logistics to designated staging,

storage, or installation locations.

Contractor shall be responsible for any and all loss or damage in the shipment and delivery of

all material.

Contractor shall arrange for their own logistical support to move product between locations.

Contractor, as part of final placement, shall:

Label end user devices with IP address and device name

Affix a bar code asset tag (to be provided by DFW) to all equipment/devices.

Log the asset (with required elements) to an Excel asset/maintenance register (form and

format to be provided).

Hardware will be acquired with three years of warranty included.

Contractor will be responsible for hardware maintenance throughout the warranty period.

When a piece of hardware under warranty is diagnosed as faulty, the contractor is responsible

for replacing that component.

Contractor shall be responsible for processing all hardware warranty claims and shall bear all

expenses involved in transportation, customs clearance, installation, logistics, travel costs and

lodging, shipment, and installation as well as insurance of the defective equipment to and from

DFW facilities.

If any equipment fails during the warranty period, the Contractor shall be immediately

informed. Contractor shall decide whether to repair the item locally or return it to their facility

for repair.

Contractor shall guarantee the continuous availability of spare parts throughout the warranty

period as may be required by the availability and performance, deployed quantities, MTBF,

MTTR, long lead items, turn-around time, redundancy and mission-critical requirements.


of 111

If a spare part(s) or replacement item is not available to restore equipment operation,

Contractor shall provide an immediate replacement of the failed item(s) in order to restore

operational capability at no extra cost.

Contractor shall guarantee a 7-day Turn-Around Time to replace failed items (excluding

shipping and customs clearance time). All warranty shipments shall be by express air freight

and all warranty work must be performed and re-certified expeditiously.

Once the problem is resolved, the contractor is responsible for shipping the faulty component

back to the manufacturer for repair and ordering replacements to maintain sparing levels. At

its sole expense, contractor shall immediately replenish such inventory with new parts

whenever spares are used.


of 111

18 ALTERNATE #2 - COTS SOFTWARE

The Airport may choose to have the contractor procure and install all COTS Software

required to run the PACS application. If this alternate is chosen, contractor shall procure

COTS software specified in the COTS Software Requirements List submitted during the

design phase and approved by the Airport at SDR.

Contractor shall be responsible for installing COTS software.

Contractor will include 1-year warranty on all COTS software and provide cost for an

additional per unit cost for 5 optional years.

Contractor will be responsible for keeping COTS software current throughout the warranty

period.

During the Warranty and Maintenance period the Contractor shall be fully responsible to

provide at its sole cost, COTS software upgrades including patches and migration to new

versions at no additional costs. The Contractor is required to maintain all COTS software at its

most current release throughout the warranty period.

Updates must be scheduled with ITS ahead of time. If they are downloaded, Airport must be

advised with two weeks advance notice that a new software release is available and that

notice must outline all the enhancements, fixes, and remaining known problems. Airport may

elect not to load one or more releases, and this shall not void the software support warranty.

Security patches and other patches which affect stability and security of the PACS

environment must be implemented within thirty (30) days of release. However, patches which

are required to protect the systems from an imminent risk shall be reviewed and deployed on

an expedited basis.

The development lab environment may be used for debugging and testing fixes to issues.

Functional and regression tests will be run to ensure no negative impacts to other aspects of

the system will occur. After successful test in the development lab contractor will test fixes in

the test/ training environment. If it passes, the contractor will install the fix in the production

environment.

The Contractor will always maintain configuration management of all COTS software for all

three environments throughout the warranty period.


of 111

19 ALTERNATE #3 - HOURLY TIME AND MATERIAL LABOR

Following contract award and for subsequent five (5) years, the contractor may be asked to

provide additional technical resources to the Airport to support activities in addition to the

defined requirements.

The potential activities planned for this technical support include:

AACS functional enhancements

PSIM functional enhancements

PACS functional enhancements

AACS integration with additional systems

PSIM application integration with additional systems

PACS application integration with additional systems

Implementation of PACS at additional portals

Development of workflows/SOPs and response plans for additional events

Requirements analysis and development of business rules for new AACS functionality

Modifications to PACS and PACS related business services,

Project management for additional projects associated with AACS,

System administration support.

Upon request, personnel shall be made available in the following labor categories:

Software Engineer – designs, develops, and implements AACS application solutions

including configuration and development of additional capabilities related to either the

PSIM and/or PACS platforms.

Senior Software Engineer – greater than 10 years’ experience

Interface / Integration Engineer - designs, develops, and implements software and device

interfaces and integrations between the AACS and other software applications and/or

technologies (e.g., sensors)

Senior PACS Programming Engineer – Lenel OnGuard LCE Certified, greater than 5

years of experience. Supports portal configuration updates, Boolean logic, and

portal/door PACS Software and Mercurify Security Hardware programming for new or

changed portals.

PACS Programming Engineer – Lenel OnGuard LCP Certified, greater than 3 years of

experience

Web Services Developer - designs, develops, and implements web-based software and

hardware components related to the AACS.


of 111

Senior Web Services Developer - greater than 10 years’ experience

System Administrator – manages, monitors, and maintains the AACS on a day-to-day

basis. Includes: installs (monitors install) and performs software updates; manages and

maintains users, profiles, workflows, business rules, and other configurations; monitors

and manages performance; provides Level 1 PACS application

maintenance/troubleshooting; coordinates Level 2/3 maintenance with Contractor; and

trains users.

Project Manager – coordinates and manages Contractor resources/staff for

project/delivery order work related to the AACS.

Senior PACS Technician – Lenel OnGuard LCP Certified, installs, configures, maintains,

wires and tests PACS Field Panels and end devices.

Business Analyst – defines and documents DPS and CBP business requirements,

event/incident workflows, business rules and systems/user procedures and SOPs related to

the PSIM platform.


of 111

20 ALTERNATE #4 - REFRESHER TRAINING

Contractor will offer additional/refresher training sessions for users and administrators on the

AACS on an as-needed basis. Contractor will provide pricing for one each additional session

for up to 10 attendees for the following classes:

Saab Safe PSIM TacComm and CBP User Training

Saab Safe PSIM General User Training

Saab Safe System Administration Training

Lenel OnGuard PACS TacCom and CBP User Training

Lenel OnGuard PACS ASD and Police User Training

Lenel OnGuard PACS Access DFW User Training

Lenel OnGuard System Administration Training


of 111

21 ALTERNATE #5 - EXTENDED WARRANTY AND

MAINTENANCE

Following the 1-year warranty period, the Airport will have the option of purchasing extended

application support and software maintenance for 5 additional one-year options. Extended

warranty and maintenance services include all services covered under the initial warranty

period for the base bid and any options exercised. Airport may extend warranty and

maintenance for any of the following services:

Lenel OnGuard PACS Server Application Warranty and Maintenance Support

Saab Safe PSIM Application Warranty and Maintenance Support

Lenel OnGuard PACS Client Application Warranty and Maintenance Support

Saab Safe PSIM Client Application Warranty and Maintenance Support

AACS Mobile Device Client Application Support

PACS Field Hardware and End Device Run and Maintain Services

PACS Door Hardware Run and Maintain Services


of 111

22 ALTERNATE #6 – ALTERNATE DELIVERY APPROACH AND

PHASING

The Airport seeks an Alternate Delivery and Phasing Approach which would allow doors to be

delivered at the earliest possible time.

To achieve this the Airport will would like consider an alternate/optional approach which

would integrate the new Lenel OnGuard PACS with the current Kaplogic PSIM to

eliminate schedule risk should the new PSIM implementation schedule be delayed.

The approach would have doors migrate from new PACS Lenel OnGuard to the Kaplogic

PSIM and proceed until the new PSIM is fully completed and tested.

At the point the new PSIM is ready, doors already migrated to the Kaplogic PSIM would

be transfered to the new PSIM and critical event history data (e.g. Action List events)

would be migrated, one-time, to the new PSIM.

Going forward, all doors would then migrate from new PACS to new PSIM.

Contractor will provide an outline of the approach and associated schedule demonstrating

earlier delivery. Contractor will also indicate cost impacts if any anticipated

If it is anticipated that Alternate Approach results in cost change, Contractor may be required

to provide an updated quote at the time should the Add Alternate be pursued.


of 111

23 ALTERNATE #7 – PRICING - OPTIONAL/ALTERNATE PSIM

SOLUTION

Contractor will provide a separate, second Pricing Form if an alternate (non-Saab) PSIM

solution is proposed.

Attachment 2a. Exhibit C-1 AACS Installation and Maintenance (Saab PSIM)

Attachment 2b. Exhibit C-2 AACS Installation and Maintenance (Alternate PSIM)

Integrations for both the Saab PSIM solution and the Alternate PSIM solution are subject to

scope refinement based upon proposal responses and design findings.

Contractor may be requested to review and provide an updated quote should scope

requirement of an integration be required.


of 111

24 APPENDIX 1 PSIM WORKFLOWS

1.0 Introduction

2.0 Event Types and Priorities

3.0 Workflow Format

4.0 Workflows

4.1 Upload Event Data To SAS

4.2 Access Control Events

4.2.1 Picture-Perfect Access Control System Door Alarm

4.2.2 Physical Access Control System Duress Alarms

4.3 Employee Portal Monitoring Event

4.4 Access Control Badge Issues Received by Phone/Intercom

4.5 AOA Gate Issues Received by Phone/Intercom

4.6 Bulk Cash Issues Received from TSA by Email

4.7 TSA Wireless Duress Buttons/Active Shooter

4.8 Requests for Video Forensics

4.9 Video Research in Response to Radio/Police 1 Dispatch

4.10 Video Research for Suspicious Circumstances (Virtual Patrol)

4.11 TSA Field Evaluation Test (FET) Testing


of 111

1.0 Introduction

The PSIM will integrate with the Airport’s existing Picture Perfect and new OnGuard Physical Access

Control Systems, Video Surveillance System, Identity Management System, Computer Aided Dispatch,

Emergency Notification System, Intercom, Audio Management System, and others as shown in Appendix

2 of this document.

The PSIM will support the transition from the existing Picture Perfect PACS to the new Lenel OnGuard

PACS.

Until the new AACS design is complete, the Contractor shall assume that the new PACS will continue to

utilize essentially the same PACS related workflows provided herein. It is anticipated that specific, new

detailed workflows associated with implementation of the new Access Control and Biometric Verification

Systems will be created. It is also anticipated that new doors, vehicle gates, and other alarmed devices

will be added for which alarmed monitoring and responses may require additional and/or modified

workflows, however, these existing documented workflows are not likely to change very much. Any major

changes to these workflows or new workflows will be accomplished via a delivery order.

The purpose of this Appendix is to generally define the workflows/Standard Operating Procedures for

implementation of the PSIM that the TacComm operators in the IOC (as well as the CBP officers in the

Terminal D CBP Operations Command Center) will follow when responding to and managing security

events. These workflows shall be reviewed and validated with the Stakeholders as part of the System

Requirements Validation Process outlined in this SOW. It does not cover workflows for events managed

in CAD.

Each workflow describes the anticipated / required actions for the Alarm Response Role Based Operator

(TacComm operator) and how the PSIM will be used during the event management / alarm response

process. System to System integrations and interfaces between PSIM and other systems are not

described in the workflows. These integrations are described in the System Requirements Specification.

Only Airport Short Listed AACS Integrators will be provided with a copy of these

workflows as they are considered DFW Airport Confidential and Sensitive

Information.


of 111

25 APPENDIX 2 AUTOMATED ACCESS CONTROL SYSTEM INTEGRATIONS SUMMARY MATRIX

AUTOMATED ACCESS CONTROL SYSTEM INTEGRATIONS SUMMARY TO SYSTEM

PICTURE PERFECT

OnGuard® EXISTING HID SAFE

NiceVision American Dynamics

NICE Inform Skidata PCS Zenitel

Alphacom ESRI GIS

Computer Aided

Disptach (CAD)

Everbridge (ENS)

Saab Situational Awareness (SAS)

SAAB PSIM

FRO

M S

YST

EM

Existing Picture Perfect (PACS)

Access Transaction Information

Card Holder and Security Group Information is sent to SAFE, when requested by SAFE.

Door/Point Status/Alarm information, transaction data is sent unsolicited to PSIM.

OnGuard® (PACS)

Card Holder and Security Group Information is sent to SAFE, when requested by SAFE.

Forward selected (certain) events For IOC audience. Dashboard Data for System Status

Front End Access into OnGuard Based on Roles and Rights Door/Point Status/Alarm information, transaction data is sent unsolicited to PSIM. / Access to Reports

Existing HID SAFE

Card Holder Information and Security Groups is sent to PP as this information is updated in SAFE.

Card Holder Information, Zones, Groups. Threat Level, access rules. Multi-Factor Rules Are sent as updated

Card Holder PII, Photos and Security Groups with Associated History and IDMS Transaction Dates is sent to the PSIM when requested by the PSIM

NiceVision

Camera call up and NVR status information, when requested by the PSIM


of 111


PICTURE PERFECT




Alphacom ESRI GIS

Computer Aided

Disptach (CAD)

Everbridge (ENS)


SAAB PSIM

American Dynamics

Camera call up and Switcher state and status information, when requested by the PSIM

NICE Inform

Audio /Video recorder status, when requested by the PSIM

Skidata PCS

Real Time access to LPR and Toll Tag Data (including Vehicle Overview and OCR Info)

Zenitel Alphacom

Intercom station calls and other events are sent unsolicited to the PSIM.

ESRI GIS Common System Map

Computer Aided Disptach (CAD)

Event Messaging /Event Coordination

Everbridge (ENS)

Notification Status updates




of 111


PICTURE PERFECT




Alphacom ESRI GIS

Computer Aided

Disptach (CAD)

Everbridge (ENS)


SAAB PSIM

Saab PSIM

Control Information (Unlock/Lock) and Alarm Acknowledgement is sent to, when initiated by a TacComm /CBP operator.

Front End Access into OnGuard Based on Roles and Rights Control Information (Unlock/Lock) and Alarm Acknowledgement is sent, when initiated by a TacComm / CBP operator.

Facilitate access to HID SAFE - Roles / Rights based access for Card Holder data modifications (including termination and adding notes)

Call up cameras and control cameras

Call up cameras and control cameras

Call up and play back audio.

Request for Real Time Toll Tag and LPR data (including Vehicle Overview and OCR Info) for Data Searches

Initiate a call to an intercom station. / communicate with an Intercom Station

Automatically populate fields in event management tracking forms. Allow tracking form to be called up.


Alert Notifications sent As Required (front Event Or part of Workflow)
