2025-10-24 Draft M2S2 Statement of Work.docx

DRAFT

Statement of Work For Modular Mobile Surveillance System

Version 1

October 24, 2025

USBP-PMO-M2S2-01-000007

PR Number: 20154536

Developed By:

U.S. Border Patrol (USBP) Headquarters Program Management Office Directorate (PMOD) 1300 Pennsylvania Avenue, NW Washington, DC 20229

Revision History

Table of Contents

List of Tables

List of Figures Figure 2: M2S2 Operational View 1 (OV-1)10

M2S2 Statement of Work

GENERAL DISTRIBUTION:

Modular Mobile Surveillance System Page 21 of 28 Background The mission of U.S. Customs and Border Protection (CBP) is to safeguard America’s borders, thereby protecting the public from dangerous people and materials while enhancing the Nation’s global economic competitiveness by enabling legitimate trade and travel.

The U.S. Border Patrol (USBP) land surveillance mission essential tasks are to detect, identify, classify, and track adversary individuals, groups, and conveyances (i.e., dismounted persons; and land, waterways/coastal, riverine and airborne conveyances) using a variety of capabilities, one of which is mobile surveillance. Waterways/coastal and riverine environments are part of land surveillance. The USBP mission requires the ability to detect, identify, classify, and track, leading to the interception of equipment, vehicles, and humans engaged in or suspected of unlawful border crossing activities. The modular mobile surveillance system (M2S2) will provide capabilities to enable execution of USBP land surveillance mission essential tasks (Figure 1). However, USBP is also seeking additional capabilities that can be achieved through a modular design that allows for the incorporation of other sensors and technology to better support the CBP mission.

Figure 1: USBP Land Surveillance Mission Essential Tasks The M2S2 will be a mobile surveillance asset with the capacity to adapt to shifting threat patterns in various terrain types, be deployed for day or night operational surveillance to provide a variety of surveillance capabilities, and enable operators to monitor potentially illicit activity. The M2S2 will consist of a sensor package, mast, power subsystem, command and control, and communications capability integrated on a commercially available, off-road capable 4x4 vehicle.

The M2S2 surveillance approach incorporates open architecture to support interoperability with other CBP systems, to include, but not limited to Team Awareness Kit (TAK).

M2S2 Operational Effectiveness Requirements These operational requirements shown in Table 1, along with the requirements in the M2S2 Capability Requirements Matrix document in accordance with Section 5.6, will enable the M2S2 to perform the necessary surveillance functions to meet the mission essential tasks listed above.

Table 1: Operational Effectiveness Requirements

Rationale: To be effective, the system needs to operate through at least one shift.

M2S2-OR-04

KPP

Rationale: This would allow an operator to classify the IoI so agents can take appropriate precautions to ensure their safety.

Rationale: Besides visually tracking, the user needs to know the IoI’s geographic coordinates.

Rationale: Items of interest can be stationary, on foot, or in a conveyance.

Rationale: Clarifies need for video recording of events from time of detection to resolution to provide evidentiary purposes.

Note: This allows an operator to slew the sensor on command.

Note: Fleet vehicles are available through the General Services Administration (GSA) and administered through the National Fleet Management System.

M2S2-OR-24

KPP

Note: Time includes from operational unit to operational unit. Material handling equipment (MHE) may be required.

M2S2 Concept of Operation Figure 2 shows a high-level operational concept for M2S2. Each M2S2 will be responsible for monitoring its designated areas of coverage (AoC), providing persistent surveillance and real-time situational awareness to support USBP operations.

The M2S2 mast will elevate its detection and imaging sensors to maximize the AoC and overcome natural obstacles along the border. This elevated positioning ensures an unobstructed line of sight for detecting and tracking IoIs across diverse and challenging environments. The number of M2S2 units deployed within each USBP sector will vary based on geography, operational priorities, and availability of equipment.

Where deployed, the M2S2 will provide operators with high-resolution video and sensor data, supported by advanced artificial intelligence (AI) capabilities. These AI-powered imaging systems enable the automated detection, tracking, identification, and classification of IoI such as individuals, vehicles, drones, and watercraft. The system’s AI capabilities reduce operator workload by providing real-time alerts and actionable intelligence, ensuring that operators can monitor IoI movements with precision and accuracy.

