Revised FRD.pdf

Page i

Low Energy Drive-Through System

Functional Requirements Document (FRD)

March 2021

Version 3.00

Developed by:

Customs and Border Protection (CBP)

Office of Field Operations (OFO)

Cargo and Conveyance Security (CCS)

Non-Intrusive Inspection Division (NIID)

Non-Intrusive Inspection Program Managment Office (NII PMO)

U.S. Customs and Border Protection

Low Energy Drive-Through System Functional Requirements Document

Page ii

Revision Summary The following Table 1 Revision Table 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 March 2021 Washington, DC Offerer Comments

Page iii

Table of Contents

1 Introduction

Mission Needs Statement (MNS) Gaps

System Constraints

2 Configurations

3 Passenger Vehicle Scanning System Use Cases

Inspection Use Case

Control Center Analysis Use Case

Secondary Use Case

4 Requirements

Behavioral Requirements

Structural Requirements

Supportability Requirements

Access Control

Auditing

Printing

Environmental Requirements

System Performance Parameters

5 Acronym List

6 Glossary

7 Availability and Maintenance Definitions

Availability

Table of Figures Figure 1 Passenger Vehicle Scanning System - Perform Operations Use Cases Figure 2 System Decomposition

Page iv

Table of Tables

Table 1 Revision Table ............................................................................................................................... ii Table 2 NII Mission Needs Statement Gaps Table 3 Passenger Vehicle Scanning System - Stakeholders Table 4 Image Data Set (IDS) Content Table 5 Detectable Objects Table 6 Concealment Locations Table 7 Transmission Image Quality Indicators (IQI) Table 8 Reflective IQI Table 9. System Operational Environment Table 10. Performance Parameters

1 Introduction The U.S. Customs and Border Protection (CBP), based upon operational needs, has an immediate requirement to inspect vehicles for illegal contraband including narcotics and terrorist weapons. Because of the volume of vehicles flowing through the Ports of Entry, a system that allows vehicles to be driven through the system by the vehicle’s driver and with vehicle occupants still inside is required. The Non Intrusive Inspection (NII) Program Mission Needs Statement (MNS) and Integrated NII Preliminary CONOPS provides the Pre-Primary and secondary scanning use cases for the Passenger Vehicle scanning system used to derive the functional and performance requirements documented herein. The use cases and requirements were further refined with input from CBP Officers and insights gained from the Pre-Primary POV Screening System (P3S) Marketing Research Report. This FRD documents the functional and performance requirements for three categories of low energy drive through NII Type Systems: Type 1. Pre/Post primary Passenger vehicle scanning system; Type 2. Secondary Passenger vehicle scanning system; Type 3. Bus/Truck Tractor Semi Trailer scanning system.

CBP’s Office of Field Operations (OFO) secures the orderly flow of people and goods into and out of the U.S., while facilitating legitimate trade and travel. The purpose of these systems is to enable CBP to perform effective and efficient Non-Intrusive Inspection of conveyances, including passenger occupied vehicles and Buses to detect contraband such as illicit drugs, terrorist weapons, and currency. These 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 and larger vehicles like buses, recreational vehicles, buses, and truck tractors with empty semitrailers and trailers. Each system shall be capable of providing a NII image with the quality identified within the performance requirements in section 4.2.0.1 of this FRD to aid CBP personnel in identifying anomalies (potential contraband) within the conveyance. In addition, CBP Officers safeguard U.S. agriculture from harmful animal, fruit, and vegetable diseases and foreign invasive pest species not currently in the US.

Mission Needs Statement (MNS) Gaps This FRD is derived from the operational analysis, the Integrated NII Preliminary POV CONOPS, the MNS, and Market Research. Below in Table 2 NII Mission Needs Statement Gaps are the NII Gaps addressed by the System.

Table 2 NII Mission Needs Statement Gaps # Gap Description Type

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.

Material

# Gap Description Type

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

Material

11 Aging and Obsolete NII Equipment

Many fielded systems, approximately 27 percent of 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.

Material

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

Material Facilities

System Constraints

a. Only active systems with generated X-Ray sources will be considered.

b. Per ANSI 43.17, potential radiation dose to vehicle occupants that exceeds 25 µrem per scan shall not be considered. 4.3.1.4

c. Any wireless communication, including Bluetooth that cannot be disabled by Administrator level operators, will not be considered. (Based on DHS 4300A Sensitive Systems Handbook)

d. Passenger vehicle scanning systems

1. Type 1 and 2 systems: Pre-Primary, Post Primary and Secondary Passenger Vehicle

Scanning Systems tunnel shall be no less than 9 ft. high x 9 ft. wide. 4.2.2.1

2. Type 1 systems: Pre-Primary, Post Primary Passenger Vehicle Scanning Systems footprint area for a single lane shall not exceed 14 ft. (T)/ 12 ft. (O) width x 20 ft. (T) / 14 ft. (O) length. Error! Reference source not found. and 4.2.2.2.1 Note: the system includes scanning sensors, sensor support, cameras, and electronics and any shielding walls inherent to the design to meet 4.2.2.6.1. Ancillary equipment in section 4.2.1, 4.2.3, 4.2.4 and USS in section 4.2.5 is excluded from this requirement.

3. Type 2 systems: Secondary Passenger Vehicle Scanning Systems footprint area shall not exceed 24 (T) 16 (O) feet wide by 24 (T) 20 (O) feet long, and 15 (T) feet high.

4.2.2.3

e. Type 3 systems: Bus/Truck low energy systems

1. Bus/Truck low energy systems shall tunnel shall be no less than 14 ft 6 in (T) 15 ft

(O) high x 12 ft (T) wide. 4.2.2.6

2. Bus/Truck low energy systems footprint shall not exceed 29 (T) 20 (O) ft wide by 27 (T) 22 (O) ft long, and 21 ft 6 in (T) high. 4.2.2.7

2 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 and top down and side views to support secondary passenger vehicle operations;

and Type 3. Portals to accommodate Bus and Truck/Semi-Trailer scanning operations. Each of these types of portals must be configured to meet the variation in Land Port of Entry (LPOE) operational requirements. CBP POEs range from small (one to two lanes) to large (over 34 lanes) and require systems capable of being configured to meet the needs of the port. 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 system must be capable initially of supporting a non-integrated CBP network post- primary CONOPS, with the eventual goal of an integrated CBP nework pre-primary 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. The final configuration is a pre-primary system integrated with Radiation Detection Equipment (RDE) and CBP Land Border Integration (LBI) systems. These configurations will be implemented incrementally. Requirements for specific types of portals are specifically designated for the type of portal. The initial baseline configuration for all portal types will be a post-primary configuration on a private network, isolated from the CBP network. Type 1 configuration one

(1) is a pre-primary system, integrated with the CBP network and the Land Border Integration (LBI) interface. Type 2 and Type 3 configuration one (1) are secondary systems integrated with the CBP network. Configuration two (2) includes Type 1, 2, and 3, systems integrated with RDE Alarms. This document includes the requirements for types of systems and all configurations. Requirements for specific types of systems are annotated with the type, requirements for a specific configuration are annotated with a (1) following the requirement. Requirements without an annotation are the baseline post primary configuration.

3 Passenger Vehicle Scanning System Use Cases The Passenger Vehicle Scanning System will be used in a post-primary CONOPS and it introduces a new CBP CONOPS. The post-primary CONOPs provides an additional inspection tool that can be used to augment physical inspections. The new 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 new CONOPS will be performing scanning and adjudicating activities prior to the passenger vehicle arriving at the primary point of inspection into the United States. Primary point of inspection may vary based on where the CBP officers start their inspection. 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. The operational description (see Figure 1 Passenger Vehicle Scanning System - Perform Operations Use Cases) includes the use cases described below. Stakeholders or actors for the use cases are described in Table 3 Passenger Vehicle Scanning System - Stakeholders.

Figure 1 Passenger Vehicle Scanning System - Perform Operations Use Cases

Table 3 Passenger Vehicle Scanning System - Stakeholders

Item Actorss Description

1. Control Center Analyst Personnel that adjudicate the Image Data Set (IDS) images

2. CBP Primary Officer CBP Primary Officer/operators of the system

3. CBP Secondary Officer CBP Secondary/operators of the system at

Secondary Area

4. Passenger Vehicle Passenger Vehicle and its Occupants

Inspection Use Case Summary

The use case describes POE 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.

Pre-Condition

1) The System is ready for operation

2) A vehicle is arriving at Port of Entry

Post Condition

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

2) The Data Store (DS) sends the Image Data Set (IDS) to the Analyst Human Machine Interface (HMI)

Stakeholders

Passenger Vehicle and its Occupants

Steps

1) This use case begins when the 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.

Extend: Opt Out Lane Processing Use Case

3) The System’s Pre-Primary License Plate Reader (LPR) captures the front License Plate (LP) and system image of the subject vehicle. (Note: not all vehicles are required to have front license plates. In addition, front license plates may be placed off to the side.)

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 drivers and passenger(s) RFID(1).

7) The vehicle advances through the passenger vehicle lane and triggers a presence sensor.

8) The presence sensor activates vehicle scanning and starts capturing undercarriage USS imagery (when deployed).

9) The vehicle’s movement through the system portal is captured on undercarriage imagery from the entrance to the exit of the tunnel. (option)

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

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

12) If scan stops due to a slow speed (step 11), then the IDS is annotated that the “scan stopped due to slow speed.”

13) When the System detects the end of the subject vehicle:

a) System stops scanning

b) System stops capturing undercarriage imagery (option)

c) System’s LPR captures the rear LP

14) If the System detects the next conveyance within 5ft of previous vehicle, then treat that conveyance as a trailer to the previous vehicle and process it as another vehicle. The scan will be a single scan, but annotated as a trailer.

15) The subject vehicle proceeds to next available Primary Lane. (1)

16) When the subject vehicle clears Portal, the Traffic Control Indicator signals the next vehicle to enter System Screening Portal.

17) System Screening Portal sends the IDS to Data Store (DS).

18) The DS stores Image Data Set (IDS) (see Table 4 Image Data Set (IDS) Content) and adds to the IDS list of LP numbers.

19) This use case ends when the DS sends the IDS to the system HMIs.

Control Center Analysis Use Case Summary The use case describes Port of Entry (POE) CBP operations when the Command Center Analyst is analyzing and adjudicating the inbound vehicles IDS at a land border crossing. In periods when the Command Center is closed due to low traffic volumes, this use case would be performed at the HMI in secondary, vs the command center. 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.

Pre-Condition

1) Passenger Vehicle Inspection Use Case has occurred

2) The list of IDS LPs are being displayed on the control center HMI(s)

Post Condition

1) The IDS is annotated with suspect or non-suspect

2) The LP, RFID, and adjudication are passed to the LBI system

Stakeholders

Command Center Analyst, Primary Officer, Secondary Officer, Passenger Vehicle and its Occupants

Steps

1) This use case begins when the Command Center Analyst picks the next IDS available from the IDS List.

2) The HMI IDS list displays “Under Review” status when the IDS is being analyzed that will timeout after 60 seconds of inactivity and return to IDS List.

3) The IDS is unavailable for other users to open or make edits when in “Under Review” status.

4) If an RDE alarms on the vehicle, the alarm is provided on the HMI. (2)

5) The Analyst reviews and adjudicates the vehicle IDS.

6) The Analyst selects the IDS status on the HMI as “Non-Suspect” or “Suspect.”

7) If “Non-Suspect” is selected, then the DS updates the IDS record as “Non-Suspect.”

8) If “Suspect” is selected, then the DS updates the IDS record as “Suspect.”

The Scanning System passes the IDS record to CBP Land Border Integration (LBI) network. (1)

(Note: Steps 9 -17 are performed by the Land Border Integration system (LBI) in a pre-primary configuration when the system is integrated with LBI and are only provided here for information purposes.)

9) The subject vehicle approaches the Primary Lane. (1)

10) The Primary LPR (Land Border Integration) (LBI) captures the front LP of the subject vehicle and the RFID if available in the Primary Lane. (1)

11) The LBI matches the LP or RFID with the scanning IDS record. (1)

12) If a match is not found, the Simplified Arrival Vehicle (SAV) indicates “no match found” and the Primary Officer calls up list of adjudicated but not matched queue on SAV to manually locate the record using a thumbnail picture of the vehicle and license plate.

13) The Primary SAV displays the subject vehicle LP and IDS status as “Suspect,” or “Non- Suspect”. (1)

14) The Primary Officer reviews the vehicle LP and IDS status, conducts interviews with vehicle occupants, inspects necessary documentation, adds notes as necessary, and determines to “Release” or “Refer” in the SAV application. (1)

15) If the vehicle IDS status is “Suspect,” then the Primary Officer selects the “Refer” option in the SAV and sends subject vehicle to Secondary. Note: The Primary Officer must select “Refer” because the vehicle cannot be released until secondary inspection occurs. (1)

16) If the vehicle status is “Non-Suspect” and the Primary Officer determines to “Release” the vehicle, then the Primary Officer selects the “Release” option in the SAV and releases the subject vehicle to exit. (1) Proceed to step 26.

17) If the subject vehicle status is “Non-Suspect” but the Primary Officer determines to “Refer” the vehicle, then the Primary Officer selects the “Refer” option in the SAV and sends subject vehicle to Secondary. (1)

18) The system DS updates the IDS record with the vehicle IDS status. This ends the use case.

Secondary Use Case Summary The use case describes the operation for Type 2 and 3 portals supporting secondary inspection operations when a vehicle has been referred for inspection. 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.

Pre-Condition

1) Passenger Vehicle Control Center Use Case has occurred

2) The Secondary Portal is operating

Post Condition

1) The IDS is annotated with suspect or non-suspect

2) The IDP is documented in the system.

Stakeholders

Secondary Officer, vehicle

Steps

1) This use case begins when the vehicle approaches secondary.

2) The System’s License Plate Reader (LPR) captures the front License Plate (LP) and vehicle image of the subject vehicle. (Note: not all vehicles are required to have front license plates. In addition, front license plates may be placed off to the side.)

3) The Traffic Control Indicator signals the subject vehicle to enter the scanning system.

4) The Traffic control Indicator signals any following vehicles to stop, until the proceeding vehicle has cleared the portal.

5) The vehicle advances through the system and triggers a presence sensor.

6) The presence sensor activates vehicle scanning and starts capturing undercarriage imagery.

7) The vehicle’s movement through the portal is captured from the entrance to the exit of the tunnel.

8) The subject vehicle continues to move through the lane at approximately 5 mph.

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

10) If scan stops due to a slow speed (step 9), then the IDS is annotated that the “scan stopped due to slow speed.”

11) When the system detects the end of the subject vehicle:

12) System stops scanning.

13) System stops capturing undercarriage imagery.

14) If the system detects the next conveyance within 5ft of previous vehicle, then treat that conveyance as a trailer to previous vehicle and process it as another vehicle. The scan will be a single scan, but annotated as a trailer.

15) System Screening Portal sends the IDS to Data Store (DS).

16) The DS stores Integrated Data Package (IDS) (see Table 4 Image Data Set (IDS) Content) and adds to the IDS list of secondary LP numbers.

17) The Analyst picks the next IDS available from the secondary IDS list.

18) The Analyst opens the Type 2 secondary image.

19) The Analyst reviews and adjudicates the system IDS.

20) The Analyst selects the IDS status on the HMI as “Non-Suspect” or “Suspect.”

21) If “Non-Suspect” is selected, then the DS updates the IDS record as “Non-Suspect.”

22) If “Suspect” is selected, then the DS updates the IDS record as “Suspect.”

23) If “Suspect is selected, the Secondary Officer prints the IDS for reference during the physical inspection.

24) The Secondary Officer conducts inspection of the subject vehicle based on the Analyst’s annotations and images in the IDS. Note: Inspection may include additional NII systems, K9s, physical inspection, and interviews.

25) The Secondary Officer adds findings and updates status if a “Seizure” is made.

26) The system Data Store updates the IDS record based on the Secondary Officer’s findings.

27) The Data Store stores other non seizure records for 30 days.

28) The Data Store overwrites files greater than 30 days old.

29) This use case ends when adverse action is initiated or vehicle is released.

4 Requirements Requirements are specified using the command imperative “shall.” A requirement statement may contain a (T), an (O), (Future), or just the single requirement statement. The descriptions are as follows:

Threshold (T): The minimum level of operational performance that the Government will accept. A threshold requirement is identified by “(T)” after the requirement.

Objective (O): A level of performance that significantly improves mission performance, safety, or supportability beyond that of the threshold value. An objective requirement represents the desired yield for system performance identified by “(O)” after the requirement. Note: Objective values are not required, but provide guidance to the Contractor with respect to areas where increased capability is of interest to the Government.

Future: Currently the system does not need to meet the requirement. It will not be verified. However, design and build should not restrict or inhibit these future interfaces and integration expansions.

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

Behavioral Requirements

Use Case Requirements

The system shall verify that the vehicle is not oversized (height & width) prior to arriving at the Traffic Control Indicator. (Note: using a mechanical means)

The system shall signal oversized vehicles to divert to the opt-out lane. (Note:

may be accomplished with signage)

When there is no previous vehicle in Screening Portal Lane, the System Traffic Control shall signal the vehicle to enter the portal.

When there is a previous vehicle, the system Traffic Control Indicator shall signal the vehicle to enter the portal, once the previous vehicle clears scanning portal.

The System shall detect when a vehicle is entering the portal.

When the previous vehicle has not cleared the System Screening Portal, the System Traffic Control shall signal the next vehicle to stop.

The System shall start scanning when the vehicle enters the portal.

The System shall timestamp each image based on administrator selected standard. (Rationale: intent is to allow POE to timestamp image with the local time.)

The System shall read the front LP of the subject vehicle.

The System shall read the rear LP of the subject vehicle, unless the LP is obscured (e.g. by a towed trailer).

The System shall capture an undercarriage USS image of the vehicle (when deployed).

The System shall capture the X-Ray images of the vehicle as it transits the portal.

The system shall stop scanning, if the subject vehicle speed is less than the speed at which the ANSI 43.17 maximum dose is exceeded (see 4.3.1.4).

If the scan stops due to the slow speed, the system shall annotate the IDS, that the “scan stopped due to slow speed.”

The system shall display the vehicle speed to the subject vehicle.

The System shall detect when a vehicle exits the portal.

The system shall stop scanning when the subject vehicle exits the scanning area.

The system shall stop capturing undercarriage imagery when the subject vehicle exits the scanning area.

The system shall validate that the rear LP matches the front LP. .

If LPs do not match, the system shall create an alert to the HMI.

The system IDS shall contain the items identified in Table 4 Image Data Set (IDS) Content.

Table 4 Image Data Set (IDS) Content Number Item Description 1 License Plate (LP) Vehicle LP number (passed to LBI)

Vehicle Front and Rear LP images (thumbnail LP images are passed to LBI)

2 Portal ID Identification of Scanning Portal that captured images.

3 X-Ray Image(s) Vehicle X-Ray image captured by X-Ray screening (note:if system provides multiple views, all images shall be provided)

4 USS image X-Ray Undercarriage Scanning System (USS) 5 User ID User that is creating and updating IDS (Analyst, Primary, and Secondary, Supervisor system users) 6 Driver ID RFID Information (passed to LBI) 7 Passenger IDs RFID Information (passed to LBI) 8 Timestamp Timestamp includes date and time 9 Analysis Status Status includes: “Under Review,” “Non-Suspect,”

“Suspect,” or “Seizure” (Passed to LBI) 10 Annotations Analyst/Officer notes and/or graphics, with associated officer ID

If the system detects the next conveyance within 5ft of previous vehicle, then the system shall treat that conveyance as a trailer to the previous vehicle.

When the system detects a trailer, the system shall process it as part of the same vehicle.

{Reserved}

The system IDS shall integrate with LBI system (2).

The system IDS shall integrate with the CBP cloud network (1).

