Marine Corps Establishes Robotics Integration Group, Experiments with Drones in Field Operations

TL;DR

The U.S. Marine Corps has established the Marine Corps Robotics Integration Group (MCRIG) and the Marine Corps Counter Drone Team (MCCDT) to standardize and institutionalize training and counter-UAS capabilities for small unmanned aircraft systems (UAS) across the force. This organizational change signals increased institutional focus and investment in drone and counter-drone technologies and a push for rapid integration and experimentation of small UAS capabilities. The immediate effect is expanded opportunity for contractors that support Group 1/2 UAS, counter-UAS systems, training curriculum development, and related sustainment and professional services. Contractors operating to the listed NAICS codes and market segments should expect an accelerated procurement and experimentation cycle and should prioritize capture and compliance readiness. Monitor solicitations against the identified contract vehicles and compliance surfaces, and prepare to bid on rapid prototyping, training, and sustainment tasking as solicitations appear. Timeline for specific solicitations and program milestones is TBD pending source review.

Key Points

• What happened: The Marine Corps established the Marine Corps Robotics Integration Group (MCRIG) and the Marine Corps Counter Drone Team (MCCDT) to standardize training and counter-UAS capabilities for small UAS across the force.
• Who is affected: Defense contractors in the listed market segments and NAICS codes, and the agencies DOD and USMC.
• Timeline: Timeline TBD pending source review.
• What contractors should do NOW: validate capability alignment to Group 1/2 UAS and counter-UAS, confirm applicable compliance posture (see compliance surfaces), update capability statements and capture packages for rapid-experimentation and training tasking, and enable continuous monitoring for follow-on solicitations via saved searches and alerts.

Who Is Affected

• Market segments: Defense; Unmanned Systems; Counter-UAS; Training and Simulation; Professional Services; Aerospace and Defense Manufacturing.
• NAICS codes: 336411, 336413, 334511, 541330, 541512, 541519, 611430, 611512.
• Agencies: DOD; USMC.
• Contract vehicles (explicitly named in segmentation): ASTRO; OASIS+; STARS III.
• Compliance regimes and regulatory surfaces (explicitly named in segmentation): CMMC (Cybersecurity Maturity Model Certification); NIST 800-171 (NIST Special Publication 800-171); ITAR (International Traffic in Arms Regulations); DFARS (Defense Federal Acquisition Regulation Supplement) 252.204-7012; NDAA (National Defense Authorization Act) Section 848.

Specific NAICS codes, agencies, and contract vehicles are listed above as provided. Program-level timelines and solicitation dates are TBD pending source review.

Frequently Asked Questions

Q: Will this reorganization lead to immediate solicitations for UAS and counter-UAS systems?

A: The Summary indicates an accelerated procurement and experimentation cycle for small UAS technologies, but specific solicitations, timelines, and award vehicles are TBD pending source review.

Q: What UAS sizes and categories should contractors prioritize?

A: The Summary specifically highlights small unmanned aircraft systems and Group 1/2 UAS as focal points. For further granularity on technical specifications or preferred platforms, pending source review.

Q: What compliance and security requirements should firms prepare for?

A: The segmentation identifies CMMC, NIST 800-171, ITAR, DFARS 252.204-7012, and NDAA Section 848 as relevant compliance surfaces. Firms should validate their current posture against those requirements and remediate gaps immediately.

Definitions

• Marine Corps Robotics Integration Group (MCRIG): The Marine Corps organization established to standardize and institutionalize training for small UAS and related capabilities across the force.
• Marine Corps Counter Drone Team (MCCDT): The Marine Corps organization established to focus and coordinate counter-UAS capabilities and operations.
• small unmanned aircraft systems (UAS): Small aerial platforms used for reconnaissance, sensing, and tactical applications; the Summary highlights rapid integration of these systems.
• Group 1/2 UAS: UAS size/weight categories referenced in the Summary as priority areas for integration and experimentation.
• counter-UAS: Systems and tactics intended to detect, mitigate, or defeat unmanned aircraft.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Use War Room feeds to track amendments, policy memos, and initial tasking announcements related to MCRIG and MCCDT.
• Cabrillo Signals Match Engine — Reprice and rescore your active opportunity pipeline immediately to reflect elevated priority for Group 1/2 UAS, counter-UAS, training, and rapid-experimentation workstreams.
• Cabrillo Signals Intelligence Hub — Configure saved searches for the listed NAICS codes, agencies (DOD, USMC), and contract vehicles (ASTRO, OASIS+, STARS III). Enable SAM.gov (System for Award Management) monitoring alerts for follow-on solicitations and notices.
• Proposal Studio (Proposal OS) — Prepare compliant proposal skeletons, compliance matrices, and win themes for training and rapid prototyping solicitations; store CMMC/NIST/DFARS artifacts and control versions.
• Proposal Studio Workflow Tracker — Launch a 9-gate capture workflow for any high-priority opportunities discovered; route compliance reviews and security artifacts automatically and maintain an audit-ready trail.

Who to notify: Capture Lead, Business Development Lead, Chief Technology Officer / Engineering Lead, Security & Compliance Officer, Program Manager for rapid prototypes. These roles should receive the initial alert and be assigned immediate actions.

First 48-hour playbook

• Hour 0–4: Validate event in Cabrillo Signals War Room; create saved search in Intelligence Hub for NAICS, agencies, and contract vehicles; run Match Engine to rescore pipeline and flag priority opportunities.
• Hour 4–12: Convene capture team (BD, Capture Lead, CTO, Security), perform capability gap analysis against Group 1/2 UAS and counter-UAS needs, and record compliance gaps against CMMC/NIST/DFARS.
• Hour 12–24: Use Proposal Studio to assemble capability statements, draft rapid-experimentation approach papers, and run bid/no-bid decision in Proposal Studio.
• Hour 24–48: Start 9-gate capture in Proposal Studio Workflow Tracker for target opportunities; assign tasks, prepare compliance artifacts for DFARS/ITAR reviews, and schedule outreach to prime partners and program offices.