DRAFT - Attachment 01b - FRD - LEP System.pdf

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

Attachment 01b – Functional Requirements Document

For:

U.S. CUSTOMS AND BORDER PROTECTION

LARGE-SCALE FIXED

NON-INTRUSIVE INSPECTION SYSTEMS

Low-Energy Portal Systems

PREPARED BY:

OFFICE OF FIELD OPERATIONS

INNOVATION AND STRATEGY DIRECTORATE

NON-INTRUSIVE INSPECTION PROGRAM OFFICE

December 31, 2025 Version 7.05

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 Code 522). 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.

Large-Scale Fixed Systems

ATTACHMENT 01B – FUNCTIONAL REQUIREMENTS DOCUMENT - LEP

ii

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 Office of Field Operations

Reviewed by:

Mindy Sawyer Technology Acquisition Portfolio Innovation and Strategy Directorate

Approved by:

Darin Asato Date Director (A) Non-Intrusive Inspection Division iii

Revision Summary

Table 1 indicates the changes made to the document since the last release.

Table 1 Revision Table Version Date Location Description

1.00 March 2020 Washington, DC Initial Release

2.00 September 2020 Washington, DC Correct Errata

3.00 February 2023 Washington, DC Corrected Signatures

4.00 March 2023 Washington, DC Corrected Formatting

5.00 March 2023 Washington, DC Corrected Signatures and

Formatting

6.00 May 2023 Washington, DC Updated Signatures

7.00 July 2025 Washington, DC Updated with changes from

lessons learned

7.01 July 2025 Washington, DC Comments and suggested

revisions made by NII Procurement Team

7.02 September 2025 Washington, DC Revised by NII SE Team

7.03 September 2025 Washington, DC Comments adjudicated by NII SE

Team

7.04 October 2025 Washington, DC Additional revisions by NII SE

Team

7.05 December 2025 Washington, DC Adjudicated RFI comments

iv

Table of Contents

1 Introduction

1.1 Mission Needs Statement (MNS) Gaps

1.2 System Constraints

2 LEP Configurations 3 Requirements

3.1 Requirements Definitions

3.2 Requirements Numbering

4 LEP Use Cases

4.1 Inspection Use Case

5 Functional Requirements

5.1 LEP Unit Functional Requirements

5.2 LEP Unit X-Ray System Functional Requirements

5.3 Under-Vehicle Backscatter System (UVBS) Objective – Optional Contract Provision 11

5.4 License Plate Reader (LPR) System Functional Requirements

5.5 RFID Reader System Functional Requirements

5.6 LEP Traffic Control System (TCS) Functional Requirements

5.7 Vehicle Detection Functional Requirements

5.8 CCTV and Camera Systems Functional Requirements

5.9 Data Storage (DS) Functional Requirements

5.10 LEP Work Center Functional Requirements

5.11 NII Control Center Functional Requirements

6 Physical Requirements

6.1 LEP System Physical Requirements

6.2 LEP Unit Physical Requirements

6.3 LEP Unit X-Ray System Physical Requirements

6.4 Under-Vehicle Back-Scatter System (UVBS) Physical Requirements

6.5 LEP Traffic Control System (TCS) Physical Requirements

6.6 CCTV and Camera Systems Physical Requirements

6.7 LEP Work Center Physical Requirements

6.8 NII Control Center Physical Requirements

v

7 Performance Requirements

7.1 LEP System Performance Requirements

7.2 LEP Unit Performance Requirements

7.3 LEP Unit X-Ray System Performance Requirements

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

7.5 License Plate Reader (LPR) System Performance Requirements

7.6 RFID Reader System Performance Requirements

7.7 CCTV and Camera Systems Performance Requirements System Performance Requirements

8 Interface Requirements

8.1 LEP System Interface Requirements

8.2 LEP X-ray Unit Interface Requirements

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

8.4 Traffic Control System (TCS) Interface Requirements

8.5 Vehicle Detection Interface Requirements

8.6 Data Storage (DS) Interface Requirements

9 Survivability Requirements

9.1 LEP System Survivability Requirements

9.2 LEP Unit Survivability Requirements

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

9.4 CCTV and Camera Systems Survivability Requirements

9.5 LEP Work Center Survivability Requirements

9.6 NII Control Center Survivability Requirements

10 Human Systems Integration (HSI) Requirements

10.1 LEP Unit HSI Requirements

10.2 Work Center HSI Requirements

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

11.1 LEP System ESOH Requirements

11.2 LEP 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 LEP System Interoperability Requirements

12.2 LEP Unit X-Ray System Interoperability Requirements

vi

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

12.4 Vehicle Detection Interoperability Requirements

12.5 CCTV and Camera Systems Interoperability Requirements

12.6 LEP Work Center Interoperability Requirements

13 Security & Privacy Requirements

13.1 LEP System Security & Privacy Requirements

13.2 Data Storage (DS) Security & Privacy Requirements

13.3 LEP Work Center Security & Privacy Requirements

13.4 Access Control Security & Privacy Requirements

13.5 Auditing Security & Privacy Requirements

13.6 Computer Security & Privacy Requirements

13.7 Identification and Authentication Security & Privacy Requirements

13.8 Printing Security & Privacy Requirements

14 Reliability, Availability, and Maintainability (RAM) vii

Table of Tables

Table 1 Revision Table ................................................................................................................ iii

