70B03C27R00000003-Attachment 1- Draft Statement of Work Large-Scale Fixed Systems (MEP LEP).pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

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

Attachment 1-Statement of Work

For:

U.S. CUSTOMS AND BORDER PROTECTION

NON-INTRUSIVE INSPECTION SYSTEMS

Large-Scale Fixed Systems (Multi-Energy Portal and Low-Energy Portal)

RFP 70B03C27R00000003

PREPARED BY:

Office of Field Operations Innovation and Strategy Directorate

Non-Intrusive Inspection Program Office

October 2026

Statement of Work

LARGE-SCALE FIXED SYSTEMS

Table of Contents 1 Background

1.1 Purpose

1.2 Objective

1.3 Scope

2 Period of Performance

3 Delivery

4 Invoicing

4.1 Milestone/Progress Payment Structure

4.2 General Requirements for Milestone/Progress Payments

4.2.1 Verification of Milestones:

4.2.2 Documentation:

4.2.3 Adjustments:

5 Program Organization

5.1 Government Management Organization

5.2 Contractor Management Organization

5.2.1 Program Management Reviews

6 Applicable Documents

6.1 Applicable Federal Regulations and Publications

6.2 Applicable National Standards

6.3 Applicable DHS/CBP Documents, as may be amended

6.4 Referenced Attachments

7 Work to be Performed

7.1 Requirements Definitions

7.2 General Requirements

7.3 System Requirements

7.3.1 Functional Requirements Documents (FRD)

7.3.2 Integration Requirements

7.3.3 Design, Construction and Installation Requirements

7.3.4 Training Requirements

7.3.5 Testing Requirements

7.4 Life Cycle Sustainment and Support Requirements

8 Deliverables

9 Pricing

10 Information Technology Security

11 Special Considerations

11.1 Changes to the SOW

11.2 Travel

11.3 Points of Contact

11.4 Subcontracting Requirements

1 Background United States (U.S.) Customs and Border Protection (CBP) is responsible for targeting, selecting, and examining vehicles and cargo deemed high risk for terrorist-related activity, smuggling of contraband, and trade law violations. CBP Officers and United States Border Patrol (USBP) Agents are also responsible for ensuring the flow of legal and legitimate trade and travel across U.S. borders. CBP has a continuing requirement to interdict contraband such as weapons, explosives, illegal narcotics, currency, stowaways and numerous other forms of contraband smuggled into the United States through examination of conveyances.

Historically, Non-Intrusive Inspection (NII) scanning was conducted on shipments that were designated by the Port-of-Entry (POE) Advance Targeting Unit (ATU), chosen by random selection, and/or at the discretion of the primary officer. These selected shipments were then scanned using NII systems located in the Secondary Inspection area. The NII systems were not integrated with CBP Information Technology (IT) infrastructure or applications.

Several years ago, CBP began pre-primary and post-primary scanning procedures with the acquisition of Large-Scale Fixed drive-through NII portals [i.e., Multi-Energy Portal (MEP) and Low-Energy Portal (LEP)] to safely scan vehicles, drivers and passengers which greatly increased throughput and the total number of scans. This follow-on NII acquisition will continue to support the deployment of MEPs/LEPs which are fully integrated with the CBP IT network infrastructure, cloud, common integration platform, law enforcement applications and associated databases.

1.1 Purpose

The purpose of these Large-Scale Fixed NII Systems is to enable CBP to perform effective and efficient Non-Intrusive Inspection (NII) of conveyances, such as passenger occupied vehicles, occupied commercial vehicles, and buses for contraband such as illicit narcotics, terrorist weapons and currency.

The LEP systems will be used for inspection of smaller vehicles such as privately owned vehicles (POV) including cars, sport utility vehicles, pickup trucks, motorcycles, commercial vans, dual-rear wheeled trucks and towed trailers, as well as larger vehicles like buses, recreational vehicles, truck tractors with empty semitrailers and trailers.

Specific configuration requirements are defined in Attachment 01b – Low-Energy Portal System Functional Requirements Document.

The MEP systems will be used for inspection of larger vehicles like buses, recreational vehicles, and truck tractors with laden semitrailers and trailers. Each system will be capable of providing an NII image with the quality and performance in accordance with this SOW and attachments to aid CBP personnel in detecting anomalies (potential contraband) within the conveyance. Specific configuration requirements are defined in Attachment 01a – Multi-Energy Portal System Functional Requirements Document.

In this Statement of Work and the related attachments, the term “Contractor” or any variant thereof refers to the prime Contractor and their personnel as well as the Contractor’s subcontractor(s) and their personnel.

1.2 Objective

The primary objective of this contract is to secure best-in-class NII equipment and systems with on-time delivery, installation, and support services necessary to meet the CBP operational requirements and mission. It is through a strong U.S. Government and Contractor partnership and communication that this important overall security objective can most effectively be achieved.

1.3 Scope

CBP has an immediate requirement for Large-Scale Fixed Systems such as LEPs and MEPs to improve its inspection of vehicles and conveyances for illegal contraband including narcotics, currency, and terrorist weapons. The volume of vehicles flowing through CBP POEs, especially along the Northern and Southwest Border, requires a mechanism that allows vehicles to be driven through the system while occupied by the driver and its passenger(s).

