RFP Attachment B Statement of Work - 00001- Tracked Changes.pdf

Transportation Security Administration (TSA) Acquisition Program Management (APM)

Statement of Work (SOW) Purchase and Installation Competition

Amendment 00001

1.

1.1 Location of Work

All work shall take place at the Contractor’s facility and the following locations:

Site Code

Airport

MSEDS

Shipping Address

EUG Eugene Airport Up to 4 Eugene OR 97402

ORF Norfolk International Airport Up to 4 Norfolk VA 23518

SAV

Savannah/Hilton Head

International Airport Up to 4 Savannah GA 31408

BNA Nashville International Airport Up to 7 Nashville, TN 37214

CMH

John Glenn Columbus

International Airport Up to 3 Columbus, OH 43219

LIH Lihue Airport Up to 3 Lihue, HI 96766

TUS Tucson International Airport Up to 3 Tucson, AZ 85756

*Site Codes/Airports are subject to change

1.2 Project Milestones

The following table lists key milestones and estimated dates for each project. Dates are subject to change based on each of the airports’ final schedule. The COR will notify the Contractor of the updated schedule upon contract kick‐off. Upon Exercise of an Optional CLIN for an associated airport, the COR shall provide the Contract the final schedule for the airport. The warranty periods are not included in this timeline; warranty periods are based on EDS installation and passing the Site Acceptance Test (SAT).

Optimal Timeline (Estimated Dates noted by Month-Year)

Airport Design Start Design

Complete

Construction MSEDS Delivery

ISAT

Testing

Go Live 30-Day Run-In

Project Completed Bid/Award Start

EUG Sep-23 Nov-25 May-26 May-26 Apr-26 Mar-27 Dec-27 Dec-27 Dec-28

ORF Sep-24 Jun-27 Jan-27 Oct-27 Sep-27 Jan-28 Feb-28 Mar-28 Nov-28

SAV Mar-24 Jun-26 Mar-27 Apr-27 Apr-28 Dec-28 Jan-29 Jan-29 Feb-30

BNA Aug-23 Apr-25 Mar-25 Jun-25 Nov-25 Sep-26 Oct-26 Nov-26 Jan-27

CMH Sep-24 Mar-26 Mar-26 Mar-26 Dec-27 Jun-28 Jul-28 Jul-28 Sep-29

LIH TBD TBD TBD TBD TBD TBD TBD TBD TBD

TUS TBD TBD TBD TBD TBD TBD TBD TBD TBD

NOTE: The Airport Authority is required to provide a construction schedule to TSA 60 days after award of the TSA Facility Modification (FACMOD) Other Transaction Agreement (OTA). The Contractor will be provided a copy of that schedule by the COR when it is available. The schedule may be changed to accommodate airport schedule changes that occur after contract award. Schedule changes will be shared by the COR with the Contractor, but will not result in a contract modification. When an airport reaches its "Design Complete" date is when the Government anticipates exercising Option CLIN(s) for a specific airport. The COR will issue a Technical Direction Letter (TDL) for that specific airport prior to the 6‐month delivery date. The airport delivery location shall not be changed once a TDL is executed; the expected delivery date of equipment may need to be flexible to accommodate the airport schedule. See TDL guidance in Section 1.3 below. Should the Government delay exceed the delivery date over two weeks of expected delivery date, the Contractor shall coordinate the delivery schedule with the Government to make shipment of the ordered equipment to the TSA Warehouse.

1.3 Time of Delivery

Transportation Security Equipment (TSE) shall be delivered within six (6) months of authorization to proceed and in accordance with all projects schedules as identified by the Government. Delivery shall occur during the contract’s period of performance.

The Government shall issue one or more Technical Direction Letters (TDLs) over the period of performance (PoP) of this contract. TDLs will include the following information:

1. CLIN Number(s)

2. Quantity Needed

3. Delivery Location

4. Date Needed

The Contractor shall be responsible for accepting the terms of the TDL within five (5) business days of receipt of the TDL, or notifying TSA (within the same time frame) that the Contractor is unable to meet the terms of the TDL. No response from the Contractor to the CO within five (5) business days will constitute acceptance of the TDL. The delivery lead time necessary for the production and delivery/installation of equipment will begin upon acceptance of the TDL, or five (5) business days after issuance of TDL (in the case of non‐response). Prior to the end of the contract PoP, if a delivery location and date have not been provided within the applicable lead time, the remaining equipment shall be sent directly to the TSA Logistics Center (TSALC).

2. Background The Transportation Security Administration (TSA) is charged with the mission of protecting the nation’s transportation systems to ensure freedom of movement for people and commerce. The mission of TSA’s Acquisition Program Management (APM) is to deliver innovative, mission‐driven capabilities required by the frontline to safeguard America’s transportation system.

TSA uses security‐related technologies to help secure approximately 2.2 million passengers, 1.4 million checked bags, and 4.9 million carry‐on bags on 6,000 flights at roughly 450 federally regulated airports every day. TSA deployed about 15,900 units of security‐related technology to airports nationwide. APM provides security‐related technology solutions for checked baggage screening through the Passenger Screening Program and Electronic Baggage Screening Program (EBSP). The focus of this requirement is on the EBSP technologies to help ensure that TSA screens 100 percent of checked baggage for explosives, as mandated by law.