Table 2 NII Mission Needs Statement Gaps

Table 3 LEP System Functional Components

Table 4 Detectable Objects

Table 5 Concealment Locations

Table 6 Transmission Image Quality Indicators (IQI)

Table 7 Backscatter IQI

Table 8 LEP System Operational Environment

LEP FRD Version 7.04 For Official Use Only Page 1

1 Introduction United States Customs and Border Protection (CBP) Office of Field Operations (OFO) secures the lawful flow of people and goods 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. These foreign nationals are often persons deemed inadmissible by the Immigration and Nationality Act (INA) and wanted by domestic and/or international law enforcement. 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 Low-Energy Portal (LEP) is a drive-through Non-Intrusive Inspection (NII) system utilizing low radiation doses to image an occupied vehicle in motion in pre-primary, primary, and secondary scanning use cases. It provides a detailed image of the vehicle which allows operators to quickly identify anomalies (including explosives, weapons, drugs, and currency). It can be configured to scan multiple lanes of traffic. The LEP systems generally include ancillary system components to assist in identifying the vehicle load or conveyance, including license plate reader (LPR) and Radio Frequency Identification (RFID) systems. Each system shall be capable of providing a NII image with the quality to aid CBP personnel in identifying anomalies (potential contraband) within the conveyance.

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 LEP use cases and associated requirements for CBP officers inspecting Privately-Owned Vehicles (POVs) arriving at northern and southern land border Ports of Entry (POEs) throughout the United States, and United States Border Patrol (USBP) checkpoints. Different LEP configurations and concepts of operation (CONOPS) are documented throughout. Each installation will have to be evaluated on case-by-case basis to accommodate the Commercial Off-The- Shelf (COTS) NII technologies based on the physical layout and existing infrastructure.

The functional and performance requirements were derived from the NII Operational Requirements Document (ORD) and NII-Integration (NII-I) Consolidate Operational

LEP FRD Version 7.04 For Official Use Only Page 2

Requirements Document (CORD). Requirements were further informed by input from CBP officers, lessons learned from previous LEP procurements, analysis, evaluation of various commercial LEP system offerings via technology demonstrations, and prior market research.

This LEP FRD is intended to be issued as Attachment 01 of a larger Statement of Work (SOW) and contracting package. Throughout this document are references to other attachments to the overall SOW.

1.1 Mission Needs Statement (MNS) Gaps

The NII gaps from the NII Mission Needs Statement (MNS)1 to be addressed by the integrated LEP 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 Consolidated Operational Requirements Document (CORD).

Table 2 NII Mission Needs Statement Gaps # Gap Description Type

1 NII System 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, Radiation Portal Monitors (RPM) 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

2 NII System Standardization

There is a wide variety of NII original equipment manufacturer (OEM) make/model systems currently deployed by CBP which address similar operational requirements, but each requires separate training, integration and maintenance support, needlessly complicating operations and logistics. Use of multiple, different OEM systems results in multiple user interface designs, increased operations and maintenance (O&M) costs and multiple, separate sustainment contracts. System standardization will

Materiel

1 CBP, “Mission Needs Statement for Non-Intrusive Inspection Program”, signed 14 August 2018.

LEP FRD Version 7.04 For Official Use Only Page 3

# Gap Description Type promote commonality in radiographic imaging formats to lessen the analyst’s learning curve with new systems, facilitate centralized analysis with third party systems and lower O&M costs.

3 Data Networking and Integration

In tandem with #1 and #2, establish a system architecture framework, with interface standards, common data and standard interfaces, and connectivity requirements to support networking and integration of current and future sensors and incremental software improvements.

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.

Materiel

Adaptation to

New Technology and CONOP

Newer Commercial-Off-The-Shelf (COTS) NII technologies have the potential to improve capabilities and greatly increase NII scanning rates using enhanced CONOPS in pre-primary or primary inspection environments. POE facility space, layout and infrastructure are often not designed or built to accommodate these new technologies or enhanced

CONOPS.

Materiel Facilities

Aging and

Obsolete NII Equipment

Many fielded systems, approximately 27 percent of the large-scale and 35 percent of small-scale NII systems, are in need of lifecycle replacement as they have exceeded the vendor defined service life or are already functionally obsolete.

LEP FRD Version 7.04 For Official Use Only Page 4

# Gap Description Type

Chemical, Biological, and

Explosive Detection Equipment

There is a lack of NII equipment capacity and capability to detect chemical, biological, and explosive threats and hazards. Additionally, the infrastructure and physical space at many POEs is insufficient to deploy and operate CBE detection systems.

Facilities

1.2 System Constraints

1. Only active systems with generated X-ray sources will be considered.

2. Per ANSI 43.17-2009 (or latest version), potential radiation dose to vehicle occupants that exceed 25 microrem (µR) per scan will not be considered as stated in Section 11.2.

3. Any wireless communication, including Bluetooth that cannot be disabled by Administrator level operators, will not be considered.

4. Passenger vehicle scanning systems exceeding threshold limits stated in Section 11.2 will not be considered.

2 LEP Configurations CBP requires three types of low-energy drive-through portals; Type 1: Portals with a limited footprint to support high traffic volume scanning in pre/post-primary passenger vehicle operations; Type 2: Portals with a larger footprint to support secondary passenger vehicle operations; and Type 3: Portals to accommodate bus and empty commercial truck and trailer scanning operations. Each of these types of portals must be configured to meet the variations in Land Port of Entry (LPOE) physical layouts, infrastructure, and operations.

