SOW - Lake Ontario Expansion for MDP (updated 5-15-2020).pdf

Statement of Work FAALC MDP Lake Ontario Expansion

FAALC/CBP

For Official Use Only (FOUO)

Federal Aviation Administration

U.S. Customs and Border Protection

Maritime Detection Program

Lake Ontario Expansion

Published: May 5, 2020

Support Agency:

Federal Aviation Administration (FAA) FAA Logistics Center 6500 S. MacArthur Blvd Oklahoma City, OK 73069

Distribution Statement: Distribution authorized to the U.S. Customs and Border Protection Agency and Federal Aviation Administration Logistics Center and their Contractors. This document contains technical data for administrative use. Requests for this document must be referred to FAALC

FAALC/CBP P a g e | ii For Official Use Only (FOUO)

FAALC/CBP P a g e | 1

For Official Use Only (FOUO)

Table of Contents

1.0 Background

2.0 Objectives

3.0 Requirements

4.0 General Requirements

FAALC Lake Ontario Expansion

FAALC/CBP P a g e | 2

For Official Use Only (FOUO)

5.0 Deliverables

6.0 Policy Requirements

7.0 Typical Operating Conditions

Appendix A — Acronyms

Appendix B — Glossary

List of Figures

Figure 1 — Lake Ontario

Figure 2 — Table DTM-4: Summary 2013 Weather Information for Detroit, Michigan

List of Tables

Table 1 — Small Water Craft

Table 2 — Small Pleasure Boat (20-30 ft.)

Table 3 — Cabin Cruiser (40-50 ft.)

Table 4 — Ships (5,000 tons displacement)

Table 5 — Identification Coverage Map for Watercraft

Table 6 — Policy Documents

Table 7 — Security Document Requirements for the Surveillance Facilities .......... Error! Bookmark not defined.11

FAALC/CBP P a g e | 1

For Official Use Only (FOUO)

1.0 Background

The purpose of this Statement of Work (SOW) is to issue the requirements for a detection and identification system proposal to be deployed on Lake Ontario as shown in figure 1. The overall objective of SOW is to identify technology that will provide the ability to detect watercraft of all types over 100 percent of Lake Ontario. The second objective of this SOW is to identify technology that is capable of identifying any watercraft along the US Border to 7.5 nautical miles into Lake Ontario to include the shoreline of any island greater than 2 square miles in size in US territorial waters. The detection and identification requirements may be part of a holistic approach, or separate proposals. Additional attention will be given to proposals that provide an integrated approach to detection and identification, such as slewing the identification technology to a target detected by the detection technology.

Figure 1 — Lake Ontario

2.0 Objectives

The objective of the SOW is to receive proposals for technologies that will provide detection and identification of watercraft on Lake Ontario. Proposals will be submitted to the government for evaluation. Minimum requirement for the proposals are stated in Section 3.0. The government will review the proposals and draft an additional SOW for acquisition of the proposed technology for proof of concept testing. The acquisition SOW will also provide options for full deployment of proposed technology upon successful completion of proof of concept testing. Proof of concept testing will be determined by the technology proposed and will be based on that technology.

3.0 Requirements

The requirements are broken down into detection and identification systems. Vendors must provide a solution for detection, identification or an integrated solution. The integrated solution is not required of all vendors. An integrated solution will be considered by the government, but may not be requested for proof of concept.

FAALC/CBP P a g e | 2

For Official Use Only (FOUO)

3.1 Detection

The government is requesting specific performance evaluations from the vendor. The performance metrics provided by the vendor may be evaluated in a proof of concept test. All proposals must meet specific requirements as defined in this section and general requirements as defined in Section 4.0.

3.1.1 Watercraft Detection Maps.

The vendor will provide probability of detection coverage maps for watercraft of various sizes, speed, sea state, and probability of detection. The vendor will provide three sets of the coverage maps for the conditions defined below. These three sets will be for bow approaching, stern receding, and tangential travel. The vendor will also provide the time to report a detected target and the false target rate in each sea state. While the government goal is 100% coverage of Lake Ontario, the government will consider solutions that are less than 100%.

Fiscal considerations will be taken into account for any proposed solution. The theoretical coverage maps will provide proposed locations If needed, in latitude and longitude. While the government is using the Radar Cross Section (RCS) to define a size of target this SOW is not limiting the respondents to a radar solution.

Table 1 — Small Water Craft

Small Water Craft

Coverage

Map #

Radar Cross

Section (m2) Speed (Knots) Sea State

Probability of

Detection (%)

1 0.02 2 0 95

2 0.02 10 1 95

3 0.02 10 3 75

4 0.02 30 1 95

5 0.02 30 3 75

6 0.02 50 1 95

7 0.02 50 3 75

Table 2 — Small Pleasure Boat (20-30 ft.)

Small Pleasure Boat (20-30 ft.)

Coverage

Map #

Radar Cross

Section (m2) Speed (Knots) Sea State

Probability of

Detection (%)

1 2 10 1 95

2 2 10 3 75

3 2 10 5 75

4 2 30 1 95

5 2 30 3 75

6 2 30 5 75

7 2 50 1 95

8 2 50 3 75

9 2 50 5 75

FAALC/CBP P a g e | 3

For Official Use Only (FOUO)

Table 3 — Cabin Cruiser (40-50 ft.)

Cabin Cruiser (40-50 ft.)

Coverage

Map #

Radar Cross

Section (m2) Speed (Knots) Sea State

Probability of

Detection (%)

1 10 10 1 95

2 10 10 3 95

3 10 10 5 75

4 10 10 7 75

5 10 10 1 95

6 10 30 3 95

7 10 30 5 75

8 10 30 7 75

Table 4 — Ships (5,000 tons displacement)

Ship (5,000 tons displacement)

Coverage

Map #

Radar Cross

Section (m2) Speed (Knots) Sea State

Probability of

Detection (%)

1 10,000 10 1 95

2 10,000 10 3 95

3 10,000 10 5 75

4 10,000 10 7 75

5 10,000 20 1 95

6 10,000 20 3 95

7 10,000 20 5 75

8 10,000 20 7 75

3.1.2 Performance Tradeoffs in Detection Facilities.

The vendor must be capable of discussing and identifying tradeoffs of performance versus cost.

3.1.3 System Detection Requirements

3.1.3.1 Automatic Detection Surface Item of Interest (SIOI)

The system must automatically detect when a Surface Item of Interest (SIoI) crosses the International Boundary.

3.1.3.2 Display SIOIs Geographic Coordinates

The system must provide the capability to display the geographic coordinates of all detected SIoIs within the surveillance area with a range error of 60 feet and an azimuth error of 0.075 deg, out to a range of 12 nautical mile (nmi), for each SIoI’s true location.

FAALC/CBP P a g e | 4

For Official Use Only (FOUO)

3.1.3.3 Continuously Update Projected Path

The system must display a continuously updated projected path for a selected SIoI for up to four minutes from its current position upon operator command.

3.1.3.4 Correlate Multiple External Tracks

The system must correlate multiple external sensor tracks into a single track.

3.1.3.5 Reporting SIOI

The system must report a SIoI within two seconds of initial detection.

3.1.3.6 Automated Constant False Target Rate

The system must have automated features to maintain a constant false target rate in differing sea states.

3.1.3.7 Lake Ontario Expansion Automatic Detection

The Lake Ontario Expansion system shall automatically detect the position of SIoIs moving at a minimum detectable range rate of at least 2 knots (T) stationary (O) with respect to the Lake Ontario Expansion system line of sight, at a confidence of 80 percent.

3.2 Identification

The section describes the identification requirements in broad terms. The identification system must allow an operator to perform the following:

• Identify: To determine whether SIoI is human, animal, conveyance, or unknown.

• Classify: To determine the level of threat of a detected SIoI.

• Track: To follow the progress or movements of a SIoI.

The government is requesting specific performance evaluations from the vendor. The performance metrics provided by the vendor may be evaluated in a proof of concept test. All proposals must meet specific requirements as defined in this section and general requirements as defined in Section 4.0.

3.2.1 Watercraft detection maps.

The vendor will provide identification coverage maps for watercraft of the various sizes. While the government goal is 100% identification any watercraft along the US Border to 7.5 miles into Lake Ontario to include the shoreline of any island greater than 2 square miles in size in US territorial waters, the government will consider solutions that are less than 100%.

Positive identification is the ability for an operator to discern the name or registration number for a particular watercraft. The theoretical coverage maps will provide proposed locations in latitude and longitude. The technology at each proposed location will also be defined.

The identification must be capable of operating during the daylight and nighttime hours.

Identification coverage maps must be generated for 90% probably of identification both nominal daytime and nighttime conditions.

FAALC/CBP P a g e | 5

For Official Use Only (FOUO)

Table 5 — Identification Coverage Map for Watercraft

Coverage

Map # Radar Cross Section (m2)

Maximum Distance

(Nautical Miles)

1 0.02 7.5

2 2 7.5

3 10 7.5

4 10,000 7.5

3.2.2 Performance tradeoffs in Identification Facilities.

The vendor must be capable of discussing and identifying tradeoffs of performance versus cost.

3.2.3 Identification System Requirements

3.2.3.1 Full Motion Video (FMV) of Resolution and Quality

The system shall provide full motion video (FMV) of resolution and quality to enable the operator to identify key characteristics of the IoIs detected within one nmi from the identification system at the user workstation display. Key characteristics of SIoIs includes, at a minimum, size, state-mandated markings, number of visible crew members and whether crew members are carrying large unconcealed long arms (e.g. rifles, shotgun, etc.).

