Navy Removes Head of Drone Programs After 8 Months, PAE Maritime Head Miller Now Leading PAE RAS

TL;DR

The Navy removed its Portfolio Acquisition Executive (PAE) for Robotic and Autonomous Systems (RAS) after only 8 months and created a new Direct Reporting Portfolio Manager for RAS who will report to the Under Secretary of the Navy. PAE Maritime Head Miller is now leading PAE RAS. The reorganization changes oversight for nearly 50 unmanned programs across the Navy and U.S. Marine Corps, including the $5 billion Medium Unmanned Surface Vehicle program. This is a significant shift in acquisition authority and accountability intended to address fragmented requirements and acquisition practices. Contractors working on maritime, air, and undersea unmanned systems should expect changes in program oversight, prioritization, and how industry engagement is managed. Immediate implications include accelerated monitoring of solicitations and contract vehicles, rapid update of capture and compliance strategies, and proactive engagement with Navy program offices as they reorganize.

Key Points

• What happened: The Navy removed its PAE for Robotic and Autonomous Systems after 8 months and created a Direct Reporting Portfolio Manager for RAS reporting to the Under Secretary of the Navy; PAE Maritime Head Miller now leads PAE RAS.
• Who is affected: Defense and unmanned-systems market segments, including firms mapped to NAICS 336411, 336414, 336992, 541330, 541712, 541715, 334511, 336611; agencies include DOD, Department of the Navy, and U.S. Marine Corps; contract vehicles cited include SeaPort-NxG and IDIQ (Indefinite Delivery/Indefinite Quantity) contracts for unmanned systems.
• Timeline: The change occurred after only 8 months (per the Summary).
• What contractors should do NOW: Immediately re-score opportunity pipelines, validate compliance posture for RAS work, update capture plans for affected programs (notably the Medium Unmanned Surface Vehicle program), and alert capture, BD, and security teams for targeted monitoring and outreach.

Who Is Affected

This reorganization impacts companies and teams engaged in unmanned and autonomous systems across maritime, aerial, and undersea domains. Specific NAICS codes, agencies, contract vehicles, market segments, and compliance regimes are explicitly identified in segmentation and are in-scope for monitoring and action:

• NAICS codes: 336411, 336414, 336992, 541330, 541712, 541715, 334511, 336611
• Agencies: DOD, Department of the Navy, U.S. Marine Corps
• Contract vehicles: SeaPort-NxG; IDIQ contracts for unmanned systems
• Market segments: Defense; Unmanned Systems; Autonomous Systems; Maritime Systems; Robotics; Unmanned Surface Vehicles; Unmanned Aerial Systems; Unmanned Underwater Vehicles
• Compliance surfaces: 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; EAR

Frequently Asked Questions

Q: What immediate contract-level impacts should contractors expect?

A: Expect changes in oversight and accountability that could alter program priorities and engagement channels for nearly 50 unmanned programs, including the Medium Unmanned Surface Vehicle program. Specific impacts to individual contracts, orders, or funding lines are pending source review.

Q: Will acquisition vehicles or solicitation routing change?

A: The Summary and segmentation flag SeaPort-NxG and IDIQ contracts for unmanned systems as relevant contract vehicles to watch. Whether solicitations or routing change materially is pending source review.

Q: Who is now overseeing RAS efforts inside the Navy?

A: PAE Maritime Head Miller is now leading PAE RAS, and a new Direct Reporting Portfolio Manager for RAS will report to the Under Secretary of the Navy. Further organizational details and named officials beyond Miller are pending source review.

Definitions

• Portfolio Acquisition Executive (PAE) for Robotic and Autonomous Systems (RAS): Senior acquisition executive responsible for portfolio-level acquisition oversight of robotic and autonomous systems programs (as referenced in the Title/Summary).
• Direct Reporting Portfolio Manager (for RAS): A portfolio-level manager position that reports directly to the Under Secretary of the Navy, established by this reorganization.
• Medium Unmanned Surface Vehicle (MUSV): The Medium Unmanned Surface Vehicle program referenced in the Summary, identified as a $5 billion program.

Intelligence Response

• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Use War Room for continuous alerts on organizational notices, leadership changes, and policy signals tied to RAS and unmanned portfolios.
• Cabrillo Signals Match Engine — Immediately rescore opportunity pipelines and priority lists so capture teams see which live opportunities and bids are most affected by this shift in acquisition authority.
• Cabrillo Signals Intelligence Hub — Activate saved searches for the listed NAICS codes, agencies, and contract vehicles (SeaPort-NxG and IDIQ unmanned systems) and enable SAM.gov (System for Award Management) solicitation alerts for follow-on actions.
• Proposal Studio (Proposal OS) and Proposal Studio Workflow Tracker — Update bid/no-bid decisions, compliance matrices, and 9-gate capture workflows; route security and compliance checks for DFARS/NIST/CMMC/ITAR/EAR review.

Notify: BD Director, Capture Manager, Program Manager for affected programs, Contracts Lead, Security/Compliance Lead, and CTO. First 48-hour playbook:

1. Hour 0–4: War Room alert to notification chain; run Match Engine rescore and activate Intelligence Hub saved searches for affected NAICS, agencies, and vehicles.

2. Hour 4–12: Triage live opportunities and existing task orders tied to affected programs (including MUSV); identify immediate risks to delivery and compliance.

3. Hour 12–24: Update bid/no-bid recommendations in Proposal Studio, run compliance gap analysis against NIST 800-171/CMMC/DFARS/ITAR/EAR, and prepare prioritized capture tasks.

4. Hour 24–48: Lock capture teams, produce outreach and questions for program offices, and begin proposal production and audit-ready documentation via Proposal Studio Workflow Tracker.