The CBP POEs range from small (one to two lanes) to large (over 30 lanes), requiring a system capable of being configured to meet the needs of the various ports, including in pre-primary, post-primary, secondary, or Border Patrol (BP) checkpoint inspection use cases. Larger LPOEs will require automated systems integrated with the CBP network and information systems to efficiently scan high volumes of traffic. The pre/post-primary systems must be capable of supporting an integrated CBP network CONOPs. Control stations may be single operator workstations networked with a single portal for a small port, or multiple portals multiplexed to multiple workstations in a large port to facilitate a high passenger vehicle throughput

Integration requirements for LEPs are specified by the type of portal. Type 1 portals are pre-primary systems integrated with the CBP network. Type 2 and Type 3 portals are pre-primary or post-primary systems that must be capable of integrating with the CBP network. The Type 2 secondary system is a baseline configuration and must be capable of supporting an integrated CBP network CONOPs.

LEP FRD Version 7.04 For Official Use Only Page 5

The requirements for specific types of systems (Type 1, 2, or 3) and configurations are defined in this document. An objective (O) configuration is a pre-primary system integrated with the CBP network and collocated with Radiation Detection Equipment (RDE). These configurations will be implemented incrementally.

3 Requirements

3.1 Requirements Definitions

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

Objective (O): An objective is considered a level of performance that significantly improves mission performance, safety, or supportability beyond that of the threshold value, and represents the maximum desired yield for system performance.

• Objective values are not required but are defined to provide guidance to the Contractor with respect to areas where increased capability is of interest 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.

• If objective values are listed, the Contractor will evaluate them to determine if they can reasonably be achieved, whether there is a cost or schedule impact, and the extent of the impact. The impact of achieving objective values will be brought to the attention of the Government for review.

Requirement Statement: This is a threshold requirement that contains a single parameter value or function.

3.2 Requirements Numbering

Each requirement in this FRD is assigned a unique ID number of the form of

XX.YY.ZZ.

• XX indicates the requirement category number.

• YY indicates the component number.

• ZZ defines the individual requirement number.

4 LEP Use Cases The LEP passenger vehicle scanning system will be used in pre-primary and post-primary CONOPs. The post-primary CONOPs is used in cases where the physical layout of the POE does not allow positioning of the LEP ahead of the primary booths (e.g., primary is too close to the border). Post-primary also provides an additional inspection tool that can be used to augment physical inspections.

LEP FRD Version 7.04 For Official Use Only Page 6

The pre-primary CONOPs utilizes technology to scan passenger vehicles prior to arriving at the primary booth providing the Primary Officer with an additional decision aid. This pre-primary CONOPs will be performing scanning and adjudicating activities prior to the passenger vehicle arriving at the primary point of inspection into the United States. This drive-through CONOPs will increase throughput enabling a higher scanning percentage of vehicles entering the U.S. and thereby increasing the probability of detecting illegal contraband entering the country to deter smuggling via passenger vehicles.

4.1 Inspection Use Case

The use case describes LPOE CBP operations when scanning inbound passenger vehicles at a land border crossing. Steps on CBP systems external to the passenger vehicle scanning system are included to provide context to the operation and to identify interfaces to CBP systems.

Use Case Pre-Condition:

1. The LEP system is ready for operation.

2. A vehicle is arriving at a POE.

Use Case Post Condition:

1. The vehicle is cleared and proceeds to exit or is referred for secondary inspection.

2. The Data Store (DS) saves the data package.

Use Case Steps

1. This system confirms the vehicle is not oversized prior to the vehicle proceeding.

2. If the vehicle chooses to opt-out of scanning, then the vehicle proceeds to the opt-out lane.

3. The system’s pre-primary License Plate Reader (LPR) captures the front license plate (LP) and front image of the subject vehicle. Note: Not all vehicles are required to have front LP.

4. The Traffic Control Indicator signals the subject vehicle to enter the passenger vehicle lane.

5. The Traffic Control Indicator signals any following vehicles to stop until the portal is clear to proceed.

6. The system captures driver and passenger(s) RFID.

7. The vehicle advances through the passenger vehicle lane and triggers the vehicle presence detection.

8. The vehicle presence detection activates vehicle scanning and starts capturing the X-ray imagery.

LEP FRD Version 7.04 For Official Use Only Page 7

9. The subject vehicle continues to move through the passenger vehicle lane at approximately 5 mph.

10. If the subject vehicle advances at a speed that could potentially expose vehicle occupants to radiation dose above 25 µR per scan, the system stops scanning.

11. If scan stops due to a slow speed (Step 10), then the data package is annotated that the “scan stopped due to slow speed.”

12. When the system detects the end of the subject vehicle:

13. System stops scanning

14. System’s LPR captures the rear LP and image.

15. The subject vehicle proceeds to next available primary lane.

16. When the subject vehicle clears the last lane sensor, the Traffic Control Indicator signals the next vehicle to enter system screening portal.

17. The LEP System creates and timestamps the data package and assigns a unique case record number. LEP System sends the data package to the Data Storage (DS).

18. The LEP data packages plus other LEP health and performance data are transmitted to the CBP network and data center/cloud.