M2S2 integrates seamlessly with communication tools, enabling the operator to share data, including geographic coordinates, imagery, and movement patterns, with field agents and command centers to support coordinated interdiction efforts. This interoperability ensures agents are equipped with the information needed to respond quickly and effectively to emerging threats, enhancing situational awareness and operational effectiveness.

By leveraging its AI-driven technology, modular design, and communication capabilities, the M2S2 will enhance USBP’s ability to adapt to dynamic operational needs, ensuring effective surveillance coverage and timely responses to emerging threats. The system’s deployment will be tailored to the unique requirements of each sector, maximizing its impact on border security operations.

Figure 2: M2S2 Operational View 1 (OV-1) Operational Scenario The M2S2 is designed to operate in diverse and challenging environments, providing advanced surveillance capabilities to support USBP operations throughout an entire shift, typically lasting 8 to 10 hours. An operator drives the M2S2-equipped vehicle to a designated location, navigating rugged terrain, extreme weather, and variable road conditions. Upon arrival, the system transitions from transport mode to mission-ready mode, elevating its mast and activating its advanced sensor suite, including detection and optical sensors.

The M2S2 provides the capability to be operated by an onsite operator in manned mode or to be placed in unmanned autonomous mode and left unattended. While the system is deployed in unmanned autonomous mode, the M2S2 will transmit positively identified IoI to a remote command and control center (C2CEN) and to field agents utilizing TAK. Additionally, health status, diagnostics, and performance metrics will be transmitted to the Network Operations Center (NOC) and C2CEN for monitoring and analysis. This ensures the system’s functionality and performance are continuously monitored, even in the absence of an onsite operator.

While in unmanned autonomous mode, the M2S2 actively monitors its perimeter using integrated physical security sensors. These sensors detect potential security threats, such as unauthorized personnel or vehicles approaching the system, and send alerts to remote operators. This feature enhances the system’s security posture, ensuring operators are informed of potential risks and can take appropriate action to safeguard the system.

In manned and unmanned modes, the M2S2 autonomously scans the area, detecting and tracking IoIs such as individuals, vehicles, drones, and watercraft. The system provides real-time alerts and actionable intelligence to the operator, who can monitor and analyze the data through an intuitive interface and use of the optical sensors. The M2S2 integrates seamlessly with communication tools, enabling the operator to share data, including geographic coordinates, imagery, and movement patterns, with field agents and command centers to support coordinated interdiction efforts. This capability ensures agents are equipped with the information needed to respond quickly and effectively to emerging threats.

The modular design of the M2S2 shall be configurable so that authorized personnel have the capability to reconfigure the system based on operational needs.

The system’s robust design supports extended operations, maintaining functionality and reliability throughout the duration of the shift. In the event of a system failure, the M2S2’s diagnostic capabilities alert the operator, and a backup unit can be deployed to ensure mission continuity.

The M2S2’s advanced capabilities, including its ability to detect, identify, and track IoIs across land, air, and water, make it an indispensable asset for USBP operations. By supporting agents with real-time intelligence and the flexibility to adapt to dynamic situations, the M2S2 plays a critical role in safeguarding the nation’s borders.

Authorities Federal Acquisition Regulation (FAR) Department of Homeland Security Acquisition Regulation (HSAR)

Scope The scope of this requirement includes but is not limited to M2S2 delivery, program management, engineering support, test and evaluation, operator training, train-the-trainer training, warranty, maintenance and logistics support, maintenance training, and delivery of Contract Data Requirements List (CDRL) documents. The Contractor is solely responsible for the execution of this requirement and shall provide all supplies and services necessary for successful delivery of all required deliverables.

Applicable Documents and Attachments The documents listed below support this SOW and are publicly available on the internet.

· DHS Agile Development and Delivery for Information Technology, April 2018

· DHS Technical Review Guide, Version 3.0, February 2022

· USBP Autonomous Surveillance Strategy, June 2022

· DHS Artificial Intelligence Strategy, December 2020

· PMOD Technology Design Principles and Standards for Interoperability, June 2023

· U.S. Border Patrol 2025-2029 Strategy, September 2025

· DHS Technology Readiness Assessment/Manufacturing Readiness Assessment Guide, dated June 2022

· E-Government Act (includes FISMA) (P.L. 107-347), December 2002

· Federal Information Security Management Act of 2014 (P.L. 113-283, Title III)

