2 defense tech companies sue US Navy after losing out on MUSV program

TL;DR

Two defense tech firms, Blue Water Autonomy and Saildrone, filed federal lawsuits after being excluded from the U.S. Navy's Medium Unmanned Surface Vessel (MUSV) Family of Systems program. The plaintiffs allege the Navy failed to follow its own requirements and applied overly restrictive evaluation criteria; Blue Water Autonomy has asked the court to halt MUSV testing and funding until it can re-enter the competition. The Navy has already selected seven other companies to proceed with at-sea prototype testing, making this a material procurement dispute. This challenge creates near-term program uncertainty and could slow the MUSV acquisition timeline, affect competition, and trigger re-evaluation or protest actions. Contractors in maritime unmanned systems, autonomy, and supporting technology lines should assume increased scrutiny on evaluation processes and prepare for potential schedule shifts and solicitation revisions.

Key Points

• Two defense technology companies (Blue Water Autonomy and Saildrone) sued after being excluded from the U.S. Navy's MUSV Family of Systems program; plaintiffs allege noncompliance with Navy requirements and overly restrictive evaluation criteria.
• Affected segments: Defense; Unmanned Systems; Maritime Technology; Autonomous Vehicles; Naval Systems. Specific NAICS codes: 336611, 541712, 541715, 336992, 541330. Affected agencies: DOD; Department of the Navy. Contract vehicle: MUSV Family of Systems. Compliance surfaces: DFARS (Defense Federal Acquisition Regulation Supplement), ITAR (International Traffic in Arms Regulations), NIST 800-171 (NIST Special Publication 800-171), CMMC (Cybersecurity Maturity Model Certification).
• Timeline: Timeline TBD pending source review.
• What contractors should do NOW: Preserve protest and proposal materials, ensure compliance controls for DFARS/ITAR/NIST/CMMC are audit-ready, notify capture/BD/contracts/compliance leadership, and use Cabrillo Club products to re-score pipelines, monitor solicitations, and accelerate compliant proposal readiness.

Who Is Affected

Companies and teams operating in Defense, Unmanned Systems, Maritime Technology, Autonomous Vehicles, and Naval Systems. Specific NAICS codes explicitly identified in segmentation: 336611, 541712, 541715, 336992, 541330. Affected agencies explicitly identified: DOD and Department of the Navy. Contract vehicle explicitly identified: MUSV Family of Systems. Compliance regimes explicitly identified: DFARS, ITAR, NIST 800-171, CMMC.

Frequently Asked Questions

Q: Why were the lawsuits filed?

A: According to the Summary, Blue Water Autonomy and Saildrone filed federal suits after being excluded from the Navy's MUSV Family of Systems competition; they allege the Navy did not comply with its own requirements and used overly restrictive evaluation criteria. Blue Water Autonomy also requested a halt to MUSV testing and funding.

Q: Will the MUSV program be delayed?

A: The Summary states this is a significant procurement dispute that could impact the Navy's unmanned surface vessel acquisition timeline. Whether the program will be delayed is pending source review and will depend on the court actions and any Navy response.

Q: What immediate actions should contractors take regarding compliance and capture?

A: Contractors should preserve proposal and protest documentation, validate compliance with DFARS/ITAR/NIST 800-171/CMMC requirements, notify capture, BD, contracts, and security/compliance teams, and actively monitor for solicitation changes or re-openings. Use Cabrillo Club platforms to rescore opportunities and prepare compliant proposals.

Definitions

• MUSV (Medium Unmanned Surface Vessel) Family of Systems: The Navy program referenced in the Title and Summary focused on medium-sized unmanned surface vessels and associated systems.
• At-sea prototype testing: Sea trials where selected companies demonstrate prototypes in operational maritime environments as part of the MUSV Family of Systems selection process.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. War Room continuously monitors protests, litigation, and changes in contract vehicle activities to flag events that alter competitive dynamics.
• Cabrillo Signals Match Engine — Will automatically rescore opportunity pipelines and adjust win probabilities for MUSV and related solicitations when litigation or selection changes shift the competitive landscape.
• Cabrillo Signals Intelligence Hub — Tracks the affected agencies (DOD, Department of the Navy), NAICS codes, and the MUSV Family of Systems contract vehicle. Saved searches will alert teams when follow-on solicitations, amendments, or court filings appear on public sources.
• Proposal Studio (Proposal OS) and Proposal Studio Workflow Tracker — Use these to accelerate compliant proposal development, maintain audit-ready compliance matrices for DFARS/ITAR/NIST 800-171/CMMC, and execute the 9-gate capture workflow.

Who to notify: Capture manager, BD lead, proposal manager, contracts officer, security/compliance lead (DFARS/ITAR/NIST/CMMC), and executive sponsor.

First 48-hour playbook:

• Hour 0–4: Convene triage call with capture/BD/contracts/compliance. Preserve all proposal and protest-related documents and communications.
• Hour 4–12: Configure Cabrillo Signals Match Engine to rescore MUSV opportunities; create saved searches in Intelligence Hub for MUSV amendments and court filings.
• Hour 12–24: Run Proposal Studio compliance sweep against DFARS/ITAR/NIST/CMMC checklists; map gaps and assign remediation owners in Workflow Tracker.
• Hour 24–48: Prepare contingency capture plan for potential re-open or recompete; ready compliant proposal skeletons and cost/price inputs.

Relevant Cabrillo content and guides: Winning Federal Contracts Guide (/insights/winning-federal-contracts). For compliance and CUI (Controlled Unclassified Information) handling, see CMMC Compliance Guide (/insights/cmmc-compliance-guide) and CUI-Safe CRM Guide (/insights/cui-safe-crm-guide).