This Statement of Work (SOW) and related attachments define the tasks necessary to provide these LS-NII fixed systems to include equipment, delivery, installation and civil works, image formatting for ingestion in the CBP systems, testing, verification, documentation, interconnectivity within all systems, lifecycle support and warranties and logistics requirements needed to satisfy the procurement. All fixed drive-through scanning systems will be placed in a manner consistent to individual POE Concept of Operations (CONOPS) requirements as agreed upon between the Government and Contractor after initial site survey.

The IDIQ contract and the SOW, along with its sections and attachments, outline all in-scope requirements. Each Order will detail the specific services, resources, equipment, supplies, and materials the contractor needs to provide. The Order requirements will always stay within the scope of the IDIQ contract but may reduce some of the contract’s requirements (like labor qualifications or training) if the Contracting Officer (CO) approves so in writing. Any reductions will only apply to that specific Order.

2 Period of Performance The ordering period of this multiple award IDIQ contract is five (5) years. The period of performance is five years from the date of contract award.

3 Delivery Performance and delivery locations include all the relevant CBP POE (i.e. land border crossings, checkpoints, and other CBP POEs within the United States and OCONUS) which will be identified at the order level.

The contractor will provide a planned delivery schedule (S003) within 30 days of award of an Order. Delivery of systems (S004) will begin no later than sixty (60) days from the date of execution of an Order. Coordination will be made with the CBP technical points of contact (TPOC) and the Contracting Officers Representative (COR) listed in SOW Section 11.3 prior to delivery. Each system shall pass on-site operational testing prior to acceptance of each system as required in Attachment 05 – Testing Requirements.

To ensure effective management of NII system deployments, the contractor will utilize the CBP Integrated Master Schedule (IMS) provided by the Government to track progress through the established deployment process in accordance with Deliverable (S005). (1) Initial Input: The contractor will review the major deployment tasks already defined and outlined in the IMS and provide anticipated start and finish dates for each task at the outset of performance. This initial input will be treated as the vendor's baseline IMS submission. Any future IMS updates will be measured against this baseline submission. (2) Weekly status updates: The contractor is required to utilize Microsoft Project to provide weekly status updates for all ongoing projects, ensuring accurate and timely reporting of milestones, challenges, and overall progress to support CBP’s operational objectives. CBP will provide the current IMS input file each week and the Contractor will enter updates directly into the file and email them back according to the agreed-upon submission deadline. Weekly updates shall include: actual start and finish dates for completed or in-progress activities; updated forecasts for remaining work; identification of any changes to plan, including schedule variances or task re-sequencing; narrative explanation of reason for changes; identification and description of any risks, issues or dependencies that could impact planned milestones.

Furthermore, the vendor will participate in bi-weekly IMS review meetings where they will provide verbal project schedule updates to the government.

4 Invoicing

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

The contractor will electronically transmit their draft payment request to the COR at the e-mail address provided in Section 11.3, as well as to the assigned Acquisition Specialist/Program Analyst, for review prior to submitting any invoices to IPP. The COR will review the draft invoice and either approve it or reject it with corresponding feedback to the contractor within seven (7) days of receipt of the draft invoice.

Upon receiving approval of the draft invoice from the COR, the contractor shall electronically submit the final invoice to IPP. The contractor will submit final invoices to IPP on the last Monday of each month. The contractor is responsible for planning their draft invoice submissions and review timelines accordingly to ensure compliance with this schedule. Any invoices submitted to IPP without prior approval from the COR will be rejected. The IPP website address is: https://www.ipp.gov.

Invoices will include all the following information:

• 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. For example:

o Shipping notifications or Bill of Lading o Photos of civil works/installation progress o Training attendance rosters

The Government's objective is to ensure timely payment for all submitted invoices. Each invoice must be submitted independently and accompanied by all required deliverables and supporting documentation, regardless of whether they have been previously submitted to the Government through other means. Failure to include the required documentation may result in delays in invoice processing and payment.

4.1 Milestone/Progress Payment Structure

The Contractor shall be compensated based on the completion of the following milestones, subject to verification and approval by the Contracting Officer or designated representative. Payments will be made as a percentage of the total Contract Line-Item Number value upon successful completion of each milestone as outlined below:

Note: The milestone payments depicted below are notional and may be adjusted at the order level.

1. Milestone 1 – Mobilization

Covers costs such as site visit and survey, site prep, construction kick-off, mobilization of equipment, and administrative setup.

• 40% (of Site Design CLIN) Milestone Payment:

o Upon Order award to support Site Visit and Survey

• 60% (of Site Design CLIN) Milestone Payment:

o Site Survey (Site Investigation Report) completed.

o Rough Order of Magnitude submitted and accepted.

o Cost and Schedule Risk Analysis submitted and accepted.

o Construction Kick-off meeting is scheduled in accordance with this SOW and Attachment 03.

• Milestone 2 – Design and Submittals

Payment for design efforts and pre-installation planning.

• 40% (of Site Design CLIN) Milestone Payment:

o Completion and approval of the System and Conceptual Design Review o Completion and approval of the 50% Site Drawing Review

• 60% (of Site Design CLIN) Milestone Payment o Completion and approval of Issued for Construction Site Drawing with PE stamp, submittals, and design documentation.

3. Milestone 3 – Hardware

Payment for system production and acceptance.

• 80% (of Equipment CLIN) Milestone Payment:

o System production completed and Contractor Conducted System FT

Report submitted to the COR o Long-Lead items ordered (i.e. command centers) o System ready for shipment o Storage pending identification of location if necessary

