RFP 70T04021R7672N001 Attachment A-SOW.pdf

Checkpoint Property Screening System (CPSS)

Increment 1 – Mid-Size

Statement of Work (SOW)

Table of Contents

1. Background

2. Purpose

3. Definitions

4. CPSS Increment 1 – Mid-Size Systems and Peripheral Equipment

5. Program Management

6. Equipment Shipping

7. Warranty

8. Logistics Support Services

9. Deliverables

APPENDIX A – ACRONYM LIST

APPENDIX B – 508 REQUIREMENTS

APPENDIX C – DHS AND TSA ENTEPRISE ARCHITECTURE COMPLIANCE

APPENDIX D – INFORMATION ASSURANCE REQUIREMENTS FOR TSA

GOVERNMENT ACQUISITIONS

1. Background

1.1. The Transportation Security Administration (TSA) was created to meet the nation’s need for safety and security throughout the transportation infrastructure, including all modes of transportation in the United States and several international locations.

1.2. Based on previous Department of Homeland Security (DHS) and TSA efforts, TSA recognizes Computed Tomography (CT) screening technology as the most impactful capability currently available to address the rapidly-evolving threats at airport checkpoints.

2. Purpose

2.1. The purpose of the requirement is for the Contractor to provide TSA with Mid-Size

Checkpoint Property Screening System (CPSS) units, simulators, program management, warranties including logistics support services, configuration management services, shipping, and installation. All associated labor, materials, and travel required to meet the requirements of this Statement of Work (SOW) shall be provided by the Contractor.

3. Definitions

3.1.This section defines words and terms that are used throughout this SOW.

“Ao” – Operational Availability. The percentage of time, during operational hours, that a security equipment technology is available to perform its required mission. (Uptime/Total

Operational Time)

“Authorized Deviation” – a temporary departure from requirements and does not constitute a permanent change.

“Automated Diverter” – baggage handling equipment that is integrated with the Scanner and

Ingress/Egress Conveyor system that automatically diverts articles to the “Suspect” holding area or onto the “Clear” conveyors for passenger retrieval, based on the CPSS decision at

Level 1, and operator decision at Level 2.

o “Parallel Divestiture Stations” – allows multiple passengers to divest their belongings into bins using divestiture stations. An automated conveyor then feeds the passenger bins into the tunnel for scanning.

o “Automatic bin return system” – automatically transports empty bins from the recomposure area back to the divestiture area.

“Configuration Audit Summary Report” (CASR) – provides text and (marked-up) technical documents (e.g., specifications, engineering drawings) that identify discrepancies between the material (including software) and the requirements delineated in the applicable technical documents. Depending on the type of audit, the identified discrepancies may be attributable to the material, the technical documents, or both.

“Configuration baseline” – the Contractor’s TSA approved CPSS Qualified Product List system configuration.

“Corrective maintenance” – consists of unscheduled maintenance activities performed to repair or otherwise restore failed Transportation Security Equipment (TSE) to operational condition. These actions usually expend consumable and repair parts.

“Engineering Change Proposal” (ECP) – a request to incorporate a permanent change to the product configuration, which produces a new baseline.

“Failure Mode Identifier” (FMI) codes – a list of standardized problem codes, definitions, and priority ratings for trouble ticket generation.

“Formal Test” – any test that demonstrates equipment operational capabilities to verify machine functionality.

“Ingress/Egress Conveyor” - baggage handling equipment that maintains belt control and is integrated with the Scanner to support transporting divested accessible property through the scanner.

“Integrated Site Acceptance Test (iSAT)” – a modified SAT test that includes additional plans, procedures, and requirements due to addition of automated components (e.g.

automated diverter, parallel divestiture stations, automatic bin return system, and automated screening lane). See definition for SAT.

“Operational Time” – Period of time within a twenty-four (24) hour day that an airport is operational. Security equipment is required to be available to perform its required mission during operational hours.

“Peripheral Equipment” – All equipment associated with CPSS scanners required to operate the system, to include but not limited to, Primary Viewing Stations (PVS), Alternate Viewing

Stations (AVS), as well as any other equipment requiring asset inventory tracking, such as ingress / egress conveyors, autodiverter systems, parallel divestiture stations, automatic bin return system.

“Request for Deviation” (RFD) – a request to temporarily incorporate a known departure from product requirements.

“Request for Waiver” (RFW) – a request to incorporate a known departure from product requirements.

“Site Acceptance Test” (SAT) – a test at a designated deployment site (e.g. airport), in accordance with approved plans and procedures, to ensure the system is installed and operating properly in its intended environment prior to acceptance from the Contractor.

“Test Readiness Notification” (TRN) – a notification from the Contractor to the Government stating that the equipment specified therein will be ready for testing on the specified date.

“Uptime” – the period of time a system is available to perform its required mission during operational hours. The natural cycle of uptime occurs during operational hours.

“Value Engineering Change Proposal” (VECP) – a proposal submitted by a Contractor under the value engineering provisions of Federal Acquisition Regulation (FAR) Part 48 that, through a change in the contract, would lower the project’s life-cycle cost.

4. CPSS Increment 1 – Mid-Size Systems and Peripheral Equipment

4.1. CPSS Increment 1 – Mid-Size System

4.1.1. The CPSS Increment 1 –Mid-Size System shall consist of the following major components:

Table 1: Major Components

Component Description

Scanner Main component of the system that contains the scanning tunnel and PVS.

Primary Viewing Station (PVS) The primary workstation that provides the necessary interface tools to conduct screening.