3.2.3.2 Typical and Non-typical Operating Conditions

Under typical operating conditions as defined in Section 7.0, the SIoIs will be tracked to a range of 25nmi from the United States coastline, at a confidence of 80 percent.

Under non-typical operating conditions, the system must continuously track detected

SIoIs at a range of at least 12 nmi from the United States coastline.

3.2.3.3 Continuous Auto Imagery Tracking

The system must automatically track the imagery of a SIoI moving at least 0.29 knots within the 10 nmi. The system must automatically track the imagery of a SIoI moving at least 2.6 knots between 10 nmi and 25 nmi.

The Lake Ontario Expansion system shall display a continuously updated projected path for a selected SIoI for up to four minutes from its current position upon operator command.

The Lake Ontario Expansion system shall correlate multiple external sensor tracks into a single track.

The system must be capable of maintaining operation in a brine ice environment. If the equipment freezes over during a brine, ice event the system must be capable of continuing operation without degradation during the event.

3.3 Integrated Solutions

Integrated solutions must provide an alert system that detects watercraft and slews the identification system to the watercraft on operator command. The identification must track the watercraft until operator control terminates track. The solution must be integrated into the Joint Perimeter Surveillance Command (JPSC2) workstation and the Sensor Management System (SMS) support by Naval Information Warfare Center (NIWC).

All integrated solution must meet the requirements in paragraphs 3.1, 3.2, and 3.3.

FAALC/CBP P a g e | 6

For Official Use Only (FOUO)

4.0 General Requirements

The following describe the general requirements for the detection and identification technologies.

4.1 General

4.1.1 Proposed Systems

All proposed systems must be at a Non-Developmental Items (NDI) with an industry standard Test Readiness Level (TRL) of seven.

4.1.2 Technology

The technology at each proposed location must be defined to Line Replaceable Unit (LRU) level.

The LRU must have a manufacturer and part number. The government must be capable of purchasing the LRU by part number from a manufacturer without the assistance of the vendor.

4.1.3 Training

4.1.3.1 Operator Training

The vendor must provide operational, system administration, and maintenance training at the vendor facility. The vendor must supply training course electronically. The government must provide approval of all training materials.

4.1.3.2 Depot Level Training

The vendor must provide depot level training at the vendor facility. The vendor must supply training course electronically. The government must provide approval of all training materials.

4.2 Environmental Survivability Requirements

4.2.1 Temperatures Survivability

The system must survive temperatures between -40 °C and +70 °C.

4.2.2 Humidity Survivability

The system must survive and operate in humidity up to 100%.

4.2.3 Weather Survivability

The system must survive wind, rain, dust, and sand conditions.

The system must survive sustained wind up to 90 miles per hour (mph) with gust velocities up to 120 mph.

4.3 Environmental Operational Requirements

4.3.1 Operating Temperatures

The system must operate with temperatures between -40 °C and +70 °C.

4.3.2 Operating Sustained Wind Velocities

The system must operate with sustained wind up to 40 mph with gust velocities up to 80 mph.

FAALC/CBP P a g e | 7

For Official Use Only (FOUO)

4.3.3 Operating Ice Build-up

The system must operate in an environment that is consistent with ice build-up on system components.

4.4 System Operation

4.4.1 Operational Availability

The system shall have an Operational Availability (Ao) of 90 percent (T) and 95 percent (O).

4.4.2 Auto Record Data

The System will automatically record all sensor data.

4.4.3 Roundtrip Latency

The System will have an overall roundtrip latency of no greater than 0.750 seconds (T), 0.500 seconds (O).

4.4.4 Structure Collocated Devices

The System will not physically, optically, or electromagnetically degrade the performance of collocated devices on the supporting structure.

4.4.5 Digital Video Quality

Any digital video quality level with comply with Standard Motion Image levels as defined in Motion Imagery Standards Profile (MISP)-2015.1, 2014 (Latest version applies).

4.4.6 Viewable Video Media and Metadata

Any video media and metadata will be viewable using commercial video players (including Windows Media Player).

4.4.7 System Protection and Supporting Equipment

The System and Supporting Equipment will be hardened against vandalism, or any unauthorized illegal action, which degrades in any way the normal performance, or sensors, and devices in accordance with (IAW) US Department of Homeland Security (DHS)/CBP policy and procedures, refer to Table 6.

4.4.8 Mean Time Between Failures

The Mean Time Between Failures (MTBF) for a sensor will be greater than or equal to 43,800 hours.

4.4.9 Sensors

The sensors will operate 24x7 in the environment defined in Section 4.3.

4.4.10 Sparing Model

The vendor must provide a sparing model.

FAALC/CBP P a g e | 8

For Official Use Only (FOUO)

4.4.11 System Detection

