Attachment B- CPSS Base-size SOW.pdf

Checkpoint Property Screening System (CPSS) Increment 1 – Base

Statement of Work (SOW)

Table of Contents

1. Background

2. Purpose

3. Definitions

4. CPSS Increment 1 – Base 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

APPENDIX D – Cybersecurity Policy for TSA Government Acquisitions

APPENDIX E – CYBER-SUPPLY CHAIN RISK MANAGEMENT (C-SCRM)

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 Base Checkpoint Property Screening System (CPSS) units, simulators, program management, warranties including logistics support services, configuration management services, engineering support 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.

“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 or degraded 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.

“Final Image” - the displayed images with regions of interest/annotation of an item saved at the Primary Viewing Station (PVS) by Level 2 operator when the operator “suspects” a threat.

“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.

“Manual Diverter” – Baggage handling equipment that is integrated with the Scanner and Ingress/Egress Conveyor system to manually divert 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.

“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 time.

“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.

“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 – Base Systems and Peripheral Equipment

4.1. CPSS Increment 1 – Base System

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

Table 1: Major Components

Component Description

Scanner Main component of the system that contains the CT 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.

Divest and Revest Roller Tables – 12 feet of divest and revest roller tables, broken into modular sections of 4 feet or less, with the option to procure and add more, as needed

Unpowered conveyors, consisting of a series of rollers, that facilitate the transportation of divested accessible property to the powered ingress/egress conveyors and through the scanner.

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

Buffers / Decision Points – zero (0) per system with option to procure and add more, as needed

Buffer modular after the scanner prior to the manual-diverter subsystem that allow for additional decision time prior to directing scanned baggage to either secondary screening or revest line.

Manual-Diverter Subsystem – one (1) per system

Subsystem that allows the PVS operator to physically separate and correctly route suspected bins for additional screening and cleared items for passenger recomposure.

CPSS Simulator – one (1) per system with the option to procure more, as needed

Simulators 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.

Bins – one-hundred-and forty (140) per system with the option to procure more, as needed

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

Component Description Bin Carts – four (4) per system with option to procure more, as needed

Wheeled carts to stack and transport a large number of bins.

Rerun Cart – one (1) per system with option to procure more, as needed

A bin cart used to move bins that contain property from the secondary conveyor or search station to the entrance of the CPSS scanner to conduct a rescan.

Search Bench – one (1) per system with option to procure more, as needed

A standalone table for secondary searches of an alarmed bag where AVS is located.

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

Base 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: Now on TSA.GOV:

https://www.tsa.gov/sites/default/files/checkpoint-requirements-and-planning-guide.pdf https://www.tsa.gov/sites/default/files/checkpoint-requirements-and-planning-guide_appendix-a.docx

4.1.4. No later than sixty (60) calendar days after contract award, the Contractor shall produce and maintain a First Article Test and Evaluation (FAT&E) unit at the Contractor’s facility that has successfully completed FAT&E and a Factory Acceptance Test (FAT). This system is in addition to the specified quantities to be deployed.

4.1.4.1. The FAT&E unit shall be the first unit produced by the Contractor and the last deliverable to TSA under the awarded contract. The unit shall be used by the Contractor to test and evaluate all proposed changes to the equipment prior to submitting change documentation to the Configuration Manager.

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

4.1.5. The first CPSS Base system shall be deployed and Site Acceptance Testing

(SAT) shall be completed no later than sixty (60) calendar days after successful completion of FAT&E and FAT of the FAT&E unit. It is the Government’s intent that the first system is operational in the field no later than one-hundred and twenty (120) days after contract award.

4.1.5.1. The Contractor will be provided specific deployment information by the COR after contract award prior to the required delivery date. Specific deployment information will include quantities, specific delivery locations, delivery dates for each system, and all necessary points of contact (POC) to complete deployment.

