20155109_Attachment 01b - LEP System FRD_20251016.docx

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 DIVISION

October 14, 2025 Version 7.04

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.

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

Submitted by:

Kelly E. Woods Date Innovation and Strategy Directorate Office of Field Operations

Endorsed by:

Program Acquisition Executive Innovation and Strategy Directorate

Approved by:

(A) Director Non-Intrusive Inspection Division

Revision Summary

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

Table 1 Revision Table

Table of Contents

Table of Tables

70B03C21Q00000150

Large-Scale Fixed Systems

ATTACHMENT 01B – FUNCTIONAL REQUIREMENTS DOCUMENT - LEP

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.

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

0. Mission Needs Statement (MNS) Gaps The NII gaps from the NII Mission Needs Statement (MNS)[footnoteRef:2] 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). [2: CBP, “Mission Needs Statement for Non-Intrusive Inspection Program”, signed 14 August 2018.]

Table 2 NII Mission Needs Statement Gaps

Image Scanning Capability / Capacity

New Technology and CONOP

Obsolete NII Equipment

Biological, and Explosive Detection Equipment

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

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

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 Land Border Integration LBI systems and collocated with Radiation Detection Equipment (RDE). These configurations will be implemented incrementally.

1. Requirements

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

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.

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

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.

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

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.

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

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

7. Check-in or Staging Kiosk N/A

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

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

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

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

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

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

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

4. LEP Unit X-Ray System Functional Requirements

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

1. For Type 1 systems, the LEP unit shall collect a top-down transmission image (T).

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

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

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

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

1. The LEP Unit shall be capable of material discrimination using the multi-energy capability to distinguish, at a minimum, between organic (low Z}[footnoteRef:3], mix of inorganic/organic (intermediate Z) and inorganic (high Z) materials, when the organic material is surrounded by inorganic material. [3: Z = atomic number or nuclear charge number]

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

1. The LEP Unit shall distinguish between low (Z ≤ 8), intermediate (8 < 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.

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

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

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

2. If included, the UVBS backscatter X-ray should 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.

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

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

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

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

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

4. License Plate Reader (LPR) System Functional Requirements

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

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

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.

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

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

4. RFID Reader System Functional Requirements

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

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

4. LEP Traffic Control System (TCS) Functional Requirements

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

5. 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. The TCS shall control travel of the conveyance through the LEP lane until exiting.

5. 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. 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. The TCS shall not require the vehicle to stop after the scanning sequence is started.

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

5. 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. The LEP TCS shall be configured to allow vehicles to pass through the LEP Unit if the LEP Unit is disabled.

5. 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. LEP Unit failure, etc.) initiated by CBP officers in the NII Control Center.

5. The TCS shall be designed and configured for unmanned operations during standard operating scenarios.

5. 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. 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. 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. The TCS shall optimize traffic flow for all operational LEP lanes.

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

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

4. Vehicle Detection Functional Requirements

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

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

4. CCTV and Camera Systems Functional Requirements

7. The CCTV and camera systems shall provide a Fixed CCTV system for each LEP Unit.

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

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

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

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

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.

7. The CCTV and camera systems shall provide elevated surveillance PTZ cameras for wide-area situational awareness

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

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

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

4. Data Storage (DS) Functional Requirements

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

8. The LEP System DS shall store X-Ray images in an uncompressed data format.

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

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

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

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

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

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

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

8. The LEP System DS shall not over-write any previous decisions or annotations made by any analyst due to any analyst manipulations or actions at any System workstations, regardless of location.

4. LEP Work Center Functional Requirements

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

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

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

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

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

4. NII Control Center Functional Requirements

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

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

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

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

5.

5. LEP System Physical Requirements

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.

1. Printers shall be capable of color printing

5. LEP Unit Physical Requirements

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

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.

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

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

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

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

5. LEP Unit X-Ray System Physical Requirements

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

5. Under-Vehicle Back-Scatter System (UVBS) Physical Requirements

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

4. If included, the UVBS physical dimensions (length, width, depth) shall not exceed TBD.

5. LEP Traffic Control System (TCS) Physical Requirements

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

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

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

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

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.

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

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

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

5. The TCS shall include license plate readers.

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

5. The TCS shall deploy these systems prior to the first set of traffic control structures and for all bypass lanes.

5. CCTV and Camera Systems Physical Requirements

6. The Fixed CCTV system shall be a high-definition (HD) or greater CCTV for each of the LEP Units, and associated operations, that is approved by CBP.

6. 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. The LEP Unit PTZ cameras shall include cameras at the entrance and exit of each LEP Unit

6. 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. The CCTV and Camera System shall include color monitor(s).

6. The color monitors shall have HD or greater resolution

6. The color monitors shall be 32" or larger.

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

5. LEP Work Center Physical Requirements

7. The LEP workstations shall comply with DHS Instruction 119-02-03, “DHS Workspace Standard”

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

5. NII Control Center Physical Requirements

8. 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, effect an orderly shutdown in case of power failures, etc.

8. The NII Control Center shall comply with DHS Instruction 119-02-03, “DHS Workspace Standard”

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

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

1.

7.

7. LEP System Performance Requirements

1. The LEP System data shall be available to the LEP Work Center or NII Cloud in five (5) seconds (T) measured from the instant that the vehicle scan is complete.

1. The LEP System data should be available to the LEP Work Center or NII Cloud in three (3) seconds measured from the instant that the vehicle scan is complete (O).

1. The upload/download time for the LEP data elements to any node on the LEP LAN shall be one (1) second or less.

7. LEP Unit Performance Requirements

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

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

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

7. LEP Unit X-Ray System Performance Requirements

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

3. The system shall 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 50 (T) percent success.

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.

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)

Table 7 is applicable to Type 1 system with backscatter technology and Type 2 and 3 systems.

Table 7 Backscatter IQI

3. The LEP Unit shall support display of radiographic images at 4096 (T) gray levels or greater.

3. The LEP Unit should support display of radiographic images at 65,536 (O) gray levels or greater.

7. Under-Vehicle Back-Scatter System (UVBS) - Performance Requirements

4. If included, the UVBS scan speed shall be equal to or greater than the maximum LEP Unit scan speed.

4. If included, the UVBS shall meet the backscatter imaging requirements in Table 7.

7. License Plate Reader (LPR) System Performance Requirements

5. The LPR camera capture rate for image shall be 99.5% (T). Note: “Capture” is defined as recording a readable image of the license plate.

5. The LPR camera capture rate for image should be 100% (O). Note: “Capture” is defined as recording a readable image of the license plate.

5. The LPR shall read license plates with a 90.0 (T) percent accuracy of the plate alphanumeric identification and the jurisdiction in all lighting conditions (including day, night, and twilight) for all 50 U.S. states, 31 Mexican states and 12 Canadian provinces/territories. Note: Exclusions for physical obstructions or damage are not allowed.

5. The LPR should read license plates with a 95.0 (O)…