The system DS shall store the IDS after the IDS is created.

The system DS shall store the IDS record for a minimum of 90 days, when in “Non-Suspect” status.

The system HMI shall display the IDS list in First-In-First-Out (FIFO) order, first on top.

The system IDS list shall identify the passenger vehicle by rear LP alphanumeric characters and time stamp.

The system HMI IDS list shall display “Under Review” status, when an IDS is waiting for analysis or being analyzed.

The system HMI IDS list shall prevent another operator from opening an IDS with “Under Review” status.

The system HMI shall timeout an IDS with “Under Review” status after 60 seconds of inactivity. Note: timeout will remove “Under Review” status from IDS list.

The system DS shall automatically save and store work in progress (annotations) when a timeout occurs.

The system HMI shall display vehicle status. (Note: vehicle status is the status of the IDS defined in 4.1.1.36.)

The system HMI shall automatically update the status of the IDS within 3 seconds of operator entry. Note: the status of the IDS is indicated as “Under Review,” “Non-Suspect,” “Suspect,” or “Seizure”.

The system HMI shall display the IDS upon operator command.

The system DS shall store the IDS.

The system HMI shall annotate IDS images upon operator command.

The system HMI shall tag annotations with the analysts identification.

The system HMI shall prevent analysts from editing other analysts annotations.

The system DS shall update the IDS lists with every status update.

The system DS shall be able to export the IDS only to a CBP-approved removable media.

The system HMI at secondary inspection shall display the IDS LP list of “suspect” vehicles in FIFO order.

Structural Requirements Below is a SysML Block Definition Diagram (BDD) showing the top-level system operational components. As shown in Error! Reference source not found., the System is comprised of a Traffic Control System, Screening Portal, LP Readers, Under Carriage Scanning System, HMI, and a Data Store. Each block defines a component, it may not be inclusive for all manufacturers.

Figure 2 System Decomposition

System Requirements

The system shall display radiographic images with the quality for a system trained CBP officer to discriminate the object described in Table 5 Detectable Object concealed in any of the locations listed in Table 6 Concealment Locations with at least 50 (T), 95 (O) percent success.

The Type 1 system shall detect objects listed in Table 5 Detectable Objects concealed in any of the locations listed in Table 6 Concealment Locations within a vehicle with at least 50 (O) percent success without operator intervention.

False detections from 4.2.0.2 shall not exceed 3 (O) percent.

Table 5 Detectable Objects

Table 6 Concealment Locations

Item Description Dimensions Density

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

2 Hand Gun 185 mm x 128 mm (7.28 inch x 5.04 inch)

7.8 g/cc

Item Location System Type 1, 2 System Type 3

1 Doors X

2 Rear Seat X Passenger Seats

3 Fuel Tank X X

Table 7 Transmission Image Quality Indicators (IQI)

Requirement Type 1 Type 2 Type 3

4.2.0.4 The system shall penetrate

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

19 (T) 65 (O) 19 (T) 65 (O) 19 (T) 65 (O)

4.2.0.5 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), 3% (O) 5% (T), 3% (O) 5% (T), 3% (O)

4.2.0.6 The system’s horizontal

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

6 (T) 2 (O) 9 (T) 6 (O) 10 (T) 6 (O)

4.2.0.7 The system’s vertical

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

8 (T) 2 (O) 12 (T) 8 (O) 20 (T) 12 (O)

4.2.0.8 The system shall

discriminate between organic (low

z) and inorganic (high z) materials when the organic material is surrounded by inorganic material.

(T) (Note: system will be tested in accordance with section 3.8.1 of the SOW)

All

1 CBP follows the ANSI 42‐46 definition spelled out in section 4.8c: horizontal is in the direction of the detector array and vertical is perpendicular to the detctor array.

2 CBP follows the ANSI 42‐46 definition spelled out in section 4.8c: horizontal is in the direction of the detector

Table 8 Reflective IQI

Requirement Type 1 Type 2 Type 3

4.2.0.9 The system shall penetrate

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

6 (T) 8 (O) 6 (T) 8 (O) 6 (T) 8 (O)

4.2.0.10 The system’s horizontal

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

9 (T) 4 (O) 10(T) 6 (O) 12 (T) 6 (O)

4.2.0.11 The system’s vertical

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

9 (T) 4 (O) 10 (T) 4 (O) 12 (T) 4(O)

4.2.0.12 The System radiographic

images shall provide a layer contrast of at least X (mm) in accordance with test procedure in

ANSI 42-46-2008.

1.5 (T) 1.0 (O) 2 (T) 1.5 (O) 2.5 (T) 2 (O)

4.2.0.13 The System

radiographic images shall provide a isolation contrast of at least X

(mm) in accordance with test procedure in ANSI 42-46-2008.

1 (T) 1 (T) 1(T)

4.2.0.14 Type 1, 2, and 3 systems shall meet the IQI performance in Table 7 Transmission Image Quality Indicators (IQI) at the offeror defined minimum scan speed (T) / 5 mph (O).

3 CBP follows the ANSI 42‐46 definition spelled out in section 4.8c: horizontal is in the direction of the detector