• 20% (of Equipment CLIN) Milestone Payment:

o Government acceptance of system upon successful SAT and forty 40-hour burn-in period.

o The first instance of Officer Training is successfully completed.

o All required deliverables have been completed, approved, and accepted by the COR;

As-Built Drawings System Manuals Technical Documentation Package Warranty Certificates

4. Milestone 4 – Civil Works

Covers costs associated with purchasing and delivering materials and work underway.

• 80% (of Civil Works CLIN) Milestone Payment:

o All metals ordered o Electrical scope ordered o Concrete and rebar ordered o Civil works underway

• 20% (of Civil Works CLIN) Milestone Payment:

o All Civil Works efforts are complete.

4.2 General Requirements for Milestone/Progress Payments

4.2.1 Verification of Milestones:

All milestones must be verified and approved by the Contracting Officer or designated representative prior to payment. All invoices will comply with the requirements as outlined in Section 4 of this SOW.

4.2.2 Documentation:

The Contractor will provide all necessary documentation within the Monthly Progress Report (S006), for instance progress reports, inspection reports, and test results, to demonstrate milestone completion in accordance with this SOW and its attachments.

Additionally for the burn-in period, the Contractor will provide daily logs during the burn-in period documenting uptime, downtime, corrective actions, and system availability (S007). Logs will be validated by the TPOC and COR identified in Section 11.3 prior to final acceptance and payment authorization.

4.2.3 Adjustments:

The Government reserves the right to adjust milestone percentages or deliverables based on project requirements, as mutually agreed upon between the Contractor and the Contracting Officer (CO) in writing and as determined by the CO. All applicable milestone payments are subject to the contract terms and conditions.

5 Program Organization

• This procurement is under the technical direction of the Lead Business Authority

(LBA) and the Acquisition Program Manager (APM) of the Innovation and Strategy Directorate (ISD).

• The contract is managed by the Contracting Officer (CO) assigned in section

11.3 of the Border Enforcement Contracting Division and the Contracting Officer’s Representative (COR) assigned to the CBP Office of Field Operations (OFO) Mission Support Directorate (MSD) NII Program.

• The overall business owner oversight, functional requirements and deployments under this contract are managed by the Non-Intrusive Inspection Division (NIID), Logistics/Deployment Branch.

• Training is managed by the Office of Training and Development (OTD).

• Data integration and compliance is managed by the Technology Integration

Division (TID) and Border Enforcement and Management Systems Directorate (BEMSD)The maintenance, repair, and logistic support will be managed by the Integrated Logistics Division (ILD) within the OIT / Enterprises Infrastructure & Operations Directorate (EIOD), with oversight from the LBA and the APM of the

ISD.

5.1 Government Management Organization

• CBP will manage this program through the CBP OFO Acquisition, the APM, and the NII Program process with CBP OFAM support for system acquisition, delivery, and acceptance.

• The CBP Integrated Logistics Division (ILD) will manage the system(s) during the warranty and maintenance periods to include any corrective maintenance actions, preventive maintenance activities, and if needed, on-demand services as required in Attachment 06 – Lifecycle Sustainment and Support Requirements.

• CBP OTD along with NIID will approve training development and operator training presentations as required in Attachment 04 – Training Requirements.

• CBP Human Resources Management (HRM) will approve radiation safety limits.

5.2 Contractor Management Organization

Within 30 days of the contract award, the Contractor will coordinate with the CO and/or COR to schedule and conduct a Contract Kick-Off Meeting (after initial IDIQ award only;

S001). The meeting will be held at the contractor site with virtual participation options.

The Contractor will provide a meeting agenda at least 5 days prior to the scheduled meeting date. The Contractor will submit meeting minutes and action items to the COR within 3 days following the meeting (S002). The purpose of this meeting is to establish a mutual understanding of contract requirements, performance expectations, deliverables, reporting protocols and communication procedures. The Kick-Off Meeting will include, at a minimum:

• Introduction of key personnel from both the Government and Contractor teams.

• Overview of the Statement of Work (SOW).

• Discussion of contract milestones and immediate deliverables, timelines.

• Clarification of roles, responsibilities, and lines of authority.

• Overview of invoicing procedures and performance monitoring.

5.2.1 Program Management Reviews

The Contractor shall participate in Program Management Reviews (PMRs) with the Government at least quarterly throughout the period of performance. PMRs may be conducted virtually or at a Government-designated location, as directed by the COR.

The purpose of the PMRs is to assess Contractor performance, review progress against contract and Order requirements, identify and resolve risks, issues, dependencies, and open action items, and maintain a mutual understanding between the Government and Contractor regarding priorities, performance expectations, planned activities, and upcoming work.

The Contractor shall prepare and provide PMR materials to the COR no later than five

(5) calendar days before each scheduled PMR, unless otherwise directed by the COR (S008). At a minimum, PMR materials shall address:

1. Status of contract and Order performance, including progress against milestones, schedules, and deliverables;

2. Accomplishments during the reporting period and planned activities for the next reporting period;

3. Status of LS-NII system design, manufacturing, delivery, installation, testing, training, warranty, maintenance, and on-demand support activities, as applicable;

4. Integrated Master Schedule status, including schedule variances, anticipated impacts, and recovery or mitigation actions;

5. Performance metrics, quality-control results, and any performance concerns;

6. Status of identified risks, issues, dependencies, and corrective actions;

