CUAS ADFOR Support PWS (SSN).docx

Performance Work Statement (PWS) Counter-UAS (CUAS) Adversary Force (ADFOR) Support For 2d Marine Division (MARDIV)

1. Introduction & Background

2d MARDIV and subordinate commands require an ADFOR drone and swarm threat to increase overall proficiency for detecting, tracking, and mitigating threats. The requirement is not only drone presence, but dynamic, high-volume UAS swarm threats in the form of RED CELL to test effectiveness of Marine Corps tactics, techniques, and procedures (TTPs), specifically in a near-peer environment on the battlefield. The RED CELL shall create an environment to mirror adversarial threats to the Ground Combat Element (GCE) operations within the exercise Area of Operations (AO). The RED CELL shall replicate passive and active physical, visual, and radio frequency (RF) drone capabilities and tactics, techniques, and procedures (TTPs) to mirror Violent Extremist Organizations (VEOs) and peer/near peer adversaries. Training in these simulated contested environments is critical to prepare the Marines of 2d MARDIV to deploy and support full-spectrum operations as part of the larger joint and coalition force. Training is still undergoing planning for specific locations listed in para 3.2.2 and 3.2.3 and the vendor will need to coordinate with 2d MARDIV G-3 for exact locations upon award.

This PWS establishes the requirement for ADFOR drone presence and swarm threat during unit training evolutions for Marine Corps Combat Readiness Evaluation (MCCRE), Service Level Training Exercise (SLTE), Integrated Training Exercise (ITX), Deployment for Training (DFT) and Home Station unit-level training from July through October, 2026.

2. General Requirement

The contractor shall provide drones and swarms during the entirety of large-scale exercises that mimic VEOs and peer/near adversaries. The contractor will provide feedback to commanders with data regarding observations, assessment of TTPs, and best practice recommendations to enhance lethality and survivability on the battlefield, with a focus on battalion and company sized maneuvers. The brief will go on 29 October to 2d Marine Regiment Commanders and key staff members aboard Camp Lejeune, NC. If the contractor noted significant improvements from the start of the exercise to the finish, it is preferred that the contractor can speak to which specific TTPs were the most effective.

3. Requirements

The contractor shall embed themselves in the RED CELL and engage a battalion sized element up to 2000 feet with group 1 and group 2 UAS. The contractor shall engage in persistent surveillance as well as First-Person View (FPV) swarm attacks against the formation. For the purposes of this contract a swarm is determined to be ten UAS. The contractor shall provide all necessary training resources (i.e. personnel, materials, supplies, and equipment necessary to execute the above-end state.). 2d MARDIV will be responsible for range access and waiver approvals of spectrum usage and flight approvals. Contractor will utilize drones with the capability of observation and be able to simulate attacks on company formations, down to squad size elements. UAS should be consistent with what near peer adversaries are using in real time. The assets used by the Contractor in this training requirement are not required to be Blue UAS or NDAA compliant.

3.1 Training Days

V22 Marine Corps Combat Certification Exercise (MCCRE) CLNC 4-10 October 2026 (tentative dates until further planning conferences).

Iteration 1 Day 1 (4 October 2026): ADFOR drone activity IVO Battalion Defense Day 2 (5 October 2026): ADFOR drone activity IVO Battalion Defense Day 3 (6 October 2026): ADFOR Drone Swarm on Battalion Defense Day 4 (7 October 2026): ADFOR Drone activity IVO Combat Town Iteration 2 Day 1 (8 October 2026): ADFOR drone activity IVO Battalion Defense Day 2 (9 October 2026): ADFOR drone activity IVO Battalion Defense Day 3 (10 October 2026): ADFOR Drone Swarm on Battalion Defense

V22 Infantry Training Exercise (ITX) 4-26 3-7 August 2026 29 Palms, CA (ranges still pending due to exercise in planning phase).

Iteration 1 Day 1 (3 August 2026): ADFOR drone activity IVO CUAS lane training Day 2 (4 August 2026): ADFOR drone activity IVO CUAS lane training Day 3 (5 August 2026): ADFOR Drone Swarm on CUAS lane training Iteration 2 Day 1 (6 August 2026): ADFOR drone activity IVO CUAS lane training Day 2 (7 August 2026): ADFOR drone activity IVO CUAS lane training

The Contractor shall provide a minimum of one (10) ten UAS drone swarm per CUAS lane training when the element size is equal to a Platoon or Company level.

Exact dates and specific locations are subject to change based on future planning conferences.

4. Place of Performance

ADFOR Drone activity for days 1-4 (Iteration 1) for MCCRE will be conducted aboard CLNC at the V26/V12 Training Areas, Camp Lejeune, NC 28547.

ADFOR Drone activity for days 5-7 (Iteration 2) for MCCRE will be conducted aboard CLNC at the V22 Training Areas, Camp Lejeune, NC 28547

ADFOR Drone activity for 1-5 (Iteration 1 & 2) for ITX will be conducted aboard 29 Palms, CA IVO CUAS lane Training. 29 Palms, CA 92277

5. Deliverables

6. Government Responsibilities