4 CBP follows the ANSI 42‐46 definition spelled out in section 4.8c: horizontal is in the direction of the detector

Type 1 systems with reflective technology and Type 2 and 3 systems shall meet the IQI performance in Table 8 Reflective IQI at the offeror defined minimum scan speed (T) / 5 mph (O).

The System shall display radiographic images at 4,096 (T) greater than or equal to 65,536 (O) gray levels

The System shall operate in temperatures defined in Table 9. System Operational Environment

Traffic Control (TC)

The System Traffic Control (TC) will ensure the efficient and effective flow of traffic without negatively affecting the overall flow of passenger vehicles through the POE. This capability may include lights, signage, and lane barriers as required.

The System TC shall detect if a vehicle is oversize at a distance of at least 30

ft. from the Screening Portal. (Note: mechanical device)

The System TC shall redirect the oversize vehicle to the opt-out lane. (Note:

signage permitted)

The System TC shall protect the Scanning Portal from vehicle physical damage. (Note: Protection can be bollards, rub rails, etc.)

The System TC shall have mechanical barriers to restrict oversized vehicles prior to entering the Screening Portal Lane.

The System TC shall have mechanical barriers to protect the system from damage.

Note: Protection can be bollards, rub rails, etc.

Scanning – Low Energy Drive Through Portal (LEP)

Type 1 and 2 systems: Pre-Primary, Post Primary and Secondary Passenger Vehicle Scanning Systems tunnel shall be no less than 9 ft. high x 9 ft. wide.

The Type 1 System footprint area for a single lane shall not exceed a width of 14 ft (T) /1 2 ft.(O) width. Note: the system includes scanning sensors, sensor support, cameras, and electronics and any shielding walls inherent to the design to meet 4.2.2.12.1.

4.2.2.2.1 The Type 1 System footprint area for a single lane shall not exceed a length of 21 ft. (T) / 14 ft. (O) length. Ancillary equipment in section

4.2.1, 4.2.3, 4.2.4 and USS in section 4.2.5 is excluded from this requirement.

The Type 2 Secondary Systems footprint area shall not exceed 24 (T) 16 (O) feet wide by 24 (T) 20 (O) feet long, and 15 (T) feet high.

Type 2 and Type 3 systems side field of view shall include from the ground to the roof. (Note: achieved without ramps or raised platforms)

The Type 2 and 3 systems shall display six images of the conveyance using both transmission and reflection technologies. (Note: top down, both sides in transmission and reflection)

The Type 3 Bus/Truck low energy systems tunnel shall be no less than 14 ft 6 in (T) 15 ft (O) high x 12 ft (T) wide.

The Type 3 Bus/Truck low energy systems footprint shall not exceed 29 (T) 20 (O) ft wide by 27 (T) 22 (O) ft long, and 21 ft 6 in (T) high.

The Type 1 Pre/Post Primary System shall scan greater than 100 passenger vehicles per hour. (T)

The Type 2 and 3 secondary and bus systems shall scan greater than 20 vehicles per hour. (T)

Note: Throughput requirement must be met while meeting all imaging and radiation safety requirements.

A system shall operate without interference from collocated NII systems of the same model with greater than 3 ft (T), 1 ft (O) separation of outer boundaries.

The System radiation control area shall be no more than 1 ft beyond outer boundary on the sides of the system (T).

The system SP shall not interfere with radiation portal monitor (RPM) performance. Note: Non-interference requirement will be verified by CBP, or their designated test agent, with an operational radiation portal monior.

4.2.2.12.1 System operation shall not generate more than 1 in 10,000 false “X-Ray” alarms interference with CBP deployed cargo vehicle RPMs at 420 ft (T) / 100 ft (O) in all directions from the system center

Or

4.2.2.12.2 System operation shall not generate more than 1 in 10,000 false “X-Ray” alarms interference with CBP deployed passenger vehicle RPMs at 360 ft (T)/ 100ft (O) in all directions from the system center. In addition, CBP may, at its option, conduct pre-award evaluations of RMP non-interference.

System operation shall employ a pulsed radiation source to support RPM blanking.” Note: total blanking duration shall not exceed 100 milliseconds in any one second (O)

License Plate Readers (LPR)

The System LPR shall read alphanumeric characters of vehicle front license plate.

The System LPR shall read alphanumberic characters of vehicle rear license plate.

The System LPR shall read license plates with a 90.0 (T) 95.0 (O) percent accuracy. The System LPR shall capture at least 99.5% (T) 99.8% (O) of the license plates crossing in its lane.

Note: Note images need to be at day and night conditions. Capture is defined as detecting the license plate.

The System LPR shall identify all 50 states and the District of Columbia for U.S. license plates with a 90.0 (T) 95.0 (O) percent accuracy.

The System LPR shall identify all 12 provinces and territories for Canadian license plates with a 90.0 (T) 95.0 (O) percent accuracy.

The System LPR shall identify all 31 states and one district of Mexican license plates with a 90.0 (T) 95.0 (O) percent accuracy.

Radio Frequency Identification (RFID)

The RFID reader shall read ISO-18000-63 (colloquially GEN2) RFID enabled travel documents.