Alternate Viewing Station (AVS) A secondary workstation that provides an equivalent display and imaging tools as the PVS.

Powered Ingress/Egress Conveyors

Powered belts integrated with the entrance and exit of the scanner to support transit of divested accessible property through the scanner.

Auto-Diverter Subsystem

Subsystem that uses input from the screening technology and/or the PVS operator to physically separate and correctly route suspected bins for additional screening and cleared items for passenger recomposure.

Bins Containers provided by the Contractor for the transport of items through the entire screening process.

Divest and Revest Roller Tables

Unpowered conveyors, consisting of a series of roller tables, that allow multiple passengers to divest belongings into divestiture station bins and facilitate the transportation of divested accessible property to the powered conveyors that feed into the tunnel for scanning.

CPSS Simulator

Simulators and workstations to train Transportation

Security Officers (TSOs) on the CPSS System with current qualified software inclusive of any approved CRs and any configuration changes that affect the operation of the CPSS System.

4.1.2. The Contractor shall deliver TSA-qualified fully functional CPSS Increment 1 –

Mid-Size systems and peripheral equipment that: a) meet the CPSS Functional

Requirements Document (FRD) Version 2.0 and b) are approved as part of the

QPL process outlined in the associated TSA QPL Window.

4.1.3. The Checkpoint Requirements and Planning Guide (CRPG) and its Appendix A shall be referenced for Checkpoint Screening Lane Design considerations and can be found at:

https://beta.sam.gov/opp/44099b735e494ef48cd27a9589c3c8ba/view.

4.1.4. No later than sixty (60) calendar days after contract award, the Contractor shall deliver and maintain a First Article Test and Evaluation (FAT&E) unit at the

Contractor’s facility that has successfully completed a Factory Acceptance Test.

This system is in addition to the specified quantities to be deployed.

4.1.4.1. The Contractor shall provide a two (2) year warranty for the FAT&E unit.

4.1.5. CPSS Mid-Size systems shall begin to be deployed and Site Acceptance

Testing/integrated Site Acceptance Testing (SAT/iSAT) shall be completed no later than sixty (60) calendar days after successful completion of FAT of the

FAT&E unit. It is the Government’s intent that the first system is operational in the field one-hundred and twenty (120) days after contract award.

4.1.5.1. The Contractor shall deploy a mimimum of twenty-two (22) CPSS Mid-

Size systems per month after the first operational unit at multiple locations as directed by TSA.

4.1.6. TSA reserves the option to purchase TSA-qualified field-tested CPSS Systems originally provided under the TSA issued Other Transaction Agreement (OTA) at a discounted price.

4.1.7. The Contractor shall ensure the final CPSS systems are configured in accordance with the configuration items and configuration management documents as seen in Section 4.7, inclusive of any approved Change Requests (CRs).

4.1.8. The Contractor shall deliver a system that provides protection to reduce the potential exposure of passengers and the TSA workforce to public health threats.

This includes, but is not limited to acrylic barriers to increase social distance and reduce direct contact between passengers and TSA employees, and ultraviolet technology to disinfect baggage tray bins against transmission of contagions.

4.1.9. All CPSS systems must meet all state and federal requirements. This includes, but is not limited to, required ancillary accessories such as seismic brackets.

These ancillary accessories are subject to the final installation location, but must be provided.

https://beta.sam.gov/opp/44099b735e494ef48cd27a9589c3c8ba/view

4.1.9.1. The Contractor shall provide systems with seismic anchoring points for installation as required based on applicable federal, state, and local codes for a deployed location (e.g. west-coast). The points (e.g. brackets) shall be outward facing for ease of installation. See section 3.3.7.2 of the FRD for additional details on requirements.

4.1.9.2. The Contractor shall provide systems with a terminal slope up to 2.5% with a nominal minimum range and as required based on applicable federal, state, and local codes for a deployed location (e.g. west-coast) and in accordance with Attachment 14, Checkpoint Sloped-Floor Study.

4.1.9.2.1. If the system provided does not meet the minimum or maximum terminal slop requirements, the Contractor shall provide corrective solution at no cost to the government.

4.1.9.3. The Contractor shall conduct routine scheduled static radiation surveys.

4.1.9.3.1. The Contractor shall ensure the emission limit meets all state and federal requirements and does not exceed the performance standard identified in 21 Code of Federal Regulations (CFR) Part 1020.40.

4.1.10. The Contractor shall ensure all delivered CPSS systems are upgradeable to all detection levels contained within the Accessible Property Screening System

(APSS) Detection Standard 6.2, Version 1, 05 October 2018, or any subsequent version of this document, at no cost to the Government.

4.1.11. The Contractor shall provide data rights that include a license to use “final images” as displayed on the operator control panel that enables TSA to identify threat items as follows:

4.1.11.1. The Government rights in production data, result data, and log files compiled during testing are determined under FAR 52.227-17 “Rights in

Data-Special Works”. All Contractor developed processes, procedures or configuration works first produced under this procurement and recorded or uploaded into or installed upon any Government system (including development, test, production, and failover environments) under this or any related or predecessor contract, is deemed to have been delivered to the

Government. All rights of the parties in these technical data deliverables other than those previously identified (production data, result data, and log files compiled during testing) shall be determined under FAR 52.227-14

“Rights in Data – General”.

4.1.11.2. FAR 52.227-1 “Authorization and Consent” shall apply only to modifications to proprietary hardware or software as directed and produced under this contract. FAR 52.227-3 “Patent Indemnity” shall apply to all other proprietary and/or pre-existing software and hardware, Commercial