2.1 Overview of Services

This Statement of Work (SOW) defines the requirements for the production, installation, integration, networking and testing of up to 28 MSEDS and associated peripherals for the various airport locations to be determined. Oversight and authorization for services shall be provided by the TSA. Exclusive of System Integrator (SI) activities, the Contractor shall provide services for the installation, integration, networking and testing of MSEDS. In addition, as a part of this contract, the contractor must provide all ancillary materials not already procured as Government Furnished Equipment (GFE).

Documents created for fleet management support services (see next section on Security Technology Support Services) such as the Program Management Plan, Risk Management Plan, Security Program Plan, and Facility Security Certificate may be applicable to activities under this contract, but must not be duplicated and/or reimbursed under this contract as well.

All services requested under this SOW are non‐personal in nature.

2.2 Fleet Management Support Services ‐ (Not priced under this contract):

Certain standard "equipment fleet management" functions will include information about or pertaining to this requirement. The support for those functions is established under separate contracts (i.e. current STSS IDIQ contracts) established by TSA for all Transportation Security Equipment (TSE) manufactured and/or supported by the Original Equipment Manufacturers (OEMs). The scope of these contracts is OEM provided system management support, engineering support services, and Information Technology (IT) security support services to support all new, current, and legacy TSE systems in all airports, all TSA warehouses, testing facilities, or other locations as specified at the award of a task order. Documents created for those contracts and task orders, such as the Program Management Plan, Risk Management Plan, Security Program Plan, and Facility Security Certificate, may be applicable to activities under this contract.

The Support Services listed below are covered under separate fleet management contracts:

Program Management Reviews

Weekly Project Status Calls

Configuration Management

Quality Assurance

Risk Management Plans

Security Program Plan

Facility Security Certificate

2.3 Configuration Management‐ (Not priced under this contract):

Configuration Management is covered under separate fleet management contracts/task orders. The information below is to provide a brief understanding of the Configuration Status expected of the equipment.

Configuration Baselines

The Configuration baseline, heretofore referred to as the PBL, is established as part of the MSEDS Testing, Certification, and Qualifications activities prior to DHS authorization for full‐rate production. It is continuously updated as a part of the ongoing improvement efforts between the contractor and TSA for all equipment on the Qualified Products List (QPL). The PBL for this effort will be based upon the most recent approved configuration prior award of this contract.

Configuration Identification (CI)

The CI identification must be included in a MCIL separately maintained under separate fleet management contracts/task orders. All system CIs and top level hardware and software CIs must be uniquely identified.

2.4 Project Management Reviews (PMR) ‐ (Not priced under this contract):

The Contractor will include the scope of this contract during the currently scheduled conduct monthly Program Management Review Meetings that will cover the entire Engineering, Production, and Installation projects for the entire TSA fleet of equipment for each OEM under separate fleet management contracts/task orders, and therefore, shall not be priced under this contract. The Contractor shall provide a monthly update to be included in the monthly fleet management PMRs. The Government reserves the right to request a supplemental teleconference should more time be needed to discuss issues at this particular site. The Contractor shall prepare and submit a PMR slide to be included in the fleet management PMRs in accordance the CDRL identified below, and submit it for review 5 days prior to the monthly PMR.

2.5 Project Status Reporting

The Contractor shall provide Project Status Reporting in conjunction with participating in a weekly/bi‐ weekly teleconference at which they will provide updates pertaining to all activities that will impact the contract period of performance, required testing or training activities, equipment installation and de‐ installation activities, associated Contractor driven schedules, and equipment movement and logistics activities, and any other project‐related activity. The Contractor shall report all commercial efforts where Government property MSEDS will be impacted, modified, removed, installed, or relocated on the Project Status Report; these commercially funded projects require Government approval prior to authorization to proceed because of its status as Government property and the need to ensure testing and logistic requirements are executed as required.

For this requirement, the Contractor personnel must provide a weekly update to the Contractor's staff member who will report for all projects during the weekly fleet management WPS conference calls.

2.6 Third Party Efforts

As a part of these installations, several third parties will be responsible for certain parts of the delivery and installation of the GFE. The third parties and their responsibilities are outlined below:

The Rigger is responsible for:

Implementation of the Contractor rigging specifications. Off‐loading or up‐loading upon delivery or pick‐ up, temporary storage, and/or any other equipment movements as needed. Providing adequate protection (above and beyond required shipping and packaging protections identified in the Packaging) to the EDS and ancillary equipment and to the site infrastructure during any and all equipment movements. Supporting all crating activities as required including crating, uncrating, or crate disposal.

2.7 System Integrator (SI)

The Government will designate a Systems Integrator (SI) that will act as the Primary Logistics Coordinator for this effort. The SI will be the primary point of contact for each installation to assist in the facilitation of installation, and temporary local storage (if necessary). The SI will receive and maintain copies of all plans, reports, and any additional documentation pertaining to this effort. The SI must be included in all communication and resolution of site installation issues. The SI will coordinate with the Government to resolve site installation matters.

The System Integrator is responsible for:

Shipping of the MSEDS equipment (CLIN 0010) unless otherwise specified.

Communicating with TSA, Riggers, and the Contractor regarding the schedule for installation and testing of the ancillary equipment. This will include (but is not limited to) coordinating the arrival of equipment at the facility, storage of equipment as needed, as well as verifying readiness of the airport for installation.

The system integrator will be responsible for identifying and confirming with the Airport Authority the conveyor line centerline and the final acceptance of the MSEDS position upon the conclusion of rigging and MSEDS placement. Additional efforts to move the MSEDS, if located by others, may require a change order to disassemble relocate and reassemble MSEDS to the new centerline.

The SI does not have the authority to make changes to scope, price, schedule, or terms and conditions of this SOW. In addition, the SI does not have the authority to sign contractual documents, order changes, modify contract terms, or create any commitment or liability on the part of the Government.

2.8 Airport Authority

The Airport Authority is responsible for:

Architectural and Engineering designs of the anticipated Baggage Handling System (BHS)

All construction efforts and coordination for necessary infrastructure to support the MSEDS components.

Any airport infrastructure modifications necessary to allow the movement and placement of MSEDS equipment within the airport.

Providing services to remove and replace any walls, windows, glass, doors, or other physical barriers in support of rigging activities

Providing the rigging egress path.

Performing structural analysis for floor loading requirements.

Rescheduling or prohibiting other trades or vendors to work in the affected areas while the MSEDS equipment is being delivered.

Power Requirements: Infrastructure power terminations to the MSEDS will be performed by the Airport Authority. The Airport Authority will be responsible for providing all infrastructure power requirements. If applicable, the Airport Authority will design and install all power requirements to terminal locations within any resolution area and at MSEDS locations.

(Remainder of this page intentionally left blank.)

3. Technical Requirement\Tasks\Outcomes

3.1. Services Overview

The Contractor shall be responsible, exclusive of System Integrator and Rigger activities, for all labor, materials, equipment, and support services needed to manufacture, assemble, power up, configure, and install, and test the MSEDS and ancillary equipment and the requisite networks into the required operational condition. This includes any system component, software, or conveyor entrance and exit configuration needed to meet the end‐state required configuration. Installation and testing of the MSEDS shall minimize, to the extent possible, disruption or interference with airline or airport operations.

The Contractor shall, at a minimum:

Provide technical consultation in support of design efforts, from 30% through 100% Design as well as pre‐ Installation efforts.

Provide all necessary equipment as authorized upon exercise of the equipment CLINs, and deliver the equipment in accordance with agreed upon schedules.

Provide appropriate support and engineering services for all installation, integration, and networking activities.

Coordinate with the Airport Authority, Systems Integrator, and TSA (prior to equipment delivery and installation) with the sites to minimize the impact on day‐to‐day operations at the sites and their related systems. Any disruptions or interference with airline or airport operations, resulting from the MSEDS assembly, power up, configuration, and installation activities that cannot be avoided shall be closely coordinated with and approved in advance by the affected parties prior to commencement of such activities. The Contractor shall perform work at night, weekends, or other varied nonoperational hours when required.

The supplies and services described herein shall be performed in accordance with this SOW and all requirements in Procurement Specification for Checked Baggage Screening Technology Medium Speed Explosives Detection System and Procurement Specification for EDS Training Simulator.

All references to the "Government" in this SOW shall mean by authority of the CO or designee. All digital media submitted to the Government in response to SOW requirements shall be compatible with the Microsoft Office suite of products or Adobe format. Acceptable digital media are Compact Disc—Read Only Memory (CD‐ROM) or Digital Versatile Disc (DVD).

Where specific sections are referenced in this SOW, it is intended to also include all subordinate sections.

3.2. Support Services

The Contractor must provide fully functional, qualified equipment including all the hardware and software required to verify compliance requirements as stated in:

Procurement Specification for Checked Baggage Screening Technology EDS version 3.2.

As defined in the Planning Guidelines and Design Standards (PGDS).

In accordance with the most current TSA approved Production Baseline (PBL), as documented in the TSA Master Configuration Item List (MCIL) in effect at the time of deployment.

The Contractor must be responsible for all labor, materials, equipment, and support services needed to deliver, assemble, power up, configure and test the equipment in the required operational condition. This includes but is not limited to any system component, software, or conveyor entrance and exit input and output modules, local control consoles to meet the end‐state required configuration.

The Contractor must maximize the use of COTS hardware and software to meet the Contract requirements.

The use of commercial items does not exempt the Contractor from complying with the SOW requirements.

The Contractor must ensure that all hardware, software, and documentation required for the operation and support of the EDS are provided as part of the supplies and services stated herein.

The Contractor must maintain an Installation Manual that describes the necessary instructions and requirements for the installation, setup, and configuration of the EDS. The Installation Manual must include any special instructions or requirements such as orientation, environmental requirements, power connectivity, maintenance access, and all site planning guidelines that would impact installation, operational, and/or maintenance capabilities.

CDRL:

C023, Installation Manual