7. Status of open action items from prior PMRs; and

8. Decisions, Government support, or direction needed to support timely performance.

The Contractor shall document PMR discussions, decisions, and action items and submit PMR meeting minutes and an updated action-item tracker to the COR within five

(5) calendar days after each PMR. The Government may require additional PMRs when needed to address significant schedule impacts, performance concerns, emerging risks, or other program requirements.

5.2.2 Project Management Plan

The Contractor will develop and submit a comprehensive Project Management Plan (PMP; S009) within 14 days of the contract award. The PMP will serve as the foundational document guiding contract execution, performance monitoring, and stakeholder communication. The PMP will be submitted to the COR for review and approval. Updates to the PMP will be submitted upon the request of the Government or when significant changes occur, subject to COR approval. The Contractor will adhere to the approved PMP throughout the contract lifecycle unless otherwise directed by the Government. The PMP will include the following:

• Organizational charts depicting the role and relationships of senior program management staff.

• Duty statements for senior program management staff identifying program responsibilities and authority.

• Identification of the program manager for the effort.

• Milestone schedule highlighting all the design, manufacturing, installation, testing and training requirements as they affect the Contractor’s ability to complete the project.

• Quality Control Plan (QCP) o The Contractor will develop, implement, and maintain QCP. The QCP will address the Contractor’s methods for ensuring system performance and availability throughout the contract term. The Contractor’s quality standards will include traceable metrics, including Operational Availability (AO), and verifiable performance standards to meet SOW requirements. At a minimum, the QCP will include performance standards, monitoring, and corrective action procedures for:

1. Test procedures used in the QA process

2. Procedures, processes, and time limits to correct QC problems and incorporate improved QC results in updated QCP.

3. Operational Availability (AO): Methods to measure and achieve the required (AO) for all critical system components.

4. Parts Availability: Supply chain management processes to ensure availability of critical spare and replacement parts.

5. Parts Delivery and Staging: Strategy for delivery lead times and forward staging of parts to ensure Operational Availability within identified performance metrics of system failure.

6 Applicable Documents Documents cited will be referenced and used as called for in this SOW and related attachments.

6.1 Applicable Federal Regulations and Publications

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

• Code of Federal Regulations, 49 CFR Part 172, Subpart B, Table of Hazardous Materials and Special Provisions

• Code of Federal Regulations, 21 CFR 1020.30, Diagnostic x-ray systems and their major components

• Code of Federal Regulations, 21 CFR 1020.31, Radiographic Equipment

• United States Code, (44 USC Chapter 35), Federal Information Security

Modernization Act (FISMA) of 2014

• Office of Management and Budget (OMB) Circular A-130, Management of

Federal Information Resources, Appendix III, Security of Federal Automated Information Resources

• Office of Management and Budget (OMB) guidance M-05-24, August 5, 2005

• United States Code (5 USC 552a), The Privacy Act

• United States Code (6 USC 133), Critical Infrastructure Information Act of 2002

(Title II, Subtitle B, of the Homeland Security Act)

• Code of Federal Regulations (49 CFR Part 1520), Protection of Sensitive

Security Information

• OMB Memorandum M-05-22, August 2, 2005

• United States Code (29 USC 701 et seq.) Rehabilitation Act of 1973, as amended, Title V, Section 508

• Code of Federal Regulations (36 CFR Part 1194) Information and

Communication Technology Standards and Guidelines

• Federal Acquisition Regulation (FAR) Subpart 39.2, Information and

Communication Technology

Note: The regulations can be accessed by going to: http://ecfr.gov.

6.2 Applicable National Standards

• Human Engineering Design Criteria Standards Part 1: Project Introduction and Existing Standards, DHS S&T TSD Standards project, (NISTIR 7889)

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

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

• Federal Information Processing Standards Publication (FIPS PUB),

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

• Federal Information Processing Standards (FIPS) 199, Standards for Security

Categorization of Federal Information and Information Systems

• Federal Information Processing Standards (FIPS) 197, Advanced Encryption

Standards

• Federal Information Processing Standards Publication (FIPS PUB) Number 201-

2, Personal Identity Verification (PIV) of Federal Employees and Contractors, August 2013.

• American National Standards Institute, ANSI/IEEE N42.42, Standard Data Format for Radiation Detectors Used for Homeland Security, 2012

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

• American National Standards Institute, ANSI/HPS N43.17, Radiation Safety for Personnel Security Screening Systems Using X-Ray or Gamma Radiation, 2009

• American Society of Civil Engineers (ASCE) 7 Minimum Design Loads for Buildings and Other Structures and the International Building Code

6.3 Applicable DHS/CBP Documents, as may be amended

• DHS Sensitive Systems Policy Directive 4300A, Version 13.3, February 13, 2023,

• U.S. CBP HB 1400-05D Information Systems Security Policies and Procedures

Handbook Version 7.0 November 16, 2017

• DHS Management Directive (MD) 11042.2 (2023) Safeguarding Sensitive but

Unclassified (For Official Use Only) Information

• Homeland Security Presidential Directive-12 (HSPD-12), Policy for a Common

Identification Standard for Federal Employees and Contractors, August 2004

• Human Engineering Design Criteria Standards Part 1: Project Introduction and

Existing Standards, DHS S&T TSD Standards project, (NISTIR 7889)

• U.S. Customs and Border Protection (CBP) Cost-Wise Readiness (CWR)