6.1 Logistics: The Government will not provide lodging or meals for Contractor personnel. The Government will provide transportation to and from the training sites solely for Government personnel. The Contractor is strictly responsible for providing their own transportation capabilities for all Contractor personnel and equipment (including off-road capable vehicles if required to access remote range locations at Camp Lejeune or MCAGCC Twentynine Palms).

6.2 Planning and Scheduling: The Government will provide the Contractor with a minimum of four (4) weeks’ notice to schedule a training event, which will include the requested location of the training. Additionally, the Government will provide the Contractor with the RED CELL scheme of maneuver no later than fourteen (14) days in advance of each scheduled training evolution.

6.3 Range, Airspace, and Clearances: The Government (via 2d MARDIV G-3) will be responsible for coordinating and approving all frequency requests, airspace waivers, and range approvals.

6.3.1 Contractor Prerequisite: To facilitate these Government approvals, the Contractor shall provide a comprehensive list of all UAS platforms intended for use (including make, model, weight, payload, operating frequencies, and transmission power) to the 2d MARDIV G-3 within ten (10) post-award days, or as directed by the COR. Failure by the Contractor to provide accurate technical data on time, resulting in denied range access, shall be considered a Contractor performance failure.

7. Contractor’s Unauthorized Work Performance and Scope Changes The Contractor shall not perform work that deviates from the contract requirements, specifications, or established schedule.

7.1 Contracting Officer Authority

Only the warranted Contracting Officer (KO) has the authority to change the scope of work, alter the contract price, or modify the period of performance. If the Contractor deviates from the contract requirements without the prior, written approval of the KO, such deviation shall be strictly at the risk of the Contractor, and any costs related thereto shall be borne entirely by the Contractor.

7.2 Unauthorized Commitments

Government personnel, including the Contracting Officer’s Representative (COR), Exercise Directors, or unit-level Commanders participating in the training, do NOT have the authority to direct the Contractor to perform work outside the scope of this PWS or alter the terms of the contract. The Contractor shall immediately notify the KO if they perceive any direction given by Government personnel constitutes a change to the contract scope.

8. Applicable Documents and References: The contractor shall ensure that the Adversary Force (ADFOR) threat replication creates a realistic training environment that allows the 2d Marine Division (MARDIV) training audience to execute, evaluate, and improve upon the following Marine Corps Tasks (MCTs).

8.1 Supported Marine Corps Tasks (MCTs):

The primary focus of this training support is to stress the training audience's defensive and passive security postures. The environment generated by the contractor shall directly support the evaluation of:

9. Installation Access and Security Requirements (MCAGCC Twentynine Palms)

9.1. General Access Policy

The Contractor shall comply with all current Marine Corps Air Ground Combat Center (MCAGCC) access procedures throughout all performance periods under this contract. The Government will not be responsible for any contractor access delays. Delays resulting from inadequate planning or failure to comply with installation security procedures are strictly the responsibility of the Contractor and shall not constitute grounds for claims or requests for equitable adjustment. Daily access procedures must not be used to circumvent mandatory background check requirements.

9.2. Access Tiers

Contractor personnel are required to obtain the appropriate level of access based on their performance duration:

9.3. Pre-Arrival Vetting & Sponsorship

Before arriving at the PMO, the Contractor must ensure the following are completed:

· Background Checks: Conducted at the Contractor's expense. Must establish U.S. citizenship or legal alien status and include a criminal record check from the county/state of residence for the previous two years.

· Combat Center Access Authority Letter: The Contractor must coordinate with the Regional Contracting Office (NW) or their designated government sponsor to obtain this authorization letter prior to arriving at the vetting office.

9.4. Required Documentation for Credentialing

To obtain a Defense Biometric Identification System (DBIDS) credential or temporary pass, Contractor personnel must report to the PMO or Contractor Vetting Office with the following original documents (copies/notarized copies are not accepted):

9.5. Contractor Vetting Office (CVO) Contact & Location

If you have questions regarding base access, Contractor Common Access Cards (CACs), or DBIDS requirements, please contact the local Contractor Vetting Office (CVO) / Pass and ID Office.

CVO Location

Hours of Operation

Contractor Vetting Office - Appointments:

Contractor Vetting Office - Questions:

Vetting Email

Contractors will report to the Contractor Vetting Office (CVO) to confirm their access requirements, undergo a background check, and receive their credential/pass.

9.6. Denial of Access and Appeals

The Commanding General, MCAGCC, has broad authority to remove or exclude any person to protect personnel, property, and the Marine Corps mission. Access may be immediately denied or revoked for reasons including, but not limited to:

· Presence on the National Terrorist Watch List.

· Illegal presence in the United States.

· Outstanding arrest warrants (individuals may be subject to arrest on the spot).

· Registered sex offender status.

· Submission of false or fraudulent employment/vetting information.

· Active debarment orders banning the individual from military installations.

Appeals: Persons denied access may appeal the decision to the Commanding General by initiating a request through the PMO Vehicle Registration and Pass Office. Note: Individuals with active warrants must resolve the warrant prior to initiating any appeal. If a sponsor or the Contractor's own company denies access, the Government appeal process does not apply.