After the first CPSS Base-size system is deployed, the Contractor must be capable of deploying a minimum of thirty-three (33) CPSS Base-size systems per month at multiple locations as directed by TSA, inclusive of the necessary FAT and SAT procedures. The Contractor may be required to provide storage at no cost to the Government for each system for up to 90 days after FAT to accommodate deployment. The Government will use reasonable efforts to enable the Contractor to deliver and SAT systems no more than two (2) weeks after FAT.

4.1.5.2. The CPSS system shall be installed and operational within one (1) day of taking the intended checkpoint location down for installation.

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.12, inclusive of any approved Change Requests (CRs).

4.1.8. Shielding - The Contractor shall provide glass or clear acrylic shielding with speaker grills and powered hands-free speaker and microphones for the divest lane and search bench of the Base CPSS.

4.1.8.1. The Contractor shall provide glass or clear acrylic shielding with a minimum of ¼ inch thickness at the divest lane and search benches to help prevent both passengers and TSOs from being exposed to harmful viruses and bacteria.

4.1.8.2. The Contractor shall provide cleaning and maintenance instructions that will preserve the integrity of the glass or clear acrylic and not cause scratching or discoloration.

4.1.8.3. Shielding height shall reach 78 inches from floor to ensure clearance in airports with 8 foot (96 inch) ceilings to maintain compliance with fire codes, proper operation of sprinkler systems, air flow, etc. and to ensure sufficient shielding for standing TSOs and public.

4.1.8.4. Divest lane shielding shall be placed on the operator side of the lane and have a 22-inch opening from the top of the table to the shielding so that TSOs can access the bins.

4.1.8.5. Divest lane shielding panels shall cover the entire length of the rollers, tables or modulars.

4.1.8.6. Search bench shielding shall be framed out, cover three (3) sides of the table on the passenger side of the table, and have a 22-inch opening with a sliding door, from the top of the table to the shielding, so that TSOs can pass the bins to the passengers once the bag search is completed.

4.1.8.7. All shielding panels shall be secured and attached to the table with brackets and shall be removable. Shielding shall have minimal movement.

4.1.8.8. Shielding panels shall have no air gaps and must fit into the brackets or silicone strips.

4.1.8.9. All glass or clear acrylic shielding shall be free of any sharp edges or safety issues.

4.1.8.10. All divest shielding panels and the passenger facing panel of the search bench shall include hands-free speaker, microphone, and speaker grills to facilitate clear communication between officer and passengers.

4.1.8.10.1. Speaker grills shall range between a minimum of 5.6 inches to a maximum of 7 inches in diameter, include a non-woven fabric insert to reduce the amount of airborne droplets while allowing two-way communication, and centered on the panel between a minimum of 54 inches to a maximum of 60 inches from the ground.

4.1.8.10.2. Hands-free speaker and microphone solution shall fit in the speaker grill slot.

4.1.8.10.3. Hands-free speaker and microphone shall be plugged into the CT unit and/or battery backup for the divest location and power strip at the search bench.

4.1.8.10.4. Wire mold shall be used on the shielding panel to protect the wire and cable management.

4.1.9. Ultraviolet Technology - The Contractor shall propose an optional “add-on” package for the CPSS Base systems to disinfect bin surfaces via germicidal ultraviolet C (UV-C) light to help prevent both passengers and TSOs from being exposed to harmful viruses and bacteria.

4.1.9.1. The UV-C light shall decontaminate bins and, at a minimum, inactivate the SARS-CoV-2 virus at 75mJ/cm2 (Log 2 reduction - 99%) (threshold).

TSA’s objective requirement is 150 mJ/cm2 (Log 3 reduction-99.9%).

4.1.9.2. UV-C light solution can reach the 75mJ/cm2 requirement using various methods, such as lengthening the bin exposure time or using more powerful bulbs.

4.1.9.3. Placement of UV-C light solution in relation to the CPSS system shall be proposed by the Contractor in order to best meet the requirement.

4.1.10. If the PVS is not attached to the Scanner, a table or stand must be provided for the PVS and the PVS cord length shall be at least 12 feet long. The table should not exceed 24” in depth and 30” in width.