Directive 5225-03 REV A

• DHS Enterprise Data Management Policy Directive 103-01, 8/25/2014

• DHS Section 508 Program Management Office and Information Technology

Accessibility MD 4010.2, 10/26/2005

• DHS Instruction 119-02-03, “DHS Workspace Standard”

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

Control Document (ICD) version 5, 2015

• CBP LPOE Design Standards 2023 rev. 1

6.4 Referenced Attachments

• Attachment 01a – Functional Requirements Document - MEP

• Attachment 01b – Functional Requirements Document - LEP

• Attachment 02a – Integration Overview

• Attachment 02b – LSX-ICD-1.0.0

• Attachment 03 – Design, Construction, and Installation Requirements

• Attachment 04 – Training Requirements

• Attachment 05 – Testing Requirements

• Attachment 06 – Life Cycle Sustainment and Support Requirements

• Attachment 07 – Deliverables

• Attachment 08 – IDIQ Pricing

• Attachment 09 – Acronyms, Abbreviations, and Definitions

• Attachment 10 – Information Technology Clauses

7 Work to be Performed The Contractor will perform all tasks within this SOW and the related attachments. The Contractor will 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 will include but are not limited to fabrication, integration, test, delivery, training, logistics, and on-demand support of LS-NII Fixed Systems.

These systems will be deployed at various CBP POEs (land border crossings, checkpoints, etcetera, along the Southwest/Northern borders) within the United States as designated by CBP. Specific sites and schedules will be identified during contract negotiations.

7.1 Requirements Definitions

All Definitions can be found in Attachment 09 – Acronyms, Abbreviations, and Definitions.

7.2 General Requirements

The Contractor will perform the work necessary to manufacture, test, deliver, and integrate the procured equipment and related data. The Contractor will also provide warranty, maintenance, logistics, and on-demand services (see Attachment 06 – Lifecycle, Sustainment and Support Requirements), initial operator training (see Attachment 04 – Training Requirements), for support of these LS- NII inspection systems. Each LS-NII system will meet the requirements defined in this Statement of Work and the related attachments.

7.3 System Requirements

CBP is seeking currently available Commercial technology. The systems shall be safe and create radiation exposure rates as low as possible according to the Nuclear Regulatory Commission (NRC) to allow for occupied vehicle inspection. The system will create a detailed image of the vehicle (from the roof of vehicle to the ground) which allows operators to quickly identify organic (narcotics, currency and explosives) and inorganic compounds (high density objects, weapons, and stowaways).

Each system will meet the requirements defined in Attachment 1a, Functional Requirements Document – MEP or Attachment 1b, Functional Requirements Document

- LEP.

The Contractor will prepare and submit monthly progress reports (S004) detailing efforts completed during the reporting period (calendar month), percent of overall completion, estimated time to completion and problems encountered with associated risk. The report period closes on the last calendar day of the month and is due on the 10th of the succeeding month. As a minimum, the report shall contain the following:

• Progress to Date

• Planned Activities: system installation, training, warranty, maintenance, on-demand services, etc.

• Deliverable Submittal Status

• Funds Expended to Date

• Current Timeline to Completion

• Program Hazards

• Open Action Items

• List of Identified Risks and Proposed Mitigation Strategies

Note: The Contractor shall continuously assess implementation and identify all risks, including risks within and outside of Contractor control, that may affect the contract schedule. Upon identification of any risks, the Contractor shall notify the COR in writing within one (1) business day. The notification shall include at a minimum, a description of the identified risk situation and any known causes.

7.3.1 Functional Requirements Documents (FRD)

Attachment 1a of this SOW details the functional requirements of the MEP, Document (FRD) use cases and associated requirements for CBP officers inspecting cargo vehicles arriving at northern and southern land border POEs throughout the United States, as well as seaport POEs and United States Border Patrol (USBP) checkpoints.

Several different MEP configurations and concepts of operation (CONOPS) are documented throughout Attachment 1a.

Attachment 1b of this SOW details the functional requirements of the LEP, the use cases and associated requirements for CBP officers inspecting POVs arriving at northern and southern land border POE throughout the United States. The COOPs addressing the pre-primary, primary and secondary scanning use cases for the passenger vehicle scanning systems are documented throughout Attachment 1b.

7.3.2 Integration Requirements

To address the increased image volume and improve operational efficiency, CBP transitioned to cloud-based architecture. This transition requires that all procured systems and components must be compliant with Attachment 02a – Integration Overview and Attachment 02b – LSX ICD 1.0.0. This shift enables the use of machine learning algorithms for image adjudication and facilitates the integration of targeting information.

7.3.3 Design, Construction and Installation Requirements

Attachment 3 to this SOW addresses design, construction, and installation processes beginning with the award of an Order and culminating in the acceptance of the LS-NII Fixed system.

7.3.4 Training Requirements

Attachment 4 to this SOW outlines the development and delivery of training for all systems and related items designed and produced under this contract. The training will cover procedures for installation, setup, operation, maintenance, and, if applicable, the use of image viewer software—depending on whether the site will utilize a common viewer.

7.3.5 Testing Requirements

The Contractor will deliver and install the equipment at the designated Government site(s) in accordance with the requirements in Attachment 5 to this Statement of Work.

Upon installation, the Contractor will conduct initial on-site testing in the presence of the Government to verify compliance with all functional and performance requirements.