· Privacy Act of 1974 (P.L. 93-579), as codified by 5 U.S.C. 552a, amended October 4, 2022

· Cybersecurity Enhancement Act of 2014 (P.L. 113-167), amended August 9, 2022

· Title 2, Code of Federal Regulations, Part 200, Subpart F, Audit Requirements

· Office of Management and Budget Memorandum M-17-25, Reporting Guidance for Executive Order on Strengthening the Cybersecurity of Federal Networks and Critical Infrastructure

· Office of Management and Budget Circular No. A-123, Management's Responsibility for Enterprise Risk Management and Internal Control

· Office of Management and Budget Circular No. A-127, Financial Management Systems

· Office of Management and Budget Circular No. A-130, Managing Information as a Strategic Resource

· Executive Order 13587, Structural Reforms to Improve the Security of Classified Networks and the Responsible Sharing and Safeguarding of Classified Information, October 2011

· Executive Order 13636, Improving Critical Infrastructure Cybersecurity

· Executive Order 13800, Strengthening the Cybersecurity of Federal Networks and Critical Infrastructure

· Federal Information Process Standards (FIPS) Publication 140-2 and Annexes A, B, C, and D, Security Requirements for Cryptographic Modules

· FIPS Publication 140-3, Security Requirements for Cryptographic Modules

· FIPS Publication 199, Standards for Security Categorization of Federal Information and Information System

· FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems

· DHS Non-Disclosure Agreement (NDA) Form 11000-6

· CBP Property and Asset Identification and Tagging Standard

· CBP Personal Property and Asset Management Handbook (HB 5200-13C) Attachments M2S2 Capability Requirements Matrix (See Section 5.6) Contract Data Requirements List (CDRL) (See Section 6) Proposed M2S2 Modularity Objectives (See Section 5.6) M2S2 unit delivery The delivered capability shall consist of a M2S2 installed on a 4x4 vehicle that is outfitted with a government-furnished equipment (GFE) land mobile radio (LMR).

The M2S2 will consist of a sensor package, mast, power subsystem, command and control, user interface, autonomy, modularity, and artificial intelligence, all integrated into a commercially available 4x4-capable vehicle.

The M2S2 is composed of two major components:

· Prime Mission Equipment

· Vehicle Installation Kit (suitable for specified vehicle make and model) The Prime Mission Equipment is defined as the operator interface and system payload.

The Contractor shall deliver Vehicle Installation Kit(s) that will allow the Prime Mission Equipment to be installed in the vehicle supplied by either the Contractor or Government as GFE, which will enable the same equipment to be transferred easily from its parent vehicle to an alternative spare/replacement vehicle during periods of vehicular maintenance or replacement. The Contractor shall submit a Material Inspection Acceptance and Receiving Report as described in CDRL #C-L06 with each Vehicle Installation Kit.

The M2S2 overall requirements include open architecture to support interoperability with other CBP systems, to include but not limited to Team Awareness Kit (TAK).

The Contractor is solely responsible for providing the management, personnel, facilities, equipment, and material required as listed below.

Manufacture, ship, and deliver M2S2 units (See Section 5.1.1, M2S2 Technical Requirements).

· Provide M2S2 specific operator, maintenance, and train-the-trainer training (See Section 5.7, and Section 5.7.1).

· Provide warranty service following Government acceptance of M2S2 units (See Section 5.8).

Program Management Effective program management is critical to ensuring the success of the M2S2 initiative, and the Contractor's responsibilities, from developing a comprehensive program management plan (PMP) to leading regular reviews and conferences, will establish a strong foundation for collaboration and progress.

· The Contractor shall develop and deliver a Program Management Plan (PMP) as described in Program Management CDRL #C-PM06.

· The Contractor shall identify a Program Manager (PM) to interface with the Government PM for purposes of assessing the M2S2 Program’s progress and addressing program issues.

· The Contractor shall lead a Post Award Conference at their facility or other location as directed by the Government following award of the contract at a time to be determined by the Government and Contractor. The purpose of the meeting is to review and ensure an understanding of the contract requirements between both parties. Post Award Conference read-ahead materials shall be provided five working days prior to the Post Award Conference as described in CDRL #C-PM03. A Post Award Conference Final Presentation shall be provided by the contractor as described in CDRL #C-PM04. Post Award Conference Meeting Minutes shall be provided by the contractor as described in CDRL #C-PM05.