The RFID reader shall read the Electronic Product Code (Memory Bank 1) and the Tag Identifier (TID) (Memory Bank 2) from each presented card.

The RFID reader shall read a minimum of 95% (threshold), 99 % (obj) of properly presented RFID enabled travel documents.

RFID reads of documents in other than the correct lane (colloquially cross-lane reads) in each lane shall be less than 0.2% (T) of all RFID reads. (note:

Where more than one System is installed, or other RFID readers are installed)

The RFID reader shall radiate only while the vehicle is within the portal.

Signage shall indicate the location and correct presentation of the RFID documents. (Note: any verbal communications on the signage shall include English and Spanish)

Under Carriage Scanning System (USS) (option)

The X-Ray scanning portal shall include a X-Ray Undercarriage Scanning System (USS). (O) Note: The vehicle plus X-Ray USS combined dose shall meet ANSI 43.17 dose requirement in 4.3.1.4.

The USS X-Ray undercarriage scanning systems shall meet the reflective imaging requirements of 4.2.0.

The System USS shall capture the complete undercarriage image.

The System USS shall survive vehicles that weigh up to 26,000 lbs.

The System USS shall have a flush mounted configuration.

The System USS shall be installed in the same lane of traffic no more than 40 feet (T) from / within the system footprint in section 4.2.2.2 and 4.2.2.3.

NII Control Center

The NII Control Center shall remotely control the System. (Note: remote control includes full remote operations for the system including the operation of the system 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 BSDP integration), and any other requirements to fully operate the System)

System Work Center

The System Work Center shall house all required workstations in the NII Control Center. A work center is defined as a single analyst or operator position with a system OEM workstation supplied for system operation / IDS analysis.

The System Work Center(s) shall allow all the required functions to fully adjudicate the IDS(s). (Note: the number of required work centers for a given site deployment shall be determined based on seasonal peak traffic volume and average analyst adjudication time per IDS).

The System work stations shall be compliant with the latest CBP Technical Reference Model (TRM) specification.

The System Work Center monitors shall be a minimum of 38” in size or the images may be compiled on a large screen which provides images of the same equivalent size.

System shall include an Uninterruptable Power Supply (UPS) for the System Work Center and a power conditioner to regulate and maintain power sufficient to allow thirty (30) minutes of standard operation and a graceful shut down of systems.

Each System Work Center shall allow any analyst on any System Work Center with full analysis capability to adjudicate an IDS from any of the connected Type 1, Type 2, or Type 3 systems.

System Work Center(s) shall be installed in the secondary to support secondary inspection operations on referred vehicles. (Note: the number of work centers shall depend on individual site requirements.)

NII Control Center Situational Wall (SW)

The NII Control Center Situational Wall (SW) shall include the following elements. Exact configuration for a given site deployment will be determined through survey and design process.

For each Portal, the SW shall include a high definition, large monitor (55” or larger) for each CCTV / PTZ system for each Scanning system.

Each Portal element of the SW shall be collocated so that there is a separate section of the wall dedicated to each Portal. (Note: the intent of this configuration is so that a supervisor can view all of the activities associated with a Unit operation in one location)

The SW shall include one (1) high definition, large screen TV (50” or greater) for monitoring news and weather channels.

The SW shall include two (2) IDS Queues on separate monitors as described below:

4.2.8.4.1 Primary IDS Queue shall be displayed on a large screen (48” or larger) for the IDS’s in “under review” status from the Portal Units.

4.2.8.4.2 Secondary IDS Queue shall be displayed on a large screen (48” or larger) for all of vehicles in “suspect” status.

4.2.8.4.3 Secondary IDS Queue shall display first-in-first out order.

4.2.8.4.4 Number of vehicles displayed in IDS Queue shall be adjustable by operator. (Note: default is 20 vehicles)

Human Machine Interface (HMI)

“The Human Machine Interface (HMI) provides Customs and Border Protection (CBP) operational control and display of the system information. CBP interaction with the System is a constraint on the theoretical throughput of the system. Therefore, an increased emphasis is placed on HMI design that increases automation of anomaly detection that follows accepted industry best practices for Human Machine Interface design.”

The System HMI shall manage the DS records upon operator command.

Note: manage means to retrieve, update, delete (authorized only), archive, copy, store, export, and send data records.

The System HMI shall manage the DS records by category upon operator command.

The System HMI response time shall not exceed 2 (T) 1 (O) second upon operator command.

The System HMI shall create operator-defined queries of IDS IDs.

The System HMI shall create operator-defined reports of IDSs.

The System HMI shall vary image magnification upon operator control.

The System HMI shall select different color palettes upon operator control.

The System HMI shall vary image contrast upon operator control.

The System HMI shall sharpen image edges of the radiographic image upon operator command.

The System HMI shall smooth edges of the radiographic image upon operator command.

The System HMI shall reduce background noise of the radiographic image upon operator command.

The System HMI shall emboss the radiographic image upon operator command.

The System HMI shall vary image brightness upon operator control.

The System HMI display shall define regions of interest upon operator control.

The System HMI shall annotate the images upon image analyst entry.