System must be capable of detecting a watercraft crossing the international Boundary and provide an alert. The alert will be both audio and visual. The alert will be configurable in audio level. The audio and visual alert must be capable of being turned off or on by the operator.

4.5 Data Integration

4.5.1 System Health Status

System must be capable of transmitting health and status information.

4.5.2 Alerts

The system must alert the CBP Network Operations Center/Security Operations Center (NOC/SOC) whenever there is a system or sub-system critical fault that makes the system non-mission capable, or puts the system in a degraded state of performance.

4.5.3 Alarm/Alert Transmission

System must be capable of transmitting alarms / alerts.

4.5.4 Data and Internet Protocol

System must provide transmission via an internet protocol for data. An Interface Communication Document (ICD) must be provided that defines each bit located in Open Systems Interconnection (OSI), Application Layer.

4.5.5 Verification of Internet Communication Document (ICD)

The vendor must provide a communications analyzer to the government for verification of ICD.

4.5.6 Remote Power

The system must be capable of remote power down and power on and all sensor subsystems upon user command.

4.5.7 Remote Data Confirmation

The system must be capable of remotely receiving and process configuration and prioritization of the transmitted data and the communication modality (i.e., user preferences, bandwidth optimization).

4.5.8 Vendor Documentation

The vendor must provide documentation for communication with the Application Programming Interface (APIs) for the sensors.

4.5.9 Vendor Code

The vendor must provide sample C# code for communicating with the APIs for the sensors.

NIWC will use the sample C# code to develop JPSC2 control and display of sensor data.

4.5.10 Vendor Simulator

The vendor must provide a simulator for testing and integration in a lab environment for the sensors.

FAALC/CBP P a g e | 9

For Official Use Only (FOUO)

4.5.11 Vendor Support

The vendor must provide email and telephone support to address questions or assistance as required during integration.

4.6 Facility Security Requirement

The contractor must meet the following minimum requirements described in this section. The Government shall review additional security requirement individually.

4.6.1 System Security Policy

The system shall comply with DHS 4300A (latest version shall apply) security policy at the Moderate Level.

4.6.2 System Compliance Standards

The system shall comply with National Institute of Standards and Technology (NIST) SP 800-53 Rev 3 (latest version shall apply).

4.6.3 System Protection Compliance Standards

The system shall incorporate physical protection measures compliant with CBP Physical Security Policy and Procedure Handbook (HB 1400-02B [latest version shall apply]).

4.6.4 System Architecture Compliance

The system shall comply with DHS Enterprise Architecture and DHS Security Architecture.

5.0 Deliverables

The vendor must provide the following information.

5.1 Detection System Only Deliverables

• Detection Coverage Maps as described in Section 3.1.

• Compliance Matrix for detection system as described in Section 3.1.

• Proposed parts list for detection system as described in Section 3.1.

• Proposed locations for detection system as described in Section 3.3.

5.2 Identification System Only Deliverables

• Identification Coverage Maps (if applicable) as described in Section 3.2.

• Compliance Matrix for identification system as described in Section 3.2.

• Proposed parts list for identification system as described in Section 3.2.

• Proposed locations for identification system as described in Section 3.3.

5.3 Integrated Solution Deliverables

• Detection Coverage Maps as described in Section 3.1.

• Compliance Matrix for detection system as described in Section 3.1.

• Identification Coverage Maps (if applicable) as described in Section 3.2.

• Compliance Matrix for integrated solution as described in Section 3.3.

• Proposed locations for integrated solution as described in Section 3.3.

FAALC/CBP P a g e | 10

For Official Use Only (FOUO)

6.0 Policy Requirements

The following documents apply to this SOW (see Table 6).

Table 6 — Policy Documents

NBR Policy Document

1.

Security and Privacy Controls for Information Systems and Organizations. NIST Special Publication

800-53 standard current version.

2.

System Reporting Form Standards for Security Categorization of Federal Information Processing

Standards (FIPS 199).

3. DHS Standard 4300 A Sensitive Systems Policy current version.

4. DHS Directive (MD 11042.1) For Official Use Only (FOUO) Information" dated January 6, 2005.

5.

CBP Security Policy and Procedures Handbook (HB1400-05D), Current version, Volume IV, Chapter 13, FOUO Information.

6.

DHS Information Security Policy, identified in MD 4300.1, (IT) Systems Security Program, and 4300A

Sensitive Systems Handbook, current version.

7. Section 508 of the Rehabilitation Act: http://www.section508.gov/.

8. Code of Federal Regulations (CFR): http://www.gpoaccess.gov/cfr/index.html.

9.

Security Guide for Interconnecting Information. NIST Special Publication 800-47 and DHS IT Security

Policies.

10. DHS Information Security Performance Plan (current version).

11. CBP Technical Reference Model (TRM) (current version).

12 DHS Security Operations Concept of Operation (current version).

13. Federal Risk and Authorization Management Program (FEDRAMP).

