Marines Test USV for Littoral Explosive Ordnance Disposal Operations

Overview

The Marine Corps Program Manager Combat Support Systems completed a Field User Evaluation of an Unmanned Surface Vessel (USV) as part of the Littoral Explosive Ordnance Neutralization System (LEON) at Camp Pendleton. That validation establishes a pathway to fielding USV systems to EOD companies in FY2027, with full LEON family integration planned within two years. For contractors, this signals an emerging procurement opportunity for autonomous maritime systems that include sonar, FLIR, and robust communications tailored to littoral explosive ordnance disposal operations. Affected agencies include DOD, USMC, and NAVSEA, and follow-on solicitations are likely to appear on contract vehicles and agency procurement portals. Action is needed now to align technical capabilities, capture plans, and compliance posture before formal solicitations and integration timelines accelerate. See the Winning Federal Contracts Guide (/insights/winning-federal-contracts) for capture planning basics and consult the CMMC (Cybersecurity Maturity Model Certification) Compliance Guide (/insights/cmmc-compliance-guide) and CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide) for handling controlled unclassified information during capture.

Immediate Actions (This Week)

• [ ] Monitor for the official solicitation and follow-on notices — watch agency portals and contract vehicle sources for listings related to LEON and USV procurements.
• [ ] Map your product and subsystem capabilities to the LEON needs called out in the event: sonar, FLIR, and communications integration for littoral EOD operations.
• [ ] Update or create a concise capability statement and one-page technical summary emphasizing autonomous maritime experience, sensor integration, and any relevant past performance.
• [ ] Confirm current positions on major contract vehicles and marketplace footholds (check availability on SeaPort‑NxG, OASIS+, and GSA (General Services Administration) MAS) and identify immediate teaming/subcontracting prospects.
• [ ] Run a quick compliance triage against named regimes (NIST 800-171 (NIST Special Publication 800-171), CMMC, DFARS (Defense Federal Acquisition Regulation Supplement) 252.204-7012, ITAR (International Traffic in Arms Regulations), NDAA (National Defense Authorization Act) Section 889) to identify any critical showstoppers.

Short-Term Actions (30 Days)

• [ ] Conduct a technical gap analysis: hardware, software (autonomy stack), sensor fusion (sonar/FLIR), and comms integration testing requirements to meet littoral EOD mission profiles.
• [ ] Complete a compliance gap assessment and remediation plan for the explicitly named regimes (NIST 800-171, CMMC, DFARS 252.204-7012, ITAR, NDAA Section 889) and schedule remediation milestones.

Long-Term Actions (90+ Days)

• [ ] Build or mature a prototype or demonstration plan that integrates sonar, FLIR, and communications components in a maritime USV form factor suitable for EOD mission demonstrations.
• [ ] Execute a capture plan: firm up teaming agreements and subcontracts under SeaPort‑NxG, OASIS+, or GSA MAS as appropriate; prepare past performance narratives and test/demonstration evidence aligned to LEON objectives.
• [ ] Institutionalize cybersecurity and export-control processes so proposals can assert compliance and flowdown readiness ahead of solicitations tied to FY2027 fielding.

Compliance Checklist

• [ ] NIST SP 800-171 (NIST Special Publication 800-171) — perform/maintain a System Security Plan (SSP) and Plan of Action & Milestones (POA&M) for any Controlled Unclassified Information (CUI) in scope.
• [ ] CMMC — assess current maturity level requirements and prepare for an organizational readiness assessment aligned to solicitation expectations.
• [ ] DFARS 252.204-7012 — ensure DFARS flowdown implementation, incident reporting capability, and alignment with NIST 800-171 controls for defense contracts.
• [ ] ITAR — validate registration with the Directorate of Defense Trade Controls (DDTC) and establish export-control handling for technical data and hardware that may be ITAR‑controlled.
• [ ] NDAA Section 889 — verify telecommunications and equipment sourcing compliance per the statute’s restrictions where applicable.

Resources

• DFARS 252.204-7012 (regulation name referenced)
• NIST SP 800-171 (regulation name referenced)
• CMMC (framework name referenced)
• ITAR (regulation name referenced)
• NDAA Section 889 (statute name referenced)
• Agencies: DOD, USMC, NAVSEA (agency names referenced)
• Contract vehicles to monitor: SeaPort‑NxG, OASIS+, GSA MAS (vehicle names referenced)

Additional reading and capture best practices: Winning Federal Contracts Guide (/insights/winning-federal-contracts), CMMC Compliance Guide (/insights/cmmc-compliance-guide), CUI-Safe CRM Guide (/insights/cui-safe-crm-guide).

How Cabrillo Club Automates This

Cabrillo Signals War Room — Already detected this event and delivered this briefing within minutes. War Room continuously monitors federal sources for regulatory changes, contract vehicle updates, policy shifts, and program milestones (including LEON/USV fielding notices) so your capture team receives early warnings and briefing context as items hit the record.

Cabrillo Signals Match Engine — When an event like this is detected, the Match Engine automatically rescales your opportunity pipeline: it updates match scores for opportunities that rely on maritime autonomy, sensor suites (sonar/FLIR), communications, or EOD mission alignment; reprioritizes opportunities tied to DOD/USMC/NAVSEA; and updates keyword relevance so your capture list reflects the new LEON-related prospects.

Cabrillo Signals Intelligence Hub — The Intelligence Hub tracks affected agencies, NAICS codes, and contract vehicles. Use saved searches for LEON/USV-related keywords and configure alerts to notify you when matching solicitations appear on SAM.gov (System for Award Management) or when contract‑vehicle opportunities (SeaPort‑NxG, OASIS+, GSA MAS) are updated. It consolidates agency notes and historical procurement patterns for faster bid/no‑bid decisions.

Proposal Studio (Proposal OS) — Proposal Studio generates first‑draft technical approaches and compliance matrices tailored to this event by pulling from your past performance library and win themes. It produces an initial DFARS/NIST compliance matrix and an ITAR/export-control statement draft to include in capability packages, accelerating the response timeline once a solicitation posts.

Proposal Studio Workflow Tracker — The Workflow Tracker codifies a 9‑gate capture workflow triggered by this event: opportunity qualification, compliance review, teaming approvals, demo evidence collection, proposal assembly, final QA, and post‑submission audit package generation. It routes required compliance reviews to contracts and legal, tracks supplier certifications, and keeps an audit-ready record of flowdowns and approvals.

Call to action: Log into your Cabrillo Club dashboard to review the War Room briefing, enable the Intelligence Hub saved search for LEON/USV, and run an automatic match-rescore in the Match Engine to reprioritize your pipeline.

Related reading: Winning Federal Contracts Guide (/insights/winning-federal-contracts), CMMC Compliance Guide (/insights/cmmc-compliance-guide), CUI-Safe CRM Guide (/insights/cui-safe-crm-guide)