The System HMI shall display the digital image of the license plate(s) along with the scanned vehicle radiographic image.

The System HMI shall print the items of an IDS upon operator control. Note:

printing is to include images and notes.

The System HMI shall display the entire length of the scanned vehicle.

The system HMI shall display UFF v2 images.

The System HMI shall display the IDS on the IDS list with a delay of no more than 5 (T), 3 (O)seconds upon completion of scan.

The System HMI shall display the IDS information with a delay of no more than 3 seconds after IDS is created at the system upon selection.

The System HMI shall display Traffic Control indicator state (red or green).

The System shall alow the Operator or Analyst initiate an emergency stop of the system remotely over a secure network connection

The System HMI shall turn-off X-Ray upon operator command. (E-Stop)

The System HMI shall highlight the IDS in red on the IDS list when anomaly is detected

The System HMI shall transition any component into Maintenance Mode upon operator command.

The System HMI shall export reports to CBP approved removable media.

The System HMI shall display an alert to the operator when a component is non-operational.

The System HMI shall display an alert to the operator when an interface is non-operational.

The System HMI shall display a Warning Banner on displays during user account logon, as follows:

"You are accessing a U.S. Government information system, which includes (1) this computer,

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

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

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

You have no reasonable expectation of privacy when you use this information system;

this includes any communications or data transiting, stored on, originated from or directed to this information system. At any time, and for any lawful government purpose, the government may monitor, intercept, search and seize any communication or data transiting, stored on, originated from or directed to or from this information system.

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

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

The System HMI shall prompt the user to accept the Warning Banner language before they can authenticate with the user ID and password to access the system.

Data Store (DS)

The System DS shall provide sufficient storage for 45 days worth of files per installed portal. (Note: 30 days plus 50% margin)

The System DS shall comply with FIPS 140-2 Level 2 or greater.

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

The System DS shall export IDS images as a Tagged Image File Format (.tiff or .tif) file.

External NII Systems (Future)

For these future NII systems, the design and build should implement and make provisions for near-term and future interfaces and integration expansions:

The System shall interface/integrate with the Land Border Initiative (LBI) system architecture to create a joint solution that supports pre-primary POV scanning.

The System shall integrate with a CBP in-cloud data system (e.g. ARDIS-C), including:

4.2.11.2.1 Physical connection from the NII system to a sweeper computer (:XSweeper”), either through a defined file share or a defined API interface.

The XSweeper will transmit packages to the CBP in-cloud system via a secure channel (SWIFT or ICP, as available).

4.2.11.2.2 Formatting of messages for transmission conforming with DAC-TER-developed technical requirements/ICD (Current version: 9+4). Under these requirements, images may be encapsulated in a format acceptable to CBP (e.g. UFF v2.0, or suvsequent version).

4.2.11.2.3 Event triggered, real-time transmission of data, including IDS, to the CBP in-cloud data systems.

The System shall interface/integrate with the Radiation Detection Equipment (RDE) using N42,42, PRIDE ICD2.0 ver 5.

The System shall interface/integrate with the NII Radiation Operations Center (NROC). Non-occupancy data shall be transmitted to the necessary CBP in-cloud data systems, to be available to NROC, via its XSweeper/SWIFT/ICP interface, or other CBP-approved architecture, to support this functionality.

The system shall be capable of integrating with other vendors’ systems and shall be able to send images for analysis to a common viewer software application.

Supportability Requirements

System Safety

The System barriers shall prevent any physical damage to the System from vehicles driving through passenger vehicle lanes.

The System shall illuminate the vehicle within the tunnel and operating area.

The System shall limit radiation exposure to 50 µR in any hour at the boundary of the radiation control area (RCA).

Per ANSI 43.17, the System shall limit radiological dose equivalent to each vehicle occupant being scanned to no more than 25 uR/scan (T) 10 uR/scan (O). (Note: Requirement must be met at speeds ≥ offeror defined minimum scan speed.)

The system shall include safety features in accordance with ANSI 43.17 (Note: lights, indicators, safety interlocks)

The radiation dose to vehicle occupants in adjacent lanes shall not exceed 50 μR in any one hour.

System Operation

The System shall be capable of operating no less than 24 hours per day, 365 days per year (8760 hours per year), excluding scheduled maintenance.

The System scheduled maintenance shall not exceed 8 hrs per lane per month.(note:scheduled maintenance includes preventive and sustainment maintenance)

The System operating life expectancy shall be greater than ten (10) years.

The System shall send Health and Status information to the operator HMI upon operator command.

The System shall send Health and Status information to the NROC upon NROC request (1)

The System shall send an alert to the NROC/SOC when a failure occurs (Future).

The System shall have a “Degraded Mode” of Operation.

When in “Degraded Mode”, the system shall create the IDS with remaining available data.

The System shall condition input power to protect system components.

Reliability, Availability and Maintainability Design Requirements

The system will be reliable, available, and maintainable to support the operator with readily available repair parts, test equipment, and supplies to maintain a level of operation. This includes logistics time, diagnostic time, fault isolation, waiting or administrative downtime, and corrective maintenance downtime.