Off-the-Shelf (COTS) or otherwise utilized or delivered by Contractor in fulfillment of its obligation under this contract. FAR 52.227-1 applies to any development effort to the commercial item. FAR 52.227-3 applies to the commercial item.

4.1.11.3. The Contractor shall make all data described in the FRD available to TSA as defined in CPSS FRD Version 2.0.

4.1.11.4. The Contractor shall provide images in DICOS v02A Toolkit compliant format, as outlined in the CPSS FRD Version 2.0.

4.1.12. The Contractor shall provide the Contracting Officer’s Representative (COR) with an electronic copy of all training material, to include a training manual, within ten (10) calendar days after award, and additional updates as needed.

4.1.13. The Contractor shall provide the COR with electronic copies of the user manual, maintenance manual, installation manual, interface control document (ICD), and

Parts List within twenty (20) calendar days after award, and additional updates as needed.

4.2. Bins

4.2.1. The Contractor shall provide the following per system: one hundred forty (140)

TSA approved bins, four (4) bin carts and one (1) rerun bin cart in compliance with TSA approved configuration as per The Checkpoint Requirements and

Planning Guide (CRPG).

4.2.2. The bin cart shall have one (1) bin permanently attached to the bin cart so any stacked bins do not slide off the cart. Bin carts shall include a safety break to keep the cart in place when not in use.

4.2.3. The rerun bin cart is to move bins that contain property from the secondary conveyor or search station to the entrance of the CPSS scanner to conduct a rescan.

4.3. Divest and Revest Roller Tables

4.3.1. The Contractor shall provide divest and revest roller tables that are level with the CPSS system conveyers, made up of modular sections 3-4 feet long or as described in The Checkpoint Requirements and Planning Guide (CRPG).

4.3.2. Roller tables shall have lips or edges that prevent items/bins from falling off either side of the roller table.

4.4. CPSS Simulator

4.4.1. The Contractor shall provide two (2) simulators, workstations and servers as part of the CPSS system to support the total quantity deployed systems per airport/lab location.

4.4.2. The Contractor shall provide TSA with two (2) simulators and workstations to train Transportation Security Officers (TSOs) on the CPSS system.

4.4.3. The Contractor shall ship and install a minimum of two (2) simulators and workstations as directed by the COR, no later than ten (10) calendar days prior to SAT.

4.4.4. The Contractor shall provide all simulators and workstations to TSA with the current qualified system software inclusive of any approved CRs and any configuration changes that affect the operation of the CPSS system (Graphic

User Interface, keyboard or buttonology, etc.).

4.4.4.1. The Contractor shall ensure all simulators and workstations directly reflect the to-be deployed system at all times.

4.4.4.2. The Contractor shall upgrade all simulators and workstations to the latest Accessible Property Screening System 6.2 and any subsequent new versions and inclusive of any data rights provided during the development of these algorithms at no cost to the government. This upgrade to the simulators shall occur when the Contractor upgrades the

CPSS Systems in accordance with TSA requirements.

4.4.5. The Contractor shall provide TSA with CPSS simulator software in CD media format that can be loaded on existing training computers (software only, not contractor hardware) for personnel training purposes on operating system as defined by the OEM.

4.4.6. The Contractor shall ensure all simulator software versions match the current versions on the CPSS fielded systems and are in accordance with APSS

Detection Standard 6.2, Version 1.0, 05 October 2018 and any subsequent new versions of this document.

4.4.7. The Contractor shall provide simulator software inclusive of any approved change request(s) CRs, software updates, and any configuration changes that affect the operation of the CPSS system (Graphic User Interface, buttonology, etc.) during the warranty period. The ability to develop and maintain multiple, random simulation sessions must reside on the simulator platform.

4.4.8. The Contractor shall notify TSA at least thirty (30) calendar days in advance if there are any new hardware requirements as a result of simulator software updates.

4.4.9. The Contractor shall provide simulator software with a Graphical User Interface

(GUI) that has the same look, feel, and functionality as the actual CT machine

(coloration, button-ology, etc.).

4.4.10. The Contractor shall provide simulator software with the capability to connect to the Security Technology Infrastructure Program (STIP) and to create, maintain, update, archive, and retrieve user profiles and threat images, using a standard file format, either through a network solution or by manual means. All images are considered Sensitive Security Information (SSI) and the storage/protection of those images must meet TSA/DHS standards for safeguarding SSI.

4.4.11. The Contractor shall provide simulator software with images exportable in

DICOS v02A Toolkit compliant format.

4.4.12. The simulator software shall have the ability to remove system generated bounding boxes from threat items for training purposes.

4.4.13. The Contractor shall provide simulator software that has the same user-authentication means as logging in to the actual CT system.

4.4.14. The Contractor shall provide TSA the simulator software as a free-software license, inclusive of all data rights, for redistribution and training purposes.

4.4.15. The Contractor shall provide simulator software (in the form of both a Compact

Disc and Universal Serial Bus flash drive for each delivery) at each airport where a CT system is installed, as directed by the COR, no less than ten (10) calendar days prior to SAT.

4.4.16. The Contractor shall provide simulator software (in the form of both a Compact

Disc and Universal Serial Bus flash drive for each delivery) at each of the following locations: TSA Systems Integration Facility (TSIF), TSA HQ, TSA

Academy, and Transportation Security Laboratory (TSL), as required by TSA no later than twenty (20) calendar days after contract award.

4.5. Test Readiness Notification (TRN)

4.5.1. The Contractor shall submit a TRN via email to the COR at least ten (10) calendar days prior to the start of each formal test.

