2026-01-27 M2S2 Gov Responses to Vendor Questions.xlsx
XLSX spreadsheet 52 KB Posted
- Attached to
- Modular Mobile Surveillance System (M2S2)
- Solicitation number
- 2026-CBP-M2S2
About this file
This file is a Government Responses to Vendor Questions document addressing 68 inquiries and comments regarding the draft M2S2 Statement of Work and Capability Requirements Matrix. The responses clarify technical requirements, definitions, and procurement parameters for the Modular Mobile Surveillance System (M2S2) acquisition by U.S. Customs and Border Protection (CBP).
Key clarifications include: the M2S2 system will be mounted on a Government-furnished Ford F250 4X4 short bed truck (2025 or newer, with Government reserving the right to change the vehicle make); near-real-time response is defined as 0.50 seconds or less; radar coverage must achieve the 360-degree objective per Functional Requirement #20; the system must enable full in-cab operator control of all sensor systems, user interface, and mast functions; mast height in stowed position shall not exceed 7 feet and fit within the vehicle bed length and width; configuration swaps including physical sensor replacement and software reconfiguration must be completed within 8 hours (threshold) and 4 hours (objective); autonomous functions may include automated sensor slewing and mission tasking without operator input; the system must integrate with Motorola APX 8500 and APX 5000 P25 LMR radios and CBP network systems; and authorized personnel performing reconfigurations include CBP/USBP agents, engineers, Government contractors, system administrators, and maintenance technicians. The Government declined to release updated draft documents prior to final RFP release and confirmed that vendors must have their M2S2 systems on a GSA schedule to submit quotes for the anticipated April 2026 posting on GSA eBuy. The intended contract is a multiple-award blanket purchase agreement with firm fixed price terms, covering one 12-month base period and four 12-month option periods.
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 | |
| 2025-10-24 Draft M2S2 Capability Requirements Matrix.xlsx | XLSX spreadsheet | |
| 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 | |
| 2025-10-24 Draft Vendor Proposed M2S2 Modularity Objectives.docx | DOCX document |
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
All Comments
| The released solicitation will supersede these Government responses, any prior communications, correspondence, or draft documents related to this requirement. All terms, conditions, and requirements will be provided in the released solicitation. | |||||
| Comment Number | Document | Document Section | Page Number | Question / Comment | Government Responses |
| 1 | - | - | - | Is there a timeline from notification of award to delivery of Unit 1? | Current timeline, subject to change, is approximately 1 month from contract award to delivery of first test unit. |
| 2 | USBP-PMO-M2S2-01-000007 |
PR Number: 20154536
| Draft M2S2 SOW | 5.9.2 | 25 | Is the 4x4 vehicle defined by the Government or by the vendor? I.E. if the Government decides to furnish the vehicle as GFE, does the vendor specify which vehicle for the Government to purchase and furnish? | Section 5.5.1 highlight truck requirements. ORD and FRD have a requirement that states, "The system shall allow authorized personnel to install it on a vehicle within the current CBP fleet" which the vendor need to make sure their system is compatible with the CBP fleet, not with any 4x4 vehicle. Section 5.8.1 states: "The Government plans to provide a new (2025 or newer) Ford F250 4X4 short bed truck for the vehicle platform. Note: The Government plans for the use of a Ford F250 platform but reserves the right to change the vehicle make at any time." |
| 3 | USBP-PMO-M2S2-01-000007 |
PR Number: 20154536
| Draft M2S2 SOW | Table 1: Operational Effectiveness Requirements | 7-10 | Are IoI target definitions or target sizes available? Are they the same as the target definitions found in the CTSE solictation? | Definition of IoI: Detected objects or persons within the field of operation of possible interest to USBP. Items of Interest may include, but are not limited to USBP assets and resources that have not yet been identified as such, law enforcement partners, contraband, animals, and unidentified humans and conveyances. |
| 4 | USBP-PMO-M2S2-01-000007 |
PR Number: 20154536
Draft M2S2 SOW Table 1: Operational Effectiveness Requirements 8 M2S2-OR-09 : "The system shall mark the position of any selected IoI such that the mark is invisible to the unaided eye."
What is the intent behind the statement "invisible to the unaided eye"? Does this imply the incorporation of some sort of targeting beacon or does this refer to marking of a target on the C2 User Interface? "Invisible to the unaided eye" in requirement M2S2-OR-09 refers to marking the position of the selected Item of Interest (IoI) in a way that is not visible to the human eye without specialized equipment or technology (e.g, Night Vision binoculars).
5 USBP-PMO-M2S2-01-000007
PR Number: 20154536
Draft M2S2 SOW Table 1: Operational Effectiveness Requirements 9 M2S2-OR-19 : "The system shall respond to an operator’s control inputs of its functions in near-real-time."
| Is there are quantitative requirement to define what is acceptable for controller latency or other definition of near-real-time? | Near-real time is defined as a time of 0.50 seconds or less. | |
| 6 | USBP-PMO-M2S2-01-000007 |
PR Number: 20154536
| Draft M2S2 SOW | 1.1 | 6 | What comprises a Team Awareness Kit (TAK)? | Please see TAK description at this link. | |
| Additional information about the TAK at this link. | |||||
| 7 | Draft M2S2 SOW & Capability Requirements Matrix | SOW 5.9.2 | |||
| FRD # 72 | SOW 23 of 44 | Section 5.2 Government-Furnished Equipment, states, "The Government may or may not provide the 4x4 vehicle as GFE. If the Government does not provide the 4x4 vehicle, the Contract shall be responsible for providing the 4x4 vehicle in accordance with this SOW." |
FRD # 72 states, "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."
| Question. In order to meet/exceed all of the Government M2S2 and 4X4 vehicle requirements, potential Government provided 4X4 vehicles may or may not support offerors otherwise compliant solution. Will the Government please confirm that any Government provided 4X4 vehicles will be of the minimum make and model (weight/load capacity) proposed by the awarded offeror, compliant to the Government requirements and proposed solution? | Section 5.5.1 highlight truck requirements. ORD and FRD have a requirement that states, "The system shall allow authorized personnel to install it on a vehicle within the current CBP fleet" which the vendor need to make sure their system is compatible with the CBP fleet, not with any 4x4 vehicle. Section 5.8.1 states: "The Government plans to provide a new (2025 or newer) Ford F250 4X4 short bed truck for the vehicle platform. Note: The Government plans for the use of a Ford F250 platform but reserves the right to change the vehicle make at any time." | ||
| 8 | Draft M2S2 SOW & Capability Requirements Matrix | SOW 5.9.2 | |
| FRD # 72 | SOW 23 of 44 | Section 5.2 Government-Furnished Equipment, states, "The Government may or may not provide the 4x4 vehicle as GFE. If the Government does not provide the 4x4 vehicle, the Contract shall be responsible for providing the 4x4 vehicle in accordance with this SOW." |
FRD # 72 states, "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."
| Question. What 4X4 vehicle, make and model, might the Government provide as GFE? In order to ensure offerors proposed M2S2 system meets FRD #72 of the 4X4 vehicle is provided as GFE, offerors need to know the make and model of the potential Government provided 4X4 vehicle? | Section 5.5.1 highlight truck requirements. ORD and FRD have a requirement that states, "The system shall allow authorized personnel to install it on a vehicle within the current CBP fleet" which the vendor need to make sure their system is compatible with the CBP fleet, not with any 4x4 vehicle. Section 5.8.1 states: "The Government plans to provide a new (2025 or newer) Ford F250 4X4 short bed truck for the vehicle platform. Note: The Government plans for the use of a Ford F250 platform but reserves the right to change the vehicle make at any time." | |||
| 9 | Draft M2S2 Capability Requirements Matrix | FRD # 35 & 218 | FRD # 35 states, "The installation kit shall enable the system to be installed and uninstalled on the M2S2 truck fleet." |
FRD # 218 states, "The system shall allow authorized personnel to install it on a vehicle within the current CBP fleet."
| Question. In order to meet/exceed all of the Government M2S2 and 4X4 vehicle requirements, potential offerors solutions may or may not be support install and uninstall on some or all of the current M2S2 truck fleet. Will the Government please clarify/confirm that offerors proposed compliant solution shall enable install and uninstall on current M2S2 truck fleet vehicles meeting the minimum 4X4 vehicle requirements of the the awarded offerors solution? | Section 5.5.1 highlight truck requirements. ORD and FRD have a requirement that states, "The system shall allow authorized personnel to install it on a vehicle within the current CBP fleet" which the vendor need to make sure their system is compatible with the CBP fleet, not with any 4x4 vehicle. Section 5.8.1 states: "The Government plans to provide a new (2025 or newer) Ford F250 4X4 short bed truck for the vehicle platform. Note: The Government plans for the use of a Ford F250 platform but reserves the right to change the vehicle make at any time." | ||
| 10 | Draft M2S2 SOW & Capability Requirements Matrix | SOW Table 1, M2S2-OR-17, Coverage |
FRD # 20 SOW 8 of 44 SOW, Table 1, M2S2-OR-17, Coverage, states, "The system (radar) shall have an area of coverage (field of view) of 120 degrees, (T) 360 degrees (O) from its position."
FRD # 20 states, "The system shall provide the radar with 360 degrees of coverage about its vertical axis."
| Question. Will the Government please confirm/clarify the (T) and (O) for radar coverage. | OR-17 defines the radar's capability in terms of its field of view, specifying a threshold (T) of 120 degrees and an objective (O) of 360 degrees. This indicates that the radar must meet a minimum coverage of 120 degrees, with 360 degrees being the desired goal. FRD #20 further clarifies the system requirement by stating that the radar shall provide 360 degrees of coverage about its vertical axis. Therefore, the system must achieve full 360-degree coverage to meet the stated requirement in FRD #20, aligning with the objective (O) specified in OR-17. | ||||
| 11 | Draft M2S2 Capability Requirements Matrix | FRD # 3 | - | FRD # 3 states, "The system shall allow the operator to establish sensor detection and sensitivity parameters (excluding radar) in relation to sensor detection capabilities." |
| Question. Will the Government provide additional clarification on what this requirement means? | Government modified FRD #3 to exclude parenthetical statement regarding exlcusion of radar. This means the system should allow operators to customize how the sensors detect and respond to various inputs or stimuli, such as adjusting sensitivity thresholds, detection ranges, or filtering settings to optimize performance for specific mission scenarios. | ||||
| 12 | Draft M2S2 Capability Requirements Matrix | FRD # 12 | - | FRD # 12 states, "The system shall enable the operator to customize the autonomous interrogation duration of an IoI between 1 second and 60 seconds." |
| Question. Will the Government please clarify what autonomous interrogation duration means? | The phrase "autonomous interrogation duration" refers to the amount of time the system automatically engages with or collects data from an IoI before moving on to the next target and without requiring continuous manual input from the operator. | ||||
| 13 | Draft M2S2 Capability Requirements Matrix | FRD # 14 | Autonomy | FRD #14 requires the system to provide the capability to autonomously slew camera sensors to interrogate multiple detections in a queue. |
Question: If the system has the capability to autonomously slew camera sensors to interrogate multiple detections in a que, what determines priority, and is CBP stating there is more that one camera sensor? The priority for autonomously slewing camera sensors to interrogate multiple detections in a queue would be determined based on predefined parameters or criteria established by the operator or system configuration (i.e., IoI type - human or conveyance).
14 Draft M2S2 Capability Requirements Matrix FRD # 19 Operator Interface FRD #19 states system shall enable the operator to simultaneously display live videos and recorded videos.
| Question: Is there a limit to the number of simultaneous displays to be presented to the operator or is live video and recorded video the only criteria? | The requirement focuses solely on the ability to present both live and recorded video streams concurrently. The vendor defines a limit to the number of simultaneous displays beyond this criterion. Therefore, the system must ensure functionality for simultaneous live and recorded video display, as stated in FRD #19. | ||||
| 15 | Draft M2S2 Capability Requirements Matrix | FRD # 23 | Panning and Tilting sensors/Devices | FRD #23 states system shall be capable of dynamic performance in the entire 360⁰ degrees horizontal FoR and +/- 45⁰ degrees vertical FoR. |
| Question: Can CBP expand on what is meant by "dynamic performance" in the entire 360⁰ degrees horizontal FoR and +/- 45⁰ degrees vertical FoR? | Dynamic performance refers to the ability of a system to adapt, respond, and operate effectively under changing conditions or varying demands. It often involves assessing how well something performs in real-time or under dynamic circumstances, such as fluctuating workloads, environmental changes, or external pressures. | ||||
| 16 | Draft M2S2 Capability Requirements Matrix | FRD # 26 | Communications | FRD #26 states system system shall allow local LMR agent communications in and around the system site, line of sight viewshed permitting. |
| Question: Can CBP provide details as to both the fixed and mobile LMR system or systems requiring integration? | The Government plans to GFE LMRs will be Motorola APX 8500 and APX 5000 P25. However, the Government reserves the right to install any Motorola or Harris (e.g., Harris CL-200-P) radio compatible with USBP's LMR network. | ||||
| 17 | Draft M2S2 Capability Requirements Matrix | FRD # 27 | - | FRD # 27 states, "The system shall provide an extension of the current fixed LMR agent communication system, line of sight permitting." |
| Question. What is the current fixed LMR agent communication system? | The Government plans to GFE LMRs will be Motorola APX 8500 and APX 5000 P25. However, the Government reserves the right to install any Motorola or Harris (e.g., Harris-CL-200-P) radio compatible with USBP's LMR network. | ||||
| 18 | Draft M2S2 Capability Requirements Matrix | FRD # 30 | Communications | FRD #30 states system system shall have the capability to operate with the Government approved communication systems. |
| Question: Can CBP provide details on the Government approved communication systems? | The M2S2 Statement of Work, Section 5.10.1, CBP Network Connectivity, addresses the ability to communicate with current and future Government communication systems. Specific details regarding the Government-approved communication systems will be provided at a later date by CBP as necessary to ensure compliance with this requirement. | ||||
| 19 | Draft M2S2 Capability Requirements Matrix | FRD # 38 | Usability | FRD #38 states system system shall enable the operator to control all features of the system and its subsystems while located inside the vehicle cab. |
| Question: Can CBP specifiying which features require the operator to control while located inside the cab, as all features of the system is an overaching requirement? | The Government requires operators to have full control of all sensor systems, user interface, and mast functions from within the vehicle's cab. | ||||
| 20 | Draft M2S2 Capability Requirements Matrix | FRD # 43 | Alerting and Reporting | FRD #43 states system system shall be hardened against physical vandalism that adversely affects system performance. |
| Question: Can CBP provide some specifics on the type of physical hardening to prevent physical vandalism that may be necessary? Is this criteria specific to the system and not the vehicle? | In order to provide sufficient physical hardening, the system must employ access control to points of entry, locking and alert systems. | ||||
| 21 | Draft M2S2 Capability Requirements Matrix | FRD # 47 | Alerting and Reporting | FRD #47 states system system shall alert the operator of IoIs approaching the operator defined security boundary of the physical system. |
| Question: Is the security boundary of the physical system defined? | The security boundary is mission-specific and should allow flexibility for mission sets (remote capability, in-cab operations, etc.) | |||||
| 22 | Draft M2S2 Capability Requirements Matrix | FRD # 74 & 75 & 76 | - | Question. We were not able to locate the referenced Tables 8 & 9. Will the Government please clarify where these tables are located? | The content of these tables is in the "M2S2 Environmental Requirements" tab in the M2S2 Capability Requirements Matrix file. | |
| 23 | Draft M2S2 Capability Requirements Matrix | FRD # 77 | Availability | FRD #77 states 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. |
| Question: Is the intent of this requirement for the sytem to operate on the move, or is this to prove the ruggedness of the system? | FRD #77 requires the vendor to specify the maximum safe speed and average speed at which the M2S2 can travel under the specified terrain conditions while the mast and sensors are stowed. This information is intended to help CBP assess the system's ability to withstand rugged terrains and ensure the system can arrive at the area of responsibility, deploy, and conduct operations effectively. | ||||
| 24 | Draft M2S2 Capability Requirements Matrix | FRD # 92 | Interoperability | FRD #92 states the system shall allow an operator to display the locations of other assets when available. |
| Question: Can CBP specify what is meant by other assets, is this specific to other M2S2 assets? | Assets include other mobile surveillance assets, CBP-approved TAK devices, and other identified CBP systems. | ||||
| 25 | Draft M2S2 Capability Requirements Matrix | FRD # 94 | Interoperability | FRD #94 requires the operator to receive the locations of other assets. |
| Question: Is this requirement limited to a specific Area of Responsibility, or does it apply to all operational areas? | The intent is to ensure that the operator can receive asset location data for all operational areas relevant to the mission. | ||||
| 26 | Draft M2S2 Capability Requirements Matrix | FRD # 94 | Interoperability | FRD #94 requires the operator to receive the locations of other assets. |
| Question: Could the Government provide additional details regarding the communication path or system that will supply this data (e.g., TAK or other protocols)? | The M2S2 Statement of Work, Section 5.10.1, CBP Network Connectivity, addresses the ability to communicate with current and future Government communication systems. | ||||
| 27 | Draft M2S2 Capability Requirements Matrix | FRD # 109 & 110 | - | FRD # 109 & 110 state, "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." and "The system shall forecast IoI movement within 60 seconds(T); 30 seconds (O) of establishment of an IoI track." |
| Question. Will the Government please clarify what is meant by forecast -- the output of a kalman filter prediction or something that projects much farther in time? | The term "forecast" in these requirements refers to the system's ability to predict the movement of an IoI based on available sensor data and tracking algorithms. | ||||
| 28 | Draft M2S2 Capability Requirements Matrix | FRD # 137 | - | FRD # 137 states, "The system shall be able to track utilization rate of the Command and Control system." |
Question. Will the Government please clarify what it means by utilization? Does the Government mean utilization of compute and nework capacity or something else? Please refer to FRD #213 for context of utilization metrics.
29 Draft M2S2 Capability Requirements Matrix FRD # 149 Operator Interface FRD #149 states the system shall allow the operator to establish parameters and set sensitivity in relation to sensor detection capabilities.
| Question: Can CBP expand on what is required for setting sensor sensitivity in relation to sensor detection capabilities? | The system should allow operators to customize how the sensors detect and respond to various inputs or stimuli, such as adjusting sensitivity thresholds, detection ranges, or filtering settings to optimize performance for specific mission scenarios. | ||||
| 30 | Draft M2S2 Capability Requirements Matrix | FRD # 168 | Usability | FRD #168 states the 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. |
| Question: Is this in conflict with an early requirement in terms sensor identification distances. This states an objective of 5 miles using the EO/IR Camera as compared to FRD 120 stating the system? | Please refer to FRD #120 for video resolution requirements. | ||||
| 31 | Draft M2S2 Capability Requirements Matrix | FRD # 172 & 201 | - | The requirement for 2" above cabin (FRD # 172) combined with mast height (FRD # 201) and detection ranges (multiple FRDs), provides a tight constraint towards mast solutions available in the market and sensor suite solution. |
Question: Given the tight constraints imposed by the 2" clearance requirement above the cabin (FRD #172), in combination with mast height limitations (FRD #201) and sensor detection range requirements (multiple FRDs), would the Government consider revising the 2" requirement from a mandatory "Shall" to an objective requirement. Recommended FRD requirement revision: “The system, in its stowed position, shall be < 2 inches above the top of the truck's cab (O) and fit inside the length and width of the vehicle' s bed (T). Mast height requirements will be modified as follows:
FRD #172: "The Mast subsystem shall extend to an operating surveillance height of a minimum of 15 feet above ground level."
FRD #201: "The system height, in its stowed position and transportation-ready, shall not exceed a maximum of 7 feet and fit within the length and width of the vehicle's bed."
32 Draft M2S2 Capability Requirements Matrix FRD # 172 Usability FRD #172 states the Mast subsystem shall extend to an operating surveillance height of up to 30 feet (T), up to 40 feet (O) above ground level.
Question: What criteria is driving the requirement for the Mast subsystem heights, as isn't the limiting factor the distance at which the sensors can perform DTIC? The requirement states the height as being an "up to height", can you be in compliance to the requirment at a lower height as long as you can meet the DTIC criteria? Mast height requirement modified as follows:
"The system height, in its stowed position and transportation-ready, shall not exceed a maximum of 7 feet and fit within the length and width of the vehicle's bed."
33 Draft M2S2 Capability Requirements Matrix FRD # 174 Usability FRD #174 states the system shall allow an operator to wear a standard uniform while in operation.
| Question: Can CBP specificy what is considered standard uniform and how the system operation may be affected by the operator standard uniform? | The agent shall be able to wear a rough duty uniform with tactical gear (Body Armor, gun belt, radio, and critical items) and the system shall not inhibit Operator's movement if under duress. | ||||
| 34 | Draft M2S2 Capability Requirements Matrix | FRD # 176 | - | FRD # 176 states, "The temperature/humidity design goal shall be between 21 °C and 25 °C (70 °F and 77 °F) and 45 percent humidity." |
| Question. Will the Government please confirm this requirement is for inside the cabin? | The requirement is intended to apply to the inside of the cabin to ensure optimal environmental conditions. | ||||
| 35 | Draft M2S2 Capability Requirements Matrix | FRD # 181 | - | FRD # 181 states, "The system position accuracy, repeatability and backlash shall be < 0.01⁰." |
Question. Does this mean self position? This requirement will be updated as follows:
"The Pan/Tilt unit shall provide position accuracy, repeatability, and backlash of less than 0.01°."
36 Draft M2S2 Capability Requirements Matrix FRD # 183 - FRD # 183 states, "The system sensors and user interface shall allow for remote operations by one trained operator outside of the vehicle at a time."
| Question. Will the Government please provide how far from the vehicle is the remote operator? | Agent is able to remotely operate from within the connected network. | ||||
| 37 | Draft M2S2 Capability Requirements Matrix | FRD # 187 | - | FRD # 187 states, "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." |
| Question. Will the Government please clarify what is 'standard operating conditions?' Vehicle in idle? | The standard operating conditions would imply, vehicle idle, mast deployed, and sensor suite operational. Net positive charge while in operational surveillance mode. | ||||
| 38 | Draft M2S2 Capability Requirements Matrix | FRD # 189 | - | FRD # 189 states, "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." |
| Question. Will the Government please clarify if these requirements are tied to battery bank alone, not including vehicle power, or if the requirements include both battery and alternator power? | The intent of this requirement is for the system to have sufficient battery capacity to operate on battery power alone. | ||||
| 39 | Draft M2S2 Capability Requirements Matrix | FRD # 191 | Robustness | FRD #191 states the system prevent damage to the system when the vehicle is traveling between thick vegetation and low hanging tree branches. |
Question: Does this requirement infer that the system can extend beyond the height of the vehicle cab, as long as there is a means for protecting the system? Does the CBP vehicle fleet have vehicles whose cab height (AGL) is different? Mast height requirement modified as follows:
FRD #201: "The system height, in its stowed position and transportation-ready, shall not exceed a maximum of 7 feet and fit within the length and width of the vehicle's bed."
40 Draft M2S2 Capability Requirements Matrix FRD # 200 Compatibility FRD #200 states the system shall not interfere with or degrade safety features of the Government Furnished Equipment (GFE).
| Question: Can CBP specify what Government Furnished Equipment will be provided in order to ensure no safety degredation? | The list of GFE is specified in the SOW, in the "Government-Furnished Equipment" section. | ||||
| 41 | Draft M2S2 Capability Requirements Matrix | FRD # 201 | Transportability | FRD #201 states 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. |
Question: Can CBP specifiy the length of the vehicle as this is critical to meeting the mast height criteria of 30 ft (O) and 40 ft (T). Additionally can an extension to the height of the cab be added or what is the limiting factor associated with cab height? Mast height requirement modified as follows:
FRD #201: "The system height, in its stowed position and transportation-ready, shall not exceed a maximum of 7 feet and fit within the length and width of the vehicle's bed."
42 Draft M2S2 Capability Requirements Matrix FRD # 204 Reliability FRD #201 states the system shall provide the operator the vehicle's engine cycle status for maintenance
| Question: Is this criteria above and beyond the vehicles ability to provide this information? | The Goverment will provide a 3/4 ton 4x4 vehicle. As this is the case, the Government will take this comment into consideration. | ||||
| 43 | Draft M2S2 Capability Requirements Matrix | FRD # 226 | - | FRD # 226 states, "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)." |
Question. Will the Government please clarify/confirm what is meant by full configuration swap? Please confirm the Government intent with this requirement is for full configuration swap of offeror's awarded solution and/or additional configuration component swaps directed by the Government after any required integration tasks are completed? A full configuration swap refers to the complete replacement and reconfiguration of LRU components in the sensor suite, including both hardware (e.g., physical sensors) and software settings, to restore or modify the system's operational capabilities.
The requirement will be modified as follows:
"The system shall allow authorized personnel to complete a full configuration swap, including physical sensor replacement and software reconfiguration, within a maximum time of 8 hours (T) and 4 hours (O)."
44 Draft M2S2 Capability Requirements Matrix FRD # 227 - FRD # 227 states, "The system's software interface shall accommodate all sensor configurations."
| Question. Will the Government please clarify/confirm what is meant accomodate all sensor configurations? Please confirm the Government intent with this requirement is to accomodate all sensor configurations of the offeror's awarded solution and/or additional sensor integrations directed by the Government after any required integration tasks are completed? | The intent is for the vendor to provide an ICD and to develop common software against all sensor configurations that the vendor is providing as part of the system package. | ||||
| 45 | Draft M2S2 Capability Requirements Matrix | FRD # 228 | - | FRD # 228 states, "The following configuration items shall be consistent across all variants: electrical connections, power supplies, sensor interface modules, quick disconnect plates, and skid mounting." |
| Question. What variants are the Government referring to? | "Variants" refers to all potential sensor configurations as described in the previous comment. | ||||
| 46 | Draft M2S2 Capability Requirements Matrix | FRD # 231 | - | FRD # 231 states, "The system shall be configurable so that authorized personnel have the capability to reconfigure the system." |
| Question. Will the Government please clarify/confirm the intent with this requirement is that authorized personnel have the capability to reconfigure the system of the offeror's awarded solution and/or additional configuration swaps directed by the Government after any required integration tasks are completed? | CBP should be able to perform sensor swaps and system reconfigurations without having to consult with the vendor. | ||||
| 47 | Draft M2S2 Capability Requirements Matrix | FRD # 231 | Interoperability | FRD #231 states the system shall be configurable so that authorized personnel have the capability to reconfigure the system. |
| Question: Can CBP specify what level of reconfiguration of the system is desired? | "Level of reconfiguration" refers to any or all sensor configurations and software configurations as required by the operational requirements and mission descriptions. | ||||
| 48 | Draft M2S2 Capability Requirements Matrix | Modularity Objective 6 | System Integration | This system integration optional objective states, "M2S2 has system integration capabilities that include meshing to other M2S2 units and other USBP systems and surveillance towers. This shall allow for track information and other data to be passed between all systems." |
| Question. Will the Government please provide clarification through which network/protocol the data is going to be shared and compiled - is it via TAK? | The network that will be used is the CBP network of devices, which may include TAK, and other monitoring and security end-nodes. | |||||
| 49 | General Comment | - | - | Thank you for the opportunity to review the draft files and provide feedback. Many of the numerous questions, clarification, and comments provided have direct impact on potential offerors design and proposed M2S2 solution approach. We therefore request and recommend the Government release an updated set of draft documents, including Sections L&M, for industry review and feedback, prior to the release of the final RFP. | We are providing responses to the questions to share information as quickly as possible with potential vendors. We do not anticipate releasing an updated set of draft documents. | |
| 50 | - | SOW § 5.6.2 (Open Architecture) | Please clarify whether CBP will consider M2S2 solutions integrating NATO-origin subsystems that are assembled and secured in the United States under ITAR-compliant frameworks. | AUSP recommends allowing allied components if final integration and cyber compliance occur on U.S. soil, consistent with Buy American Act exceptions for defense articles. | CBP will consider any M2S2 solution that is fully compliant with the requirements in the Statement of Work, including all applicable referenced regulations, policies, laws, etc. | |
| 51 | - | SOW § 5.6.3 (Interoperability / Interdependency) | Will CBP accept U.S. integrators serving as prime contractors for partner technologies not yet on GSA Schedule if the final system meets all network and security standards? | Permit U.S. primes with GSA Schedule eligibility to represent qualified foreign technology providers under the hybrid BPA framework. | No. | |
| 52 | - | SOW § 5.6.4 (Autonomous and Remote Operations) | The SOW defines “autonomous” broadly to include AI, ML, and computer vision. Will autonomous functions be limited to detection and alert or may they include automated sensor slewing and mission tasking without operator input? | Clarify expected TRL and autonomy scope to align with DHS AI Strategy 2020 and PMOD interoperability standards. | Autonomous functions are not limited to detection and alerting; they may include advanced capabilities such as automated sensor slewing and mission tasking without operator input, provided these functions align with operational requirements and security protocols | |
| 53 | - | Vendor Proposed Modularity Objectives (UAS Detection) | Is CBP interested in integrating commercially available UAS detection modules capable of cueing EW or kinetic counter-UAS systems? | AUSP recommends explicitly including counter-UAS integration as an evaluated optional capability within the final RFP. | Please see modularity section of the SOW. | |
| 54 | - | SOW § 5.4 (Test & Evaluation) | Will CBP host an industry day or accept live demonstrations of candidate systems prior to RFP release or DT/OT&E? | AUSP recommends a limited demo event to assess modular autonomy and multi-sensor fusion performance in terrain analogous to border conditions. | CBP welcomes no-cost demonstrations of vendor solutions. | |
| 55 | - | SOW § 5.10.2 (Hardware Frequency Authorization) | Will the Government permit vendors to submit requests for temporary experimental frequency assignments for testing prior to formal NTIA approval? | Allow submission under experimental authorization to expedite prototyping and RF compliance testing. | CBP will rely on vendor experimental frequency approvals to get through any DT/OT events. | |
| 56 | - | Acquisition Strategy Section (Overview) | Will CBP allow vendor teams to propose as small-business-led consortia or integrator alliances to expand industrial base capacity under DPA Title III and EDA industrial program objectives? | AUSP recommends explicitly encouraging small-business and dual-use partnership participation to enhance domestic supply chain resilience. | The associate contractor clause at the bottom of the SOW is all we have in there. We do not have anything specific to subcontracting to expand the industrial base. | |
| 57 | 2025-10-24+Draft+M2S2+Statement+of+Work | 1.1 | 7 | With regards to M2S2-OR-13, the requirement asks that the "system shall allow an operator to receive imagery in real-time". Is there a threshold time that needs to be met to be considered "real-time"? Additionally, is this requirement measured locally on the system or remotely (i.e. at C2CEN). | Near-real time is defined as a time of 0.50 seconds or less. | |
| 58 | 2025-10-24+Draft+M2S2+Statement+of+Work | 5.6.2.1 | 20 | In several locations within the SOW and CRM, there is reference to "authorized personnel" that shall have the capability to perform varying tasks. Who are considered "authorized"? Will the vendor define this depending on the task and in some cases is it acceptable that the vendor is the only authorized personnel? | Authorized personnel will consist of CBP/USBP agents (supervisors and operators), engineers, Government contractors, sys admins, maintenance technicians and any other individuals designated by CBP. | |
| 59 | 2025-10-24+Draft+M2S2+Statement+of+Work | 5.6.4 | 21 | The SOW states that the system shall meet Functional Requirements Document (FRD) requirements as specified in the M2S2 Capability Requirements Matrix (CRM). Will the FRD be provided in addition to the CRM. | Any documentation, parameters, assumptions and other required information pertaining to system design will be included as part of the RFP package. | |
| 60 | 2025-10-24+Draft+M2S2+Statement+of+Work | 5.1 | 23 | "M2S2s are required to follow all applicable USBP network policies". What are the network policies? | The network policies required are DHS 4300A, “Information Technology System Security Program, Sensitive Systems” and U.S. CBP Information Systems Security Policies, HB 1400-05D Version 9.0. | |
| 61 | 2025-10-24+Draft+M2S2+Statement+of+Work | 5.11.2 | 29 | "The vendor shall provide a 24-hour help desk support line for Tier-1 level issues". What are considered Tier-1 level issues? Is this defined by the vendor? | Tier-1 level issues are defined as issues that can be resolved in the field with telephonic support and not requiring specialty tools or training. | |
| 62 | 2025-10-24+Draft+M2S2+Statement+of+Work | 5.11.3 | 29 | The SOW refers to a "broader sustainment concept" to which maintenance training must be conducted to align with. Where can this concept be found? | Any documentation, parameters, assumptions and other required information pertaining to system design will be included as part of the RFP package. | |
| 63 | 2025-10-24+Draft+M2S2+Statement+of+Work | 5.11.4 | 29 | It is being requested that CMLS providers stock 30-day supply of bench and shop stock as well as critical LRU spares. Critical LRU spares (i.e. radar/camera) are high value items, will there be funding provided (or future agreement to purchase as sparesL) to CMLS providers to stock said items? | No. The vendor should consider these costs when preparing their CMLS Price Proposal. | |
| 64 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 32 | - | What frame rates are required. | The frame rate shall be adequiate to meet this and other image quality requirements. | |
| 65 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 43 | - | Are there specific forms of physical vandalism that the system needs to be hardened against? | In order to provide sufficient physical hardening, the system must employ access control to points of entry, locking and alert systems, incident response planning, and surveillance. | |
| 66 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 47 | - | The requirement refers to a security boundary within which the system shall alert the operator of IoIs approaching. What is the range of said boundary? | The security boundary is mission-specific and should allow flexibility for mission sets (remote capability, in-cab operations, etc.) | |
| 67 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 44 and 49 | - | What levels of non-physical attacks need to be detectable for alerting, further clarification and potential test cases. Some forms of attack may not be able to be defeated. | The Government will take this comment into consideration. |
| 68 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 70 | - | Performing self-checks at only 4-hour intervals upon start-up of system would be too sparse to ensure adequate performance of system. It is suggested that this be reduced to <30 minutes. | The Government is evaluating this requirement. |
| 69 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 74, 75, 76 | - | In addition to the Environmental Requirements within the CRM, will the source document referred to, M2S2 ORD, be provided? | Any documentation, parameters, assumptions and other required information pertaining to system design will be included as part of the RFP package. |
| 70 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 89 | - | EMI is apparent in all designs. It is suggested that the requirement clarify that EMI should be at a level that does not severely degrade system performance | The Government will modify the requirement as follows: |
"The system shall operate without operational degradation in the presence of EMI."
| 71 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 104 and 111 | - | How is CBP defining the difference between "fusing detections", FRD #104, and "correlate detections", FRD #111 | Any documentation, parameters, assumptions, definitions and other required information pertaining to system design will be included as part of the RFP package. |
| 72 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 108 | - | Will CBP define prioritization parameters? | The parameters should be fliexible enough to accommodate different mission sets and be configured by an operator. |
| 73 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 115 | - | This alignment is achievable but does not seem practical for the application. Alignment within 1 milli-radian is recommended. | The Government will take this comment into consideration. |
| 74 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD #124 | - | It is believed that the requirement is meant to say the divergence of the LRF be "no greater than 10 feet on minor axis" at 5 miles. If so, is this the half or full angle divergence? | The Government will take this comment into consideration. |
| 75 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD #128 | - | While 25 IoIs might be adequate in some scenarios of walking personnel, there have been situations at the border with much larger number of targets within the FoR. Also, if the radar is located near a highway or a herd of animals, there may be much more than 25/50 IoIs. It is suggested that this be increased to 50 (T) 100 (O). | The Government will take this comment into consideration. |
| 76 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 131 | - | Are there specific types of manual metadata that were in mind that an operator may need to enter? | The manual inputs should be flexible enough to accomodate different mission sets and be inputted by an operator. |
| 77 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 172 | - | A Mast Subsystem that can extend up to 30 feet (T) introduces challenges when considering FRD # 201 and could contribute to decreased system performance attributed to a taller Mast. | The Government will modify the requirement as follows: |
"The Mast subsystem shall extend to an operating surveillance height of a minimum of 15 feet above ground level."
| 78 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 176 | - | The temperature/humidity design goals described in this requirement seem to contradict those in the Environmental Requirements Tab. | Functional requirement refers to climate-controlled areas versus ambient environmental operating conditions. |
| 79 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 188 | - | Limiting the sound level of the power subsystem to values defined rules out certain modes of energy generation. It is suggested to increase allowed sound level. | The Government will take this comment into consideration. |
| 80 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 201 | - | What is the rationale for the selection of 2" on this requirement? What issues are of concern if the system resided higher, 4-6"? | Mast height requirement modified as follows: |
"The system height, in its stowed position and transportation-ready, shall not exceed a maximum of 7 feet and fit within the length and width of the vehicle's bed."
81 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix FRD # 212 - Factoring in time to report the system being down, troubleshooting and repair, a MDT of 8 hours is not viable, and an order of magnitude closer to 48 hours would be more appropriate. The Government will take this comment into consideration.
| 82 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 218 | - | Requirement seems to contradict what is stated in the SOW, "M2S2 truck shall be a new (2025 or newer), unused 4x4 vehicle capable…". | Tht Government will take this comment into consideration. |
| 83 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 226 | - | When factoring in elements like configuration, there is a low probability of being able to meet the time threshold of this requirement. | The Government will take this comment into consideration. |
| 84 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | FRD # 234 | - | What sort of algorithms are of interest to be potentially be integrated? | The vendor is anticipated to propose a design that incorporates an open architecture using non-proprietary data standards. |
| 85 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | Environmental Reqs | - | Rain, fog, snow, etc. can have extreme adverse effects on equipment performance, particularly Radar/Camera. Guaranteed performance of system to CRM Requirements is not likely. Suggestion for further clarity on operational requirements/ranges for these conditions. | Operational Environmental Conditions provide details for environmental conditions at operational sites expected along the borders. M2S2 will to operate under day and night conditions to a Field of View (FoV)/Field of Regard (FoR) with an unobstructed line of sight (LOS) for at least15 seconds. |
| 86 | 2025-10-24+Draft+M2S2+Capability+Requirements+Matrix | Environmental Reqs | - | "Wind, Operating (When Stowed)", The stowed condition is typically a non-operational condition of the system. It is believed that this requirement should be reworked to remove "Operating" | Operating when stowed general refers to traveling to and from the Station. |
| 87 | Draft M2S2 Capability Requirements Matrix.xlsx | FRD#248 | Tab 1 | This is a mobile C2 platform. For remote access to the system via CBP network infrastructure and CBP laptop, PIV MFA will be inherited from CBP. For local access, PIV MFA may not be feasible due to limited computing/architectural constraints. What are "other CBP policy approved technology and implementation standards." identified in lieu of PIV authentication? | The Government will review and alternative technology designs against the security policy to include NIST FPS 201 “Personal Identity Verification (PIV) of Federal Employees and vendors”. |
| 88 | Draft M2S2 Capability Requirements Matrix.xlsx | FRD#253 | Tab 1 | Please identify retention requirements for security logs. In addition, what is the expectation of forwarding these logs to CBP SOC - keep in mind that this is a mobile platform that may have WAN network disruptions? | Refer to FRD #240 and #179 for retention and security requirements. The system shall provide the CBP SOC with, at a minimum, the following information (including but not limited to): |
-Source and destination Internet Protocol (IP) addresses -Time and date of the event -Uniform Resource Locator (URL) -Access attempts to network services -Rejected source-routed addresses -Use of Internet Control Message Protocol (ICMP) -Redirects -etc.
Refer to FRD #178 to ensure the system has redundant data flow in case of disruptions.
89 Draft M2S2 Capability Requirements Matrix.xlsx FRD # 3 Tab 1 What is meant by sensitivity parameters in the following requirement? Does this mean exclusion and priority zones?
| "The system shall allow the operator to establish sensor detection and sensitivity parameters (excluding radar) in relation to sensor detection capabilities." | Sensitivity parameters in this requirement generally refer to the ability to configure how sensors detect and respond to stimuli based on their detection capabilities. This may include settings such as detection thresholds, range configurations, environmental filters, or alert conditions to optimize sensor performance in various operational scenarios. | |||||
| 90 | Draft M2S2 Capability Requirements Matrix.xlsx | FRD # 226 | Tab 1 | Please defined the meaning of full configuration swap in this case? | A full configuration swap refers to the complete replacement and reconfiguration of LRU components in the sensor suite, including both hardware (e.g., physical sensors) and software settings, to restore or modify the system's operational capabilities. | |
| 91 | Draft M2S2 Capability Requirements Matrix.xlsx | FRD#43 | Tab 1 | How far do we need to go to harden the system? Would it include bullet proof protection as well? | In order to provide sufficient physical hardening, the system must employ access control to points of entry, locking and alert systems, incident response planning, and surveillance. It would not include bulletproof protection. | |
| 92 | Draft M2S2 Capability Requirements Matrix.xlsx | FRD#49 | Tab 1 | Could you provide additional details regarding the specific threats that the vendor needs to protect and alert against in accordance with a specific MIL-STD? | This requirement will be deleted. | |
| 93 | Draft M2S2 Capability Requirements Matrix.xlsx | FRD#84 | Tab 1 | Could this be clarified with actual scenarios? | Any documentation, parameters, assumptions and other required information pertaining to system design will be included as part of the RFP package. | |
| 94 | Draft M2S2 Capability Requirements Matrix.xlsx | FRD#92 | Tab 1 | Could assets be further defined in this case? | Assets include CBP/USBP-approved TAK phones or devices, and other identified CBP systems. | |
| 95 | Draft M2S2 Capability Requirements Matrix.xlsx | FRD#94 | Tab 1 | Could assets be further defined in this case? | Assets include CBP/USBP-approved TAK phones or devices, and other identified CBP systems. | |
| 96 | Draft M2S2 Capability Requirements Matrix.xlsx | FRD#189 | Tab 1 | Does the alternator count as “recharging” the battery? Are they expecting power or enough battery for 8-16 hrs of silent (truck off time)? | The mission is expecting power/battery for up to 16 hours of operation without use of an external power source. | |
| 97 | Draft M2S2 CDRL DID forms | - | 35 | Monthly Program Management Review CDRL lacks critical information | The Government will take this comment into consideration. | |
| 98 | Draft M2S2 CDRL DID forms | - | 36 | Monthly Program Mgmt Review DID lacks all information | The Government will take this comment into consideration. | |
| 99 | Draft M2S2 CDRL DID forms | - | 37 | Missing information on the DID description | The Government will take this comment into consideration. | |
| 100 | Draft M2S2 CDRL DID forms | - | 38 | Missing information on the DID description | The Government will take this comment into consideration. | |
| 101 | Draft M2S2 CDRL DID forms | - | 39 | Missing information on the DID description | The Government will take this comment into consideration. | |
| 102 | Draft M2S2 CDRL DID forms | - | 40 | Missing information on the DID description | The Government will take this comment into consideration. | |
| 103 | Draft M2S2 CDRL DID forms | - | 41 | Missing information on the DID description | The Government will take this comment into consideration. |
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 .