4.1.11. System power and data cables shall be at least 25 feet in length and be able to reach electrical outlets A, B, and C as per the CRPG Electrical and Data Sections. Battery backup cords need to be at least 10 feet in length.

4.1.12. All sections of security glass panels need to be flexible in size to account for each buffer module and reject line/revest section when modular are removed or added, as needed.

4.1.13. All CPSS systems must meet all applicable federal, state, and local requirements based on the final installation location. 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.

4.1.13.1. The Contractor shall provide systems with seismic anchoring brackets and hardware needed 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. Signed, sealed, stamped drawings by a seismic engineer and detail drawings shall be submitted.

4.1.13.2. The Contractor shall provide systems with a terminal slope up to 2% with a nominal minimum range and as required based on applicable federal, state, and local codes for a deployed location and in accordance with Attachment 14, Checkpoint Sloped-Floor Study.

4.1.13.3. The Contractor shall provide field stamped engineering drawings for requested slope for proof of concept.

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

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

4.1.13.4.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.14. TSA reserves the right to add additional security screening equipment and/or barriers external to the CPSS system to protect the checkpoint from potential security breaches.

4.1.15. The Contractor shall ensure all delivered CPSS systems are upgradeable to Accessible Property Screening System (APSS) Detection Standard 6.2 Level 1 at no cost to the Government. No cost to the Government includes all costs associated with the APSS 6.2 Level 1 upgrade installation, including any associated costs with SAT and training/simulator updates.

4.1.16. In accordance with the CPSS Program’s Incremental approach, the Contractor shall ensure all delivered CPSS systems are capable of being upgraded to meet future CPSS Functional Requirements Documents (FRDs).

4.1.17. 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.17.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.17.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.17.3. The Contractor shall make all data described in the FRD available to TSA as defined in CPSS FRD Version 2.0.

4.1.17.4. The Contractor shall provide images in DICOS v02A Toolkit compliant format, as outlined in the CPSS FRD Version 2.0 and any subsequent engineering changes. Deliverables shall be determined at the time the optional CLIN for engineering support services is exercised.

4.1.18. The Contractor shall provide the Contracting Officer’s Representative (COR) with editable electronic copies of all training material, to include, but not limited to, a training manual, operator manual, simulator manual, job aids, and TSA specific, specification sheets within ten (10) calendar days after award, and additional updates as needed.

4.1.18.1. Training materials shall be the basis for TSA to develop unique curriculum incorporating the Contractor’s material with the appropriate safety and screening procedures.

4.1.19. The Contractor shall provide the COR with electronic copies of the user manual, maintenance manual, installation manual, interface control document (ICD), TSA specific specification sheets 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 one-hundred and-forty (140) TSA-approved bins per system.

4.2.1.1. Antimicrobial Bins – The Contractor may propose optional antimicrobial bins, but it is not required. Any proposed bin must be approved through the Transportation Security Laboratory (TSL) to ensure detection performance certification is not impacted by use of the alternate bin.

4.3. Divest and Revest Roller Tables

4.3.1. The Contractor shall provide twelve (12) foot of divest and revest roller tables per system that are level with the CPSS system conveyers, made up of modular sections no more than four (4) feet long with rubber footing to prevent sliding on the floor (3’ to 3’3” is preferred for each section of rollers).

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

4.4. Buffers

4.4.1. The Contractor shall provide systems with a standard of zero (0) buffers, and an option for a maximum of three (3) buffers, based on the checkpoint design for each lane.

4.4.2. The Contractor shall ensure engineering and testing with each buffer configuration is complete prior to delivery of the FAT&E system.

4.5. CPSS Simulator

4.5.1. The Contractor shall provide one (1) simulator (hardware and software) per CPSS system to train TSOs on the CPSS system.

4.5.1.1. The Contractor shall ship and install the simulator prior to CT system delivery as directed by the COR, no later than thirty (30) calendar days prior to SAT/iSAT.

4.5.1.2. The Contractor shall ensure all necessary images are loaded into the simulator prior to shipment and installation.