4.5.1.1. A formal test may include, but is not limited to, a Factory Acceptance

Test (FAT) a Site Acceptance Test (SAT), and an integrated SAT

(iSAT).

4.5.2. The Contractor’s TRN shall, at a minimum, include the following:

a. Contract number;

b. Serial number of the unit(s) to be tested;

c. Type of test to be conducted;

d. Open test anomalies observed to date;

e. Open ECPs, RFDs, or RFW;

f. Test procedure status (version—date);

g. System configuration (i.e., stand-alone, fully integrated, exit-integrated) and part numbers with revisions of critical components as identified in the

Master Configuration Item List (MCIL);

h. Software version;

i. Affirmation that the system will be ready for testing on the specified date;

and

j. Comments.

4.6. Acceptance Testing (FAT/SAT/iSAT)

4.6.1. FAT Plan, Procedures, and Execution

4.6.1.1. The Contractor shall submit a First Article Test and a Factory

Acceptance Test Plan as coordinated between the OEM and the TSA

Assessment Test and System Acceptance (ATSA) team to the COR within twenty (20) days after contract award.

4.6.1.1.1. The Contractor shall ensure its FAT plan describes the methods for testing, evaluating, and accepting the CPSS systems at the

Contractor’s facility prior to shipment, as well as defining the range of tests, system initialization requirements, input data, expected output, and the criteria for evaluating test results.

4.6.1.1.2. Within the FAT plan, the Contractor shall provide a schedule for all scheduled FATs and all test and evaluation resources required, including personnel, equipment, and facilities.

4.6.1.1.3. The COR must approve the Contractor’s FAT plan prior to any

FAT taking place.

4.6.1.2. TSA and its designated test agent will observe the scheduled FAT at the

Contractor’s facility upon the Contractor’s submission of the TRN to

TSA.

4.6.1.3. The TSA Acceptance Test Team will review and accept the Contractor’s

FAT procedures. The TSA test lead may add additional tests to the procedure as deemed necessary.

4.6.2. SAT/iSAT Plan, Procedures, and Execution

4.6.2.1. The Contractor shall provide support, as needed, for TSA’s SAT/iSAT plan and procedures development. Once these procedures are developed, they will be provided to the Contractor. The Contractor shall review and provide their final recommendations to the COR within twenty (20) calendar days.

4.6.2.2. Upon final review, additional tests may be added by the TSA

Acceptance Test Team as required to adequately determine if the system is operationally suitable and effective.

4.6.2.3. TSA or its designated test agent will perform each SAT/iSAT at every installation site in accordance with TSA’s approved SAT/iSAT plan and procedures and confirm the CPSS system is ready for operational use.

All equipment is subject to Government approval for each installation site configuration. The SAT/iSAT is typically performed one (1) day after the completion of system installation.

4.6.2.3.1. The system shall be installed and operational within two days of taking the intended checkpoint location down for installation.

4.6.2.3.2. The Contractor shall provide direct on-site support during these tests to answer any questions, perform any required system maintenance, obtain system data, and assist with system testing.

4.6.2.3.3. TSA will provide notification of SAT/iSAT to the Contractor at least ten (10) calendar days prior to execution of SAT/iSAT.

4.7. Configuration Management (CM)

4.7.1. The Contractor shall maintain CPSS systems under strict CM.

4.7.1.1. The Contractor shall uniquely identify and map back to the Contractor’s configuration baseline all system Configuration Items (CI), hardware, software and firmware CIs.

4.7.2. The Contractor shall not alter the system in any way without the Government’s express written approval.

4.7.3. The Contractor shall establish, implement, and maintain a CM Plan based on the

SOW requirements. The CM Plan also includes all design documentation used to support the production baseline configuration. Additional guidance may be found in TSA Configuration Management Guidance, Version 2.0, dated 06/30/2015.

4.7.3.1. The Contractor shall maintain its TSA-approved Configuration

Management Plan (CMP) for the life of this contract, should the

Contractor already have a TSA- approved CMP.

4.7.3.2. If the Contractor does not already have a TSA-approved CMP, the

Contractor shall prepare and deliver its CMP in accordance with Attachment 1, Configuration Management Plan to the COR within thirty (30) calendar days of contract award

4.7.3.3. The Contractor shall provide an organizational structure with configuration identification and control methods, configuration audits, and Configuration Status Accounting (CSA) procedures for system hardware, software, firmware and deliverables in CMP. The CM requirements are applicable to all deliverables under this contract.

4.7.4. Configuration Baselines

4.7.4.1. The Contractor shall establish and maintain the configuration baseline for each TSE configuration and establish and maintain the required documentation to support each configuration, referred to as the Product

Baseline (PBL).

4.7.5. Configuration Identification

4.7.5.1. The Contractor's PBL shall retain all documentation for identification, control, and status accounting of any CI throughout the program life cycle.

4.7.5.1.1. The Contractor shall ensure the CI identification is available in a

MCIL and uniquely identify all system CIs and top level hardware and software.

4.7.5.2. The Contractor shall prepare and deliver one (1) MCIL per TSE to the

COR ten (10) calendar days after contract award in accordance with

Attachment 2, Master Configuration Item List.

4.7.5.3. The Contractor shall update MCILs quarterly, in accordance with

Attachment 2, Master Configuration Item List.

4.7.6. Configuration Control

4.7.6.1. The Contractor shall apply configuration change management measures to each baseline CI and its configuration documentation.

4.7.6.2. The Contractor’s configuration change management system shall provide effective means, as applicable, for proposing changes to CIs and ensuring implementation of the approved change.

