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

Executive Summary

Two defense technology firms — Blue Water Autonomy and Saildrone — have filed federal lawsuits after being excluded from the U.S. Navy's Medium Unmanned Surface Vessel (MUSV) Family of Systems program. The plaintiffs allege procedural and evaluation errors and one plaintiff has requested that MUSV testing and related funding be halted until they can re-enter the competition. Seven other companies were selected to proceed with at-sea prototype testing, making this a visible procurement dispute that could affect the Navy’s unmanned surface vessel acquisition timeline.

Market segments identified in the Tags (Defense; Unmanned Systems; Maritime Technology; Autonomous Vehicles; Naval Systems) are the most directly affected. Contractors in these segments should monitor the litigation, the Navy’s response, and any changes to MUSV evaluation or testing plans because the outcome could alter selection processes, near-term testing schedules, and partner or subcontractor opportunities. Compliance surfaces tagged with this event (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)) remain relevant for teams preparing to support MUSV or related efforts.

Impact Matrix

Defense

• Risk Level: Medium
• Opportunity: Compete for MUSV-related work and related Navy opportunities; Specific NAICS codes present in Tags: 336611, 541712, 541715, 336992, 541330. Specific opportunities (e.g., solicitations or sub-awards) TBD pending solicitation language.
• Timeline: Potential impact to the Navy's unmanned surface vessel acquisition timeline; a plaintiff has requested a halt to MUSV testing and funding pending re-entry.
• Action Required: Monitor litigation filings and Navy messaging; review proposal artifacts and past RFP responses for defensibility; refresh capture plans for MUSV and adjacent Navy programs.
• Competitive Edge: Maintain documented compliance with cited acquisition requirements and be ready to mobilize partnerships quickly if the Navy re-opens testing or recompetes portions of the program.

Unmanned Systems

• Risk Level: High
• Opportunity: Position prototypes and demonstrations for possible re-evaluation or for follow-on MUSV testing opportunities. Specific opportunities TBD pending solicitation language.
• Timeline: Timeline TBD pending source review, though the Summary flags possible pauses to MUSV testing and funding while litigation proceeds.
• Action Required: Ensure prototype readiness and test data are current; validate technical claims against expected evaluation criteria; secure or refresh agreements with test ranges and integration partners.
• Competitive Edge: Invest in demonstrable, testable capability records and clear traceability between system performance and evaluation criteria to withstand scrutiny in any revised selection process.

Maritime Technology

• Risk Level: Medium
• Opportunity: Support at-sea prototype testing, integration, and sustainment work tied to MUSV Family of Systems. Specific opportunities TBD pending solicitation language.
• Timeline: Timeline TBD pending source review; possible near-term disruption to scheduled at-sea testing.
• Action Required: Review contracts and subcontracts for schedule and funding risk; confirm readiness to meet Navy testing requirements should the selected teams remain or change.
• Competitive Edge: Demonstrate a resilient testing and logistics plan that mitigates schedule risk and helps the Navy keep prototype campaigns on track if the program proceeds.

Autonomous Vehicles

• Risk Level: High
• Opportunity: Offer autonomy stacks, sensors, or systems integration for MUSV prototypes or future competitions. Specific opportunities TBD pending solicitation language.
• Timeline: Timeline TBD pending source review; litigation could affect prototype testing windows.
• Action Required: Harden cybersecurity and supply chain compliance (per tagged compliance surfaces); preserve test records and IP protection measures to reduce barriers if re-entry or protest remedies occur.
• Competitive Edge: Pair robust cybersecurity posture with interoperable autonomy architectures to reduce perceived evaluation risk and appeal to evaluators focused on field survivability and integration.

Naval Systems

• Risk Level: High
• Opportunity: Engage on systems engineering, integration, and platform support for MUSV Family of Systems under Navy direction. Specific opportunities TBD pending solicitation language.
• Timeline: Potential to affect MUSV testing and acquisition pacing as noted in the Summary.
• Action Required: Track Navy procurements and communications for MUSV adjustments; validate that proposed system architectures align with Navy requirements and evaluation factors.
• Competitive Edge: Emphasize systems integration experience and prior naval testing support to be seen as lower-risk contributors in any revised prototyping or follow-on efforts.

Cross-Segment Implications

• Litigation around MUSV selection can pause or shift at-sea prototype testing, which directly affects Unmanned Systems, Maritime Technology, and Naval Systems contractors that rely on those test windows for evaluation and follow-on work.
• Changes in selection or testing schedules create downstream schedule and funding uncertainty across the supply chain, increasing the importance of contractual flexibility and preservation of test data for re-evaluation.
• The compliance surfaces tagged (DFARS, ITAR, NIST 800-171, CMMC) mean that cybersecurity, export control, and defense acquisition compliance remain gating factors across all segments; any repackaging or recompetition will favor teams already demonstrably compliant.
• Contractors that can rapidly demonstrate tested, integrated capabilities and strong compliance records stand to gain if the Navy re-opens competition or adjusts evaluation criteria, while teams lacking documentation or compliance posture are at higher risk of exclusion.