SOW_Relocatable Passenger Vehicle Scanning System.pdf

U.S. Department of Homeland Security U.S. Customs and Border Protection

Statement of Work

For:

U.S. CUSTOMS AND BORDER PROTECTION

NON-INTRUSIVE INSPECTION SYSTEMS

Relocatable Passenger Vehicle Scanning System

PREPARED BY:

NII PROGRAM MANAGEMENT OFFICE (PMO)

Tabel of Contents

1. PURPOSE

1.1 Background and Scope

1.2 Period of Performance

1.2.1. Delivery

1.2.2. Invoicing

1.3 Program Organization

1.3.1. Government Management Organization

2. APPLICABLE DOCUMENTS

2.1 Federal Regulations and Publications

2.2 National Standards

2.3 DHS/CBP Documents

2.4 Order of Precedence

3. REQUIREMENTS

3.1 Requirements Definitions

3.2 General Requirements

3.2.1. Performance Requirements for Relocatable Passenger Vehicle Scanning Systems 12

3.2.2. Computer Security

3.2.3. Printed Documents

3.2.4. Printer / Scanner

3.3 Systems Integration

3.3.1. Work Center

3.3.2. Workstation Integration and Interface

3.3.3. Integrated Image Capture

3.3.4. Integrated Image Storage

3.3.5. Integrated Image and Data Capture

3.3.6. Image Download

3.3.7. Integrated Data Package Download / Transfer

3.4 Safety Interlocks

3.5 Reliability, Availability and Maintainability

3.5.1. Classification of Reliability Critical Items

3.5.2. Basic Reliability Quantitative Requirements

3.5.3. Control of Reliability Critical Items

3.5.4. Availability - Operational Availability (Ao)

3.5.5. Obsolescence Report

3.5.6. Service Calls and Work Orders

3.5.7. Preventive Maintenance

3.5.8. Corrective Maintenance

3.5.9. Corrective Maintenance Services

3.5.10. Remote Maintenance Monitoring

3.5.11. Configuration Report

3.6 On-Demand Services (Technology Refresh, Other Maintenance, and Other Support Services)

3.6.1. Corrosion Control

3.6.2. Engineering Services

3.6.3. Ad Hoc Reports

3.6.4. Site Surveys

3.6.5. Provisioning Support

3.6.6. Retrofit Support

3.6.7. Relocation Services

3.6.8. Site Work

3.6.9. Decommissioning and Disposal Services

3.6.10. Emergency Services

3.6.11. Special Events

3.6.12. On-Demand Training

3.7 Safety Plan

3.7.1. Hazardous Materials

3.8 System Support Requirements

3.8.1. System Training

3.8.2. Operator Training

3.8.3. Train-the-Trainer

3.8.4. Ownership

3.8.5. Technical Manuals

3.8.6. System User's Manual

3.8.7. Operational/Storage Checklist

3.8.8. Operator Service Manual

3.8.9. Other Reviews

3.9 Quality Assurance and Testing

3.9.1. Quality Assurance

3.9.2. Contractor Testing

3.9.3. CBP Factory Testing

3.9.4. CBP Site Acceptance Testing

3.9.5. Technical Reviews

3.10 Radiation Safety

3.10.1. Radiological Survey and Report

3.10.2. Annual Radiation Survey and Report

3.11 Configuration Management

3.11.1. Technical Documentation

3.11.2. Engineering Change Proposals (ECPs)

3.11.3. Interchangeability

3.11.4. Accessibility

3.11.5. Government Furnished Equipment

4. LIFE CYCLE SUSTAINMENT AND SUPPORT REQUIREMENTS

4.1 Warranty

4.2 Warranty Period Configuration Changes

5. INFORMATION TECHNOLOGY SECURITY

5.1 Basic Requirements

5.1.1. System administration duties shall consist of:

5.2 Security Authorization

5.3 Encryption Compliance Requirement

5.4 Security Review

5.5 DHS Security Policy Requirement

5.6 Enterprise Security Architecture

5.7 Product Assurance

5.8 Continuous Monitoring

5.9 Access to Unclassified Facilities, Information Technology (IT) Resources, and Sensitive Information

5.10 Personal Identity Verification (PIV) of Contractor Personnel

5.11 PIV Credential Compliance

5.12 CBP Contractor Handling PII Level

5.13 Security Requirements for Unclassified Information Technology Resources .. 49

5.14 Contractor Employee Access (JULY 2023)

5.14.1. HSAR Clause 3052.204-71, Contractor Employee Access

5.14.2. ALTERNATE I (JULY 2023)

5.14.3. ALTERNATE II (JULY 2023)

5.15 3052.204-72 - Safeguarding Of Controlled Unclassified Information (July 2023)

5.15.1. Definitions. As used in this clause—

5.15.2. Handling of Controlled Unclassified Information

5.15.3. Incident Reporting Requirements

5.15.4. Incident Response Requirements

5.16 Information Technology Security Awareness Training (JULY 2023)

5.16.1. Security Training Requirements

5.16.2. FAR 52.224-3 Privacy Training – ALTERNATE I (Deviation)

5.17 DHS-CBP Enterprise Architecture Compliance

5.18 Supply Chain Risk Management Terms and Conditions:

5.19 DHS Information Technology Portfolio Alignment

5.20 1Pv6

5.21 Accessibility Requirements (Section 508 Compliance)

5.20.1. Section 508 Applicable EIT Accessibility

5.20.2. Section 508 Applicable Exceptions

5.20.3. Section 508 Compliance Requirements

5.21 3052.204-73 Notification And Credit Monitoring Requirements For Personally Identifiable Information Incidents (July 2023)

5.22 Interconnection Security Agreement Requirements

5.23 OCIO CISO Cyber-Supply Chain Risk Management (C-SCRM)

5.23.1. Definitions

5.23.2. Original Equipment Manufacturer (OEM) End-use Information and Communications Technology (ICT) Product

5.23.3. Accounting of Components in ICT Products

5.23.4. Supply-Chain Transport

5.23.5. Changes to Ownership and Control

6. SPECIAL CONSIDERATIONS

6.1 Changes to the SOW

6.2 Travel

6.3 Points of Contact

6.3.1. Technical POC:

6.3.2. Contracting Officer:

6.3.3. Contracting Officer's Representative:

6.3.4. Budget (SAP Approver):

Version Date Comments v1 09/03/2024 Original v2 12/18/2024 ILD Comments

Statement of Work

1. PURPOSE

The purpose of these LS-NII Relocatable Passenger Vehicle Scanning Systems is to enable CBP to perform effective and efficient scanning passenger cars and other light vehicles in large numbers to reveal anomalies (including explosives, drugs, and currency) in high-throughput environments like border crossings. These mobile systems allow drivers and passengers to remain in the vehicle with the use of low dose x-ray.

Relocatable Passenger Vehicle Scanning Systems are capable of scanning 150 vehicles per hour or more in the normal flow of checkpoint traffic. The system scans entire vehicles, bumper to bumper, in just a few seconds and can be relocated quickly with no disassembly.

1.1 Background and Scope

The U.S. Customs and Border Protection (CBP) Office of Field Operations (OFO) and United States Border Patrol (USBP) requires a capability to quickly detect the illegal transit of contraband transported through people, cargo containers, and in other conveyances entering through ports of entry (POE) and at international mail and express consignment carrier facilities. Since 2014, there has been an escalation of dangerous synthetic drug usage, specifically fentanyl, in the United States. The majority of fentanyl being trafficked in the United States is produced in other countries such as China and is smuggled primarily through the international mail and express consignment carrier facilities (e.g., FedEx and UPS) and through POE along the southern land border. As America’s unified border agency, the CBP has a critical role in the Nation’s efforts to keep fentanyl, and other dangerous synthetic drugs, out of the hands of the American public while ensuring safety of CBP’s frontline officers.

1.2 Period of Performance

The anticipated period of performance is twelve (12) months from the date of award with four (4) option years.

The effective period begins at award and ends at completion of the warranty period of the last Relocatable Passenger Vehicle Scanning Systems order during the last active order, or the last day of the ordering period, whichever is later.

CBP intends to procure five (5) Relocatable Passenger Vehicle Scanning Systems during the base year.

1.2.1. Delivery

The contractor shall provide a planned delivery schedule within 30 days of award. Delivery of systems shall begin no later than Sixty (60) days from the date of execution of a Delivery Order. Coordination shall be made with the CBP technical POC listed in SOW Section 6 prior to delivery. On site operational testing shall be conducted prior to acceptance of each system.

The contractor shall provide updates to the delivery schedule on a quarterly basis or if a significant deviation of more than 10% occurs.

1.2.2. Invoicing

The Contractor shall submit an original invoice to the address designated in the contract to receive invoices. The invoice shall be simultaneously transmitted electronically to the COR at the e-mail address provided in section 6.3, and the Contractor shall invoice CBP per CBP invoicing clause, “Electronic Invoicing and Payment Requirements – Invoice Processing Platform (IPP) (JAN 2016).”

Please ensure the following are included in all invoices:

• Contract number.

• Order Number (e.g., Task Order, Delivery Order, Purchase Order, etc.).

• Description of supplies or services provided for a specified time period.

• CLIN the supplies or services are charged under.

• Unit price and total amount of each item; and discount terms (if applicable).

• Company name, telephone number, taxpayer’s identification number, and complete

• mailing address to which payment will be mailed.

• Backup documentation showing the government has received the goods and/or services.

Payment requests shall be submitted electronically through the U. S. Department of the Treasury's Invoice Processing Platform System (IPP).

"Payment request" means any request for contract financing payment or invoice payment by the Contractor. To constitute a proper invoice, the payment request must comply with the requirements identified in FAR 32.905(b), "Payment documentation and process." The IPP website address is: https://www.ipp.gov.

A courtesy e-mail notification upon invoice submission in IPP shall be sent by the Contractor to the COR. Only the CO has the authority to represent the Government in cases where the delivery order requires a change in the terms and conditions, delivery schedule, scope of work and/or price of the products and/or services under this task order

1.3 Program Organization

This program is under the technical direction of the LS-NII Contracting Officer Representative (COR) assigned to the Office of Field Operations (OFO) and Non- Intrusive Inspection Division in coordination with CBP OIT/Enterprise Network and Technology Support Directorate (ENTSD) Integrated Logistics Division (ILD)

1.3.1. Government Management Organization

CBP will manage this program through the CBP NII PMO process for system acquisition, delivery, and acceptance. CBP OIT/Enterprise Networks and Technology Support Directorate (ENTSD), Integrated Logistics Division (ILD) will manage the system(s) during the warranty period(s) to include any corrective maintenance actions, preventive maintenance activities, and Logistic Support. CBP Non-Intrusive Inspection Division (NIID) will approve training development and operator training and presentations. CBP Human Resources Management (HRM) will approve radiation safety limits.