The Contractor must maintain an Operator Manual that describes all functions for the operation of the MSEDS systems. The Operator Manual must include detailed instructions on how to execute each function. The Operator Manual must include any troubleshooting guidance necessary or appropriate to resolve errors; not requiring corrective maintenance by qualified technicians. The Operator Manual must identify and provide the procedures for all Level 1 Preventive Maintenance and Level 1 Corrective Maintenance activities as defined in Section 3.6.6 and 3.6.7 of this SOW and applicable sections of Integrated Logistics Support Contracts that meet these requirements. The Operator Manual must describe any operations of the Contractor's network management, remote monitoring and control system functions, and procedures.

CDRL:

C022, Operator Manual

Where specific sections are referenced in this SOW, it is intended to also include all subordinate sections.

(Remainder of this page intentionally left blank.)

3.3. Support & Engineering Services Tasks Pricing for all Service CLINs includes all Labor, Travel, and Other Direct Costs necessary to perform all tasks associated with the CLIN.

3.3.1. Project Coordination (CLIN 0002 Base Year) [1002‐ 7002 Optional]

The Contractor shall be fully responsible for providing all equipment and work described in the SOW. The Contractor shall establish and maintain a formal plan to manage the requirements in this SOW. The Contractor shall efficiently and effectively execute the requirements of this SOW.

CDRLs:

C002, Meeting Minutes

3.3.1.1. Pre‐Planning Communications

The Contractor must participate in all necessary pre‐planning conference calls and meetings necessary to support the installation of the EDS.

3.3.1.2. Post Award Conference (CLIN 0002 Base Year)

A post award conference will be conducted via conference call within thirty (30) calendar days after the contract award. The TSA will designate Government conference attendees and will identify any unique conference support requirements. The Contractor must support the post award conference as needed and must provide the minutes following the conference.

During the post award conference, the Contractor must be prepared to address, at a minimum, a review and status of the following topics:

CDRL submission status and projected schedule;

Invoicing procedures;

Project milestones;

Organizational status;

Schedule and performance (technical) aspects of the SOW;

Quality elements;

Lines of communication.

CDRL:

C002, Meeting Minutes

3.3.1.3. Contract Data Requirements Lists (CDRL)

The Contractor’s Project Coordinator must be responsible for preparation and delivery of all CDRL, which are referenced in this SOW. The full list of CDRLs can be found in SOW Section 3.16 and included in SOW Attachment B. Data Items Descriptions (DIDs) referenced by their CDRL titles are to be developed in accordance with the CDRL of the same name. All data deliverables must be prepared or updated and delivered in accordance with the corresponding CDRL items specified under the SOW requirement.

Section 3.16 contains the full list of CDRLs for reference.

3.3.2. Airport Design and Preplanning Technical Consultation/Support (CLIN 0003 & 1003)

3.3.2.1. Pre‐Planning and Third Party Coordination

3.3.2.1.1. The Contractor must coordinate with COR, Rigger, and SI regarding equipment rigging and shipping logistics. The Contractor must coordinate the work schedule with the SI, Airport Authority and/or the local TSA. The SI must contact the Airport Authority POC 72 hours prior to delivery/pick up to determine delivery/pick up location and to avoid impacting airport, airline, or local TSA operations. The SI and/or Contractor must schedule and coordinate delivery/pick up in advance of delivery/pick date.

3.3.2.1.2. The Contractor must witness rigging and uncrating activities in order to ensure that Contractor standard practices and specifications are implemented.

3.3.2.2. Design and Pre‐Installation Support

The Contractor shall provide design support to TSA and the Airport Authority between the 30% ‐ 100% design phases, as well as Construction Pre‐Equipment Installation efforts for four (4) phases of construction.

This includes providing equipment specifications to the Airport Authority Points of Contact (Airport POCs) (Airport POC List ‐ Attachment C) to assist in the design of the overall BHS. This may include, but is not limited to:

3.3.2.2.1. Technical Consultations for design specifications and recommendations. The Contractor shall provide technical consultations to the Systems Integrator and Airport Authority representatives during the site design and installation engineering phases of this project. The Contractor shall provide recommendation and support for the necessity for equipment infrastructure requirements to be taken into account to meet equipment specifications, including any data cabling and electrical requirements. The recommended equipment layout must, to the extent possible, provide clear and unrestricted access to any rack or equipment unit, including consoles, to permit equipment maintenance or removal.

The Contractor may be requested to provide recommendations and feedback regarding the structural analysis of the airport. Note: This may include limited support post 100% Design approval, prior to installation commencing.

3.3.2.2.2. Provide infrastructure recommendations to support an Optimum Network design.

3.3.2.2.3. Conference calls with Airport Authority representatives for additional support as necessary.

3.3.2.3. Site Survey / Site Visits

The Contractor shall conduct up to one (1) site visit/surveys per airport project for the purpose of providing network and infrastructure design recommendations and specifications to assist with the BHS design.

The Contractor shall conduct a site survey and submit a Site Assessment and Survey Report (SSR) for the site. The Contractor shall coordinate with the Government concerning access to the MSEDS installation site prior to performing the required site surveys or as directed and approved by the Government.

Depending upon the extent of Site Assessment and Survey required by the Government, the SSR may consider special service requirements for modifications to electrical power, environmental control, communication services, floor loading, equipment handling, and access clearance requirements.