14. Federal Information Security Management Act (Public Law 113-283).

15. ANSI/ISO/ASQ Q10007 – Quality Management Systems – Guidelines for Configuration Management.

16. Information Security Continuous Monitoring. NIST Special Publication 800-137.

17.

Risk Management Framework for Information Systems and Organizations: A System Life Cycle

Approach for Security and Privacy. NIST Special Publication 800-37.

18. CBP Directive Operational Materiel Cost Wise Readiness (CWR) Policy and Oversight.

19. DOD Reliability, Availability, Maintainability, and Cost Rationale Report Manual.

20. Guide to LTE Security. NIST Special Publication 800-187.

21. Protecting Controlled Unclassified. NIST Special Publication 800-171.

6.1 DHS and CBP Enterprise Requirements

The vendor must support the Government while its solution is incorporated into the DHS and CBP Enterprise Architecture (EA), and the DHS and CBP TRM.

Where feasible, the vendor must use of DHS/CBP approved products, standards, services, and profiles as reflected by the Hardware (HW) and Software (SW), application, and infrastructure components of the DHS/CBP TRM/standards profile. The DHS/CBP TRM/standards profile will be updated as Technology Insertion Requests (TIR) are accomplished.

The vendor must support the Government to add all items, currently not in the TRM, into the TRM.

The Government may decide to provide as Government Furnished Equipment (GFE)/Government Furnished Information (GFI) SW products that are in the vendor’s system, and which are in the

TRM.

FAALC/CBP P a g e | 11

For Official Use Only (FOUO)

Contract Data Requirements Lists (CDRLs) for the Network Description Document (NDD), Version Description Document (VDD), the Software Description Document (SDD), and Operations and Maintenance manuals are used to the DHS and CBP enterprise requirements.

6.2 Vulnerability Scans and Remediation Process Requirements

The FAALC will perform an initial scan and associated vulnerability reports on the network/system devices using tools compliment with current DHS policy. Currently those tools are Nessus, WebInspect, and AppDetective. FAALC will send the scan files and associated vulnerability reports to the Government ISSO.

Once the ISSO reviews the scan files, the Nessus scan files are sent to the Vulnerability Assessment Team (VAT) for review and processing into the Continuum system.

Once the VAT team processes the files and corrects the anomalies, the scan files are sent to DHS for review, processing, and creating the Federal Information Security and Management Act (FISMA) reports and score cards. The FISMA reports and score cards are utilized to identify system deficiencies that needs to be addressed.

The Government ISSO retrieves the vulnerability reports from the Continuum system. The vulnerability reports are utilized to identify, document, and create a Plan of Action and Milestones (POA&M) to mitigate any identified findings.

Note: Once the vulnerability is identified, the system has 30 days to try to remediate the issue and work with the vendor if necessary. If the vulnerability cannot be resolved in 30 days then a POA&M is created to track the plan and milestone.

The vendor must work with the Government ISSO and In-Service Management Authority (ISMA)/Software Support Authority (SSA) to generate remediation plans and create patch files, which must be successfully applied to the prototype. It is strongly encourage that the vendor have an information assurance role within their team.

The NOC/SOC will validate procedures for patches and scans.

7.0 Typical Operating Conditions

The system will operate under the Typical Operating Conditions found in and around its installed area. For the Detroit Sector (DTM), the following charts provide information pertaining to the typical environmental conditions. See Section 3.6 of the Northern and Southwest Border Design Reference Mission v2.5 April 2015.

Figure 2 — Table DTM-4: Summary 2013 Weather Information for Detroit, Michigan

FAALC/CBP P a g e | 12

For Official Use Only (FOUO)

Appendix A — Acronyms

Acronym Description

ANSI/TIA American National Standards Institute/Telecommunications Industry Association

Ao Operational Availability

AOC2 (the System’s) C2 Availability

AOI Area of Interest

AOR Area of Responsibility

API Application Programming Interface

ATVs All-Terrain Vehicle

BI Background Investigation

C Celsius

C2 Command and Control

C2C C2 Center

CBP Customs and Border Protection

CDRL Contract Data Requirements List

CFR Code of Federal Regulations

CM Configuration Management

CO Contracting Officer

CWR Cost Wise/Worthiness Readiness

DHS Department of Homeland Security

DTM Detroit Sector

EA Enterprise Architecture

EO Electric Optical

FAALC Federal Aviation Administration Logistic Center

FEDRAMP Federal Risk and Authority Management Program

FIPS Federal Information Processing Standards

FISMA Federal Information Security Management Act

FMV Full Motion Video

FOUO For Official Use Only

FOV Field of View

Ft. Feet

FTR Federal Travel Regulations

GFE Government Furnished Equipment

GFI Government Furnished Information

HB Handbook

HW Hardware

IAW In Accordance With

ICD Internet Communication Document

