Modular Mobile Surveillance System (M2S2)

Other / Unclassified

This memorandum is a request from the United States Border Patrol (USBP) to the General Services Administration (GSA) Assisted Acquisition Services (AAS) to expedite the processing of GSA Schedules and modifications for vendors providing Modular Mobile Surveillance Systems (M2S2).

This document is critical for potential bidders. It informs them that the USBP plans to release a Request for Quotations (RFQ) for M2S2 systems in May 2026, to be procured via the GSA Multiple Award Schedule (MAS) under SIN 334220. Crucially, vendors must have an active GSA MAS to submit a quote. Those without an active GSA MAS at the time of the RFQ release will be excluded, even if they are in the process of obtaining one. The document provides contact information for Johnathan F. Romero for any questions regarding this request.

Solicitation / RFP / RFQ

This document outlines the acquisition strategy for the Modular Mobile Surveillance System (M2S2). It is intended for GSA schedule holders via eBuy.

• The core requirement is the procurement of M2S2 units.

• The strategy involves a multi-phase source selection process.

• Key technical sub-factors include Vendor Demonstration, System Overview (TRL, Capabilities Matrix, Management), and Manufacturing Readiness Level (MRL) Facility Visit. These are listed in order of importance.

• Contract Type: Multiple-award blanket purchase agreement – Firm Fixed Price.

• Period of Performance: One (1) 12-month base period and Four (4) 12-month option periods, totaling five (5) years.

• Award Decision Method: Best Value Trade-Off.

• Evaluation Ratings: Technical (High Confidence to No Confidence), Past Performance (High Confidence to Neutral), Price (Price Reasonableness).

• Evaluation Factors are listed in order of importance.

• Phase I Evaluation: Technical Sub-factor 2 (System Overview).

• Phase II Evaluation: Vendor Demonstrations, Manufacturing Facility Visits, Past Performance, and Price.

• Preliminary Schedule:

  • RFQ Release: April 2026
  • Evaluation Phase I (Quotes Due): May 2026
  • Evaluation Phase II (Demonstrations/Visits): June – Aug 2026
  • BPA Awards & LRIP Units (Est. 3/vendor): November 2026
  • Test and Evaluation: December 2026 - May 2027
  • Full Rate Production Units (Est. 18/vendor): June 2027

• Potential quoters are GSA schedule holders.

• Post-BPA award activities include M2S2 Low-Rate Initial Production (LRIP) and Full Rate Production (FRP) unit procurement, and Test and Evaluation.

Questions & Answers / Clarifications

This document provides Government responses to vendor questions regarding the M2S2 solicitation, clarifying various technical requirements, operational parameters, and contractual details. The released solicitation will supersede these responses.

• Delivery Timeline: Approximately 1 month from contract award to delivery of the first test unit.
• Vehicle Platform: The Government plans to provide a Ford F250 4x4 short bed truck, but reserves the right to change the vehicle make.
• Near-Real-Time Definition: Defined as 0.50 seconds or less for controller latency and imagery reception.
• "Invisible to the unaided eye" (M2S2-OR-09): Refers to marking IoI position in a way not visible to the human eye without specialized equipment.
• System Hardening: Requires access control, locking, alert systems, incident response planning, and surveillance against physical vandalism.
• Mast Height: Modified requirements specify a minimum operating height of 15 feet and a stowed height not exceeding 7 feet.
• Communications: Government-furnished LMRs will be Motorola APX 8500 and APX 5000 P25, with the right to install other compatible radios.
• Configuration Swap: Full configuration swap (hardware/software) time modified to 8 hours (T) and 4 hours (O).
• Remote Operations: Agents can remotely operate from within the connected network.
• Power Requirements: System must operate for 8 hours (T) / 16 hours (O) on battery power alone.
• Authorized Personnel: Includes CBP/USBP agents, engineers, Government contractors, sys admins, maintenance technicians, and others designated by CBP.

These clarifications provide essential details for vendors to refine their technical proposals and understand specific performance expectations, vehicle compatibility, and operational constraints. Vendors should carefully review these responses as they pertain to their proposed solutions.

Statement of Work (SOW)

This Statement of Work (SOW) outlines the requirements for the development, delivery, and support of the Modular Mobile Surveillance System (M2S2) for the U.S. Border Patrol (USBP). The M2S2 aims to enhance border surveillance capabilities by providing a mobile, adaptable system capable of detecting, identifying, classifying, and tracking items of interest (IoI) in diverse environments.

• M2S2 System Delivery: Includes a sensor package, mast, power subsystem, command and control, user interface, autonomy, modularity, and artificial intelligence integrated onto a 4x4 vehicle. The system must support open architecture for interoperability with other CBP systems, including Team Awareness Kit (TAK).

• Program Management: Contractor responsibilities include developing a Program Management Plan (PMP), leading reviews, and providing monthly status reports.

• Engineering Support: Provision of engineering artifacts, technical documentation, and ad-hoc support for development, testing, and deployment.

• Test and Evaluation: Contractor support for government-led Development Test/Operational Test and Evaluation (DT/OT&E) and potential Follow-On Test and Evaluation (FOT&E).

• Training: Development and delivery of operator training, train-the-trainer (T3) training, and maintenance training.

• Maintenance and Logistics: Contractor will provide Contractor Maintenance and Logistical Support (CMLS) for a base period and option periods, ensuring high operational availability.

• Warranty: A minimum 12-month warranty covering the entire M2S2 unit.

• Deliverables: Includes various Contract Data Requirements List (CDRL) documents covering training materials, manuals, reports, plans, and technical data.

• Operational Effectiveness: Specific requirements for persistence (8-16 hours), accuracy (detection, identification, classification, location), tracking capabilities, and data management.

• Key Performance Parameters (KPPs): Accuracy for detection (2-5 miles), Accuracy for identification (1-3 miles), and Mobility (transition times).

• Availability: M2S2 systems must achieve 90% operational availability (Ao), 96.5% probability of 8-hour operation without critical failure, Mean Time Between Critical Failures (MTCBF) of 240 hours, and Mean Time To Repair (MTTR) of less than 8 hours.

• Period of Performance (POP): One (1) 12-month base period and nine (9) 12-month option periods, totaling ten (10) years.

• Place of Performance: Maintenance support to be within a one-hour drive of USBP Sector Headquarters or at CBP facilities where M2S2 units are deployed.

• Vehicle Requirements: New (2025 or newer) 4x4 vehicle with specific off-road capabilities and features.

• Environmental Conditions: Operational requirements for temperature, wind, humidity, sand/dust, salt fog, rain, snow, ice, and visibility.

• Network Connectivity: M2S2 units must connect to the CBP network, requiring specific Cisco hardware and compliance with USBP network policies.

• Security: Contractor personnel require background investigations and may need access to Controlled Unclassified Information (CUI).

• Modularity: The system must be configurable and allow for reconfiguration and integration of different sensor types.

• Autonomous Operations: The system must support autonomous detection, identification, classification, and tracking without continuous human command.

Form / Attachment / Pricing Sheet

This document is a template for vendors to submit questions or comments regarding the M2S2 opportunity. It provides a structured format for vendors to ask questions and for the government to potentially respond.

• The spreadsheet includes columns for 'Document', 'Document Section', 'Page Number', and 'Question / Comment'.
• It is intended to facilitate organized communication between vendors and the government.

Vendors should use this template to submit any questions or comments they have about the M2S2 opportunity. The government notes that responses to questions are not guaranteed and will be posted on Sam.gov if provided. This document is crucial for clarifying any ambiguities in the solicitation documents.

Form / Attachment / Pricing Sheet

This document is a draft M2S2 Capability Requirements Matrix, presented as an Excel spreadsheet. It details functional, environmental, and modularity requirements for the M2S2 system. Bidders are expected to use this matrix to document their system's compliance with each requirement.

• M2S2 Functional Requirements: Lists 271 functional requirements categorized by capability (e.g., Detection, Tracking, Autonomy, Operator Interface, Security). For each requirement, vendors must indicate 'Contractor's System Requirement Compliance' (e.g., 'System does not meet requirement'), 'Contractor's System Performance Capability' (a metric, if applicable), and 'Evidence of System Compliance' (e.g., Tested, Analysis, Not Applicable).
• M2S2 Environmental Requirements: Details 21 environmental conditions (e.g., Temperature, Humidity, Sand and Dust, Wind) and requires vendors to specify compliance, system parameters, and evidence of compliance.
• M2S2 Modularity Objectives: Outlines 13 optional modularity capabilities (e.g., Detect UAS, Vessel Detection, Autonomy) for which vendors can claim compliance.
• Evidentiary Basis: Defines the acronyms (TADI) used to indicate the basis for compliance claims.

This matrix is critical for bidders to understand the specific technical, environmental, and modularity requirements for the M2S2 system. It serves as a template for demonstrating how their proposed solution meets or does not meet each specified requirement. All listed requirements currently show 'System does not meet requirement' or 'Not Applicable' for evidence, indicating a baseline against which vendors must propose their capabilities.

Solicitation / RFP / RFQ

This document solicits innovative and commercially available solutions from industry for Modular, Mobile, Multi-Mission, Sensor, and Support (M2S2) capabilities. The government is seeking solutions to address specific mission requirements and operational challenges, particularly in detecting, identifying, and tracking Unmanned Aerial Systems (UAS) and vessels, as well as autonomous detection and reporting. The government does not prescribe a specific solution and encourages bidders to leverage commercial products, emerging technologies, and innovative practices.

Bidders are invited to describe M2S2 capabilities that fulfill or exceed the following optional objectives:

• UAS Detection, Identification, and Tracking: Systems capable of cueing counter-UAS systems (electronic warfare, kinetic). This includes performance against RF Group 1 and 2 UAS, Non-RF UAS, and Ultralight UAS, detailing detection range and performance in various weather conditions.

• Vessel Detection, Tracking, and Reporting: Capabilities to detect, track, and report on vessels, including details on detection range, vessel size tracked, and performance under different weather conditions.

• Autonomous Detection and Reporting: Capabilities for autonomous detection and reporting of UAS, vehicles, vessels, and other Items of Interest (IoIs) under various environmental factors (distance, time, temperature, weather, camera type).

• Equipment Configurations: Options beyond integrated truck platforms, such as trailer solutions or mobile tower configurations, including extended power options (over five days) and mast configurations.

• Command and Control (C2) Solutions: Integration with CBP systems to support M2S2 METs, explaining potential efficiencies and mission enhancement.

• System Integration: Capabilities for meshing with other M2S2 units, USBP systems, and surveillance towers for track information and data sharing.

• Logistics Sustainment: System design and data enabling transition to organic or third-party logistics sustainment, including training for depot and intermediate maintenance.

• Adaptability: Integration with other C2 systems and Common Operational Picture (COP) systems.

• Additional Modularity Capabilities: Any other modularity capabilities of interest to the government.

• Bidder's proposals should describe M2S2 capabilities that fulfill or exceed the stated objectives.

• Solutions should utilize Commercial Off-The-Shelf (COTS) or Non-Developmental Items (NDI) where practicable.

• Proposals should demonstrate innovation, efficiency, cost-effectiveness, minimize development risks and lifecycle costs, and support timely implementation.

• The government will consider any proposed M2S2 modularity capabilities in the overall evaluation of the bidder's quote. These objectives are optional, not required.

This document outlines objectives for optional M2S2 capabilities. While not mandatory, proposed capabilities will be considered during the evaluation.

Forms / Attachments / Pricing Sheets

This document contains a comprehensive list of Contract Data Requirements List (CDRL) items and their associated Data Item Descriptions (DIDs) for the Modular Mobile Surveillance System (M2S2) Program. It details the deliverables required from the contractor, including training materials, manuals, reports, plans, and technical documentation.

• Deliverable Summary Table: Lists all required deliverables with their ID, Title, and Submittal Date/Frequency.
• CDRL Forms: Each form (e.g., C-L01 Operator Training Material, C-L04 User Manual, C-L08 Integrated Contractor Support Plan, C-SE01 Technical Data Package) specifies the deliverable's purpose, preparation instructions, submission requirements (format, dates), and related contract references.
• Data Item Descriptions (DIDs): Provide detailed descriptions of the content and purpose for each deliverable.

This document is crucial for bidders as it outlines all the documentation and reporting the contractor will be responsible for throughout the contract lifecycle. It provides insight into the expected level of detail, reporting cadence, and specific technical and programmatic documentation required for the M2S2 program. Bidders must understand these requirements to accurately estimate costs and resources, and to ensure compliance if awarded the contract.