The Contractor shall consult with the appropriate airline and airport representatives to determine any special operational or facility considerations including existing or planned terminal modification or construction that must be accommodated. The SSR shall describe the site modification requirements, site‐ specific MSEDS equipment requirements, and any site‐specific deficiencies that must be addressed in order for the equipment provided by the Contractor to be installed and made operational. The Contractor shall take into account, in preparing the SSR, the BHS design efforts that are being undertaken by the airport and how the requirements and deficiencies identified in the SSR can be addressed by the airport’s BHS design efforts.

C008, Site Assessment and Survey Report

3.3.2.4. Infrastructure Recommendations

3.3.2.4.1. The Contractor must provide the Airport Authority the contractor’s recommended network infrastructure to support an optimum network design, with enough time for the airport authority to ensure network infrastructure adequacy. In addition, the contractor must communicate with the airport authority to secure optical loss budget verifications for fiber and continuity with copper CAT 6 or CAT 5e and verify that existing connections are functional at Gigabit speed.

3.3.2.4.2. The Contractor must assess where IT Physical security and other considerations are met or capable of meeting when the system is installed. This includes but is not limited to:

ability to have separated TSA MSEDS network with no other equipment having access to the network.; Network rooms have the appropriate ventilation; Network rooms have the appropriate fire protection; Network rooms have the appropriate control access. (Note: The Network Acceptance Testing (NAT) will serve as the final report post installation.)

3.3.3. MSEDS Equipment Installation (CLIN 0004) [Optional]

If exercised, the Contractor shall be responsible, exclusive of System Integrator activities, for all labor, materials, equipment, and support services needed to assemble, power up, configure, and install the MSEDS Scanner into the required operational condition. This includes any system component, software, or conveyor entrance and exit configuration needed to meet the end‐state required configuration. Installation and testing of the equipment shall minimize, to the extent possible, disruption or interference with airline or airport operations. The Contractor shall work in conjunction with the Systems Integrator (Refer to Section 2.7 System Integrator).

The Contractor shall, at a minimum, participate in and at times schedule the installation activities, prior to installation, with the sites to minimize the impact on day‐to‐day operations at the sites and their related systems. Any disruptions or interference with airline or airport operations, resulting from the equipment assembly, power up, configuration, and installation activities that cannot be avoided shall be closely coordinated with and approved in advance by the affected parties prior to commencement of such activities.

The Contractor shall perform work at night, weekends, or other varied nonoperational hours when required.

The Contractor shall conduct a Site Acceptance Test (SAT) at every installation site location for each installed MSEDS, in accordance with the Government‐approved SAT Plan and Procedures. The SAT will confirm that the MSEDS is properly set up, operationally configured, and remains in compliance with contractual requirements. The SAT will be witnessed by Government and/or Government designated contracted representative(s). All equipment is subject to Government approval for each installation site configuration.

3.3.3.1. Site Acceptance Test Plan

The Contractor shall prepare a SAT Plan that describes methods for testing, evaluating, and accepting the MSEDS at each site. The Contractor's SAT Plan shall define the range of tests, system initialization requirements, input data, expected output, and the criteria for evaluating test results. The Contractor shall identify all Test and Evaluation (T&E) resources required, including personnel, and equipment. The Contractor shall identify all mitigation plans and procedures in the case of failed testing events.

The Contractor shall deliver the MSEDS SAT Plans in accordance with the following referenced CDRL:

C010, Site Acceptance Test Plan

3.3.4.2. Site Acceptance Test Procedures and Reports

The Contractor shall prepare SAT Procedures that detail the step‐by‐step test process to be conducted during each SAT. At a minimum, a separate SAT Procedure shall be prepared and submitted for each MSEDS. The Contractor shall ensure that the test procedures indicate traceable paths to the approved Contractor Verification Requirements Traceability Matrix (VRTM). The Contractor shall prepare a SAT Report and Quick Look Report (QLR) at the conclusion of each test.

C011, Site Acceptance Test Procedures C012, Site Acceptance Test Report C007, Quick Look Report

All equipment is subject to Government approval for each installation site configuration.

3.3.4. MSEDS Baggage Handling System Integration (CLIN 0005) [Optional]

If exercised, the Contractor shall accommodate and support, as necessary, any and all integration and testing activity by the BHS Contractor (BHSC), Systems Integrator, the site authority, and/or the Government or designated representative throughout all phases of the MSEDS BHS Integration effort to include MSEDS integration, BHSC testing support, Test Readiness Report (TRR) testing support, ISAT testing support, and operational run‐in support. The Contractor shall only take direction from the Government representative(s) to schedule testing activities, which includes only the Government deployment project lead or manager, CO, or COR. For all testing phases the Contractor shall provide support efforts to include, but are not limited to:

providing technical consultation, ensuring the MSEDS will be operationally available to support testing activities and promptly notifying the Government and/or Government contracted representative in advance, if testing must be rescheduled.

The Contractor shall prepare a BHS Integration Test Report (ITR) for each construction phase to verify that the system is ready to enter ISAT. The report shall provide evidence that MSEDS BHS is connected properly and results for each ISD tested shall be recorded.