· A Program Management Review shall be scheduled monthly at a mutually agreed time and location as described in CDRL #C-PM02. Virtual meetings (telephone or video conference) may be used when approved by the Government PM.

· The Contractor shall provide a Monthly Status Report as described in the CDRL #C-PM01.

Quality Control Plan The Contractor shall establish, execute and maintain the necessary process and quality controls to deliver products to the Government that meet contract requirements. The Contractor shall prepare and deliver a Quality Control Plan (QCP) as described in the CDRL C-QC01. The Contractor shall support quality inspections by the Government.

Safety Reporting The Contractor shall monitor the M2S2 for vehicle and equipment recall notices, safety reports, and customer complaints from similar programs and report findings in the Monthly Status Report (CDRL #C-PM-01). Findings which are deemed a safety hazard to operators, maintainers or the general public shall be reported immediately to the M2S2 PM and included in the Monthly Status Report.

Physical Inspection and Functional Checkout The Contractor shall conduct a physical inspection and functional checkout (PIFCO) of each M2S2 to ensure the systems are free from defects, adhere to the latest configuration designs, and are functional. In support of this effort, the contractor shall deliver a PIFCO procedure in accordance with CDRL #C-SE02.

Engineering Support The Contractor shall provide engineering support to ensure successful development, testing, and deployment of the system in accordance with this SOW. The Contractor shall develop and deliver engineering artifacts as listed in Section 6. These engineering artifacts shall include all content specified in the CDRL attachment. This support shall include, but is not limited to, the preparation and delivery of key technical documentation, such as the Technical Data Package (CDRL #C-SE01), Engineering Change Proposal (CDRL #C-SE03), System Description Document (CDRL #C-SE14), and Interface Control Document (CDRL #C-SE11) in accordance with associated CDRLs and DIDs. The contractor shall also facilitate and support technical interchange meetings (CDRL #C-SE10) to ensure alignment with program objectives and address technical challenges. The Contractor shall provide network support services for implementation and connectivity to the CBP network prior to delivery of each system.

AD-HOC ENGINEERING SUPPORT:

The Government has a requirement for the Contractor to quickly provide Ad-Hoc M2S2 Engineering Support when urgently needed and requested by the Contracting Officer’s Representative (COR) or Contracting Officer (CO). All work to be performed under the Ad-Hoc Engineering Support CLIN shall be time and material and shall be pre-authorized and approved by the CO prior to commencement.

M2S2 Ad-Hoc Engineering Support may include but is not limited to the following:

Ad Hoc Mission Support Damage Repairs for damages not covered under warranty or CMLS Engineering Change Proposal (ECP) Development (not ECP implementation) Field Support Maintenance and Logistics Support that is not covered by the exercised CMLS CLIN Newly Required Meetings Other Direct Costs (ODCs) and Incidentals Prototype Development Report Development Technical Documentation Development Technical Reach Back Support Testing Training Travel

M2S2 AD-HOC ENGINEERING SUPPORT REQUIREMENTS

All M2S2 support provided under this CLIN shall comply with the M2S2 Blanket Purchase Agreement (BPA) requirements including but not limited to the M2S2 Capability Requirements Matrix, unless otherwise authorized by the Government.

All M2S2 support provided under this CLIN shall also comply with all applicable Federal, State, and Local codes and standards.

PROCEDURE REQUIREMENTS

The Government will provide a written requirement description of the specific M2S2 support to be performed under the Ad-hoc Engineering Support not covered under warranty support.

The Contractor shall submit a detailed time and material (with not-to-exceed value) quote to perform the requested support.

The quote shall include pricing detail for all associated labor, travel, per diem, services, parts, materials, and any other associated costs.

Quote pricing shall be in accordance with Federal Acquisition Regulation (FAR), Federal Travel Regulations and the M2S2 BPA pricing.

The COR or CO will review the quote for approval or rejection.

The COR or CO will send the Contractor an email approving the NTE value and authorizing the work to be performed by the Contractor.

After the quote is approved and the work is authorized by the COR or CO, the Contractor shall provide the required support in accordance with the written description and delivery schedule requirements.

After the required support has been successfully provided, the Contractor is authorized to submit an invoice for only the actual time and material expenses incurred for the support. The invoice shall not exceed the pre-approved NTE quote value.

The Contractor shall submit a proper invoice in accordance with FAR 32.905 as an attachment in the IPP system.

The Contractor shall submit supporting substantiating evidence such as actual receipts and invoices to support all claimed expenses as an attachment to the invoice.

The Government reserves the right to reject an invoice that does not include supporting substantiating evidence for claimed expenses.

Invoices shall be submitted within 30 days of completion of work.

The Contractor shall notify the COR/CO immediately, as soon as the Contractor becomes aware of any expenses that are beyond the pre-approved NTE, and request approval to increase the approved NTE value.

Any expenses incurred beyond the approved NTE quote value will be rejected for reimbursement.

The Contractor shall not conduct any work under this CLIN without prior authorization and approval from the COR or CO.

Test and Evaluation The contractor shall support all test and evaluation (T&E) activities by providing documentation and onsite technical support during T&E events, troubleshooting and maintenance of systems under test to verify that system performance, functionality, interoperability, and suitability meet the Government operational and functional requirements. The T&E events will include a PIFCO and a developmental test/operational test and evaluation (DT/OT&E). Based on the results of the DT/OT&E, the Government may direct the Contractor to support a follow-on test and evaluation event.

Development Test/Operational Test and Evaluation The Government will develop the DT/OT&E test plan and execute these test events. The Contractor shall support these efforts by providing two test articles, in-person initial operator training (CDRL #C-L01), instrumentation, technical assistance, and onsite maintenance as required. Prior to DT/OT&E, the Contractor shall conduct a PIFCO of the system per CDRL #C-SE02, witnessed by the Government, to ensure all hardware, software, and interfaces are configured and performing properly. Prior to DT/OT&E the Contractor shall deliver the final version of the System Performance Analysis Report (CDRL #C-SE09).

Follow-On Test and Evaluation (Contingent) The purpose of this government-led follow-on test and evaluation (FOT&E) event will be to validate that corrective actions implemented by the Contractor address any identified shortcomings and performance gaps identified in the DT/OT&E test event. The Contractor shall provide modified test articles, technical documentation describing corrections, and onsite support during execution of the government-led FOT&E event.

M2S2 Platform Requirements The M2S2 shall consist of a sensor package, mast, power subsystem, command and control, user interface, autonomy, modularity, and artificial intelligence, all integrated into a commercially available 4x4-capable vehicle. The sensors will be designed and built to function with the software interfaces in a command and control (C2) subsystem. M2S2 units delivered by the contractor shall comply with the requirements found in this SOW and the M2S2 Capability Requirements Matrix .

Truck Requirements The M2S2 truck shall be a new (2025 or newer), unused 4x4 vehicle capable of carrying the M2S2 payload and traversing rugged, remote terrain and shall be equipped with the features listed below.

· All terrain tires

· Color should be earth tone with matte finish

· Consignee delivery (no dealer prep)

· Deactivated daytime running lights

· Fog lights

· V8 gas engine

· Off-road suspension package (heavy duty)

· Rear window electric defroster

· Remote keyless entry

· Mirrors – exterior rearview heated and remote controlled

· Reclining bucket/captain’s chairs

· Original equipment manufacturer (OEM) reverse obstacle sensor or camera

· Enhanced front bumper with brush guard

· Full skid pan

· Dual alternators Enhanced Front Bumper: M2S2 units shall be able to operate off-road. The bumper shall provide protection to the vehicle from front end and cooling system damage during minor collisions and while operating off-road.

M2S2 Environmental Conditions The M2S2 will operate within the conditions outlined in the Operational Environmental Conditions column in Table 2. The M2S2 shall not be operational (e.g., to be turned off or not powered on) and merely survive (e.g., able to operate once environmental conditions improve) within the conditions outlined in the Survival Environmental Conditions column in Table 2.

Table 2: Environmental Conditions

Gusts up to 61 mph (20% beyond average) Average of 60MPH Gusts up to 20% beyond average

MIL STD 810

Winds >95 mph Appropriate MIL 810

Lightning

MIL STD 810

MIL STD 810

N/A

MIL STD 810

N/A

MIL STD 810

N/A

MIL STD 810

N/A

Inclined surfaces need to support only as much snow as can accumulate on the slope involved.

MIL STD 810

N/A

MIL STD 810

Note: Natural freeze-thaw cycle effects can exert great stress on susceptible components of materiel.

N/A

MIL-STD 810

N/A

M2S2 Functional Requirements The M2S2 functional requirements captured in the M2S2 Capability Requirements Matrix – M2S2 Functional Requirements tab outline the requirements necessary to deploy and operate M2S2 units successfully. M2S2 units delivered by the contractor shall comply with the requirements found in the M2S2 Capability Requirements Matrix – M2S2 Functional Requirements document. The Government will base the DT/OT&E plan, procedures and success criteria of evaluation of the M2S2 against the M2S2 Capability Requirements Matrix – M2S2 Functional Requirements.

M2S2 Enabling Functionality The M2S2 shall use open systems architecture, be interoperable/interdependent with other border security systems, and be able to support autonomous operations during the performance of mission essential tasks.

M2S2 Open Architecture The M2S2 units shall incorporate open architecture hardware and software standards into the system integration. The M2S2 architecture shall support the integration of different technologies, facilitate technology refresh, system upgrades, and promote lifecycle affordability. Hardware and software standards and protocols shall be well-defined and openly published to promote compatibility across CBP components, mission systems, and partner agencies. The Contractor shall develop an Open Architecture Plan (CDRL #C-SE16). Reference: PMOD Technology Design Principles and Standards for Interoperability, June 2023.

Modularity The M2S2 system shall be configurable so that authorized personnel have the capability to reconfigure the system. A modular architecture design allows various components, used to create a system, to work interchangeably in an integrated format to support the mission need. The system will incorporate a modular sensor architecture that enables the integration, removal, or replacement of various sensor types and communication systems in support of mission-specific requirements and evolving capability needs. Any combination of modular components will not degrade overall system performance or operational availability; will comply with serviceability requirements, maintainability requirements, and support full operational capability throughout the mission duration and system lifecycle, without necessitating additional modifications.

The Government has also established a set of high-level objectives to address modularity with specific mission requirements and operational challenges. The Contractor’s delivered M2S2 system shall meet the above modularity requirements and all modularity capability objectives proposed by the Contractor and incorporated into the blanket purchase agreement.

M2S2 Interoperability/Interdependency The Contractor shall adhere to the design goals and principles, standards (i.e., general data, technology specific, communications, power, environmental), and data/object and physical interoperability requirements outlined in the Program Management Office Directorate’s (PMOD) Technology Design Principles and Standards for Interoperability, June 2023.

M2S2 Autonomous and Remote Operations The M2S2 shall provide secure system access for users to view and operate the system remotely through any networked device. Accessible data should include, at a minimum, sensor data and system health and status. The Contractor will leverage computer processing advances in graphics processors, communications, commercial sensors, AI, and analytics collection on M2S2. The system shall meet Functional Requirements Document (FRD) requirements to support autonomous operations as specified in the M2S2 Capability Requirements Matrix.

Note: DEFINITION OF AUTONOMOUS. —The term ‘‘autonomous’’ means a system designed to apply artificial intelligence, machine learning, computer vision, or other algorithms to accurately detect, identify, classify, and track items of interest in real time such that the system can make operational adjustments without the active engagement of personnel or continuous human command or control.

M2S2 Operator Training The Contractor shall provide platform specific operator training as described in (CDRL #C-L01). Each training class shall be provided for up to 20 students per class. Training shall include mostly hands-on training with some classroom and/or virtual/digital training. The Contractor shall provide each trainee with one hard copy and one digital electronic copy of the training materials. The Contractor shall also provide the Government with one hard copy and one digital electronic copy of all training materials for each training class. The digital electronic copy shall include demonstration videos which may be used for subsequent training of other trainees. The duration of training shall be no more than eight hours/day for two to four days as appropriate. The Contractor shall provide training materials to the Government when the prototype M2S2 units are delivered for test.

The Contractor shall provide each trainee with one hard copy and one digital electronic copy of the user manual in accordance with (CDRL #C-L04). The Contractor shall also provide the Government with one hard copy and one digital electronic copy of the same user manual.

Training may be at a Government designated training site, or the Contractor’s designated training site (within 25 miles of the relevant USBP Sector Headquarters location) as mutually agreed upon by the Government and Contractor. The Contractor is responsible for providing audio/visual equipment necessary for training. If at a Government facility, a classroom with power and display connectivity will be provided. Upon completion of operator training, the operator shall be able to successfully operate the M2S2 and all its features during day and night operational conditions.

Train-the-Trainer Training The Contractor shall provide train-the-trainer training (T3) as described in CDRL #C-L02. Each training class shall be provided for up to 10 students per class. Training shall include mostly hands-on training with some classroom and/or virtual/digital training.

The purpose of the T3 training course is to instruct USBP agents on how to effectively train and provide new USBP operators with the knowledge and skills necessary to effectively and safely operate the M2S2. The T3 training shall consist of an operator training portion, required in SOW Section 5.7, and an instructional portion focusing on instructional tips for the trainers to replicate the course conduct for attrition training. It shall encompass at least eight hours of instruction providing designated CBP instructors with every opportunity to ask detailed and specific equipment questions, to participate in hands-on training on the equipment, and conduct teach-backs.

The Contractor shall provide each T3 trainee with one hard copy and one digital electronic copy of the user manual in accordance with (CDRL #C-L04). The Contractor shall also provide the Government with one hard copy and one digital electronic copy of same user manual.

The Contractor shall also provide each trainee with one hard copy and one digital electronic copy of the T3 training materials. The Contractor shall also provide the Government with one hard copy and one digital electronic copy of all training materials for each T3 training class. The digital electronic copy shall include demonstration videos which may be used for subsequent T3 training of other trainees.

Training may be at a Government designated training site, or the Contractor’s designated training site (within 25 miles of the relevant USBP Sector Headquarters) as mutually agreed upon by the Government and Contractor. The Contractor is responsible for providing audio/visual equipment necessary for training. If at a Government facility, a classroom with power connectivity will be provided.

Upon completion of T3 training by a Border Patrol Agent (BPA), the BPA trainer shall be able to successfully train other USBP agents to effectively operate the M2S2 and all its features.

M2S2 Warranty The contractor shall provide, at a minimum, an OEM warranty period of 12 months, effective upon the date each unit is accepted. The warranty shall cover the entire M2S2 unit and shall include, but not be limited to:

· sensors, operator control station, mast, power subsystem, and all associated hardware and software;

· all parts and labor; and

· all system software (i.e., patches and version upgrades).

If the contractor provides the truck platform, the OEM warranty shall be transferred to the Government following inspection and acceptance.

Under the warranty (excluding the truck platform), the Contractor shall repair/replace any unit defects and provide all necessary labor, technical support, materials, shipping/handling, and travel to do so at no additional cost to the Government. The Government and the Contractor will coordinate shipment, repair times and free onboard destination delivery when the repaired unit is returned.

All component manufacturer warranties which extend beyond the one-year warranty shall convey to the Government upon expiration of the initial warranty period.

The Contractor shall provide a monthly Warranty Performance Report to the Government on all warrantied and non-warrantied repairs as described in CDRL #C-L05.

Configuration Management The Contractor shall be responsible for maintaining a configuration baseline for test units, low-rate initial production, and full-rate production M2S2 units. The Contractor shall document the M2S2 baseline in the Common Configuration Baseline Report (CDRL #C-SE13). All implemented changes shall be retrofitted into previously delivered vehicles to maintain a baseline configuration.

Any M2S2 delivered after acceptance of the first two platforms shall conform to the M2S2 Common Configuration Baseline. The Contractor shall submit a Material Inspection Acceptance and Receiving Report as described in CDRL #C-L06 for each M2S2 ordered by the Government. The Contractor will be required to update the test units to the same configuration as the full rate production units.

The Contractor shall deliver Vehicle Installation Kit(s) that will allow the Prime Mission Equipment to be installed in the vehicle supplied by either the Contractor or Government as GFE, and which will enable same equipment to be transferred easily from its parent vehicle to an alternative spare/replacement vehicle during periods of vehicular maintenance or replacement. In support of this effort, the Contractor shall deliver Vehicle Installation Kit Procedures (CDRL #C-L07). The Contractor shall submit a Material Inspection Acceptance and Receiving Report as described in CDRL #C-L06 for each Vehicle Installation Kit ordered by the Government.

Vehicle Installation Kit Verification Prior to the start of the DT/OT&E pre-test and after delivery of GFE, the Contractor shall conduct a verification of the installation of the Vehicle Installation Kit onto the trucks. The purpose of this event is to demonstrate the contract requirement in the FRD the time it takes to install the Vehicle Installation Kit and verify the accuracy of the Vehicle Installation Kit Procedures in CDRL #C-L07. This verification shall be witnessed by the Government, conducted in accordance with the Vehicle Installation Kit Procedures (CDRL #C-L07) and verified in accordance with the FRD. The Vehicle Installation Kit Verification shall not exceed one day.

Government-Furnished Equipment The Government will provide as GFE a Land Mobile Radio (LMR) and TAK hardware license transition schedule. The Government shall be responsible for the installation of the LMR in each vehicle. 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.

Hardware Requirements USBP M2S2s are required to be connected to the CBP network for scanning, patching, and remediation compliance. Additionally, M2S2s are required to follow all applicable USBP network policies.

CBP Network Connectivity USBP M2S2s are required to be connected to the CBP network for scanning, patching, and remediation compliance. Additionally, M2S2s are required to follow all applicable USBP network policies. The Contractor shall procure authentic CISCO hardware listed in Table 3 and Table 4 from authorized CISCO vendors and integrate onto the M2S2. The Contractor shall provide a Network Description Document (CDRL #C-SE12) to support the system connectivity to the CBP network. The Contractor shall ensure hardware licenses are transferred from the Contractor to CBP prior to the delivery of M2S2s. IP-addressable hardware must have unique IP addresses which must be provided by the CBP network team. The contractor shall provide a list of addressable hardware devices or a total number or IP addresses required for the solution.

All Contractor personnel accessing the CBP network must obtain a CBP BI before access to the CBP network and hardware configurations can be granted.

Figure 3 below provide a reference to network design with CISCO hardware incorporated onto an M2S2. These diagrams are for reference only. The Contractor shall develop a network diagram specific to the delivered solution as part of CDRL #C-SE12 Figure 3: Notional M2S2 Network Diagram for Multiple Communication Paths

The contractor shall provide all of the associated hardware in Table 3 and Table 4. This hardware is necessary for the system to operate on the CBP network.

Table 3: CISCO Router Hardware Part Number and Associated Hardware

CISCO Router BOM

Table 4: Layer 3 Switch Hardware Part Number and Associated Hardware

CISCO Layer 3 Switch

IE-3300 8-port switch

IE-3300 8-port Expansion module (as needed)

Hardware Frequency Authorization and Compliance The Contractor shall ensure equipment complies with federal radio regulations as prescribed by the National Telecommunications and Information Administration (NTIA) that includes approved Radio Frequency Authorization (RFA) and equipment certifications. The Contractor shall ensure that all frequencies required to operate the M2S2 unit are approved via submission of the Radio Frequency Assignment Request (CDRL #C-SE07) and up to date under experimental or permanent frequency assignments throughout verification and operational testing of the M2S2. The Contractor shall be responsible for coordination and compliance with all applicable federal regulations governing frequency usage and emitter certification necessary through the CBP Spectrum Office. The Contractor shall develop an Electromagnetic Interference (EMI)/Electromagnetic Compatibility (EMC) Plan (CDRL #C-SE06).

Maintenance and Logistical Support Integrated Contractor Support Plan The Contractor shall deliver an Integrated Contractor Support Plan (ICSP) per (CDRL #C-L08).

The ICSP shall describe the Contractor’s plan to conduct Contractor Maintenance and Logistical Support (CMLS) as described in Section 5.11.2. Prior to Government acceptance of test units, the Contractor shall conduct an overview briefing of the CMLS approach described in the ICSP (CDRL #C-L08) to the M2S2 PM.

Maintenance The M2S2 supportability and sustainment concept consists of Organizational-level (O-level) and Depot-level (D-level) maintenance of all warrantied and non-warrantied system components, to include but not limited to sensors, operator control station, mast, power subsystem, and all associated hardware/software and firmware.

M2S2 systems will be supported under a CMLS agreement for a base year period of 12 months, with the option to extend it to four additional 12-month option periods. The M2S2 Contractor will be responsible for contract sustainment support, to include but not limited to, both O-Level and D-Level corrective maintenance and preventive maintenance, for each designated sector. For safety reasons, nighttime maintenance is unlikely. After the base 12-month period of CMLS, the Government may exercise its option to transition and assume responsibility for M2S2 support as described in the Transition Plan (CDRL #C-L09) and provide a Maintenance Manual (CDRL #C-L10).

When providing maintenance support within a USBP sector, the Contractor will perform all maintenance actions within a one-hour drive of the USBP Sector Headquarters, or…