Attachment_14_AT_CT_SOW_redlined_as_of_A00005.pdf

Attachment 14:

Advanced Technology (AT)/Computed Tomography (CT)

Statement of Work (SOW)

A00004A00005

1. Background

1.1. The Transportation Security Administration (TSA) was created to meet the nation’s need for safety and security throughout our 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 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 AT/CT systems, simulators, program management, warranties, configuration management services, as well as shipping and installation. All other associated labor, materials, and travel required to meet the requirements of this Statement of Work 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 do 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 AT/CT Qualified Product List system configuration and associated TSA bins.

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

“Engineering Change Proposal” (ECP) – a request to incorporate a permanent change to 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 Conveyer” - The ingress system is conveyances (rollers/belts) to introduce bags into the CT. The Egress system is the conveyances (rollers/belts) to exit the bags from the system.

“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 AT/CT 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 and diverter systems.

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

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

4.1. Checkpoint Systems (CLINs 00001, 00001A and 00011)

4.1.1. AT/CT Checkpoint System

4.1.1.1. The Contractor shall deliver TSA qualified, fully functional AT/CT systems as submitted as part of the QPL process, inclusive of all TSA critical mandated fixes.

4.1.1.1.1. Systems shall include the scanner and, all peripheral equipment required to complete a checkpoint screening lane as defined in Attachment 19, the Checkpoint Design Guide CDG) Version 6.1.

4.1.1.1.2. No later than 60 90 calendar days after award, the Contractor shall deliver a FAT&E unit, which includes all TSA critical mandated fixes, to the Transportation Security Integration Facility (TSIF) for final approval.

However, the Contractor may propose an alternate delivery date.

4.1.1.1.2.1. Thirty (30) AT/CT systems shall be deployed no later than

30 calendar days after successful completion of FAT&E, and 30 systems per month following the first delivery. However, the Contractor may propose an alternate deployment schedule.

4.1.1.2. Prior to the cessation of warranty services and in accordance with Other