4.7.6.3. The Contractor shall maintain configuration change management of hardware, software, firmware, and developmental/commercial and training documentation.

4.7.6.4. The Contractor shall maintain configuration change management of hardware to the Lowest Replaceable Unit level and software to the version level.

4.7.6.5. Changes represent opportunities for improvement or correction of deficiencies. TSA uniquely identifies and documents desired changes in Request for Changes in the form of ECPs, RFDs, and RFWs. TSA enters, tracks, controls, and documents all change requests.

4.7.6.5.1. The Contractor shall establish and maintain a system for tracking, controlling, and submitting all changes to TSA. The Contractor is encouraged to voluntarily develop, prepare, and submit VECPs.

4.7.6.5.1.1. The Contractor shall share in any net maintenance cost savings realized from accepted VECPs in accordance with the incentive sharing rates in paragraph (f) of FAR 52.248-1

“Value Engineering”.

4.7.6.5.1.2. The Contractor shall prepare the VECP to include a clear description and related schedule on how the Contractor plans on incorporating the VECP into fielded TSE units without adversely affecting operational availability of the CPSS.

4.7.6.6. The Contractor shall submit ECPs to the COR, in accordance with

Attachment 3, Engineering Change Proposal Form.

4.7.6.7. The Contractor shall submit RFDs to the COR, in accordance with

Attachment 4, Request for Deviation Form.

4.7.6.7.1. RFDs must state actions to be taken at the end of the temporary deviation (e.g. restoration to original configuration).

4.7.6.8. The Contractor shall submit RFWs to the COR in accordance with

Attachment 5, Request for Deviation/Waiver.

4.7.6.8.1. Authorized waivers are for specific quantities of product and do not constitute a change to the baseline configuration or its documentation.

4.7.6.8.2. All CRs for TSA mandated fixes, including but not limited to resolutions from TSIF FRD Developmental Testing and Operational

Testing and Evaluation shall be corrected prior to FAT&E.

4.7.6.8.2.1. Qualification Testing (QT) validates FRD requirements against the system configuration at TSIF. Following QT and regression testing of mandated fixes, FAT&E is conducted to establish a product baseline.

4.7.6.8.3. Any CRs required to meet functional requirements in place at the time of contract award shall be performed by the Contractor at no additional cost to the Government.

4.7.6.9. The Contractor shall provide all configuration management changes for TSE via email to CTOCM@tsa.dhs.gov.

4.7.7. Configuration Status Accounting (CSA)

4.7.7.1. The Contractor shall maintain a CSA information system to assure accurate identification of each CI.

4.7.7.2. The Contractor shall ensure that the CSA information is provided to the Government upon request.

4.7.7.3. The Contractor shall provide CSA information as a monthly

Configuration Status Accounting Report (CSAR).

4.7.7.3.1. The Contractor shall prepare and deliver the CSAR to the COR thirty (30) calendar days after delivery of the first system and monthly thereafter, in accordance with Attachment 6, Configuration

Status Accounting Report.

4.7.7.3.2. The Contractor shall ensure the CSAR identifies all deviations from the MCIL for each unit (i.e. for all serial numbers).

4.7.7.4. The Contractor shall describe its CSA system in the Contractor’s

CMP.

4.7.8. Configuration Audits

4.7.8.1. The Contractor shall support PBL audits and shall perform internal

Contractor configuration audits.

4.7.8.2. The Contractor shall prepare a Configuration Audit Plan (CAP) in accordance with Attachment 7, Configuration Audit Plan, that describes procedures for conducting the audit, including Functional

Configuration Audit and Physical Configuration Audit.

4.7.8.2.1. The Contractor may invite subcontractors, vendors, and suppliers to participate in the configuration audits when proposed and approved by TSA via the CAP.

mailto:CTOCM@tsa.dhs.gov

4.7.8.2.2. The Contractor shall deliver the CAP thirty (30) calendar days before a configuration audit.

4.7.9. Configuration Audit Summary Report (CASR)

4.7.9.1. The Contractor shall prepare a CASR documenting the results of each audit and the resolution for each finding.

4.7.9.2. The Contractor shall submit a CASR to the COR thirty (30) calendar days after contract award and thirty (30) calendar days after each occurring audit in accordance with Attachment 8, Configuration Audit

Summary Report.

5. Program Management

5.1. The Contractor shall prepare the Program Management Plan (PMP) to include a risk management component that identifies cost, schedule, and technical risks, a plan for performance of preventative maintenance, warranty implementation, and a Parts

Obsolescence Report that includes identification of obsolete parts, problem resolution, and a recommended approach for mitigating risks associated with obsolete parts over the life of the systems.

5.1.1. The Contractor shall deliver the PMP to the COR twenty (20) calendar days after award.

5.2. Post-Award Conference

5.2.1. The Government will conduct a post-award conference at the Contractor’s facility, TSA Headquarters, or virtually as specified by the Government within thirty (30) calendar days after contract award at a date proposed by the

Contractor and approved by the COR.

5.2.2. TSA will designate Government conference attendees and will identify any unique conference support requirements.

5.2.3. The Contractor shall prepare and deliver the minutes for the conference in accordance with Section 5.3.

5.3. Program Meetings and Meeting Documentation

5.3.1. The Contractor shall prepare and submit meeting agenda and presentation materials to the COR at least two (2) calendar days in advance of any meeting.

5.3.2. The Contractor shall record formal meeting minutes during all meetings to include details of all discussion points and all identified action items. The meeting minutes shall also include a summary of action items and all presentation materials from the meeting.