19. The LEP data package is ‘posted’ to the LEP queue in the control booth / NII control center.

20. A LEP (Work Center) operator/analyst is automatically assigned a LEP scan image in the order scanned, which triggers the analysis process.

21. The LEP operator/analyst provides a ‘red’ suspect referral or ‘green’ non-suspect release recommendation and annotates the preliminary decision in the Government system. The LEP operator/analyst annotates the image with overlay graphics to indicate the location of the anomaly if present.

22. If ‘red,’ the LEP scan image is available to officers/agents for reference to perform follow on enforcement actions.

23. The POV pulls up to the Primary booth.

24. The Primary officer observes the vehicle, reviews documentation, interacts with the driver and passenger(s). The officer also checks the red/green referral recommendation from the image analysis. The Primary officer makes a decision to either refer the POV for further inspection (i.e., Secondary) or allow entry into the U.S.

25. The Primary officer inputs the decision into the Government system.

26. The Primary officer either directs the POV to proceed to the exit gate, or

Secondary inspection area for further investigation.

LEP FRD Version 7.04 For Official Use Only Page 8

27. The use case ends when the POV either proceeds to the POE exit or is detained for further inspection.

5 Functional Requirements Table 3 list the major components of the LEP system. Besides these major components the system also includes additional associated hardware and software elements. Note that to keep the numbering consistent with the Multi-Energy Portal (MEP) FRD, some components that are listed in the table are Not Applicable (N/A) to the LEP.

Table 3 LEP System Functional Components Component Functional Component Description

1. LEP Unit The LEP Unit refers to the systems and subsystems, which are installed in one traffic lane to execute the full scanning operation. The LEP system is a drive-through, low-energy X-ray system. The LEP system shall include integrated RFID transponder reader and LPR for use at LPOE, to uniquely identify the LEP data package for the specific vehicle/container being scanned. The LPOE drive-through systems may include as options an integrated Backscatter or Under Vehicle Back-Scatter system (UVBS).

2. LEP Unit X-Ray System

X-ray scanning system capable of providing images and material characterization of the POV, occupants, and contents. As an option, the LEP Unit X-ray may include a backscatter X-ray system (in addition to primary transmission X-ray system).

3. Under-Vehicle Back- Scatter System (UVBS)

- Objective – Optional Contract Provision

Backscatter X-ray scanning system capable of providing images of the undercarriage of vehicles.

4. License Plate Reader (LPR) System (Land Border configuration)

Identification system that uses OCR technology to read the front and rear license plates of the POV. Provides jurisdiction (e.g., state, province) and plate alphanumeric ID.

5. RFID Reader System (Land Border configuration)

Identification system that uses RF signals to read passive (backscatter) transponders (tags) of the driver and/or passenger(s) if enrolled a trusted partner program (e.g., NEXUS, SENTRI) that provides expedited screening and clearance.

6. Optical Character Recognition (OCR) System

N/A

7. Check-in or Staging Kiosk

N/A

8. Traffic Control System

(TCS)

The Traffic Control System (TCS) will ensure the efficient and effective flow of traffic without negatively impacting the overall flow of vehicles through the POE. This capability may include lights, signage, control arms, pavement striping, lane barriers, and other elements as required (to the extent possible, these elements should be customer serviceable). The TCS shall

LEP FRD Version 7.04 For Official Use Only Page 9

Component Functional Component Description be integrated with LEP operation. It will include a traffic/lane controller to automatically and actively guide traffic through the system steps and manage lane closures, LEP system outages, etc., with operator or smart queuing system input.

9. Vehicle Detection System used to detect the presence of vehicles in a specific position in a lane. Examples include inground inductive loops or break-beam sensors.

10. Closed-Circuit Television (CCTV) and Camera Systems

Closed-circuit television (CCTV) systems used for surveillance. Has the capability to record and view video. Uses pan-tilt-zoom (PTZ) video cameras.

11. Data Storage (DS) Local computer data storage to preserve images and data packages.

12. LEP Work Center Workstations where CBP officers and agents can view and enhance (e.g., zoom, contrast) X-ray images to look for the presence of anomalies that would warrant further inspection of vehicles or cargo.

13. NII Control Center The NII Control Center allows for remote operational control of the LEP System. Remote control includes the operation of the LEP Unit(s), the traffic control system, required communications to support the workflow, situational awareness (CCTV system displays), and any other requirements to fully operate the LEP System and perform analysis of LEP data. In some secondary locations, the control center can be a simple operator / analyst booth located adjacent to the LEP system. In other applications, it can be a stand-alone facility or dedicated office space within an existing POE or regional facility. Within the control center, there can be one or more work centers, consisting of LEP operator / analysis workstations and an associated CBP networked workstation hosting law enforcement applications such as ACE-TMM, TECS, etc.

5.1 LEP Unit Functional Requirements

The LEP Unit refers to the systems and subsystems which are installed in one traffic lane or one inspection/scanning area to make up the full scanning operation.

5.1.1 The LEP Unit shall be designed and configured for operation from the LEP Work Center or NII Control Center.

5.1.2 For Type 1 and Type 2 systems, the LEP Unit, including all associated equipment, shall accommodate vehicles up to 9’ 0" in height (T)

5.1.3 For Type 1 and Type 2 systems, the LEP Unit, including all associated equipment, shall have a tunnel width that is at least 9’ 0" wide (T).