Transaction Agreement 70T04019T9DAPM204, the Contractor shall negotiate, in good faith, and enter into any necessary agreements with TSA’s third-party service providers to provide any Original Equipment Manufacturer (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 AT/CT systems.

4.1.1.2.1. The Contractor shall provide documentation to TSA, no later than sixty (60) business days prior to the expiration of this contract, to confirm that there is an agreement in place with the third-party service provider(s) to provide any Original Equipment Manufacturer (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 AT/CT systems with the third-party service provider(s).

4.1.1.2.2. The Contractor shall maintain an Excel spreadsheet with AT/CT system warranty period dates for all deployed systems.

4.1.1.2.2.1. The spreadsheet shall be submitted to the COR no later than three days after SAT of the first systems and updated monthly thereafter.

4.1.1.3. The Contractor shall include all necessary hardware and software with the

AT/CT systems to meet all AT/CT Operational Requirements Document V 4.0 and Functional Requirements Document V 1.6 requirements.

4.1.1.4. The Contractor shall ensure the final AT/CT systems are AT Tier II certified and are configured in accordance with the configuration items and configuration management documents as seen in section 4.4, inclusive of any approved Change Requests (CRs).

4.1.1.5. The Contractor shall ensure all AT/CT systems are upgraded to Accessible

Property Screening System 6.2 and any subsequent new versions and inclusive of any data rights provided during the development of these algorithms.

4.1.1.6. 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.1.6.1. The Government rights in production data, result data, and log files compiled during testing are determined under FAR 52.227-17 “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.1.6.2. FAR 52.227-1 “Authorization and Consent (DEC 2007)” shall apply only to modifications to proprietary hardware or software as directed and produced under this contract. FAR 52.227-3 “Patent Indemnity (APR 1984)” 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.1.6.3. The Contractor shall make all data described in the Functional

Requirements Document (FRD) available to TSA as defined in Reference 5, AT/CT Functional Requirement Document Version 1.6, Requirements 21-23.

4.1.1.7. The Contractor shall provide the COR with an electronic copy of all training material within twenty (20) business days after award.

4.1.1.7.1. This material shall reflect the latest, updated system.

4.2. Test Readiness Notification (CLINs 0001 and 00001A)

4.2.1. The Contractor shall submit a TRN via email to the Contracting Officer’s

Representative (COR) at least ten (10) business days prior to the start of each formal test.

4.2.1.1. A formal test may include, but is not limited to, a Factory Acceptance Test (FAT) or a Site Acceptance Test (SAT).

4.2.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.3. Acceptance Testing (FAT/SAT) (CLINs 0001 and 00001A)

4.3.1. FAT Plan, Procedures, and Execution

4.3.1.1. The Contractor shall submit a FAT plan and FAT procedures to the COR within twenty (20) business days after contract award using the attached FAT procedures template.

4.3.1.1.1. The Contractor shall ensure its FAT plan describes the methods for testing, evaluating, and accepting the AT/CT 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.3.1.1.2. The Contractor shall provide a schedule for planned FATs and all test and evaluation resources required, including personnel, equipment, and facilities in the FAT plan.

4.3.1.2. The COR must approve the Contractor’s FAT plan prior to any FAT taking place.

4.3.1.3. TSA and its independent test agent will observe the FAT at the Contractor’s facility upon the Contractor’s notification to TSA that the system is ready for FAT.

4.3.1.4. 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.3.2. SAT Plan, Procedures, and Execution

4.3.2.1. The Contractor shall review and provide recommendations on TSA’s SAT plan and procedures to the COR within twenty (20) business days after the COR provides the Contractor with TSA’s SAT plan and procedures.

4.3.2.2. TSA Acceptance Test Team will review the Contractor’s recommended test procedures and add additional tests as required to adequately determine if the system is operationally suitable and effective.

4.3.2.3. TSA or its independent test agent will perform a SAT for each AT/CT system at every installation site in accordance with TSA’s approved SAT plan and procedures developed under Section 4.3.2.2 as well as OEM or TSA provided test articles (when needed).

4.3.2.3.1. The Contractor shall provide direct on-site support during these tests.

4.3.2.3.2. The Contractor shall be available to the test team during testing to answer any questions, perform any required system maintenance, obtain system data, and assist with system testing.

4.3.2.3.3. TSA will provide notification of SAT to the Contractor at least ten

(10) business days prior to execution of SAT.

4.3.2.3.4. The Government and/or Government designated contract representative will perform each SAT and confirm the AT/CT system is properly configured 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.4. Configuration Management (CM) (CLINs 0001 and 00001A)

4.4.1. The Contractor shall maintain AT/CT systems under strict CM.

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

4.4.3. The Contractor shall establish, implement, and maintain a CM Program based on the SOW requirements. The CM Program 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.4.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.4.3.1.1. If the Contractor does not already have a TSA approved CMP, the Contractor shall prepare and deliver its CMP to the COR in accordance with Attachment 1, Configuration Management Plan within thirty (30) business days of contract award

4.4.3.2. 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 CM Program. The CM requirements are applicable to all deliverables under this contract.

4.4.4. Configuration Baselines

4.4.4.1. The Contractor shall establish and maintain the configuration baseline for each TSE configuration and establish and maintain the required documentation to support this configuration, referred to as the Product Baseline (PBL).

4.4.5. Configuration Identification

4.4.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.4.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.4.5.2. The Contractor shall prepare and deliver one (1) MCIL per TSE to the

COR ten (10) business days after contract award in accordance with Attachment 2, Master Configuration Item List to the COR.

4.4.5.3. The Contractor shall update MCILs quarterly in accordance with

Attachment 2, Master Configuration Item List.

4.4.6. Configuration Control

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

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

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

4.4.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.4.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 VECP

4.4.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 clause 52.248-1.

4.4.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 AT/CT.

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

Attachment 3, Engineering Change Proposal Form.

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

Attachment 4, Request for Deviation Form.

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

4.4.6.8. The Contractor shall submit RFWs to the COR in accordance with Attachment 5, Request for Deviation/Waiver (RFD/RFW).

4.4.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.4.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 First Article Test and Evaluation (FAT&E).

4.4.6.8.2.1. FAT&E validates FRD requirements against the first unit manufactured. A product baseline is derived from this test.

4.4.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.4.6.9. The Contractor shall provide all configuration management changes for

TSE via email to CTOCM@tsa.dhs.gov.

4.4.7. Configuration Status Accounting

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

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

4.4.7.3. The Contractor shall provide CSA information as a monthly Configuration

Status Accounting Report (CSAR).

4.4.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.4.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.4.7.4. The Contractor shall describe its CSA system the Contractor’s CMP.

4.4.8. Configuration Audits

4.4.8.1. The Contractor shall support PBL audits and shall perform internal contractor configuration audits.

4.4.8.2. The Contractor shall prepare a Configuration Audit Plan (CAP) in accordance with Attachment 7, Configuration Audit Plan that describes mailto:CTOCM@tsa.dhs.gov procedures for conducting the audit, including Functional Configuration Audit and Physical Configuration Audit.

4.4.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.4.8.3. The Contractor shall deliver the CAP thirty (30) business days before a configuration audit.

4.4.9. Configuration Audit Summary Report

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

4.4.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. AT/CT Simulator (CLINs 00002 and 00002A)

5.1. The Contractor shall provide TSA with simulators to train Transportation Security

Officers (TSO) on the AT/CT system.

5.2. The Contractor shall ship and install simulators, as directed by the COR, no less than ten

(10) business days prior to SAT.

5.3. 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 AT/CT system (Graphic User Interface, keyboard or buttonology, etc.).

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

5.3.2. The Contractor shall upgrade all simulators 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. This upgrade to the simulators shall occur when the Contractor upgrades the AT/CT systems in accordance with Section 4.1. of this SOW.

6. AT/CT Simulator Upgrades (CLIN 00002B)

6.1. The Contractor shall update the two (2) simulators previously purchased by TSA at TSA Headquarters with the current qualified system software inclusive of any approved CRs within twenty (20) business days after award.

7. Program Management (CLINs 00003-00003D)

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

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

7.1.2. Post-Award Conference

7.1.2.1. The Government will conduct a post-award conference at the Contractor’s facility, TSA Headquarters, or an alternative site specified by the Government within thirty (30) calendar days after contract award at a date proposed by the Contractor and approved by the COR.

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

7.1.2.3. The Contractor shall prepare and deliver the minutes for the conference in accordance with section 7.1.3.2

7.1.3. Program Meetings and Meeting Documentation

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

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

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

7.1.3.3. The Contractor shall conduct and administratively support quarterly Program Management Reviews (PMR) at the Contractor’s site, TSA Headquarters, or an alternative site specified by the Government. Typically, PMRs will alternate between the Contractor’s site and TSA Headquarters.

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

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

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

7.1.3.6. The Contractor shall report on organizational status (i.e., changes, issues, etc.) during each PMR.

7.1.3.7. The Contractor shall report on cost, schedule, and technical progress in meeting reviews/status reports.

7.1.3.8. The Contractor shall provide Program Status Reports (PSR) monthly to the COR. A PSR is not required the month the PMR occurs.

7.1.3.8.1. The Contractor shall ensure the reports address problems/risks in the Contractor’s functional areas as well as cost, schedule, technical progress, and status of deliverables.

8. Logistics and Maintenance Support Services (CLINs 00004 - 00004D)

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

8.1.1. Warranty or maintenance 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.

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

8.2. Logistics support service shall include the following:

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

8.2.1.1. The Government considers tests required at scheduled intervals such as radiation leak surveys to be preventive maintenance.

8.2.1.2. The Contractor shall coordinate all preventive maintenance scheduling with local TSA staff as appropriate.

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

8.2.1.4. The Contractor shall request COR approval to waive the requirements for performing monthly preventive maintenance in the month when TSA decommissions an AT/CT system.

8.2.1.5. 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.2.2. 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.2.2.1. The Contractor shall inform the COR when refurbished parts are initiated into the Contractor’s supply chain for corrective maintenance repairs.

8.2.2.2. 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.2.2.3. The Contractor is responsible for the storage of all spare parts, consumables, hardware and software necessary to fulfill the requirements of this contract.

8.2.3. 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.2.4. The Contractor shall ensure documentation of all maintenance actions (including preventive, corrective, and excepted) is in the TSE Maintenance Database.

8.2.5. 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.2.6. 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.2.6.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.3. Parts Obsolescence Management Program (CLINs 00004 – 00004D)

8.3.1. The Contractor shall establish and implement a parts obsolescence program.

8.3.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.3.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.3.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.4. Logistics Support Service Level Requirements (CLINs 00004 – 00004D)

8.4.1. The Operational Availability (Ao) of Transportation Security Equipment (TSE) is critical to TSA. Performance penalties shall be enforced to ensure the Contractor meets the Service Level Agreement (SLA) Ao metrics set forth in this section.

8.4.2. The Service Level Agreement requirements specified in this section are Contract requirements. The Contractor shall calculate Ao for each airport on a monthly basis, and this calculation will be used as the basis for the Contract performance requirement. Section III.B, C. 5200.242.003(h) of the Request for Proposal outlines the penalties for months when Ao falls below Contract requirements.

8.4.3. The contractor shall provide the calculations and raw data on a monthly basis to

TSA. The Ao metrics will be calculated as applicable in accordance with Attachment 18, TSE Terms and Definitions and RMA Metrics utilizing Airport Operational hours.

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

During Airport Operating Hours SLA Required Ao

Fleet Level SLA1 98% Table 2: Ao Requirements

8.4.4.1. TSA will apply the SLA requirements to the total number of units deployed nationwide.

8.4.4.2. TSA will count any failure inherent to the AT/CT system that is a component of the AT/CT system and maintained by the AT/CT OEM toward Ao.

8.4.5. The Contractor shall only include installed systems that have passed SAT in its Ao calculations.

8.5. Preventive Maintenance (CLINs 00004 - 00004D)

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

8.5.1.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 AT/CT system.

8.5.1.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.1.2.1. In providing Level II preventive maintenance, the Contractor shall comply with the following:

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

8.5.1.2.1.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.1.2.1.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.1.2.1.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.1.2.1.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.1.2.1.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.1.2.1.5. The Contractor shall coordinate with local TSA staff the week prior to the scheduled week.

8.5.1.2.1.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.1.2.1.7. The Contractor shall provide all required consumables

(cleaning supplies, filters, etc.).

8.5.1.2.1.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.1.2.2. 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.1.2.3. The Contractor shall record PM actions in local maintenance logbooks provided by local TSA and in the Contractor’s database.

8.5.1.2.3.1. If there is no logbook available at the location, the

Contractor shall notify local TSA at the location. If a logbook is not provided by TSA, the Contractor is not required to wait for the logbook. If the logbooks are not available and local TSA is not present, then the Contractor will continue with his or her scheduled work. In both cases, the Contractor will note the non-availability of the logbook in the remarks section of the PM ticket.

8.5.1.2.3.2. If there is no local maintenance logbook available, the

Contractor shall record this in the database along with date the PM was conducted. Entering the date conducted indicates that the Contractor completed the PM in full on that date according to the applicable OEM checklist.

8.5.2. The Contractor shall perform preventive maintenance as part of the PMP, and ensure it is performed no greater than seven (7) calendar days past the recommended period.

8.5.2.1. The Government reserves the right to consideration if the Contractor fails to perform the Level II Preventative Maintenance requirements as outlined in this Section.

8.5.3. The Contractor shall provide a copy of the radiation survey report for each system to the local TSA POC, TSA COR, and be able to provide a copy to additional designated Government personnel upon request after the Contractor completes the annual survey.

8.5.3.1. The Contractor shall ensure the emission limit set in the performance standard identified in 21 Code of Federal Regulations (CFR) Part 1020.40 is not exceeded.

8.5.3.2. The Contractor shall perform radiation surveys at least annually or after any maintenance that affects the radiation shielding or x-ray production components, after system relocation, and after any incident that may have damaged the system such that unintended radiation emission could occur.

8.5.3.2.1. The Contractor is responsible for investigating and recording all unusually high emission readings identified on the survey and correcting any conditions on the system which caused the elevated readings as applicable.

8.5.3.2.1.1. If the Contractor makes repairs to address the elevated readings, then the Contractor shall perform a follow up survey to verify effectiveness of corrective action.

8.5.3.2.2. The Contractor’s Radiation Survey Officer or qualified individual shall review each radiation survey, perform a quality check, and sign the form confirming it has been completed correctly.

8.5.3.2.2.1. If TSA or the Contractor identifies an error and the COR returns the survey to the Contractor to correct, the Contractor shall make all corrections and resubmit the corrected survey to the COR within seven (7) calendar days of identification and notification.

8.5.3.3. The Contractor shall immediately notify the COR and local TSA if there is an emission level confirmed above the 21 CFR 1020.40 emission limit.

8.5.3.3.1. The Contractor shall adhere to the electronic product radiation control provisions 21 CFR 1002.20 and/or 21 CFR 1003.10 as applicable if a radiation survey reading is confirmed to have exceeded the emission limit.

8.5.3.3.2. The Contractor shall document radiation readings before and after any service call that is related to suspected and unplanned radiation exposure and document the incident in the TSE database.

8.5.3.3.3. The Contractor shall provide the COR with, but not limited to, the system SN, system location, and explanation of why the radiation reading is high, a pre radiation survey documenting the high radiation reading, action to resolve the issue, and a completed radiation survey when the issue is resolved.

8.5.3.4. Local TSA officials will ensure the equipment is removed from service

(i.e. not used for security screening) until the Contractor repairs the system and verifies repairs are within the 21 CFR 1020.40 performance standard limits if there is an emission level confirmed above the 21 CFR 1020.40 emission limit.

8.5.3.5. The Contractor shall mount a radiation survey sticker to the AT/CT system upon completion of the survey. The label will include the following:

performed by, date of survey, next radiation survey due, and System Meets Food and Drug Administration Requirements of 21 CFR 1020.40.

8.5.3.5.1. The Contractor shall provide a copy of the radiation survey report for each AT/CT unit to the local TSA POC (reference Attachment D-2).

8.5.3.6. The Contractor shall prepare the Radiation Survey Reports in accordance with Attachment 9, Radiation Survey Submittal.

8.6. Corrective Maintenance (CLINs 00004 – 00004D)

8.6.1. The Contractor shall perform corrective maintenance. After the system is delivered, installed and passes SAT/ORT then the Contractor is responsible to respond and repair the system when a maintenance work order is called in.

8.6.2. The three (3) levels of corrective maintenance are as follows:

8.6.2.1. Level I – TSA performs as needed to effect repairs that do not require trained Field Service Technicians (FST) (e.g., bag jams, etc.).

8.6.2.2. Level II – The Contractor performs as needed to effect repairs that always require trained FSTs. These services are included under Section 4.

8.6.2.3. Level III – The Contractor performs by shipping the TSE end item (vs.

component of TSE) to a repair depot after the Contractor fails to repair the failed TSE. These services are included under Section 4.

8.7. TSE Maintenance Database (CLINs 00004 – 00004D)

8.7.1. The Contractor shall establish and maintain a TSE maintenance database after the

CT system has passed SAT/ORT and ready or being used for security screening operations:

• Includes the entire inventory of fielded TSE maintained under this SOW, which will be the basis for computation of performance metrics;

• Uniquely identifies each TSE by model and serial number;

• Includes information on all accumulating preventive and corrective maintenance actions;

• Includes preventive maintenance start time (at the machine) and stop time

(when the FST is finished) for every unit so TSA can monitor the average preventive maintenance duration time;

• Includes maintenance metrics data and provides the full maintenance and performance history;

• Will reflect all time values reported in local airport location time;

• Will provide Government access to all data collected;

• Will provide a database summary report that itemizes data errors and calculation corrections made by the Contractor to achieve maintenance statistics;

• Will provide Government personnel upon request detailed maintenance actions on work order tickets; and

• Will ensure FMI codes are in a standard format and used in a consistent manner.

• The Contractor shall establish and maintain a TSE Database in accordance with Attachment 10, TSE Database.

8.8. FMI Codes (CLINs 00004 – 00004D)

8.8.1. The Contractor shall create or develop FMI codes and capture the FMI codes in the TSE Maintenance Database.

8.8.2. The Contractor shall assign one (1) or more FMIs for each corrective maintenance action.

8.8.3. The Contractor shall ensure FMI codes identify the failure cause; sub-system part(s) consumed in the repair; and detailed resolution or action code(s) that would restore the TSE to operational condition.

8.8.4. The Contractor shall submit the proposed FMI codes to the COR and the TSA

Service Response Center within sixty (60) calendar days after award for approval prior to implementation and whenever the Contractor updates the FMI codes.

8.8.4.1. The Contractor shall apply the FMI codes in a consistent manner.

8.8.4.2. The Contractor shall ensure only the approved FMI codes are used in maintenance reporting.

8.9. Waste Disposal (CLINs 00004 – 00004D)

8.9.1. The Contractor shall be responsible for the proper removal and disposal of any and all equipment or components replaced during preventive and corrective

8.9.2. The Contractor shall take immediate ownership of all replaced parts that have been removed from the equipment except for Government accountable property with a TSA property bar code.

8.9.3. The Contractor shall be responsible for all labor, materials, equipment, and coordination of logistics activities to load, transport, and offload waste materials.

8.9.3.1. The Contract shall properly package, crate, and prepare waste materials for shipment.

8.9.3.2. The Contractor shall take full advantage of reuse, reutilize, and recycle options as the first method of disposition or disposal.

8.9.3.3. The Contractor shall be responsible for proper disposal of any and all hazardous waste in accordance with and as defined by 40 CFR Parts 260, 261, and 263.

8.9.3.4. The Government reserves the right to direct the Contractor to an alternate disposition of removed equipment and components.

8.9.3.5. The Contractor shall request disposition of accountable property from the Government Property Manager.

8.9.4. CT Hard Drive Sanitization

8.9.4.1. The Contractor shall sanitize each AT/CT system’s internal hard drives upon disposal.

8.9.4.2. The Contractor shall ship TSA information technology assets, including computers, hard drives (including magnetic and solid-state), and media with persistent memory containing Sensitive Security Information (SSI) that the Contractor determines to be beyond repair capability at the unit location back to the Contractor’s TSA authorized facility for disposal.

8.9.4.2.1. The Contractor shall ship the item via any traceable means (i.e., tracking number) through a mail or parcel carrier (e.g., U.S. Postal Service, Federal Express) and packaged in a way that does not disclose its contents or the fact it contains sensitive information (double-wrapped in a non-opaque wrapper) in accordance with the TSA Management Directive (MD) 1400.3, TSA Information Technology (IT) Security Handbook.

8.9.4.2.2. The Contractor shall comply with all data disposition requirements stated in the TSA IT Security Policy Handbook, applicable Technical Standards and TSA MD 3700.4, Handling Sensitive Personally Identifiable Information.

8.9.4.3. TSA will sanitize hard drives that the Contractor determines to be beyond repair capability or refurbishment (on-site or at the Contractors depot facility) of SSI data at the TSA Springfield Warehouse.

8.9.4.3.1. The Contractor shall complete Sections I, II, and III of TSA Form 1412 TSA Media Sanitization Certificate dated April 2009 (Attachment

11) for each hard drive and shall email it to the Acquisition Program Management Accountable Property Officer at CtoPropertyManagement@dhs.gov.

8.9.4.3.2. The Contractor shall ship the inoperable hard drives, with a copy of the completed and signed TSA Form 1412, via any traceable means (i.e., tracking number) through a mail or parcel carrier (e.g., U.S. Postal mailto:CtoPropertyManagement@dhs.gov

Service, Federal Express) packaged in a way that does not disclose its contents or the fact that it contains sensitive information (double-wrapped in a non-opaque wrapper) to TSA Springfield Warehouse at the address below.

TSA Springfield Warehouse ATTN: Jason Lockley / David Funk 6810 Loisdale Rd Building A, Door 19 Springfield, VA 22150 Jason.Lockley@tsa.dhs.gov 703-313-7868

8.10. Reliability, Maintainability, Availability (RMA) Metrics (CLINs 00004 –

00004D)

8.10.1. The Contractor shall prepare a RMA metrics report and deliver it monthly to the COR via email in a PowerPoint or pdf document.

8.10.1.1. The Contractor shall report all reported metrics for the month in which they are incurred.

8.10.1.2. The Contractor shall only calculate and include in the calculations of higher level metrics for the reporting period that portion of the metric actually taking place during the reporting period when a low level metric spans a period longer than the reporting period.

8.11. Dispatch Contact Capability (CLINs 00004 – 00004D)

8.11.1. The Contractor shall have contact capability to receive maintenance requests from the TSA Service Response Center (TSRC) and dispatch FSTs to provide

8.11.2. The TSRC is required to dispatch calls within fifteen (15) minutes of receipt.

8.11.3. The Contractor shall establish interface protocols with the TSRC to ensure that all TSE maintenance calls are recorded and dispatched to Contractor FSTs within fifteen (15) minutes of receipt of a maintenance request from the TSRC.

8.11.4. The Contractor shall provide status updates to the TSRC on every open trouble ticket as status changes occur until the ticket is closed.

8.11.5. The Contractor shall send a formal notification to both the TSRC and the local TSA POC upon closure of the trouble ticket.

8.11.6. The Contractor shall supply the location and serial numbers to the TSRC prior to a new TSE installation or equipment relocation to ensure there is no disruption in maintenance service response.

8.11.7. The Contractor’s contact facility shall be reachable twenty-four (24) hours a day, seven (7) days a week.

8.11.8. The Contractor shall not use callback or voice message systems for the TSRC calls related to TSE maintenance.

9. Equipment Shipping (CLINs 00005 - 00008A)

9.1. The Contractor shall directly ship the AT/CT systems to specified airports, Systems

Integrator’s facilities (local riggers’ warehouse), or additional TSA laboratories.

9.1.1. The System Integrator will handle the site preparation, shipping from the Riggers Staging Facility to the airport, rigging, and coordination with OEMs.

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

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

9.2.2. 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).

The Contractor shall provide storage for each AT/CT system at no additional cost to the Government for up to six (6) months after FAT to accommodate deployment.

9.3. The Contractor shall provide a AT/CT Specification Cut Sheet no later than twenty (20) business days after award, that provides guidance necessary to enable TSA to execute all site preparation requirements in advance of deployment of AT/CT systems.

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

10. Bins (CLINs 00009 and 00009A):

10.1. If the Contractor requires bins that differ from the TSA bins, the Contractor shall provide 140 bins, 4 bin carts per system and one (1) rerun bin cart.

10.1.1. The bin cart shall have one bin permanently attached to the bin cart so any stacked bins do not slide off the cart.

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

11. Divest and Revest Roller Tables (CLINs 00010 – 00010A):

11.1. The Contractor shall provide divest and revest roller tables that are level with the AT/CT system conveyers, made up of modular sections 3-4 feet long.

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

12. Deliverables

12.1. The Contractor shall provide all deliverables in Table 3: Deliverables.

12.1.1. While the Government defines the contents throughout the SOW, table 8.2 outlines the due date/frequency of each deliverable.

12.1.2. The Contractor shall send all electronic deliverables to the COR via email.

12.1.3. The Contractor shall schedule and coordinate all physical deliverables requiring shipping/acceptance s with the COR.

No. Deliverable Due Date

1 AT/CT Units and Two (2) Year Warranty In accordance with the schedule identified in Section

4.1.1.1.2 or as proposed by the Contractor

2 FAT&E Unit No later than (NLT) 60 calendar days after award or as proposed by the Contractor.

Excel spreadsheet with AT/CT system warranty period dates for all deployed systems

NLT three (3) days after SAT of the first systems and updated monthly thereafter

Documentation confirming that OEM has entered into agreement with third party maintenance provider

NLT sixty (60) business days prior to expiration of the contract

5 Training Class Materials Twenty (20) business days after award 6 TRN Ten (10) business days prior to each formal test 7 FAT Plan and Procedures Twenty (20) business days after contract award 8 SAT Plan and Procedures Recommendations Twenty (20) business days after contract award 9 CMP Thirty (30) business days of contract award

10 MCIL Initially ten (10) business days after award and updated…