4.5.2. The Contractor shall provide all simulators 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.5.2.1. The Contractor shall ensure all simulators are representative of deployed

CPSS systems at all times; they shall provide a Graphical User Interface (GUI) that has the same look, feel, and functionality as the actual CPSS system (coloration, button-ology, etc.). Upgrades to the simulators shall occur when the Contractor upgrades the CPSS System in accordance with TSA requirements and approval.

4.5.3. The Contractor shall provide a simulator with the capability to export images in

DICOS v02A Toolkit compliant format.

4.5.4. Simulators shall have the ability to remove system generated bounding boxes from threat items for training purposes.

4.5.5. Simulators must have an automatic scoring feature for all practice and assessment image sessions.

4.5.6. Simulators shall have the same user-authentication means as logging into the actual CPSS system.

4.5.7. Simulators shall have the ability to develop and store multiple simulation sessions that can be recalled as needed for training purposes.

4.5.8. Simulator shall have the ability to create, maintain, update, archive, and retrieve user profiles and threat images, using a standard file format. All images are considered Sensitive Security Information (SSI) and the storage/protection of those images must meet TSA/DHS standards for safeguarding SSI.

4.5.9. The Contractor shall provide TSA with two (2) simulators (hardware and software) and two (2) simulator software in CD or USB media format that can be loaded on existing training computers (software only, not contractor hardware) for training purposes at no cost to the Government; this will be included as part of the Training Class Materials deliverable no later than ten

(10) calendar days after contract award.

4.5.9.1. The existing TSA training computers have a 64-bit Operating System, x64-based processor Windows 10 operating system with Intel® Core™ i7-4790 CPU @ 3.60GHz 16.0 GB Installed Memory (15.9 GB Useable) and TSA Workstation Image 3.0_2019_09_U.

4.6. Rerun Cart

4.6.1. The Contractor shall provide one (1) rerun cart per system.

4.6.2. 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.7. Bin Carts

4.7.1. The Contractor shall provide four (4) bin carts per system.

4.7.2. Bin carts shall have the first set of bins permanently attached to the bin cart so any stacked bins do not slide off the cart.

4.7.3. Bin carts shall include a safety brake to keep the cart in place when not in use.

4.8.Search Bench

4.8.1. The Contractor shall provide one (1) standalone table for secondary searches of an alarmed bag where AVS is located.

4.8.2. The search bench shall be 30” inches x 48” inches standard or 30” inches x 72” inches rectangular tables, as required by the location. All search benches shall have shielding and communication devices. If a 30” x 72” table is required, it shall be ready for upgrades to a 2nd AVS unit.

4.8.3. The search bench shall include cable management for AVS and shall have a stainless steel top. The table must be able to be placed independent of the CPSS system, meaning as a stand-alone item. The table must have lockable doors to ensure the computer and equipment can be securely located under the table.

4.9. Test Readiness Notification (TRN)

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

4.9.1.1. A formal test may include, but is not limited to, a First Article Test and Evaluation (FAT&E), a Factory Acceptance Test (FAT), or Site Acceptance Test (SAT).

4.9.2. The Contractor shall submit a Test Scheduling Notice (TSN) via email to the COR and the Acceptance Test Lead at least fourteen (14) calendar days prior to the start of each formal test using the template provided by the TSA Acceptance Test and System Acceptance (ATSA) team.

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

a. Program Name;

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

c. Model name of the unit(s) to be tested;

d. Type of test to be conducted;

e. Equipment setup;

f. Date, time and location of test event;

g. Test procedure (version);

h. Program Officer and Original Equipment Manufacturer (OEM) representative name, email and phone number;

i. Comments.

The TRN Template will be provided by the Government prior to the Post- Award Conference.

4.10. First Article Testing

4.10.1. The Contractor shall submit an FAT&E Plan and procedures as coordinated between the OEM and the ATSA team to the COR within twenty (20) days after contract award.

4.10.1.1. The Contractor shall ensure its FAT&E 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.10.1.2. Within the FAT&E Plan, the Contractor shall provide a schedule for the FAT&E and all test and evaluation resources required, including personnel, equipment, and facilities.