IFOV Instantaneous Field of View (single pixel FOV)

IOI Item of Interest

FAALC/CBP P a g e | 13

For Official Use Only (FOUO)

Acronym Description

R Infrared

ISA Interconnection Security Agreement

ISMA In-Service Management Authority

ISO/IEC International Organization for Standardization / International Electro-Technical Commission

ISSO Information System Security Officer

IT Information Technology

JPSC2 Joint Perimeter Surveillance Command

LoS Line of Sight

LR Long Range

LRHP Long Range High Performance

LRU Line Replaceable Unit

LTE Long-Term Evolution

MD Management Directive

MDP Maritime Detection Project

MISB Motion Imagery Standards Board

MISP Motion Imagery Standards Profile

MLDT Mean Logistics Down Time

MOA Memorandum of Agreement

MOU Memorandum of Understanding

Mph Mile Per Hour

MR Medium Range m/sec Meters per Second

MTBCF Mean Time Between Critical Failure

MTBF Mean Time Between Failures

MTBF Mean Time Between Maintenance

MTTR Mean Time to Repair

NB Northern Border

NDD Network Description Document

NDI Non-Development Items

NIST National Institute of Standard and Technology

NMCC National Maritime Command Center

Nmi Nautical Mile

NOC/SOC Network Operations Center/Security Operations Center

O Objective

Oct Typical Operation Conditions

OIT Office of Information Technology

POA&Ms Plan of Action and Milestones

RCS Radar Cross Section

RoB Rules of Behavior

FAALC/CBP P a g e | 14

For Official Use Only (FOUO)

Acronym Description

ROM Rough Order of Magnitude

RTM Requirements Traceability Matrix

RVSS Remote Video Surveillance System

SB Southern Border

SDD System Description Document

SIOI Surface Item of Interest

SMS/JPSC2 Sensor Management System/Joint Perimeter Surveillance Command

SOW Statement of Work

SR Short Range

SSA Software Support Authority

SSP System Security Plan

STOI Surface Targets of Interest

SW Software

T Threshold

TEP Test and Evaluation Plan

TIR Technology Insertion Request

TRL Technology Readiness Level

TRM Technical Reference Model

UAR User Access Request

US BP United States Border Patrol

US CBP United States Customs and Border Protection

VAT Vulnerability Assessment Team

VDD Version Description Document

WA Wide Angle

FAALC/CBP P a g e | 15

For Official Use Only (FOUO)

Appendix B — Glossary

Animal: For the purpose of this document, an Animal is any pack animal or work animal such as donkeys, horses, and mules normally used in carrying humans or cargo

AoC2: C2 capable time (sum of all C2 mission-critical components and units) divided by the total C2 time (mission capable time and down time).

Area of Coverage: Resultant area (considering installation location of all units, view shed and LoS obstructions, etc.) within which USBP can successfully conduct surveillance activities using the system or a combination of system.

Area of Responsibility (AoR): The geographical area where border security operations are authorized. USBP formally defines AoRs at the Sector level and Station level. USBP also informally assigns AoRs at the individual agent level according to operational needs.

Audible or "plainly audible": Any sound for which the information content of that sound is unambiguously communicated to the listener, such as understandable spoken speech.

Authorized Personnel: User with valid login and appropriate access.

Azimuth: The direction of a celestial object from the observer, expressed as the angular distance from the north or south point of the horizon to the point at which a vertical circle passing through the object intersects the horizon.

Backhaul: Intermediate links between the backbone of a network and the sub-networks at the "edge" of the entire hierarchical network.

C2 Center (C2C) facility: Room or worksite, which supports one or more workstations for RVSS, as well as other surveillance systems.

Category 1: Failure of the system’s primary functions and/or any safety related issue.

Category 2: Partial failure or degradation of primary system functions that impact primary functionality, but mission operations are achievable with alternative methods.

Category 3: Failure that causes minimal degradation to system operations.

Classify: To assign an appropriate level of threat or importance to an IoI; normally involves viewing an image with sufficient detail to show special facial features, numbers on a license plate, colors, small items of interests (e.g. unconcealed long weapon), etc.

Compatible: Fully functional without degradation to the operation or performance of CBP and other Agency co-located systems.

Component: Component is a logical element of the NB RVSS system architecture illustrated, which performs functions specified in this document. Logical components can contain other logical components and so on.

Darkness: Outdoor visible light which is low light level ...low to zero light conditions (<1lux to 0.0001 lux).

Detect: To discover a possible IoI.

Device: A non-camera/video camera item such as a spotlight/floodlight, public address system, or sub-platforms, which may be part of the RVSS Upgrade unit.

Effective Surveillance Range: Radial distances where the camera is expected to produce usable images in performing the RVSS primary mission of detection, identification/classification, and tracking. See Usable Image.

Elevation: Height above a given level, especially sea level