Integration Milestone completion at TSA Acceptance of the BHS ITR identifies the system is ready to enter ISAT. TSA has 5 business days to review the BHS ITR and address any concerns with the report.

The Contractor must maintain an Integration Manual to include, but not be limited to, special instructions or requirements for the Baggage Handling System (BHS) and interface programming; SVS and barcode scanner implementation; discrete signals; dieback operations; timing requirements; bag Identification (ID) formats;

and any other information or data required to describe installation, operational, and/or maintenance capabilities. The Contractor must develop all integration documentation and specifications in accordance with the requirements outlined in the Checked Baggage Inspection System (CBIS) Interface Requirements Document. The Contractor must use The Planning Guidelines and Design Standards for Airport Checked Baggage Inspection Systems (PGDS) as guidance and a reference in developing the BHS to MSEDS interface specifications.

C024, Integration Manual

3.3.4.1. Explosives Detection System Integration

The Contractor shall install and test the required software and hardware to allow implementation of MSEDS operations and provide MSEDS integration in accordance with Checked Baggage Inspection System (CBIS) Interface Requirements Document and the Planning Guidelines and Design Standards for Airport Checked Baggage Inspection Systems (PGDS). The Contractor shall provide resources to assist the site authority with the BHSC to establish data communication between the MSEDS units and BHS at the project site.

Functionality of the MSEDS’ BHS interface hardware and software shall be verified by the Contractor at the interface box prior to working with the BHSC to ensure a proper operating interface. Terminations to the MSEDS for BHS communication will be performed by the BHSC. The Contractor shall provide any required system component equipment and installation to facilitate the integration with the BHS. All integration and testing issues shall be reported to the Government in the ITR. Once communication between devices has been established, the Contractor shall provide continuous support and integration services per direction of the Government and/or Government contracted representative.

3.3.4.2. Baggage Handling System Contractor Testing Support

The Contractor shall provide onsite assistance to the BHSC to obtain efficient MSEDS operation and facilitate the entire integration effort with the BHS. The onsite support shall have sufficient knowledge to assist in validation of all input, output, and timing signals from the MSEDS. The Contractor shall be able to distinguish between MSEDS specific issues and non‐MSEDS issues involving solely BHS troubleshooting, and shall report that information accordingly. All integration and testing issues shall be reported to the Government in the ITR. In the event where testing activities are rescheduled, canceled, failed, or halted by the BHSC or the Systems Integrator, the Contractor shall notify the Government and immediately halt testing support activities allowing no more than two (2) hours of waiting on standby for testing activities to commence.

3.3.4.3. Test Readiness Review and Testing Support

The Contractor must provide support efforts to include, but are not limited to: being available to support system testing and validation conducted by internal or external organizations including a Site‐Specific Test Plan (SSTP) survey meeting for the ISAT, pre‐ISAT CBIS testing, TRR and ISAT; and being available throughout all phases of this requirement. The Contractor must coordinate with the Government or designated contracted representative to receive copies of the SSTP for sites covered and be kept apprised of testing schedules. All integration and testing issues must be reported to the Government in the ITR in accordance with the below identified CDRL. When determining resources, the Contractor must, at a minimum, plan on one (1) test effort and one (1) retesting effort for each construction phase.

C014, BHS Integration Test Report C015, BHS Interface Control Document E032, Test Readiness Review (TRR) Report

3.3.5. Multiplex Network Installation and Network Acceptance Test (NAT) (CLIN 0006) [Optional]

3.3.5.1. Multiplex Network Installation

If exercised, the Contractor shall install, integrate, and test a network that will function with the MSEDS in accordance with this SOW. Network size shall be determined by maximum network elements, to include, but not be limited to, the network server, the maximum quantity MSEDS to be networked, the maximum quantity of PVS and SVS, required network switch port sizes, and the control interface to accommodate site specific network topologies. The Contractor shall provide all labor and materials necessary to complete this task.

Prior to the network installation, the Contractor shall have communicated with the Airport Authority regarding the Contractor’s recommended network infrastructure, with enough time for the Airport Authority to ensure network infrastructure adequacy.

The Contractor must provide all labor and materials necessary to complete this task.

Providing specific project management, technical support services, and documentation control to support site specific network design review and site planning;

Configuring, creating, and testing software and hardware packages;

Installing and connecting, as required, all separately purchased CLINs to include, but not be limited to the:

o PVS (CLIN 0011), o SVS (CLIN 0012), o SVS Mounting Kit (CLIN 0013), o Printer (CLIN 0015), o Network equipment package (to support up to 7 EDS) (CLIN 0016‐2016), and o Master Control Station (CLIN 0017);

Procuring and installing all network ancillary equipment required to install and test the network equipment to include, but not be limited to, network switches, patch cables, enclosure racks, media converters, and connectors;

Deploying a Network Engineer to the site;

Providing site specific training and materials for network operation;

Performing baseline network infrastructure testing;

Conducting Integrated Network ORT; and

Supporting all travel and shipping expenses as required.

Prior to the network installation, the Contractor must have communicated with the airport authority regarding the contractor’s recommended network infrastructure, with enough time for the airport authority to ensure network infrastructure adequacy.

