Blue Water Autonomy, Saildrone Sue Navy Over MUSV Rejection

Executive Summary

Two vendors (Saildrone and Blue Water Autonomy) have filed protests in the U.S. Court of Federal Claims challenging the Navy’s rejection of their proposals for the Medium Unmanned Surface Vessel (MUSV) program. The protests allege the Navy did not follow its own selection criteria after selecting seven contractors from roughly two dozen bidders for a program described in the Summary as a $5 billion effort that plans to procure 36 vessels in FY2026. Because the challenges target the evaluation and selection process, they could create program-level schedule risk for the MUSV prototype phase and create uncertainty about how the Navy will evaluate future offers.

Contractors in the named segments should pay attention now because litigation can produce delays, re-evaluations, or corrective actions that change award timing and requirements. Companies active in Defense, Autonomous Systems, Maritime/Naval Systems, Unmanned Systems, and Shipbuilding may see near-term impacts to business development pipelines and should prepare for both potential interruptions to the MUSV timeline and any shifts in evaluation emphasis that result from protest outcomes or corrective actions. Relevant compliance surfaces flagged in the event include ITAR (International Traffic in Arms Regulations), DFARS (Defense Federal Acquisition Regulation Supplement), and CMMC (Cybersecurity Maturity Model Certification); firms should ensure those areas remain well-documented and defensible in proposals.

Impact Matrix

Defense

• Risk Level: Medium
• Opportunity: Continued competition for a major Navy acquisition if the procurement re-opens or is adjusted; potential for re-evaluation opportunities. Specific opportunities TBD pending solicitation language.
• Relevant NAICS codes (from tags): 336611, 541330, 541712, 541715, 336612
• Timeline: Procurement plans include 36 vessels in FY2026; litigation could impact the MUSV prototype phase timeline.
• Action Required:
• Monitor litigation filings and Navy notices for potential corrective actions or re-solicitation.
• Review and document proposal compliance and evaluation rationale to support challenges or rapid re-bid.
• Ensure program-level compliance artifacts (especially related to DFARS/CMMC/ITAR) are current and auditable.
• Competitive Edge: Maintain an auditable, proposal-ready record of compliance and technical claims; establish teaming relationships to be prepared for rapid re-entry if the Navy re-opens competition.

Autonomous Systems

• Risk Level: High
• Opportunity: If evaluations are adjusted, technical evaluation criteria for autonomy could shift, creating space for differentiated technical approaches. Specific opportunities TBD pending solicitation language.
• Relevant NAICS codes (from tags): 336611, 541330, 541712, 541715, 336612
• Timeline: Plans to procure 36 vessels in FY2026; prototype-phase timing could be affected by the legal challenge.
• Action Required:
• Validate autonomy capabilities claims with test evidence and objective metrics that withstand scrutiny.
• Update and preserve supporting test data and integration plans to respond quickly to revised requirements.
• Coordinate legal/BD teams to track protest outcomes and implications for autonomy-related requirements.
• Competitive Edge: Invest in independently verifiable autonomy performance data and modular design documentation to reduce evaluation risk and make rapid proposal updates easier.

Maritime/Naval Systems

• Risk Level: Medium
• Opportunity: Potential changes to evaluation emphasis or corrective actions could create new openings for naval-systems integrators; Specific opportunities TBD pending solicitation language.
• Relevant NAICS codes (from tags): 336611, 541330, 541712, 541715, 336612
• Timeline: Procurement plans include 36 vessels in FY2026; litigation could shift prototype-phase milestones.
• Action Required:
• Confirm naval-systems design and integration assumptions are well-documented.
• Review subcontract and supply-chain commitments to ensure agility if schedule or scope changes.
• Reassess cost and schedule margins for prototype development in light of potential delays.
• Competitive Edge: Emphasize modular, shipboard integration approaches and supplier flexibility to adapt to revised Navy requirements quickly.

Unmanned Systems

• Risk Level: Medium
• Opportunity: Rework or re-evaluation of proposals could favor vendors with demonstrable unmanned-systems maturity; Specific opportunities TBD pending solicitation language.
• Relevant NAICS codes (from tags): 336611, 541330, 541712, 541715, 336612
• Timeline: Procurement plans include 36 vessels in FY2026; litigation could impact prototype-phase timing.
• Action Required:
• Maintain demonstration records, safety analyses, and system integration evidence to strengthen future proposals.
• Ensure compliance posture (ITAR/DFARS/CMMC) is addressed for unmanned-systems data and components.
• Prepare outreach to primes/teaming partners to reposition if awards are revised.
• Competitive Edge: Build a concise evidence package (performance datapoints, safety cases, SOC/IT controls) that shortens evaluator work and reduces perceived technical risk.

Shipbuilding

• Risk Level: Medium
• Opportunity: If the program’s competitive field changes, shipbuilders and yards that can support prototype construction or integration may gain opportunities; Specific opportunities TBD pending solicitation language.
• Relevant NAICS codes (from tags): 336611, 541330, 541712, 541715, 336612
• Timeline: Procurement plans include 36 vessels in FY2026; the prototype phase timeline could be impacted by litigation.
• Action Required:
• Review production scheduling and supplier commitments in case of schedule slips or re-planning.
• Validate cost estimates and capacity assumptions against potential delay scenarios.
• Keep teaming arrangements current to respond to corrected solicitations or re-awards.
• Competitive Edge: Demonstrate surge capacity, flexible scheduling, and prior ship integration experience to be a preferred partner if the program requires remediation or expanded competition.

Cross-Segment Implications

• Litigation over evaluation procedures for the MUSV program links Defense, Autonomous Systems, Maritime/Naval Systems, Unmanned Systems, and Shipbuilding: a corrective action or re-evaluation could change technical thresholds, evaluation weighting, or allowable teaming arrangements, cascading to subsystem suppliers, integrators, and yards.
• Compliance surfaces named in the tags (ITAR, DFARS, CMMC) are cross-cutting: any rework or re-bid will re-expose proposal data and system security documentation to close scrutiny across segments, increasing the value of mature compliance postures.
• Supply-chain and scheduling dependencies mean delays in the prototype phase could shift effort across primes, subs, and shipyards, affecting revenue timing and resource allocation for companies active in multiple of the named segments.
• NAICS codes in the tags indicate the types of firms likely watching this event; interoperability between autonomy software/hardware developers and shipbuilding/integration partners will be decisive if opportunities reopen or evaluation criteria change.