FAALC/CBP P a g e | 16

For Official Use Only (FOUO)

EO Camera: Daytime camera

Extreme climatic conditions: Typically occur in Winter and/or Summer periods and include but not limited to very high/low temperatures, heat/cold waves, high salt air conditions, dirt & fine dust conditions, very high/low humidity, extreme rain, fog, heavy snow, severe icing, high winds, dust storms, sand storms, and electrical storms.

False IoI: A detection of an IoI that is not human, animal, or conveyance.

Field of View (FOV): Sometimes called the angle of coverage or angle of view) is defined as the angle (in object space) over which objects are recorded on the film or camera in a camera at one time. It depends on two factors, the focal length of the lens and the physical size of the sensor. Since it depends on the camera size, it is not a fixed characteristic of a lens and it can only be stated if the size of the camera it will be used with is known.

For a lens used to form a rectangular frame, three fields of view are often given, the horizontal FOV (minimum to maximum camera range), the vertical FOV, and the diagonal FOV.

Health & Status: Is the state of a component, SS or system. It states whether it is operating as intended, degraded, failed or does not operate or function. H&S also states the component configuration and version.

Instantaneous Field of View (IFOV): A measure of the spatial resolution of a remote sensing imaging system. It is defined as the horizontal and vertical angular extent in object space of a single sensing element of the imaging system.

Identify: To determine whether an IoI is a human, conveyance, animal, or other object.

IR Camera – Infra red camera

Item of Interest (IoI): Humans (on foot, mounted on animals, alone, in groups), animals, and conveyances (e.g., All-Terrain Vehicles (ATVs), motorcycles, automobiles, trucks, watercraft with minimum size of 2.5 m x 6.0 m).

Key Performance Parameter (KPP): Denotes a characteristic of the system that is considered critical or essential to its capability. It marks a specification that is mandatory and “not tradable” under any circumstance.

Large bundle: A large sized carried package of a minimum size of 3 cubic feet.

Latency: The time from C2 User Interface control to sensor function, and resulting confirmation image back to the C2 User Interface Monitor. When roundtrip latency is 0.750 seconds or better, it is considered “Near Real Time.”

Loading Constraints: For existing towers are available from structural analyses contained in the As-Built, available in the “Reading Room.”

Long Range (LR) camera: A camera typically used in a Remote environment; is capable of displaying usable images from its minimum effective surveillance range out to 5 miles (T), 7.5 miles (O).

Long Range High Performance (LRHP) camera: A camera that meets all daytime Long Range camera requirements and enhanced classification requirements.

Long Weapons: Large man-portable firearm (i.e., rifles, shotguns, etc.) that cannot generally be concealed beneath clothing.

Loud Hailer: An intercommunication device intended for limited or private dialogue, direction, collaboration, or announcements. Same as a Public Address (PA) system.

Lux: Unit of luminous emittance, measuring luminous flux per unit area. One (1) Lux is equal to one lumen per square meter.

Mean Time Between Failure (MTBF): Average time between failures; typically includes all failures without regard to any fault tolerance that may exist.

FAALC/CBP P a g e | 17

For Official Use Only (FOUO)

Mean Time Between Critical Failure (MTBCF): Used when redundancy exists in a system. It is often used to differentiate system reliability from series mean time between failures (MTBF).Mean Time to Repair (MTTR):

Average time required to repair a specific item to working status

Mean Time Between Critical Failure (MTBCF): Used when redundancy exists in a system. It is often used to differentiate system reliability from series MTBF.

Medium Range (MR) camera: A camera typically used in both Urban and Rural environments; is capable of displaying usable images from its minimum effective surveillance range out to 3 miles (T), 5 miles (O).

Mission-Critical component: Any component required by the System to perform one or more of its intended mission elements (i.e., CBP Mission Elements: Predict, Deter, Detect, Track, Identify/Classify, Respond, Resolve).

As such, the following components and subsystems are considered Mission-Critical: SR, MR, LR EO, and IR cameras, scanning sensor(s) including the PTU’s, the communications component, and each C2 User Interface.

Non-mission critical components include the laser illuminator, spotlight, loud hailer, and Obscurant device.

Mission Elements of CBP: Predict, Deter, Detect, Track, Identify/Classify, Respond, and Resolve (Objective 1.1 in CBP’s 2009-2014 Strategic Plan).

Moving IoI: Any IoI having a lateral, closing, or opening rate of motion, which equals or exceeds 0.15 meters per-second.

Near Real Time: A low-latency time delay of approximately one-half second (i.e. 500 (O) to 750 (T) milliseconds).

Nine camera types: (1) Short Range (SR) Electric Optical (EO), (2) SR Infrared (IR), (3) Medium Range (MR) EO,

(4) Medium Range IR, (5) Long Range (LR) EO, (6) LR IR, (7) Wide Angle (WA) EO, (8) WA IR and (9) LR High Performance EO.