4.10.1.3. The ATSA Team will review and accept the Contractor’s FAT&E Plan and procedures. The TSA test lead may add additional tests to the procedures as deemed necessary.

4.10.1.4. The COR must approve the Contractor’s FAT&E Plan prior to the

FAT&E taking place.

4.10.1.5. The COR, along with a team of Subject Matter Experts, will participate in the FAT&E.

4.10.1.6. The COR will approve the FAT&E unit.

4.11. Acceptance Testing (FAT/SAT)

4.11.1. FAT Plan, Procedures, and Execution

4.11.1.1. The Contractor shall submit a Factory Acceptance Test Plan and Procedures as coordinated between the OEM and the ATSA team to the COR within twenty (20) days after contract award.

4.11.1.1.1. The Contractor shall ensure its FAT plan and procedures describe 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.11.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.11.1.1.3. The ATSA team will review and accept the Contractor’s FAT Plan and procedures and will notify the COR. The TSA test lead may add additional tests to the procedures as deemed necessary.

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

FAT taking place.

4.11.1.2. TSA and its designated test agent reserves the right to observe or not to observe the scheduled FAT at the Contractor’s facility upon the Contractor’s submission of the TRN to TSA.

4.11.1.3. TSA, its designated test agent, or the Contractor shall submit a report of FAT results and findings within three (3) calendar days after the test event to the COR and TSA Acceptance Test Lead for approval. The COR, in coordination with the TSA Acceptance Test Lead, will determine and notify the Contractor who will be responsible for providing FAT results and findings for approval in advance of the scheduled FAT.

4.11.2. SAT Plan, Procedures, and Execution

4.11.2.1. The Contractor shall provide support, as needed, for TSA’s SAT 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. The Government reserves the right to accept or reject recommendations provided by the Contractor.

4.11.2.2. Additional tests may be added by the ATSA team as required to adequately determine if the system is operationally suitable and effective.

4.11.2.3. TSA or its designated test agent will perform each SAT at every installation site in accordance with TSA’s approved SAT 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 is typically performed one (1) day after the completion of system installation.

4.11.2.3.1. 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.11.2.3.2. TSA will provide notification of SAT to the Contractor at least ten

(10) calendar days prior to execution of SAT.

4.12. Configuration Management (CM)

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

4.12.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.12.2. The Contractor shall not alter the system in any way without the Government’s express written approval.

4.12.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.12.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.12.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.12.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.12.4. Configuration Baselines

4.12.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.12.5. Configuration Identification

4.12.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.12.5.1.1. The Contractor shall ensure the CI identification is available in a

Master Configuration Item List (MCIL) and uniquely identify all system CIs and top level hardware and software.

4.12.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.12.5.3. The Contractor shall update MCILs quarterly, in accordance with

Attachment 2, Master Configuration Item List.

4.12.6. Configuration Control

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

4.12.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.12.6.3. The Contractor shall maintain configuration change management of hardware, software, firmware, and developmental/commercial and training documentation.

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

4.12.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.12.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.12.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.12.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.12.6.6. The Contractor shall submit ECPs to the COR and Configuration

Manager via email at CTOCM@tsa.dhs.gov, in accordance with Attachment 3, Engineering Change Proposal Form.

4.12.6.6.1. Any modification that results in a change to the system’s form, fit, function, safety, cost, or schedule, or that requires a retrofit requires a Class 1 ECP. In addition, any change to a CI, no matter how minor, shall be approved by the agency via a Class 1 ECP prior to its implementation.

4.12.6.6.2. Any modification that does not result in a Class 1 ECP shall be submitted to the agency via a Class 2 ECP for acknowledgement and concurrence.

4.12.6.7. The Contractor shall submit RFDs to the COR and Configuration Manager via email at CTOCM@tsa.dhs.gov, in accordance with Attachment 4, Request for Deviation Form.

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

4.12.6.8. The Contractor shall submit RFWs to the COR and Configuration Manager via email at CTOCM@tsa.dhs.gov, in accordance with Attachment 5, Request for Deviation/Waiver Form.