5.1.4 For Type 3 systems, the LEP Unit, including all associated equipment, shall accommodate vehicles up to 14’ 6" in height (T)

LEP FRD Version 7.04 For Official Use Only Page 10

5.1.5 For Type 3 systems, the LEP Unit, including all associated equipment, and shall have a tunnel width that is at least 12’ 0" wide (T).

5.1.6 For Type 3 systems, the LEP Unit, including all associated equipment, should accommodate vehicles up to 15’ 0" in height (O).

5.2 LEP Unit X-Ray System Functional Requirements

5.2.1 The LEP unit shall use active X-Ray technology.

5.2.2 For Type 1 systems, the LEP unit shall collect a top-down or bottom-up transmission image (T) Top-down is preferred.

5.2.3 For Type 1 systems, the LEP unit should collect a backscatter image (O).

5.2.4 The LEP unit shall start scanning when the vehicle enters the portal.

5.2.5 The LEP unit shall stop scanning when the subject vehicle exits the scanning area.

5.2.6 The LEP unit shall display the entire length of the vehicle (front to end of last trailer), from the ground to the roof for the side views and the complete length and width of the vehicle for the top-down view or bottom-up view.

5.2.7 The LEP Unit shall be capable of material discrimination using the multi-energy capability to distinguish, at a minimum, between organic (low Z}2, mix of inorganic/organic (intermediate Z) and inorganic (high Z) materials.

5.2.8 The LEP Unit shall allow the operator-analyst to toggle material discrimination colors on and off.

5.2.9 The LEP Unit shall distinguish between low (Z ≤ 10), intermediate (10 < Z < 20), and high (Z ≥ 20) materials using different colors for their display. Material categories are to be color-coded as follows: low (orange), intermediate (green) and high (blue) (T).

Shades of these colors are to be used to indicate thickness. All colors should be in compliance with the Unified File Format, Version 3.

5.2.10 The LEP Unit should distinguish Heavy Metals (Z ≥ 30) (Color not defined by CBP) (O).

2 Z = atomic number or nuclear charge number

LEP FRD Version 7.04 For Official Use Only Page 11

5.2.11 The Type 2 and 3 systems shall display six images of the conveyance using both transmission and backscatter technologies: top-down, both sides in transmission and backscatter.

5.3 Under-Vehicle Backscatter System (UVBS) Objective – Optional Contract Provision

5.3.1 If included, the UVBS backscatter X-ray shall be integrated into the scanning operation of the LEP Unit to perform high resolution scan of the undercarriage of a standard width vehicle and variable under-vehicle heights.

5.3.2 If included, the UVBS shall automatically begin operation when the vehicle triggers the system that the scanning run has begun.

5.3.3 If included, the UVBS shall stop capturing undercarriage imagery when the subject vehicle exits the scanning area.

5.3.4 If included, the UVBS scan image shall be spatially aligned with the LEP X-ray (transmission / backscatter) scan images.

5.3.5 If included, the UVBS system shall include an automated means to be kept free of obstructions (dust/debris) at all times to ensure the acquisition of X-ray image for each inspection.

5.3.6 If included, the UVBS system shall capture the complete undercarriage.

5.4 License Plate Reader (LPR) System Functional Requirements

5.4.1 The LPR system shall be capable of reading a single front license plate and a single rear license plate, where the license plates comply with American Association of Motor Vehicle Administrators (AAMVA) License Plate Standard, Edition 3 (or latest standard)

5.4.2 The LPR system shall provide a broad image of the front and rear areas of the vehicle, which can be used to confirm the accuracy of the optical characters.

5.4.3 The LPR shall create an alert if the front license plate is missing or not detected. Note that some jurisdictions do not require front plates

5.4.4 The LPR shall validate that the rear license plate matches the front license plate.

5.4.5 The LPR shall create an alert if the front and rear license plates do not match.

LEP FRD Version 7.04 For Official Use Only Page 12

5.5 RFID Reader System Functional Requirements

5.5.1 The RFID system shall be capable of reading GEN 2 RFID tags, per ISO-18000-63 version 2 specification, Information Technology

- Radio Frequency Identification for Item Management - Part 63 with EPC Global / GS 1 GDTI-96 tag format.

5.5.2 The RFID system shall filter out non-DTOPS tags based on CBP defined header in memory bank #1 EPC Global / DTOPS registration number.

5.6 LEP Traffic Control System (TCS) Functional Requirements

5.6.1 The TCS shall ensure the efficient and effective flow of traffic without negatively impacting the overall flow of vehicles through the POE.

5.6.2 The TCS shall include positive control of each conveyance before entering the LEP lane. Positive control of the traffic system is the point at which a driver is forced to proceed through the LEP system while being directed by lights, signage, control arms, etc.

5.6.3 The TCS shall control travel of the conveyance through the LEP lane until exiting.

5.6.4 The TCS shall control the area after the scan to allow the conveyance the proper stopping distance including the post-LEP staging lane area, as applicable.

5.6.5 If required due to traffic congestion, the TCS shall allow the vehicle to safely come to a stop after fully exiting the LEP Unit.

5.6.6 The TCS shall not require the vehicle to stop after the scanning sequence is started.

5.6.7 The TCS shall be capable of directing traffic for driver opt-outs and oversize vehicles.