5.3.2.1. The Contractor shall deliver formal written minutes to the COR within five (5) calendar days after the meeting.

5.3.3. The Contractor shall schedule, conduct and administratively support quarterly

Program Management Reviews (PMR) at the Contractor’s site, TSA

Headquarters, or virtually as specified by the Government. Typically, PMRs will alternate between the Contractor’s site and TSA Headquarters.

5.3.3.1. The Government reserves the right to replace a formal quarterly review with a less formal update to be completed via teleconference and to increase or decrease the frequency of quarterly reviews as required.

5.3.3.2. PMRs shall include, at a minimum, a review and status of the following:

Contractor’s organizational status (i.e., changes, issues, etc.);

Major program accomplishments as defined by the Contractor during reporting quarter;

Work to be accomplished in the next quarter;

Cost, schedule, and performance (technical) aspects of the contract;

Deliverable status

Technical and implementation problems/issues;

Risk identification, assessment, impact, priority, mitigation plans and status;

Training related issues and status;

ECP, RFD, and RFW status;

Subcontractor’s technical progress on all assigned tasks;

RMA performance of fielded systems;

Status of previous PMR action items;

New PMR action items; and

Date for next PMR.

5.3.4. The Contractor shall provide Program Status Reports (PSR) monthly to the COR.

A PSR is not required the month the PMR occurs.

5.3.4.1. The Contractor shall ensure the PSRs address problems/risks in the

Contractor’s functional areas as well as cost, schedule, technical progress, and status of deliverables.

6. Equipment Shipping

6.1 The Contractor shall provide a CPSS Specification Sheet in accordance with Attachment

13, Checkpoint Property Screening System Specification Sheet no later than twenty (20) calendar days after award, that provides guidance necessary to enable TSA to execute all site preparation requirements in advance of deployment of CPSS systems.

6.1.1 The guide shall include the following system specifications and limitations at a minimum: system height, weight, electrical requirements, temperature requirements, load requirements, as well as equipment handling.

6.2 The Contractor shall ship the CPSS systems to specified airports (or designated airport staging sites), Systems Integrator’s facilities (local riggers’ warehouse), or additional

TSA laboratories.

6.2.1 The COR will provide the Contractor with specific delivery information no later than fifteen (15) calendar days prior to the required delivery date.

6.2.1.1 TSA’s specific delivery information will include quantities, specific delivery locations, delivery dates for each system and all necessary points of contact (POC) to complete delivery.

6.2.2 The System Integrator will handle the site preparation, shipping from the Riggers

Staging Facility to the airport (as needed), rigging, and coordination with OEMs.

6.2.2.1 The Contractor shall coordinate with the Systems Integrator for exact shipping information (i.e. needs for loading dock, fork lift, dolly cart, and times of delivery).

6.3 The Contractor shall provide storage for each CPSS system at no additional cost to the

Government for up to six (6) months after FAT to accommodate deployment.

6.4 The Contractor shall provide the COR with an electronic copy of shipment and storage instructions, to include detailed instructions on the shipment and storage procedures/process and any special shipping and storage requirements for delivery and installation, within twenty (20) calendar days after award, and additional updates as needed.

7. Warranty

7.1. The Contractor shall provide a two (2) year warranty with each CPSS system, commencing at SAT approval, or commencing at iSAT approval if iSAT is required.

7.1.1. TSA reserves the right to exercise optional years of warranties, up to a total of an additional eight (8) years.

7.1.1.1. The Contractor shall maintain CPSS system warranty period dates for all deployed systems in accordance with Attachment 9, Transportation Security

Equipment (TSE) Database.

7.1.2. The spreadsheet shall be submitted to the COR no later than three (3) days after

SAT of the first system and updated monthly thereafter.

7.1.3. Warranty does not include catastrophic response, special coverage or support associated with holiday and national security special events, not limited to, presidential inaugurations, major international summits held in the United States, major sporting events, or presidential nominating.

7.1.4. Warranty period shall include hardware or software upgrades to support new algorithms.

7.1.5. The Contractor shall provide documentation to TSA, no later than sixty (60) calendar days prior to the cessation of warranty services and as part of the TSE

Database, to confirm that there is an agreement in place with the third-party service provider(s) to provide any OEM-certified repair parts, consumables, tools and test equipment, technical documentation, technician training and certification, and labor as required to requesting Maintenance Service Providers to enable effective and affordable maintenance services for CPSS systems with the third-party service provider(s).

7.1.6. The Contractor shall provide a detailed list of hardware and software to the COR including the companies (with country of origin locations) who assembled and developed each part as part of the MCIL.

8. Logistics Support Services

8.1.The Contractor shall provide logistics support services (maintenance and repair) for in-warranty TSE and peripheral equipment (to include bins) necessary to meet the logistics support service level requirements. Logistics support service shall include the following:

8.1.1. Preventive maintenance in accordance with the OEM maintenance manuals and state and federal environmental and safety regulations.

8.1.2. The Contractor shall repair components and bearing assemblies associated with the required rotation of an X-ray disk in the gantry area on-site.

8.1.3. The Contractor shall include repair parts, training, and tools and test equipment with all labor for TSE preventive maintenance, corrective maintenance and associated logistics support resources.

8.1.3.1. All equipment maintenance shall be conducted by Original Equipment

Manufacturer (OEM) certified technicians using OEM MCIL repair parts.

8.1.3.2. The Contractor shall be responsible for providing trained and certified