4.12.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.12.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.12.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.12.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.12.6.9. The Contractor shall provide all configuration management changes for TSE via email to CTOCM@tsa.dhs.gov.

4.12.7. Configuration Status Accounting (CSA)

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

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

4.12.7.3. The Contractor shall provide CSA information as a monthly

Configuration Status Accounting Report (CSAR).

4.12.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.12.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.12.7.4. The Contractor shall describe its CSA system in the Contractor’s

CMP.

4.12.8. Configuration Audits

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

Contractor configuration audits.

4.12.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 (PCA).

4.12.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.

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

4.12.8.2.3. The Contractor shall schedule a PCA for the First Article prior to the First Article Test & Evaluation (FAT&E) that will set the production MCIL for the production model. The baseline of the production model shall be consistent with the MCIL that was identified during system qualification. Any updates to the product baseline, after contract award and prior to the PCA, shall be approved via a Class 1 ECP prior to them being included as part of the product baseline.

4.12.9. Configuration Audit Summary Report (CASR)

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

4.12.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.

4.13. Engineering Support Services

4.13.1. Optional engineering support services shall only be utilized at the discretion of the Contracting Officer, formalized via a signed modification. If an option is exercised for engineering support services, the Contractor shall provide engineering services to support upgrades and enhancements to the systems as required to address evolving needs in the field for all deployed systems, to include any donated CPSS units in which the Contractor is prime.

4.13.1.1. The Contractor shall propose optional engineering support services for TSA review, regardless whether the proposed service level is Low, Medium, or High, based on the established CLIN schedule. The service level will be stipulated in the modification to exercise the optional CLIN for engineering support services.

4.13.2. The Contractor shall perform all work required to support services on all systems purchased under this contract as well as any donated CPSS units in which the Contractor is prime.

4.13.2.1. The Contractor shall be responsible for all travel, labor, materials, equipment and installation, disposal and support services needed to perform upgrades and enhancements.

4.13.2.2. The Contractor shall schedule on-site work with sites prior to commencing work to minimize impact on day-to-day operations. Any disruptions or interference with airline or airport operations resulting from the work that cannot be avoided shall be closely coordinated with and approved in advance by the affected parties (i.e., airport authority and TSA) prior to commencement of activities.

4.13.3. Engineering support services may include, but is not limited to:

Software or hardware improvements Services to support configuration management changes resulting in system enhancements Activities that require knowledge of TSE engineering data to meet

TSA requirements.

System upgrades to fielded systems (including software or algorithm changes and system hardware modifications) Approved ECP deployment implementation

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;

Date for next PMR; and System Physical Design Review.

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 the Checkpoint Property Screening System Specification Sheet Attachment and appropriate slope and seismic documentation 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 slope and seismic documentation shall be a sealed engineering document approved and signed by a seismic engineer confirming any change by the Contractor to the approved configuration design do not impact the integrity or functionalist of the CPSS system.

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.2.2.2 The Contractor shall remove and dispose of all dunnage from shipping and installation of new OEM equipment.

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. The individual components of the system can be stored in different locations when the required documentation is provided to the TSA Deployment Logistics Division (DLD) to allow tracking for system 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 initial warranty with each CPSS system, commencing at iSAT approval.

7.1.1. TSA reserves the right to exercise optional years of warranties, up to a total of an additional eight (8) years, to include warranties for donated CPSS units in which the Contractor is prime.

7.1.1.1. The Contractor shall maintain CPSS system warranty period dates for all deployed systems, to include all donated CPSS units in which the Contractor is prime, 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 and bin carts) 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.2.1. In the event that a repair cannot be completed in the CPSS’ deployed location, due to the impact on checkpoint screening operations (i.e., shutting down other lanes), the Contractor is responsible for all costs associated with rigging and moving the CPSS and peripheral equipment to an agreed upon location in the airport; completing the repair; and the re-installation of the CPSS and peripheral equipment at the CPSS’ deployed location.