Following successful completion of on-site testing, the equipment will undergo a continuous forty (40) hour burn-in period under normal operating conditions. The burn-in period will be used to validate sustained performance, reliability, and compliance with contract requirements. This testing will include confirmation that all installed equipment meets requirements for integration and data transmission.

The contractor will hold all technical reviews and quality assurance procedures as required by Attachment 5, Testing Requirements. The contractor will perform all inspections and tests required (Attachment 05, Testing Requirements) to ensure that each LS-NII Fixed Systems conform to CBP approved technical specifications and configuration specifications outlined in Attachment 01a, Functional Requirements Document – MEP and 1b, Functional Requirements Document – LEP.

7.4 Life Cycle Sustainment and Support Requirements

The contractor will provide services to ensure the reliability, availability, and maintainability of each system delivered to the Government to include warranty, corrective and preventive maintenance, and on-demand services as provided in Attachment 06, Life Cycle Sustainment and Support Requirements.

8 Deliverables Any defined products or documents defined as requirements with this SOW and its related attachments known as Deliverables, are provided in Attachment 07. The Contractor will provide all deliverables to the required points of contact in accordance with the due dates cited within the attachment.

9 Pricing Attachment 08 of this SOW will be used to submit any Request for Proposals, Quotes, and/or Rough Orders of Magnitude throughout the IDIQ period of performance.

10 Information Technology Security The Contractor will adhere to all DHS and CBP IT security policies and the basic requirements, security authorization, encryption compliance, and pass security review as required in Attachment 10, Information Technology Clauses.

11 Special Considerations

11.1 Changes to the SOW

No changes to this SOW (including related attachments) or cost increases will be incurred without written prior approval of the CO as coordinated by the COR. Any changes or cost increases will not take effect until the CO executes a written modification.

11.2 Travel

Travel may be required to support the tasks identified in this SOW.

Unless otherwise specified at the order level, the Contractor will provide all transportation associated with the movement of Contractor personnel performing work under this contract to and from the Order performance location, including:

• Transportation between such individual residence and the Order performance location upon beginning work.

• Providing and arranging for all necessary documentation and any other prerequisites for travel to the Order performance location, (e.g., visas, work permits, inoculations/immunizations, medical examinations/tests, etc.).

• Transportation throughout the areas of operation (e.g., shuttle bus services considered necessary within POE or to the performance location, etc.). Any restrictions related to Contractor-provided vehicle usage will be identified by the performance location.

• The Contractor will make all applicable travel arrangements on their own or through a commercial travel agency.

Further travel requirements and information will be provided in each individual Order.

11.3 Points of Contact.

Contracting Officer:

Name: To be identified upon award Office:

Contracting Officer's Representative:

Email:

Note: Order CORs will be separately identified upon award.

Technical POC:

Technical POC- Integration:

Acquisition Specialist / Program Analyst

Business Operations Division

ILD Ops Center

ILD MDC

ILD Maintenance Management

OTD

11.4 Subcontracting Requirements

The Contractor will directly employ all personnel providing services unless otherwise authorized by the CO.

In the event that the Contractor requires the services of subcontractors to perform any obligations under an Order, the Contractor will obtain prior written consent from the CO.

The CO is entitled to review the qualifications of and reject any Contractor-proposed subcontractor that they reasonably consider not capable or qualified to fulfill the requirements of this contract and applicable Order.

The subcontractor must meet the same vetting requirements for security clearances, vetting approvals, and public trust certifications as the prime Contractor as identified in contract and Order position requirements.

Remainder of page left intentionally blank.

1 Background

1.1 Purpose

1.2 Objective

1.3 Scope

2 Period of Performance

3 Delivery

4 Invoicing

4.1 Milestone/Progress Payment Structure

4.2 General Requirements for Milestone/Progress Payments

4.2.1 Verification of Milestones:

4.2.2 Documentation:

4.2.3 Adjustments:

5 Program Organization

5.1 Government Management Organization

5.2 Contractor Management Organization

5.2.1 Program Management Reviews

6 Applicable Documents

6.1 Applicable Federal Regulations and Publications

6.2 Applicable National Standards

6.3 Applicable DHS/CBP Documents, as may be amended

6.4 Referenced Attachments

7 Work to be Performed

7.1 Requirements Definitions

7.2 General Requirements

7.3 System Requirements

7.3.1 Functional Requirements Documents (FRD)

7.3.2 Integration Requirements

7.3.3 Design, Construction and Installation Requirements

7.3.4 Training Requirements

7.3.5 Testing Requirements

7.4 Life Cycle Sustainment and Support Requirements

8 Deliverables

9 Pricing

10 Information Technology Security

11 Special Considerations

11.1 Changes to the SOW

11.2 Travel

11.3 Points of Contact.

11.4 Subcontracting Requirements

U.S. Department of Homeland Security

Attachment 01a – Functional Requirements Document

For:

U.S. CUSTOMS AND BORDER PROTECTION

LARGE-SCALE FIXED

NON-INTRUSIVE INSPECTION SYSTEMS

Multi-Energy Portal Systems

PREPARED BY:

OFFICE OF FIELD OPERATIONS

INNOVATION AND STRATEGY DIRECTORATE

NON-INTRUSIVE INSPECTION PROGRAM OFFICE

June 9, 2026 Version 2.7

WARNING: This document is FOR OFFICIAL USE ONLY. It contains information that may be exempt from public release under the Freedom of Information Action (5 United States Code522). It is to be controlled, stored, handled, transmitted, distributed, and disposed of in accordance with the Department of Homeland Security policy relating to FOR OFFICIAL USE ONLY information and is not to be released to the public or other personnel who do have a valid “need-to-know” without prior approval of an authorized Department of Homeland Security official.

ATTACHMENT 01A – FUNCTIONAL REQUIREMENTS DOCUMENT - MEP

ii For Official Use Only

Program Signature Page

This document is an authoritative source for the content therein. The approval authorities sign this page.

Prepared by:

Systems Engineering Office Innovation and Strategy Directorate

Reviewed by:

Mindy Sawyer Technology Acquisition Portfolio Innovation and Strategy Directorate

Approved by:

Laura E. Hermosillo Date Director (A) Non-Intrusive Inspection Division iii

Table of Contents

1 Introduction

1.1 Mission Needs Statement (MNS) Gaps

1.2 System Constraints

2 MEP Configurations

2.1 MEP Configuration 1 (No RFID or QR) for BP Checkpoint or Seaport

2.2 MEP Configuration 2 (with RFID and QR) for Land Border POE

2.3 MEP Configuration 3 (Virtual Primary) for Land Border POE

3 Requirements

3.1 Requirements Definitions

3.2 Requirements Numbering

4 MEP Use Cases

4.1 MEP Use Case 1 – Border Patrol Checkpoint

4.2 MEP Use Case 2 - Seaport Inspection

4.3 MEP Use Case 3 – Land Border POE with Pre-Primary or Post-Primary Scan10

5 Functional Requirements

5.1 MEP Unit Functional Requirements

5.2 MEP Unit X-Ray System Functional Requirements

5.3 Under-Vehicle Back-Scatter System (UVBS) - Objective – Optional Contract Provision Functional Requirements

5.4 License Plate Reader (LPR) System Functional Requirements (Land Border configuration)

5.5 RFID Reader System Functional Requirements (Land Border configuration) .. 17

5.6 Optical Character Recognition (OCR) System Functional Requirements

5.7 Check-In / Staging Lane Kiosk Functional Requirements

5.8 Traffic Control System (TCS) Functional Requirements

5.9 Vehicle Sensors Functional Requirements

5.10 Closed Circuit Television (CCTV) and Camera Systems Functional Requirements

5.11 Data Storage (DS) Functional Requirements

5.12 MEP Work Center Functional Requirements

5.13 NII Control Center Functional Requirements for Local Network Deployments 21

6 Physical Requirements

6.1 MEP System Physical Requirements

iv

6.2 MEP Unit Physical Requirements

6.3 Under-Vehicle Back-Scatter System (UVBS) – Objective Physical Requirements

6.4 Check-In / Staging Lane Kiosk Physical Requirements

6.5 Traffic Control System (TCS) Physical Requirements

6.6 CCTV and Camera Systems Physical Requirements

6.7 MEP Work Center Physical Requirements

6.8 NII Control Center Physical Requirements

7 Performance Requirements

7.1 MEP System Performance Requirements

7.2 MEP Unit Performance Requirements

7.3 MEP Unit X-Ray System Performance Requirements

Note: “Test bricks” are benign test articles developed by LSS that simulate powdered narcotic tightly packaged in blocks of the dimensions and weight noted

7.4 Under-Vehicle Back-Scatter System (UVBS) Objective - Performance Requirements

7.5 License Plate Reader (LPR) System Performance Requirements

7.6 RFID Reader System Performance Requirements (Land Border

configuration)

7.7 Optical Character Recognition (OCR) System Performance Requirements

7.8 Check-In/Staging Lane Kiosk Performance Requirements

7.9 CCTV and Camera Systems Performance Requirements

8 Interface Requirements

8.1 MEP System Interface Requirements

8.2 MEP X-ray Unit Interface Requirements

8.3 Under-Vehicle Back-Scatter System (UVBS) – Objective Interface Requirements

8.4 Traffic Control System (TCS) Interface Requirements

8.5 Vehicle Sensors Interface Requirements

8.6 Data Storage (DS) Interface Requirements

9 Survivability Requirements

9.1 MEP System Survivability Requirements

9.2 MEP Unit Survivability Requirements

9.3 Under-Vehicle Back-Scatter System (UVBS) – Objective Survivability Requirements v

9.4 CCTV and Camera Systems Survivability Requirements

9.5 MEP Work Center Survivability Requirements

9.6 NII Control Center Survivability Requirements ... Error! Bookmark not defined.

10 Human Systems Integration (HSI) Requirements

10.1 MEP Unit HSI Requirements

10.2 MEP Work Station HSI Requirements

10.3 NII Control Center HSI Requirements

11 Environmental, Safety, and Occupational Health (ESOH) Requirements

11.1 MEP System ESOH Requirements

11.2 MEP Unit X-Ray System ESOH Requirements

11.3 Traffic Control System (TCS) ESOH Requirements

11.4 CCTV and Camera Systems ESOH Requirements

12 Interoperability Requirements

12.1 MEP System Interoperability Requirements

12.2 MEP Unit X-Ray System Interoperability Requirements

12.3 Under-Vehicle Back-Scatter System (UVBS) Objective - Interoperability Requirements

12.4 Vehicle Sensors Interoperability Requirements

12.5 CCTV and Camera Systems Interoperability Requirements

12.6 MEP Work Center Interoperability Requirements

13 Security & Privacy Requirements