3.3.5.2. Multiplex Network Acceptance Test and Reports

The Contractor shall conduct and prepare NAT Procedures that detail the step‐by‐step test process to be conducted during each network SAT. The test procedures shall address the entire Network. The Contractor shall ensure the test procedures indicate traceable paths to the approved Master Test Plan (MTP) VRTM. The Contractor shall prepare a QLR and a NAT Report at the conclusion of each test. Set‐ up of the network in preparation for the NAT and conduct of the NAT are included under this effort. All equipment is subject to Government approval for each installation site configuration.

The Contractor must conduct and prepare NAT Procedures that detail the step‐by‐step test process to be conducted during each network ORT. The test procedures must address the entire Network. The Contractor must ensure the test procedures indicate traceable paths to the approved Master Test Plan VRTM (MTP VRTM). The NAT must include detailed information to the level necessary to show adequacy of the proposed methods, deliverables, and success criteria for verification of performance objectives compliance. The Contractor's plan and procedures must include:

a. Establish and document the testing plan, procedures and criteria for completing NAT

b. Include supporting Government witnessed activities during NAT execution

c. Incorporate physical security measures adopted to control risks, and documentation that specifically addresses recommendations on;

Physical access control for network devices and wiring closets

Physical security for information systems, applications, databases, electronic interfaces, and network cabling

Physical security access controls

Physical security and access controls for data processing hardware

Physical security for data media and backups

Physical security for data access points

IT Network Topologies to include as Design and as Is Diagrams (i.e., Cabinet Rack Elevation Drawings & Details)

Network diagrams

d. Incorporate physical safety measures adapted to control risks, and documentation that address fire/smoke detection and fire suppression systems.

e. Incorporate posting of "Access Controlled Lists" (ACL) on exteriors of all IT cabinets.

f. Incorporate posting of "Sign in/Out Sheets" within interiors of all IT cabinets.

g. Incorporate Network Equipment End Point (NEEP) inventories for all MSEDS elements.

h. Incorporate Mapping of all MSEDS elements to switches and port channels on switches

i. Incorporate IT Cabinet Rack Elevation Drawings & Details

j. Identification of any Co‐Mingling of IT Equipment and mitigation to prevent any co‐ mingling of IT equipment to provide a secure TSA network

k. Include Environmental controls and monitoring devices (i.e., temperature and humidity gauges/sensors)

The Contractor must prepare a QLR and a NAT Report at the conclusion of each network test. Set‐ up of the network in preparation for the NAT and conduct of the NAT are included under this effort. All equipment is subject to Government approval for each installation site configuration.

The Contractor must deliver NAT Reports, QLRs, and the appropriate BHS Interface Control Document in accordance with the following referenced CDRLs:

C016, Multiplex Network Acceptance Test Report

Network Milestone completion is at TSA Acceptance of NAT Report identifying the network is fully operational. TSA has 10 business days to review the NAT Report and address any concerns with the report.

3.3.6. MSEDS Integration Site Acceptance Testing (ISAT) Support (CLIN 0007) [Optional]

If exercised, the Contractor shall accommodate and support, as necessary, any and all ISAT testing activity by the BHSC, Systems Integrator, the site authority, and/or the Government or designated representative. The Contractor shall only take direction from Government representative(s) to schedule testing activities, which includes only the Government deployment project lead or manager, CO, or COR. For all testing phases the Contractor shall provide support efforts to include, but are not limited to providing technical consultation, ensuring the MSEDS will be operationally available to support testing activities and promptly notifying the Government and/or Government contracted representative in advance, if testing must be rescheduled.

The Contractor shall ensure that the MSEDS will be operationally available to support testing activities or promptly notify the Systems Integrator and Government contracted Independent Validation and Verification (IV&V) representative in advance, if testing must be rescheduled. All integration and testing issues shall be reported to the Government in the ITR. When determining resources, the Contractor shall, at minimum, plan on one (1) test effort and one (1) re‐testing effort.

C016, Multiplex Network Acceptance Test Report

3.3.7. Operator Training (CLIN 0008) [Optional]

If exercised, the Contractor shall provide operator training services that will include all labor, material, and Other Direct Costs (ODC). These tasks may include, but not be limited to the provision of training materials, course development, delivery of training at designated sites, or training evaluation activities for any MSEDS or system component under configuration management.

The Contractor shall conduct operator training classes following MSEDS integration with the network for no more than five (5) business days with up to ten (10) TSA personnel/operators in each class for each Government selected airport in accordance with a Government‐approved training program for each MSEDS.

These operators will be selected from current screener population, if possible. The Contractor shall ensure that this training is targeted to match the skill level, qualifications, and capacity of current X‐ray imaging operators and supervisors performing similar baggage inspection. The Government will witness the initial training class.

The Contractor shall provide and utilize the MSEDS Training Materials referenced in the below CDRLs when conducting training:

C017, Participant Guide C018, Classroom Presentation

3.3.8. 30‐Day Run‐in Support Service (Operational Run‐In) (CLIN 0009) [Optional]