Field Service Technicians (FST) who have completed training by the OEM on the fundamentals of safety, functional operation, maintenance and repair of specific CPSS TSE and associated peripheral equipment.

8.1.3.3. The Contractor shall establish a robust supply chain management process that includes the appropriate levels of OEM MCIL repair parts, distribution procedures, and shipping modes to support the Service Level Agreement (SLA) requirements as defined in Paragraph 8.3.2 of this SOW.

8.1.3.4. The Contractor shall inform the COR when refurbished parts are initiated into the Contractor’s supply chain for corrective maintenance repairs.

8.1.3.5. The Contractor shall ensure that parts obsolescence during the contract period of performance does not affect the Contractor’s ability to meet logistics support service level requirements.

8.1.3.6. The Contractor is responsible for the storage of all spare parts, consumables, hardware and software necessary to fulfill the requirements of this contract.

8.1.4. The Contractor’s price for logistics support shall include shipment and all associated transportation costs including local logistics transportation to the unit with repair part shipment from the Contractor’s part location to the system location.

8.1.5. The Contractor shall ensure documentation of all maintenance actions (including preventive, corrective, and excepted) is in the TSE Maintenance Database.

8.1.6. The Contractor shall recommend adjustments to preventive maintenance schedules, with supporting rationale, that have the potential to improve TSE reliability or reduce costs without degrading TSE reliability.

8.1.7. The Contractor shall reschedule preventive maintenance on impacted machines during the same month in the event a scheduled maintenance activity cannot be completed due to factors outside of the Contractor’s control, or the performance of corrective maintenance prevents the Contractor from completing preventive maintenance.

8.1.7.1. It is at the Government’s discretion whether relief is granted or not. The

Contractor shall complete the preventive maintenance action within forty-eight

(48) hours once TSA provides the Contractor with a disapproval notice.

8.2. Parts Obsolescence Management Program

8.2.1. The Contractor shall establish and implement a Parts Obsolescence Management

Program.

8.2.2. The Contractor shall be responsible for the identification, resolution, and implementation for all Diminishing Manufacturing Sources (DMS), obsolescence, and sustainment issues associated with the repair of TSE.

8.2.3. The Contractor shall document procedures for identifying and controlling DMS and obsolescent technologies in a Parts Obsolescence Management Plan as part of the PMP.

8.2.3.1. The Contractor shall make changes it considers necessary to ensure the continued repair of the TSE in accordance with the CM procedures (RFD, RFW, and ECP).

8.3. Logistics Support Service Level Requirements

8.3.1. The Operational Availability (Ao) of Transportation Security Equipment (TSE) is critical to TSA. Performance disincentives shall be enforced to ensure the

Contractor meets the Service Level Agreement (SLA) Ao metrics set forth in

Paragraph 8.3.2 The Contractor shall provide the calculations and raw data on a monthly basis to TSA. TSA will count any failure inherent to the CPSS system that is a component of the CPSS system and maintained by the CPSS OEM toward Ao. The Ao metrics will be calculated as applicable in accordance with

Attachment 10, TSE Metrics Terms and Definitions & RMA Metrics utilizing

Airport Operational hours.

8.3.1.1. The Government will measure overall Contractor performance using Ao to evaluate the availability of TSE in relation to all relevant critical failures and all relevant non-critical failures.

8.3.1.2. The period of time TSE is available to perform its required mission during the operational hours of a facility is as described in Attachment 12 Airport

Operating Hours, Airport Listing.

8.3.1.3. The Government will measure overall Contractor performance using

Operational Availability (Ao). Ao shall be measured by ‘airport-equipment type’ monthly, at the airport level and any applicable disincentives shall be included in that month’s invoice in accordance with Section 8.4, Disincentives. The

Contractor shall provide sustainment services for fielded TSE to meet the Ao requirement in section 8.3.2.

8.3.2. For systems under warranty, the Contractor shall provide logistics support services for fielded TSE and network systems (servers, software and hardware components) to meet Operational Availability Service Level Agreement (SLA) requirements as follows:

Values Operational Availability SLA Required Ao

During Airport Operating Hours

Ao for all CPSS at each airport, measured monthly

SLA1 98%

Table 2: Ao Requirements

8.3.3. For systems not under warranty, software upgrades can be performed if approved through the CM change request process as described in section 4.7 Configuration

Management (CM) of the SOW.

8.3.4. The Contractor shall only include installed systems that have passed SAT in its

Ao calculations.

8.3.5. The Service Level Agreement requirements specified in Paragraph 8.3.2 of this

SOW are Contract requirements. The Contractor shall calculate Ao for CPSS and airport level on a monthly basis and send to the COR no later than five (5) calendar days after the end of each month and any applicable disincentives shall be included in that month’s invoice in accordance with Section 8.4. This calculation will be used as the basis for Warranty Services invoicing.

8.4.Disincentives

8.4.1. The Contractor shall develop a monthly invoice which separately identifies, per technology and model, the number of systems sustained for the given invoice period, the number of days each system was sustained per invoice period, the fixed daily unit price being applied, and any applicable disincentives.

8.4.1.1. Backup data shall be provided in an excel spreadsheet to allow for validation of invoice.

8.4.2. Operational Availability (Ao) Disincentive. The following shows the amount (in percentage terms) of the downward adjustment of the CLIN X0001 unit price if the contractor is not able to meet the threshold set forth in 8.3.2 of this SOW.

As Calculated in Attachment 10

CPSS (by Airport) SLA Disincentive

Ao for all CPSS at each airport, monthly 98.0% or higher

-10% for each CPSS by airport

As an example, if an airport has two (2) CPSS at an airport, then the Ao for that airport’s CPSS are derived from combining all CPSS performance for that month.

For example, in a 100-hour reporting period, if airport ABC has CPSS-A and the monthly performance respectively was 97.0% (with 97 hours of uptime and 3 hours of downtime) and CPSS-B with 98.9% (with 98.9 hours of uptime and 1.1 hours of downtime), then airport ABC-CPSS Ao equals 97.95% [(97 hours + 98.9 hours) /

(100 hours + 100 hours)]. Since the total CPSS performance at that airport is less than the threshold of 98.0%, the Ao disincentive is applied to both units.

8.4.3. Preventive Maintenance Disincentive. For any CPSS for which the Preventive

Maintenance (PM) is not performed within the requirements of 8.5.5.2, Level II, the

Contractor shall decrement the monthly invoice as follows. Disincentives for TSE with monthly PM requirements shall only apply the disincentive to the current month.

Level II Preventive Maintenance

Measurement SLA Disincentive

100% Completion Within timeframes specified in 8.5.5.2

-10% for each CPSS

PM missed

The PM disincentive is additive to the Ao disincentives explained above. For example, if three (3) CPSS at an airport with a total of ten (10) CPSS did not receive a PM within the month of December per the guidelines specified in 8.5.5.2, then those three (3) units will have a 10% reduction applied to the daily rate for that month. If the Ao SLA was also not met at this airport in the same month of

December, then the Ao penalty disincentive is applied to all ten (10) CPSS and then the PM penalty is applied to the three (3) CPSS that missed PMs.

8.5. Preventive Maintenance

8.5.1. The Government considers tests required at scheduled intervals to be preventive

8.5.2. The Contractor shall coordinate all preventive maintenance scheduling with local

TSA staff as appropriate.

8.5.3. The Contractor shall not perform preventive maintenance during the calendar month in which a unit is installed.

8.5.4. The Contractor shall request COR approval to waive the requirements for performing monthly preventive maintenance in the month when TSA decommissions a CPSS system.

8.5.5. The two (2) levels of preventive maintenance are as follows:

8.5.5.1. Level I – TSA primarily performs preventive maintenance every shift on a daily (one (1) to three (3) times) and weekly basis. TSA performs Level I without the need to open the CPSS system.

8.5.5.2. Level II – the Contractor primarily performs preventive maintenance monthly, quarterly, and/or annually, as defined in OEM maintenance manual.

These activities are included under this logistics support SLA.

8.5.5.2.1. For CPSS requiring monthly PM, the Contractor shall ensure that at least one PM is performed within each calendar month, regardless of number of days in that month. If the OEM CPSS maintenance manual requires Quarterly PMs then they shall have a maximum of 91 calendar days between PMs, and if OEM CPSS maintenance manual requires Semi-

Annual PMs then they shall have a maximum of 182 calendar days between PMs.

8.5.5.2.2. If the Contractor is denied access to TSE to perform PM, then the

COR shall be notified at that time and provided with airport code, model

TSE, serial number, and local TSA POC that denied access.

8.5.5.2.3. Disincentives resulting from Level II PMs not being completed on time, regardless of required periodicity, shall be applied to invoices in accordance with Section 8.4, Disincentives. The Government will determine if disincentives will be applied to TSE that the Contractor reported could not be accessed due to Government restrictions.

Disincentives for these units will be applied if the Contractor delays in notifying the Government.

8.5.5.2.4. In providing Level II preventive maintenance, the Contractor shall comply with the following:

8.5.5.2.4.1. Coordinate all Level II preventive maintenance scheduling with local TSA staff.

8.5.5.2.4.2. Provide the next month’s preventive maintenance

notifications to each location’s POC no later than seven (7) calendar days prior to the end of the current month.

8.5.5.2.4.2.1. The Contractor shall ensure notifications specify airport code, airport name, manufacturer, model, serial number

(SN), barcode, preventive maintenance due date, and the week preventive maintenance is scheduled to be performed.

8.5.5.2.4.3. Send a summary level file (airport code, airport name, manufacturer, model, SN, barcode, preventive maintenance due date, and the intended week for preventive maintenance) of all preventive maintenance actions scheduled for the month to the COR on the first day of that month.

8.5.5.2.4.3.1. Make every effort to schedule preventive

maintenance actions during non-operational hours or non-peak operational hours with approval of local TSA officials.

8.5.5.2.4.4. The Contractor shall schedule preventive maintenance actions during non-peak operational hours or during hours that both the Contractor and local TSA officials agree upon. If local TSA officials have approved preventive maintenance actions during times other than non-peak hours, then the Contractor shall submit a list to the

COR that identifies the location and the TSA official(s).

8.5.5.2.4.5. The Contractor shall coordinate with local TSA staff the week prior to the scheduled week.

8.5.5.2.4.6. The Contractor shall notify local TSA staff if the scheduled week slips and shall coordinate a new week within the required periodicity.

8.5.5.2.4.7. The Contractor shall provide all required consumables

(cleaning supplies, filters, etc.).

8.5.5.2.4.7.1. The Contractor is responsible for the storage of all spare parts, consumables, hardware and software necessary to fulfill the requirements of this contract.

8.5.5.2.5. The Contractor may contact local TSA to conduct the preventive maintenance on an earlier date than scheduled; however, if the earlier date is not convenient for local TSA this shall not be reflected as a lack of access to the facility and the Contractor shall adhere to the original schedule to perform the preventive maintenance.

8.5.5.2.6. The Contractor…