5.6.8 The TCS shall control traffic flow when exception conditions occur. Note: Examples of exception conditions are: Lane Closure (e.g. disabled vehicle); Response to emergency conditions either by CBP Officers or by other emergency services.

5.6.9 The LEP TCS shall be configured to allow vehicles to pass through the LEP Unit if the LEP Unit is disabled.

5.6.10 The TCS shall be configured to include pre-set, automatic traffic pattern sequences to accommodate standard and non-standard traffic patterns and exception conditions (e.g. All lanes open, reduced number of lanes, specific lane closes, etc.) initiated by CBP officers in the NII Control Center.

LEP FRD Version 7.04 For Official Use Only Page 13

5.6.11 The TCS shall be designed and configured for unmanned

operations during standard operating scenarios.

5.6.12 The TCS shall be designed and configured for unmanned

operations for identifiable non-standard operating conditions such as a LEP Unit not being available for scanning.

5.6.13 The TCS shall verify that the vehicle is not oversized (height and width) prior to arriving at the Traffic Control Indicator using mechanical or electronic means.

5.6.14 The TCS shall take inputs from lane capacity at the primary booth and other sensors to automatically assign trucks to LEP lanes, bypass lanes, or specific booths to maximize throughput and maintain optimal primary operations.

5.6.15 The TCS shall optimize traffic flow for all operational LEP lanes.

5.6.16 The TCS shall include logic-based routing to optimize traffic flow.

5.6.17 The TCS shall be configured to maximize throughput for all operational LEP lanes and provide CBP Officers with the ability to actively route traffic past the LEPs when necessary to maintain optimal primary operations.

5.7 Vehicle Detection Functional Requirements

5.7.1 The LEP Unit(s) shall detect the presence (or absence) of vehicles in the LEP lane.

5.7.2 The LEP Unit(s) shall measure the vehicle’s instantaneous speed to the nearest 0.1 MPH from 0 to 15 MPH as it approaches and passes through each LEP Unit.

5.8 CCTV and Camera Systems Functional Requirements

5.8.1 The CCTV and camera systems shall provide a Fixed CCTV

system for each LEP Unit.

5.8.2 The Fixed CCTV system shall capture live video of vehicles traveling through the LEP Units.

5.8.3 The Fixed CCTV system shall provide full 360-degree coverage of the LEP Unit operating area.

5.8.4 The CCTV and camera systems shall provide PTZ cameras for each LEP Unit.

5.8.5 PTZ cameras positioned at the entrance and exit of each LEP

Unit shall provide sufficient resolution and image quality to permit qualitative descriptions (make, model, color and length) of all and vehicles that pass through the LEP.

LEP FRD Version 7.04 For Official Use Only Page 14

Note: The CBP Border Security Deployment Program (BSDP) has established an approved specification for surveillance video cameras and recording called CAVSS. Any camera covering interactions between CBP officers and drivers must comply with CAVSS requirements.

5.8.6 The CCTV and camera systems shall provide elevated

surveillance PTZ cameras for wide-area situational awareness

5.8.7 The surveillance PTZ cameras shall have the capability to focus using pre-programmed presets.

5.8.8 All camera views (CCTV, LEP PTZ, surveillance PTZ) shall be automatically recorded.

5.8.9 The CCTV and camera systems shall be capable of providing screenshots at any time.

5.9 Data Storage (DS) Functional Requirements

5.9.1 The LEP System Data Storage (DS) shall store the data

packages (including X-ray images, IDs, and metadata) sent to the NII Control Center or Cloud.

5.9.2 The LEP System DS shall store X-Ray images in an

uncompressed data format.

5.9.3 The LEP System DS shall retain raw X-Ray image data for each data package in addition to any proprietary / processed X-Ray image format.

5.9.4 The LEP System DS stored images shall retain the full dynamic gray-level range of the X-Ray image

5.9.5 The LEP System DS shall store data packages for a rolling first-in first-out period of thirty (30) days.

5.9.6 The LEP System DS shall support operator-defined queries, including standard reports for scans performed, scans per day / per analyst and other Government defined metrics

5.9.7 The LEP System shall provide an option at the Administrator level for auto delete of files that are over 30 days old.

5.9.8 The LEP System DS shall have a full capacity backup system that is configured to automatically backup files at designated intervals

5.9.9 The LEP System DS shall delete oldest data packages to restore room for new packages when storage reaches 99% of its maximum storage capacity.

5.9.10 The LEP System DS shall not over-write any previous decisions or annotations made by any analyst due to any analyst

LEP FRD Version 7.04 For Official Use Only Page 15 manipulations or actions at any System workstations, regardless of location.

5.10 LEP Work Center Functional Requirements

5.10.1 The LEP Work Center(s) shall allow all the required functions to fully adjudicate the X-ray images.

5.10.2 The LEP Work Center(s) shall provide the ability to do the following: enhance the image(s), change the magnification, select different color palettes, optimize the image’s contrast and brightness, sharpen the image, highlight potential areas of interest, annotate the file for secondary inspection, input decisions on shipment adjudication and perform other standard and required operations to meet the objective of detecting contraband and anomalies.

5.10.3 The LEP Work Center(s) shall display complete images free of vertical or horizontal lines, any noise and any data or corruption that may confuse or hinder the operators’ display, i.e., missing or incomplete data such as partial vehicle scans. This requirement is intended to present images of the entire vehicle, free of noise and garbage.