If exercised, the Contractor must support the Government’s operational run‐in of live checked baggage for each construction phase, which will be determined by the Government or designated contracted representative upon satisfactory completion of the ISAT, or conditional acceptance of the ISAT (meaning minor issues with the BHS remain, but are not significant enough to deem the ISAT failed and must be retested). Satisfactory or conditional completion are determined by the Government approved Independent Verification and Validation (IV&V) representative. The Contractor must provide Field Data Recording System (FDRS) data in Comma Separated Value (CSV) format or Microsoft Excel as requested on a daily basis for the duration of the operational run‐in. Summary reports may be requested by the Government in addition to the FDRS data. The Equipment Summary Reports, Bag Summary Reports, and System Event Reports are used to support evaluation of a predetermined 30‐day operational run‐in period. See Section 3.12.7 for more information on FDRS data.

NOTE: This CLIN must include a 7‐day delay period wherein the 30‐day run in review is temporarily stopped and restarted within a few days.

Milestone completion at conclusion of 30‐day Operational Run‐in Period.

L012, FDRS Report

3.4. MSEDS Equipment (CLIN 0010) [Optional]

If exercised, the Contractor must provide fully functional equipment in accordance with this SOW and the most current TSA approved Performance Baseline (PBL) as documented in the TSA MCIL, that can operate in an environment that is described in the PGDS. The Contractor must ensure that all hardware, software, and documentation required for the operation and support of the MSEDS are provided as part of the supplies and services stated herein.

All equipment is subject to Government approval for each installation site configuration.

Pricing for the MSEDS Scanner CLIN (0010) includes all Labor, Materials, and other direct costs necessary to manufacture and prepare the equipment for transportation to designated sites.

Pricing for ALL peripheral Equipment CLINs (0011 – 0018) includes all Labor, Materials, Shipping, and other direct costs necessary to manufacture, packaged, and deliver the equipment to designated sites.

The Contractor shall also be responsible, exclusive of Systems Integrator activities, for all labor and support services needed to perform rigging oversight including:

Coordinating with the TSA Office of Property Management and the System Integrator in accordance with Section 2.7 as well as all Support Services as outlined in Section 3.2.

Providing oversight and technical guidance to the Systems Integrator or other entity charged with the rigging of the MSEDS or MSEDS‐related equipment

Notifying appropriate TSA personnel promptly in the event of improper equipment handling by the Systems Integrator or other entity charged with the rigging of the MSEDS or MSEDS‐related equipment

3.4.1 Medium Speed Explosive Detection System Scanner (CLIN 0010)

The Contractor shall provide fully MSEDS Equipment in accordance with this SOW, the most current TSA approved PBL as documented in the TSA Master Configuration Items List (MCIL), that has a 95% rated throughput of 674 bags/hour or greater using the throughput calculation method specified in Table3.1 of the PGDS in effect at the time the CLIN is exercised. The Contractor shall ensure that all hardware, software, and documentation required for the operation and support of the MSEDS are provided as part of the supplies and services stated herein.

3.4.1.1 The MSEDS Scanner unit consists of the component listed in the following table:

Component Name QTY

Scanner (which includes input/output conveyance) 1

Operational Test Kit 1

MSEDS Installation Manual (digital copy) CDRL 0022 1

MSEDS Operation Manual (digital copy) CDRL 0023 1

MSEDS Integration Manual (digital copy) CDRL 0024 1

Original Equipment Manufacturer (OEM) Maintenance Manual 1

3.4.1.1. Factory Acceptance Test Plan

The Contractor shall prepare and submit a Factory Acceptance Test (FAT) Plan that describes methods for testing, evaluating, and accepting the MSEDS at the Contractor's facility prior to shipment. The FAT Plan shall define the range of tests, system initialization requirements, input data, expected output, and the criteria for evaluating test results. The Contractor shall identify schedules and all test and evaluation resources required, including personnel, equipment, and facility. The Contractor shall identify all mitigation plans and procedures in the case of failed testing events.

The Contractor shall prepare and deliver the MSEDS FAT Plan in accordance with the referenced CDRL:

C004, Factory Acceptance Test Plan

3.4.1.2. Factory Acceptance Test Procedures and Reports

The Contractor shall conduct a FAT for each MSEDS in accordance with the FAT Plan and Procedures prepared by the Contractor, and approved by the Government. The Contractor shall prepare and submit FAT Procedures. The Contractor shall perform the approved FAT Procedures for each FAT under the witness of the Government, or Government Designated Representative. The Contractor shall ensure that the test procedures indicate traceable paths to the approved Contractor's VRTM.

The Contractor shall prepare a FAT Report and a Quick Look Report (QLR) at the conclusion of each test. The Contractor shall deliver the MSEDS FAT Procedures, Reports, and QLRs in accordance with the following referenced CDRLs:

C005, Factory Acceptance Test Procedures C006, Factory Acceptance Test Report

3.5. Primary Viewing Station (CLIN 0011) [Optional]

If exercised, the Contractor must provide Primary Viewing Stations (PVS) that will function with the MSEDS in accordance with this SOW and the Procurement Specification for Checked Baggage Screening Technology Medium Speed Explosives Detection Systems under CLIN 0010. The PVS in accordance with the most current TSA‐approved PBL as documented in the TSA MCIL in effect at the time the CLIN is exercised.