2. APPLICABLE DOCUMENTS

Documents cited shall be referenced and used as called for in this Statement of Work Performance Specifications.

2.1 Federal Regulations and Publications

• Code of Federal Regulations, 10 CFR 20, Standards for Protection against Radiation, 2012, (NRC).

• Code of Federal Regulations, 10 CFR 39.35, Leak Testing of Sealed Sources, 2012, (NRC).

• Code of Federal Regulations, 10 CFR 71, Packaging and Transportation of Radioactive Materials, 2012, (NRC).

• Code of Federal Regulations, 21 CFR 179, Irradiation in the Production, Processing and Handling of Food, 2012, (FDA).

• Code of Federal Regulations, 29 CFR 1910, Occupational Safety and Health Standards, 2012, (OSHA).

• Code of Federal Regulations, 49 CFR 172, Hazardous Materials, Etc., 2012, (DOT)

• U. S. Department of Transportation Federal Highway Administration Bridge Formula Weights August 2006 FHWA-HOP-06-105 (http://www.ops.fhwa.dot.gov/publications/publications.htm#fa).

2.2 National Standards

• American National Standards Institute, ANSI/IEEE N42.41, Minimum Performance Criteria for Active Interrogation Systems Used for Homeland Security, 2007.

• American National Standards Institute, ANSI/IEEE N42.46, Determination of the Imaging Performance of X-Ray and Gamma-Ray Systems for Cargo and Vehicle Security Screening, 2008.

• American National Standards Institute, ANSl/HPS N43.3, General Radiation Safety - Installations Using Non-Medical X-Ray and Sealed Gamma-Ray Sources, Energies up to 10 MeV, 2008.

• American National Standards Institute, ANSl/HPS N43.14, Radiation Safety for Active Interrogation Systems for Security Screening of Cargo, Energies up to 100 MeV, 2011.

• National Fire Protection Association, NFPA 79, Electrical Standards for Industrial Machinery, 2007.

• Federal Information Processing Standards Publication (FIPS PUB),

• Number 140-2, Security Requirements for Cryptographic Modules, 2001

• National Fire Protection Association, NFPA 70, Recommended Practice for

Electrical Equipment Maintenance, 2010.

2.3 DHS/CBP Documents

• DHS Sensitive Systems Policy Directive 4300A, Version 13.0.

• CBP Information Systems Security Policies and Procedures, HB 1400-05D, Version 7.0.

• DHS Management Directive (MD) 11042.1 Safeguarding Sensitive But

Unclassified (For Official Use Only).

• DHS-CBP N.25, Standard Messaging Protocol, Version 1.5.0.6, 2010

• CBP Interface Control Document, Version 5, Jan 2013.

• CBP Port Radiation Inspection, Detection and Evaluation (PRIDE) 2.0 Interface

Control Document (ICD) version 5, 2015.

• CBP Training Development Standards, 2008.

• CBP Instructor-Led Training (ILT) Style Guide, 2009.

• CBP Instructor-Led Training (ILT) Process Guide, 2008

2.4 Order of Precedence

In the event of a conflict between the texts of this SOW and the references cited above, this SOW takes precedence. However, nothing in this SOW supersedes applicable federal and state safety laws.

3. REQUIREMENTS

The Contractor shall perform all tasks within this SOW. The Contractor shall abide by all applicable Federal regulations, national standards, and U.S. Department of Homeland Security (DHS) and CBP documents in performing all tasks. Requirements for this effort shall include the fabrication, integration, test, delivery, training, logistics, and on-demand support of LS-NII Mobile Systems.

These systems will be deployed at various CBP POEs along the Southwest Boarder within the United States as designated by CBP. Specific sites and schedules shall be identified during contract negotiations.

3.1 Requirements Definitions

3.1.1. Threshold: The minimum level of operational performance that the Government is willing to accept is considered a threshold value.

3.1.2. Objective: A level of performance that significantly improves mission performance, safety, or supportability beyond that of the threshold value, and represents the desired yield for system performance is considered an objective.

3.1.3. Objective values are not required but can be defined to provide guidance to the Contractor with respect to areas where increased capability is of interest/value to the government. If Objectives are defined, the interval between the Objective and Threshold values for a given parameter is the government program manager’s (PM) trade-space.

3.1.4. Single Requirement: Some requirements will have only a single parameter value and, when this is the case, these values are thresholds.

3.2 General Requirements

The Contractor shall perform the work necessary to develop, test and deliver the procured equipment. The Contractor shall also provide warranty, logistics, and on-demand services, including initial operator training, for support of these LS- NII inspection systems. Each LS-NII system shall meet the requirements defined in this Statement of Work/Performance Specification.

3.2.1. Performance Requirements for Relocatable Passenger Vehicle Scanning

Systems

3.2.1.1. The complete system, all sub-systems, and all components, parts, and attachments shall be new. Proposals incorporating reconditioned or used systems in part or in full are not acceptable and will be deemed as non-responsive. The system shall be new, commercially available, and in commercial production as of the closing date of this solicitation. The system shall be relocatable, readily deployable, have self-contained mobile capability and meet all the main and sub-system manufacturers published overall and sub-system performance specifications prior to delivery.

3.2.1.2. The system containing all listed sub-systems and major components shall be provided as part of the complete system and shall meet individually described detailed technical and performance specifications. Thus, any vendor not responding to all minimum requirements shall be deemed as non-responsive. No prototypes, one-of-a-kind, or two-of-a-kind systems will be considered.

The system shall meet the following specifications:

• The system shall be capable of effective scanning while vehicles are traveling through a port of entry at a rate of 3 to 10 mph.

• The system shall be capable of maintaining a throughput of 150 vehicles per hour.

• The system shall be capable of being installed in a port of entry and rapidly relocated without requiring civil works.

• The system shall be relocatable for port entry or exit.

• The system shall be compliant with ANSI/HPS N43-17-2009.

• The system shall be capable of remote operations.

• Typical system deployment dimensions: 13 ft. wide by 11 ft. high.

x 13 ft. long.

• Typical scanning area dimensions: Approximately 10 ft. wide x 9

ft. high.

• Typical Configuration: 3,500 lb.; Shipping: 4,550 lb.; Mobile configuration: Portal 3,080 lb.; Portal and truck combined: 16,060 lb.

• Each system shall have an ambidextrous portal with a tether (power cable) capable of connecting to either side of the deployed ambidextrous portal.

• The portal tether (power cable) shall be a minimum of 75’ long.

• Each system shall be capable of using shore power.

• Each system shall include the components needed to connect to shore power.

• Auxiliary heat shall be able to operate on both generator power and shore power.

• Each unit delivered shall be delivered with an independent power source/generator that is capable of running at least 24 hours without having a cool down period.

• System shall be capable to start up and begin scanning within 20 minutes at environmental temperatures as low as minus 20 degrees Celsius (minus 4 degrees Fahrenheit).

Special Non-System Requirements

• The contractor shall install CBP supplied radio installation kits in each system.

• Each unit delivered shall be delivered with a pair of signs similar to size, shape, and colors of the attached example. Wording needs to be exact.

• Each portal shall be equipped with signage attached to the overhead, horizontal Support structure, entrance side, informing the occupants they will be scanned with low dose X- rays, in both English and one additional language.

• Each system delivered shall be delivered with CBP OFO branding. (Per current CBP OFO branding style guidelines)

• Each system shall be delivered with law enforcement lights and light bars sirens (with both blue and red flashing lights/strobes to conform with regular OFO fleet vehicle light bars).

3.2.2. Computer Security

All LS-NII System computers and software programs that allow a User to analyze, enhance and store an IDS, and the Data Base computers and programs that store the IDS, shall have the following security features incorporated.

3.2.2.1. Identification and Authentication

• User Accounts - Three levels of CBP User access (Operator Level 1, Operator Level 2, and Administrator) shall be provided. Operator Level 1 shall be able to perform all system functions except copying and deleting images or Data Sets. Operator Level 1 shall not have access to User Accounts. Operator Level 2 shall be able to perform all Operator functions plus be able to copy and delete IDS files. Operator Level 2 shall not have access to User Accounts. The Administrator shall be able to perform all Operator Level 2 functions plus have access to User Accounts. The Administrator shall be able to create, edit and/or delete User Accounts. The Contractor shall be required to create a simplified procedure for the Administrator to use in order to create, edit and delete User Accounts. Operator Level 1 & 2 shall not have access to Windows except for those hard drives that have IDS stored on them or the external drives from which an image may be imported or an image or IDS may be exported or copied. The Administrator shall have access to Windows if required for system operation.

• Passwords – All user account passwords shall be required to be strong passwords. Passwords shall meet the requirements of Password Management of the DHS 4300A Sensitive Systems Handbook Version

9.0 dated 2011, or the latest version at the time of award. Strong password requirements are:

o Be at least 8 characters in length o Contain a combination of alphabetic, numeric, and special characters o Not be the same as any of the user’s previous 8 passwords o Should not contain a dictionary word o Should not contain any simple pattern of letters or numbers o Should not be any word, noun, or name spelled backwards or with a single digit appended, or with a two digit “year” string o Should not be the same as the user Id.

• Passwords – Automatic password change frequency. The system shall prompt the user to change their password every 90 days.

• Password Storage – They system shall store all user account passwords in encrypted form.

3.2.2.2. Access Control

• Unique User Accounts – All users shall have unique account identifiers, including separate operator accounts and administrator accounts for users that have both responsibilities.

• Automatic Account Lockout – The system shall lock a user account for twenty (20) minutes after three consecutive failed logon attempts.

• Automatic Session Termination – The system shall lock the user login session after twenty (20) minutes of inactivity. The system shall require the user to authenticate with the user account password to regain system access after the system lock. After 60 minutes of inactivity, the user account shall be logged off of the system.

• Warning Banner – The DHS Chief Information Security Officer (CISO) stipulates that a warning banner statement be displayed on all DHS systems during user account logon. The system shall prompt the user to accept the current language before they can authenticate with the user id and user password to access the system. The current language required follows:

o You are accessing a U.S. Government information system, which includes (1) this computer, (2) this computer network, (3) all computers connected to this network and (4) all devices and storage media attached to this network or to a computer on this network. This information system is provided for U.S. Government-authorized use only.

o Unauthorized or improper use or access of this system may result in disciplinary action, as well as civil and criminal penalties.

o By using this information system, you understand and consent to the following:

You have no reasonable expectation of privacy when you use this information system; this includes any communications or data transiting, stored on, originated from or directed to this information system. At any time, and for any lawful government purpose, the government may monitor, intercept, search and seize any communication or data transiting, stored on, originated from or directed to or from this information system.

The government may disclose or use any communications or data transiting, stored on, originated from or directed to or from this information system for any lawful government purpose.

You are NOT authorized to process classified information on this information system.

3.2.2.3. Auditing

• Audit Records – System will retain audit records sufficient in detail to facilitate the reconstruction of events if compromise or malfunction occurs. Audit records shall contain at least the following information:

o Identity of each user and device accessing or attempting to access the system o Time and date of the access and the logoff o Activities that might modify, bypass, or negate information security safeguards o Security – relevant actions associated with processing o All activities performed using an administrator account/identity

• Audit Record Access – Audit records and audit logs should be protected from unauthorized access, modification, or destruction.

• Audit Record Retention – Audit records should be maintained on the system for a minimum of ninety (90) days. Audit records shall be preserved for a period of 7 years as part of managing records for each system to allow audit information to be placed online for analysis with reasonable ease.

• Audit Reduction / Report Generation – The system will provide an audit reduction and report generation capability that:

o Supports on-demand audit review, analysis, and reporting requirements and after-the-fact investigations of security incidents o Without altering the original content or time ordering of audit records

• The system will have the capability to tag each scan with the username who conducted it. The username and time shall be displayed with the image and the IDS.

3.2.3. Printed Documents

All LS-NII Systems shall have the capability of printing all the items of an IDS.

This is to include the radiographic image, video capture "snapshots", notes and the Data Sheet and/or Manifest if included as part of the IDS. All printed documents shall have "LAW ENFORCEMENT SENSITIVE" in the header or footer.

3.2.4. Printer / Scanner

Printer shall be capable of quality printing while retaining a limited physical footprint. Scan/print devices may be combined or separate units.

3.3 Systems Integration

Integration of NII inspection system equipment and its supporting Subsystems shall be the responsibility of the NII systems Contractor.

3.3.1. Work Center

The Contractor shall deliver a Work Center ergonomically designed for housing the system's Workstation. The system's Workstation for mobile systems shall be housed inside the mobile unit.

3.3.2. Workstation Integration and Interface

The Contractor shall configure and integrate Workstations and Interface Operating systems to include an Operator Console, computers and computer software, cameras and the controls and displays to scan a conveyance, analyze the image, make a Suspect or Non-suspect decision and store all the items that make up that IDS.

3.3.3. Integrated Image Capture

All LS-NII Systems shall be capable of capturing and displaying all of the items that make up an IDS. The IDS shall include the radiographic image, one or more video capture snapshot images, a Data Sheet or Manifest, Notes, the Suspect or Non-suspect decision and the User's name. This Metadata shall be the sole property of CBP.

3.3.4. Integrated Image Storage

All LS-NII Systems shall be capable of storing a complete IDS for a period of 90 Days, or one (1) Terabyte of storage, whichever is greater. A warning shall be provided when the hard drive used to store the IDS files reaches 70% of its maximum storage capacity and again when it reaches 90% of its maximum storage capacity. The warnings shall alert the Operator for the need to copy and delete IDS files. If the hard drive reaches 99% of its maximum storage capacity, a warning shall be provided and the system will not be allowed to scan until IDS files have been copied and deleted. The system shall provide an option at the Administrator level for auto delete of Non-Suspect files that are over 90 days old.

3.3.5. Integrated Image and Data Capture

All NII Systems will be capable of capturing and displaying all of the items that are contained in an IDP (See FRD Appendix A). The IDP shall include, as applicable, the radiographic image(s), a video capture snapshot image from each system CCTV camera, system metadata, conveyance identification (e.g., container ID, LPR, RFID and QR code reads), a Data Sheet or Manifest, operator notes, the operator’s Suspect or Non-suspect decision and the User's name. Additional IDP element requirements, if applicable, are specified in the FRD. All NII image data and metadata shall be the sole property of CBP.

LPR and Container ID (if applicable) read capability shall be installed as a means to identify a particular vehicle and cargo shipment, and to associate it with its NII image package as the vehicle proceeds through the POE scanning and inspection process. This metadata shall be collected as the vehicle queues to be scanned by the NII sensor system.

3.3.6. Image Download

The image will be configured in a format known as Unified File Format (UFF), where CBP may easily transfer the image from one computer containing the image analysis software to another computer containing the image analysis software without the loss of the image analysis functionality. For traditional NII scanning operations in secondary, this transfer will be conducted manually via secure thumb drive or other OIT-approved media. In future NII- IP integrated system applications, all NII image and metadata shall be collected by CBP and securely transferred to the CBP Cloud.

3.3.7. Integrated Data Package Download / Transfer

The IDP shall consist of the data specified within the FRD. The consolidated IDP shall encompass all of the data required to perform an offsite scan review and analysis as though the reviewer was stationed at the original data site. The system shall also be capable of creating and exporting a summary scan report for each conveyance scanned – the format of this report shall be PDF. For the NII-IP, the complete IDP will be securely transferred via the CBP network to the CBP Cloud and no longer needs to be retained for any extended length of time on the NII sensor system itself. DACTER will associate manifest and/or other more sensitive data with the NII IDP within the XARDIS Cloud database. The contractor shall support the development of an Interface Control Specification (ICD) and physical/data connections to CBP IT systems, to facilitate the connection to CBP network and IDP transfer capabilities.

3.4 Safety Interlocks

The Contractor shall provide safety interlocks such as operator proximity/presence sensors and/or "dead man switches" for all systems for the protection of pedestrian traffic and untrained personnel.

The Contractor shall provide Emergency Stop Switches for all systems which will allow an operator to manually interrupt the scanning process disabling the transmission of X-rays in an emergency or when there is an unauthorized entry inside the system's Radiation Control Area. Emergency Stops shall be strategically located in the driver's cab, in the Work Center, and on the side and rear of the system where applicable. A remote emergency stop switch for the traffic control secondary operator is an objective.

See ANSI N43.3-2008 and ANSI N43.14- 2011 for more details on safety interlocks.

When actively radiating the LS-NII system shall provide audible and visible (flashing lights) alarms.

3.5 Reliability, Availability and Maintainability

Each NII system is expected to have the highest Reliability, Availability and Maintainability achievable for this type of technology. The following are minimum requirements for these systems.

3.5.1. Classification of Reliability Critical Items

A Critical Item is an identified weak link in a system, has an adverse impact on, or contributes to failures of the system performing its mission, creates potential safety problems, or contributes to other areas of high risk to overall system reliability. The Contractor shall classify all LS-NII items as critical if one or more of the following conditions are satisfied:

• Item represents a significant new development or application.

• Item has critical failure modes.

• Item has history indicating need for improvement. A Preplanned

Product Improvement Plan (PPIP) shall be developed and provided by the Contractor for any item with a history of needing improvement.

• Item has known operating life, limited shelf life, or environmental sensitivity (e.g., vibration, thermal, etc.) that warrants controlled surveillance.

• Item whose failure can result in the failure of the system and which is not compensated by redundancy or alternate operational procedures

3.5.2. Basic Reliability Quantitative Requirements

The system shall possess a mean time between failure (MTBF) of no less than 1000 hours or 8000 scans. The operating life of the NII system shall be no less than 10 years. The NII system shall normally operate 16 hours a day, 6 days a week, 52 weeks a year during an operating life of 10 years but it shall be capable of surge operating 24 hours a day, 7 days a week for 2 weeks (336 hours).

3.5.3. Control of Reliability Critical Items

The Contractor shall be responsible for the Quality Control of critical items, which shall include as a minimum:

• Procedures for the procurement of, and availability of, spares of critical items.

• Criteria and procedures for the design and redesign of critical items

• Procedures for controlling and monitoring of critical items after manufacture (e.g., date coding, traceability, assembly techniques, test requirements, acceptance test requirements, control of sub- Contractors' and manufacturers' controls, in-process controls, special handling and storage requirements).

3.5.4. Availability - Operational Availability (Ao)

An average Ao by unit shall be calculated using data for WOs completed during the reporting period:

AO = Total Hours by Unit – Down Time Hours by Unit Total Hours by Unit

Operational Availability is defined as the percentage of time during the reporting period (monthly) that a specific unit serialized device listed in the contract is available to support the operations for which it was designed.

Downtime associated with preventive maintenance, accidents, incidents, or delays at the Government request are not included in the Ao calculation. The following lists the standard Ao targets for equipment types, as defined in the definition section of this document, by location category:

96% - Large Scale Equipment (to include rail inspection) in CONUS Pre- Primary Ports of Entry locations.

95% - Large Scale NII Systems (excluding handheld technologies) in CONUS locations

90% - NII Systems (excluding handheld technologies) in OCONUS locations

The Ao shall be calculated at the system level (per serialized system). The Contractor shall also consider the pre-primary NII at CBP locations when assessing the urgency and nature of the request.

Customer Wait Time (CWT)

The Contractor shall restore systems reported in a non-operational status to a satisfactory operational status within the CWT corresponding to the Ao’s above, based on a 720-hour month.

WOs for work performed under on-demand (other maintenance support services) and WOs with customer delays are excluded from all the formulas above.

The Contractor shall meet or exceed these performance standards while complying with all applicable State and Federal regulations. In addition to the quality of deliverables, operational availability levels achieved, coordination, and reporting requirements represent the measurements considered appropriate to the performance of this work statement.

3.5.5. Obsolescence Report

The Vendor shall provide obsolescence notifications to the ILD as soon as possible, but no later than one (1) year in advance of a component, software, firmware, hardware, part, or peripheral associated with the system becoming obsolete, and which would cause the device to be unserviceable, unrepairable, or otherwise unsupportable.

3.5.6. Service Calls and Work Orders

All service calls and work orders apply to corrective maintenance under the warranty period, and preventative maintenance. The Integrated Logistics Division (ILD) - manages an NII Maintenance Dispatch Center (MDC) for maintenance, repair call activities, and incident management that operates 24/7/365. The NII Maintenance Dispatch Center responds to service calls from the numerous CBP locations to intake and track the calls for service in the CBP databases. The NII Maintenance Dispatch Center staff issue requests for repair or maintenance services to the Vendor in the form of a work order (WO) that initiates the maintenance request.

Work Completion Form - The WCF is a unique form to a specific maintenance event. The WCF shall include the WO number assigned by the Government, a description of the maintenance action performed, identify the failure cause or part if any, a list of replaced parts, usage data or scan count since last maintenance activity, name and email address of the Port Official that witnessed completion, and completion date/time. The Contractor shall forward both the Corrective Maintenance WCF within 24 hours and the Preventative Maintenance WCF within 48 hours to the ILD Maintenance Dispatch Center upon completion of each maintenance action, E-mail: MDC@cbp.dhs.gov. Call the Technology Service Desk (TSD) at 1- 800-927-8729, choose the option “NII and RPM” to reach the Maintenance Dispatch Center.

The Contractor shall provide one (1) copy of the completed WCF to the Government Site Representative.

Work Site Cleanliness – The Contractor shall properly dispose of all damaged parts; components; assemblies; subassemblies; consumables;

and Petroleum, Oil, and Lubricants (POL), unless otherwise directed to retain for failure item analysis or other reasons. The Contractor shall remove all work-related used parts, waste, and debris from the CBP site upon job completion, unless directed otherwise.

3.5.7. Preventive Maintenance

Preventive Maintenance (PM) is defined as any scheduled and planned maintenance actions performed to maintain the target Operational Availability (Ao) and maintenance metrics as defined herein. Preventive Maintenance includes periodic inspections, calibration, condition monitoring, critical item replacement, and servicing requirements. Necessary repair actions discovered during the performance of a preventive maintenance action require separate corrective Work Orders (WO) from the Maintenance Dispatch Center. To the widest extent possible, all preventive maintenance shall be scheduled around port operational activities to prevent disruption to daily operations. The Preventive Maintenance Schedule which entails the number of PMs to perform during that period may also have to be adjusted based on Operational tempo. These decisions will be communicated to the Contractor based on the direction of the Government, to include the ILD staff and the COR. Preventive Maintenance activities shall be considered fluid and maybe adjusted throughout the life of the contract based on evidence from corrective actions. In such case the proposed action shall be proposed and agreed upon bilaterally.

NII Monthly Preventive Maintenance Schedule – The Contractor shall provide a schedule of planned preventive maintenance actions that has been coordinated with Port Officials organized by equipment model, equipment serial number, location, estimated duration of the visit, and planned date of the preventative maintenance visit to the designated ILD Maintenance Manager and COR fifteen (15) business days prior to the beginning of the month.

Preventive Maintenance Visit Schedule – The Contractor shall provide a list scheduled preventive maintenance visits that were conducted with maintenance action to include completed, partially completed, or not performed. The report shall be in excel format to the COR, NII Asset Manager, NII Regional Manager and Port Official. The report should include columns for WO number, equipment model, equipment serial number, location, type of maintenance, maintenance status (fully completed, partially completed, or not performed), duration of service, and date of service monthly by the 5th business day for the previous month.

3.5.8. Corrective Maintenance

Corrective Maintenance is defined as any maintenance activity, which is required to diagnose, correct equipment malfunctions or failures that has occurred or is in the process of occurring. This may consist of repair, restoration, or replacement of components, Desktop/Workstation support that includes password resets, application support, staff access support, and all other Desktop support that might be needed. Corrective maintenance is an unscheduled maintenance activity caused by a unit or component failure and includes tests, measurements, and adjustments.

The Contractor shall contact site and attempt to troubleshoot each problem telephonically. If unable to meet the Customer Wait Time (CWT) as established in the metrics listed below in the table below corresponding with the target Ao, the Contractor shall provide the justification, and a time estimate for effecting repairs to the ILD Maintenance Dispatch Center. The Contractor shall notify the ILD Maintenance Dispatch Center and provide the date and time of System Operational Status changes, Estimated Time of Arrival (ETA) for parts, and Contractor Technician scheduled arrival at site.

These updates to the ILD MDC are integral to successful operations and must be maintained. The contractor must ensure that a minimum update must be made every 48 hours to the MDC even if the status is stagnant to maintain an adequate work history. Deficiencies in updates will result in contractual actions. Habitual deficiencies in the same area will be addressed with the Contractor PM for reconciliation and result in contractual actions.

The Contractor shall coordinate site visits with the CBP ports, as required.

Corrective services may also include assessments on how system comments operate in conjunction with other CBP systems. CBP has deployed integrated and common viewer systems, providing data to other CBP applications. This means that individual systems are connected to software (SW) and hardware (HW) components of other original equipment manufacturers (OEMs). The communication link and compatibility of systems needs to be evaluated in a coordinated effort with other OEMs to meet CBPs operational requirements. Failure to work with other OEMs to meet the success of the mission results in failure to meet the contractual requirements of this contract.

3.5.9. Corrective Maintenance Services

The Contractor shall provide labor, services, parts, equipment, supplies, packaging, transport, shipment, and materials necessary to diagnose and correct malfunctions or failures of equipment.

The Contractor shall provide the labor, services, parts, equipment, supplies, packaging, transport, shipment, Desktop/Workstation support that includes password resets, and materials necessary to diagnose and correct malfunctions or failures and functionality tests of NII Technology when requested. This includes performing minor site restoration or infrastructure construction as required to restore systems reported in a non-operational PRIORITY 1 status to a satisfactory Equipment Operational Status (Priority 2 or 3) within the required Customer Wait Time (CWT) listed in section 5.2 of this document. The Contractor shall restore systems in a PRIORITY 2 Equipment Operational Status to PRIORITY 3 within 5 business days for Large Scale NII systems and 10 business days for Small Scale NII systems.

See operational status definitions in Appendix A.

The Contractor shall respond to the WO by contacting the site POC provided by the ILD Maintenance Dispatch Center. The Contractor shall report the date/time of the contact to the ILD Maintenance Dispatch Center immediately after contacting the site POC.

3.5.10. Remote Maintenance Monitoring

The system shall have the capability to produce failure codes for remote maintenance monitoring to transmit electronically to CBP. The exact transmission method will be determined at a later date. The health status of system components shall be able to be viewed remotely in order to obtain system statistics, guide preventative maintenance actions, and diagnose system issues.

3.5.11. Configuration Report

The Configuration Report shall include the following: equipment model, equipment serial number, location, current software version with any software upgrade history/retrofits for the control console and programmable logic controllers (PLCs); baseline and red line drawings, hardware design and changes; sub-systems, warranty information: and control vehicle configuration. The Contractor shall submit a configuration report within 30 days after award of contract and a quarterly configuration report thereafter to the COR and ILD Service Maintenance.

3.6 On-Demand Services (Technology Refresh, Other Maintenance, and Other Support Services)

The Government anticipates requiring other requested services, separate from those outlined above, as needs arise during this contract. The Government reserves the right to set and escalate priorities for these services to allow for expediting as urgent needs arise. This work is priced as Firm Fixed Price (FFP) based on product incident/accident repairs, reconditioning, technical refresh services, severe corrosion restoration, refurbishment services, engineering services, installation, relocation services, disposal, site services/surveys, maintenance and operator refresher training, source change out, retrofit, emergency services, password resets, software patching, and special event services. On demand services may be requested for any CBP accepted equipment regardless of warranty status or prior inclusion in the contract equipment lists.

3.6.1. Corrosion Control

The Contractor shall apply corrosion control techniques and measures to mitigate and correct corrosion of the X-ray NII equipment listed in individual task orders.

The Contractor shall visually inspect the equipment for signs of corrosion. The Contractor shall apply best practices to remove corrosion or replace parent material, properly treat and prepare surfaces for painting, and apply a color-matched finish.

3.6.2. Engineering Services

Upon written request, the Contractor shall provide engineering services beyond those required in the design, build, and maintenance of the system as required in this SOW (i.e., equipment modifications or enhancements).

3.6.3. Ad Hoc Reports

Upon written request, the Contractor shall provide data that would enable Government performance analysis, economic trade-off studies, budget impact analysis, etc.

3.6.4. Site Surveys

Upon written request, the Contractor shall conduct site surveys based upon CBP/OFO priorities as designated by the COR to support the equipment identified in individual task orders. The Contractor shall coordinate survey activities prior to and during the site surveys with the COR.

3.6.5. Provisioning Support

Upon written request, the Contractor shall provide provisioning technical data for the equipment listed in individual task orders. The Contractor shall provide provisioning technical data traceable to the Original Equipment Manufacturer (OEM) supportability analysis, tailored to satisfy the level of repair and sustainment period identified in the request. The provisioning technical data shall identify major repairable parts, smaller non- repairable components used to effect repairs, consumable lubricants, piece parts used in assembly, criticality of items, acquisition lead times, and Contractor identification information.

3.6.6. Retrofit Support

Upon written request, the Contractor shall perform retrofit functions to address approved Engineering Change Proposals (ECPs), enhancements, Service Life Extension Programs (SLEPs), and technical refresh activities for the equipment listed in individual task orders.

3.6.7. Relocation Services

Upon written request, the Contractor shall provide emergent need relocation services for the equipment identified in individual task orders. The Contractor shall disassemble, transport, and reassemble the components of the system at the new location. The Contractor shall perform post-assembly functional testing of the relocated system and familiarize operators with configuration and operational changes brought about by the relocation. The Contractor shall coordinate re-commissioning and/or recalibration activities, as required.

3.6.8. Site Work

Upon written request, the Contractor shall provide minor repair or electrical work that may be required at the various POE sites where equipment will be deployed external to the equipment unit. An example of work that will be performed includes. Requirements will be identified and requested at the delivery/task order level.

3.6.9. Decommissioning and Disposal Services

Upon written request, The Contractor shall provide decommissioning and disposal services for the system and equipment.

3.6.10. Emergency Services

Upon written request, the Contractor shall provide support in response to various emergency situations and natural disasters (i.e., labor, services, parts, equipment, supplies, packaging, transport, shipment, and materials necessary to support emergency service requirements).

3.6.11. Special Events

Upon written request, the Contractor shall provide support for special events, such as major sporting events and conventions (i.e., labor, services, parts, equipment, supplies, packaging, transport, shipment, and materials necessary to support service requirements).

3.6.12. On-Demand Training

Upon written request, the Contractor shall provide additional, on-demand training services such as: training development, operator training, secondary operator training, train-the-trainer training, training laptops and training material as described in Section 3.8 of this SOW.

3.7 Safety Plan

In accordance with OSHA regulations, the Contractor shall develop and implement a safety plan. The contractor’s safety plan shall also continually identify all safety hazards and provide a methodology to mitigate or eliminate each of the identified hazards.

All products, designs and specifications provided, and all construction and installation activities conducted shall comply with all OSHA, GSA and NRC regulations, as well as any other appropriate laws, regulations, standards, codes and health and safety guidelines.

3.7.1. Hazardous Materials

In accordance with OSHA regulations, the Contractor shall provide a list of all hazardous materials and the corresponding Material Safety Data Sheet (MSDS) for each identified Hazardous Material. The list shall include the material description, quantity of the material, storage and disposal instructions, exposure risks, symptoms and treatments.