13.1 MEP System Security & Privacy Requirements

13.2 MEP Work Center Security & Privacy Requirements

13.3 Access Control Security & Privacy Requirements

13.4 Auditing Security & Privacy Requirements

13.5 Computer Security & Privacy Requirements

13.6 Identification and Authentication Security & Privacy Requirements

13.7 Printing Security & Privacy Requirements

14 Reliability, Availability, and Maintainability (RAM)

Table of Tables vi

Table 1 NII Mission Needs Statement Gaps to be addressed by MEP Table 2 MEP System Functional Components Table 3. MEP System Environmental Conditions

MEP FRD Version 2.7 For Official Use Only Page 1

1 Introduction United States Customs and Border Protection (CBP) Office of Field Operations (OFO) facilitates legitimate trade and travel into and out of the U.S. CBP Officers must screen all incoming persons and inspect vehicles, conveyances and cargo to detect and resolve potential threats. CBP Officers stand ready to interdict terrorists and their weapons, illicit narcotics and numerous forms of contraband smuggled into the United States. CBP Officers also detect and intercept foreign nationals illegally attempting entry into the United States. In addition, CBP Officers safeguard United States agriculture from harmful animal, fruit, and vegetable diseases and foreign invasive pest species not currently in the United States.

The Multi-Energy Portal (MEP) system offers a variety of transmission and backscatter X-ray imaging capabilities/energies which allow safe scanning of occupied vehicle cabs (per ANSI 43.17 2009) and higher flux multi-energy scanning of cargo trailers and sea containers, even through dense cargo or shielding. Multi-energy transmission X-ray allows the MEP to discern varying cargo densities which can support detection of anomalies within the cargo load. MEP configurations can also include under-vehicle and multi-view backscatter imaging.

The MEP systems include ancillary system components to assist in identifying the vehicle load or conveyance. It includes either license plate reader (LPR), Quick Response (QR) code readers and Radio Frequency Identification (RFID) systems for land border applications and Optical Character Recognition (OCR) cameras for seaport containers. The MEP collects and packages image data and associates it with the specific vehicle and manifest filing metadata obtained from other CBP IT systems.

CBP is committed to enhancing its mission effectiveness in securing the nation's borders, facilitating legitimate trade, and ensuring efficient travel. Non-Intrusive Inspection (NII) technologies are critical tools in achieving these objectives, providing essential capabilities for detecting illicit goods and threats. To that end, NII intends to modernize its infrastructure to enable CBP to revolutionize how NII data is utilized, including leveraging advanced technologies such as Artificial Intelligence and Machine Learning (AI/ML). All MEP system configurations and their subcomponents shall be capable of exporting all collected image and metadata in real-time to designated CBP IT systems and authorized external platforms. Real-time data export is essential to enable advanced artificial intelligence (AI) technologies to maximize scanner utility, support automated threat detection, and enhance operational efficiency.

The Functional Requirements Document (FRD) details MEP use cases and associated requirements for use of these systems by CBP officers inspecting cargo vehicles arriving at northern and southern land border POEs throughout the United States, as well as seaport POEs and United States Border Patrol (USBP) checkpoints. Different MEP configurations and use cases are documented within this document. Each POE will be evaluated on case-by-case basis and the design, infrastructure, and installation customized to accommodate the commercial NII technologies based on the POE

MEP FRD Version 2.7 For Official Use Only Page 2 physical layout and existing infrastructure. See Attachment 03, Design, Construction, and Installation Requirements. The configurations and use cases in this document are generalized and may differ from the ones for a specific POE.

This MEP FRD is Attachment 01 to the Statement of Work (SOW) for Large-Scale Fixed Systems. Throughout this document are reference to other attachments to the overall

SOW.

1.1 Mission Needs Statement (MNS) Gaps

The NII gaps from the NII Mission Needs Statement (MNS) to be addressed by the integrated MEP System are listed in Table 2. Note that the “enhanced” CONOPS discussed in Gaps 4 and 7 are those associated with the NII-I Program and documented in the NII-I CORD.

Table 1 NII Mission Needs Statement Gaps to be addressed by MEP # Gap Description Type

1 NII Systems Integration

CBP NII imaging systems are currently not integrated with Radiation Detection Equipment (RDE), the CBP network, data center, local operational command centers nor CBP information technology enforcement applications and databases. Standalone NII large-scale systems do not support automated, efficient data exchange or real-time targeting, do not provide a consolidated threat picture for operators and do not support remote performance monitoring and system maintenance. By themselves, RPM’s [Radiation Portal Monitors] are limited in detecting radiation from well-shielded weapons or radioactive material – such threats must also be scanned for anomalies by an NII imaging system to improve threat detection.

Materiel

Primary NII Image

Scanning Capability / Capacity

Currently, NII image scanning is largely a secondary or targeted inspection process. Various operational vectors, including land border Privately Owned Vehicle (POV), truck cargo, seaports, mail, express consignment cargo, and air freight, do not perform NII scanning on a large percentage of incoming traffic / containers. The NII Program must identify and employ new, more efficient technology systems and associated CONOPs, which can offer an opportunity to greatly increase scan rates in these vectors without increasing wait times.

MEP FRD Version 2.7 For Official Use Only Page 3

# Gap Description Type

Adaptation to New

Technology and CONOPS

Newer Commercial NII technologies have the potential to improve capabilities and greatly increase NII scanning rates…