2d MarDiv CUAS ADFOR Support

Performance Work Statement (PWS) Counter-UAS (CUAS) Adversary Force (ADFOR) Support For 2d Marine Division (MARDIV) 1.0 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) from the date of award through October, 2026. 2.0 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.0 Performance 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 Marine Corps Combat Readiness Evaluation (MCCRE) 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 The Final Planning Conference (FPC) is currently scheduled for 2 September, 2026. The Contractor shall begin active communication and planning with the Government upon award. 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. 3.2 Swarm Engagement and Red Cell Requirements 3.2.1 Simulated Payloads: The contractor’s UAS platforms are authorized to carry inert, simulated payloads (such as inert drop-mechanisms or training LED visual effects) to simulate tactical battlefield effects and allow the training audience to recognize physical weaponization. All simulated payloads must be technical-safety cleared by Range Control and G-3. 3.2.2 FPV Swarm Attacks: Multiple airborne drones that must be deterred along one vector or multiple vectors and able to perform simultaneous or near-simultaneous strikes on a point target or a target array. 3.2.3 Frequencies: The Regiment and Division spectrum managers will coordinate RF spectrum clearances for the contractor's UAS platforms. Technical submittals must be received at least twenty-five (25) days prior to range execution. In the event of a denied frequency, the Government and contractor will coordinate alternative frequencies or negotiate alternative platform lists without penalty. 3.2.4 Red Cell Scheme of Maneuver: A successful swarm engagement from the Red Cell perspective will be Red Cell-oriented. The Red Cell will be able to achieve simultaneous or near simultaneous impacts on a point target or array target. Friendly oriented – the formation being targeted performs appropriate immediate actions and relays information to their HHQ which drives hardening at adjacent sites to the target formation. 3.3 Surveillance: The contractor shall provide continuous overwatch to maintain persistent surveillance across the entire battalion Area of Operations (AO) during active training windows. Specific mission tasking, search…