5.10.4 The System shall display the username and local time with the image and the data package.

5.10.5 The System shall tag each scan analysis with the username who conducted it.

5.11 NII Control Center Functional Requirements

5.11.1 Supervisors in the NII Control Center with Administrator accounts shall remotely control the LEP System.

Note: Remote control includes full remote operations for the system including the operation of the LEP Unit, NII Control Center Situational Wall (SW), the traffic control system, any required communications to support the work flow, situational awareness (CCTV system displays), and any other requirements to fully operate the LEP System.

5.11.2 The NII Control Center SW shall include two (2) scan Queues on separate monitors as described below: a) Primary scan queue shall be displayed on a screen for the un-adjudicated scans from the LEP Units. b) Secondary scan queue shall be displayed on a screen for all shipments which are ‘red lighted’ and referred for secondary examination.

LEP FRD Version 7.04 For Official Use Only Page 16

5.11.3 For each LEP Unit, the NII Control Center SW video wall shall allow display for each CCTV / PTZ system so that the images associated with each LEP unit (lane) are easily identified.

6 Physical Requirements Physical requirements include those covering components, dimensions, and installation.

6.1 LEP System Physical Requirements

6.1.1 The LEP System shall include computers and server(s) with enough memory, speed and other features to meet all the requirements of this FRD and supporting contract SOW / references.

6.1.2 Printers shall be capable of color printing

6.2 LEP Unit Physical Requirements

6.2.1 The LEP Unit shall operate whether installed in a pre-primary, post-primary or secondary position.

6.2.2 For Type 1 systems, the LEP Unit shall be able to be installed within a defined footprint no wider than 14 feet and no longer than 20 feet and no higher than 15 feet (T). These dimensions do not include any fencing or shielding walls and other auxiliary equipment or exit distance.

6.2.3 For Type 2 systems, the LEP Unit shall be able to be installed within a defined footprint no wider than 24 feet and no longer than 24 feet and no higher than 15 feet (T). These dimensions do not include any fencing or shielding walls and other auxiliary equipment or exit distance.

6.2.4 For Type 2 systems, the LEP Unit should be able to be installed within a defined footprint no wider than 16 feet and no longer than 20 feet and no higher than 15 feet (O). These dimensions do not include any fencing or shielding walls and other auxiliary equipment or exit distance.

6.2.5 For Type 3 systems, the LEP Unit shall be able to be installed within a defined footprint no wider than 29 feet and no longer than 27 feet and no higher than 21.5 feet (T). These dimensions do not include any fencing or shielding walls and other auxiliary equipment or exit distance.

6.2.6 For Type 3 systems, the LEP Unit should be able to be installed within a defined footprint no wider than 20 feet and no longer than 22 feet and no higher than 21.5 feet (O). These dimensions do not include any fencing or shielding walls and other auxiliary equipment or exit distance.

LEP FRD Version 7.04 For Official Use Only Page 17

6.3 LEP Unit X-Ray System Physical Requirements

6.3.1 For Type 2 and 3 systems, the side view shall include from the ground to the roof without ramps or raised platforms.

6.4 Under-Vehicle Back-Scatter System (UVBS) Physical Requirements

6.4.1 If included, the UVBS shall be flush mounted with the road.

6.4.2 If included, the UVBS physical dimensions (length, width, depth) shall not cause an increase LEP lane dimensions beyond what is stated in Section 6.3.

6.5 LEP Traffic Control System (TCS) Physical Requirements

6.5.1 The TCS shall cover all lanes leading into or bypassing the LEP

Units and to the agreed upon distances before and after the LEP Units.

6.5.2 As applicable, the TCS controller shall be centrally located in the NII Control Center with a separate operating workstation.

6.5.3 The TCS shall be located and configured to allow a vehicle to achieve required minimal scan speed prior to entering the LEP Unit scan tunnel.

6.5.4 The TCS should achieve the traffic control goals without the use of gate arms (O).

6.5.5 The TCS shall have mechanical barriers to restrict oversized conveyances defined by height and/or width (6.2.2 to 6.2.6) prior to entering the LEP lane to prevent collision damage to the LEP Unit.

6.5.6 The TCS shall include active signage for all lanes to direct vehicles to open LEP lanes or past the LEP lanes when necessary.

6.5.7 The TCS shall include active signage for all lanes after the LEP to direct vehicles to open primary lanes.

6.5.8 The TCS shall include a minimum of one bypass lane for every three LEP lanes to ensure sufficient bypass capacity.

6.5.9 The TCS shall include license plate readers.

6.5.10 The TCS shall have sufficient infrastructure (power and fiber) to support additional technologies, such as facial recognition cameras, touch screen monitors, and other future systems.

Refer to the SOW for additional details.

6.5.11 The TCS components shall be physically installed in locations that ensure requirements in Section 5.6.2 are met.

LEP FRD Version 7.04 For Official Use Only Page 18

6.6 CCTV and Camera Systems Physical Requirements

6.6.1 The Fixed CCTV system shall be a high-definition (HD) or greater

CCTV for each of the LEP Units, and associated operations, that is compliant with CBP CAVSS and approved by CBP BSDP.

6.6.2 The LEP Unit PTZ cameras shall be placed to allow for viewing of the license plates of the vehicle and provide enough range to view the vehicle and occupants.

6.6.3 The LEP Unit PTZ cameras shall include cameras at the

entrance and exit of each LEP Unit

6.6.4 The Elevated PTZ cameras shall be attached to one or more LEP Units to provide for full situational awareness of the traffic lanes leading up to the LEP Units and the lane areas between the LEP Units and the Primary Booths.

6.6.5 The CCTV and Camera System shall include color monitor(s).

6.6.6 The color monitors shall have HD or greater resolution

6.6.7 The color monitors shall be 32" or larger.

6.6.8 The LEP System shall include Network Video Recorder (NVR) with a minimum 30-day recording capability capable of playing back any camera view.

6.7 LEP Work Center Physical Requirements

6.7.1 The LEP workstations shall comply with DHS Instruction 119-02-

03, “DHS Workspace Standard”

6.7.2 The LEP workstation monitors (excluding the Government

workstation) shall be a minimum of 40” in size or the images may be compiled on a large screen (50+”) which provides images of the same equivalent size.

6.8 NII Control Center Physical Requirements

6.8.1 The NII Control Center shall include an administrative work space, where a supervisor with Administrator account can manage workload situations, emergencies, respond to system alarms (e.g. gate-arm crash), activate and deactivate LEP lanes, effecting an orderly shutdown in case of power failures, etc.

6.8.2 The NII Control Center shall comply with DHS Instruction 119-02- 03, “DHS Workspace Standard”; and 2023 CBP LOPE Design Standards and CBP security requirements and CBP OIT requirements.

6.8.3 The NII Control Center SW shall include one (1) HD or greater resolution screen TV for monitoring news and weather channels.

LEP FRD Version 7.04 For Official Use Only Page 19

7 Performance Requirements General performance relates to quantity, speed, and other general performance characteristics of the system.

7.1 LEP System Performance Requirements

7.1.1 The LEP System data shall be available to the LEP Work Center in five (5) seconds (T) after the truck scan is complete.

7.1.2 The LEP System data should be available to the LEP Work

Center in three (3) seconds after the truck scan is complete (O).

7.1.3 The LEP System date shall begin to upload to the CBP Network in two (2) seconds (T) after the truck scan is complete.

7.1.4 The LEP System data should be available to the LEP Work

Center or NII Cloud in one (1) second after the truck scan is complete (O).

7.2 LEP Unit Performance Requirements

7.2.1 The LEP Unit shall scan conveyances traveling with speeds of 2 to 10 MPH.

7.2.2 For Type 1 pre/post primary systems, the LEP Unit shall have a minimum throughput of 100 (T) vehicles per hour.

7.2.3 For Type 2 and 3 secondary and bus systems, the LEP Unit shall have a minimum throughput of 20 (T) vehicles per hour.

7.3 LEP Unit X-Ray System Performance Requirements

7.3.1 The LEP system shall display radiographic images free of vertical or horizontal lines or any noise, and not missing any data that may hinder the operators clear view of the message (i.e., missing or incomplete data) such as partial vehicle scans.

7.3.2 The system shall display radiographic images of sufficient quality to enable a trained CBP officer to identify the objects described in Table 4 Detectable Objects concealed in any of the locations listed in Table 5 Concealment Locations with a minimum success rate of 50 (T) percent.

7.3.3 The system should display radiographic images with the quality for a system trained CBP officer to discriminate the object described in Table 4 Detectable Objects concealed in any of the locations listed in Table 5 Concealment Locations with at least 95

(O) percent success.

LEP FRD Version 7.04 For Official Use Only Page 20

Table 4 Detectable Objects

Table 5 Concealment Locations

Table 6 is applicable to Type 1, 2, or 3 systems.

Table 6 Transmission Image Quality Indicators (IQI) Requirement Type 1 Type 2 Type 3

7.2.5 The system shall

penetrate X (mm) of steel in accordance with test procedure in ANSI 42-46- 2008.

19 (T) 19 (T) 19 (T)

7.2.6 The system should

penetrate X (mm) of steel in accordance with test procedure in ANSI 42-46- 2008.

65 (O) 65 (O) 65 (O)

7.2.7 The system’s

radiographic images shall discriminate object to background density by at least X (%) in accordance with test procedure in ANSI 42-46- 2008.

5% (T) 5% (T) 5% (T)

Item Description Dimensions Density

1 Narcotic 8” x 5.5” x1.5” 0.74 to 1.5 g/cm3

2 Handgun 185 mm x 128 mm (7.28” x 5.04”) 7.8 g/cc3

Item Location System Type 1, System Type 3

1 Doors X

2 Rear Seat X Passenger Seats

3 Fuel Tank X X

LEP FRD Version 7.04 For Official Use Only Page 21

Requirement Type 1 Type 2 Type 3

7.2.8 The system’s

radiographic images should discriminate object to background density by at least X (%) in accordance with test procedure in ANSI 42-46- 2008.

3% (O) 3% (O) 3% (O)

7.2.9 The system’s horizontal

spatial resolution shall be less than X (mm) in accordance with test procedure in ANSI 42-46-2008.

6 (T) 9 (T) 10 (T)

7.2.10 The system’s horizontal

spatial resolution shall be less than X (mm) in accordance with test procedure in ANSI 42-46-2008.

2 (O) 6 (O) 6 (O)

7.2.11 The system’s vertical

spatial resolution shall be less than X (mm) in accordance with test procedure in ANSI 42-46-2008.

8 (T)…