Number of RVSS/Integrated Fixed Tower (IFT)/Maritime Detection Program (MDP) Units: A single System is comprised of a number of RVSS/IFT/MDP units, numbering as few as 1 (Qty) to as many as 30 Qty (T), 50 Qty (O) RVSS/IFT/MDP units. A single System may be composed of a single unit type or any combination of unit types.

“Object of Minimum Size”: Defined as the cross-sectional dimensions of 1.5 meters high x 0.5 meters wide.

This is equivalent to an average sized human.

Operational Availability (Ao): The percentage of time that a system will be available to perform its operational functions; Ao = (Mission Capable Time) / (Total Time). To determine how to increase availability, the components of Total Time (i.e., up time plus down time) must be quantified. Up time is simply Mission Capable Time or Mean Time Between Maintenance (MTBM). Down time is the sum of MTTR and Mean Logistics Down Time (MLDT). Therefore, the formula for predicting Ao can be written as Ao = (MTBM) / (MTBM+MTTR+MLDT) =

(MTBM) / (MTBM + MDT).

Operator: CBP person using the RVSS C2 User Interface.

Panoramic: An unobstructed and wide view of an extensive area in all directions.

Platform: RVSS structure to which an RVSS Upgrade unit is mounted and strategically placed throughout the assigned AoR.

Quality & Resolution: Is the accurate reproduction of the scene captured by the imaging device, which does not contain noticeable distortion, degradation, noise, or artifacts.

Remote Environment: Border areas characterized by very low population densities and limited transportation infrastructure/inadequate access. Terrain varies from flat to mountains and canyons, sparse to heavily vegetation. Time available for agents to respond to a threat is measured in hours to days.

FAALC/CBP P a g e | 18

For Official Use Only (FOUO)

Rural Environment: Border areas characterized by sparse population densities and limited transportation infrastructure/access. Terrain varies from flat to rolling hills; vegetation varies from sparse to dense. Time available for agents to respond to a threat is measured in minutes to hours.

RVSS Upgrade unit: Consists of the platform, sub-platform, and sensor suite (i.e. cameras).Short Range (SR): A camera typically used in an Urban environment; is capable of displaying usable images from its minimum effective surveillance range out to 1 mi (T), 3 miles (O).

Site: Is geographic location of the permanent structure and all components of the platform, sub-platform and supporting infrastructure.

Slew: To pan and/or tilt the imaging sensors.

Spotlight: A strong beam of visible light, which can be focused to illuminate a small area.

Survive: To function normally after exposure to extreme conditions (e.g., extreme cold/heat, lighting storms, and physical abuse). May require maintenance action.

System Component: Component is an identifiable part of a larger system that provides a particular function.

Tall Structure: Structures that are suitable to mount a Sensor Suite, i.e. tall building, tower, and rooftop.

Targeted Area: Same as Area of Interest (AoI).

Typical Operating Conditions (OCt): Operating conditions typically encountered in and around the area of responsibility. These conditions include environmental lighting (i.e., daylight, darkness, and twilight), weather, and LoS obstructions such as prevailing dust, smoke, and atmospheric optical turbulence. OCt is detailed in the Operating Environment in Section 3.0 of this document.

Twilight: Is the condition between daylight and darkness.

Urban Environment: Areas on the U.S. border with “built-up” characteristics such as industrial, business, commercial, and residential infrastructure that may provide quick access to safe houses and transportation.

Terrain varies from flat to rolling hills, vegetation generally sparse, but clutter high. Time available for agents to respond to a threat is measured in seconds to minutes.

Usable Image: An image having quality, resolution, and context to orient and enable the Operator to detect and identify/classify an IoI located in the camera’s FOV and DOF.

U.S. Border: Borders of U.S./Canada; and U.S./Mexico.

Video: Sequential or continuous streaming of images that appear unbroken to the human eye, typically at specified temporal rates greater than 24 frames/second (Hertz). It does not differentiate between digital and analog.

Video Analytics: The System shall automatically detect and track the imagery of an IoI moving at least 0.15 meters/second [16] within the camera’s FOV.

Viewshed: Area of water, land, and/or other environmental element visible from a fixed vantage point.

Walking speed of an averaged size adult: On a prepared surface is estimated to be 3 mph. The 0.15 m/sec (0.33 mph) equates to the same sized adult walking cautiously in low light condition through a rugged area similar to the Sonoran desert environment at the US Borders.

Wide Angle: – a video image that is spatially continuous, fixed, wide (up to 180 degree) FOV, such as for the border region of interest; field of view approximating that of the human eye (about 160 x 75 degrees); or an image which is at least twice as wide as it is high.

Wide Angle (Panoramic) camera: Camera best suited for wider than normal FOV while providing image details or characteristics important to the Operator; has effective optical range of 0.50 miles or less.