2025-10-24 Draft M2S2 Capability Requirements Matrix.xlsx
XLSX spreadsheet 57 KB Posted
- Attached to
- Modular Mobile Surveillance System (M2S2)
- Solicitation number
- 2026-CBP-M2S2
About this file
This document is a Draft M2S2 Capability Requirements Matrix detailing comprehensive technical requirements for a Modular Mobile Surveillance System (M2S2) for U.S. Customs and Border Protection (CBP). The extensive matrix contains 271 specific system requirements across categories including detection, tracking, autonomy, communication, operator interface, power, safety, security, and environmental conditions. Each requirement is currently marked as "System does not meet requirement" with "Not Applicable" evidence of compliance, suggesting this is a draft capability assessment document for potential system development or procurement.
The requirements cover detailed technical specifications such as autonomous detection capabilities, sensor performance, communication protocols, environmental operating conditions, and system interoperability. Key performance areas include detecting and tracking items of interest (IoIs) at various ranges, operating in diverse environmental conditions from -17°F to 124°F, supporting remote and urban environments, providing robust communication and data management capabilities, and meeting stringent security and safety standards. The document is part of a pre-solicitation process for a potential multiple-award blanket purchase agreement with a planned solicitation in the 2nd quarter of FY 2026, covering a 10-year period of performance.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| CBP Request for Expedited GSA Schedule Processing - M2S2.pdf | ||
| 2026-01-27 Draft M2S2 Acquisition Strategy.docx | DOCX document | |
| 2026-01-27 M2S2 Gov Responses to Vendor Questions.xlsx | XLSX spreadsheet | |
| 2025-10-24 Draft Vendor Proposed M2S2 Modularity Objectives.docx | DOCX document | |
| 2025-10-24 Draft_M2S2_CDRL_DID_Forms.docx | DOCX document | |
| 2025-10-24 Draft M2S2 Statement of Work.docx | DOCX document | |
| 2025-10-24 M2S2 Vendor Questions - Comments Spreadsheet Template.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
M2S2 Functional Requirements
| The below Contractor claims will be incorporated into the awarded BPA as system requirements to be achieved for both testing and operational performance |
| 1.) Vendor shall select the accurate Contractor's System Requirement Compliance for each system requirement |
| 2.) Vendor shall input accurate Contractor's System Performance Capability to indicate the system's specific threshold or objective metric (only for unblocked cells / 10 characters max.) |
| 3.) Vendor shall select the highest level of Evidence of System Compliance achieved for each system requirement |
| M2S2 Functional Requirements | ||||||
| FRD # | FRD Capability Category | FRD Requirement | Contractor's System Requirement Compliance | Contractor's System Peformance Capability | Evidence of System Compliance | |
| 1 | Detection | The system shall be able to autonomously detect moving IoI 1-50 mph located within the sensor's field of view (FOV) without operator intervention. | System does not meet requirement | Not Applicable | ||
| 2 | Detection | The system shall autonomously detect no less than 90% (T), 95% (O) of IoIs within the surveillance area with a confience level of 85% or higher. | System does not meet requirement | Not Applicable | ||
| 3 | Detection | The system shall allow the operator to establish sensor detection and sensitivity parameters (excluding radar) in relation to sensor detection capabilities. | System does not meet requirement | Not Applicable | ||
| 4 | Identification | The system shall allow the operator to change detection priorities by IoI classification from the C2. | System does not meet requirement | Not Applicable | ||
| 5 | Tracking | The system shall autonomously determine track data for an IoI (including current speed, current heading, current location in geo-coordinates, and track duration). | System does not meet requirement | Not Applicable | ||
| 6 | Tracking | The system shall allow the operator to manually track IoIs moving within the camera field of regard (FoR). | System does not meet requirement | Not Applicable | ||
| 7 | Illuminating | The illumination/designation area shall be within a radius of 10 feet from the IoI's true physical location. | System does not meet requirement | Not Applicable | ||
| 8 | Illuminating | The illuminator beam shall be visible to agents wearing CBP-issued night vision goggles (NVG). | System does not meet requirement | Not Applicable | ||
| 9 | Illuminating | The system shall mark the position of any selected IoI such that the mark is invisible to the unaided eye. | System does not meet requirement | Not Applicable | ||
| 10 | Range | The system shall determine the range of a single, selected IoI. | System does not meet requirement | Not Applicable | ||
| 11 | Autonomy | The system shall fuse IoI surveillance data, BPA, and other law enforcement data into a unified dataset with in 0.5 seconds. | System does not meet requirement | Not Applicable | ||
| 12 | Autonomy | The system shall enable the operator to customize the autonomous interrogation duration of an IoI between 1 second and 60 seconds. | System does not meet requirement | Not Applicable | ||
| 13 | Autonomy | The system shall be able to autonomously identify moving IoI located within the sensor's field of view (FOV) without operator intervention. | System does not meet requirement | Not Applicable | ||
| 14 | Autonomy | The system shall provide the capability to autonomously slew camera sensors to interrogate multiple detections in a queue. | System does not meet requirement | Not Applicable | ||
| 15 | Operator Interface | The system shall display the geographic location of a selected IoI. | System does not meet requirement | Not Applicable | ||
| 16 | Operator Interface | The system shall allow the operator to select detections in the queue to display a visual cue of the location of the selected detection. | System does not meet requirement | Not Applicable | ||
| 17 | Operator Interface | The system shall enable the operator to create presets of latitude /longitude locations. | System does not meet requirement | Not Applicable | ||
| 18 | Operator Interface | The system's controls and displays shall be readable under all lighting conditions of the operating environment. | System does not meet requirement | Not Applicable | ||
| 19 | Operator Interface | The system shall enable the operator to simultaneously display live videos and recorded videos. | System does not meet requirement | Not Applicable | ||
| 20 | Panning and Tilting sensors/Devices | The system shall provide the radar with 360 degrees of coverage about its vertical axis. | System does not meet requirement | Not Applicable | ||
| 21 | Panning and Tilting sensors/Devices | The system shall be capable of continuous tracking and recording of the IoI located anywhere within the FoR. | System does not meet requirement | Not Applicable | ||
| 22 | Panning and Tilting sensors/Devices | The EO/IR cameras, laser illuminator, and laser range finder shall be capable of 360 degrees continuous rotation about its vertical axis in both directions. | System does not meet requirement | Not Applicable | ||
| 23 | Panning and Tilting sensors/Devices | The system shall be capable of dynamic performance in the entire 360⁰ degrees horizontal FoR and +/- 45⁰ degrees vertical FoR. | System does not meet requirement | Not Applicable | ||
| 24 | Panning and Tilting sensors/Devices | The system shall determine and display the real-time pitch and roll angles of the system with an accuracy of ±1 degree. | System does not meet requirement | Not Applicable | ||
| 25 | Power | The vehicle shall be capable of charging the power subsystem without an external generator by running the vehicle's power system at engine idle speed. | System does not meet requirement | Not Applicable | ||
| 26 | Communication | The system shall allow local LMR agent communications in and around the system site, line of sight viewshed permitting. | System does not meet requirement | Not Applicable | ||
| 27 | Communication | The system shall provide an extension of the current fixed LMR agent communication system, line of sight permitting. | System does not meet requirement | Not Applicable | ||
| 28 | Communication | The system shall operate without interference or degradation to existing CBP backhaul communication and surveillance systems. | System does not meet requirement | Not Applicable | ||
| 29 | Communication | The system shall be able to send data to and receive data from an operator via bidirectional TAK. | System does not meet requirement | Not Applicable | ||
| 30 | Communication | The system shall have the capability to operate with the government approved communication systems. | System does not meet requirement | Not Applicable | ||
| 31 | Communication | The system shall automatically display Blue Force presence and location (when and where Blue Force is available). | System does not meet requirement | Not Applicable | ||
| 32 | Communication | The system shall transmit surveillance data at a minimum resolution of 1080p to ensure the operator can view the image to execute the METs. | System does not meet requirement | Not Applicable | ||
| 33 | Communication | The system shall be able to send data to and recevice data from authorized government personnel. | System does not meet requirement | Not Applicable | ||
| 34 | Remote Operation | The system shall enable authorized personnel to remotely access and exercise full operational control of the sensor suite. | System does not meet requirement | Not Applicable | ||
| 35 | Installation Kit | The installation kit shall enable the system to be installed and uninstalled on the M2S2 truck fleet. | System does not meet requirement | Not Applicable | ||
| 36 | Usability | The system shall provide a manual method of lowering the mast from its maximum raised position to its fully stowed position within 15 minutes without the use of primary power. | System does not meet requirement | Not Applicable | ||
| 37 | Usability | The operator interface shall display the system's battery voltage, current, state of charge, time to full charge, and time to full discharge. | System does not meet requirement | Not Applicable | ||
| 38 | Usability | The system shall enable the operator to control all features of the system and its subsystems while located inside the vehicle cab. | System does not meet requirement | Not Applicable | ||
| 39 | Usability | The system shall enable the operator to perform all functions from within the cab to transition the system from a mission-ready state to a transport-ready state. | System does not meet requirement | Not Applicable | ||
| 40 | Usability | The system shall enable the operator to perform all functions from within the cab to transition the system from a transport-ready state to a mission-ready state. | System does not meet requirement | Not Applicable | ||
| 41 | Usability | The system shall display system health and status of line replaceable units (LRU) at the operator interface when prompted by the operator. | System does not meet requirement | Not Applicable | ||
| 42 | Usability | The system shall record all video and sensor data immediately upon detection of an IoI within the sensor's FOV. | System does not meet requirement | Not Applicable | ||
| 43 | Alerting and Reporting | The system shall be hardened against physical vandalism that adversely affects system performance. | System does not meet requirement | Not Applicable | ||
| 44 | Alerting and Reporting | The system shall be hardened against non-physical attacks (e.g., jamming, cyberattack, electrical attack, etc.). | System does not meet requirement | Not Applicable | ||
| 45 | Alerting and Reporting | The system shall include a safety mechanism that prevents mast deployment when the overhead alarm is activated and the corresponding warning is displayed. | System does not meet requirement | Not Applicable | ||
| 46 | Alerting and Reporting | The system shall sound and display initial warning to the operator of overhead obstruction (e.g., power lines, bridges, tree branches, awnings, etc.) which may damage the system when the mast is not in the transport-ready position. | System does not meet requirement | Not Applicable | ||
| 47 | Alerting and Reporting | The system shall alert the operator of IoIs approaching the operator defined security boundary of the physical system. | System does not meet requirement | Not Applicable | ||
| 48 | Alerting and Reporting | The system shall allow an operator to control alert notification methods. | System does not meet requirement | Not Applicable | ||
| 49 | Alerting and Reporting | The system shall alert the operator of non-physical attacks (e.g., jamming, cyberattack, electrical attack, etc.) on the system. | System does not meet requirement | Not Applicable | ||
| 50 | Alerting and Reporting | The system shall provide the operator with three selectable alert methods: audible only, visual only, and audible and visual both. | System does not meet requirement | Not Applicable | ||
| 51 | Alerting and Reporting | The sensor configuration shall provide a near-real-time indicator to the operator of all system sensors status. | System does not meet requirement | Not Applicable | ||
| 52 | Alerting and Reporting | The system shall produce audio and visual alerts to the operator upon detection of an IoI. | System does not meet requirement | Not Applicable | ||
| 53 | Alerting and Reporting | The system shall allow manual override of visual and/or audible radar alerts. | System does not meet requirement | Not Applicable | ||
| 54 | Alerting and Reporting | The system shall continuously monitor its performance, and detect faults in real-time. | System does not meet requirement | Not Applicable | ||
| 55 | Processing Data | The system shall perform real-time video analysis locally on the truck using onboard processing capabilities. | System does not meet requirement | Not Applicable | ||
| 56 | Processing Data | The system shall create metadata, including: a timestamp of the video recording with the date and time (HH:MM:SS.SSS); the magnetic bearing of the sensor’s direction; the latitude/longitude coordinates of the operator-selected IoI; the unique identification number of an IoI; sensor position and angle; all “on-screen”; and the zoom ratio. | System does not meet requirement | Not Applicable | ||
| 57 | Processing Data | The system shall store video at a quality and resolution no less than that originally displayed at the operator interface. | System does not meet requirement | Not Applicable | ||
| 58 | Processing Data | The system shall automatically store presets with an unique name. | System does not meet requirement | Not Applicable | ||
| 59 | Processing Data | Operators shall have the ability to place a marker and/or add notes to data that will aid searching for a specific event in support of ongoing operations and post-event analysis. | System does not meet requirement | Not Applicable | ||
| 60 | Data Management | The system shall enable only authorized personnel to export extracted video, individual frames, and associated metadata to CBP secured and authorized cloud-based services with authorized access control. | System does not meet requirement | Not Applicable | ||
| 61 | Data Management | The system shall enable only authorized personnel to export extracted video, individual frames, and associated metadata to CBP secured and authorized external media sources using a CBP approved USB interface. | System does not meet requirement | Not Applicable | ||
| 62 | Data Management | The system shall allow the operator the capability to tag recorded video and associated metadata. | System does not meet requirement | Not Applicable | ||
| 63 | Data Management | The system shall allow the operator to retrieve recorded video and individual frames with associated metadata. | System does not meet requirement | Not Applicable | ||
| 64 | Data Management | The system shall be able to continuously record metadata. | System does not meet requirement | Not Applicable | ||
| 65 | Data Management | The system shall apply the CoT standard for machine-to-machine communications with the C2CEN. | System does not meet requirement | Not Applicable | ||
| 66 | Data Management | The battery health system shall monitor and report the state of health status with at least 95% accuracy at a minimum update rate of once per minute during operation. | System does not meet requirement | Not Applicable | ||
| 67 | Data Management | The battery health system shall monitor and report the state of charge status with at least 95% accuracy at a minimum update rate of once per minute during operation. | System does not meet requirement | Not Applicable | ||
| 68 | Data Management | The battery health system shall have high and low-capacity alarm functions with at least 95% accuracy, at a minimum update rate of once per minute during operation. | System does not meet requirement | Not Applicable | ||
| 69 | Data Management | The battery health system shall monitor and report battery voltage and with at least 95% accuracy at all times during operation. | System does not meet requirement | Not Applicable | ||
| 70 | Error Handling | The system shall employ device self-checks (upon start-up and every 4 hours thereafter) to alert the operator of system problems. | System does not meet requirement | Not Applicable | ||
| 71 | Error Handling | The system shall allow the operator to run system diagnostics checks. | System does not meet requirement | Not Applicable | ||
| 72 | Transportability | The total weight of the system (combined passengers, gear, extra fuel, surveillance sensors, mast, and skids) shall not exceed 75% of the vehicle’s original equipment manufacturer payload specification. | System does not meet requirement | Not Applicable | ||
| 73 | Transportability | The payload on the mast shall not exceed the payload capacity of the mast. | System does not meet requirement | Not Applicable | ||
| 74 | Availability | The system shall operate, without operational degradation, as specified within the environment described in the M2S2 ORD Table 8 Environmental Conditions, Column B Operational Environmental Conditions. *REFER TO ENVIRONMENTAL TAB | System does not meet requirement | Not Applicable | ||
| 75 | Availability | The system shall operate without operational degradation, as specified within the non-operationally generated environment described in the M2S2 ORD Table 8 Environmental Conditions, Column C Survival Environmental Conditions. *REFER TO ENVIRONMENTAL TAB | System does not meet requirement | Not Applicable | ||
| 76 | Availability | The system shall operate, without operational degradation, as specified within the operationally generated environment described in the M2S2 ORD Table 9 Terrain Attributes.*REFER TO ENVIRONMENTAL TAB | System does not meet requirement | Not Applicable | ||
| 77 | Availability | The vendor shall specify the maximum safe speed and average speed at which the vehicle can operate under the following terrain conditions: | ||||
| • | Gravel and clay roads with slopes up to 3 percent. | |||||
| • | Moderately severe terrain with limited washboard, potholes, water erosion, rock formations, and sharp sweeping turns. | |||||
| • | Moderately severe terrain with Belgium Block. | |||||
| • | Moderately severe terrain with six-inch washboards. | |||||
| • | Moderately severe terrain with two-inch washboards. | |||||
| • | Moderately severe terrain with radial washboards. | |||||
| *REFER TO ENVIRONMENTAL TAB | System does not meet requirement | Not Applicable | ||||
| 78 | Maintainability | The system shall be capable of being maintained by trained maintenance technicians at each sector/station. | System does not meet requirement | Not Applicable | ||
| 79 | Maintainability | The system shall continuously record system reliability, availability and maintainability (RAM) data. | System does not meet requirement | Not Applicable | ||
| 80 | Maintainability | The system shall allow retrieval of RAM data by authorized personnel. | System does not meet requirement | Not Applicable | ||
| 81 | Serviceability | The sensor shall be transferable on and off of a vehicle with the use of commonly available equipment or lifting tools, such as forklift, hoist, and overhead crane/boom. | System does not meet requirement | Not Applicable | ||
| 82 | Security | The system shall have the mechanism to implement backup and restore procedures for all non-sensitive IT systems, data, and information. | System does not meet requirement | Not Applicable | ||
| 83 | Security | The C2 system shall include diagnostic capability to identify the subsystem's alerts and faults. | System does not meet requirement | Not Applicable | ||
| 84 | Security | The system shall include a diagnostic capability to support a user’s ability to continue the mission while under cyberattack | System does not meet requirement | Not Applicable | ||
| 85 | Security | The system shall comply with the controls within DHS Sensitive system Policy Directive 4300A (current version), CBP HB 1400-05D, Information systems Security Policies and Procedures (current version) and NIST SP 800-53 (r5) for appropriate moderate security categories. | System does not meet requirement | Not Applicable | ||
| 86 | Security | The system shall control and limit user access based on authentication mechanisms that support the requirements of access control, least privilege, and system confidentially and integrity. | System does not meet requirement | Not Applicable | ||
| 87 | Security | The system shall enable only authorized personnel to export extracted unaltered data. | System does not meet requirement | Not Applicable | ||
| 88 | Security | The system shall uniquely identify and authenticate users (or processes acting on behalf of users). | System does not meet requirement | Not Applicable | ||
| 89 | Interoperability | The system shall operate without EMI when LMR and TAK are installed and operating simultaneously. | System does not meet requirement | Not Applicable | ||
| 90 | Interoperability | The system functional software upgrades shall be structured as non-destructive updates to the previous software version. | System does not meet requirement | Not Applicable | ||
| 91 | Interoperability | The sensors and system software shall come with published application program interfaces (API), software development kits (SDK), and interface control documents (ICD), as applicable. | System does not meet requirement | Not Applicable | ||
| 92 | Interoperability | The system shall allow an operator to display the locations of other assets when available. | System does not meet requirement | Not Applicable | ||
| 93 | Interoperability | The system shall support integration with current and future joint operational/mission planning, execution, reporting, and assessment systems. | System does not meet requirement | Not Applicable | ||
| 94 | Interoperability | The system shall allow an operator to receive the locations of other assets. | System does not meet requirement | Not Applicable | ||
| 95 | Interoperability | The system shall transmit, receive, ingest, and display data in CoT format. | System does not meet requirement | Not Applicable | ||
| 96 | Interoperability | The system shall be able to transmit data and receive data from CBP approved external/internal nodes (e.g. TAK server). | System does not meet requirement | Not Applicable | ||
| 97 | Interoperability | The system shall be able to autonomously transmit data to CBP approved external/internal nodes (e.g. TAK server). | System does not meet requirement | Not Applicable | ||
| 98 | Interoperability | The system shall be compliant with Federal Communications Commission (FCC) and National Telecommunications and Information Administration (NTIA) requirements. | System does not meet requirement | Not Applicable | ||
| 99 | Interoperability | All Radio Frequency (RF) emitters and electronics within the system shall operate without affecting other internal electronics or subsystems within 1 meter. | System does not meet requirement | Not Applicable | ||
| 100 | Safety | The Laser Illuminator shall have a safety mechanism to preclude inadvertent arming and firing. | System does not meet requirement | Not Applicable | ||
| 101 | Safety | The Laser Range Finder shall have a safety mechanism to preclude inadvertent arming and firing. | System does not meet requirement | Not Applicable | ||
| 102 | Autonomy | The system shall be able to integrate IoI data information from different sources (sensors) into a single unified set. | System does not meet requirement | Not Applicable | ||
| 103 | Autonomy | The system shall correctly identify a detection, 90% (T), 99% (O) as human, animal, conveyance or unknown, by sensor system, within sensor capabilities. | System does not meet requirement | Not Applicable | ||
| 104 | Autonomy | The system shall autonomously fuse detections with accuracy of at least 90% (T), 95%(O) with an 85% confidence level. | System does not meet requirement | Not Applicable | ||
| 105 | Autonomy | The system shall autonomously identify IoI(s) at a range of 1 mile (T), 3 miles (O). | System does not meet requirement | Not Applicable | ||
| 106 | Autonomy | The system shall record all human intervention (HI) in relation to IoI validation. | System does not meet requirement | Not Applicable | ||
| 107 | Autonomy | The system shall autonomously identify IoI(s) within operator defined priority zones. | System does not meet requirement | Not Applicable | ||
| 108 | Autonomy | The system shall autonomously assign a prioritization value to an IoI based on operator predefined attributes within sensor capabilities, 98% (T), 99.9% (O) of the time. | System does not meet requirement | Not Applicable | ||
| 109 | Autonomy | The system shall accurately forecast IoI movement (e.g., routes of egress, heading and estimated time of arrival) with a confidence of at least 85% within the capabilities of the sensor. | System does not meet requirement | Not Applicable | ||
| 110 | Autonomy | The system shall forecast IoI movement within 60 seconds(T); 30 seconds (O) of establishment of an IoI track. | System does not meet requirement | Not Applicable | ||
| 111 | Autonomy | The system shall autonomously correlate detections 90% (T), 99% (O) of the time when an object is in the field of view of multiple sensors. | System does not meet requirement | Not Applicable | ||
| 112 | Autonomy | The system shall autonomously identify IoI no less than 90% (T), 95% (O) within the surveillance area with an 85% confidence level. | System does not meet requirement | Not Applicable | ||
| 113 | Classify | The system shall provide imagery resolution at minimum of 1080p to allow agents to classify IoI no less than 90% (T), 95% (O) of identifications within the surveillance area with an 80% confidence level. | System does not meet requirement | Not Applicable | ||
| 114 | Classify | The system shall allow the operator to classify an IoI at a range 1 mile (T), to at least 3 miles (O) with a success rate of at least 85%. | System does not meet requirement | Not Applicable | ||
| 115 | Illuminating | The illuminator shall be aligned to within ½ of the IR sensor’s Instantaneous field of view (IFOV: single pixel FOV). | System does not meet requirement | Not Applicable | ||
| 116 | Illuminating | The illuminator modes of operation shall include "strobe" and "continuous" modes. | System does not meet requirement | Not Applicable | ||
| 117 | Illuminating | The illuminator operating mode shall be selectable by the operator from the operator Interface. | System does not meet requirement | Not Applicable | ||
| 118 | Illuminating | The illuminator shall be equipped with an automatic shut-off timer with operator adjustable duration time. | System does not meet requirement | Not Applicable | ||
| 119 | Detection | The system shall detect small moving conveyance IoIs of 0.46m^2 radar cross-section at a minimum of 2 miles (T), 5 miles (O). | System does not meet requirement | Not Applicable | ||
| 120 | Detection | The system shall provide video resolution at minimum of 1080p to allow an operator to detect the presence of a single, moving object the size of an average adult during daylight and night under typical Line of Sight (LoS) conditions at a range of 2 miles (T), 5 miles (O) with an 85% confidence level or higher. | System does not meet requirement | Not Applicable | ||
| 121 | Detection | The system shall autonomously detect IoI at a range of 2 miles or greater (T), 5 miles (O). | System does not meet requirement | Not Applicable | ||
| 122 | Identification | The Sysyem shall provide image resolution at minimum of 1080p to allow an operator to identify as human, conveyance, or animal at range of 1 mile (T), 3 miles (O) with a success rate at or above 85% confidence level. | System does not meet requirement | Not Applicable | ||
| 123 | Range | The Day sensor shall be bore sighted with the IR sensor to an accuracy of 5 angular mil (4.91 mrad, 0.281 deg), radial distance 30 m RMS at 12 km or less in Azimuth and Elevation | System does not meet requirement | Not Applicable | ||
| 124 | Range | The Laser Range finder's output shall have a range up to 5 miles with a dispersion of no greater than 10 feet on minor axis of the ellipse and shall not be visible to the unaided eye. | System does not meet requirement | Not Applicable | ||
| 125 | Tracking | The operator shall have the capability to enable/disable the sensor automatic tracking feature. | System does not meet requirement | Not Applicable | ||
| 126 | Tracking | The system shall autonomously track an IoI up to a range of 2 miles (T), 5 miles (O) with the success rate of no less than 85%. | System does not meet requirement | Not Applicable | ||
| 127 | Tracking | The system shall allow the operator the capability to surveil IoI(s) traveling at speeds up to 75 mph within the surveillance area. | System does not meet requirement | Not Applicable | ||
| 128 | Tracking | The system shall track up to 25 (T), 50 (O) IoI or groups of IoI within the FOR. | System does not meet requirement | Not Applicable | ||
| 129 | Processing Data | The system shall utilize maps that can be developed and maintained by CBP. | System does not meet requirement | Not Applicable | ||
| 130 | Processing Data | The system shall synchronize system timestamp with GPS time. | System does not meet requirement | Not Applicable | ||
| 131 | Data Management | The system shall have the ability to autonomously and manually record metadata. | System does not meet requirement | Not Applicable | ||
| 132 | Data Management | The system shall store metadata and video to be available for 15 days (T); 30 Days (O) on the cloud storage space. | System does not meet requirement | Not Applicable | ||
| 133 | Data Management | The system shall store metadata and video to be available for 15 days (T); 30 Days (O) on the Solid-State Hard Drive. | System does not meet requirement | Not Applicable | ||
| 134 | Data Management | The system shall store videos as H.265 (T) and H.266 or better (O). | System does not meet requirement | Not Applicable | ||
| 135 | Data Management | The system shall allow an authorized user to import custom map overlays in CBP identified file formats (i.e., .csv, .shp, .kml, .kmz). | System does not meet requirement | Not Applicable | ||
| 136 | Data Management | The system shall receive the secured transmission data within the system’s C2 no greater than 200 milliseconds (T), no greater than 150 milliseconds (O) response time from the sender. | System does not meet requirement | Not Applicable | ||
| 137 | Data Management | The system shall be able to track utilization rate of the Command and Control system. | System does not meet requirement | Not Applicable | ||
| 138 | Alerting and Reporting | The system shall alert the operator when there is 20% system battery power remaining. | System does not meet requirement | Not Applicable | ||
| 139 | Alerting and Reporting | The system IoI tracking latency shall be ≤0. 5 sec. | System does not meet requirement | Not Applicable | ||
| 140 | Operator Interface | The operator Interface shall display whether the Illuminator is in continuous or strobe mode. | System does not meet requirement | Not Applicable | ||
| 141 | Operator Interface | The operator Interface shall display whether the Illuminator is ON or OFF. | System does not meet requirement | Not Applicable | ||
| 142 | Operator Interface | The system shall determine its geographic location in Longitude/Latitude and elevation within a 5 ft. radius, of its actual position 90% of the time. | System does not meet requirement | Not Applicable | ||
| 143 | Operator Interface | The sensor configuration shall determine the geographic coordinates of a selected IoI that is within a circular error probable of 250 ft. (T), 50 feet (O) of the IoI's physical location, at a distance of 2 miles (T) and 5 miles (O) from the system. | System does not meet requirement | Not Applicable | ||
| 144 | Operator Interface | The operator Interface shall enable the operator to enable/disable the Autonomous Mode detection feature. | System does not meet requirement | Not Applicable | ||
| 145 | Operator Interface | The system shall enable the operator to select IoIs within sensors' FOV for tracking. | System does not meet requirement | Not Applicable | ||
| 146 | Operator Interface | The system shall enable the operator to select an item on the display to automatically create its preset location with a response time of no greater than 0.5 seconds. | System does not meet requirement | Not Applicable | ||
| 147 | Operator Interface | The system shall enable the operator to select a preset location to which the sensor will automatically slews to the preset location. | System does not meet requirement | Not Applicable | ||
| 148 | Operator Interface | The system shall store a minimum of 10 preset locations (T), a minimum of 20 preset locations (O). | System does not meet requirement | Not Applicable | ||
| 149 | Operator Interface | The system shall allow the operator to establish parameters and set sensitivity in relation to sensor detection capabilities. | System does not meet requirement | Not Applicable | ||
| 150 | Operator Interface | The system shall allow the operator to create alert zones, minimum 3 (T), 5 (O). | System does not meet requirement | Not Applicable | ||
| 151 | Operator Interface | The system shall enable the operator to display a list of stored preset locations that are within the FoR. | System does not meet requirement | Not Applicable | ||
| 152 | Operator Interface | The system shall enable the operator to change the name for each stored preset with at least two characters length for the name. | System does not meet requirement | Not Applicable | ||
| 153 | Operator Interface | The system shall enable the operator to delete stored preset locations. | System does not meet requirement | Not Applicable | ||
| 154 | Operator Interface | The operator Interface shall provide digital and physical interfaces to control all sensors. | System does not meet requirement | Not Applicable | ||
| 155 | Operator Interface | The system shall provide Aids that enable the operator to assess information presented at the display to include, but not limited to, compass bearing, distance, unit of measure converter and arithmetic calculator. | System does not meet requirement | Not Applicable | ||
| 156 | Operator Interface | The operator Interface shall incorporate a customizable graphical user interface which allows the operator to individually select and de-select tools and aids. | System does not meet requirement | Not Applicable | ||
| 157 | Operator Interface | The system shall allow the user to view operations/surveillance feeds and platform perimeter security feeds simultaneously. | System does not meet requirement | Not Applicable | ||
| 158 | Operator Interface | The system's C2 shall display a visual cue of the location of the autonomously detected IoI within 0.5 seconds of the system detecting an IoI. | System does not meet requirement | Not Applicable | ||
| 159 | Operator Interface | The system shall ensure the detected geolocation of the IoI is within the camera's field of view (FOV) within 1 second of initiating a slew-to-cue command across all operational modes. | System does not meet requirement | Not Applicable | ||
| 160 | Usability | The camera's resolution shall be at minimum of 1080p (T). | System does not meet requirement | Not Applicable | ||
| 161 | Usability | The system shall provide sensors' feedback to the operator Interface which presents status information, confirmation, and verification of input throughout system interactions. | System does not meet requirement | Not Applicable | ||
| 162 | Usability | The system shall respond to an operator’s control inputs of its functions within 0.5 seconds. | System does not meet requirement | Not Applicable | ||
| 163 | Usability | The system control to the sensor suite shall have a response time of no greater than 0.5 seconds within the vehicle. | System does not meet requirement | Not Applicable | ||
| 164 | Usability | The system shall allow an operator to receive imagery from camera sensor no greater than 0.5 seconds when the camera is in use within the vehicle. | System does not meet requirement | Not Applicable | ||
| 165 | Usability | The system shall have a response time no greater than 0.5 seconds from operator input control to receiving sensor response in all operating modes within the vehicle. | System does not meet requirement | Not Applicable | ||
| 166 | Usability | The system shall relinquish control to the requester if the operator does not respond within 300 seconds time limit. | System does not meet requirement | Not Applicable | ||
| 167 | Usability | The system shall allow the operator to disable autonomous mode for slew-to-cue and control the camera sensors independently. | System does not meet requirement | Not Applicable | ||
| 168 | Usability | A system shall provide video resolution at minimum of 1080p to allow an operator to detect, track, and identify the presence of a single, moving object the size of an average adult during darkness under typical LoS conditions at the following ranges: 2 mile (T) to 5 mile (O)) using the EO/IR Camera. | System does not meet requirement | Not Applicable | ||
| 169 | Usability | The system shall enable the operator to perform within the cab all functions to transition the system from a transport mode to a mission ready mode within 15 minutes (T), 5 Minutes (O) | System does not meet requirement | Not Applicable | ||
| 170 | Usability | The system shall enable the operator in the driver seat to perform within the cab all functions to transition the system from a mission ready state to a transport-ready state within 15 minutes (T), 5 Minutes (O). | System does not meet requirement | Not Applicable | ||
| 171 | Usability | The system shall enable the operator to vary the operating height/extension of the mast subsystem. | System does not meet requirement | Not Applicable | ||
| 172 | Usability | The Mast subsystem shall extend to an operating surveillance height of up to 30 feet (T), up to 40 feet (O) above ground level. | System does not meet requirement | Not Applicable | ||
| 173 | Usability | The operator Interface shall have two (2) flat panel display screens with diagonal size of at least 15 inches (T). | System does not meet requirement | Not Applicable | ||
| 174 | Usability | The system shall allow an operator to wear a standard uniform while in operation. | System does not meet requirement | Not Applicable | ||
| 175 | Usability | The system design/configuration shall incorporate Human Factors principles in the MIL-STD-1472, Design Criteria Standard: Human Engineering (15 Sep 2020) that apply directly to the system and its user interfaces. | System does not meet requirement | Not Applicable | ||
| 176 | Usability | The temperature/humidity design goal shall be between 21 °C and 25 °C (70 °F and 77 °F) and 45 percent humidity. | System does not meet requirement | Not Applicable | ||
| 177 | Communication | The system shall send the secured transmission data within the control and computer system of no greater than 200 milliseconds (T), no greater than 150 milliseconds (O) response time to the receiver. | System does not meet requirement | Not Applicable | ||
| 178 | Communication | The system shall be capable of having redundant data flow to safeguard from an inoperable tower or weak cellular signal (i.e., LTE). | System does not meet requirement | Not Applicable | ||
| 179 | Communication | The system Security risks shall be mitigated through vulnerability management, prompt system patching and anti-virus software updating on a bi-weekly basis. | System does not meet requirement | Not Applicable | ||
| 180 | Panning and Tilting sensors/Devices | The system shall enable the operator to rotate pan sensors at an angular velocity > 50⁰/sec. | System does not meet requirement | Not Applicable | ||
| 181 | Panning and Tilting sensors/Devices | The system position accuracy, repeatability and backlash shall be < 0.01⁰. | System does not meet requirement | Not Applicable | ||
| 182 | Panning and Tilting sensors/Devices | The system shall enable the operator to independently tilt sensors, excluding radar, requiring tilt's capabilities, at variable tilt speeds. | System does not meet requirement | Not Applicable | ||
| 183 | Remote Operation | The system sensors and user interface shall allow for remote operations by one trained operator outside of the vehicle at a time. | System does not meet requirement | Not Applicable | ||
| 184 | Remote Operation | The system active operator shall have the ability to retain or relinquish control to a secondary trained operator's request for remote access to the system. | System does not meet requirement | Not Applicable | ||
| 185 | Remote Operation | The onsite operator shall prioritize control of the system over any incoming remote control access requests. | System does not meet requirement | Not Applicable | ||
| 186 | Remote Operation | The system shall timeout the remote access request if the active operator does not respond within a configurable timeout period of between 1 and 120 seconds. | System does not meet requirement | Not Applicable | ||
| 187 | Power | The Power subsystem shall recharge its battery from less than or equal to 10% state of charge (SoC), defined as 10% +/- 1.0% SoC, to %100 within 8 hours (T), or 4 hours (O), under standard operating conditions. | System does not meet requirement | Not Applicable | ||
| 188 | Power | The Power subsystem shall produce no more than 42 dbA (Leq (Equivalent Continuous Noise Level) over 1 minute) (T), no more than 32 dbA (Leq over 1 minute) (O) at 7 meters away from the source when operating at full capability. | System does not meet requirement | Not Applicable | ||
| 189 | Power | The system with any combination of active sensors shall continue mission critical functions for no less than 8 hours (T), no less than 16 hours (O) without recharge. | System does not meet requirement | Not Applicable | ||
| 190 | Robustness | The system shall operate without Operational degradation while performing health and status checks or device self-checks. | System does not meet requirement | Not Applicable | ||
| 191 | Robustness | The system shall prevent damage to the system when the vehicle is traveling between thick vegetation and low hanging tree branches. | System does not meet requirement | Not Applicable | ||
| 192 | Robustness | The system shall be stabilized in all operating modes. | System does not meet requirement | Not Applicable | ||
| 193 | Compatibility | The system shall be powered independently of the vehicle's starter battery. | System does not meet requirement | Not Applicable | ||
| 194 | Compatibility | The system shall not interfere with convenience functions of the truck vehicle including, but not limited to: access to vehicle operating components such as glove box, fuse boxes, spare tires, lug wrenches, vehicle jacks and other vehicle accessories. | System does not meet requirement | Not Applicable | ||
| 195 | Compatibility | The system shall enable users to operate the system in lights-out/black-out mode. | System does not meet requirement | Not Applicable | ||
| 196 | Compatibility | The system shall be capable of transport on one 4x4 pick-up truck. | System does not meet requirement | Not Applicable | ||
| 197 | Compatibility | The operator Interface shall operate without interfering with the operator's view of the surveillance area through the vehicle's windshield | System does not meet requirement | Not Applicable | ||
| 198 | Compatibility | The operator Interface shall be configured to not impede the operator's and passenger's (if any) ability to enter and exit the vehicle cab. | System does not meet requirement | Not Applicable | ||
| 199 | Compatibility | The operator Interface shall be configured to not interfere with the driver's ability to operate the vehicle and LMR during transport. | System does not meet requirement | Not Applicable | ||
| 200 | Compatibility | The system shall not interfere with or degrade safety features of the Government Furnished Equipment (GFE). | System does not meet requirement | Not Applicable | ||
| 201 | Transportability | The system, in its stowed position, shall be < 2 inches above the top of the truck's cab and fit inside the length and width of the vehicle' s bed. | System does not meet requirement | Not Applicable | ||
| 202 | Reliability | The system shall have an optimum cost-wise readiness (CWR) mean time between failures (MTBF) of 240 hours. | System does not meet requirement | Not Applicable | ||
| 203 | Reliability | The system shall have a mean time between critical failure (MTBCF) of 240 hours (T), 360 hours (O). | System does not meet requirement | Not Applicable | ||
| 204 | Reliability | The cable and wire harness assemblies for the system shall be fabricated and tested in accordance with IPC/WHMA-A-620. | System does not meet requirement | Not Applicable | ||
| 205 | Reliability | The system shall provide the operator the vehicle's engine cycle status for maintenance | System does not meet requirement | Not Applicable | ||
| 206 | Reliability | The system shall provide the operator the mast cycle status for maintenance. | System does not meet requirement | Not Applicable | ||
| 207 | Reliability | The cable and wire harness assemblies for the system shall be fabricated with a maximum of 3% voltage drop. | System does not meet requirement | Not Applicable | ||
| 208 | Reliability | The system shall have a 96.5% probability or greater of completing 8-hours of operation without a critical failure. | System does not meet requirement | Not Applicable | ||
| 209 | Availability | The system shall have an operational availability (Ao) equal to or greater than 90% (T), 99% (O). | System does not meet requirement | Not Applicable | ||
| 210 | Availability | The system shall have a material availability (Am) equal to or greater than 75% (T) 95% (O), where Am is defined as system uptime divided by the sum of system uptime and system downtime. | System does not meet requirement | Not Applicable | ||
| 211 | Availability | The system shall have an optimum CWR materiel availability of 90%. | System does not meet requirement | Not Applicable | ||
| 212 | Availability | The system shall have an optimum CWR mean down time (MDT) of 8 hours. | System does not meet requirement | Not Applicable | ||
| 213 | Availability | The system shall track and log utilization metrics, including but not limited to operational hours, mileage, usage frequency, and performance data. | System does not meet requirement | Not Applicable | ||
| 214 | Availability | The system shall have an achieved availability (AA) of at least 90% (T), or at least 95% (O), where AA = MTBM/(MTBM + MMT). | System does not meet requirement | Not Applicable | ||
| 215 | Maintainability | The system shall provide real-time audible and visual alerts for any component failures, including detailed fault codes to facilitate root cause determination. | System does not meet requirement | Not Applicable | ||
| 216 | Maintainability | The system shall be capable of diagnosing issues with surveillance equipment, vehicle engine, and other critical systems. | System does not meet requirement | Not Applicable | ||
| 217 | Maintainability | The system shall allow authorized personnel to replace failed components at the lowest replaceable unit. | System does not meet requirement | Not Applicable | ||
| 218 | Maintainability | The system shall allow authorized personnel to install it on a vehicle within the current CBP fleet. | System does not meet requirement | Not Applicable | ||
| 219 | Maintainability | The system shall maintain RAM data for 15 days (T), 45 days (O). | System does not meet requirement | Not Applicable | ||
| 220 | Maintainability | The system shall have a mean time to repair (MTTR) of less than 8 hours (T), 4 hours (O). | System does not meet requirement | Not Applicable | ||
| 221 | Maintainability | The system shall have preventative maintenance performed at a maximum occurrence of twice (T), or once (O) each month. | System does not meet requirement | Not Applicable | ||
| 222 | Maintainability | The system shall have preventive maintenance completed in 8 hours (T), 4 hours (O). | System does not meet requirement | Not Applicable | ||
| 223 | Serviceability | The sensor shall be transferable from one vehicle to another vehicle by no more than two personnel. | System does not meet requirement | Not Applicable | ||
| 224 | Serviceability | The sensor shall be transferred from one vehicle to another vehicle and be full mission capable (FMC) in under 8 hours (T), in under 4 hours (O). | System does not meet requirement | Not Applicable | ||
| 225 | Interoperability | The system shall include common hardware interface and reusability with all sensor configurations. | System does not meet requirement | Not Applicable | ||
| 226 | Interoperability | The system shall enable authorized personnel to perform a full configuration swap, including physical sensor replacement and software reconfiguration, within a maximum time of 1 hour (T), 30 minutes (O). | System does not meet requirement | Not Applicable | ||
| 227 | Interoperability | The system's software interface shall accommodate all sensor configurations. | System does not meet requirement | Not Applicable | ||
| 228 | Interoperability | The following configuration items shall be consistent across all variants: electrical connections, power supplies, sensor interface modules, quick disconnect plates, and skid mounting. | System does not meet requirement | Not Applicable | ||
| 229 | Interoperability | Any combination of modular components shall not degrade overall system performance or operational availability | System does not meet requirement | Not Applicable | ||
| 230 | Interoperability | Any combination of modular components shall support full operational capability throughout the mission duration and system lifecycle. | System does not meet requirement | Not Applicable | ||
| 231 | Interoperability | The system shall be configurable so that authorized personnel have the capability to reconfigure the system. | System does not meet requirement | Not Applicable | ||
| 232 | Interoperability | The system shall be open architecture compliant (T), integrated sensor architecture (ISA) compliant (O). | System does not meet requirement | Not Applicable | ||
| 233 | Interoperability | The system shall support full integration with a cloud-based USBP C2CEN that provides sensor fusion and correlation, sensor command and control, video storage, and the application of algorithms to sensor data. | System does not meet requirement | Not Applicable | ||
| 234 | Interoperability | The system shall implement an open architecture using non-proprietary data standards that enables integration of algorithms. | System does not meet requirement | Not Applicable | ||
| 235 | Interoperability | The system shall allow an operator to send IoI information to responding Agents, in a CBP defined format. | System does not meet requirement | Not Applicable | ||
| 236 | Security | The system shall be resilient to data manipulation attacks. | System does not meet requirement | Not Applicable | ||
| 237 | Security | The system shall deny personnel the ability to modify recorded data under any circumstances. | System does not meet requirement | Not Applicable | ||
| 238 | Security | The system shall maintain separate access privileges. | System does not meet requirement | Not Applicable | ||
| 239 | Security | The system shall employ security protocols to define the key internal boundaries of the information system. | System does not meet requirement | Not Applicable | ||
| 240 | Security | The system shall provide the capability and capacity to record all events that occur within all layers of the system (e.g., operating system, application, network, and middleware database, and system logs) and maintain these event logs as per retention requirements for minimum of 15 days (T), 30 days (O). | System does not meet requirement | Not Applicable | ||
| 241 | Security | The system shall comply with all applicable DHS/CBP policy, standards, and guidance. Applicable policy includes NIST SP 800-53r5, DHS 4300A, and CBP HB 1400-05D. | System does not meet requirement | Not Applicable | ||
| 242 | Security | The system shall protect data during transport and at rest in compliance with FIPS 140-2 (T), 140-3 (O). | System does not meet requirement | Not Applicable | ||
| 243 | Security | The system shall incorporate physical protection measures compliant with DHS Sensitive systems Policy Documents 4300A (Sections 4.2-Physical Security, 4.3-Media Controls, and 4.8.2-Laptop Computers and Other Mobile Computing Devices). | System does not meet requirement | Not Applicable | ||
| 244 | Security | The system shall comply with DHS Enterprise Architecture and DHS Security Architecture. | System does not meet requirement | Not Applicable | ||
| 245 | Security | The system shall allow for the ability to enforce a configurable limit of consecutive invalid access attempts by a user, and automatically lock an account when the maximum number of unsuccessful access attempts is exceeded | System does not meet requirement | Not Applicable | ||
| 246 | Security | The system shall allow for the ability for a password to automatically reset after a configurable amount of time. | System does not meet requirement | Not Applicable | ||
| 247 | Security | The system shall uniquely authenticate users and processes acting on behalf of users to support non-repudiation of activity. | System does not meet requirement | Not Applicable | ||
| 248 | Security | The system shall support multi-factor authentication using CBP Personal Identity Verification (PIV) card technology or other CBP policy approved technology and implementation standards. | System does not meet requirement | Not Applicable |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .